[Pacemaker] How to properly define DRBD resources

[Michał Margula]

Hello!

Let me go trough it to see if I understand correctly:

W dniu 17.12.2013 08:57, Nikita Staroverov pisze:
> primitive drbd_YOURVM ocf:linbit:drbd \
>          params drbd_resource="YOURVM" \
>          op monitor interval="29s" role="Master" \
>          op monitor interval="31s" role="Slave"
>
>

So here difference is target-role dropped? I had "Started" here.


> primitive kvm_YOURVM ocf:heartbeat:VirtualDomain \
>          params config="/etc/libvirt/qemu/YOURVM.xml"
> migration_transport="ssh" \
>          meta allow-migrate="false" target-role="Started"
> is-managed="true" \
>          op start interval="0" timeout="120s" \
>          op stop interval="0" timeout="120s" \
>          op monitor interval="60s" timeout="120s"

Here seems to be the same (I use xen but it shouldn't matter).

>
> ms ms_drbd_YOURVM drbd_YOURVM \
>          meta master-max="1" master-node-max="1" clone-max="2"
> clone-node-max="1" notify="true" target-role="Started" is-managed="true"
>

So here target-role is "Started" instead of "Master". And I have 
master-max set to 2 and you have set to 1. It causes to have Master 
(Primary DRBD) on one node and Slave (Secondary DRBD) on another?

> location kvm_YOURVM_prefer_YOURFIRSTSERVER kvm_YOURVM 50: YOURFIRSTSERVER

It is optional? I mean it should not have any impact on DRBD configuration.

> order kvm_YOURVM_after_drbd_YOURVM inf: ms_drbd_YOURVM:promote
> kvm_YOURVM:start

Same here.

> In my configuration VM's works with primary/secondary drbd.

Why not dual primary? Is there a reason for that?

Thank you for your help!

-- 
Michał Margula, alchemyx at uznam.net.pl, http://alchemyx.uznam.net.pl/
"W życiu piękne są tylko chwile" [Ryszard Riedel]