Allow instance-ingress bandwidth limiting

Registered by Armando Migliaccio on 2016-04-14

The current implementation of bandwidth limiting rules only supports egress bandwidth
limiting. There are cases where ingress bandwidth limiting is more important than
egress limiting, for example when the workload of the cloud is mostly a consumer of data (crawlers, datamining, etc), and administrators need to ensure other workloads won't be affected.

Blueprint information

Status:
Complete
Approver:
Miguel Angel Ajo
Priority:
Low
Drafter:
Slawek Kaplonski
Direction:
Approved
Assignee:
Slawek Kaplonski
Definition:
Approved
Series goal:
Accepted for pike
Implementation:
Implemented
Milestone target:
milestone icon pike-2
Started by
Kevin Benton on 2017-04-28
Completed by
Ihar Hrachyshka on 2017-07-12

Related branches

Sprints

Whiteboard

Oct-31-2016(armax): Waiting on QoS driver refactor ( https://review.openstack.org/351858 )

Sep-08-2016(armax): deferred to Ocata

Aug-02-2016(mangelajo): Improved qos rule validation is being prioritized in front of this, since this is partly dependent on the other blueprint.
Apr-14-2016(armax): RFE approved.

Gerrit topic: https://review.openstack.org/#q,topic:add-rule-to-delete-handler,n,z

Addressed by: https://review.openstack.org/466899
    Extend QoS L2 drivers interface to handle ingress rule types

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.