Greetings Programs, We to have been toying with a similar idea in our lab. We are using the same model as Oleg, for existing clouds. The current OpenStack paradigm is a bit different. Having not read all his info yet, I hope they include service resources for the openstacks bits configured into his CIB.
We have been toying with the idea, of doing linux-ha clusters under the openstack services for service availability across the cloud. p On Thu, May 26, 2011 at 03:11:34PM +0200, Diego Parrilla Santamaría wrote: > Hi Oleg, > thank you very much for your post, it's really didactic. We are taking a > different approach for HA at storage level, but I have worked formerly > with DRBD and I think it's a very good choice. > I'm curious about how you have deployed nova-volume nodes in your > architecture. You don't specify if the two nodes of the DRBD cluster run > one or two instances of nova-volume. If you run one instance probably you > have implemented some kind of fault-tolerant active-passive service if the > nova-volume process fails in the active node, but I would like to know if > you can run an active-active two nova-volume instances on two different > physical nodes on top of the DRBD shared resource. > Regards > Diego� > -- > Diego Parrilla > CEO > [1]www.stackops.com |� [2][email protected] | +34 649 94 43 29 | > skype:diegoparrilla > > On Thu, May 26, 2011 at 1:29 PM, Oleg Gelbukh <[3][email protected]> > wrote: > > Hi, > We were researching Openstack for our private cloud, and want to share > experience and get tips from community as we go on.� > We have settled on DRBD as shared storage platform for our installation. > LVM is used over the drbd device to mange logical volumes. OCFS2 file > system is created on one of volumes, mounted and set up as > image_path�and�instance_path in the nova.conf, other space is reserved > for storage volumes (managed by nova-volume).� > As a result, we have shared storage suitable for features such as live > migration and snapshots. We also have some level of fault-tolerance, > with DRBD I/O error handling, which automatically redirects I/O requests > to peer node over network in case of primary node failure. We created > [4]script for bootstrapping lost VMs in two crash scenarios: > * dom0 host restart/domU failure: restore VMs on the same host > * dom0 host failure: restore VMs on peer node > We are considering such pair of servers with shared storage as a basic > block for the cloud structure. > For whom it may interest, the details of DRBD installation are [5]here. > I'll be glad to answer any questions and highly appreciate feedback on > this. > Oleg S. Gelbukh, > Mirantis Inc. > [6]www.mirantis.com > _______________________________________________ > Mailing list: [7]https://launchpad.net/~openstack > Post to � � : [8][email protected] > Unsubscribe : [9]https://launchpad.net/~openstack > More help � : [10]https://help.launchpad.net/ListHelp > > References > > Visible links > 1. http://www.stackops.com/ > 2. mailto:[email protected] > 3. mailto:[email protected] > 4. > https://github.com/Mirantis/openstack-utils/blob/master/recovery_instance_by_id.py > 5. > http://mirantis.blogspot.com/2011/05/shared-storage-for-openstack-based-on.html > 6. http://www.mirantis.com/ > 7. https://launchpad.net/~openstack > 8. mailto:[email protected] > 9. https://launchpad.net/~openstack > 10. 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 _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
