Chapter 6. Post-deployment configuration
After the overcloud deployment finishes, complete the following steps to validate the functionality.
Procedure
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-zoneparameter:openstack server create --flavor m1.tiny --image cirros --network private --security-group basic dcn-instance --availability-zone dcn0
$ openstack server create --flavor m1.tiny --image cirros --network private --security-group basic dcn-instance --availability-zone dcn0Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create a volume on the first availability zone. This volume uses the cinder active/active service running on the
dcn0nodes.openstack volume create --size 1 --availability-zone dcn0 myvol
$ openstack volume create --size 1 --availability-zone dcn0 myvolCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteThis 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 Copy linkLink copied to clipboard!
Verify that the container is functioning correctly.
Procedure
- Log in to the node that is running the Ceph MON service by using SSH.
Run the following command to view container health:
podman exec ceph-mon-$HOSTNAME ceph -s --cluster CLUSTERNAME
$ podman exec ceph-mon-$HOSTNAME ceph -s --cluster CLUSTERNAMECopy to Clipboard Copied! Toggle word wrap Toggle overflow Replace
CLUSTERNAMEwith the name of the cluster, for example,dcn0. The default value isceph.-
Confirm that the health status of the cluster is
HEALTH_OKand that all of the OSDs areup.