[Pacemaker] Fencing of movable VirtualDomains

[Andrew Beekhof]

On 6 Oct 2014, at 8:14 pm, Daniel Dehennin <daniel.dehennin at baby-gnu.org> wrote:

> Andrew Beekhof <andrew at beekhof.net> writes:
> 
>>> It may be due to two “order”:
>>> 
>>> #+begin_src
>>> order ONE-Frontend-after-its-Stonith inf: Stonith-ONE-Frontend ONE-Frontend
>>> order Quorum-Node-after-its-Stonith inf: Stonith-Quorum-Node Quorum-Node
>>> #+end_src
>> 
>> Probably. Any particular reason for them to exist?
> 
> Maybe not, the collocation should be sufficient, but even without the
> orders, unclean VMs fencing is tried with other Stonith devices.

Which other devices?  The config you sent through didnt have any others.

> 
> I'll switch to newer corosync/pacemaker and use the pacemaker_remote if
> I can manage dlm/cLVM/OCFS2 with it.

No can do.  All three services require corosync on the node. 

> 
> Regards.
> 
> -- 
> Daniel Dehennin
> Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
> Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20141007/07aeb442/attachment-0003.sig>