Bug 1608271
Summary: | Support lvm cache for thickpool configuration | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | bipin <bshetty> |
Component: | gdeploy | Assignee: | Sachidananda Urs <surs> |
Status: | CLOSED WONTFIX | QA Contact: | SATHEESARAN <sasundar> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhhiv-1.5 | CC: | bshetty, bugs, fhirtz, rhs-bugs, sabose, sankarshan, sasundar, smohan, storage-qa-internal, vdas |
Target Milestone: | --- | Keywords: | ZStream |
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: | 1608268 | Environment: | |
Last Closed: | 2018-10-22 06:01:37 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: | 1608268 |
Description
bipin
2018-07-25 08:47:06 UTC
Can you please paste the complete config file? Moving this bug out of 3.4.0 as this doesn't meet blocker criteria. This can be re-proposed for 3.4.0 if required. The case differs only in the place where the cachepool LV is attached to the OriginLV. With thinpool - Cachepool LV is attached to the VG/thinpool non-thinpool - Cachepool LV is attached to the VG/origin_lv To enable support for this request, the parameter 'poolname' should be made optional and one more parameter 'origin_lv' should be made available. These 2 parameters 'poolname' & 'origin_lv' should be mutually exclusive, which means only one of them should be available. If this param 'poolname' is available, attach cachepool to VG/thinpool, else look for param 'origin_lv' and attach cache to 'VG/origin_lv' Let me also furnish the steps used to create the lvmcache which could also enabled the understandig. Variables ------------ SSD - /dev/sdc ( say 225G ) HDD - /dev/sdb VG name - gluster_vg_sdb With thinpool ------------- thinpool name - gluster_thinpool_sdb 1. Add the SSD to the VG # vgextend gluster_vg_sdb /dev/sdc 2. Create 'cachelv' # lvcreate -n cachelv -L 220G vg1 /dev/sdc 3. Create 'cachepool' # lvconvert --type cache-pool vg1/cachelv 4. Attach the 'cachepool' to the thinpool # lvconvert --type cache vg1/cachelv vg1/gluster_thinpool_sdb Without thinpool (ie.) with thick LVs ------------------------------------- Let's say one of the thick LV name is 'lv1' 1. Add the SSD to the VG # vgextend gluster_vg_sdb /dev/sdc 2. Create 'cachelv' # lvcreate -n cachelv -L 220G vg1 /dev/sdc 3. Create 'cachepool' # lvconvert --type cache-pool vg1/cachelv 4. Attach the 'cachepool' to the thick LV ( as per requirement ) # lvconvert --type cache vg1/cachelv vg1/lv1 @sas @bipin we are not planning to do this in gdeploy but will be taking care of this in gluster-ansible. I'll be closing this bug, feel free to reopen if you want this feature in gdeploy. |