openstack/openstack-manuals
Code Issues Proposed changes

Merge "[admin-guide] Fix the rst mark-ups for database service"

Browse Source
This commit is contained in:
Jenkins 2015-12-15 03:59:04 +00:00 committed by Gerrit Code Review
commit a68ac6d95a
1 changed files with 104 additions and 93 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

119
doc/admin-guide-cloud/source/database.rst
View File

@ -21,19 +21,18 @@ levels, and automates complex administrative tasks such as
deployment, configuration, patching, backups, restores, and deployment, configuration, patching, backups, restores, and
monitoring. monitoring.
Create a datastore Create a data store
~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
An administrative user can create datastores for a variety of An administrative user can create data stores for a variety of
databases. databases.
This section assumes you do not yet have a MySQL datastore, and shows This section assumes you do not yet have a MySQL data store, and shows
you how to create a MySQL datastore and populate it with a MySQL 5.5 you how to create a MySQL data store and populate it with a MySQL 5.5
datastore version. data store version.
|
**To create a datastore** **To create a data store**
#. **Create a trove image** #. **Create a trove image**
@ -41,9 +40,9 @@ datastore version.
example, MySQL, MongoDB, Cassandra. example, MySQL, MongoDB, Cassandra.
This image must have the trove guest agent installed, and it must This image must have the trove guest agent installed, and it must
have the :file:`trove-guestagent.conf` file configured to connect to have the ``trove-guestagent.conf`` file configured to connect to
your OpenStack environment. To configure :file:`trove-guestagent.conf`, your OpenStack environment. To configure ``trove-guestagent.conf``,
add the following lines to :file:`trove-guestagent.conf` on the guest add the following lines to ``trove-guestagent.conf`` on the guest
instance you are using to build your image: instance you are using to build your image:
.. code-block:: ini .. code-block:: ini
@ -63,7 +62,9 @@ datastore version.
You need to register your guest image with the Image service. You need to register your guest image with the Image service.
In this example, you use the glance :command:`image-create` In this example, you use the glance :command:`image-create`
command to register a ``mysql-5.5.qcow2`` image:: command to register a ``mysql-5.5.qcow2`` image.
.. code-block:: console
$ glance image-create --name mysql-5.5 --disk-format qcow2 --container-format bare --is-public True < mysql-5.5.qcow2 $ glance image-create --name mysql-5.5 --disk-format qcow2 --container-format bare --is-public True < mysql-5.5.qcow2
+------------------+--------------------------------------+ +------------------+--------------------------------------+
@ -88,9 +89,9 @@ datastore version.
| virtual_size | None | | virtual_size | None |
+------------------+--------------------------------------+ +------------------+--------------------------------------+
#. **Create the datastore** #. **Create the data store**
Create the datastore that will house the new image. To do this, use Create the data store that will house the new image. To do this, use
the :command:`trove-manage` :command:`datastore_update` command. the :command:`trove-manage` :command:`datastore_update` command.
This example uses the following arguments: This example uses the following arguments:
@ -106,10 +107,10 @@ datastore version.
- The configuration file to use. - The configuration file to use.
- :option:`--config-file=/etc/trove/trove.conf` - :option:`--config-file=/etc/trove/trove.conf`
* - name * - name
- Name you want to use for this datastore. - Name you want to use for this data store.
- ``mysql`` - ``mysql``
* - default version * - default version
- You can attach multiple versions/images to a datastore. For - You can attach multiple versions/images to a data store. For
example, you might have a MySQL 5.5 version and a MySQL 5.6 example, you might have a MySQL 5.5 version and a MySQL 5.6
version. You can designate one version as the default, which version. You can designate one version as the default, which
the system uses if a user does not explicitly request a the system uses if a user does not explicitly request a
@ -121,15 +122,17 @@ datastore version.
| |
Example:: Example:
.. code-block:: console
$ trove-manage --config-file=/etc/trove/trove.conf datastore_update mysql "" $ trove-manage --config-file=/etc/trove/trove.conf datastore_update mysql ""
#. **Add a version to the new datastore** #. **Add a version to the new data store**
Now that you have a MySQL datastore, you can add a version to it, Now that you have a MySQL data store, you can add a version to it,
using the trove-manage :command:`datastore_version_update` command. using the :command:`trove-manage` :command:`datastore_version_update`
The version indicates which guest image to use. command. The version indicates which guest image to use.
This example uses the following arguments: This example uses the following arguments:
@ -145,18 +148,18 @@ datastore version.
- The configuration file to use. - The configuration file to use.
- :option:`--config-file=/etc/trove/trove.conf` - :option:`--config-file=/etc/trove/trove.conf`
* - datastore * - data store
- The name of the datastore you just created via - The name of the data store you just created via
trove-manage :command:`datastore_update`. ``trove-manage`` :command:`datastore_update`.
- ``mysql`` - ``mysql``
* - version name * - version name
- The name of the version you are adding to the datastore. - The name of the version you are adding to the data store.
- ``mysql-5.5`` - ``mysql-5.5``
* - datastore manager * - data store manager
- Which datastore manager to use for this version. Typically, - Which data store manager to use for this version. Typically,
the datastore manager is identified by one of the following the data store manager is identified by one of the following
strings, depending on the database: strings, depending on the database:
* mysql * mysql
@ -175,7 +178,7 @@ datastore version.
* - packages * - packages
- If you want to put additional packages on each guest that - If you want to put additional packages on each guest that
you create with this datastore version, you can list the you create with this data store version, you can list the
package names here. package names here.
- ``""`` - ``""``
@ -190,15 +193,17 @@ datastore version.
| |
Example:: Example:
.. code-block:: console
$ trove-manage --config-file=/etc/trove/trove.conf datastore_version_update mysql mysql-5.5 mysql GLANCE_ID "" 1 $ trove-manage --config-file=/etc/trove/trove.conf datastore_version_update mysql mysql-5.5 mysql GLANCE_ID "" 1
**Optional.** Set your new version as the default version. To do **Optional.** Set your new version as the default version. To do
this, use the trove-manage :command:`datastore_update` command again, this, use the :command:`trove-manage` :command:`datastore_update`
this time specifying the version you just created. command again, this time specifying the version you just created.
:: .. code-block:: console
$ trove-manage --config-file=/etc/trove/trove.conf datastore_update mysql mysql-5.5 $ trove-manage --config-file=/etc/trove/trove.conf datastore_update mysql mysql-5.5
@ -206,12 +211,12 @@ datastore version.
.. note:: .. note::
**Applies only to MySQL and Percona datastores** **Applies only to MySQL and Percona data stores**
* If you just created a MySQL or Percona datastore, then you need * If you just created a MySQL or Percona data store, then you need
to load the appropriate validation rules, as described in this to load the appropriate validation rules, as described in this
step. step.
* If you just created a different datastore, skip this step. * If you just created a different data store, skip this step.
**Background.** You can manage database configuration tasks by using **Background.** You can manage database configuration tasks by using
configuration groups. Configuration groups let you set configuration configuration groups. Configuration groups let you set configuration
@ -220,7 +225,7 @@ datastore version.
When you set up a configuration group using the trove When you set up a configuration group using the trove
:command:`configuration-create` command, this command compares the configuration :command:`configuration-create` command, this command compares the configuration
values you are setting against a list of valid configuration values values you are setting against a list of valid configuration values
that are stored in the :file:`validation-rules.json` file. that are stored in the ``validation-rules.json`` file.
.. list-table:: .. list-table::
:header-rows: 1 :header-rows: 1
@ -232,37 +237,41 @@ datastore version.
* - Ubuntu 14.04 * - Ubuntu 14.04
- :file:`/usr/lib/python2.7/dist-packages/trove/templates/DATASTORE_NAME` - :file:`/usr/lib/python2.7/dist-packages/trove/templates/DATASTORE_NAME`
- DATASTORE_NAME is the name of either the MySQL datastore or - DATASTORE_NAME is the name of either the MySQL data store or
the Percona datastore. This is typically either ``mysql`` the Percona data store. This is typically either ``mysql``
or ``percona``. or ``percona``.
* - RHEL 7, CentOS 7, Fedora 20, and Fedora 21 * - RHEL 7, CentOS 7, Fedora 20, and Fedora 21
- :file:`/usr/lib/python2.7/site-packages/trove/templates/DATASTORE_NAME` - :file:`/usr/lib/python2.7/site-packages/trove/templates/DATASTORE_NAME`
- DATASTORE_NAME is the name of either the MySQL datastore or - DATASTORE_NAME is the name of either the MySQL data store or
the Percona datastore. This is typically either ``mysql`` or ``percona``. the Percona data store. This is typically either ``mysql`` or ``percona``.
| |
Therefore, as part of creating a datastore, you need to load the Therefore, as part of creating a data store, you need to load the
:file:`validation-rules.json` file, using the :command:`trove-manage` ``validation-rules.json`` file, using the :command:`trove-manage`
:command:`db_load_datastore_config_parameters` command. This command :command:`db_load_datastore_config_parameters` command. This command
takes the following arguments: takes the following arguments:
* Datastore name * Data store name
* Datastore version * Data store version
* Full path to the :file:`validation-rules.json` file * Full path to the ``validation-rules.json`` file
| |
This example loads the :file:`validation-rules.json` file for a MySQL This example loads the ``validation-rules.json`` file for a MySQL
database on Ubuntu 14.04:: database on Ubuntu 14.04:
.. code-block:: console
$ trove-manage db_load_datastore_config_parameters mysql mysql-5.5 /usr/lib/python2.7/dist-packages/trove/templates/mysql/validation-rules.json $ trove-manage db_load_datastore_config_parameters mysql mysql-5.5 /usr/lib/python2.7/dist-packages/trove/templates/mysql/validation-rules.json
#. **Validate datastore** #. **Validate data store**
To validate your new datastore and version, start by listing the To validate your new data store and version, start by listing the
datastores on your system:: data stores on your system:
.. code-block:: console
$ trove datastore-list $ trove datastore-list
+--------------------------------------+--------------+ +--------------------------------------+--------------+
@ -272,8 +281,10 @@ datastore version.
| e5dc1da3-f080-4589-a4c2-eff7928f969a | mysql | | e5dc1da3-f080-4589-a4c2-eff7928f969a | mysql |
+--------------------------------------+--------------+ +--------------------------------------+--------------+
Take the ID of the MySQL datastore and pass it in with the Take the ID of the MySQL data store and pass it in with the
:command:`datastore-version-list` command:: :command:`datastore-version-list` command:
.. code-block:: console
$ trove datastore-version-list DATASTORE_ID $ trove datastore-version-list DATASTORE_ID
+--------------------------------------+-----------+ +--------------------------------------+-----------+
@ -297,7 +308,7 @@ query router(s) and config server(s).
**Configuration.** By default, the system creates one query router and **Configuration.** By default, the system creates one query router and
one config server per cluster. You can change this by editing one config server per cluster. You can change this by editing
the :file:`/etc/trove/trove.conf` file. These settings are in the the ``/etc/trove/trove.conf`` file. These settings are in the
``mongodb`` section of the file: ``mongodb`` section of the file:
.. list-table:: .. list-table::