All Neutron CI jobs (except for unit, functional and fullstack jobs),
have explicitly defined the network backend used:
- linuxbridge
- ovs
- ovn
That was discussed and approved during the Neutron CI meetings [1].
[1]https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-06-15-15.00.log.html
Change-Id: I036924f13b77dd5957ad5e60b9f536562deb9f05
It is set to true by default in base jobs. Also e.g. in
functional job for neutron-dynamic-routing it is set to True so
it should be fine to use default value in the neutron-functional job as
well.
Related-bug: #1932483
Change-Id: I2c8392628dd63ca612c6d8428daab66724e88c20
In order to check how the "nftables" binaries work with Neutron, two
new jobs have been added to the periodic queue:
- neutron-tempest-plugin-scenario-linuxbridge-nftables
- neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-nftables
In those two jobs, the binaries for "iptables", "ip6tables",
"arptables" and "ebtables" are replaced with the "nftables"
counterparts; by default, newer operating systems use the "nftables"
versions, providing the legacy API to the user but executing the
new packet handling in Netfilter.
Change-Id: Idec6d480886298f6d71b1dd649c9255ee6b7bebb
Related-Bug: #1508155
Related-Bug: #1922892
This patch tries to make execution of the CI jobs in the Neutron
queue to be more smart. There is no need to e.g. run
linuxbridge scenario jobs job when only changed files in patch
are in e.g. the openvswitch agent module, or vice versa.
Change-Id: Ie33514da28991fa5952a1d8c289402ecb9ffee49
To limit usage of resources (mostly memory) in the fullstack job and
to avoid oom killer to kill e.g. mysqld service, this patch:
* Makes number of API workers changeable by tests, as a parameter to
EnvironmentDescription and defaults its value to 1. As neutron server
is spawned separately for each test and is used only to process just
few API requests during that single test so this should be still
enough there, and where more API workers are needed (like some dhcp HA
tests: TestDhcpAgentHARaceCondition) it can be changed,
* reduces number of test run workers from 4 to 3 - job will run slower
but hopefully more stable,
* in the functional and fullstack tests job definition disable etcd3
service - this will not save us a lot of memory but still it's not
needed at all so why to run it there.
Change-Id: If19803ab6db144e2d17d6805d379c1c76d8fa343
Closes-Bug: #1906366
We have to pick OVS patches compatible with kernel 4.15.0-118
after switching to it.
Change-Id: I1ff47fc3398760d5b631bf89e6cfcc7ae339f0e3
Related-bug: #1883601
Closes-bug: #1896766
This commit bumps the OVN version used in the gate from v20.03.0 to the
latest tagged version, v20.06.1.
Change-Id: Ie070f3c4d75272d12f295a2ea4f7fa6548a7b002
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
OVS tag v2.13.0 is not compatible with current used kernel on upstream
Bionic Ubuntu kernel 4.15.0. This patch sticks to commit hash to unblock
the gate. We can either change to newer 2.13 tag once released or better
stop compiling OVS and use one packaged by Ubuntu.
Run functional/fullstack tests with selected OVN and OVS versions
Previously for functional tests OVS version was hardcoded - v2.12.0,
and OVN was installed from OVS repository.
After we merged OVN driver to Neutron tree we run both
Neutron/OVS and Neutron/OVN functional tests in one job.
This patch adds possibility to specify from which tag/branch OVS and OVN
should be checkout.
Change-Id: I83688031951b97bfe64f3aaa761ad7afc1d5ea55
Closes-Bug: #1883601
Closes-Bug: #1878160
neutron-fullstack-with-uwsgi and neutron-functional-with-uwsgi
jobs are run in devstack gate[1] also. On devstack side these jobs
are broken when migrated to zuulv3 and start using neutron defined
tox env. neutron gate is no issue as job find the tox env in neutron's
tox.ini but devstack does not.
We need to define the working dir to neutron so that any where
they are run they always look for the neutron's tox.ini for used
tox env.
Failure: https://review.opendev.org/#/c/577779/
[1] c3b58f5335/.zuul.yaml (L717)
Change-Id: I0cadebb45864a83dfba7b54c9f161d11611164db
Security groups are based on iptables in many cases and can interfere
between other tests. So it means that if some other test will manipulate
with iptables on host during SG related test is run, this SG related
test may fail without any obvious reason.
So lets try to run those test serially to be sure that no other agents
will manipulate iptables/openflow rules in same time.
Change-Id: I4d19f2a457e004306fdf40980a943073f1b8704a
Closes-Bug: #1779328
We already have many different jobs defined for Zuul in Neutron repo.
Up to now all those jobs were in .zuul.yaml file but this file growth
really big and it was hard to read and navigate in it.
So this patch proposes to move jobs definitions to zuul.d directory to
separate yaml files per "job types". So there will be now separate files
with definitions for:
* grenade jobs,
* base jobs like functional and fullstack,
* rally jobs,
* tempest multi node jobs,
* tempest single node jobs,
* tripleo jobs.
And maybe others in the future.
Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7