and update tox to later version

Change-Id: I4c07e622f2285513c86f168c15b375e62b5594ad

in order to remove and retire panko.

Change-Id: I8bc2981f01a4b068272cddfa2026860c97a3355e

The job is apparently broken in cleanup phase.

Change-Id: I2c3fb918c559b892865287a3363e090cad9e9b98

Moving on py3 as the default runtime for tox to avoid to update
this at each new cycle.

Change-Id: I03700a8ee7e5d38ec0ab5933ef277c422a228ef3

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

This has been changed with https://review.opendev.org/#/c/746492/.

Change-Id: I8af3b53df57099e135551b248abaf419e8a4912b

The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I9bc74b7d1be322ddc0c284cbacc3e625bc72872e

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] https://opendev.org/openstack/tempest/src/commit/e8f1876aa6772077f85f380677b30251c2454505/.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

OpenStack is dropping the py2.7 support in ussuri cycle.

telemetry-tempest-plugin is ready with python 3 and ok to drop the
python 2.7 support.

Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal - https://review.opendev.org/#/c/691178/

Change-Id: I72abc58ee67cf0594faa07e0f89b52f1c9cc6c2f

The purpose is to remove dependency of gocchiclient.

Change-Id: I4c07a8d15338b6ec80ca95cef64ab74ed6028319

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

Change-Id: Icdd8b5a178527fec7479bf518eb4a0792eb35c21

The links are invalid.
Replace them with the available one.

Change-Id: I244332c9eff84c5f15d7d656f80a24f1267c6218

Change-Id: I26f8f9fcdcf9cc18f947440d18e8bb3c63db1e1f

Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.

Change-Id: I599da0883546c2af9fd054f64bee695a70d823d8

For more detail, see http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006478.html

Change-Id: I2be06b68a69f8ccae340d2dbc560d1e1fb07c27b

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 adds the new job 'telemetry-dsvm-integration-ipv6-only'
run on gate which is derived from 'devstack-tempest-ipv6'.

Verification structure will be:
- 'devstack-IPv6' deploy the service on IPv6
- 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address
- 'telemetry-dsvm-integration-ipv6-only' will run the tests.

Story: #2005477
Task: #35939

[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html

Change-Id: Ic5588d7351cf6f60775703bbb995c80c2647d335

It's not always true that Gonocchi is deployed in the environment,
in which case the aodh tempest tests will always fail at the resource
setup phase.

This patch adds the option to config if alarm should be created in the
resource setup method.

Change-Id: I69adb9eef8a0bdbe2333e3ec4866a44aae50d0a2

This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.

See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html

Change-Id: Icd848acb737e046e76e5496f3acd02e1437b7349

To avoid the name conflict in integration test.

Change-Id: Ia64e42403f29056008d69aa5c60d396564d66755

When running the tests against production cloud, the resource list call
would return tons of records, so it's better to use resource search api
instead to check the resources.

Change-Id: I723f99e5b19ddf4dc2d9c20738e818b7399f54a4

Change-Id: I10a98d16f9df6bdae5aa1b0751d28c6439a7fc12