Bug 1466052

Summary:	[RFE][UX] Reconfigure OpenShift on RHV hot-add CPU
Product:	OpenShift Container Platform	Reporter:	Thom Carlin <tcarlin>
Component:	RFE	Assignee:	Eric Paris <eparis>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	aos-bugs, eparis, jokerman, mmccomas, pweil, tcarlin
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:	2019-06-12 11:57:13 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:
Bug Depends On:
Bug Blocks:	1724792

Description Thom Carlin 2017-06-28 21:33:17 UTC

Description of enhancement:

With later version of Docker, hot-adding CPU(s) is detected and Docker adjusts automatically.  Enhancement request is for OpenShift to similarly adjust.

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

3.5.0

Additional info:

Current workaround:
* systemctl restart atomic-openshift-node

We encountered this when deploying pods on nodes using default values.  Some pods went into PENDING due to Insufficient pods.

"oc describe nodes" can be used to see the current values and pods running on that node.

"docker info" is similarly used to see its current values

Comment 1 Paul Weil 2017-06-29 14:51:42 UTC

Thom,  Can you provide some more details here?  What, exactly, would you like to adjust within OpenShift?

Comment 2 Thom Carlin 2017-06-29 15:56:50 UTC

For example, by default a node allows 10 x number_of_cpus as the capacity/allocatable (e.g. for 2 CPUs, only 20 pods are allowed to run).  We reached that limit of non-terminated pods

I added more CPUs to the VM running the OpenShift node (e.g. 4):
* The CPUs were visible from RHEL
* Docker also detected the change
* OpenShift did not -- instead, I needed to restart the service for the limit to change

The RFE is for OpenShift to detect and adjust on the fly without user intervention.

It is important to note this would apply for *any* CPU-derived parameters, not just the example I used.

Comment 3 Paul Weil 2017-06-30 07:30:38 UTC

Thanks Thom.  I suspect, also, that someone would want to opt in to this behavior.  For instance I should be able to have my value honored if I want to limit capacity or want to reserve resources for non-OpenShift items.

Comment 4 Thom Carlin 2017-06-30 11:39:21 UTC

Paul, I'm unclear if the default should be opt-in or opt-out.  However, the end-user having the freedom to select (especially for NUMA) is a great point.

Comment 6 Kirsten Newcomer 2019-06-12 11:57:13 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.