Chapter 11. 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:

   Copy to Clipboard Toggle word wrap

   $ 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:

   Copy to Clipboard Toggle word wrap

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

Procedure

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

   Copy to Clipboard Toggle word wrap

   $ cd /var/lib/mistral/overcloud/

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

   Copy to Clipboard Toggle word wrap

   $ ./ansible-playbook-command.sh

   You can pass additional Ansible arguments to this script, which are then passed unchanged to the ansible-playbook command. This makes it is possible to take further advantage of Ansible features, such as check mode (--check), limiting hosts (--limit), or overriding variables (-e). For example:

   Copy to Clipboard Toggle word wrap

   $ ./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:

   Copy to Clipboard Toggle word wrap

   $ less deploy_steps_playbook.yaml

   The playbook uses various task files contained with 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 defined in your overcloud’s roles_data file. For example:

   Copy to Clipboard Toggle word wrap

   $ 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. For example:

   Copy to Clipboard Toggle word wrap

   $ 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:

   Copy to Clipboard Toggle word wrap

   $ 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. For example:

   Copy to Clipboard Toggle word wrap

   $ ./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:

   Copy to Clipboard Toggle word wrap

   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 case, the working directory is for the overcloud named overcloud:

   Copy to Clipboard Toggle word wrap

   $ 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:

   Copy to Clipboard Toggle word wrap

   $ 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:

   Copy to Clipboard Toggle word wrap

   $ git diff a7e9063 dfb9d12

Procedure

1. Generate the config-download files:

   Copy to Clipboard Toggle word wrap

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

   • --name is the overcloud to use for the Ansible file export.
   • --config-dir is the location to save the config-download files,

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

   Copy to Clipboard Toggle word wrap

   $ cd ~/config-download

3. Generate a static inventory file:

   Copy to Clipboard Toggle word wrap

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