Re: [Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby - possible solution?

2014-05-20 Thread Ian
On , Andrew Beekhof wrote: On 19 May 2014, at 4:17 pm, Andrew Beekhof wrote: On 16 May 2014, at 3:41 am, Ian wrote: Doing some experiments and Reading TFM, I found this: 5.2.2. Advisory Ordering When the kind=Optional option is specified for an order constraint, the constraint is conside

Re: [Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby - possible solution?

2014-05-19 Thread Andrew Beekhof
On 19 May 2014, at 4:17 pm, Andrew Beekhof wrote: > > On 16 May 2014, at 3:41 am, Ian wrote: > >> Doing some experiments and Reading TFM, I found this: >> >> 5.2.2. Advisory Ordering >> When the kind=Optional option is specified for an order constraint, the >> constraint is considered optio

Re: [Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby - possible solution?

2014-05-18 Thread Andrew Beekhof
On 16 May 2014, at 3:41 am, Ian wrote: > Doing some experiments and Reading TFM, I found this: > > 5.2.2. Advisory Ordering > When the kind=Optional option is specified for an order constraint, the > constraint is considered optional and only has an effect when both resources > are stopping a

Re: [Pacemaker] Pacemaker unnecessarily (?) restarts a vm on active node when other node brought out of standby - possible solution?

2014-05-15 Thread Ian
Doing some experiments and Reading TFM, I found this: 5.2.2. Advisory Ordering When the kind=Optional option is specified for an order constraint, the constraint is considered optional and only has an effect when both resources are stopping and/or starting. Any change in state of the first res