On Mon, May 16, 2011 at 5:38 PM, RaSca ra...@miamammausalinux.org wrote:
Il giorno Lun 16 Mag 2011 09:01:08 CET, Andrew Beekhof ha scritto:
[...]
Implicit that once the resource go away it becomes slave?
Pretty sure this is a bug in 1.0.
Have you tried 1.1.5 ?
Not yet, but so Andrew are
On Sat, May 14, 2011 at 9:31 AM, RaSca ra...@miamammausalinux.org wrote:
Il giorno Ven 13 Mag 2011 16:09:14 CET, Viacheslav Biriukov ha scritto:
In your case you have two drbd master. So, I think, it is not a good
idea to create that collocation. Instead of this you can set location
directives
Il giorno Lun 16 Mag 2011 09:01:08 CET, Andrew Beekhof ha scritto:
[...]
Implicit that once the resource go away it becomes slave?
Pretty sure this is a bug in 1.0.
Have you tried 1.1.5 ?
Not yet, but so Andrew are you saying that keeping the colocation even
if I have a dual primary drbd is
Il giorno Ven 13 Mag 2011 16:09:14 CET, Viacheslav Biriukov ha scritto:
In your case you have two drbd master. So, I think, it is not a good
idea to create that collocation. Instead of this you can set location
directives to locate vm-test_virtualdomain where you want to be default.
For
Hi all,
I've got a setup with a dual primary DRBD with over it a KVM virtual
machine, managed by a Virtualdomain resource.
In a classical primary-seconday setup, the declaration of the resource is:
primitive vm-test_r0 ocf:linbit:drbd \
params drbd_resource=r0 \
op monitor
In your case you have two drbd master. So, I think, it is not a good idea to
create that collocation. Instead of this you can set location directives to
locate vm-test_virtualdomain where you want to be default. For example:
location L_vm-test_virtualdomain_01 vm-test_virtualdomain 100:
