Chapter 6. Configuring overcloud software with the director Operator

Procedure

1. Create a file named openstack-config-generator.yaml on your workstation. Include the resource specification to generate the Ansible playbooks. For example, the specification to generate the playbooks is as follows:

   apiVersion: osp-director.openstack.org/v1beta1
   kind: OpenStackConfigGenerator
   metadata:
     name: default
     namespace: openstack
   spec:
     enableFencing: true
     gitSecret: git-secret
     imageURL: registry.redhat.io/rhosp-rhel8/openstack-tripleoclient:16.2
     heatEnvConfigMap: heat-env-config
     # List of heat environment files to include from tripleo-heat-templates/environments
     heatEnvs:
     - ssl/tls-endpoints-public-dns.yaml
     - ssl/enable-tls.yaml
     tarballConfigMap: tripleo-tarball-config

   Set the following values in the resource specification:

   metadata.name

   Set to the name of the Compute node bare metal set, by default default.

   metadata.namespace

   Set to the director Operator namespace, by default openstack.

   spec.enableFencing

   Enable the automatic creation of required heat environment files to enable fencing.

   Note

   Production OSP environments must have fencing enabled. Virtual machines running pacemaker require the fence-agents-kubevirt package.

   spec.gitSecret

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

   spec.heatEnvs

   A list of default tripleo environment files used to generate the playbooks.

   spec.heatEnvConfigMap

   Set to the ConfigMap that contains your custom environment files, by default heat-env-config.

   spec.tarballConfigMap

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

   For more descriptions of the values you can use in the spec section, view the specification schema in the custom resource definition for the openstackconfiggenerator CRD:

   $ oc describe crd openstackconfiggenerator

   Save the file when you have finished configuring the Ansible config generator specification.

2. Create the Ansible config generator:

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

Verification

1. View the resource for the config generator:

   $ oc get openstackconfiggenerator/default -n openstack

Procedure

1. Access the remote shell for openstackclient:

   $ 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-8-for-x86_64-baseos-eus-rpms
         - rhel-8-for-x86_64-appstream-eus-rpms
         - rhel-8-for-x86_64-highavailability-eus-rpms
         - ansible-2.9-for-rhel-8-x86_64-rpms
         - openstack-16.2-for-rhel-8-x86_64-rpms
         - fast-datapath-for-rhel-8-x86_64-rpms
     tasks:
       - name: Register system
         redhat_subscription:
           username: myusername
           password: p@55w0rd!
           org_id: 1234567
           release: 8.4
           pool_ids: 1a85f9223e3d5e43013e3d6e8ff506fd
       - name: Disable all repos
         command: "subscription-manager repos --disable *"
       - name: Enable Controller node repos
         command: "subscription-manager repos --enable {{ item }}"
         with_items: "{{ repos }}"

   This play contains the following three tasks:

   • Register the node.
   • Disable any auto-enabled repositories.
   • Enable only the repositories relevant to the Controller node. The repositories are listed with the repos variable.

4. Register the overcloud nodes to required repositories:

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

Procedure

1. Select the hash/digest of the latest OpenStackConfigVersion:

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

Procedure

1. Create a file named openstack-deployment.yaml on your workstation. Include the resource specification to the Ansible playbooks. For example:

   apiVersion: osp-director.openstack.org/v1beta1
   kind: OpenStackDeploy
   metadata:
     name: default
   spec:
     configVersion: n5fch96h548h75hf4hbdhb8hfdh676h57bh96h5c5h59hf4h88h…
     configGenerator: default

   Set the following values in the resource specification:

   metadata.name

   Set the name of the Compute node baremetal set, by default default.

   metadata.namespace

   Set to the diretor Operator namespace, by default openstack.

   spec.configVersion

   The config version/git hash of the playbooks to deploy.

   spec.configGenerator

   The name of the configGenerator.

   For more descriptions of the values you can use inthe spec section, view the specification schema in the custom resource definition of the openstackdeploy CRD:

   $ oc describe crd openstackdeploy

   Save the file when you have finished configuring the OpenStackDeploy specification.

2. 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 tail the logs of the job to watch the Ansible playbooks running:

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

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