Chapter 13. Configuring the overcloud with Ansible

Procedure

1. Use the setfacl command to grant the stack user on the undercloud access to the files in the /var/lib/mistral directory:

   $ sudo setfacl -R -m u:stack:rwx /var/lib/mistral

   This command retains mistral user access to the directory.

Procedure

1. View the log with the less command within the config-download working directory. The following example uses the overcloud working directory:

   $ less /var/lib/mistral/overcloud/ansible.log

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

2. Run the deployment command with the --stack-only option. Include any environment files required for your overcloud:

   $ openstack overcloud deploy \
     --templates \
     -e environment-file1.yaml \
     -e environment-file2.yaml \
     ...
     --stack-only

3. Wait until the provisioning process completes.

4. Enable SSH access from the undercloud to the overcloud for the tripleo-admin user. The config-download process uses the tripleo-admin user to perform the Ansible-based configuration:

   $ openstack overcloud admin authorize

5. Run the deployment command with the --config-download-only option. Include any environment files required for your overcloud:

   $ openstack overcloud deploy \
     --templates \
     -e environment-file1.yaml \
     -e environment-file2.yaml \
     ...
     --config-download-only

6. Wait until the configuration process completes.

Procedure

1. Change to the directory of the Ansible playbook::

   $ cd /var/lib/mistral/overcloud/

2. Run the ansible-playbook-command.sh command to reproduce the deployment:

   $ ./ansible-playbook-command.sh

   You can pass additional Ansible arguments to this script, which are then passed unchanged to the ansible-playbook command. This means that you can use other Ansible features, such as check mode (--check), limiting hosts (--limit), or overriding variables (-e). For example:

   $ ./ansible-playbook-command.sh --limit Controller

3. The working directory contains a playbook called deploy_steps_playbook.yaml, which runs the overcloud configuration. To view this playbook, run the following command:

   $ less deploy_steps_playbook.yaml

   The playbook uses various task files contained in the working directory. Some task files are common to all OpenStack Platform roles and some are specific to certain OpenStack Platform roles and servers.

4. The working directory also contains sub-directories that correspond to each role that you define in your overcloud roles_data file. For example:

   $ ls Controller/

   Each OpenStack Platform role directory also contains sub-directories for individual servers of that role type. The directories use the composable role hostname format:

   $ ls Controller/overcloud-controller-0

5. The Ansible tasks are tagged. To see the full list of tags, use the CLI argument --list-tags for ansible-playbook:

   $ ansible-playbook -i tripleo-ansible-inventory.yaml --list-tags deploy_steps_playbook.yaml

   Then apply tagged configuration using the --tags, --skip-tags, or --start-at-task with the ansible-playbook-command.sh script:

   $ ./ansible-playbook-command.sh --tags overcloud

6. When config-download configures Ceph, Ansible executes ceph-ansible from within the config-download external_deploy_steps_tasks playbook. When you run config-download manually, the second Ansible execution does not inherit the ssh_args argument. To pass Ansible environment variables to this execution, use a heat environment file. For example:

   parameter_defaults:
     CephAnsibleEnvironmentVariables:
       ANSIBLE_HOST_KEY_CHECKING: 'False'
       ANSIBLE_PRIVATE_KEY_FILE: '/home/stack/.ssh/id_rsa'

Procedure

1. Change to the config-download working directory for your overcloud. In this example, the working directory is for the overcloud named overcloud:

   $ cd /var/lib/mistral/overcloud

2. Run the git log command to list the commits in your working directory. You can also format the log output to show the date:

   $ git log --format=format:"%h%x09%cd%x09"
   a7e9063 Mon Oct 8 21:17:52 2018 +1000
   dfb9d12 Fri Oct 5 20:23:44 2018 +1000
   d0a910b Wed Oct 3 19:30:16 2018 +1000
   ...

   By default, the most recent commit appears first.

3. Run the git diff command against two commit hashes to see all changes between the deployments:

   $ git diff a7e9063 dfb9d12

Procedure

1. Generate the config-download files:

   $ openstack overcloud config download \
     --name overcloud \
     --config-dir ~/config-download

   • --name is the name of the overcloud that you want to use for the Ansible file export.
   • --config-dir is the location where you want to save the config-download files.

2. Change to the directory that contains your config-download files:

   $ cd ~/config-download

3. Generate a static inventory file:

   $ tripleo-ansible-inventory \
     --ansible_ssh_user heat-admin \
     --static-yaml-inventory inventory.yaml