7.4. Adding an Image service API

Procedure

1. Open your OpenStackControlPlane CR file, openstack_control_plane.yaml, and add the parameters to the glance template to configure a new glanceAPI. In the following example, there is an existing default API that uses the Object Storage service (swift) as a back end, and you update the OpenStackControlPlane to deploy a new default1 API:

   ...
   apiVersion: core.openstack.org/v1beta1
   kind: OpenStackControlPlane
   spec:
     glance:
       template:
         databaseInstance: openstack
         keystoneEndpoint: default
         glanceAPIs:
           default:
             customServiceConfig: |
               [DEFAULT]
               enabled_backends = <backend_name>:swift
               [glance_store]
               default_backend = <backend_name>
               [<backend_name>]
               swift_store_create_container_on_put = True
               swift_store_auth_version = 3
               swift_store_auth_address = {{ .KeystoneInternalURL }}
               swift_store_endpoint_type = internalURL
               swift_store_user = service:glance
               swift_store_key = {{ .ServicePassword }}
             preserveJobs: false
             replicas: 3
           default1:
             type: single
             replicas: 1
         storage:
           storageRequest: 10G
   ...

   • Replace <backend_name> with the name of the default back end.

2. Update the control plane:

   $ oc apply -f openstack_control_plane.yaml -n openstack

3. 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.