Mailing List Archive

Configuring Dependencies and Groups in CRM
Hello,

I've a cluster with two nodes with a master-slave DRBD and filesystem.
On top of the filesystem there are several OpenVZ containers which are
managed by ocf:heartbeat:ManageVE.

Currently I've configured the VEs within one group together with DRBD
and filesystem. This setup is running fine but creates a depencency
between the VEs which is not neccessary and makes it impossible to stop
one VE without restarting all VEs that come later in the group.

Is there any possibility to configure the filesystem as depencency for
all VEs but not to define an order between the VEs? I've tried to create
seperate groups for all VEs but then CRM warns that the filesystem
resource is already in use.

Important parts from CRM:

------------------------------------------------------------
primitive res_DRBD ocf:heartbeat:drbd
primitive res_Filesystem ocf:heartbeat:Filesystem

primitive res_ve100 ocf:heartbeat:ManageVE
primitive res_ve101 ocf:heartbeat:ManageVE
primitive res_ve102 ocf:heartbeat:ManageVE
primitive res_ve103 ocf:heartbeat:ManageVE

group group_VE res_Filesystem res_ve100 res_ve101 res_ve102 res_ve103

ms ms_DRBD res_DRBD

colocation col_FSDRBD inf: group_VE ms_DRBD:Master

order order_DRBDFS inf: ms_DRBD:promote group_VE:start
------------------------------------------------------------

Thanks, Stephan


_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: Configuring Dependencies and Groups in CRM [ In reply to ]
> On 17 Nov 2014, at 12:54 am, Stephan <stephan@projectlabs.de> wrote:
>
> Hello,
>
> I've a cluster with two nodes with a master-slave DRBD and filesystem. On top of the filesystem there are several OpenVZ containers which are managed by ocf:heartbeat:ManageVE.
>
> Currently I've configured the VEs within one group together with DRBD and filesystem. This setup is running fine but creates a depencency between the VEs which is not neccessary and makes it impossible to stop one VE without restarting all VEs that come later in the group.
>
> Is there any possibility to configure the filesystem as depencency for all VEs but not to define an order between the VEs? I've tried to create seperate groups for all VEs but then CRM warns that the filesystem resource is already in use.

Don't use groups. Use colocation and ordering constraints instead.

>
> Important parts from CRM:
>
> ------------------------------------------------------------
> primitive res_DRBD ocf:heartbeat:drbd
> primitive res_Filesystem ocf:heartbeat:Filesystem
>
> primitive res_ve100 ocf:heartbeat:ManageVE
> primitive res_ve101 ocf:heartbeat:ManageVE
> primitive res_ve102 ocf:heartbeat:ManageVE
> primitive res_ve103 ocf:heartbeat:ManageVE
>
> group group_VE res_Filesystem res_ve100 res_ve101 res_ve102 res_ve103
>
> ms ms_DRBD res_DRBD
>
> colocation col_FSDRBD inf: group_VE ms_DRBD:Master
>
> order order_DRBDFS inf: ms_DRBD:promote group_VE:start
> ------------------------------------------------------------
>
> Thanks, Stephan
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org


_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org