Shulou(Shulou.com)05/31 Report--

This article mainly introduces how to use OpenStack Database to achieve replication and aggregation, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let Xiaobian take you to understand.

As applications migrate to the cloud, the complexity of manipulating databases becomes apparent in this new environment. Even if you do this in a controlled luxury data center with dedicated hardware, it is difficult to operate the database infrastructure. The cloud introduces performance variability and virtualization overhead, and provides a lower level of control for end users on the underlying hardware. In the public cloud, the reliability of a single virtual machine instance is considered to be much lower than that of dedicated machines in the data center. When operating a large number of servers, failures are observed more frequently. All this makes it more challenging to operate databases in the cloud.

Database-as-a-Service simplifies operations on databases in the cloud by reducing the administrative burden on administrators when operating the infrastructure. By tightly integrating into the underlying infrastructure and automating many common operations, DBaaS greatly simplifies many of these activities. However, failure (failures) can lead to service disruption. Therefore, it is critical that the DBaaS platform interpret and handle failures in order to make them transparent to end users

Trove implements these aspects.

First, trove is closely integrated with the OpenSatck infrastructure and tightly integrated with Nova,Neutron,Swift,Cinder and keystone. It automates a large number of configurations and settings required to start a new server, similar to what other tools such as Puppet,Chef and Ansible do. It also allows webmasters to establish standard configurations and use those configurations to start the server reliably.

The areas where this configuration supports are particularly important are replication and aggregation. Without Trove, users may have to manually configure these features and manage failures and failover on their own. Trove automates these functions, and they are being implemented in phases.

Replication, which was originally implemented in Trove, uses mysql's built-in replication feature for MysqL data storage. Subsequent phases extend this functionality to include aggregating and replicating all Trove-supported data stores. In the first version of this feature, users can create a separate instance of MySQL, and then create a dependent instance. The act of creating a slave creates a new replication instance that is equivalent to the original instance

The following command shows how the user will do this. The following Trove instance runs a mysql5.5:

$trove list+--+ | ID | | Name | Datastore | Datastore Version | Status | Flavor ID | Size | +-- +-+ | d2bd91ef-3d7c-43ae-97a9-f0726c91d322 | M1 | mysql | 5.5 | ACTIVE | 7 | 2 +-+- -+

You will now create a second (slave) instance that references the master provided above, as follows.

$trove create s17-- size 2-- slave_of d2bd91ef3d7cMuth43aeMuth97a9Muvef0726c91d322Mutual Mutual + | Property | Value | +- -+-- + | created | 2014-06-13T14:33:27 | | datastore | mysql | | datastore_version | 5.5 | flavor | | 7 | | id | 9ffc7b3a-9205-412a-9cd2-521f95755c43 | | name | S1 | | slaveOf | d2bd91ef-3d7c-43ae-97a9-f0726c91d322 | | status | BUILD | | updated | 2014-06-| 13T14:33:27 | | volume | 2 | +-+-+

Users can now view the status pair (replicated pair) of the replication as shown below.

$trove show 9ffc7b3a-9205-412a-9cd2-521f95755c43copyright copyright plus | Property | Value | +- -+-+ | created | 2014-06-13T14:33:27 | | datastore | mysql | | datastore_version | | | flavor | 7 | | id | 9ffc7b3a-9205-412a-9cd2-521f95755c43 | | name | S1 | | slaveOf | d2bd91ef-3d7c-43ae-97a9-f0726c91d322 | | status | | | ACTIVE | | updated | 2014-06-13T14:33:27 | | volume | 2 | +-- | -+ $trove show d2bd91efmuri 3d7c Muay 43ae97a9Mub f0726c91d322 Mustang Murray + | Property | Value | | +-+ | created | 2014-06-13T14:33:27 | | datastore | mysql | | | datastore_version | 5.5 | flavor | 7 | | id | d2bd91ef-3d7c-43ae-97a9-f0726c91d322 | | name | S1 | | | slaves | 9ffc7b3a-9205-412a-9cd2-521f95755c43 | | status | ACTIVE | | updated | 2014-06-13T14:33:27 | | volume | 2 | +-| -+

Disconnect a slave from master, and the user will "detach":

$trove detach_replication

Now you have learned the basic structure of Trove's replication feature. In the next article, we will describe the implementation details of the client and task manager.

Thank you for reading this article carefully. I hope the article "how to use OpenStack Database to achieve replication and aggregation" shared by the editor will be helpful to everyone. At the same time, I also hope that you will support and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.