[REC-64] Verify CPU pinning Created: 18/Sep/19  Updated: 15/Oct/19

Status: To Do
Project: Radio Edge Cloud
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Medium
Reporter: kinkwan tsui Assignee: Cynthia Billovits
Resolution: Unresolved Votes: 0
Labels: FunctionalTest, TestCase
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

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



 Comments   
Comment by Ferenc Tóth [ 15/Oct/19 ]

TC1: ok

TC2: ok

TC3: the whole CaaS subsystem is using the default pool, so it must work. I don't see a reason to test it separately.

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...

Comment by Deepak Kataria [ 14/Oct/19 ]

https://github.com/nokia/CPU-Pooler/blob/master/README.md

The link above provides additional detail and examples.

Comment by Deepak Kataria [ 14/Oct/19 ]

TC1: Test CPU allocation from exclusive pool.  This is for testing CPU allocation for latency-sensitive containers requiring exclusive access.

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.

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.

TC4: Test CPU allocation using cpuset

TC5: Test CPU allocation using POD annotation

TC6: Test CPU allocation using environment variables (e.g., EXCLUSIVE_CPUS, SHARED_CPUS)

TC7: Test mapping an application process running within a container to a particular CPU allocated for the container

Generated at Sat Feb 10 06:04:48 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.