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
After switch of the default Neutron backend to the ML2/OVN
in the Devstack we had 2 rally jobs running actually with the
same Neutron backend.
This patch configures explicitly ML2/OVS as a backend in the
'neutron-rally-task' job so it is like it was before the change in
the Devstack repo.
In order to fix the CI, this patch also skips "test_models_sync" test
cases. Once [1] is fixed and released, we'll be able to create SQL
tables specifying the "_constraints_included" flag. When creating a
table, this flag should be set to "False" in order to be able to set
the "index" and "unique" parameters for each column in the table
definition, as we do now.
"test_update_router_admin_state" is excluded from
"neutron-ovn-tempest-slow" until LP#1890445 is fixed.
Set "test_restart_wsgi_on_sighup_multiple_workers" as unstable.
CI job "neutron-ovn-tempest-slow" has been set to non-voting until
LP#1930402 is fixed.
Related-Bug: #1929518
Related-Bug: #1890445
Related-Bug: #1930402
Related-Bug: #1930367
[1]https://github.com/sqlalchemy/alembic/issues/848
Change-Id: I38ed7931169434fecbbefa3762f51a522ef3c509
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
We don't need to run Swift, Cinder and etcd services in the
Neutron jobs so this patch disables those services on all
such jobs defined in the Neutron repository.
It will skip some tests which aren't really related to Neutron
and will safe some resources on test nodes.
This patch also enables br-ex-tcpdump and br-int-flows services
in the jobs where it was missing.
It may be useful during debugging some failures of those jobs
in the future.
Depends-On: https://review.opendev.org/762622
Change-Id: I0db516b184cf621e4539d11726fe1bd47b53ba05
The DevStack module for OVN has now been moved to the DevStack repository,
this patch is deletes it from the Neutron repository.
Depends-On: https://review.opendev.org/#/c/748140/
Change-Id: I2c30b8130525380234d767a7cb46f9bcca2a0d6b
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
There were duplicated methods doing almost the same in terms
of OVS/OVN compilation.
This change:
* move of OVS related compilation code to devstack/lib/ovs
* delete of OVS related compilation code from devstack/lib/ovn_agent
* source unified functions in devstack/lib/ovn_agent from
devstack/lib/ovs
* Unify NEUTRON_PATH variable to NEUTRON_DIR
Closes-Bug: #1877377
Change-Id: Ia012a8e116a276a6674f86366c803e0e2d8ff704
... to q-ovn-metadata-agent.
To the best of my understanding we decided to keep using the
neutron-legacy devstack module since it is the one used in the gate:
http://lists.openstack.org/pipermail/openstack-discuss/2019-December/thread.html#11544
And we merge new features like the ovn migration only working with
neutron-legacy:
https://review.opendev.org/696592
It seems to me we were a bit inconsistent in naming devstack service
'neutron-ovn-metadata-agent' since legacy style devstack service
names start with 'q-'.
For example this sample config is broken:
https://opendev.org/openstack/neutron/src/branch/master/devstack/ovn-compute-local.conf.sample#L31-L35
stack.sh dies with:
lib/neutron: line 368: neutron_plugin_create_nova_conf: command not found
Because not having a single 'q-' service in that enabled service list
we trip up devstack's 'is_neutron_legacy_enabled' check:
e51cbf0ea9/lib/neutron (L127-L135)
This change renames devstack service neutron-ovn-metadata-agent
to q-ovn-metadata-agent.
I'm not proud to propose this change in 2020 (circa 5 years after
the rename from Quantum to Neutron) so let me know if you see a better
way. :-)
Change-Id: I507a3426e2b63bff49891bd5a51fa9d9999a0ffa
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