Bug 1325828

Summary: [RFE] gdeploy to allow multiple LV creation from single physical block device
Product: Red Hat Gluster Storage Reporter: Sahina Bose <sabose>
Component: gdeployAssignee: Sachidananda Urs <surs>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.1CC: asrivast, nvarma, rcyriac, rhinduja, sasundar
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: RHGS 3.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gdeploy-2.0-5 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-23 05:29:43 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:
Bug Depends On:    
Bug Blocks: 1258386, 1311817    

Description Sahina Bose 2016-04-11 10:22:58 UTC 
Description of problem:

For HC use case, each server may have only one physical block device (for instance, a RAID6 LUN).
It should be possible to create multiple LVs (thick or thin) from one single PV using gdeploy configuration

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


How reproducible:
NA
Comment 4 SATHEESARAN 2016-05-11 10:28:23 UTC 
Tested with gdeploy-2.0-11

The thick volume could be create with the 'lvtype=thick'
Also there could be multiple lvs created out of a thinpool using 'lvs' section

[lvs]
action=create
lvtype=thick
vgname=rhgs_vg1

or

[lvs1]
action=create
lvtype=thinpool
poolname=lvpool1
size=40GB
vgname=rhgs_vg1

[lvs2]
action=create
lvtype=thinlv
vgname=rhgs_vg1
...

Above conf sections could be used to create thick and thin lvs together
Comment 6 errata-xmlrpc 2016-06-23 05:29:43 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-2016:1250