Creating Cloud Automation Manager persistent volumes using GlusterFS

Use GlusterFS to dynamically create four persistent volumes for Cloud Automation Manager database, log files, terraform, and Cloud Automation Manager Template Designer.

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 adding GlusterFS, see Adding GlusterFS storage to your IBM® Cloud Private cluster .

Procedure

If you have configured GlusterFS on your IBM Cloud Private cluster, you can use GlusterFS to dynamically create the required Cloud Automation Manager persistent volumes. You must set some configuration parameters during the Cloud Automation Manager 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 Automation Manager, then set the following values while you configure the chart parameters:

  • MongoDB 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.
  • Logs 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.
  • Terraform 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.
  • Template Designer 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 Automation Manager, 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:

    camMongoPV:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    camLogsPV:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    camTerraformPV:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"
    camBPDAppDataPV:
      persistence:
        useDynamicProvisioning: true
        storageClassName: "<your GlusterFS storage class name>"