search

IBM / cloud-pak-deployer

Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
https://ibm.github.io/cloud-pak-deployer/
Apache License 2.0
139 stars 68 forks source link

Allow update of CP4D license #380

Closed semccombe closed 1 year ago

semccombe commented 1 year ago

After an installation of CP4D 4.6.4 using the deployer, we found that the License Service was reporting usage of "IBM Cloud Pak for Data", whereas the customer has purchased "IBM Cloud Pak for Data Enterprise Edition."

To correct this, we used the following command to update the license:

cpd-cli manage apply-entitlement \
--cpd_instance_ns=${PROJECT_CPD_INSTANCE} \
--entitlement=cpd-enterprise \
--production=false

This command is documented here: https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=manage-apply-entitlement The CPFS License Service is documented here: https://www.ibm.com/docs/en/cpfs?topic=license-service

After this command was run, the License Server output started to correctly show usage of "IBM Cloud Pak for Data Enterprise Edition."

The request is that cp-deployer allow us to set the type of license (cpd-enterprise or cpd-standard) and whether it's a production license (true or false).

The alternative is to run the cpd-cli command after cp-deployer has completed, in order to update the license.

fketelaars commented 1 year ago

Implemented change. License status page now shows:

image

After changing to standard edition:

image