Description of problem: At present we dont have a way to mention from which 'cluster' of CNS the volume has to be provisioned. Adding this ( optional) feature gives more flexibility for the admin to define QoS based on his setup. Version-Release number of selected component (if applicable): CNS 3.4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Example usage in Storage class: + clusterid: "630372ccdc720a92c681fb928f27b53f" resturl: "http://127.0.0.1:8081" restuser: "admin" secretNamespace: "default" secretName: "heketi-secret" ``` +* `clusterid`: `630372ccdc720a92c681fb928f27b53f` is the ID of the cluster which above mentioned endpoint `glusterfs-cluster` refer. This endpoint should hold the ip addresses of all the nodes of cluster with id `630372ccdc720a92c681fb928f27b53f`.
This functionality is available atleast from OCP version openshift v3.5.0.14+20b49d0.
Validation of this feature is completed. Admin can define the storageclass according to a clusterid or a list of cluster id passed as comma separated value. Moving this bug to verified.
This is not a finalized draft, I am requesting michael to look at this. However my point is that this feature should be use case driven. --snip-- This release add a new storage class parameter called 'clusterid' in Gluster Dynamic Provisioner configuration. With this, selecting a cluster for a dynamically provisioning volumes made possible. This allows an administrator to define the storageclass according to a cluster ID or a list of cluster ID passed as comma separated value. For eg# If there are are two clusters where one with fast SSDs and another with IDE disks, admin can define a storage class to provision volumes from only SSD cluster by specifying SSD cluster ID in a specific storage class definition vice versa. --/snip--
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1116