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
- Update classifiers
- Update requirements, no need for python_version anymore

Change-Id: I28b14bfc8430d75271308ee91925e58b55b6dcc2

Blazar APIs support directly fetching a resource (whether host, floating
ip, or lease) with its ID. However, the default logic for this includes
a block that supports additionally looking up the resource by name (to
allow looking up e.g., a lease by it's name.) This requires fetching the
entire list of all resources and iterating over them until a match is
found, which is very inefficient. Moreover, this branch would be taken
even if the input was already a UUID.

This commit changes that behavior so that if a UUID is provided, it is
used to directly fetch the resource, which seems to be what the original
intent was in the first place.

Change-Id: I5b1ccf4abfe4aa9068bc011764cac4b3507ef697

1. 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.

2. pbr hasn't need the hook configuration since forever [2]

[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
[2] https://opendev.org/openstack/pbr/commit/c84876dc0f559a66fec19b2f81f5717204b253e2

Change-Id: I22e930f9876ca29750093a78e4bf3a7d4a479eb9

Python 2 is no longer supported. Python 3 is required.
This patch stops testing with Python 2 and issues the release note.

Change-Id: I7dc416927ea23d581dbee366d54a733ee53498cf

Change-Id: If7bb34575b5dae5896503b8e134bb5721cff21f3

Add file to the reno documentation build to show release notes for
stable/train.

Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.

Change-Id: Ie9a285b88b2544ff7f73ed9de7aade432b681d08
Sem-Ver: feature

The lease-update command needs to know about all possible keys that can
be passed as reservation parameters. Also treat required_floatingips as
a list, like in commit 91839508.

Change-Id: Iad95ebf662fb052000f05aa3d76f76308704fd1d
Related-Bug: #1843258

An API request to create a floating IP reservation is expected to pass
the required_floatingips parameter as a list, not as a string. Modify
the CLI to parse required_floatingips as a JSON array so it can be
passed to the API in the right format.

Change-Id: Ia84ceb881f0889266c8f0349a1ffb047597bac2d
Closes-Bug: #1843258

Change-Id: I2974b600d1f65e91e490eb80029a67e601d6a78e

Change-Id: I84d9e97e26f7569767deac4144d57590896047fc

The network_id parameter was not defined in CREATE_RESERVATION_KEYS. As
a result, it could not be parsed by the command-line client.

Change-Id: Icad6533ea32967601cf8d3bd4ccee659bb0b5abd
Closes-Bug: #1840759

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: Ibc4be4c59c2dca995f1999879ea2a9e70b129f7f
Story: #2005924
Task: #34199

Change-Id: I44b9d8003566793e54ebdc15cbb95450841fd3cd

Change-Id: I7a73a4e7d2026eba2d0a3d6dfe9db42879ff6416

Change-Id: I30a1b8d6a5b3c8e402fc9c3671065ffe13bcbead

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.

All the integration testing has been moved to
Bionic now[1] and py3.5 is not tested runtime for
Train or stable/stein[2].

As per below ML thread, we are good to drop the py35
testing now:
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html

[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html
[2]
https://governance.openstack.org/tc/reference/runtimes/stein.html
https://governance.openstack.org/tc/reference/runtimes/train.html

Change-Id: I08d1764ad06ae1a30f5c3e30437823459bac7ec8

Add file to the reno documentation build to show release notes for
stable/stein.

Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.

Change-Id: I50cd486f57ba1ce7adaae87866a720f14d7581f2
Sem-Ver: feature

This is a mechanically generated patch to add a unit test job running
under Python 3.7.

See ML discussion here [1] for context.

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135626.html

Change-Id: I7145092da763821d855d39b71db1e12efc91e18d
Story: #2004073

Change-Id: I90fb45e5065f13e3a5cc803d5caf42f0e9653da1

Small cleanups:

* Use openstack-lower-constraints-jobs template, remove individual
  jobs.
* Sort list of templates

Change-Id: I432310cdede37a00be894541fff7f23bc10220f5
Needed-By: https://review.openstack.org/623229

Change-Id: I3edee36fe577fe60052749858dd994a5fea7fff8

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

Change-Id: Ie473cea777ff3a1707e7e7a69daacf85751996f8

Change-Id: I57233628a7bf7d49fd7cb1b87c25b96c37cdb015

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: I1b9cc38fceb099e30c46d8c5f2ac84fbffabaf76
Story: #2002586

Change-Id: Ifbc3535ca69e323018c59fc4283b7631cd1b030a

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: I9280e4a921c825428cae9f0df0db532fd96fb77b
Story: #2002586
Task: #24286

This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs 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: Ie5e3a45baa15a4508101db05d427c10b34d6a708
Story: #2002586
Task: #24286

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: I851be19e8a3cd925067ea096d9265008d0585c48
Story: #2002586
Task: #24286

Change-Id: Id97e2836e9f55de610e580ccbabe07cf00d32c47

The resource variable, originally containing the resource type, i.e.
'lease', was reassigned with a lease object before being used in the
exception message. As a result, the message displayed a dictionary of
lease values, instead of "type 'lease'".

Change-Id: If4cb03cfb4a895c11e3952f0f1b79e0c7d14de8c
Closes-Bug: #1786030

Change-Id: I5fe0de436dd5e2c21ab9eb08b47c1995b5154a53
Closes-Bug: #1784038