Akraino JIRA https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 [REC-64] Verify CPU pinning https://jira.akraino.org/browse/REC-64 Radio Edge Cloud <p>Create pods with specific CPU pinning and other CPU related enforcement as provided by CPU-pooler and verify that processes are pinned to CPU as expected</p> REC-64 Verify CPU pinning Task Medium To Do Unresolved Cynthia Billovits kinkwan tsui Wed, 18 Sep 2019 18:06:32 +0000 Tue, 15 Oct 2019 06:57:08 +0000 0 3 <p>TC1: ok</p> <p>TC2: ok</p> <p>TC3: the whole CaaS subsystem is using the default pool, so it must work. I don't see a reason to test it separately.</p> <p>TC4-7: these are not really an independent TCs, more like a sub-task of TC1. Once your Pod requests exclusive pools, you can test that environment variables are set, a process can be pinned to a core, etc...</p> <p><a href="https://github.com/nokia/CPU-Pooler/blob/master/README.md" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/nokia/CPU-Pooler/blob/master/README.md</a></p> <p><font color="#172b4d">The link above </font><font color="#172b4d">provides additional detail and examples.</font></p> <p>TC1: Test CPU allocation from exclusive pool.  This is for testing CPU allocation for latency-sensitive containers requiring exclusive access.</p> <p>TC2: Test millicpu allocation from share pool. This is for testing CPU allocation for containers that can utilize limited level of sharing, with protection from best effort workloads. 1 millicpu is equal to one thousandth of a CPU core.</p> <p>TC3: Test CPU allocation from Kubelet managed default pool. This is for testing CPU allocation from the default CPU management policy of K8s. It should be noted that the shared pool and default pool's CPU sets are distinct.</p> <p>TC4: Test CPU allocation using cpuset</p> <p>TC5: Test CPU allocation using POD annotation</p> <p>TC6: Test CPU allocation using environment variables (e.g., EXCLUSIVE_CPUS, SHARED_CPUS)</p> <p>TC7: Test mapping an application process running within a container to a particular CPU allocated for the container</p> Development Rank 0|i0024c: