Bug 1699027

Summary:	[RFE] OCS / CRS / CNS multi-tier-brick clusters for >1 storage class per cluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Aaren <aren.dej>
Component:	heketi	Assignee:	John Mulligan <jmulligan>
Status:	CLOSED ERRATA	QA Contact:	Vinayak Papnoi <vpapnoi>
Severity:	high	Docs Contact:	Amrita <asakthiv>
Priority:	medium
Version:	ocs-3.11	CC:	arukumar, asakthiv, asriram, hchiramm, kramdoss, madam, nigoyal, prpandey, puebele, rhs-bugs, rtalur, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 6
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	heketi-9.0.0-10	Doc Type:	Enhancement
Doc Text:	With this update, users can segregate their devices into groups like "fast/slow"` or "gold/silver/bronze" etc. Users can create storage classes to supply applications with different characteristics as per the required need. Heketi volumes can now be created with a tag-matching rule that enables users to set up tiers of storage on their devices. Users can apply tags to devices via Heketi and set up volume options to apply the rules based on those tags.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-17 04:31:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1926155

Description Aaren 2019-04-11 15:10:22 UTC

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.

Comment 4 Dave Cain 2019-04-23 16:11:46 UTC

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.

Comment 16 errata-xmlrpc 2020-12-17 04:31:42 UTC

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

Comment 21 Red Hat Bugzilla 2023-09-15 00:16:31 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days