Devstack recently introduced the functionality to use a single venv[1]
but some devstack plugins in telemetry project are not compatible with
this change.
This disables the option as a short term workaround.
[1] https://review.opendev.org/c/openstack/devstack/+/558930
Related-Bug: 2031639
Change-Id: I62c31bb942465d3179b906c1eb657272c76e4f23
The gnocchi install is broken on setuptools delivered
by centos9s, lets make these jobs non-voting until
that is solved to unblock the gate.
Change-Id: I3a5e7d576b3ca5b4adff1bd3a807907e764efeaa
Recent changes to git prevent git repos from being parsed if they
are not owned by the current user as part of a CVE fix. Some
project use stevedore to load plugins and this is broken if
gnocchi is installed from git via "sudo pip install".
This change uses devstacks git_clone to ensure that the gnocchi
repos is clonned under $DEST aka /opt/stack as the current user not
root. It then uses pip install -e to install the precloned repo.
To enable this GNOCCHI_REPO and GNOCCHI_BRANCH are intoduced
and the non standard GNOCCHI_GIT_PATH is removed.
A long standing comment to stop installing from git after
Gnocchi 4.0 is adressed by only installing from git if
gnocchi is listed in LIBS_FROM_GIT. However since
4.4.2 is currently incompatible with openstacks upper-constraits
file the ci will continue to git however the git repo will
now be prepared by zuul using required-projects.
This will have the side effect of allowing
Depends on to work for PRs to gnocchi however testing that
is out of scope of this patch.
This patch adds a sample local.conf that can be used to deploy
locally for devopment.
Depends-On: https://review.opendev.org/c/openstack/telemetry-tempest-plugin/+/872350
Change-Id: I833ea3bffb18bec063423450be0f3b8ff92f9a5a
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Ibf8a7ba2bed10e90fc6acb7693055489c170ec03
The latest cinder requires Python >=3.8 which is not available in
CentOS Stream 8. This bumps the base OS version to 9 which has Python
3.9.
This change makes the fips job non-voting because it is frequently
failing now.
Depends-on: https://review.opendev.org/840811
Change-Id: Iedf7f5aea15920053fb7a0b24e44e24db209edec
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
Tempest has defined the base job 'devstack-tempest-ipv6' which will
deploy services on IPv6.
This commit Run 'telemetry-dsvm-integration-ipv6-only' job in ceilometer gate.
Story: #2005477
Task: #35939
[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
Change-Id: I068c996b04c75f0aa077b1902e7be2ab7afc3983
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: Ifb40dd40e716c0f07cafce4425e4ac13619d2085
Depends-On: https://review.opendev.org/#/c/641878/
Use openstack-tox-cover template, this runs the cover job
in the check queue only.
Remove jobs and use template instead.
Change-Id: Icbe18f9f5c2249c878c54621aafc3dd10106f20d
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ie153246b718d80b1ddf179a9e064cfc2dafbd178
Story: #2002586
Task: #24339
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I789ea2f371239239fbe6ec7edcd173a2caf23a65
Story: #2002586
Task: #24339
stestr is recommended by OpenStack Project Testing Interface for running tests
[1]. This change migrates to stestr for running unit tests and coverage
job. Modified `cover` env allows running it as Zuul job and visualising
its results in Gerrit.
[1] https://governance.openstack.org/tc/reference/pti/python.html#python-test-running
Change-Id: I9e8b79d7a18cd36946daff10abb1a2f43b1aa3a1
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ief4619ab4970bfea8dfcbac47ab3cd5aa951d7a1
Configure the layout to execute the scenario001 and 002 jobs.
Note that baremetal job will be run on stable/pike and container on
Queens and beyond.
A note has been added in comment explaining more details.
Change-Id: Ic9fc3bd769a5ccafb3f81fe55513c96d611dbe7d
Zuul now supports including the file extension on the playbook path
and omitting the extension is now deprecrated. Update references
to include the extension.
Change-Id: I2e4ebb963ea917a6eeb2336935b7d8a02c384d31
Yadnesh Kulkarni
OpenStack Release Bot