Bug 1376473

Summary: [RFE] Extend gdeploy functionality to support other medium term features of HC
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: gdeployAssignee: Sachidananda Urs <surs>
Status: CLOSED WONTFIX QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: rhinduja, rhs-bugs, smohan, storage-qa-internal
Target Milestone: ---Keywords: FutureFeature
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: Environment:
Last Closed: 2018-03-27 08:06:42 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:
Embargoed:

Description SATHEESARAN 2016-09-15 13:52:57 UTC 
Description of problem:
------------------------
This bug is continuation of the bug BZ1356296, which was initially raised to accomodate short term goals as well as medium term goals.

short-term goals are worked on with RHGS 3.2.0, where as the medium term goals are tracked as part of this bug

Medium term 6-9 months
- support gluster based tiering in addition to lvmcache
- automatically configure the lvmcache lv sizes instead of having them hard-coded by the admin in the conf file - still support current settings as an override, but the tool should make some sensible default choices, based on device size.

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

How reproducible:
------------------
NA

Steps to Reproduce:
-------------------
NA

Actual results:
---------------
NA

Expected results:
-----------------
gdeploy should provide the features as mentioned in the description of this bug

Additional info:
-----------------
see also https://bugzilla.redhat.com/show_bug.cgi?id=1356296#c4
Comment 1 Sachidananda Urs 2018-03-27 08:06:42 UTC 
Will be fixed in gluster-ansible. The issue is tracked at:

https://github.com/gluster/gluster-ansible/issues/29