When trying to execute the fullstack tests, I was a little bit lost in
the documentation.
This change is a proposal to refactor this a little bit so the only
source of truth is the doc/source/contributor/testing/fullstack.rst
file.
Change-Id: Ibaf2ab9a227d71d18adf027d2ae509168c1e26da
Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
Some of the docs use the long hand path for firewall_driver,
which might not always work. Change the remaining few
examples to use the short hand from setup.cfg instead.
Change-Id: I02bcf654e041ff9c1ff27e64b8493c5e13d7e479
Closes-bug: #1809578
With [0] the incompatibility between neutron-dynamic-routing and OVN has
been removed. Mark the BGP extensions as supported by OVN and amend the
list of gaps accordingly.
[0] https://review.opendev.org/c/openstack/neutron/+/864051
Change-Id: I773e581e8d044e87e45a10394cca25ecbe7603ad
That includes the limitation of ML2/OVN for VXLAN networks to
a maximum of 4096 networks and the explanation.
Closes-Bug: #1998085
Change-Id: I0b0ba353c219a49acd80edecd0997d1f653b0192
Nothing much else, what the title says...
Change-Id: Ib1d41a6e4c869e108f31c1eb604f22c794d66467
Closes-Bug: #1996759
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
There is an inconsistency for keystone domain names
in the docs, 'default' and 'Default'. Should always
use the latter, 'Default'.
Change-Id: I4487de4e121362a02f839546721f007781f84057
Closes-bug: #1996889
Metadata service now supports IPv6 networks. This patch removes
this limitation in the documentation.
Related-Bug: #1460177
Change-Id: I1c50aef5e4aa60705f923f399e8d36c37a9d6289
This patch replaces the Linux Bridge references with Open vSwitch in
the installation manuals.
Closes-Bug: #1996772
Change-Id: Ib63daad7fac52e1e10dca2e98add01d5ee7635a3
This was discussed during the October 2022 PTG in the Neutron room.
Even if we do have many Neutron jobs which inherits from the
"tempest-integrated-networking" job, we are overriding some
configuration of that base job in our repo.
To make sure that we are not breaking any other projects we should run
in our check and gate queues directly "tempest-integrated-networking"
job too as this is our "reference" job from the integrated CI used by
other projects.
To avoid redundancy in CI jobs this patch also removes
"neutron-ovn-tempest-ovs-release" from the check queue and moves it back
to the experimental queue.
Change-Id: I00e5248ed816618d2132b502a7116626f9c59dc5
Column with python's version used in the job was useful when we had
both py2.7 and py3 jobs. But now we supports only Python 3 so this
column is not needed anymore (and also it was outdates as we don't use
python 3.6 anymore in master branch).
Change-Id: I49cfeca1d454af9fb6379227d2aebac3da3709e1
We had 2 different kinds of "ovn ipv6 only" jobs defined:
- neutron-ovn-tempest-ovs-release-ipv6-only
- neutron-ovn-tempest-ipv6-only
First of them was running only smoke tempest tests and we had it
in our periodic queue.
Second was run in the check and gate queues and was running all tempest
networking related tests.
That second one was also installing OVS and OVN from sources instead of
the packages provided by the distro.
This patch unifies those 2 jobs so we now have
abstract "neutron-ovn-tempest-ipv6-only-base" and derived from that
2 different jobs:
- neutron-ovn-tempest-ipv6-only-ovs-release - used in check/gate queue,
- neutron-ovn-tempest-ipv6-only-ovs-master - used in periodic queue
Additionally this patch removes "neutron-ovn-tempest-ovs-release" job
from the periodic queue as it is now in the check/gate queue.
Change-Id: I355c5eaca31e12bf980794b1867e1ca39aea96e0
This job was run only in periodic queue until now but to avoid issues
like described in the related but, we should have this job run in
the check/gate queues as this is job which almost directly inherits from
the "tempest-integrated-networking" defined in the tempest.
Related-Bug: #1991962
Change-Id: I0ceaa9667a9218cb12a0f3b666a68d4bddeb6911
Since [1], ML2/OVN mechanism driver supports minimum bandwidth
QoS rules. This support was implemented in OVN v22.06.0.
[1]https://review.opendev.org/c/openstack/neutron/+/842292
Related-Bug: #1982951
Change-Id: I52fd399ff9580df3e30d3aa66b3f54882897e6cf
Bullet points shouldn't be preceded by a space. Doing so renders them as
blockquotes. We also have a load of literals/code. Mark them as such.
Change-Id: I59c09c88a68f617f03a1753332ffb5311f8806a6
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
In neutron, user can create multiple ports with same IPv6 address if
the network has no IPv6 address scope. This maybe result in some
security issues.
This can be exploited by a malicious tenant via creating a subnet with
a prefix that covers an address that is already in use and take over
(part of) the traffic flowing towards that address. The success of the
attack depends on winning the race of who answers the NDP query first,
but still a 50% chance of capturing traffic seems dangerous. The attack
works not only against other addresses served by NDP proxy, but also
against other hosts that may exist, potentially even the gateway for
the external network.
So, we should use `IPv6 address scope` to ensure the IPv6 address is
unique when we want to use `ndp proxy` feature.
Depends-on: https://review.opendev.org/#/c/855997
Closes-Bug: #1987410
Change-Id: I0fa431a91a7679e409386a357a01c31ec5ad0cfd
- Use only the documentation prefix in examples
- Update some formatting and wording
- Add a reference in the OVN gaps document
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I2acf762008ce44b6a792c615c153071e1c10e0b3
A new script to remove the duplicated port bindings was added. This
script will list all ``ml2_port_bindings`` records in the database,
finding those ones with the same port ID. Then the script removes
those ones with status=INACTIVE. This script is useful to remove
those leftovers that remain in the database after a failed live
migration.
"dry_run" mode is possible if selected in "[cli_script] dry_run"
boolean config option. The duplicated port bindings are printed in
the shell but not deleted.
Related-Bug: #1979072
Change-Id: I0de5fbb70eb852f82bd311616557985d1ce89bbf
As a failsave the migration code can create a backup of
the controllers to use in case that the migration fails
and leaves the environment on a unusable state.
The revert plan has two stages:
1- Backup stage: included on the current ovn-migration.yml.
Can be configured using the env variable CREATE_BACKUP
(True by default). This stage will run the new ansible
role, recovery-backup.
It will store the backup on `/ctl_plane_backup` on the host
where the BACKUP_MIGRATION_IP belongs to (can be modified by
modifing the env var).
In order to restore the controllers, boot them using the iso created
by ReaR (stored in /ctl_plane_backup) and perform `automatic recover`
2- Revert stage: this stage has its own ansible playbook (revert.yml)
This playbook will clean the environment from all the OVN ressources
that could had been created (breaking the data plane connectivity)
to leave the environment in a stage where an overcloud deploy with
the OVS templates can be run.
Note: If the user creates new resources after running the backup stage
and then performs the recovery of the controllers, those resources will
be lost.
Change-Id: I7093f6a5f282b06fb2267cf2c88c533c1eae685d
Updated documentation about minimum guaranteed bandwidth support
for OVN backend. This mech driver is capable of informing the
Placement API about the bandwidth resources of each chassis and
schedule a port depending on the minimum bandwidth rules applied.
This patch also updates the document pointing to the new
``resource_requeste`` blob passed to Nova with the information of
the requested resources of each port.
Related-Bug: #1578989
Change-Id: I75401fa64e1ccd814aa485a74b38092849ff2a18
The doc build needs WebTest, which used to be imported as a transitive
requirement via pecan, but the latest release of pecan dropped this
dependency. So make this requirement explicit.
Change-Id: Ib3f3318440c79909090616b9d480b8dbf55e7b81
https://docs.openstack.org/nova/latest/admin/aggregates.html link failure,
From openstack U version, this link is not in the user directory. Currently, only the latest version has been changed.
You are advised to change all the links
Change-Id: Ic3b5a0ac7d832b162848b363396264ed0bfc4a25
During the Zed PTG it was decided to handle unsupported features in
Neutron as experimental. See section titled "When we say something is
not supported?", day 2 in [1]. The agreement was:
"We keep existing jobs for linuxbridge driver for example, but when the
tests start to fail we skip them and finally we stop the job also.
To make it clear for operators we add warning logs highlighting that the
given feature/driver is experimental, and introduce cfg option to enable
such features explicitly."
This commit implements this agreement, initially with Linuxbridge
Depends-On: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/845646
[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-April/028164.html
Change-Id: Ib18efa3f472736b58c8967847b1061da0e3897d7
Original url leads user to a markdown file, I think it's better to
use official html document rather than a markdown file.
Change-Id: Ib3ee4c6bccbb98a6469e2d7e9cde652288bbb163
