The prelude section is usually used for release highlights.
As of now, the prelude section has only one contents on SmartNIC
support, but it is not necessarily most important topic.
It is already covered by "features" section, so it looks natural
to drop it from the prelude section.
Change-Id: Ibfe773f93ee5d805dcad27938209275197dadadb
L3 agent supports multiple external networks from a long
time ago, so remove this RPC call since it is not used.
According to codesearch of [1] and [2], we just remove
neutron built-in L3 agent RPC. For neutron server side
or RPC callback classes, the function is still remained.
[1] http://codesearch.openstack.org/?q=get_external_network_id
[2] http://codesearch.openstack.org/?q=L3RpcCallback
Change-Id: I764423e175d6e82729a647e415a9f267f495916f
Closes-Bug: #1844168
Change the execution order of:
- @privileged.default.entrypoint
- @lockutils.synchronized("privileged-ip-lib")
"synchronized" decorator holds the execution of the function until
the lock is released. Using the current decorator ordering, this
active wait is done inside the privsep context. This can exhaust
the number of execution threads reserved for the privsep daemon.
Closes-Bug: #1833721
Change-Id: Ifcce954003e360f620f9131a36a08ab84cbe6193
Neutron-LBaaS has now been retired and there will be no Train
release[1]. This patch removes neutron-lbaas references from
neutron.
[1] https://review.opendev.org/658494
Closes-Bug: #1833125
Change-Id: I0fe3fbaf4adf7fb104632fd94cd093e701e12289
In "ListNamespacePids", to check that a process is running inside a
namespace, a new thread is spawned. Inside it a shell command is
executed ("sleep <timeout>"). To avoid calling the method
"utils.kill_process" with the correspondent overhead when running as
root, this patch reduces the "sleep" time to a short period (3 seconds)
and lets the process to finish gracefully.
Trivial-Fix
Change-Id: Ib33e725b563b863810f61f457a0ddfee8edc5c2e
Type of lvm.vlan is int and other_config.get('tag') is a string,
they can never be equal. We should do type conversion before
comparing to avoid unnecessary operation of ovsdb and flows.
Change-Id: Ib84da6296ddf3c95be9e9f370eb574bf92ceec15
Closes-Bug: #1843425
This patch removes the dependency from ironicclient for the ironic
event notifiers in favor of openstacksdk.
Also, increasing minimum required versions for mock and
openstacksdk.
Change-Id: Ib76e19d29f0ae3db6d181578b638da699181f60d
Even though we check for the existence of the process before, it may
still terminate before we get to read its command line, so catch the
error that can occur here.
Change-Id: I3e89aca8bedfd2912effe2490718223f7d03133e
Closes-Bug: 1844500
This commit adds possibility to configure L3 conntrack_helper
service plugin and l3 extension with devstack plugin.
Related-Bug: #1823633
Change-Id: Ie96ff80f1c296c40ec2cd82c8d917a8bb262b12e
We need to mock all invocations of the ironic client, otherwise we see
failures with python-ironicclient 3.0.0.
Change-Id: If781a7733367a6636b9801a80a5c331910ed036e
Implement the Floating IP association logic only in one single place,
L3_NAT_dbonly_mixin._update_fip_assoc(). The dictionary returned will
include a new key, "association_event", with values:
- None: there is no association event. The internal port does not
change.
- True: a new internal port is added to the FIP register. An
association event can imply a disassociation event if the FIP register
had an existing internal port.
- False: the previous internal port is removed and no one is added.
Change-Id: I775aee178cf56f842b3c0a375eda01577840e227
Related-Bug: #1842327
Although notify_nova_on_port_status_changes defaults to true, it
could be to false, making the nova_notifier attribute unsafe to
use without checking.
This patch checks both the config option and that the attribute
exists, since the config could be changed after the plugin is
already initialized without the nova_notifier attribute being set.
Change-Id: Ide0f93275e60dffda10b7da59f6d81c5582c3849
Closes-bug: #1843269
ip_lib.IPDevice.device_has_ip doesn't include ipv6 addresses when
checking if a local adapter is configured to use a certain address.
This change fixes this issue, which will also allow using ipv6
tunnel endpoints.
Co-authored-by: Alin Serdean <aserdean@cloudbasesolutions.com>
Change-Id: Iff3d25a5701b96df9da75cf398fd19d29e5cfeda
Closes-Bug: #1843889
Zuul