Open Stack

Hi,

I'm doing some work on heat at the moment, and on my list is 
implementation of the HealthCheckType parameter for autoscaling groups, 
as well as the automatic 'replace unhealthy or missing instances' 
behavior that you get with AWS autoscaling groups.

Once I started looking at it, I realized that 'unhealthy or missing' 
actually seems a bit hard to quantify based on things like CPU usage.

Does anyone have any suggestions of things (eg, virsh state 'crashed' or 
something) that I could use for this?  Also, how to detect that an 
instance has gone missing (eg, hypervisor has shutdown or something)?

Cheers,
-- 
Stephen Gran
Senior Systems Integrator - theguardian.com
Please consider the environment before printing this email.
------------------------------------------------------------------
Visit theguardian.com   

On your mobile, download the Guardian iPhone app theguardian.com/iphone and our iPad edition theguardian.com/iPad   
Save up to 33% by subscribing to the Guardian and Observer - choose the papers you want and get full digital access.
Visit subscribe.theguardian.com

This e-mail and all attachments are confidential and may also
be privileged. If you are not the named recipient, please notify
the sender and delete the e-mail and all attachments immediately.
Do not disclose the contents to another person. You may not use
the information for any purpose, or store, or copy, it in any way.
 
Guardian News & Media Limited is not liable for any computer
viruses or other material transmitted with or as part of this
e-mail. You should employ virus checking software.
 
Guardian News & Media Limited
 
A member of Guardian Media Group plc
Registered Office
PO Box 68164
Kings Place
90 York Way
London
N1P 2AP
 
Registered in England Number 908396

--------------------------------------------------------------------------