Bug 1325854 - [RFE] gdeploy to allow adding lvmcache to thinpool if SSD is available on server
Summary: [RFE] gdeploy to allow adding lvmcache to thinpool if SSD is available on server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHGS 3.1.3
Assignee: Sachidananda Urs
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: Gluster-HC-1 1311817
TreeView+ depends on / blocked
 
Reported: 2016-04-11 11:10 UTC by Sahina Bose
Modified: 2016-06-23 05:29 UTC (History)
5 users (show)

Fixed In Version: gdeploy-2.0-5
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 05:29:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1250 0 normal SHIPPED_LIVE gdeploy update for Red Hat Gluster Storage 3.1 update 3 2016-06-23 09:11:59 UTC

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

If SSD devices are available on server, it should be possible to use this device as lvmcache and attach it to a thinpool device.

gdeploy should provide the user the flexibility to configure this as part of brick provisioning

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

How reproducible:
NA
Comment 3 SATHEESARAN 2016-05-11 10:30:36 UTC 
lvs section has got a action 'setup-cache' which setups the dm-cache

[lvs]
action=setup-cache
ssd=sdc
poolname=lvpool1
vgname=rhgs_vg1
cache_lvsize=10GB

the above section helps in the creation of dm-cache ( lvmcache ) if ssd is available
Comment 5 errata-xmlrpc 2016-06-23 05:29:49 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
Note You need to log in before you can comment on or make changes to this bug.