[Openstack-operators] Putting a hypervisor into maintenance / how to get a list of all instance IDs on a host

Madhu sudhan madhuchary80 at gmail.com
Fri Feb 14 11:00:31 UTC 2014


Use the below command
nova hypervisor-server id
On 14 Feb 2014 16:14, "Tim Bell" <Tim.Bell at cern.ch> wrote:

>  Robert,
>
>
>
> How about sharing the script if you can get it to a generic state ? This
> would seem to be an activity that many operators would like to be able to
> do.
>
>
>
> Tim
>
>
>
> *From:* Joe Topjian [mailto:joe at topjian.net]
> *Sent:* 14 February 2014 09:13
> *To:* Robert van Leeuwen
> *Cc:* openstack-operators at lists.openstack.org
> *Subject:* Re: [Openstack-operators] Putting a hypervisor into
> maintenance / how to get a list of all instance IDs on a host
>
>
>
> Hello,
>
>
>
>   > nova-manage (and I believe somewhere in the nova command as well?)
> can disable a service. This will
>
> > prevent new instances from spawning but still allow them to be migrated
> to another host.
>
> Yes this is what I use in my script.
>
>
>
> I think this is the best way to go about maintenance.
>
>
>
>    > And there's also the "nova evacuate" command, but I've never used
> it, so I'm not entirely sure how it works
>
> > or when to use it:
>
> From what I have read from the docs this is used when you have a failed
> hypervisor and want to spawn the instances somewhere else.
>
>
>
> Indeed, but it's curious that there is an optional "shared storage" flag.
> IMO, shared storage should be enabled by default and optionally off.
> Without the shared storage flag, the best that can be done is launching new
> instances of a specific image on another node, which is perhaps worse than
> any type of evacuation.
>
>
>
> I need to try this command out in a sandbox to learn more about it.
>
>
>
>    I was just wandering what people do when they want to put a node into
> maintenance.
> We want to live-migrate everything to another host and I was wondering if
> people already build scripts for this.
>
>
>
> It sounds like you're doing the right thing: disable the service, look up
> the instances, loop and migrate them to other server(s).
>
>
>
>
>
> Cheers,
> Robert van Leeuwen
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140214/36b77be5/attachment-0001.html>


More information about the OpenStack-operators mailing list