Funny you bring that up today;
I spent the day working on that. I've implemented Gluster FS on my openstack running installation and written a script along that.
Here is the implementation

node1- 1 instance running
the node 1 crashes (could be anything atm)
the script detect the node is gone (to be defined : heartbeat, monitoring, etc...) and relaunch the instance in the specified node.

I've tested it and successfully works. Just need to write the final touches
Regards

Razique Mahroua


Le 10 nov. 2011 à 17:15, Viacheslav Biriukov a écrit :

Hm....
If we planning vm hosting we work on the other level. So if hw node fails we need fast automatic migration to other node.

2011/11/10 Soren Hansen <[email protected]>
2011/11/10 Viacheslav Biriukov <[email protected]>:
> Hi all.
> What are the best practices for HA of the hardware compute-node, and virtual
> machines.
> After googling I found matahari, pacemaker-cloud, but nothing about
> build-in fiches  openstack.
> 1) How do you create such environments?
> 2) Does it is right way to use pacemaker-cloud with openstack? Is it stable?

I'd avoid depending on anything like that altogether. Try to design
your application so that it doesn't depend on any one instance being
up. It'll work out better in the long run.

--
Soren Hansen        | http://linux2go.dk/
Ubuntu Developer    | http://www.ubuntu.com/
OpenStack Developer | http://www.openstack.org/



--
Viacheslav Biriukov
BR

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to