Appendix E. Gluster Block Storage as Backend for Logging and Metrics

Following section guides to configure Gluster Block Storage as the backend storage for logging and metrics

Note

Block volume expansion is not supported in CNS 3.6. Administrators are required to do proper capacity planning while using Gluster Block as backend storage when using dynamic provisioning.

E.1. Prerequisites

Before setting gluster block storage as the backend for logging or metrics, check if the following prerequisites are met:
  • In the storageclass file, check if the default storage class is set to the storage class of gluster block. For example:
    # oc get storageclass
    NAME                TYPE
    gluster-block        gluster.org/glusterblock
  • If the default is not set to gluster-block (or any other name that you have provided) then execute the following command. For example:
    # oc patch storageclass gluster-block -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
    • Execute the following command to verify:
      oc get storageclass
      NAME                     TYPE
      gluster-block (default)   gluster.org/glusterblock