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

* Remove six usage
* Remove python 2.7 stanza from setup.py
* Update supported python versions in setup.cfg
* Remove i18n related sections in setup.cfg
  as tempest-horizon has no translation support
* Remove unused requirements (oslo_log and babel) from requirements.txt

Change-Id: Ifd530546bfb5ae25e01e72a0e3c02f963d9d04d2

Hacking 3.0 was just released with minor changes, update to the new
version.

Change-Id: I8153c333e8e65cd9469e490a2841a691a269303c

* Update the horizon URL to the new one after doc migration
* Use https instead http
* Adjust title marker length to match the title length

Change-Id: I9c2280793bd8d6496224e36dffd479e1f3732db0

* Move basepython to [testenv] which is a place to define common things
* Move upper-constraints from install_command to deps
* Update the min version to 2.0 to allow http links in deps
* Cleanup unused tox envs ('cover' and 'debug')
* Drop unnecessary envs from envlist (only pep8 is used now)

Change-Id: Ie915a93b824331407a48affcbd31076d6a7cccfa

We don't provide any sphinx documents as we cover horizon specific
topics in the horizon repository. The current version is just from
the cookiecutter and is never maintained since created.
README and CONTRIBUTING.rst would be enough.

Change-Id: I60c6e64e771f4e6bd3482a4d6a2a37228dde98b9

Update hacking to latest version to catch Python 3 problems.

The existing entries in flake8 ignore are dropped
as they are unnecessary.

Change-Id: I8e268f3852ad7acf4805f8ef7e4cbe25a90054a0

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.

Mailinglists have been updated.
So, replacing openstack-dev to openstack-discuss

Change-Id: I8cf824d252a2bd3f5640c710dc343535cab771e3

Change-Id: Id57e35ec7fd058a85953f3154d0be54934fa6e9b

This opiton was deprecated more than three years ago so it's safe to
remove it.

Change-Id: Id65e439871c800068e26797781365b3cd749642d

We want to default to running all tox environments under python 3, so
set the basepython value in each environment.

We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.

We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.

Change-Id: I8f0602bc84aca649bdd70495286327c41c4d00ce
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

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: I604943aff8e732d544dffc85881e682e2b4d7d55
Story: #2002586
Task: #24299

Change-Id: I6be0829340cf8057f83ef58d4866072467f8c21a

According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
So we should switch to stestr.

[1] https://etherpad.openstack.org/p/YVR-python-pti

Change-Id: I6c6e1b3873a71d3b069f0c0bc45d9ba9885c2886

Tempest uses stestr since Iff4abef50178bdc83b868eed4a906e22d790762b was
merged. This patch chaned README to fix instructions for a default
configuration

Change-Id: I90860c4b8e3a0cfdee780fc587d9af21b1f36956

In Python 3, get_reponse returns a bytes object, not str, so we
have to encode() and decode(), otherwise it fails. This fixed
issues running the tests in Debian.

Change-Id: Ifc18bb48e27cee96864e3a9b64d8a4fd294a912b

We want to default to running all tox environments under python 3, so
set the basepython value in each environment.

We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.

We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.

Change-Id: I4ef8678c433cc593db64f596a320d16bc1215eb1

test_basic_scenario should run in smoke set

Change-Id: Ife5abf3afabc4f44be3daed22279edc5e96b5bdb

Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.

Change-Id: I995154c056dd99b3a2c0ee9f7ddd9077e5686b79

Change-Id: I3c6109df15480d5fbee1d420d573a4f529022d91

Change-Id: I9648255a9bed8c75902763cbcf02ec2638fabcbd

Instead of looking at Python major and micro versions, check for the
required ssl.create_default_context function directly.

Change-Id: I6ef528a79d8ff6ff649e8f66f2d11d418e87d9d7

Read-only property 'os' has moved to 'os_primary' in version 'Pike' and
will be removed in version 'Queens'

Change-Id: Ice03458c69d0e107dac6f6735391c3e8567cf855