[RFE] Does not support shared N-S qos per-tenant
Bug #1787793 reported by
Na Zhu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Wishlist
|
Unassigned |
Bug Description
The data center N-S bandwidth is bought from ISP, so it is alwawys limited and need charge when tenant use it.
For example, when tenant associate floatingip to port, he need select the floatingip bandwidth size he wants to use and need pay the bandwidth. Besides floatingip, the ipsec vpn also consumption N-S bandwidth. To save money, the tenant want the cloud provider can support floatingip and ipsec vpn shared one bandwidth, because sometimes the floatingip flow is large and sometimes the ipsec vpn flow is large, if the two share one bandwidth, he just need pay one bandwidth, which size can be less than 2 bandwidth.
summary: |
- Does not support shared N-S qos per-tenant + [RFE] Does not support shared N-S qos per-tenant |
tags: | added: rfe |
tags: |
added: rfe-approved removed: rfe-triaged |
To post a comment you must log in.
First of all, QoS for VPN traffic is not implemented yet so we can't "share" bandwidth between FIP and VPN traffic for now :)
You can apply QoS policy with limit to port directly - then it will be shared between different types of traffic but I can understand that it's not exactly what You have in mind.