Strict minimum bandwidth support (scheduling aware)

Registered by Miguel Angel Ajo on 2016-11-16

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:
milestone icon stein-3
Started by
Miguel Lavalle on 2018-07-28
Completed by
Bence Romsics on 2019-05-03

Related branches

Sprints

Whiteboard

https://github.com/openstack/neutron/blob/master/CONTRIBUTING.rst

Gerrit topic: https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api

Addressed by: https://review.openstack.org/396297
    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.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.