Chapter 9. Customizing the Object Storage service (swift)

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

   Copy to Clipboard Toggle word wrap

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

   Copy to Clipboard Toggle word wrap
   • Replace <number_of_hours> with the minimum time in hours before you want a partition in a ring to 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>

   Copy to Clipboard Toggle word wrap
   • Replace <number_of_workers> with the number of workers you want in the object-server service.

4. Update the control plane:

   $ oc apply -f openstack_control_plane.yaml -n openstack

   Copy to Clipboard Toggle word wrap

5. Wait until RHOCP creates the resources related to the OpenStackControlPlane CR. Run the following command to check the status:

   $ oc get openstackcontrolplane -n openstack

   Copy to Clipboard Toggle word wrap

   The OpenStackControlPlane resources are created when the status is "Setup complete".

   Tip

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

Procedure

1. Log in to one of the Controller nodes.

2. Run the following command:

   $ oc debug --keep-labels=true job/swift-ring-rebalance -- /bin/sh -c 'swift-ring-tool get && swift-recon -arqlT --md5'

   Copy to Clipboard Toggle word wrap

   • Optional: Use the --all option to return additional output.

     This command queries all servers on the ring for the following data:

     • Async pendings: If the cluster load is too high and processes cannot update database files fast enough, some updates occur asynchronously. These numbers decrease over time.
     • Replication metrics: Review the replication timestamps; full replication passes happen frequently with few errors. An old entry, for example, an entry with a timestamp from six months ago, indicates that replication on the node has not completed in the last six months.
     • Ring md5sums: This ensures that all ring files are consistent on all nodes.
     • swift.conf md5sums: This ensures that all configuration files are consistent on all nodes.
     • Quarantined files: There must be no, or very few, quarantined files for all nodes.
     • Time-sync: All nodes must be synchronized.