[ClusterLabs] How to Fence Virtualbox VM with Windows 10 as host.

[durwin at mgtsciences.com]

Marek Grac <mgrac at redhat.com> wrote on 01/25/2017 01:33:07 AM:

> From: Marek Grac <mgrac at redhat.com>
> To: Cluster Labs - All topics related to open-source clustering 
> welcomed <users at clusterlabs.org>
> Date: 01/25/2017 01:34 AM
> Subject: Re: [ClusterLabs] How to Fence Virtualbox VM with Windows 10 as 
host.
> 
> Hi,
> 
> On Tue, Jan 24, 2017 at 9:06 PM, <durwin at mgtsciences.com> wrote:
> This is my first attempt at clustering, just so you know the level 
> required to convey ideas. 
> 
> I have Windows 10 running Virtualbox with 2 VMs running Fedora 25.  
> I have followed 'Pacemaker 1.1 Clusters from Scratch' 9th edition up
> through chapter 7.  It works.  I am uncertain as how to fence the 
> VMs with Windows 10 as host.  The output from 'pcs stonith describe 
> fence_vbox' is below. 
> 
> I have Cygwin installed with sshd configured and running.  I can 
> remotely ssh into the Windows 10 machine.  I can add the keys from 
> the machines into Windows authorized_keys so no user/password is 
> required.  I however do not know which of the options are 
> *required*.  Nor do I know what the options should be set to.  Some 
> of the options *are* obvious.  If I use *only* required ones, ipaddr
> is obvious, login is obvious, but not sure what port is.  Would it 
> be the name of the VM as Virtualbox knows it? 
> 
>         ipaddr (required): IP address or hostname of fencing device 
>         login (required): Login name 
>         port (required): Physical plug number on device, UUID or 
> identification of machine 
> 
> Does the host require anything running on it to support the fence?  
> Do I require any other options in addition to 'required'?  How do I 
> test it from a nodes commandline? 
> 
> You can take  a look at manual page of fence_vbox (or run 
fence_vbox--help). 
> 
> In your case it should be enough to set:
> * ipaddr
> * login
> * port (= node to shutdown)

Thank you.  man page says.

       -n, --plug=[id]
              Physical plug number on device, UUID or identification of 
machine This parameter is always required.

How do I determine the 'plug' of the VM?  I the output of 'pcs stonith 
describe fence_vbox' refers to this as port (to my understanding, very 
misleading).

>From your reply, am I correct in assuming nothing to support Fencing is 
required to run on the Windows host?

Thank you,

Durwin

> * identity_file (= private key)
> 
> m,_______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org



This email message and any attachments are for the sole use of the 
intended recipient(s) and may contain proprietary and/or confidential 
information which may be privileged or otherwise protected from 
disclosure. Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient(s), please contact the 
sender by reply email and destroy the original message and any copies of 
the message as well as any attachments to the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170125/315e3ccb/attachment-0003.html>