openstack/openstack-ansible
Code Issues Proposed changes

Consolidating infrastructure playbook doc

Browse Source 
Deleted the the install-infrastructure-* files
Moved content into install-infrastructure.rst

Change-Id: I215ccb937ab181b8066567e5b15b8568db56a7d3
This commit is contained in:
Karin Levenstein 2016-01-15 14:03:25 -06:00 committed by Jesse Pretorius
parent b3d6ff2d14
commit 838d172f4d
3 changed files with 69 additions and 96 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
doc/source/install-guide/install-infrastructure-run.rst
View File

@ -1,30 +0,0 @@
`Home <index.html>`_ OpenStack-Ansible Installation Guide
Running the infrastructure playbook
-----------------------------------
.. seealso:: Before continuing, the configuration files may be validated using the guidance in "`Checking the integrity of your configuration files`_".
.. _Checking the integrity of your configuration files: ../install-guide/configure-configurationintegrity.html
#. Change to the ``/opt/openstack-ansible/playbooks`` directory.
#. Run the infrastructure setup playbook, which runs a series of
sub-playbooks:
.. code-block:: shell-session
# openstack-ansible setup-infrastructure.yml
Confirm satisfactory completion with zero items unreachable or
failed:
.. code-block:: shell-session
PLAY RECAP ********************************************************************
...
deployment_host : ok=27 changed=0 unreachable=0 failed=0
--------------
.. include:: navigation.txt

60
doc/source/install-guide/install-infrastructure-verify.rst
View File

@ -1,60 +0,0 @@
`Home <index.html>`_ OpenStack-Ansible Installation Guide
Verifying infrastructure operation
----------------------------------
Verify the database cluster and Kibana web interface operation.
**Procedure 7.1. Verifying the database cluster**
#. Determine the Galera container name:
.. code-block:: shell-session
# lxc-ls | grep galera
infra1_galera_container-4ed0d84a
#. Access the Galera container:
.. code-block:: shell-session
# lxc-attach -n infra1_galera_container-4ed0d84a
#. Run the MariaDB client, show cluster status, and exit the client:
.. code-block:: shell-session
# mysql -u root -p
MariaDB> show status like 'wsrep_cluster%';
+--------------------------+--------------------------------------+
| Variable_name | Value |
+--------------------------+--------------------------------------+
| wsrep_cluster_conf_id | 3 |
| wsrep_cluster_size | 3 |
| wsrep_cluster_state_uuid | bbe3f0f6-3a88-11e4-bd8f-f7c9e138dd07 |
| wsrep_cluster_status | Primary |
+--------------------------+--------------------------------------+
MariaDB> exit
The ``wsrep_cluster_size`` field should indicate the number of nodes
in the cluster and the ``wsrep_cluster_status`` field should indicate
primary.
 
**Procedure 7.2. Verifying the Kibana web interface**
#. With a web browser, access the Kibana web interface using the
external load balancer IP address defined by the
``external_lb_vip_address`` option in the
``/etc/openstack_deploy/openstack_user_config.yml`` file. The Kibana
web interface uses HTTPS on port 8443.
#. Authenticate using the username ``kibana`` and password defined by
the ``kibana_password`` option in the
``/etc/openstack_deploy/user_variables.yml`` file.
--------------
.. include:: navigation.txt

75
doc/source/install-guide/install-infrastructure.rst
View File

@ -3,12 +3,6 @@
Chapter 6. Infrastructure playbooks
-----------------------------------
.. toctree::
install-infrastructure-run.rst
install-infrastructure-verify.rst
**Figure 6.1. Installation workflow**
.. image:: figures/workflow-infraplaybooks.png
@ -28,6 +22,75 @@ services and performs the following operations:
- Configure Rsyslog
Running the infrastructure playbook
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. seealso::
Before continuing, the configuration files may be validated using the
guidance in "`Checking the integrity of your configuration files`_".
.. _Checking the integrity of your configuration files: ../install-guide/configure-configurationintegrity.html
#. Change to the ``/opt/openstack-ansible/playbooks`` directory.
#. Run the infrastructure setup playbook, which runs a series of
sub-playbooks:
.. code-block:: shell-session
# openstack-ansible setup-infrastructure.yml
Confirm satisfactory completion with zero items unreachable or
failed:
.. code-block:: shell-session
PLAY RECAP ********************************************************************
...
deployment_host : ok=27 changed=0 unreachable=0 failed=0
Verify the database cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~
#. Change to the ``/opt/openstack-ansible/playbooks`` directory.
#. Execute the following to show the current cluster state:
.. code-block:: shell-session
# ansible galera_container -m shell -a "mysql \
-h localhost -e 'show status like \"%wsrep_cluster_%\";'"
The results should look something like:
.. code-block:: shell-session
node3_galera_container-3ea2cbd3 | success | rc=0 >>
Variable_name Value
wsrep_cluster_conf_id 17
wsrep_cluster_size 3
wsrep_cluster_state_uuid 338b06b0-2948-11e4-9d06-bef42f6c52f1
wsrep_cluster_status Primary
node2_galera_container-49a47d25 | success | rc=0 >>
Variable_name Value
wsrep_cluster_conf_id 17
wsrep_cluster_size 3
wsrep_cluster_state_uuid 338b06b0-2948-11e4-9d06-bef42f6c52f1
wsrep_cluster_status Primary
node4_galera_container-76275635 | success | rc=0 >>
Variable_name Value
wsrep_cluster_conf_id 17
wsrep_cluster_size 3
wsrep_cluster_state_uuid 338b06b0-2948-11e4-9d06-bef42f6c52f1
wsrep_cluster_status Primary
The ``wsrep_cluster_size`` field should indicate the number of nodes
in the cluster and the ``wsrep_cluster_status`` field should indicate
primary.
--------------
.. include:: navigation.txt