Chapter 5. Creating overcloud nodes with director Operator

Procedure

1. Create a file named openstack-controller.yaml on your workstation. Include the resource specification for the Controller nodes. The following example defines a specification for a control plane that consists of 3 Controller nodes:

   apiVersion: osp-director.openstack.org/v1beta2
   kind: OpenStackControlPlane
   metadata:
     name: overcloud 1
     namespace: openstack 2
   spec: 3
     openStackClientNetworks:
           - ctlplane
           - internal_api
           - external
     openStackClientStorageClass: host-nfs-storageclass
     passwordSecret: userpassword 4
     virtualMachineRoles:
       Controller:
         roleName: Controller
         roleCount: 3
         networks:
           - ctlplane
           - internal_api
           - external
           - tenant
           - storage
           - storage_mgmt
         cores: 12
         memory: 64
         rootDisk:
           diskSize: 500
           baseImageVolumeName: openstack-base-img 5
           storageClass: host-nfs-storageclass 6
           storageAccessMode:  ReadWriteMany
           storageVolumeMode: Filesystem
         # optional configure additional discs to be attached to the VMs,
         # need to be configured manually inside the VMs where to be used.
         additionalDisks:
           - name: datadisk
             diskSize: 500
             storageClass: host-nfs-storageclass
             storageAccessMode:  ReadWriteMany
             storageVolumeMode: Filesystem
     openStackRelease: "17.1"

   1

   The name of the overcloud control plane, for example, overcloud.

   2

   The OSPdO namespace, for example, openstack.

   3

   The configuration for the control plane.

   4

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

   5

   The name of the data volume that stores the base operating system image for your Controller VMs. For more information on creating the data volume, see Creating a data volume for the base operating system.

   6

   For information on configuring Red Hat OpenShift Container Platform (RHOCP) storage, see Dynamic provisioning.

2. Save the openstack-controller.yaml file.

3. Create the control plane:

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

4. Wait until RHOCP creates the resources related to OpenStackControlPlane CR. OSPdO also creates an OpenStackClient pod that you can access through a remote shell to run RHOSP commands.

Verification

1. View the resource for the control plane:

   $ oc get openstackcontrolplane/overcloud -n openstack

2. View the OpenStackVMSet resources to verify the creation of the control plane VM set:

   $ oc get openstackvmsets -n openstack

3. View the VMs to verify the creation of the control plane OpenShift Virtualization VMs:

   $ oc get virtualmachines -n openstack

4. Test access to the openstackclient remote shell:

   $ oc rsh -n openstack openstackclient

Procedure

1. Create a file named openstack-compute.yaml on your workstation. Include the resource specification for the Compute nodes. The following example defines a specification for 1 Compute node:

   apiVersion: osp-director.openstack.org/v1beta1
   kind: OpenStackBaremetalSet
   metadata:
     name: compute 1
     namespace: openstack 2
   spec: 3
     count: 1
     baseImageUrl: http://<source_host>/rhel-9.2-x86_64-kvm.qcow2
     deploymentSSHSecret: osp-controlplane-ssh-keys
     # If you manually created an OpenStackProvisionServer, you can use it here,
     # otherwise director Operator will create one for you (with `baseImageUrl` as the image that it server)
     # to use with this OpenStackBaremetalSet
     # provisionServerName: openstack-provision-server
     ctlplaneInterface: enp2s0
     networks:
       - ctlplane
       - internal_api
       - tenant
       - storage
     roleName: Compute
     passwordSecret: userpassword 4

   1

   The name of the Compute node bare-metal set, for example, compute.

   2

   The OSPdO namespace, for example, openstack.

   3

   The configuration for the Compute nodes.

   4

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

2. Save the openstack-compute.yaml file.

3. Create the Compute nodes:

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

Verification

1. View the resource for the Compute nodes:

   $ oc get openstackbaremetalset/compute -n openstack

2. View the bare-metal machines that RHOCP manages to verify the creation of the Compute nodes:

   $ oc get baremetalhosts -n openshift-machine-api

Procedure

1. Create a file named openstack-provision.yaml on your workstation. Include the resource specification for the Provisioning server. The following example defines a specification for a Provisioning server using a specific RHEL 9.2 QCOW2 images:

   apiVersion: osp-director.openstack.org/v1beta1
   kind: OpenStackProvisionServer
   metadata:
     name: openstack-provision-server 1
     namespace: openstack 2
   spec:
     baseImageUrl: http://<source_host>/rhel-9.2-x86_64-kvm.qcow2 3
     port: 8080 4

   1

   The name that identifies the OpenStackProvisionServer CR.

   2

   The OSPdO namespace, for example, openstack.

   3

   The initial source of the RHEL QCOW2 image for the Provisioning server. The image is downloaded from this remote source when the server is created.

   4

   The Provisioning server port, set to 8080 by default. You can change it for a specific port configuration.

   For further descriptions of the values you can use to configure your OpenStackProvisionServer CR, view the OpenStackProvisionServer CRD specification schema:

   $ oc describe crd openstackprovisionserver

2. Save the openstack-provision.yaml file.

3. Create the Provisioning Server:

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

4. Verify that the resource for the Provisioning server is created:

   $ oc get openstackprovisionserver/openstack-provision-server -n openstack