Bug 1523589

Summary:	[RFE] provide a way for the user to setup-cache
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sahina Bose <sabose>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhhi-1.1	CC:	bugs, godas, knarra, lbailey, rcyriac, rhs-bugs, sabose, sasundar
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHHI-V 1.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Administrators can now select a faster device to use as a cache when configuring a brick for RHHI for Virtualization. This enables better performance when using hard disk drives as bricks.	Story Points:	---
Clone Of:	1415179	Environment:
Last Closed:	2018-11-08 05:37:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1415179
Bug Blocks:	1520833

Description Sahina Bose 2017-12-08 11:05:50 UTC

+++ This bug was initially created as a clone of Bug #1415179 +++

Description of problem:
As of now user does not have a way to setup-cache using gluster deployment wizard. Provide a way for the user to setup cache.

Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard-0.10.7-0.0.3.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
There is no way for the user to setup-cache using 'gluster deployment wizard'

Expected results:
Provide a way for the user to setup-cache using gluter deployment wizard.

Additional info:

--- Additional comment from Ramesh N on 2017-03-16 04:50:32 EDT ---

Comment 3 SATHEESARAN 2018-04-04 11:43:06 UTC

Tested with RHV 4.2.2-6 and cockpit-ovirt-dashboard-0.11.19

Cockpit provides the enhancement that enabled to setup lvmcache per host.

Comment 8 errata-xmlrpc 2018-11-08 05:37:25 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/RHEA-2018:3523