Open Stack

On 07/24/2012 09:52 AM, 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?
> 

The idea of keeping a minimum number of VMs running based upon VM load
is called auto-scaling.  We have added auto-scaling to our v5 release
(which is targeted for July 30th).

As far as puppet/chef integration goes, CloudFormation integrates well
with both.

For chef read:
http://www.full360.com/blogs/integrating-aws-cloudformation-and-chef

For puppet read:
https://s3.amazonaws.com/cloudformation-examples/IntegratingAWSCloudFormationWithPuppet.pdf

Note while these links talk about "AWS CloudFormation", Heat is
essentially an AWS CloudFormation implementation for OpenStack.

If you want to get started and give heat a try on Fedora 17+ or Ubuntu
Precise, our getting started guides are in our wiki:

https://github.com/heat-api/heat/wiki

Let me know if you have follow-up questions.

Regards
-steve

> Best
> 
> Alessandro
> 
> Il giorno 24/lug/2012, alle ore 14:34, Jay Pipes ha scritto:
> 
>> On 07/24/2012 04:29 AM, Alessandro Tagliapietra wrote:
>>> Hi guys,
>>>
>>> i've 2 missing pieces in my HA openstack install. Actually all openstack
>>> services are managed by pacemaker and i can succesfully start/stop vm
>>> etc. when the cloud controller is down (i've only 2 servers atm).
>>>
>>> 1 - how can i make a VM HA? Actually live-migration works fine, but if a
>>> host goes down, how can i restart the vm on the other host? Should i
>>> edit the 'host' column in the db and issue the restart of the vm? Any
>>> other way?
>>
>> Check out that HEAT API:
>>
>> https://github.com/heat-api/heat/wiki/
>>
>>> 2 - i've the servers hosted at Hetzner, for floating ip we've bought
>>> failover ip which are assigned to each host and can be changed via the
>>> api. So i have to make sure that if vm is on host1, floating ip
>>> associated to the vm is routed to host1.  My idea was to run a job that
>>> checks the floating ip already associated to any vm, then queries the vm
>>> info, checks on which host it's running and if it's different from the
>>> other check, calls the hetzner api to switch the ip to the other server.
>>> Any other idea?
>>
>> See above :)
>>
>> Best,
>> -jay
>>
>>> Thanks in advance
>>>
>>> Best Regards
>>>
>>> -- 
>>> Alessandro Tagliapietra | VISup srl
>>> piazza 4 novembre 7
>>> 20124 Milano
>>>
>>> http://www.visup.it
>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>