openstack/openstack-ansible
Code Issues Proposed changes

docs: fix small mistake with MariaDB and RabbitMQ

Browse Source 
Change-Id: Iccb988457e964d07e0b2b4e91277e96e1359736f
This commit is contained in:
Ivan Anfimov
2025-05-14 11:57:15 +00:00
parent 1e22194dc8
commit d119fbae40
4 changed files with 5 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/admin/backup-restore.rst
View File

@@ -25,7 +25,7 @@ directory to your cloud environment.
Database backups and recovery
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MySQL data is available on the infrastructure nodes.
MariaDB data is available on the infrastructure nodes.
You can recover databases, and rebuild the Galera cluster.
For more information, see
:ref:`galera-cluster-recovery`.

7
doc/source/admin/maintenance-tasks/galera.rst
View File

@@ -5,7 +5,7 @@ Routine maintenance includes gracefully adding or removing nodes from
the cluster without impacting operation and also starting a cluster
after gracefully shutting down all nodes.
MySQL instances are restarted when creating a cluster, when adding a
MariaDB instances are restarted when creating a cluster, when adding a
node, when the service is not running, or when changes are made to the
``/etc/mysql/my.cnf`` configuration file.
@@ -206,7 +206,6 @@ continue to process SQL requests.
wsrep_cluster_state_uuid 338b06b0-2948-11e4-9d06-bef42f6c52f1
wsrep_cluster_status Primary
In this example, node 3 has failed.
#. Restart MariaDB on the failed node and verify that it rejoins the
@@ -336,7 +335,6 @@ the cluster have failed:
seqno: -1
cert_index:
All the nodes have failed if ``mariadbd`` is not running on any of the
nodes and all of the nodes contain a ``seqno`` value of -1.
@@ -376,7 +374,6 @@ Recovering from certain failures require rebuilding one or more containers.
# openstack-ansible oopenstack.osa.containers_lxc_create -l node3 \
-l node3_galera_container-3ea2cbd3
The playbook restarts all other containers on the node.
#. Run the infrastructure playbook to configure the container
@@ -387,7 +384,6 @@ Recovering from certain failures require rebuilding one or more containers.
# openstack-ansible openstack.osa.setup_infrastructure \
--limit node3_galera_container-3ea2cbd3
.. warning::
The new container runs a single-node Galera cluster, which is a dangerous
@@ -459,5 +455,4 @@ Recovering from certain failures require rebuilding one or more containers.
wsrep_cluster_state_uuid 338b06b0-2948-11e4-9d06-bef42f6c52f1
wsrep_cluster_status Primary
#. Enable the previously failed node on the load balancer.

2
doc/source/admin/upgrades/distribution-upgrades.rst
View File

@@ -255,7 +255,7 @@ Deploying Infrastructure Hosts
openstack-ansible openstack.osa.galera_server --limit localhost,reinstalled_host* -e galera_server_bootstrap_node="{{ groups['galera_all'][-1] }}"
You'll now have mariadb running, and it should be synced with
You'll now have MariaDB running, and it should be synced with
non-primaries.
To check that verify MariaDB cluster status by executing from

4
doc/source/admin/upgrades/major-upgrades.rst
View File

@@ -199,7 +199,7 @@ Upgrade infrastructure
~~~~~~~~~~~~~~~~~~~~~~
We can now go ahead with the upgrade of all the infrastructure components. To
ensure that rabbitmq and mariadb are upgraded, we pass the appropriate flags.
ensure that RabbitMQ and MariaDB are upgraded, we pass the appropriate flags.
.. warning::
@@ -220,7 +220,7 @@ ensure that rabbitmq and mariadb are upgraded, we pass the appropriate flags.
# openstack-ansible openstack.osa.setup_infrastructure -e 'galera_upgrade=true' -e 'rabbitmq_upgrade=true' -e package_state=latest
With this complete, we can now restart the mariadb containers one at a time,
With this complete, we can now restart the MariaDB containers one at a time,
ensuring that each is started, responding, and synchronized with the other
nodes in the cluster before moving on to the next steps. This step allows
the LXC container configuration that you applied earlier to take effect,