Support pinning container to specific CPU cores
This blueprint shall build on the existing container fields and add a cpu_policy field during the container creation. cpu_policy could be shared or dedicated.
Blueprint information
- Status:
- Complete
- Approver:
- hongbin
- Priority:
- Medium
- Drafter:
- Sudipta Biswas
- Direction:
- Approved
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- hongbin
- Completed by
- hongbin
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
add the cpuset to container object
Addressed by: https:/
add cpuset to the docker driver
UPDATE1: As discussed at IRC/team meeting, we proposed to expose a parameter 'cpu_policy' instead. 'cpu_policy' could be 'shared' or 'dedicated'. At the backend, the Docker driver could choose to implement 'dedicated' using --cpuset option. The team requires a spec for this feature. Take a look at Nova spec for reference: https:/
-- hongbin 2017-01-28
Addressed by: https:/
Introduce host capabilities and cpusets
Addressed by: https:/
Introduce os-capability parsing
Addressed by: https:/
Introduce numa related objects
Addressed by: https:/
[WIP] Add ComputeNode Tracker
Addressed by: https:/
host inventory as a periodic task
Addressed by: https:/
Support cpuset and scheduler for cpuset
Addressed by: https:/
Support cpuset and scheduler for cpuset
Addressed by: https:/
[WIP] Add 'enable_
Work Items
Dependency tree
* Blueprints in grey have been implemented.
