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

Marek Grac mgrac at redhat.com
Wed Jan 25 03:33:07 EST 2017


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)
* identity_file (= private key)

m,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170125/3b3c809e/attachment-0003.html>


More information about the Users mailing list