This was overlooked when the documentation was removed by [1].
[1] 3997367300b7d9c0159f5dacc10dac31cce1d3bd
Change-Id: I3d42cd865427e8870c956986d3c8bd8a43d497ee
TripleO project has been retired[1]. Remove the migration tool
implemented specifically for TripleO deployments.
Change-Id: I32775a0aa963b65a3900a87f28a88ab63901a8a0
... because TripleO project has been retired.
Also remove the example environment file for TripleO.
Change-Id: I3f3985cc9afafaaa7101cab55875ea640103dea6
This option was removed by b09b44608b1e5b787c686c6ce52bb37480fb5129 .
Update the unit test code not to register the option to config mock.
Change-Id: I87e2a2ede6a375e62835a0ea131240031a02f76d
Fixes a logic error which meant that we didn't iterate over all logical
switches when associating a FIP to an OVN loadbalancer. The symptom was
that the FIP would show in neutron, but would not exist in OVN.
Closes-Bug: #2068644
Change-Id: I6d1979dfb4d6f455ca419e64248087047fbf73d7
Co-Authored-By: Brian Haley <haleyb.dev@gmail.com>
Since [1], the SG rule SQL view also retrieves the table
"default_security_group", using a complex relationship [2].
When the number of SG rules of a SG is high (above 50 it
is clearly noticeable the performance degradation), the
API call can take several seconds. For example, for 100
SG rules it can take up to one minute.
This patch changes the load method of the SG rule
"default_security_group" relationship to "selectin".
Benchmarks with a single default SG and 100 rules,
doing "openstack security group show $sg":
* 2023.2 (without this feature): around 0.05 seconds
* master: between 45-50 seconds (1000x time increase)
* loading method "selectin" or "dynamic": around 0.5 seconds.
NOTE: this feature [1] was implemented in 2024.1. At this
time, SQLAlchemy version was <2.0 and "selectin" method was
not available. For this version, "dynamic" can be used instead.
[1]https://review.opendev.org/q/topic:%22bug/2019960%22
[2]08fff4087d/neutron/db/models/securitygroup.py (L120-L121)
Closes-Bug: #2081087
Change-Id: I46af1179f6905307c0d60b5c0fdee264a40a4eac
Currently if the nova endpoint do not exist
exception is raised. Even the endpoint gets created
notification keeps on failing until the session
expires.
If the endpoint not exist the session is not useful
so marking it as invalid, this will ensure if endpoint is
created later the notification do not fail.
Closes-Bug: #2081174
Change-Id: I1f7fd1d1371ca0a3c4edb409cffd2177d44a1f23
During the 2025.1 release, the lower version of grenade "skip-level"
jobs should be stable/2024.1.
During this release (SLURP), these jobs are now executed in the
"check" queue as voting.
Change-Id: I25faa22db7688eabfc702d0101804ae4ba23dcb0
Add file to the reno documentation build to show release notes for
stable/2024.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.2.
Sem-Ver: feature
Change-Id: I65298c0d198ebfe97635295c8a0deabdc88424e3
The job was added to check queue during sqlalchemy 2.0 transition. We
are past the transition, so let's not waste gate resources (and
developers attention).
Change-Id: Ic4e2d91f03ce29e8ce83c393e95cb1dce29b3457
This patch enables debug_iptables_rules config option in the L3 agent
related functional tests.
Related-Bug: #2079048
Change-Id: I6cb17b149626fb88c82937e046632dc8ca8d7ced
All ``ARPSpoofTestCase`` tests now define the source device (using
the IP address) to be used to execute the "ping" command.
Related-Bug: #2003196
Change-Id: Iace245b013e10eec323c0b58bf5cdf5ee9236338
This new method allows to create multiple tags for a single resource.
The tags are passed as arguments in the ``POST`` call. That solves
the issue with the usage of URI reserved characters in the name of
the tags.
Bumped neutron-lib library to version 3.15.0, that contains [1].
[1]https://review.opendev.org/c/openstack/neutron-lib/+/924700
APIImpact add create method for service pluging "tagging"
Closes-Bug: #2073836
Change-Id: I9709da13c321695f324fe8d6c1cdc03756660a03
This ovn option for the Logical Router Port was added to be set with [1]
but FLAT networks are basically working in the same way and should have
this option set in the same way.
[1] https://review.opendev.org/c/openstack/neutron/+/871252
Change-Id: I3203678c1ca6fb778c993b6084bab171a312ec28
This patch adds implementation of the "port_trusted_vif" API extension
as ml2 extension.
With this extension enabled, it is now possible for ADMIN users to set
port as trusted without modifying directly 'binding:profile' field
which is supposed to be just for machine to machine communication.
Value set in the 'trusted' attribute of the port is included in the
port's binding:profile so that it is still in the same place where e.g.
Nova expects it.
For now setting this flag directly in the port's binding:profile field
is not forbidden and only warning is generated in such case but in
future releases it should be forbiden and only allowed to be done using
this new attribute of the port resource.
This patch implements also definition of the new API extension directly
in Neutron. It is temporary and will be removed once patch [1] in
neutron-lib will be merged and released.
[1] https://review.opendev.org/c/openstack/neutron-lib/+/923860
Closes-Bug: #2060916
Change-Id: I69785c5d72a5dc659c5a2f27e043c686790b4d2b
