Chapter 7. Deploying a RHOSP hyperconverged infrastructure (HCI) with director Operator

Procedure

1. Access the remote shell for openstackclient:

   $ oc rsh -n openstack openstackclient

2. Unset the OS_CLOUD environment variable:

   $ unset OS_CLOUD

3. Change to the cloud-admin directory:

   $ cd /home/cloud-admin/

4. Generate a new roles_data.yaml file with the Controller and ComputeHCI roles:

   $ openstack overcloud roles generate -o roles_data.yaml Controller ComputeHCI

5. Exit the openstackclient pod:

   $ exit

6. Copy the custom roles_data.yaml file from the openstackclient pod to your custom templates directory:

   $ oc cp openstackclient:/home/cloud-admin/roles_data.yaml custom_templates/roles_data.yaml -n openstack

Procedure

1. Create a directory for your custom templates:

   $ mkdir custom_templates

2. Create a custom template file named multiple_nics_vlans_dvr.j2 in your custom_templates directory.
3. Add configuration for the NICs of your bare-metal nodes to your multiple_nics_vlans_dvr.j2 file. For an example NIC configuration file, see Custom NIC heat template for HCI Compute nodes.

4. Create a directory for your custom environment files:

   $ mkdir custom_environment_files

5. Map the NIC template for your overcloud role in the network-environment.yaml environment file in your custom_environment_files directory:

   parameter_defaults:
     ComputeHCINetworkConfigTemplate: 'multiple_nics_vlans_dvr.j2'

Procedure

1. Navigate to the location of your custom templates:

   $ cd ~/custom_templates

2. Archive the templates into a gzipped tarball:

   $ tar -cvzf custom-config.tar.gz *.yaml

3. Create the tripleo-tarball-config ConfigMap CR and use the tarball as data:

   $ oc create configmap tripleo-tarball-config --from-file=custom-config.tar.gz -n openstack

4. Verify that the ConfigMap CR is created:

   $ oc get configmap/tripleo-tarball-config -n openstack

Procedure

1. Create the heat-env-config ConfigMap object:

   $ oc create configmap -n openstack heat-env-config \
    --from-file=~/<dir_custom_environment_files>/ \
    --dry-run=client -o yaml | oc apply -f -

   • Replace <dir_custom_environment_files> with the directory that contains the environment files you want to use in your overcloud deployment. The ConfigMap object stores these as individual data entries.

2. Verify that the heat-env-config ConfigMap object contains all the required environment files:

   $ oc get configmap/heat-env-config -n openstack

Procedure

1. Create a file named openstack-hcicompute.yaml on your workstation. Include the resource specification for the HCI Compute nodes. For example, the specification for 3 HCI Compute nodes is as follows:

   apiVersion: osp-director.openstack.org/v1beta1
   kind: OpenStackBaremetalSet
   metadata:
     name: computehci 

   1

   
     namespace: openstack 

   2

   
   spec: 

   3

   
     count: 3
     baseImageUrl: http://<source_host>/rhel-9.2-x86_64-kvm.qcow2
     deploymentSSHSecret: osp-controlplane-ssh-keys
     ctlplaneInterface: enp8s0
     networks:
       - ctlplane
       - internal_api
       - tenant
       - storage
       - storage_mgmt
     roleName: ComputeHCI
     passwordSecret: userpassword 

   4

   1

   The name of the HCI Compute node bare metal set, for example, computehci.

   2

   The OSPdO namespace, for example, openstack.

   3

   The configuration for the HCI Compute nodes.

   4

   Optional: The Secret resource that provides root access on each node to users with the password.

2. Save the openstack-hcicompute.yaml file.

3. Create the HCI Compute nodes:

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

4. Verify that the resource for the HCI Compute nodes is created:

   $ oc get openstackbaremetalset/computehci -n openstack

5. To verify the creation of the HCI Compute nodes, view the bare-metal machines that RHOCP manages:

   $ oc get baremetalhosts -n openshift-machine-api

6. Create the Ansible playbooks for overcloud configuration with the OpenStackConfigGenerator CRD. For more information, see Creating Ansible playbooks for overcloud configuration with the OpenStackConfigGenerator CRD.
7. Register the operating system of your overcloud. For more information, see Registering the operating system of your overcloud.
8. Apply the overcloud configuration. For more information, see Applying overcloud configuration with director Operator.