Chapter 6. Configuring and deploying the overcloud with director Operator

Procedure

1. Create a file named openstack-config-generator.yaml on your workstation. Include the resource specification to generate the Ansible playbooks. The following example defines a specification to generate the playbooks:

   apiVersion: osp-director.openstack.org/v1beta1
   kind: OpenStackConfigGenerator
   metadata:
     name: default 

   1

   
     namespace: openstack
   spec:
     enableFencing: true 

   2

   
     gitSecret: git-secret 

   3

   
     imageURL: registry.redhat.io/rhosp-rhel8/openstack-tripleoclient:17.1
     heatEnvConfigMap: heat-env-config 

   4

   
     # List of heat environment files to include from tripleo-heat-templates/environments
     heatEnvs: 

   5

   
     - ssl/tls-endpoints-public-dns.yaml
     - ssl/enable-tls.yaml
     tarballConfigMap: tripleo-tarball-config 

   6

   1

   The name of the config generator, which is default by default.

   2

   Set to true to enable the automatic creation of required heat environment files to enable fencing. Production RHOSP environments must have fencing enabled. Virtual machines running Pacemaker require the fence-agents-kubevirt package.

   3

   Set to the ConfigMap object that contains the Git authentication credentials, by default git-secret.

   4

   The ConfigMap object that contains your custom environment files, by default heat-env-config.

   5

   A list of the default heat environment files, provided by TripleO in the tripleo-heat-templates/environments directory, to use to generate the playbooks.

   6

   The ConfigMap object that contains the tarball with your custom heat templates, by default tripleo-tarball-config.

2. Optional: To change the location of the container images the OpenStackConfigGenerator CR uses to create the ephemeral heat service, add the following configuration to your openstack-config-generator.yaml file:

   spec:
     ...​
     ephemeralHeatSettings:
       heatAPIImageURL: <heat_api_image_location>
       heatEngineImageURL: <heat_engine_image_location>
       mariadbImageURL: <mariadb_image_location>
       rabbitImageURL: <rabbitmq_image_location>

   • Replace <heat_api_image_location> with the path to the directory where you host your heat API image, openstack-heat-api.
   • Replace <heat_engine_image_location> with the path to the directory where you host your heat engine image, openstack-heat-engine.
   • Replace <mariadb_image_location> with the path to the directory where you host your MariaDB image, openstack-mariadb.
   • Replace <rabbitmq_image_location> with the path to the directory where you host your RabbitMQ image, openstack-rabbitmq.

3. Optional: Customize the ephemeral heat instance to override default heat parameter values. For example, include the following configuration to change the default max_template_size:

   spec:
     ...
     ephemeralHeatSettings:
       ...
       heatOverride:
         customServiceConfig: |
           [DEFAULT]
           max_template_size=1048576

4. Optional: To create the Ansible playbooks for configuration generation in debug mode, add the following configuration to your openstack-config-generator.yaml file:

   spec:
     ...​
     interactive: true

   For more information on debugging an OpenStackConfigGenerator pod in interactive mode, see Debugging configuration generation.

5. Save the openstack-config-generator.yaml file.

6. Create the Ansible config generator:

   $ oc create -f openstack-config-generator.yaml -n openstack

7. Verify that the resource for the config generator is created:

   $ oc get openstackconfiggenerator/default -n openstack

Procedure

1. Open an RSH connection to the OpenStackClient pod:

   $ oc rsh -n openstack openstackclient

2. Change to the cloud-admin home directory:

   $ cd /home/cloud-admin

3. Create a playbook that uses the redhat_subscription modules to register your nodes. For example, the following playbook registers Controller nodes:

   ---
   - name: Register Controller nodes
     hosts: Controller
     become: yes
     vars:
       repos:
         - rhel-9-for-x86_64-baseos-e4s-rpms
         - rhel-9-for-x86_64-appstream-e4s-rpms
         - rhel-9-for-x86_64-highavailability-e4s-rpms
         - openstack-17.1-for-rhel-9-x86_64-rpms
         - fast-datapath-for-rhel-9-x86_64-rpms
         - rhceph-6-tools-for-rhel-9-x86_64-rpms
     tasks:
       - name: Register system 

   1

   
         redhat_subscription:
           username: myusername
           password: p@55w0rd!
           org_id: 1234567
           release: 9.2
           pool_ids: 1a85f9223e3d5e43013e3d6e8ff506fd
       - name: Disable all repos 

   2

   
         command: "subscription-manager repos --disable *"
       - name: Enable Controller node repos 

   3

   
         command: "subscription-manager repos --enable {{ item }}"
         with_items: "{{ repos }}"

   1

   Task that registers the node.

   2

   Task that disables any auto-enabled repositories.

   3

   Task that enables only the repositories relevant to the Controller node. The repositories are listed with the repos variable.

4. Register the overcloud nodes to the required repositories:

   $ ansible-playbook -i /home/cloud-admin/ctlplane-ansible-inventory ./rhsm.yaml

Procedure

1. Retrieve the hash/digest of the latest OpenStackConfigVersion object, which represents the Ansible playbooks that should be used to configure the overcloud:

   $ oc get -n openstack --sort-by {.metadata.creationTimestamp} openstackconfigversion -o json

2. Create a file named openstack-deployment.yaml on your workstation and include the resource specification to the Ansible playbooks:

   apiVersion: osp-director.openstack.org/v1beta1
   kind: OpenStackDeploy
   metadata:
     name: default
   spec:
     configVersion: <config_version>
     configGenerator: default

   • Replace <config_version> with the Ansible playbooks hash/digest retrieved in step 1, for example, n5fch96h548h75hf4hbdhb8hfdh676h57bh96h5c5h59hf4h88h....
3. Save the openstack-deployment.yaml file.

4. Create the OpenStackDeploy resource:

   $ oc create -f openstack-deployment.yaml -n openstack

   As the deployment runs, it creates a Kubernetes job to execute the Ansible playbooks. You can view the logs of the job to watch the Ansible playbooks running:

   $ oc logs -f jobs/deploy-openstack-default

   You can also manually access the executed Ansible playbooks by logging into the openstackclient pod. You can find the ansible playbooks and the ansible.log file for the current deployment in /home/cloud-admin/work/directory.

Procedure

1. Open a Remote Shell (RSH) connection to the OpenStackConfigGenerator pod:

   $ oc rsh $(oc get pod -o name -l job-name=generate-config-default)

2. Inspect the files and playbook rendering:

   $ ls -la /home/cloud-admin/
   ...
   config 

   1

   
   config-custom 

   2

   
   config-passwords 

   3

   
   create-playbooks.sh 

   4

   
   process-heat-environment.py 

   5

   
   tht-tars 

   6