Hi All,

I have been experimenting with Openvswitch and QoS. I have a question regarding 
how an existing QoS configuration on a port is removed.

I setup QoS on an existing port with the following command

sudo ovs-vsctl -- set Port $IF_NAME qos=@newqos -- \
    --id=@newqos create QoS type=linux-htb other-config:max-rate=4000000 
queues=0=@q0 -- \
    --id=@q0 create Queue other-config:min-rate=4000000 
other-config:max-rate=4000000

This gives me the _uuid of both the QoS and Queue entry

0b62cfb0-c335-45ca-8910-ca4030ea13af
24ff16d8-926e-4c12-aad8-b7b06c6ec575

When I send traffic I can see that QoS is indeed configured.

I then remove the QoS configuration on the port with the following command

sudo ovs-vsctl clear Port $IF_NAME qos

I can see that QoS is no longer active on the port as the throughput is no 
longer being limited.

However when I check the database to see if QoS has been removed the QoS table 
entry is still present along with the queue entry.

sudo ovs-vsctl list qos
_uuid               : 0b62cfb0-c335-45ca-8910-ca4030ea13af
external_ids        : {}
other_config        : {max-rate="4000000"}
queues              : {0=24ff16d8-926e-4c12-aad8-b7b06c6ec575}
type                : linux-htb

To remove these entries I have to complete an additional step as follows for 
both QoS and queue

sudo ovs-vsctl  --  destroy  qos 0b62cfb0-c335-45ca-8910-ca4030ea13af
sudo ovs-vsctl  --  destroy  queue 24ff16d8-926e-4c12-aad8-b7b06c6ec575

Previously I assumed that clearing QoS from the port with my first command 
would automatically clear the database QoS entry as well but it would seem that 
this is not the case. Is this behavior expected?

I have also seen similar behavior if I destroy the QoS record first. Although 
the record will no longer be in the database it seems that the port is still 
configured for QoS until I call clear Port $IF_NAME qos.

Appreciate any insight on this.

Thanks
Ian Stokes
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to