Chapter 7. Initial steps for overcloud preparation

Procedure

1. Log in to the undercloud as the stack user.

2. Source the stackrc file.

   Copy to Clipboard Toggle word wrap

   $ source ~/stackrc

3. Create a static inventory file of all nodes:

   Copy to Clipboard Toggle word wrap

   $ tripleo-ansible-inventory --static-yaml-inventory ~/inventory.yaml --stack STACK_NAME

   If you are not using the default overcloud stack name, set your stack name with the --stack STACK NAME option replacing STACK NAME with the name of your stack.

4. To execute Ansible playbooks on your environment, run the ansible-playbook command and include the full path of the dynamic inventory tool using the -i option. For example:

   Copy to Clipboard Toggle word wrap

   (undercloud) $ ansible-playbook -i ~/inventory.yaml PLAYBOOK

Procedure

1. Source the stackrc file.

   Copy to Clipboard Toggle word wrap

   $ source ~/stackrc

2. Run the openstack tripleo validator run command with the --group pre-upgrade option and include the /usr/libexec/platform-python python runtime environment:

   Copy to Clipboard Toggle word wrap

   $ openstack tripleo validator run --group pre-upgrade --python-interpreter /usr/libexec/platform-python -i inventory.yaml

3. Review the results of the validation report. To view detailed output from a specific validation, run the openstack tripleo validator show run --full command against the UUID of the specific validation from the report:

   Copy to Clipboard Toggle word wrap

   $ openstack tripleo validator show run  --full <UUID>

Procedure

1. Log in to the undercloud as the stack user.

2. Source the stackrc file.

   Copy to Clipboard Toggle word wrap

   $ source ~/stackrc

3. Log in to a Controller node and run the Pacemaker command to disable fencing:

   Copy to Clipboard Toggle word wrap

   $ ssh heat-admin@CONTROLLER_IP "sudo pcs property set stonith-enabled=false"

4. In the fencing.yaml environment file, set the EnableFencing parameter to false to ensure that fencing stays disabled during the upgrade process.

Procedure

1. Select an environment file and the check if it has an ExtraConfig parameter:

   Copy to Clipboard Toggle word wrap

   $ grep ExtraConfig ~/templates/custom-config.yaml

2. If the results show an ExtraConfig parameter for any role (e.g. ControllerExtraConfig) in the chosen file, check the full parameter structure in that file.

3. If the parameter contains any puppet Hierdata with a SECTION/parameter syntax followed by a value, it might have been been replaced with a parameter with an actual Puppet class. For example:

   Copy to Clipboard Toggle word wrap

   parameter_defaults:
     ExtraConfig:
       neutron::config::dhcp_agent_config:
         'DEFAULT/dnsmasq_local_resolv':
           value: 'true'

4. Check the director’s Puppet modules to see if the parameter now exists within a Puppet class. For example:

   Copy to Clipboard Toggle word wrap

   $ grep dnsmasq_local_resolv

   If so, change to the new interface.

5. The following are examples to demonstrate the change in syntax:

   • Example 1:

     Copy to Clipboard Toggle word wrap

     parameter_defaults:
       ExtraConfig:
         neutron::config::dhcp_agent_config:
           'DEFAULT/dnsmasq_local_resolv':
             value: 'true'

     Changes to:

     Copy to Clipboard Toggle word wrap

     parameter_defaults:
       ExtraConfig:
         neutron::agents::dhcp::dnsmasq_local_resolv: true

   • Example 2:

     Copy to Clipboard Toggle word wrap

     parameter_defaults:
       ExtraConfig:
         ceilometer::config::ceilometer_config:
           'oslo_messaging_rabbit/rabbit_qos_prefetch_count':
             value: '32'

     Changes to:

     Copy to Clipboard Toggle word wrap

     parameter_defaults:
       ExtraConfig:
         oslo::messaging::rabbit::rabbit_qos_prefetch_count: '32'