This option was deprecated in favor of the new aodh option. However
the old name is still used by code which causes the following warning
message.
WARNING oslo_config.cfg [-] Config option service_available.aodh_plugin
is deprecated. Use option service_available.aodh instead.
Change-Id: If10cec87a2f07f9dbe09005bb22070ca7a6e9364
The latest release of gnocchi is not installable
due to the protobuf version we use in upper constraints.
This change adds gnocchi as a required project so that
it will be cloned by Zuul and added to LIBS_FROM_GIT
Depends-On: https://review.opendev.org/c/openstack/devstack/+/872902
Change-Id: Ie70fec0a79b8c9ba1354cf32d6740ac710976c5c
For autoscaling granularity is set to 60 and the heat
stack is expected to scale out after instance reaches
CPU utilization higher than 10%.
According to this configuration the cpu time must be
10**9*60*(10/100) which is 6000000000 ns.
The default threshold for aodh alarms is "10000000"
which comes from ceilometer's devstack settings.
This change overrides the aodh_threshold value in
tempest.conf to the correct cpu time as per
cpu util and granularity values.
Signed-off-by: Yadnesh Kulkarni <ykulkarn@redhat.com>
Change-Id: Ic90613b70556d0ce5bcf64c2305a3351928bf83e
Disable SSL validation to prevent autoscaling tests
from failing with error
"certificate verify failed: unable to get local issuer certificate"
Set parameter "disable_ssl_certificate_validation" to True
which was introduced in 959fc69e49
Signed-off-by: Yadnesh Kulkarni <ykulkarn@redhat.com>
Change-Id: Iaa61eebf0e652b60182f893bba009b30d4734f95
Add a variation of the telemetry-dsvm-integration-centos-8s jobs using
branch selectors and provide a config for python 3.6 on older branches
(i.e. pre-yoga)
Change-Id: Ia57b83c7d764e2bb4eda19a46034ff2d3353aff7
This patch sets a zuul variable "nslookup_target" to 'opendev.org'
to fix the FIPS jobs.
The nslookup_target var was added as a required var for the enable-fips
role in [1].
[1] 25caf7ef5e
Change-Id: Ifb0f929cf7cb9dddedcf4f0bd930b4bd7ca2dd72
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.
Note CentOS Stream 8 jobs are still left now but will be removed once
job definitions in aodh/ceilometer are updated.
Change-Id: I6add67a23a5d39852a1cdca9e2baf3faa1ac0cbb
The failing part of the integration test was disabled until
we figured out what exactly fails and why. In the mean time,
we can take advantage of the rest of the integration tests.
Change-Id: Iaefaa06b37deb5ecf2108c027ac7db98130c8c98
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I696ad20f74bdb1c510fe02e6ae08d72396ffd548
stopping check jobs.
Also switch ussuri jobs to non-voting until HEAT has merged replacing
Fedora 31 with the Fedora 32 image.
Change-Id: Ifc5a6c442ec68438dbe58e2c84e1861c43d6fad4
tempest.Manager has been deprecated for more than 4 years already.
Tempest plugins are expected to consume
tempest.lib.services.clients.ServiceClients directly.
Change-Id: I614451e909ef2471493f702928db8eff591be037
Gabbi does not allow to pass custom path to (self-signed) SSL certs,
so we can't really re-use the CONF.identity option (as does the AODH
test client).
This patch adds a new config option
CONF.telemetry.disable_ssl_certificate_validation
(False by default) that will disable SSL cert validation when running
gabbits.
For comparison, see similar patch to heat's tempest plugin
https://review.opendev.org/#/c/703335
Change-Id: I298c8ebb45f0768b12919cf4f67462df0ff4c631
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
Most of the Tempest jobs will be migrate automatically once devstack
base job start running on Focal(Depends-On).
Stable jobs testing stable branch needs to keep running on their supported
distro version which is bionic from stein till ussuri.
Depends-On: https://review.opendev.org/#/c/752294/
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-fo$
Change-Id: I7e032bb8848dd662432f846c51989180aa7c9b28
Story: #2007865
Task: #40223
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I45295290471a5d8d32fb11ddbb64a8accdb7710a
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: Ie9ce28dea10f06dc6d65a6f76f762212d1917df9
Keystone catalog url could be with or without the trailing slash.
Removing it when get the endpoint.
Change-Id: I55bbfb5823957ff50d9a588c9cc1a9faebecffff
Supported stable branches in maintenance state
(stein, train, ussuri) use the Tempest and plugins master
version for their testing. To make sure master version (new
tests or any changes) is compatible with stable branch testing,
we need to add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the stable
branches in same way[1].
Ussuri onwards, Tempest or plugins are py3 only, so we are
running only python3 version of stable jobs
Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
[1] e8f1876aa6/.zuul.yaml (L646)
Change-Id: I5a37c4717b6702c8a47f7a26faa3393a2acd3148
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Update requirements, no need for python_version anymore
- Switch to using sphinx-build
- Use newer openstackdocstheme and Sphinx versions
- Switch to hacking 3.0, fix problems found
Change-Id: I499bb071847dd006d4045faf2325f588d07b4ffe
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
Change-Id: I547968d14abbdb8d134d7a94a545ea38342ec6a1
current tests implementation is not friendly to test re-runs:
as archive policy may fail to delete when there are still samples
stored for it (and the test expects it, see the last xfail: true in
the aodh-gnocchi-threshold-alarm.yaml), next test rerun may fail
right on the initial setup as it receives 409 Conflict instead of 201
on attempt to create an archive policy that already exists.
Solve this by tolerating 409 in the archive policy creation step,
and moving checks for fields of created (or existing) policy to an
extra GET /v1/archive_policy/<name> step.
Change-Id: I978937d89b2e886e2ef690661bc00a730db94c92
Takashi Kajinami