Bug 1371962

Summary: [RFE] visibility into, and the ability to restrict, users' disk space and I/O bandwidth usage.
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: RFEAssignee: Bradley Childs <bchilds>
Status: CLOSED DEFERRED QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.0CC: aos-bugs, bchilds, erjones, fgrosjea, jkaur, jokerman, mbarrett, mmccomas, stwalter, tkimura, tvvcox
Target Milestone: ---Keywords: Reopened
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-08-31 14:26:30 UTC 
- What is the nature and description of the request? 
As an admin I require visibility into, and the ability to restrict, users' disk space and I/O bandwidth usage.

- Why does the customer need this? (List the business requirements here) 
Certain pods are using up so much I/O that the nodes they are on are non-functional until the pod is deleted. 

- How would the customer like to achieve this? (List the functional requirements here) 
Set limits on the projects or the pods so it doesn't use up everything available on the node.

- For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Deploy a pod (customer is seeing this with python), make it use up a lot of I/O, set limit, and check if the I/O still goes too high

- Is there already an existing RFE upstream or in Red Hat Bugzilla?
There is a trello card
https://trello.com/c/Mfi6fWG2
Comment 8 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.