* 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

1. Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
2. Remove unncessary "=="

Change-Id: I0008ca81b9c753d26ef97e10957a1745d340d2c0

build-openstack-sphinx-docs jobs are obsolete since some time,
use the newer build-openstack-docs-pti jobs instead - using
a template.

Update tox.ini to use proper sphinx-build invocation.

Change-Id: Idfa081711a24a6076e8b9a0ca770423d6fa62f94

Thorough replacement of git.openstack.org URLs with their opendev.org counterparts.

Change-Id: Id6768e790fbcf4e73cde4e479e0f31ed5e1a9b8d
Closes-Bug: #1826041

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

Change-Id: I0378297e099412191a4adc41e53b0eb23f6c43ae

oslo project provide jsonutils, and mistral-tempest use it in many place[1],
this PS to update the remained json module to oslo jsonutils for
consistency.

[1]: https://github.com/openstack/mistral-tempest-plugin/search?utf8=%E2%9C%93&q=jsonutils&type=

Change-Id: I3872e3d10e103439fdf4005785d46ed580e520af

Change-Id: I1d8a79faf168391fba1058c9d0ad91048b250a5e

Change-Id: Ie1fc3ed3ef23959f9d266561eb4fd749209a139b

Change-Id: I58b984c73b372f6301608f79ac634e7950390fb2

Mailinglists have been updated. Openstack-discuss replaces openstack-dev.

Change-Id: I7652a67bf577003e9f33e6f68699a3f8176c7d01

Change-Id: Ie26054678e0f3fa06b467ffd8622591e10321b47

Without this change, the result can be accurate but in the wrong order,
causing a failure like:

    AssertionError:
    Lists differ: ['greeting', 'farewell'] != ['farewell', 'greeting']

Change-Id: Ia0f3e9fa03834feb4c87c6ac50930a0d533a19bd

This is a mechanically generated patch to add a unit test job running
under Python 3.6 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: I86d27bc17d3e6e96aa40845d4db092a930ff45a0

In setup.cfg file the python 3.5 is added

Change-Id: Id636f96c3a23bc719681c000bc55743e647c9a66

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: I1625aa8becf4b5a4d59c3e0a0ffc1eab490f1881
Story: #2002586
Task: #24311

With concurrent test executions it is possible that namespaced and
non-namespaced tests run at the same time, making it flaky whether
the name of the workflow is enough to identify the workflow. Using
the id should work in all cases.

Change-Id: Ib0e7d31f9a983c723704b64b1c46940aace545d7