Bug 1561799

Summary: ability to specify storage class for elasticsearch metrics
Product: OpenShift Container Platform Reporter: Greg Rodriguez II <grodrigu>
Component: RFEAssignee: Paul Weil <pweil>
Status: CLOSED DUPLICATE QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.7.1CC: anli, aos-bugs, jokerman, mmccomas, mmckinst
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 02:24:17 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 Greg Rodriguez II 2018-03-29 00:10:11 UTC 
Description of problem:
Customer uses AWS with multiple storage classes, efs and gp2 with efs configured to be default.  When deploying metrics, it will be deployed on efs by default because there is no option to specify what storage class to use.  The customer wants it deployed on gp2.
Customer modified the ansible playbook to specify the storage class.  They feel this was an unnecessary step and would like it implemented as a feature.  
See for more details: https://github.com/openshift/openshift-ansible/compare/release-3.7...mmckinst:storage_class?expand=1

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

How reproducible:
Customer verified

Steps to Reproduce:
See https://github.com/openshift/openshift-ansible/compare/release-3.7...mmckinst:storage_class?expand=1 for details provided by customer

Actual results:
Had to alter playbook to specify storage class

Expected results:
Would prefer this be a feature asking to specify

Additional info:
https://github.com/openshift/openshift-ansible/compare/release-3.7...mmckinst:storage_class?expand=1
Comment 1 Anping Li 2018-03-29 02:24:17 UTC 

*** This bug has been marked as a duplicate of bug 1522388 ***
Comment 2 Anping Li 2018-04-19 02:10:48 UTC 

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