Hi,
On Thu, Feb 23, 2017 at 5:32 PM, wrote:
> Klaus Wenninger wrote on 02/23/2017 01:12:19 AM:
>
> > > There is a major issue with current setup in Windows. You have to
> > > start virtual machines from openssh connection if you wish to manage
>
Klaus Wenninger <kwenn...@redhat.com> wrote on 02/23/2017 01:12:19 AM:
> From: Klaus Wenninger <kwenn...@redhat.com>
> To: Cluster Labs - All topics related to open-source clustering
> welcomed <users@clusterlabs.org>
> Date: 02/23/2017 01:13 AM
> Subje
Marek Grac writes:
> Hi,
>
> we have added support for a host with Windows but it is not trivial to
> setup because of various contexts/privileges.
>
> Install openssh on Windows (tutorial can be found on
> http://linuxbsdos.com/2015/07/30/how-to-install-openssh-on-windows-10/)
On 02/23/2017 07:48 AM, Marek Grac wrote:
> Hi,
>
> we have added support for a host with Windows but it is not trivial to
> setup because of various contexts/privileges.
>
> Install openssh on Windows (tutorial can be found on
>
Hi,
we have added support for a host with Windows but it is not trivial to
setup because of various contexts/privileges.
Install openssh on Windows (tutorial can be found on
http://linuxbsdos.com/2015/07/30/how-to-install-openssh-on-windows-10/)
There is a major issue with current setup in
Hi,
I have updated fence agent for Virtual Box (upstream git). The main benefit
is new option --host-os (host_os on stdin) that supports linux|macos. So if
your host is linux/macos all you need to set is this option (and ssh access
to a machine). I would love to add a support also for windows but
Maybe you need some mapping between vbox-guest-names and pacemaker
node-names? (attribute pcmk_host_map)
That you are writing that you added the script as fence_virtual is probably
a typo in the mail ... and would probably create a different error
message ...
On 02/06/2017 07:06 PM, Jihed
Yeah, I see your point. :)
On Mon, Feb 6, 2017, 3:40 PM Klaus Wenninger wrote:
> On 02/06/2017 03:35 PM, Jihed M'selmi wrote:
> >
> > So do you suggest to used the sdb ?
> > The virtualbox was installed above Windows.
> >
>
> Just wanted to give you an option if you don't
On 02/06/2017 03:35 PM, Jihed M'selmi wrote:
>
> So do you suggest to used the sdb ?
> The virtualbox was installed above Windows.
>
Just wanted to give you an option if you don't have
a working fence-agent directly talking to the hypervisor -
which I would always prefer.
>
> On Mon, Feb 6,
So do you suggest to used the sdb ?
The virtualbox was installed above Windows.
On Mon, Feb 6, 2017, 3:20 PM Klaus Wenninger wrote:
> No experience with fencing vbox-VMs on my side either ...
> But as always when there is no physical fencing-device
> available sbd might be
No experience with fencing vbox-VMs on my side either ...
But as always when there is no physical fencing-device
available sbd might be a way to go - either with just
a watchdog (guess vbox offers a virtual watchdog that
is supported by the linux-kernel or at least if you install
the guest-support
Not really, I found something in some google group but, it's not documented
(if I am not wrong).
On Mon, Feb 6, 2017, 2:21 PM Marek Grac wrote:
> Hi,
>
> I don't have one. But I see a lot of question about fence_vbox in last
> days, is there any new material that references
Hi,
I don't have one. But I see a lot of question about fence_vbox in last
days, is there any new material that references it?
m,
On Mon, Feb 6, 2017 at 1:56 PM, Jihed M'selmi
wrote:
> Hi,
>
> I want set up a pcmk/corosync cluster using couple vbox nodes.
>
> Anyone
Hi,
I want set up a pcmk/corosync cluster using couple vbox nodes.
Anyone could.share how to install/configure a fence agent fence_vbox ?
Cheers
JM
--
J.M
___
Users mailing list: Users@clusterlabs.org
14 matches
Mail list logo