Re: [ClusterLabs] different start/stop order

2017-11-01 Thread Ken Gaillot
On Wed, 2017-11-01 at 09:44 +0100, Stefan Krueger wrote: > Hello Ken, > > thanks for you help, at the moment it looks like this (its not > final): > crm(live)# conf sho > node 1084815873: zfs-serv1 > node 1084815874: zfs-serv2 > primitive HA_IP-Serv1 IPaddr2 \ > params ip=172.16.101.70

Re: [ClusterLabs] different start/stop order

2017-10-31 Thread Ken Gaillot
On Fri, 2017-10-27 at 22:08 +0200, Stefan Krueger wrote: > Hello Ken, thanks for this information! > > > You can make ordering constraints asymmetrical, > > so they only apply in the listed direction: > > > > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pace > >

Re: [ClusterLabs] different start/stop order

2017-10-27 Thread Stefan Krueger
Hello Ken, thanks for this information! > You can make ordering constraints asymmetrical, > so they only apply in the listed direction: > > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#s-resource-ordering Ok but i see only how can i create a

Re: [ClusterLabs] different start/stop order

2017-10-27 Thread Ken Gaillot
On Fri, 2017-10-27 at 14:35 +0200, Stefan Krueger wrote: > Hello, > > is it possible to start a ressource in a different way then they > stopped? > eg: > primitive HA_IP-Serv1 IPaddr2 \ > params ip=172.16.101.70 cidr_netmask=16 \ > op monitor interval=20 timeout=30 on-fail=restart

[ClusterLabs] different start/stop order

2017-10-27 Thread Stefan Krueger
Hello, is it possible to start a ressource in a different way then they stopped? eg: primitive HA_IP-Serv1 IPaddr2 \ params ip=172.16.101.70 cidr_netmask=16 \ op monitor interval=20 timeout=30 on-fail=restart nic=bond0 \ meta target-role=Started primitive HA_IP-Serv2