9.2. Changing default parameters for object storage

Procedure

1. Open your OpenStackControlPlane CR file, openstack_control_plane.yaml, and enable Ceilometer middleware and object encryption under the swiftProxy parameter in the swift template:

   apiVersion: core.openstack.org/v1beta1
   kind: OpenStackControlPlane
   metadata:
     name: openstack-control-plane
     namespace: openstack
   spec:
     ...
     swift:
       enabled: true
       template:
         swiftProxy:
           ceilometerEnabled: true
           encryptionEnabled: true
           replicas: 2
   ...

2. Add values for minPartHours, partPower, and ringReplicas under the swiftRing parameter:

   ...
   spec:
     ...
     swift:
       enabled: true
       template:
         swiftProxy:
           ...
         swiftRing:
           minPartHours: <number_of_hours>
           partPower: <partition_power>
           ringReplicas: <number_of_copies>
   ...

   • Replace <number_of_hours> with the minimum time in hours before a ring partition can be moved following a rebalance.
   • Replace <partition_power> with the partition power you want to use when building Object Storage rings, for example, 12.
   • Replace <number_of_copies> with the number of object copies you want in your cluster.

3. Change the number of workers in the object-server service by adding the defaultConfigOverwrite parameter under the swiftStorage parameter:

   ...
   spec:
     ...
     swift:
       enabled: true
       template:
         swiftProxy:
           ...
         swiftRing:
           ...
         swiftStorage:
           replicas: 3
           storageClass: local-storage
           storageRequest: 10Gi
           defaultConfigOverwrite:
             01-object-server.conf: |
               [DEFAULT]
               workers = <number_of_workers>

   • Replace <number_of_workers> with the number of workers you want in the object-server service.

4. Optional: Set resource limits for the Object Storage service containers to change the Quality of Service (QoS) class from BestEffort to Burstable. Add resources for swiftProxy and swiftStorage under the swift template:

   ...
   spec:
     ...
     swift:
       enabled: true
       template:
         swiftProxy:
           ...
           resources:
             limits:
               cpu: <cpu_limit>
               memory: <memory_limit>
             requests:
               cpu: <cpu_request>
               memory: <memory_request>
         swiftStorage:
           ...
           resources:
             limits:
               cpu: <cpu_limit>
               memory: <memory_limit>
             requests:
               cpu: <cpu_request>
               memory: <memory_request>
   ...

   • Replace <cpu_limit> with the maximum absolute allocation of CPU for the pods for this service in millicpus. For example, set to 2000m to limit the CPU allocation to the pods for this service to 200%.
   • Replace <memory_limit> with the maximum allocation of memory for the pods for this service. For example, set to 5Gi to limit the memory allocation to the pods for this service to 5 GiB.
   • Replace <cpu_request> with the requested minimum allocation of CPU for the pods for this service in millicpus. For example, set to 500m to allocate 50% of the CPU to the pods for this service.
   • Replace <memory_request> with the requested minimum allocation of memory for the pods for this service. For example, set to 5Gi to allocate 5 GiB of memory to the pods for this service.

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.