Bug 1656588

Summary:	[RFE] Feature Toggles
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Ernesto Puerta <epuertat>
Component:	Ceph-Dashboard	Assignee:	Ernesto Puerta <epuertat>
Status:	CLOSED ERRATA	QA Contact:	Uday kurundwade <ukurundw>
Severity:	high	Docs Contact:	Bara Ancincova <bancinco>
Priority:	high
Version:	4.0	CC:	ceph-eng-bugs, mkasturi, pasik, tserlin
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-14.2.4	Doc Type:	Enhancement
Doc Text:	.Displaying and hiding Ceph components in Dashboard In the {product} Dashboard you can display or hide Ceph components, such as Ceph iSCSI, RBD mirroring, Ceph Block Devices, Ceph File System, or Ceph Object Gateway. This feature allows you to hide components that are not configured.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-31 12:45:35 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:	1730176
Deadline:	2018-12-21

Description Ernesto Puerta 2018-12-05 19:05:51 UTC

Provides support for disabling/enabling features from the Ceph-dashboard by means of configuration changes.

In this context features should be primarily considered from UI perspective and include at least:
Single components (e.g.: iSCSI)
Optionally: Sets of related components (e.g: RBD comprising Images, Mirroring & iSCSI). This could also be enabled/disabled on a per-component basis.
Takes precedence over Role Based Authorization: features are either enabled/disabled for all users.
No need for an instant effect: a Ceph-mgr or module reload could happen if needed. However, no code changes or builds should be needed.
No need to disable back-end functionality too.

Comment 3 Ernesto Puerta 2018-12-12 17:56:03 UTC

Take

Comment 21 errata-xmlrpc 2020-01-31 12:45:35 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, 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:0312