Bug 1515299

Summary:	[RFE] Support multiple bricks per storage device
Product:	[oVirt] ovirt-engine	Reporter:	Sahina Bose <sabose>
Component:	BLL.Gluster	Assignee:	Kaustav Majumder <kmajumde>
Status:	CLOSED DUPLICATE	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.1.7.3	CC:	bugs, dfediuck
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature
Target Release:	---	Flags:	rule-engine: ovirt-4.4? ylavi: planning_ack+ sabose: devel_ack? sabose: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1523613 (view as bug list)		Environment:
Last Closed:	2019-04-23 07:21:51 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:	1539636
Bug Blocks:	1523613

Description Sahina Bose 2017-11-20 14:24:04 UTC

Description of problem:

oVirt supports creation of bricks from storage devices on host. However, this is restricted to creation of a single brick per device.
This request is to enhance the brick creation feature such that user can
1. Create multiple bricks per storage device on host. Multiple logical volumes are created from a single device where the logical volumes can either be thinly provisioned volumes or not.
2. Allow attaching lvmcache device to thinpool in case of thinly provisioned volumes or to the thick provisioned LV. 

Version-Release number of selected component (if applicable):


How reproducible:
NA

Steps to Reproduce:
NA

Comment 1 Sahina Bose 2017-11-20 14:24:58 UTC

The brick creation process should be similar to the process via cockpit-gdeploy plugin

Comment 2 Sahina Bose 2018-01-29 11:16:06 UTC

Changing this bug to reflect point 1 mentioned in Comment 0.
Bug 1539636 is logged to track the lvmcache configuration

Comment 3 Sahina Bose 2019-04-23 07:21:51 UTC


*** This bug has been marked as a duplicate of bug 1470954 ***