neutron

History

Zachary 40a811bea4 [Qos] Fix residues of ovs in ingress bw limit When we delete vm port with attached QoS policy, it is just doing nothing if vif_port does not exist. This is fine for egress bandwidth limit as it is configured directly on vif_port in OVS. For ingress bw limit however it uses additional records in Openvswitch database: qos and queue. Those records are not cleaned up in such case. This patch also records port in self.ports in the case of bandwidth limit rules, just as in the case of dscp rules. Never execute port clear if vif_port not exists. Finally, ovs driver can clean such qos and queue records Change-Id: Iddeb49e1e6538a178ca468df0fdf9e0617ca4f1c Closes-Bug: #1726732 (cherry picked from commit `ee423e1fa0`)	2017-12-06 15:37:43 +08:00
..
__init__.py	Add unit tests and fixes for OVS Agent QoS Extension Driver	2015-07-15 15:23:59 +03:00
test_qos_driver.py	[Qos] Fix residues of ovs in ingress bw limit	2017-12-06 15:37:43 +08:00

Zachary 40a811bea4 [Qos] Fix residues of ovs in ingress bw limit

When we delete vm port with attached QoS policy,
it is just doing nothing if vif_port does not exist.

This is fine for egress bandwidth limit as it is configured
directly on vif_port in OVS.

For ingress bw limit however it uses additional records in
Openvswitch database: qos and queue. Those records are not
cleaned up in such case.

This patch also records port in self.ports in the case of
bandwidth limit rules, just as in the case of dscp rules.
Never execute port clear if vif_port not exists. Finally, ovs
driver can clean such qos and queue records

Change-Id: Iddeb49e1e6538a178ca468df0fdf9e0617ca4f1c
Closes-Bug: #1726732
(cherry picked from commit ee423e1fa0)

2017-12-06 15:37:43 +08:00

__init__.py Add unit tests and fixes for OVS Agent QoS Extension Driver 2015-07-15 15:23:59 +03:00

test_qos_driver.py [Qos] Fix residues of ovs in ingress bw limit 2017-12-06 15:37:43 +08:00