Open Stack

Yes, that's a valid scenario.

I am just wondering the VM status from nova api is not "fully" reliable, if some 3rd party tools reply on this to manage VM lifecycle/HA/scaling, they will run into troubles...


Kimi Zhang
+86 186 0800 8182

From: ext matt [mailto:matt at nycresistor.com]
Sent: Wednesday, August 07, 2013 3:19 PM
To: Zhang, Kimi (NSN - CN/Cheng Du)
Cc: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] VM status keeps ACTIVE after its nova-compute host is powered off

imagine a scenario in which rabbitmq were to fail to poll the nova-compute service and put the system into an inactive state... yet, the instances were still up and operating as expected.
i am not sure there is a way for openstack to ensure down or up in the scenario in which message bus communications are severed.  so i don't see a benefit either assuming down or coasting with previous values until otherwise updated.
-matt

On Wed, Aug 7, 2013 at 12:11 AM, Zhang, Kimi (NSN - CN/Cheng Du) <kimi.zhang at nsn.com<mailto:kimi.zhang at nsn.com>> wrote:
Hi,

Currently if a nova-compute host is down not gracefully, e.g. a power cut.  Its hosting VMs still have ACTIVE status in Database.

Even though nova knows the compute node is down, it does nothing to VMs status.

Should Nova be improved to update those VMs status to something else(e.g. ERROR) other than confusing "ACTIVE" ??




Kimi Zhang
+86 186 0800 8182<tel:%2B86%20186%200800%208182>



_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto: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/20130807/11fc36b0/attachment.html>