James Gauld observed that the recent addition of CPUShares and CPUQuota
settings has excessively throttled the sysinv-agent during configuration
tasks.
The change can be viewed here:
https://review.opendev.org/c/starlingx/config/+/932556
The intent behind the CPUQuota setting was to smooth out occasional CPU
spikes, which is manageable when low latency isn't a priority.
However, during critical configuration tasks—such as fresh installations
of an AIO-DX/Standard or DC system controller
—the sysinv-agent operates at high CPU usage for extended periods.
Under these conditions, the quota setting significantly hampers
performance, extending the time required for these operations.
The CPUQuota/AllowedCPU were removed in the review:
https://review.opendev.org/c/starlingx/config/+/933603
In a recent test configuring a DC with a single subcloud, errors were
observed due to the extended time required to apply the Puppet code
(approximately 1000 seconds to execute a runtime manifest).
As a result, the CPUShares configuration will now also be removed.
Partial-Bug: 2084714
Tests:
DC system with one AIO-SX subcloud
Change-Id: I1f0ae17542e987a54835a26fb7b71152402f9c0b
Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com>
bc6637cbf2