I'm currently building a ovirt test-environment using nested virtualization on libvirt/kvm. For the most part this works great. However, I can't configure fencing/power management because only hardware BMC's/fencing devices are supported. Is this something that could/should be included in a future oVirt version? Or is there another option/workaround to test power management?
On 11/13/2013 07:47 AM, Sander Grendelman wrote:
I'm currently building a ovirt test-environment using nested virtualization on libvirt/kvm.
For the most part this works great. However, I can't configure fencing/power management because only hardware BMC's/fencing devices are supported.
Is this something that could/should be included in a future oVirt version? Or is there another option/workaround to test power management? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
please elaborate a bit more on what's missing. what are you trying to fence and from where?
I'm running an ovirt environment (two virt hosts and one engine host) on libvirt/kvm on fedora 19. (nested KVM). I want to fence the virtualized virtualization hosts from the engine host (or their partner host) through libvirt. Fence-virt can do this. I know this is a bit of a niche case, but it's very useful for testing/demo purposes. On Wed, Nov 13, 2013 at 8:33 PM, Itamar Heim <iheim@redhat.com> wrote:
On 11/13/2013 07:47 AM, Sander Grendelman wrote:
I'm currently building a ovirt test-environment using nested virtualization on libvirt/kvm.
For the most part this works great. However, I can't configure fencing/power management because only hardware BMC's/fencing devices are supported.
Is this something that could/should be included in a future oVirt version? Or is there another option/workaround to test power management? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
please elaborate a bit more on what's missing. what are you trying to fence and from where?
On 11/13/2013 04:27 PM, Sander Grendelman wrote:
I'm running an ovirt environment (two virt hosts and one engine host) on libvirt/kvm on fedora 19. (nested KVM).
I want to fence the virtualized virtualization hosts from the engine host (or their partner host) through libvirt. Fence-virt can do this.
I know this is a bit of a niche case, but it's very useful for testing/demo purposes.
you can just edit the configs to add it (may be overridden during upgrade): VdsFenceType, VdsFenceOptionMapping and VdsFenceOptionTypes
On Wed, Nov 13, 2013 at 8:33 PM, Itamar Heim <iheim@redhat.com> wrote:
On 11/13/2013 07:47 AM, Sander Grendelman wrote:
I'm currently building a ovirt test-environment using nested virtualization on libvirt/kvm.
For the most part this works great. However, I can't configure fencing/power management because only hardware BMC's/fencing devices are supported.
Is this something that could/should be included in a future oVirt version? Or is there another option/workaround to test power management? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
please elaborate a bit more on what's missing. what are you trying to fence and from where?
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Sander Grendelman" <sander@grendelman.com> Cc: users@ovirt.org, "Eli Mesika" <emesika@redhat.com> Sent: Thursday, November 14, 2013 3:04:39 AM Subject: Re: [Users] Fence-virt support
On 11/13/2013 04:27 PM, Sander Grendelman wrote:
I'm running an ovirt environment (two virt hosts and one engine host) on libvirt/kvm on fedora 19. (nested KVM).
I want to fence the virtualized virtualization hosts from the engine host (or their partner host) through libvirt. Fence-virt can do this.
I know this is a bit of a niche case, but it's very useful for testing/demo purposes.
you can just edit the configs to add it (may be overridden during upgrade): VdsFenceType, VdsFenceOptionMapping and VdsFenceOptionTypes
Did that worked for you or do you need any further help? Thanks Eli
On Wed, Nov 13, 2013 at 8:33 PM, Itamar Heim <iheim@redhat.com> wrote:
On 11/13/2013 07:47 AM, Sander Grendelman wrote:
I'm currently building a ovirt test-environment using nested virtualization on libvirt/kvm.
For the most part this works great. However, I can't configure fencing/power management because only hardware BMC's/fencing devices are supported.
Is this something that could/should be included in a future oVirt version? Or is there another option/workaround to test power management? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
please elaborate a bit more on what's missing. what are you trying to fence and from where?
It "kind of" worked. I did an insert into the database to add an "xvm" fence mode. After that I had to first change the mode to ipmilan to get rid of a couple of mandatory fields. The setup also breaks when I try to edit a host. The fence mechanism makes a couple of assumptions that don't work with fence-virtd: - fence-virtd uses a keyfile, no username and password. - fence-virtd uses port=vmname to identify a VM The gui has mandatory username and password fields and the standard port/sshport field only takes numeric values. Some of the problems I ran into are probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1020344 On Mon, Nov 18, 2013 at 1:26 PM, Eli Mesika <emesika@redhat.com> wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Sander Grendelman" <sander@grendelman.com> Cc: users@ovirt.org, "Eli Mesika" <emesika@redhat.com> Sent: Thursday, November 14, 2013 3:04:39 AM Subject: Re: [Users] Fence-virt support
On 11/13/2013 04:27 PM, Sander Grendelman wrote:
I'm running an ovirt environment (two virt hosts and one engine host) on libvirt/kvm on fedora 19. (nested KVM).
I want to fence the virtualized virtualization hosts from the engine host (or their partner host) through libvirt. Fence-virt can do this.
I know this is a bit of a niche case, but it's very useful for testing/demo purposes.
you can just edit the configs to add it (may be overridden during upgrade): VdsFenceType, VdsFenceOptionMapping and VdsFenceOptionTypes
Did that worked for you or do you need any further help? Thanks Eli
On Wed, Nov 13, 2013 at 8:33 PM, Itamar Heim <iheim@redhat.com> wrote:
On 11/13/2013 07:47 AM, Sander Grendelman wrote:
I'm currently building a ovirt test-environment using nested virtualization on libvirt/kvm.
For the most part this works great. However, I can't configure fencing/power management because only hardware BMC's/fencing devices are supported.
Is this something that could/should be included in a future oVirt version? Or is there another option/workaround to test power management? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
please elaborate a bit more on what's missing. what are you trying to fence and from where?
----- Original Message -----
From: "Sander Grendelman" <sander@grendelman.com> To: "Eli Mesika" <emesika@redhat.com> Cc: users@ovirt.org Sent: Monday, November 18, 2013 3:52:09 PM Subject: Re: [Users] Fence-virt support
It "kind of" worked.
I did an insert into the database to add an "xvm" fence mode. After that I had to first change the mode to ipmilan to get rid of a couple of mandatory fields. The setup also breaks when I try to edit a host.
The fence mechanism makes a couple of assumptions that don't work with fence-virtd:
- fence-virtd uses a keyfile, no username and password.
This is a real problem , we are not supporting currently other authentication methods
- fence-virtd uses port=vmname to identify a VM
The gui has mandatory username and password fields and the standard port/sshport field only takes numeric values.
For that we have the options field , you could omit the port from the fence mapping and then add in the options "port=<value>"
Some of the problems I ran into are probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1020344
This is actually related to another BZ https://bugzilla.redhat.com/show_bug.cgi?id=1014513
On Mon, Nov 18, 2013 at 1:26 PM, Eli Mesika <emesika@redhat.com> wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Sander Grendelman" <sander@grendelman.com> Cc: users@ovirt.org, "Eli Mesika" <emesika@redhat.com> Sent: Thursday, November 14, 2013 3:04:39 AM Subject: Re: [Users] Fence-virt support
On 11/13/2013 04:27 PM, Sander Grendelman wrote:
I'm running an ovirt environment (two virt hosts and one engine host) on libvirt/kvm on fedora 19. (nested KVM).
I want to fence the virtualized virtualization hosts from the engine host (or their partner host) through libvirt. Fence-virt can do this.
I know this is a bit of a niche case, but it's very useful for testing/demo purposes.
you can just edit the configs to add it (may be overridden during upgrade): VdsFenceType, VdsFenceOptionMapping and VdsFenceOptionTypes
Did that worked for you or do you need any further help? Thanks Eli
On Wed, Nov 13, 2013 at 8:33 PM, Itamar Heim <iheim@redhat.com> wrote:
On 11/13/2013 07:47 AM, Sander Grendelman wrote:
I'm currently building a ovirt test-environment using nested virtualization on libvirt/kvm.
For the most part this works great. However, I can't configure fencing/power management because only hardware BMC's/fencing devices are supported.
Is this something that could/should be included in a future oVirt version? Or is there another option/workaround to test power management? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
please elaborate a bit more on what's missing. what are you trying to fence and from where?
On Mon, Nov 18, 2013 at 3:08 PM, Eli Mesika <emesika@redhat.com> wrote:
- fence-virtd uses a keyfile, no username and password.
This is a real problem , we are not supporting currently other authentication methods Yes, It's probably going to take a bit of a hack to make this work with the current mechanism/gui because the key file has to be an actual _file_.
I just made a local config + keyfile for my testnodes.
- fence-virtd uses port=vmname to identify a VM
The gui has mandatory username and password fields and the standard port/sshport field only takes numeric values.
For that we have the options field , you could omit the port from the fence mapping and then add in the options "port=<value>"
Yes that's what I did. One of the problems with that is that port= maps to the sshport field in the apc part of the gui which brings us back to BZ 1014513.
Some of the problems I ran into are probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1020344
This is actually related to another BZ https://bugzilla.redhat.com/show_bug.cgi?id=1014513
Yes, that's actually the one I meant but I couldn't find it.
----- Original Message -----
From: "Sander Grendelman" <sander@grendelman.com> To: "Eli Mesika" <emesika@redhat.com> Cc: users@ovirt.org Sent: Monday, November 18, 2013 4:25:16 PM Subject: Re: [Users] Fence-virt support
On Mon, Nov 18, 2013 at 3:08 PM, Eli Mesika <emesika@redhat.com> wrote:
- fence-virtd uses a keyfile, no username and password.
This is a real problem , we are not supporting currently other authentication methods Yes, It's probably going to take a bit of a hack to make this work with the current mechanism/gui because the key file has to be an actual _file_.
I just made a local config + keyfile for my testnodes.
- fence-virtd uses port=vmname to identify a VM
The gui has mandatory username and password fields and the standard port/sshport field only takes numeric values.
For that we have the options field , you could omit the port from the fence mapping and then add in the options "port=<value>"
Yes that's what I did. One of the problems with that is that port= maps to the sshport field in the apc part of the gui which brings us back to BZ 1014513.
You should add a new agent type to VdsFenceType config values then add the relevant info to (without port) for this agent to VdsFenceOptionMapping Then , when you are selecting it from the UI , the ssh port should not be shown and you can use it in the options field
Some of the problems I ran into are probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1020344
This is actually related to another BZ https://bugzilla.redhat.com/show_bug.cgi?id=1014513
Yes, that's actually the one I meant but I couldn't find it.
participants (3)
-
Eli Mesika -
Itamar Heim -
Sander Grendelman