When devstack was switching to ML2/OVN as default backend,
in the base grenade job it was explicitly configured to use old default
ML2/OVS backend. It was done like that to avoid problems with upgrade
and change backend in the same job.
Now, as ML2/OVN is default backend in Devstack since at least
couple of cycles it's fine to switch grenade jobs to use default
backend.
Depends-On: https://review.opendev.org/c/openstack/ironic/+/866993
Depends-On: https://review.opendev.org/c/openstack/devstack/+/867065
Change-Id: Iede9fe71d81fc86a92122800d5a16f45442dd79e
(MTU - 50) only supports VxLAN over IPv4, decrease it
to support IPv6 as well, which is 20 bytes larger.
Change-Id: I8a9efa119afd43d1883b65a2c5c6eac8de8a7841
Setup a native Zuul v3 grenade-base job that defines base folders and
base devstack settings. The grenade play checks out repositories
in two locations, old and new, and sets up devstack config
in old and new as well.
Define a grenade job that sets up devstack services.
This job runs:
- devstack from grenade_from_branch (without tempest)
- grenade from grenade_to_branch
- projects in old from grenade_from_branch
and then tries to run grenade and then tempest.
The configure-grenade-branches role sets the base/target
branch variables (grenade_{from,to}_branch) and must be
updated when cutting a new branch.
Also, define the native versions of the grenade-postgresql
and grenade-multinode jobs, replacing non-native jobs
(like neutron-grenade and neutron-grenade-multinode) when possible.
Even though Python 3 is now the default, define grenade-py3
for compatibility reasons.
Finally, define a basic grenade-forward job which should
be used for forward upgrade testing. Forward testing
requires the user to set the destination branch,
and it is relevant for stable branches only, so disable it
from master.
At least for legacy grenade jobs, Zuul seems to be taking care
of Depends-On on the stable branch.
It is worth noting that tls-proxy is set to False as
it happens with the current legacy jobs. It does not
work by just flipping it to true.
Co-Authored-By: Luigi Toscano <ltoscano@redhat.com>
Depends-On: https://review.opendev.org/637523
Depends-On: https://review.opendev.org/649275
Change-Id: Iefe8d1d7d13bb56cbc9e80fb009d19218f8b1a64
'legacy-grenade-dsvm-neutron-forward' grenade neutron forward jobs
is present in opensatck-zuul-jobs repo running on python 2. This needs
to run on py3 from Ussuri onwards and py2 for stable/branch.
py2 version has been kept in opensatck-zuul-jobs and for ussuri
onwwards this has been migrated to grenade repo with py3 version.
Change-Id: Ifebd2492b9af322661c18a17c3724940d065c2b5
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I53dcfcb704a6dbdc8772d275001475bc0b1ecf26
This adds a grenade job which uses python3 on both
the old and new side of the upgrade run. This is part
of the python3-first community wide goal for the Stein
release. The exact version of python3 used depends on
the version of the underlying distro used in devstack
on both sides of the upgrade run.
Change-Id: Icc37e24c5910f189d09bcfed6cfbd348f6c24ab2
With the coming nova/placement extraction and need
to copy tables from the nova_api DB to the placement
DB, we should have a job using postgresql to verify
the upgrade also works for table copy/dump routine
for postgresql.
This adds a new grenade-postgresql job which copies
the neutron-grenade job configuration with the
exception of setting DEVSTACK_GATE_POSTGRES and it
runs in the experimental queue so it can be run
on-demand.
Change-Id: I7c11f244fc5529e0b8e5b7fcaa5874eb38cc9407
Slawek Kaplonski