Creating Cost and Asset Management persistent volumes using GlusterFS

Use GlusterFS to dynamically create five persistent volumes for Cost and Asset Management databases and one for Cloud Management Platform database.

Before you begin

1. To use this procedure, you must configure GlusterFS in your IBM Cloud Private cluster and define a storageclass. For more information about GlusterFS, see GlusterFS.

Procedure

If you have configured GlusterFS on your IBM Cloud Private cluster, you can use GlusterFS to dynamically create the required Cost and Asset Management persistent volumes. You must set some configuration parameters during the Cost and Asset Management helm chart installation. You can use the IBM Cloud Private user interface or the command line.

• If you are using the IBM Cloud Private user interface to install Cloud Management Platform, then set the following values while you configure the chart parameters:

  • CouchDB Volume section:
    • Select the Use Dynamic Provisioning.
    • Set the Dynamic Provisioning: Storage Class Name to the GlusterFS storage class you configured in the Before you begin section of this topic.

• If you are using the IBM Cloud Private user interface to install Cost and Asset Management, then set the following values while you configure the chart parameters:

  • CAM data Volume section:
    • Select the Use Dynamic Provisioning.
    • Set the Dynamic Provisioning: Storage Class Name to the GlusterFS storage class you configured in the Before you begin section of this topic.
  • CAM rabbitmq Volume section:
    • Select the Use Dynamic Provisioning.
    • Set the Dynamic Provisioning: Storage Class Name to the GlusterFS storage class you configured in the Before you begin section of this topic.
  • CAM MariaDB data Volume section:
    • Select the Use Dynamic Provisioning.
    • Set the Dynamic Provisioning: Storage Class Name to the GlusterFS storage class you configured in the Before you begin section of this topic.
  • CAM MariaDB backup Volume section:
    • Select the Use Dynamic Provisioning.
    • Set the Dynamic Provisioning: Storage Class Name to the GlusterFS storage class you configured in the Before you begin section of this topic.
  • CAM MariaDB tmp Volume section:
    • Select the Use Dynamic Provisioning.
    • Set the Dynamic Provisioning: Storage Class Name to the GlusterFS storage class you configured in the Before you begin section of this topic.

• If you are using the helm command line to install Cloud Management Platform, then set these additional parameters. It is recommended to use an input YAML file to set these parameters on the helm install command:

  • Example input storage YAML file:

    coreCouchdbPv0:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    

• If you are using the helm command line to install Cost and Asset Management, then set these additional parameters. It is recommended to use an input YAML file to set these parameters on the helm install command:

  • Example input storage YAML file:

    camDataPv0:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    camRabbitmqPv0:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    mariadbDataPv0:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    mariadbBackupPv0:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    mariadbTmpPv0:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"