Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
On 02/20/2014 11:38 AM, Matt Riedemann wrote: On 2/19/2014 4:05 PM, Matt Riedemann wrote: The os-hosts OS API extension [1] showed up before I was working on the project and I see that only the VMware and XenAPI drivers implement it, but was wondering why the libvirt driver doesn't - either no one wants it, or there is some technical reason behind not implementing it for that driver? [1] http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-hosts-v2_updateHost_v2__tenant_id__os-hosts__host_name__ext-os-hosts.html By the way, am I missing something when I think that this extension is already covered if you're: 1. Looking to get the node out of the scheduling loop, you can just disable it with os-services/disable? 2. Looking to evacuate instances off a failed host (or one that's in "maintenance mode"), just use the evacuate server action. In compute/api.py the API.evacuate() routine errors out if self.servicegroup_api.service_is_up(service) is true, which means that you can't evacuate from a compute node that is "disabled", you need to migrate instead. So, the alternative is basically to disable the service, then get a list of all the servers on the compute host, then kick off the migration (either cold or live) of each of the servers. Then because migration uses a "cast" instead of a "call" you need to poll all the migrations for success or late failures. Once you have no failed migrations and no servers running on the host then you're good. Chris ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
On Sunday, February 23, 2014 12:41:15 PM, Jay Pipes wrote: On Sun, 2014-02-23 at 09:14 +0800, Jay Lau wrote: So there is no need to implement libvirt driver for the host_maintenance_mode API as host_maintenance_mode is mainly for VMWare and XenServer, also we can use evacuate and os-services/disable for libvirt host maintain, right? At a minimum, can we please make the API consistent in regards to what we call this operation (evacuation, "host maintenance", enable/disable, etc). Death to API extensions. Best, -another jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Well, the other thing here is we have no Tempest coverage of this virt driver API since only xenapi and vmware drivers implement it and community Tempest runs against the libvirt driver. I'm not aware of anything in Tempest that allows automatically detecting virt driver-specific APIs that we can test, like get_diagnostics. XenServer CI and MineSweeper could run against these in Tempest otherwise, we just don't have tests defined. -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
On Sun, 2014-02-23 at 09:14 +0800, Jay Lau wrote: > So there is no need to implement libvirt driver for the > host_maintenance_mode API as host_maintenance_mode is mainly for > VMWare and XenServer, also we can use evacuate and os-services/disable > for libvirt host maintain, right? At a minimum, can we please make the API consistent in regards to what we call this operation (evacuation, "host maintenance", enable/disable, etc). Death to API extensions. Best, -another jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
Hi, Plesae note that regarding the Vmware driver the maintenance mode only works with the ESX driver and not the VC driver. For the VC driver there is a patch in review - https://review.openstack.org/#/c/72143/ Thanks Gary From: Jay Lau mailto:jay.lau@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Sunday, February 23, 2014 3:14 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API? So there is no need to implement libvirt driver for the host_maintenance_mode API as host_maintenance_mode is mainly for VMWare and XenServer, also we can use evacuate and os-services/disable for libvirt host maintain, right? Thanks, Jay 2014-02-23 5:22 GMT+08:00 Bruce Montague mailto:bruce_monta...@symantec.com>>: On Fri Feb 21 21:14:56 UTC 2014 Joe Gordon https://urldefense.proofpoint.com/v1/url?u=http://gmail.com&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=qZox2RtL9TtyfQTCmPHLVKpeImL2Fe1NG33oxxlIFTU%3D%0A&s=aa22811e8ac28f6361f9a621b6fddd174c06e474b0585238e1ef7d294f5fe501>> wrote: > On Thu, Feb 20, 2014 at 9:38 AM, Matt Riedemann linux.vnet.ibm.com<https://urldefense.proofpoint.com/v1/url?u=http://linux.vnet.ibm.com&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=qZox2RtL9TtyfQTCmPHLVKpeImL2Fe1NG33oxxlIFTU%3D%0A&s=d0e9aac9517d6900c84731a432cf9180404b53911f3b683c6d41860465926d44>> > wrote: >> >> >> On 2/19/2014 4:05 PM, Matt Riedemann wrote: >>> >>> The os-hosts OS API extension [1] showed up before I was working on the >>> project and I see that only the VMware and XenAPI drivers implement it, >>> but was wondering why the libvirt driver doesn't - either no one wants >>> it, or there is some technical reason behind not implementing it for >>> that driver? >>> > > If I remember correctly maintenance mode is a special thing in Xen. Maintenance mode is pretty heavily used with VMware vCenter. When an environment supports "universal" live migration of all VMs, it makes sense to migrate all VMs running on a physical machine off of that machine before bringing it down for maintenance, such as upgrading the hardware. Provides some classes of end-users with a more 24x7x365 experience. >>> [1] >>> >>> http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-hosts-v2_updateHost_v2__tenant_id__os-hosts__host_name__ext-os-hosts.html<https://urldefense.proofpoint.com/v1/url?u=http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-hosts-v2_updateHost_v2__tenant_id__os-hosts__host_name__ext-os-hosts.html&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=qZox2RtL9TtyfQTCmPHLVKpeImL2Fe1NG33oxxlIFTU%3D%0A&s=8120001d41ddc39e4e5edf7721c4f47ea324a388dfb95cad944a140fa8b257de> >>> >>> >> >> By the way, am I missing something when I think that this extension is >> already covered if you're: >> >> 1. Looking to get the node out of the scheduling loop, you can just disable >> it with os-services/disable? >> >> 2. Looking to evacuate instances off a failed host (or one that's in >> "maintenance mode"), just use the evacuate server action. > > I don't think your missing anything. > >> >> >> -- >> >> Thanks, >> >> Matt Riedemann >> >> -bruce ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=qZox2RtL9TtyfQTCmPHLVKpeImL2Fe1NG33oxxlIFTU%3D%0A&s=7d513d1b8c61f68ad14e8f896d90dab47a2eb82e320c9a4f6542a0f677b26349> -- Thanks, Jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
So there is no need to implement libvirt driver for the host_maintenance_mode API as host_maintenance_mode is mainly for VMWare and XenServer, also we can use evacuate and os-services/disable for libvirt host maintain, right? Thanks, Jay 2014-02-23 5:22 GMT+08:00 Bruce Montague : > > On Fri Feb 21 21:14:56 UTC 2014 Joe Gordon > wrote: > > > On Thu, Feb 20, 2014 at 9:38 AM, Matt Riedemann linux.vnet.ibm.com> wrote: > >> > >> > >> On 2/19/2014 4:05 PM, Matt Riedemann wrote: > >>> > >>> The os-hosts OS API extension [1] showed up before I was working on the > >>> project and I see that only the VMware and XenAPI drivers implement it, > >>> but was wondering why the libvirt driver doesn't - either no one wants > >>> it, or there is some technical reason behind not implementing it for > >>> that driver? > >>> > > > > If I remember correctly maintenance mode is a special thing in Xen. > > > Maintenance mode is pretty heavily used with VMware vCenter. When an > environment supports "universal" live migration of all VMs, it makes sense > to migrate all VMs running on a physical machine off of that machine before > bringing it down for maintenance, such as upgrading the hardware. Provides > some classes of end-users with a more 24x7x365 experience. > > > >>> [1] > >>> > >>> > http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-hosts-v2_updateHost_v2__tenant_id__os-hosts__host_name__ext-os-hosts.html > >>> > >>> > >> > >> By the way, am I missing something when I think that this extension is > >> already covered if you're: > >> > >> 1. Looking to get the node out of the scheduling loop, you can just > disable > >> it with os-services/disable? > >> > >> 2. Looking to evacuate instances off a failed host (or one that's in > >> "maintenance mode"), just use the evacuate server action. > > > > I don't think your missing anything. > > > >> > >> > >> -- > >> > >> Thanks, > >> > >> Matt Riedemann > >> > >> > > > > -bruce > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Thanks, Jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
On Fri Feb 21 21:14:56 UTC 2014 Joe Gordon wrote: > On Thu, Feb 20, 2014 at 9:38 AM, Matt Riedemann linux.vnet.ibm.com> wrote: >> >> >> On 2/19/2014 4:05 PM, Matt Riedemann wrote: >>> >>> The os-hosts OS API extension [1] showed up before I was working on the >>> project and I see that only the VMware and XenAPI drivers implement it, >>> but was wondering why the libvirt driver doesn't - either no one wants >>> it, or there is some technical reason behind not implementing it for >>> that driver? >>> > > If I remember correctly maintenance mode is a special thing in Xen. Maintenance mode is pretty heavily used with VMware vCenter. When an environment supports "universal" live migration of all VMs, it makes sense to migrate all VMs running on a physical machine off of that machine before bringing it down for maintenance, such as upgrading the hardware. Provides some classes of end-users with a more 24x7x365 experience. >>> [1] >>> >>> http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-hosts-v2_updateHost_v2__tenant_id__os-hosts__host_name__ext-os-hosts.html >>> >>> >> >> By the way, am I missing something when I think that this extension is >> already covered if you're: >> >> 1. Looking to get the node out of the scheduling loop, you can just disable >> it with os-services/disable? >> >> 2. Looking to evacuate instances off a failed host (or one that's in >> "maintenance mode"), just use the evacuate server action. > > I don't think your missing anything. > >> >> >> -- >> >> Thanks, >> >> Matt Riedemann >> >> -bruce ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
On Thu, Feb 20, 2014 at 9:38 AM, Matt Riedemann wrote: > > > On 2/19/2014 4:05 PM, Matt Riedemann wrote: >> >> The os-hosts OS API extension [1] showed up before I was working on the >> project and I see that only the VMware and XenAPI drivers implement it, >> but was wondering why the libvirt driver doesn't - either no one wants >> it, or there is some technical reason behind not implementing it for >> that driver? >> If I remember correctly maintenance mode is a special thing in Xen. >> [1] >> >> http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-hosts-v2_updateHost_v2__tenant_id__os-hosts__host_name__ext-os-hosts.html >> >> > > By the way, am I missing something when I think that this extension is > already covered if you're: > > 1. Looking to get the node out of the scheduling loop, you can just disable > it with os-services/disable? > > 2. Looking to evacuate instances off a failed host (or one that's in > "maintenance mode"), just use the evacuate server action. I don't think your missing anything. > > > -- > > Thanks, > > Matt Riedemann > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][libvirt] Is there anything blocking the libvirt driver from implementing the host_maintenance_mode API?
On 2/19/2014 4:05 PM, Matt Riedemann wrote: The os-hosts OS API extension [1] showed up before I was working on the project and I see that only the VMware and XenAPI drivers implement it, but was wondering why the libvirt driver doesn't - either no one wants it, or there is some technical reason behind not implementing it for that driver? [1] http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-hosts-v2_updateHost_v2__tenant_id__os-hosts__host_name__ext-os-hosts.html By the way, am I missing something when I think that this extension is already covered if you're: 1. Looking to get the node out of the scheduling loop, you can just disable it with os-services/disable? 2. Looking to evacuate instances off a failed host (or one that's in "maintenance mode"), just use the evacuate server action. -- Thanks, Matt Riedemann ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
