You're right, but beware: QoS set by tc does not survive a restart of the openvswitch service, including ones during upgrades (verified on 2.1.0.34867). We've seen this behavior at Rackspace across several OVS upgrades. We manually rebuild QoS immediately following upgrades.
-AH On Fri, May 22, 2015 at 7:52 AM, Hardik Soni <[email protected]> wrote: > Hi All, > > I went through QoS section of FAQ. > https://github.com/openvswitch/ovs/blob/master/FAQ.md#quality-of-service-qos > > As I understood, OVS doesnt implement QoS, It configures linux-QoS for the > interfaces it is handling. > If I set linux QoS using 'tc' for a given interface and attach the interface > to an OVS bridge using add-port command ovs-vsctl, will it retain the > configuration? > I want to make sure, OVS doesnt reset my pre-set linux-QoS for the interface > it is handling. > > Example. > tc qdisc add dev eth0 root tbf rate 0.5mbit burst 5kb latency 70ms peakrate > 1mbit minburst 1540 > creating a bridge br-0 > ovs-vsctl add-port br-0 eth0 > > Now, eth0 will retain the QoS set by tc. Am I right? > > Thanks, > Hardik Soni > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
