openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #15067
Re: VM High Availability and Floating IP
On 07/24/2012 10:08 AM, Alessandro Tagliapietra wrote:
> But i don't see any part (except the future plans) talking about HA at instance level, that seems more to an application level
>
Currently heat's healthchecking is application only, but we do intend to
improve instance healthchecking in v6. We are currently in our v5
development which concludes on July 30th. We have 4-5 week development
windows. I'll make certain vm healthchecking is solid for v6 around
August. However, we may be able to fit into v5 - I'll have to check
with the main author of the HA feature (Angus Salkeld).
The HA feature HOWTO is described a bit here:
https://github.com/heat-api/heat/wiki/Using-HA
An example HA application template is here:
https://github.com/heat-api/heat/blob/master/templates/WordPress_Single_Instance_With_HA.template
This template launches a wordpress cloud application. If httpd or mysql
fail, they are restarted. If they fail 3 times in 5 minutes, the entire
VM is restarted (this is called escalation) under the assumption that
the VM container is defective in some way.
Regards
-steve
> Il giorno 24/lug/2012, alle ore 18:56, Jay Pipes ha scritto:
>
>> On 07/24/2012 12:52 PM, Alessandro Tagliapietra wrote:
>>> Thank you Jay, never read about that.
>>> Seems something like scalr/chef? WHich handles application and keeps a minimum number of vm running?
>>
>> Yeah, kinda.. just one more way of doing things... :)
>> -jay
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References