[Openstack-operators] Graceful VM shutdown

Jonathan Proulx jon at jonproulx.com
Thu May 16 18:11:34 UTC 2013


I don't know a standard mechanism, but I think it would be nice to have one.

I'd start by setting server metadata, though obviously that requires
running the metadata service and an agent inside the running image that
polls
for what ever key is set (something like "nodeshutown=<Null | timestamp>"
perhaps )

Just a thought,
-Jon


On Thu, May 16, 2013 at 2:02 PM, Tim Bell <Tim.Bell at cern.ch> wrote:

> ** **
>
> I am interested to see how other service providers handle the cases where
> there is a need to reboot a hypervisor but it is planned (such as a reboot
> after OS patching).****
>
> ** **
>
> We do not want to do live or block migration for these cases as there is
> no shared storage and block migration can be a bit unreliable at times.***
> *
>
> ** **
>
> In my ideal case, we would be able to warn the VMs in some way so they can
> do a reasonable job of shutting down. In some cases, our users would like
> many minutes of notice to complete their current transaction.****
>
> ** **
>
> Does anyone know of a standard mechanism for hypervisor communicating to
> the guest to warn of an impending shutdown ?****
>
> ** **
>
> Tim****
>
> ** **
>
> _______________________________________________
> 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/20130516/ca725927/attachment.html>


More information about the OpenStack-operators mailing list