7.5. Decommissioning an Image service API

Procedure

1. Verify that more that one glanceAPI is deployed in the OpenStackControlPlane:

   $ oc -n openstack get oscp  $(oc get oscp -o custom-columns=NAME:.metadata.name --no-headers) -o jsonpath='{.spec.glance.template.glanceAPIs}' | jq

2. Identify the current glanceAPI that is registered in the Keystone catalog:

   $ oc -n openstack get oscp $(oc get oscp -o custom-columns=NAME:.metadata.name --no-headers) -o jsonpath='{.spec.glance.template.keystoneEndpoint}'

3. Verify that the new glanceAPI has a Keystone endpoint:

   $ oc exec -it openstackclient bash -- openstack endpoint list | grep image

4. If the glanceAPI that you are removing is the API registered in the Keystone catalog, open your OpenStackControlPlane CR file, openstack_control_plane.yaml to decommission the API and update the keystoneEndpoint parameter. In the following example, you remove the glanceAPI that is named default and update the keystoneEndpoint parameter to default1:

   ...
   apiVersion: core.openstack.org/v1beta1
   kind: OpenStackControlPlane
   spec:
     glance:
       template:
         keystoneEndpoint: default1
         glanceAPIs:
           default1:
             type: single
             replicas: 1
         storage:
           storageRequest: 10G
   ...

5. Update the control plane:

   $ oc apply -f openstack_control_plane.yaml -n openstack

6. 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".

   提示

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