Description of problem: Many cases and customers would see great benefit from having BOTH SSD and HDD disks on gluster nodes, allowing to serve more than 1 tier of storage for OCS with OpenShift/ OKD. It's a great waste of virtual infra resources to have 2 clusters simply to serve SSD storage class alongside HDD storage class. Version-Release number of selected component (if applicable): any/all OpenShift/ OCS How reproducible: n/a -- RFE Steps to Reproduce: 1. Openshift-Ansible installer has no way to create unique storage classes per brick tier on single clusters of gluster. Expected results: To be able to have 2 storage classes, based on specified disks in the same cluster of Gluster, when building OCS. Additional Info: This should be doable with vanilla Gluster installs, as well as OpenShift-Ansible playbooks.
Note: this RFE is also a request we get from OEM system vendor / server partners that work with us on building out OpenShift Container Platform 3 on baremetal. Having different physical disk media in servers is very common ( SAS/SATA SSD, NVMe, etc), especially with large capacity servers with quite a bit of drive bays.
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 (OpenShift Container Storage 3.11.z bug fix update), 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/RHBA-2020:5602
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days