The workflow is on top of the pages, this is an exception. It
should fix it.
Change-Id: I40c9981f2c6b26fe5c2c61cfc45330cd476f2385
(cherry picked from commit 9be2fe792c
)
4.0 KiB
Run playbooks
The installation process requires running three main playbooks:
- The
setup-hosts.yml
Ansible foundation playbook prepares the target hosts for infrastructure and OpenStack services, builds and restarts containers on target hosts, and installs common components into containers on target hosts. - The
setup-infrastructure.yml
Ansible infrastructure playbook installs infrastructure services: Memcached, the repository server, Galera, RabbitMQ, and rsyslog. - The
setup-openstack.yml
OpenStack playbook installs OpenStack services, including Identity (keystone), Image (glance), Block Storage (cinder), Compute (nova), Networking (neutron), etc.
Checking the integrity of the configuration files
Before running any playbook, check the integrity of the configuration files.
Ensure that all the files edited in the
/etc/openstack_deploy
directory are Ansible YAML compliant.Check the integrity of your YAML files.
Note
To check your YAML syntax online, you can use the YAML Lint program.
Change to the
/opt/openstack-ansible/playbooks
directory, and run the following command:# openstack-ansible setup-infrastructure.yml --syntax-check
Recheck that all indentation is correct. This is important because the syntax of the configuration files can be correct while not being meaningful for OpenStack-Ansible.
Run the playbooks to install OpenStack
Change to the
/opt/openstack-ansible/playbooks
directory.Run the host setup playbook:
# openstack-ansible setup-hosts.yml
Confirm satisfactory completion with zero items unreachable or failed:
PLAY RECAP ******************************************************************** ... deployment_host : ok=18 changed=11 unreachable=0 failed=0
Run the infrastructure setup playbook:
# openstack-ansible setup-infrastructure.yml
Confirm satisfactory completion with zero items unreachable or failed:
PLAY RECAP ******************************************************************** ... deployment_host : ok=27 changed=0 unreachable=0 failed=0
Run the following command to verify the database cluster:
# ansible galera_container -m shell \ -a "mysql -h localhost -e 'show status like \"%wsrep_cluster_%\";'"
Example output:
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 indicates the number of nodes in the cluster and thewsrep_cluster_status
field indicates primary.Run the OpenStack setup playbook:
# openstack-ansible setup-openstack.yml
Confirm satisfactory completion with zero items unreachable or failed.