Activating IBM Concert Software License Metrics (OCP without CPFS)

IBM® Concert is licensed under RESOURCE_UNIT (RU) license metrics.

You need to deploy IBM Licensing service on your cluster and then activate the licensing service on Concert. The Concert licensing service runs two cronjobs. These jobs ensures that the license usage is calculated and updated on to the licensing Service.

Prerequisite

If you do not have the licensing service running on your cluster, refer the following steps for Installing License Service without Operator Lifecycle Manager (OLM).
After deploying the licensing service, create OperandRequest CRD by copying the CRD from Concert GitHub repository to your workstation. After copying it on your workstation, run the following command
```
kubectl apply -f operator.ibm.com_operandrequests.yaml -n <concert-namespace>
```

Enable licensing

Run the following command to enable licensing. It will create a secret and config map that has licensing service access URL, token, and certificate. This is used by Concert license metering jobs to upload the results on the licensing service.

./activate-license-cron.sh <concert namespace>

Verification

Verify the logs for the concert-metering-cronjob. Use the following command to check the details of next scheduled time to run the cron job:
```
kubectl get cronjob concert-metering-aggregate-cronjob --template
'{{.status.lastScheduleTime}}' -n <concert namespace>
```
Note: The cron job runs in every 24 hr.
The result gives the detail for the run time that cron job will execute.
Example:
If it says 2024-12-10T19:00:00Z, then the next run time would be 2024-13-10T19:00:00Z . You should check the logs of the cron job just after 2024-13-10T19:00:00Z. Run the following query to get the logs
```
kubectl get pods --selector=job-name=concert-metering-cronjob -n <concert namespace>
```
After you get the pod name, run the following command to get the list of successful logs:
```
kubectl logs <pod name> -n <concertnamespace>
```