starlingx/monitoring
Code Issues Proposed changes

Add kube-cpusets tool to summarize kubernetes container cpusets

Browse Source 
This tool gathers cpuset usage information for all kubernetes
containers that are running on the current host.

With kubernetes CPUManager policy:
- 'none' -- the k8s-infra cpuset is used for all pods
- 'static' -- pods get exclusive cpuset for QoS Guaranteed or
  using isolcpus, otherwise pods inherit DefaultCPUSet.

This displays the cpusets per container and the mapping to numa nodes.
This displays the aggregate cpuset usage per system-level groupings
(i.e., platform, isolated, guaranteed, default), per numa-node.

Story: 2006999
Task: 39579

Change-Id: I7f1b12e2bbcf7d0b1606c1c948c545216ec454c5
Signed-off-by: Jim Gauld <james.gauld@windriver.com>
This commit is contained in:
Jim Gauld
2020-04-28 02:03:57 -04:00
parent f7437000c7
commit 1a5e6c4c3d
19 changed files with 1508 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
kube-cpusets/kube-cpusets/test-requirements.txt Normal file
View File

@@ -0,0 +1,11 @@
# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
hacking>=1.1.0,<=2.0.0 # Apache-2.0
coverage!=4.4,>=4.0 # Apache-2.0
mock>=2.0.0 # BSD
stestr>=1.0.0 # Apache-2.0
testtools>=2.2.0 # MIT