Bug 1398278 - [RFE] fully automated pod idling. [NEEDINFO]
Summary: [RFE] fully automated pod idling.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 11:37 UTC by Vladislav Walek
Modified: 2021-06-10 11:42 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-18 19:50:27 UTC
Target Upstream Version:
vwalek: needinfo? (bbennett)
acomabon: needinfo? (bbennett)


Attachments (Terms of Use)

Description Vladislav Walek 2016-11-24 11:37:48 UTC
Description of problem:

Our OSE 2 cluster (aka ITOS) currently uses the idling features to auto-idle projects which aren't being used, which helps to reduce the 'wasted' resources when users forget about old projects/toys.

With OSE3 this originally went away.  The new idling feature in OSCP 3.3 is a good step back in the right direction and allows us to apply a little gaffertape and construct something to vaguely replicate the old OSE2 feature.

This RFE is for the remaining piece of the puzzle which is for the product to add the necessary automation pieces so that when using the default HAProxy routers we can set an 'auto-idle' timeout, and have this as a supported feature rather than a home-brew script.

See https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html/Deployment_Guide/Automated_Gear_Idling.html for the level of simplicity we'd like...

Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.3.0

Comment 7 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.


Note You need to log in before you can comment on or make changes to this bug.