Strict minimum bandwidth support (scheduling aware)
Newton release added minimum bandwidth support to QoS policy
rules. While this improvement works at the hypervisor level,
it's a best effort measure that will not prevent oversusbcription
on a specific network link bandwidth (When SUM i port[i].min_bw >
max available bandwidth within a provider network).
NFV/Telcos are interested in this type of rules to make sure
functions don't over commit compute nodes.
CSPs could make use of this feature to provide bandwidth
guarantees for streaming.
Blueprint information
- Status:
- Complete
- Approver:
- Slawek Kaplonski
- Priority:
- High
- Drafter:
- Miguel Angel Ajo
- Direction:
- Needs approval
- Assignee:
- Bence Romsics
- Definition:
- Approved
- Series goal:
- Accepted for stein
- Implementation:
- Implemented
- Milestone target:
- stein-3
- Started by
- Miguel Lavalle
- Completed by
- Bence Romsics
Related branches
Related bugs
Sprints
Whiteboard
https:/
Gerrit topic: https:/
Addressed by: https:/
Add a spec for strict minimum bandwidth support
Oct-13-2017 (mlavalle): Follow up spec to detail minimum bandwidth allocation in Placement API
Work Items
Dependency tree
* Blueprints in grey have been implemented.