Openstack-ha Deployment Scenarios

Source: Internet
Author: User
Tags node server

Build OpenStack High Availability (Ha,high availability)

first, the database MySQL high reliability:

clusters are not highly reliable,A common approach to building high-reliability MySQL is active-passive master mode : Using DRBDto achieve the disaster tolerance of the main standby machine, heartbeat orCorosyncdo heartbeat monitoring, service switching, or even failover,pacemaker to achieve service (resource) switching and control, or similar mechanisms. The main use of pacemaker to achieve the MySQL active-passive high-availability cluster . One important technique is DRBD: (Distributed replication block device), or distributed replication block devices, which is often used in place of shared disks. It works by: on a host on the specified disk device write request, the data sent to a host of kernel, and then through a module in kernel, the same data to the B host of kernel, and then the B host to write its own designated disk device, Thus the synchronization of the two host data is realized, and the write operation is highly available. DRBD is generally a master one from, and all the read and write operations, Mount can only be performed on the primary node server, but between the master-slave DRBD server can be exchanged. herehave a Introduction to DRBD .


hafornovadb-openstack describes the high reliability of OpenStack through pacemaker by using only shared disks and not using DRBD. novazookeeperheartbeatThis paper describes the use of zookeeper for heartbeat detection. MySQL HA with Pacemakerdescribes the use of pacemaker to provide highly reliable services, which is also a common solution. GaleraIt is an open source project for MYSQL/INNODB Synchronous multi-master cluster, which provides many advantages (such as synchronous replication, read and write to any node, automatic member control, automatic node join, small delay, etc.), can be referenced.

the working modes of pacemaker and DRBD and MySQL can be consulted as follows:


650) this.width=650; "class=" Fit-image "height=" 375 "alt=" pacemaker.jpg "src=" http://www.linuxidc.com/upload/2012_ 07/120701061229801.jpg "width=" 498 "style=" border:0px;text-align:center; "/>


Other scenarios, according to Mysqlperformance, are the availability of several high-availability solutions for MySQL as follows:

650) this.width=650; "src=" Http://www.linuxidc.com/upload/2012_07/120701061229802.png "style=" border:0px; "/>


Ii. Building High-availability OpenStack(high-availabilityOpenStack)

In general, high availability is the creation of redundant backups, common strategies are:

    • Cluster working mode . Multi-machine interoperability, such that the mode is to backup each instance multiple copies, no central node, such as the distributed object Storage System Swift, nova-network multi-host mode .

    • Autonomous mode . Sometimes, solving a single point of failure (SPoF) can simply use each node to work autonomously, through the master-slave relationship to reduce the failure of the main control node, such as NOVA-API only responsible for their own node.

    • Primary and Standby mode . The common mode is active-passive cluster, active-passive, passive node in monitoring and backup mode, timely switch when failure, such as MySQL high-availability cluster, nova-use pacemaker and heartbeat to achieve.

    • Dual Master mode . This mode of mutual assistance, RABBITMQ is the active-active cluster high availability, the nodes in the cluster can be replicated in the queue. Architecturally, so you don't have to worry that the passive node won't start or the delay is too big?

In summary, the deployment and application of OpenStack is constantly being tried and developed for OpenStack optimization and improvement. Need to practice tuning . Practice is very important, good design and ideas need to be proven in practice.


Each of the services of OpenStack is described above , and I am purely a catalyst. Hope to practice communication, but also hope that the time of the friends can be some of the deployment of some scenarios to add to onestack/hastack. For a discussion and description of OpenStack High Availability , you can take a look at the following areas:

http://docs.openstack.org/

http://wiki.openstack.org




This article is from the "OpenStack Private Cloud" blog, declined to reprint!

Openstack-ha Deployment Scenarios

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.