AIO System Controller CPU assignment changes required
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Jim Gauld |
Bug Description
Brief Description
-----------------
The following changes are required for an AIO running as a DC system controller
- All cores are assigned as platform cores
- kubelet, same config options as a standard controller
Severity
--------
Major: System/Feature is usable but degraded
Steps to Reproduce
------------------
Launch AIO with DC system controller.
Expected Behavior
------------------
Desire all sysinv managed cores have 'Platform' function. This implies CPU affinity of the platform and kubernetes processes float across all logical cpus and numa nodes. The kubelet process should have CPU manager policy 'none' with no reserved cpus.
Actual Behavior
----------------
Only 2 cores from numa node 0 are assigned 'Platform' function, so this system is highly constrained since the CPU affinity of processes are limited to these cores. The kubelet process has CPU manager policy 'non' with reserved cpus.
Reproducibility
---------------
Reproducible.
System Configuration
-------
AIO DC System controller.
Branch/Pull Time/Commit
-------
NA.
Last Pass
---------
no, this is day one issue
Timestamp/Logs
--------------
NA.
Test Activity
-------------
Other - System scaleability engineering.
Changed in starlingx: | |
assignee: | nobody → Jim Gauld (jgauld) |
tags: | added: stx.distcloud |
tags: | added: in-r-stx30 |
Fix proposed to branch: master /review. opendev. org/698321
Review: https:/