Bug 2025043

Summary:	[RFE][ODF] Make flexible scaling feature configurable at UI
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Mustafa Aydın <maydin>
Component:	management-console	Assignee:	Afreen <afrahman>
Status:	CLOSED DEFERRED	QA Contact:	Elad <ebenahar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.8	CC:	afrahman, egemen.bal, etamir, jefbrown, madam, mmuench, nibalach, ocs-bugs, owasserm
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	maydin: needinfo-
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2054359 (view as bug list)		Environment:
Last Closed:	2022-02-02 10:08:13 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:	2054359

Description Mustafa Aydın 2021-11-19 18:38:07 UTC

Description of problem (please be detailed as possible and provide log
snippests):

As of 4.7 , the flexible scaling feature gets enabled by default if there is no availability zone:

"
The flexible scaling feature gets enabled on creating a storage cluster with 3 or more nodes spread across fewer than the minimum requirement of 3 availability zones. This feature is available only for the new deployments of OpenShift Container Storage 4.7 clusters and does not support the upgraded clusters. For information about flexible scaling, see Scaling Storage Guide
"

This feature causes the failure domain  set to "hosts", however it is very common requirement at private datacenters to have the failure domain set to "rack" for the data redundancy.

We can explicitly set the "flexibleScaling: false" during OCS instance creation if we use cli based installation and the failure domain is set to rack as expected. It would be nice to have this feature configurable at UI as well even if there is no availablity zone. 


Version of all relevant components (if applicable):
4.9

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
If the user has no deep knowledge about OCS internals, they can end up with wrong hierarchy. 


Is there any workaround available to the best of your knowledge?
Yes.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes