When the segmentation ID of a network is updated, first the provider
network segment is validated and then reserved. If service plugin
"network_segment_range" is enabled, the Neutron server retrieves the
network segment ranges with shared=True or those ones with the same
project_id as the network.
This patch adds the "project_id" information to the filters when
reserving the network provider segment. This change will allow to
retrieve those private networks segments belonging to the same
project.
Change-Id: I21bd60af000276779f56b3a6d45b4a6c1836bed1
Closes-Bug: #1863619
When Load Balancer and its member has FIP assigned
and environment is configured to use DVR the member
FIP needs to be centralized. It is current core OVN
limitation, that should be solved in [1].
This patch adds this mechanism to OVN Client and
OVN Octavia provider driver.
It covers cases:
1) FIP association on port that is a member of
some LB - make it centralized.
2) FIP association on LB VIP - find a members
FIPs and centralized them.
3) Add a member to LB that has FIP already
configured - checks if a member has FIP
and centralize it.
4) The reverse of each of the above cases.
In addition I needed to extend OVN LB member external_id
entry to add an information about member subnet_id
in order to easly track member port from mechanism OVN
driver.
That means I needed also to support both old and new
conventions. This patch adds also this code.
Old convention:
member_`member_id`_`ip_address`:`port`
New convention:
member_`member_id`_`ip_address`:`port`_`subnet_id`
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1793897
(Cherry-picked from networking-ovn 57ac38921efa6bbf0bc4a22950355256cc3ebe6d)
Related-Bug: #1860662
Change-Id: I254f0ac28f7585b699a8238e01ffb37dd70282ef
This reverts commit 0ef4233d89.
This patch is introducing a redundant filter already present in
"testing.filters". The problem described in the related bug should
be solved in https://review.opendev.org/#/c/707697/.
Related-Bug: #1862927
Related-Bug: #1863213
Change-Id: I4de37364a6fb0184230a9742daced40e4edbfb30
If a relative path is set in rootwrap filters_path, the rootwrap
command must be executed from the neutron root directory. Some
commands, like those execute by RootHelperProcess, do not have
a defined working directory. To avoid the problems present in the
related bug, an absolute path is set in the rootwrap configuration.
Related-Bug: #1862927
Change-Id: I02ce4d6b84242c42ec26954eeb9b776cb779bff4
In [1], new tests to check "ncat" tool were added. The missing piece
of this patch was to add a new rootwrap filter to allow to execute
"ncat" binary as root and inside a namespace.
Closes-Bug: #1862927
[1]https://review.opendev.org/#/q/If8cf47a01dc353734ad07ca6cd4db7bec6c90fb6
Change-Id: I8e8e5cd8c4027cce58c7073002120d14f251463d
The fullstack test TestPlacementBandwidthReport.
test_configurations_are_synced_towards_placement sporadically failing
and one possible reason is that multiple agents are visible to the
server after restart of the agent (perhaps due to parallel execution).
Partial-Bug: #1862177
Change-Id: I79aa2cb9bcd69fc0cb35e0fd351a373e00feb062
https://review.opendev.org/705154 introduced NEUTRON_PATH but let it
empty by default, this patch adds default value to NEUTRON_PATH.
Partial-Bug: #1861469
Change-Id: Id5aab7f14e23ae8d7d1fc7ac4d23c67964bdb674
This patch changes the SB IDL from the MetadataProxyHandler class to
only watch the two required tables for it to function.
The more tables it monitors, the bigger the burden is on the OVSDB to
keep all the in-memory replicas updated. In special, the Chassis table
can generate a lot of events due to the agents health check mechanism
in the OVN driver so, removing it will prevent many events from being
sent across the fabric.
Closes-Bug: #1862648
Change-Id: Ib4fb9b445ed7fe4bce7bc05ae1b8dca264324718
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
Low port delete priority may lead to duplicate entries in network
cache if IPs are reused frequently.
Also can't find a strict reason why it should be of lower priority.
Change-Id: I55f858d50e636eb9091570b256380330b9ce9cb3
Related-bug: #1862315
Related-bug: #1828423
Resolves the following warnings seen in the likes of Neutron:
opt/stack/neutron/neutron/common/eventlet_utils.py:28:
DeprecationWarning: Please provide `is_available()`
function in your custom Eventlet hub <module 'oslo_service'
It must return bool: whether hub supports current platform. See
eventlet/hubs/{epoll,kqueue} for example.
Since we're simply taking the default hub provided by eventlet and
overriding a single attribute, we will always have support so set the
attribute.
Change-Id: Ie90bcce1d1724108e5d0e583a36aa2e20102bba4
As we now have new stadium project OVN-Octavia-provider [1] lets
add official tag which will be used for tracking bugs related to
it in Launchpad.
[1] https://review.opendev.org/#/c/697095/
Change-Id: Iaf99b75a79e1823742d7bd195f675f6ea42deb51
In a python3 only environment, 'python' might not be available (only
'python3'). So instead of hardcoding 'python' as executable, use the
executable that is used to run the tests itself which is
sys.executable .
Change-Id: Iae44aa2f1c336a0f5501312af05b0133193c5462
In patch [1] there was introduced simple lock for creation of
DVR agent's floating IP gateway ports for network to avoid races
and creation of duplicated ports for one agent and one network.
This fix from [1] works in simple examples with only one neutron-server,
so it helped e.g. in CI but it wasn't proper fix for production
deployments which are much bigger and have more neutron server api
workers.
So this patch introduces constraint on database level so this works even
across cluster with multiple neutron-server api workers.
[1] https://review.opendev.org/#/c/673331/
Change-Id: Id55b8a21d6ecf5e029d1ca267b2cbd2ed91cca4c
Closes-Bug: #1830763
This reverts commit 7b81c1bc67.
It isn't needed anymore with new solution with lock "on db level"
which is introduced in follow-up patch.
Change-Id: Ibf15ee1969f902e8a266825934d9ac963353f0a0
Related-Bug: #1830763
test_failing_async_process_handle_error_once() is calling
the python 2 interpreter. Let's make it use python3 instead.
Change-Id: I1f2f13685306f6b08b654a827a6477dc0aea942f
Remove the duplicated QoS supported rules and directions from
contributor/internals/quality_of_service page as the table is already in
admin/config-qos page.
Change-Id: I927b90877afb8bfeedb9b9ed0327650780972852
Both the neutron.base.agent and neutron.l3.agent
option templates contain RPC_EXTRA_OPTS, leading to
a warning during doc builds:
doc/source/configuration/l3-agent.rst:3:
WARNING: Duplicate ID: "DEFAULT.rpc_response_max_timeout".
It also leads to the rpc_response_max_timeout option
showing up twice in the resultant l3-agent.ini sample
file. For example, when running 'tox -e genconfig'.
Remove it from the list of l3-agent specific options as
it's unnecessary.
Trivial-fix
Change-Id: I70e626dbf9de4bd43952836f8c4d01a693ddac7f
The metadata agent registers the Chassis table with ovsdb-server
and therefor gets database updates every time *any* Chassis is
updated--even if the update is just a liveness check that updates
nb_cfg.
This patch adds a condition so that metadata agent only gets updates
for the Chassis that it is running on.
Change-Id: I452b7de09312ecea621c4b448cc63f037cad9675
Related-bug: #1861092
Rodolfo Alonso Hernandez