On 06/24/2014 02:53 PM, Steve Gordon wrote:
----- Original Message -----
From: "Rick Jones" <rick.jon...@hp.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
On 06/24/2014 02:38 PM, Joe Gordon wrote:
I agree nova shouldn't take any actions. But I don't think leaving an
instance as 'active' is right either. I was thinking move instance to
error state (maybe an unknown state would be more accurate) and let the
user deal with it, versus just letting the user deal with everything.
Since nova knows something *may* be wrong shouldn't we convey that to
the user (I'm not 100% sure we should myself).
I suspect the user's first action will be to call Support asking "Hey,
why is my perfectly usable instance showing-up in the ERROR|UNKNOWN state?"
rick jones
The existing alternative would be having the user calling to ask why
their non-responsive instance is showing as RUNNING so you are kind
of damned if you do, damned if you don't.
There will be a call for a non-responsive instance regardless what it
shows. However, responsive instance not showing ERROR or UNKNOWN will
not generate a call. So, all in all I think you will get fewer calls if
you don't mark the "not known to be non-responsive" instance as ERROR or
UNKNOWN.
rick
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
