b97646f665
* OVN + NDR testing is possible as of Neutron 22.0.0 (2023.1 or Antelope), see [1][2]. * Vault is added to non-OVN bundles as the tests.yaml file is shared and uses a configure step for Vault Important note: at the time of writing the OVN integration code in Neutron does not have any use for `distributed` and `ha` router extra attributes and whether distributed or centralized FIPs are used in OVN is governed by the ovn/enable_distributed_floating_ip option which does not operate at the per-router granularity and is global. The docs have not been updated and still say [3] that OVN routers do not expose `ha` or `distributed` attributes which are now there as of [1]. At the same time, the NDR implementation uses the `distributed` attribute to determine whether to use the gateway port IP and treat FIPs as centralized [4] and add a next-hop to the gateway port IP or not in the advertised /32 routes. For routers with `distributed == True`, NDR only attempts [5] to find ports with device owner `'floatingip_agent_gateway'`. Therefore, when distributed FIPs are enabled via ovn/enable_distributed_floating_ip, the `distributed` extra attribute on a router is set to `False` and /32 routes are advertised as centralized. The distributed FIP case is currently not exercised by the current bundles neither for ML2/ovs nor ML2/ovn. The current bundles only test the control plane and route advertisement, not packet forwarding via advertised next-hops. [1] https://review.opendev.org/c/openstack/neutron/+/864051 [2] |
||
|---|---|---|
| src | ||
| unit_tests | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| LICENSE | ||
| build-requirements.txt | ||
| charmcraft.yaml | ||
| metadata.yaml | ||
| osci.yaml | ||
| rebuild | ||
| rename.sh | ||
| requirements.txt | ||
| test-requirements.txt | ||
| tox.ini | ||