mistral-tempest-plugin 1.3.0 release

meta:version: 1.3.0
meta:diff-start: -
meta:series: xena
meta:release-type: release
meta:pypi: no
meta:first: yes
meta:release:Author: Ghanshyam Mann <gmann@ghanshyammann.com>
meta:release:Commit: Ghanshyam Mann <gmann@ghanshyammann.com>
meta:release:Change-Id: Iad6f4a21cf7f35f56420b61c1af05e0603075c95
meta:release:Code-Review+1: Martin Kopec <mkopec@redhat.com>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

This patch updates/adds the contributor documentation to follow
the guidelines of the Ussuri cycle community goal[1].

[1] https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-contrib-docs.html

Story: #2007236
Task: #38537
Change-Id: Ifde9c6b18a034e2784459a9dbfb22b080166781e

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

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

Wallaby support officially the following runtimes [1]:
- Python 3.6
- Python 3.8

During Victoria Python 3.7 was used as the default runtime [2] however this
version isn't longer officially supported.

[1] https://governance.openstack.org/tc/reference/runtimes/wallaby.html#python-runtimes-for-wallaby
[2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria

Change-Id: I832d5805a138d7d091dffa100110c90cb80c23b4

mistral-tempest-plugin 1.1.0 release

meta:version: 1.1.0
meta:diff-start: -
meta:series: victoria
meta:release-type: release
meta:pypi: no
meta:first: yes
meta:release:Author: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Commit: Sean McGinnis <sean.mcginnis@gmail.com>
meta:release:Change-Id: I5c767517cc7efde3b0cc88407ad7442faf8cc686
meta:release:Code-Review+2: Hervé Beraud <hberaud@redhat.com>
meta:release:Workflow+1: Hervé Beraud <hberaud@redhat.com>

* Some more adjustements to the Actions API tests related to
  the Action Provider transition. Some tests have to be temporarily
  disabled because there's no way to make them on both current
  version of Mistral and the version including action providers.

Change-Id: I13033253d5098655a001135c8702d1b1d13e76d4

* It's part of the Action Provider refactoring. The API had to
  slightly change.
* Pagination has to be still implemented.

Change-Id: Ibc26645a90101eceab507e7c7755cdd4fbbf7536

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: I3651224de022bff78840df8cd6ca95792dc5cce5
Story: #2007865
Task: #40196

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

Change-Id: I19e72d79de5a6212c3901f1ce5b6640cb285310c

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

Change-Id: If4746b8ce991f83d613cd02db4aeb1f7a9e8b027

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

* Backports to stable/train are now failing because tempest requires
  Py3 but for some reason Py2 is provided. So we have to explicitly
  define the version of Python in master because there are no
  stable branches for tempest.

Change-Id: I19b57e686306b9d3f26bc5a0228ebf5d7c08bb20

The 'std' prefix was removed from the workflow name
make sure it passes on both cases.

Change-Id: I9bd36bf2ad1a36ff569f385190c186b63b78f1e1

* Mutable default arg
* Use of reserved names as parameters
* Missing requirements
* Unused parameters
* use static method
* Doc errors

Change-Id: Iaf7efa263398005ba1fa7261c894c85cb2fbcf47

Change-Id: I199ccdbf6684c1bc979428898a7d9094a7267f9d

The Service api was fixed and supported only in ussri
Don't run it if not supported

see: https://review.opendev.org/#/c/700507/
     https://review.opendev.org/#/c/700517/
     
Change-Id: I84ddb8a075269dc475fb56e0fc5ecabd28bba1a8

Change-Id: Ibfe40f6a442317d2879ee5a36682134d439de33e

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

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

Removing the USE_PYTHON3=True from base job so that it can
keep running  on py3 for < ussuri branches.

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://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html

Change-Id: I060587c96baba096525211ffccbe29f71b38760d

Change-Id: Ia96244290428e374ec22ee250264225d708ddc87

Also drop py27 support and remove pypy

Depends-On: https://review.opendev.org/#/c/700507/
Change-Id: I23f92c8f514e51b90bdf01a46278e7b53282117d

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 'mistral-devstack-tempest-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
- 'mistral-devstack-tempest-ipv6-only' will run the tests.
- 'mistral-devstack-non-apache-tempest-ipv6-only' will run the tests.

Story: #2005477
Task: #35905

Depends-On: https://review.opendev.org/#/c/699959/

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

Change-Id: Iacd2d9cb5effde9a801010ce3e5f590f47f8831e

Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.

[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045

Change-Id: If027d55cea9fd88fadbb1539bbe713b2c2a7bd29

Depends-On: https://review.opendev.org/#/c/621470/
Change-Id: I28e7bced65386b01ebb7024a942b95eb5455be6f

Change-Id: Idc39d6f6e367d3dea673d48a160b8314a51394e8

Remove double quoting that suddenly confuses the job.

Change-Id: I58f1943d427c83c72e9bf17f99f3f870ba7d008b