UPPER_CONSTRAINTS_FILE is old name and deprecated

[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file

Change-Id: Ib0faeee98c348eb83354994aee9cff62e839eb3e

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: I543595c0e3145495923517101ffa057fd7bccb4c

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

Change-Id: I38a488598b9ecbeb2dfae42cb7279c7f4710bb31

Tempest replaced the below rolevar for run-tempest role
- tempest_test_blacklist is replaced by tempest_test_exclude_list
- tempest_black_regex is replaced by tempest_exclude_regex

old name are still supported for compatibility but we recommend
to switch to new one.

Change-Id: I73c5f0df0854a502e06e7c45f8b4d215a0832bdf

So that changes to this plugin (at least, most of them) don't break
victoria.

As stein moved to EM, remove its job according the common guidelines.

Change-Id: Ic9c4bd70a1071fccb8b71f0c9a97e0d2bfbc12a2

for some reason mistral api stoppped working in gate
need to investigate

Change-Id: Ic0793b518cb8545d8aed6af15dc721f141cfce49

heat fixed the image name

Change-Id: Idb16a1d7dd5c093f074fb6668f67205bb4068e99

This reverts commit 021dab33.

Reason for revert:Python 3.7 *is* supported because it falls
in the range of supported Python versions (3.6-3.8) [1].

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019648.html

Change-Id: I4ebd30942c35dc10222c17525fbd80285fe29278

Change-Id: I61e1f44aa786b99a46e480cbbfd518a503a3baa0

Change-Id: I68dab875e88b6dbdeb9ff453e60035137df7dfbd

We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].
Removing specific doc requirements from test-requirements.txt.

The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.

This project meet the conditions leading to the bug.

Also removing useless requirements, and pulling them from the right
place.

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36

Depends-On: https://review.opendev.org/c/openstack/vitrage-tempest-plugin/+/769917
Change-Id: Ia841a2d4198b43bac46a5b5af01f52e1354eea4a

Remove python3.7 from setup.cfg, since Wallaby's python
supported runtimes are python 3.6 and python 3.8[1]:

[1]: https://governance.openstack.org/tc/reference/runtimes/wallaby.html

Change-Id: I90f65e3b76332803f2f9b0367b1c77d5c677159f

Change-Id: I3320623bce9a3351cac91d5b4c1d30fbb999e5b1

Change-Id: I5995ba0dc020fa40ddf66b7ac9f36220967b670e

Change-Id: Idcd726767060197f44311b605a9b28a0d6e736f0

swap size was reduced to all nodes this created oom when running ceilometer
increase the size to what it was before

Change-Id: I8b86ba958bab07589abf6570f2242f7fc29bdb78

Replace the following items with Python 3 style code.
- six.moves.BaseHttpServer
- six.moves.zip
- six.PY2
- six.viewitems

Change-Id: If68cc2778bfccc56248ab8fba3de764044a707e9

Change-Id: I82bd58c804c7f8b2dd2f77954489cfa3f2c42060

for some strange reason when installing ceilometer and gnocchi
the mysqld process is killed by the oom killer of the operating system
this happens only in the gate and not localy on my devstack.

for now we won't enable the ceilometer plugin (which installs gnocchi)

Change-Id: If870b80456d8ebd4877253d977b5c59a11ad1c16

Tempest could be used not only after initial deployment but for
cloud verification during operations or after update. We don't
need to check that services are created today.

Depends-On: https://review.opendev.org/#/c/751657/
Change-Id: Ifc3cb1933a591ce1fe05fe11d5e07b78a0e61375

WHile moving the jobs to zuulv3 native, Focal migration work
got reverted- https://review.opendev.org/#/c/747109/

This commit makes stable jobs to keep running in Bionic and
master IPv6 on Focal.

Change-Id: Ibc82fbe95f6eca6f660596cf9da8c5c2e03c6fe2

Change-Id: I3b658f82217a7bdea4849fee2e075258c4c47538

Change-Id: I938cb7d5f820a761fc65ac82d137f83a2188faed

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.


[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html

Change-Id: Ia69f906364d6fe5a31b14dc8ec9cd37e18bdf27d
Story: #2007865
Task: #40226

Change-Id: Ibf32b59f078c4258d01c298068507d7fa22a9715

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: If0c72f4b5df2ac8983401a91e468d4e3863b2ba5

Change-Id: I1fd34bf4c8c6ed0993ac9a402decb78313f298e2

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: Id1bdef61cbca373e70d34cb45287a09ecc3776bb

Change-Id: I98c20bfb8cf366dd9a6f8d70b9de1d6c1de9ef50

Can have 2 (public,shared) or 1 (public)

Change-Id: Id6dd338fe32b5fb7d838525551fa876e40ceb604

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: If608c6af470f8a1645750e779392856b3a3d29db

Update docs building:
* Switch to sphinx-build
* Update requirements for Sphinx and openstackdocstheme for
  python 3
* Remove unneeded doc and translation sections from setup.cfg
* Remove install_command, it's unneeded, the default is fine.

Change-Id: I91b3d395f980f9aa55e4c6134b821efec4450643

We still use python 2 in stein

Change-Id: Ibf27c864818f4ec4f17896aa7e0862fa0030fabe

The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.

Fix problems found.

Change-Id: Ib598d6c80dc8665ee8b583f3a2238a14b0b5c04a