Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1554242

Summary:	Problem attaching lvmcache to thinpool
Product:	[oVirt] cockpit-ovirt	Reporter:	SATHEESARAN <sasundar>
Component:	Gdeploy	Assignee:	Parth Dhanjal <dparth>
Status:	CLOSED DEFERRED	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	0.11.12	CC:	bugs, godas, rhs-bugs, sabose
Target Milestone:	---	Flags:	sbonazzo: ovirt-4.3-
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1554241	Environment:
Last Closed:	2019-11-21 06:36:48 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:
Bug Blocks:	1554241

Description SATHEESARAN 2018-03-12 08:41:54 UTC

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

Description of problem:
-----------------------
With the current implementation ( with asymmetric brick configuration ), there could separate thinpools for each device. But lvmcache could be attached to only one thinpool. Need to have a clarity on this. 

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
ovirt-cockpit-dashboard-0.11.14

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Start RHHI installation via cockpit
2. For 'host1', select 'sdb' for vmstore volume brick and select 'sdc' for data volume brick
3. Enable lvmcache

Actual results:
---------------
lvmcache is attached to one of the thinpool on one of the device 

Expected results:
-----------------
All the bricks ( XFS filesystems ) should able to make use of lvmcache 

Additional info:
----------------
There are 2 options possible. 
1. SSD could be partitioned and could act as lvmcache for each of the thinpool or 
2. one thinpool needs to be created out of multiple devices. 

But the latter approach is against the perf recommendation for RHGS, where 1 Disk -> 1 PV -> 1 VG -> 1 thinpool -> lv is preferred

Comment 1 Gobinda Das 2018-12-03 11:42:10 UTC

Parth please consider this during ansible role integration.

Comment 2 Sandro Bonazzola 2019-01-28 09:43:36 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 3 Gobinda Das 2019-11-21 06:36:48 UTC

Closing as dependent bug closed.