Containerized databases

For each containerized database (relational or NoSQL) for where compliance reporting is required, you must follow specific guidelines.

Note: The following instructions are for installing custom resource files for data stores running in Openshift or Kubernetes clusters. These instructions are not applicable when the data source runs on other types of containers.
For each containerized data store where compliance reporting is required:
  1. Add the License Service Annotations for Data Replication to the pods for the data store by using the custom resource (CR) file.
  2. Install the License Service.
Ensure License Service is installed.

License Service annotations

  • There are numerous IBM licenses available for Data Replication. Check with your enterprise to find out which Data Replication licenses apply to your installation. For each database for which you purchased entitlements create a CR file to update the pods for the source database. The following is an example of the custom resource:
    apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"
  • For each data store used as a replication source in a non-production environment create a Custom Resource file (CR) to update the pods for the source database. The following is an example of the custom resource:
    apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"

License Service annotations for IBM InfoSphere Data Replication

  • For each data store used as a replication source or target in a production environment create a CR file to update the pods for the source database. The following is an example of the custom resource:
    apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"
  • For each data store used as a replication source or target in a non-production environment create a CR file to update the pods for the source database. The following is an example of the custom resource:
    apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
    cloudpakId: "0ac0b413c9ab4fd6bc5b8b987e735de9"
    cloudpakName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productID: "4b6998f20e3c4c20a214f0d30bfe8667"
    productName: "IBM Infosphere Data Replication Cartridge for IBM Cloud Pak for Data Non-Production"
    productMetric: "VIRTUAL_PROCESSOR_CORE"
    productChargedContainers: "All"
    productCloudpakRatio: "1:1"

License Service annotations for IBM InfoSphere Data Replication Add-on for watsonx.data™

  • For each data store used as a replication target in a production environment create a CR file to update the pods for the target database. The following is an example of the custom resource:
    apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
  cloudpakId: "bfa9759de51c48f9bbc2702587416754"
  cloudpakName: "IBM InfoSphere Data Replication Cartridge Add-on for IBM watsonx.data"
  productID: "9c3c9f27f1c54aafbed1031c6e34ff57" 
  productName: "IBM InfoSphere Data Replication Add-on for IBM watsonx.data"
  productMetric: "RESOURCE_VALUE_UNIT"
  productChargedContainers: "All"
  productCloudpakRatio: "1:1"

License Service annotations for IBM InfoSphere Data Replication for watsonx.data

  • For each data store used as a replication target in a production environment create a CR file to update the pods for the target database. The following is an example of the custom resource: 
    apiVersion: operator.ibm.com/v1 
kind: IBMLicensingDefinition
metadata:
  name: idr-ls
  namespace: cpd-instance #Specifiy  namespace for Database otherwise License Service will check all PODS in the cluster
spec:
  action: cloneModify
  condition:
    metadata:
      annotations:
        <key: value>
        ... 
# For the <key:value>, use existing annotations in your pod where data replication licensing needs to be counted. 

  scope: cluster
  set:
# License Service Annotation for IIDR for Cp4D
  cloudpakId: "340672afe3cd42708e892265804d9132"
  cloudpakName: "IBM InfoSphere Data Replication for watsonx.data Cartridge Reserved". 
  productID: "94e5d3d95bf744598db4ced20d69c490"
  productName: "IBM InfoSphere Data Replication for watsonx.data"
  productMetric: "RESOURCE_VALUE_UNIT"
  productChargedContainers: "All"
  productCloudpakRatio: "1:1"