[RFE] Allow instance-ingress bandwidth limiting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Slawek Kaplonski |
Bug Description
The current implementation of bandwidth limiting rules only supports egress bandwidth
limiting.
Use cases
=========
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.
Other example are CSPs which need to plan & allocate the bandwidth provided to customers, or provide different levels of network service.
API/Model impact
===============
The BandwidthLimiting rules will be added a direction field (egress/ingress), which by default will be egress to match the current behaviour and, therefore
be backward compatible.
Combining egress/ingress would be achieved by including an egress bandwidth limit and an ingress bandwidth limit.
Additional information
=======
The CLI and SDK modifications are addressed in https:/
description: | updated |
description: | updated |
description: | updated |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in neutron: | |
assignee: | nobody → Slawek Kaplonski (slaweq) |
Changed in neutron: | |
status: | In Progress → Triaged |
tags: |
added: rfe-approved removed: rfe |
Changed in neutron: | |
milestone: | none → newton-1 |
Changed in neutron: | |
status: | Triaged → In Progress |
Changed in neutron: | |
milestone: | newton-1 → newton-2 |
Changed in neutron: | |
milestone: | newton-2 → newton-3 |
Changed in neutron: | |
milestone: | newton-3 → newton-rc1 |
Changed in neutron: | |
milestone: | newton-rc1 → ocata-1 |
Changed in neutron: | |
milestone: | ocata-1 → ocata-2 |
Changed in neutron: | |
milestone: | ocata-2 → none |
Changed in neutron: | |
assignee: | Slawek Kaplonski (slaweq) → Rodolfo Alonso (rodolfo-alonso-hernandez) |
Changed in neutron: | |
assignee: | Rodolfo Alonso (rodolfo-alonso-hernandez) → Slawek Kaplonski (slaweq) |
description: | updated |
Changed in neutron: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | none → pike-3 |
no longer affects: | cloud-archive |
no longer affects: | cloud-archive/mitaka |
no longer affects: | cloud-archive/ocata |
no longer affects: | neutron (Ubuntu) |
no longer affects: | neutron (Ubuntu Xenial) |
I think it is a reasonable request. For the reference implementation with OVS, QoS mechanism with linux TC should work.