Bug 1566927 - [RFE] Autoscale Overcloud VM-based OCP on OSP
Summary: [RFE] Autoscale Overcloud VM-based OCP on OSP
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Tomas Sedovic
QA Contact: weiwei jiang
Depends On: 1566424 1566431
TreeView+ depends on / blocked
Reported: 2018-04-13 07:52 UTC by Tomas Sedovic
Modified: 2019-06-12 11:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-12 11:57:03 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Tomas Sedovic 2018-04-13 07:52:59 UTC
Define metrics that will drive scaling up and down of the OpenShift app nodes.

Set up the OpenShift/Kubernetes autoscaler to monitor and scale the OCP cluster using the scale-up and scale-down playbooks.

Update openshift-ansible to optionally deploy and configure this autoscaler.

Comment 2 Kirsten Newcomer 2019-06-12 11:57:03 UTC
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.

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