Bug 1403010

Summary: [RFE] Specify a PV for the metrics deployer to use for the PVC
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: RFEAssignee: Matt Wringe <mwringe>
Status: CLOSED CURRENTRELEASE QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.1CC: aos-bugs, erjones, jokerman, mbarrett, mmccomas
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-12 13:54:36 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:

Description Eric Jones 2016-12-08 21:22:50 UTC
- What is the nature and description of the request? 
As an admin I require the ability to deploy metrics and know exactly which of my PersistentVolumes it is going to use.

- Why does the customer need this? (List the business requirements here) 
Because currently if you want to have persistent storage, the metrics deployer will simply deploy a PVC that will bind to whatever PV matches it's needs, even if you have multiple PVs that meet those qualifications but aren't the one you want it to use.

- How would the customer like to achieve this? (List the functional requirements here) 
Take advantage of the Selector-label volume binding [0] if we need

[0] https://docs.openshift.com/container-platform/3.3/install_config/persistent_storage/selector_label_binding.html

- Is there already an existing RFE upstream or in Red Hat Bugzilla?
Unable to locate one.

Comment 3 Eric Rich 2018-03-12 13:54:36 UTC
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.