> On 8 Nov 2014, at 11:58 am, aridh bose wrote:
>
> Hi,
>
> While using heartbeat and pacemaker, is it possible to bringup first node
> which can go as Master, followed by second node which should go as Slave
> without causing any issues to the first node? Currently, I see a couple of
> pro
> On 9 Nov 2014, at 9:28 pm, Matthias Teege wrote:
>
> Hallo,
>
> On a cluster I have to place three resources on the same node.
>
> ms ms_disk_R p_disk_R
> ms ms_disk_S p_disk_S
> primitive vm_srv ocf:heartbeat:VirtualDomain
>
> The colocation constraints looks like this:
>
> colocation vm
> On 8 Nov 2014, at 10:22 pm, Matthias Teege wrote:
>
> Hello,
>
> I have a cluster with 300 resources. A lot of them are using the
> same monitoring intervalls. Is it necessary to increase the
> batch-limit to allow pacemaker to run all monitoring scripts in
> parallel?
Short version... it sh
I think you can use a single colocation with a set of resources. crmsh
allows you to create such a colocation with:
crm colocation vm_with_disks inf: vm_srv ( ms_disk_R:Master
ms_disk_S:Master )
This forces the cluster to place the master resources on the same host,
starting them without specific
Hallo,
On a cluster I have to place three resources on the same node.
ms ms_disk_R p_disk_R
ms ms_disk_S p_disk_S
primitive vm_srv ocf:heartbeat:VirtualDomain
The colocation constraints looks like this:
colocation vm_with_disk_R inf: vm_srv ms_disk_R:Master
colocation vm_with_disk_S inf: vm_sr
