QoS minimum egress bandwidth

Registered by Rodolfo Alonso on 2016-05-18

Minimum bandwidth support (opposed to bandwidth limiting), guarantees a port minimum bandwidth when it's neighbours are consuming egress traffic and can be throttled in favor of the guaranteed port.

Strict minimum bandwidth support requires scheduling cooperation, to avoid physical interfaces overcommit. This RFE addresses only the hypervisor side of it. Scheduling cooperation will be addressed in a separate RFE [2] , this work is a pre-requisite for the 2nd step.

Blueprint information

Status:
Complete
Approver:
Ihar Hrachyshka
Priority:
Low
Drafter:
Rodolfo Alonso
Direction:
Approved
Assignee:
Rodolfo Alonso
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-rc1
Started by
Armando Migliaccio on 2016-09-13
Completed by
Armando Migliaccio on 2016-09-13

Related branches

Sprints

Whiteboard

2016-Aug-02: (mangelajo) Rodolfo is looking at the openstack-cli, since the freeze happens earlier, and it's a stopper for the new REST methods to be merged.

2016-Jul-15: (mangelajo) spec is ready (3 +2's , just needs driver's team eyes), the coding effort must continue (go rodolfo go!!, good work btw!)

RFE: https://bugs.launchpad.net/neutron/+bug/1560963
SPEC: https://review.openstack.org/#/c/316082/

2016-May-30: (mangelajo): Let's iterate over https://bugs.launchpad.net/neutron/+bug/1586056 quickly, so we define the final form of the API here based on that (minimum-egress-bandwidth rule , vs minimum-bandwidth rule with "ingress/egress" field where egress is the only allowed value for now).

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.