Configure back end availability zones

Configure back end availability zones (AZs) for Volume service back ends and the Backup service to group cloud infrastructure services for users. AZs are mapped to failure domains and Compute resources for high availability, fault tolerance, and resource scheduling.

About this task

For example, you could create an AZ of Compute nodes with specific hardware that users can select when they create an instance that requires that hardware.

Note

Post-deployment, AZs are created by using the RESKEY:availability_zones volume type extra specification.

Users can create a volume directly in an AZ provided that the volume type does not restrict the AZ.

Procedure

  1. Open your OpenStackControlPlane CR file, openstack_control_plane.yaml.
  2. Edit the CR file and add the AZ configuration.

    The following example demonstrates an AZ configuration:

    apiVersion: core.openstack.org/v1beta1
kind: OpenStackControlPlane
metadata:
name: openstack
spec:
  cinder:
    template:
      cinderVolumes:
        nfs:
          networkAttachments:
          - storage
          - storageMgmt
          customServiceConfigSecrets:
          - cinder-volume-nfs-secrets
          customServiceConfig: |
                [nfs]
                volume_backend_name=nfs
                backend_availability_zone=zone1
        iSCSI:
          networkAttachments:
          - storage
          - storageMgmt
          customServiceConfig: |
                [iscsi]
                volume_backend_name=iscsi
                backend_availability_zone=zone2
    • backend_availability_zone: The availability zone associated with the back end.
  3. Save the file.
  4. Update the control plane: 
    $ oc apply -f openstack_control_plane.yaml -n openstack
  5. Wait until RHOCP creates the resources related to the OpenStackControlPlane CR. Run the following command to check the status: 
    $ oc get openstackcontrolplane -n openstack

    The OpenStackControlPlane resources are created when the status is "Setup complete".

    Tip
    Append the -w option to the end of the get command to track deployment progress.