Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: qos
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1787793
Title:
Does not support shared N-S qos per-tenant
Status in neutron:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1787793/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
