Runtime aware scheduling
As discussed at OpenStack Vancouver Summit, we don't want to schedule kata container and runc container to the same compute host because there are security concerns that the runc container might impact the security of the hosting environment of kata.
To address this concern, consider the following approach:
* Allow each compute node to declare a list of container runtimes they support
* Add a runtime filter to match the container to the right host that supports the requested runtime
Blueprint information
- Status:
- Complete
- Approver:
- hongbin
- Priority:
- High
- Drafter:
- hongbin
- Direction:
- Approved
- Assignee:
- feng.shengqin@zte.com.cn
- Definition:
- New
- Series goal:
- Accepted for stein
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- feng.shengqin@zte.com.cn
- Completed by
- feng.shengqin@zte.com.cn
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Runtime aware scheduling
Addressed by: https:/
Runtime aware scheduling
Addressed by: https:/
enable RuntimeFilter
Addressed by: https:/
enable RuntimeFilter
Addressed by: https:/
Make Runtime work with capsule