[RFE]Add bandwidth_limit to vip

[zhaobo]

Currently, neutron lbaas and octavia just support connection_limit, but not bandwidth_limit. We need support it to make LB more powerful.
If no bandwidth_limit, the upstream bottleneck of vip will issue the low speed in the public cloud, eventhough the backend server is powerful.

[Michael Johnson (johnsom)]

Can you provide a little more information on this bug?

It seems like you are requesting a way to limit the bandwidth available through the load balancer, bandwidth_limit.

But then the second sentence mentions the vip being a bottleneck which implies you do not want to limit the bandwidth on the load balancer's vip.

Maybe a use case that describes your need would help this RFE?

[zhaobo (zhaobo6)]

Hi Michael, I'm so sorry for returning so late.

The description here may be so simple and looked as outsider wrote(Yes, i am. :)). I descripe this more details.

As in the real life, the upstream banding is very expensive for ISP or other organization. So if the vip is very popular for users, such as the large scale web portals. Thousands of people are free to access it. If there are some download/upload services supported, the upstream bandwith will be excessive consumped. Also, a connection may get the most of the bandwidth.So we should limit the vip bandwidth, and verify not consume the public internet bandwidth too much..

Why limit vip:

As there are many servers(backends) related with this vip. We do not need the limitation on every server's port. We only do that on the vip which is the entrance. It may more simple for cloud product, i think.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/441912

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/441912
Committed: https://git.openstack.org/cgit/openstack/octavia/commit/?id=509865dcf08d55d01453f32362cd01446f9fac0e
Submitter: Jenkins
Branch: master

commit 509865dcf08d55d01453f32362cd01446f9fac0e
Author: ZhaoBo <email address hidden>
Date: Mon Mar 6 20:13:53 2017 +0800

    Support QoS policy apply on vip port

    This spec intro to extend octavia API to accept Qos policy which created
    by users from neutron. In Octavia, we just accept the qos policy but not
    provide Qos function to the vip port of loadbalancer. This is very useful
    to adapt the changes about neutron qos in the future.

    Change-Id: Ia47da1e26106c6353eebd880138df4b57bcf9db4
    Closes-Bug: #1657090

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/octavia 1.0.0.0b1 development milestone.