Resource Management Daemon - Base Enablement
Currently Nova only provides static allocation of hardware resources when an instance like VM is scheduled with no concept of local node monitoring and fine tuning of a subset of hardware resources that can help improve or maintain the performance.
OpenStack workloads can benefit from the Resource Management Daemon (RMD) when deployed on a compute node and RMD can extend the capabilities of a hypervisor like Libvirt to provide more than static allocation of resources using its plugins.
We propose a solution for OpenStack Nova to leverage the RMD to manage a subset of host resources traditionally not visible to Nova. These are resources that shall allow more fine grain resource control for more predictable performance. This will require running RMD on the compute nodes along with RMD plugins to interface each resource it supports and modifying Nova Compute.
The integration between OpenStack and RMD require the following two changes in Nova Compute:
* Enabling a path between Nova Compute and RMD that allows Nova Compute to query the inventory of resources managed by RMD, and to delegate resource allocation requests to RMD. The OpenStack flavor determines as always eligible hosts and the amount and types of the various resources being requested for an instance.
* Enabling a path from Nova Compute to Placement API to update resource inventory information obtained from RMD.
The details for enabling specific platform resource through RMD Openstack integration and RMD resource plugins will be covered in a separate spec.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Dakshina Ilangovan
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Eric Fried
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Implements: blueprint nova-local-
Gerrit topic: https:/
Gerrit topic: https:/
[efried 20190726] This approach is superseded by provider config files in-tree (http://