Chapter 6. Post-deployment configuration

After the overcloud deployment finishes, complete the following steps to validate the functionality.

Procedure

  1. Create a test instance in the availability zones. In this example, the new instance runs on the distributed compute node (DCN). The specific AZ is targeted using the --availability-zone parameter: 

    $ openstack server create --flavor m1.tiny --image cirros --network private --security-group basic dcn-instance --availability-zone dcn0

  2. Create a volume on the first availability zone. This volume uses the cinder active/active service running on the dcn0 nodes. 

    $ openstack volume create --size 1 --availability-zone dcn0 myvol
    Note

    This step depends on the cinder availability zone configuration, which is defined by CinderStorageAvailabilityZone. For more information, see Deploying availability zones in the Storage Guide.

You now have two separate HCI stacks, with a Ceph cluster deployed by each one. For more information on HCI, see Hyperconverged Infrastructure Guide.

6.1. Checking container health

Verify that the container is functioning correctly.

Procedure

  1. Log in to the node that is running the Ceph MON service by using SSH.

  2. Run the following command to view container health: 

    $ podman exec ceph-mon-$HOSTNAME ceph -s --cluster CLUSTERNAME

    Replace CLUSTERNAME with the name of the cluster, for example, dcn0. The default value is ceph.

  3. Confirm that the health status of the cluster is HEALTH_OK and that all of the OSDs are up.