Chapter 3. Enabling cloud rating in a RHOSO environment

Procedure

1. Create a Secret CR on your workstation to connect Loki to the AWS s3 object storage you use for the Loki log store:

   apiVersion: v1
   kind: Secret
   metadata:
     name: cloudkitty-loki-s3
     namespace: openstack
   stringData:
     access_key_id: <your_key_id>
     access_key_secret: <your_key_secret>
     bucketnames: <your_bucket_name>
     endpoint: <your_s3_endpoint>

   Copy to Clipboard Toggle word wrap

2. Create the Secret CR in the cluster:

   $ oc create -f loki_s3_secret.yaml -n openstack

   Copy to Clipboard Toggle word wrap

3. Verify that the Secret CR is created:

   $ oc describe secret logging-loki-s3 -n openstack

   Copy to Clipboard Toggle word wrap
4. Open the OpenStackControlPlane CR file on your workstation, for example, openstack_control_plane.yaml.

5. Locate the service definition for telemetry and add the following cloudkitty configuration to enable the Ratings service:

     telemetry:
       enabled: true
         template:
           ...
           cloudkitty:
             enabled: true
             s3StorageConfig:
               schemas:
               - effectiveDate: "2024-11-18"
                 version: v13
               secret:
                 name: cloudkitty-loki-s3
                 type: s3

   Copy to Clipboard Toggle word wrap

6. Check how long metrics data is being retained for, and ensure that they are not being stored for more than 7 days:

         template:
           metricStorage:
             enabled: true
             ...
             monitoringStack:
               ...
               storage:
                 strategy: persistent
                 retention: 24h

   Copy to Clipboard Toggle word wrap
7. Ensure that the Loki Operator log store is sized for your environment. For more information, see Loki deployment sizing.

8. Update the control plane:

   $ oc apply -f openstack_control_plane.yaml -n openstack

   Copy to Clipboard Toggle word wrap

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

   $ oc get openstackcontrolplane -n openstack
   NAME              STATUS  MESSAGE
   openstack-control-plane   Unknown   Setup started

   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.

10. Confirm that the control plane is deployed by reviewing the pods in the openstack namespace:

    $ oc get pods -n openstack

    Copy to Clipboard Toggle word wrap

    The control plane is deployed when all the pods are either completed or running.

Verification

1. Access the remote shell for the openstackclient pod and verify that the Rating service is enabled:

   $ oc rsh -n openstack openstackclient
   $ openstack rating module list
   +-----------+---------+----------+
   | Module    | Enabled | Priority |
   +-----------+---------+----------+
   | hashmap   | False   | 1        |
   | noop      | True    | 1        |
   | pyscripts | False   | 1        |
   +-----------+---------+----------+

   Copy to Clipboard Toggle word wrap
2. Ensure that you can enable, disable, and change the priority of each module. For more information about how to use the Rating service, see https://docs.openstack.org/cloudkitty/latest/user/rating/index.html.