neutron

Commit Graph

Author	SHA1	Message	Date
Darragh O'Reilly	540d00f68e	Make OVS controller inactivity_probe configurable This parameter applies to the OVSDB Controller table when the native openflow driver is used. There are reports that increasing it can reduce errors on busy systems. This patch also sets the default value to 10s which is more than the OVS default of 5s. See the ovs-vswitchd.conf.db man page for full description. Change-Id: If0d42919412dac75deb4d7f484c42cea630fbc59 Partial-Bug: #1817022	4 years ago
Slawek Kaplonski	beb2f2ef15	Fix handling no qos_queues while removing min bw limit rule When ovs L2 agent is removing qos minimum bandwidth rules for port, it may happen that qos_queues for this port will not be found. Such case should be handled properly to not raise AttributeError when trying to call "keys()" method on None object. Change-Id: Ic76bf41983e021919ab0a6ffcf0fdcfd45c935ee	4 years ago
Rodolfo Alonso Hernandez	92f1281b69	Add a more robust method to check OVSDB values in BaseOVSTestCase Sometimes, when the OVSDB is too loaded (that could happen during the functional tests), there is a delay between the OVSDB post transaction end and when the register (new or updated) can be read. Although this is something that should not happen (considering the OVSDB is transactional), tests should deal with this inconvenience and provide a robust method to retrieve a value and at the same time check the value. This new method should provide a retrieving mechanism to read again the value in case of discordance. In order to solve the gate problem ASAP, another bug is fixed in this patch: to skip the QoS removal when OVS agent is initialized during funtional tests When executing functional tests, several OVS QoS policies specific for minimum bandwidth rules [1]. Because during the functional tests execution several threads can create more than one minimum bandwidth QoS policy (something in a production environment cannot happen), the OVS QoS driver must skip the execution of [2] to avoid removing other QoS created in parellel in other tests. This patch is marking as unstable "test_min_bw_qos_policy_rule_lifecycle" and "test_bw_limit_qos_port_removed". Those tests will be investigated once the CI gates are stable. [1] Those QoS policies are created only to hold minimum bandwidth rules. Those policies are marked with: external_ids: {'_type'='minimum_bandwidth'} [2] `d6fba30781/neutron/plugins/ml2/drivers/openvswitch/agent/extension_drivers/qos_driver.py (L43)` Closes-Bug: #1818613 Closes-Bug: #1818859 Related-Bug: #1819125 Change-Id: Ia725cc1b36bc3630d2891f86f76b13c16f6cc37c	4 years ago
Rodolfo Alonso Hernandez	cc8808d539	Add QoS minimum egress bandwidth rule into ovs-agent Add minimum egress bandwidth support for Open vSwitch. The scope of this implementation is reduced to N/S traffic. There is no QoS applied on traffic between VMs. The QoS rules are aplied to exit ports in bridges other than br-int; that means all physical bridges. No tunneled traffic will be shaped. This feature will be implemented in a following patch. Partial-Bug: #1560963 Change-Id: I0a2ef52b13151a39e678e9a3e6f75babb47298d0	4 years ago

4 Commits (1c2e10f8595d2286bd9bec513bc5a346a84a6f7c)