File "/home/zuul/src/opendev.org/openstack/freezer-api/freezer_api/common/exceptions.py", line 73, in handle
    status=falcon.status.HTTP_404,

    AttributeError: module 'falcon' has no attribute 'status'

Change-Id: I3b77a5a3799f066ef189862e75de24b4c25c0569

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: #38522
Change-Id: I16738f205ae235d9d8af2e54395d7decefded7d0

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

As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:

1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.

2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.

Also replace policy.json to policy.yaml ref from doc.

[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html

Change-Id: I066488c47e1bb6502b27b8677988113f66b9b09b

   AttributeError: 'Connection' object has no attribute 'iterdump'

Change-Id: I1bca4617d6d57dd6d62e38b11a109dc87cc6bfcd

Use pylint = 2.6.0 , fix some errors.

Change-Id: I1fdb40c7a8ac986332e10b642ab86799fc5ff78d

Change-Id: Ie452dbdd42ec7ef34993572ac0b456562aabab79

With the removal of screen support,tail_log is deprecated and removed after Queens.

Change-Id: Ia0dadd6cb403e98c988c99935d32804df9b7ed59

Change-Id: I92e67d7ef9366137a4107d0e6de7299478b784c8

The project CI jobs have  Migrated to  Zuul V3 CI jobs.
Remove  these yaml files for zuul v2 CI jobs.

Change-Id: I59bef0e9d072e50a1da9c12b41f6971914ad55bb

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for wallaby.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I1570feb65a279a49133fd70ee3bde6be8a3921ef

Change-Id: I6b79d1e283dd043bf9650e29eb848244fadeb1e1

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

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

Change-Id: I8d4159761acd6468bb5b8c57c6e84497f115c9a4
Sem-Ver: feature

As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).

Fixing:
- bug#1886298
Bump the lower constraints for required deps which added python3.8 support
in their later version.

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

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

Change-Id: I482ac98bc56f0e3cfb8b767f47649da11ed1afab
Story: #2007865
Task: #40184

- use the jobs already defined inside freezer-tempest-plugins
  instead of redefining them locally, as they are the same;
- remove the other legacy jobs, as they are not used and
  the jobs from freezer-tempest-plugins could be directly used
  or adapted if needed.

Change-Id: Iacc4c218c29d44dabbf2bc933291790e7c9b7480

Change-Id: Idde9a450e9ac4ffe786f5233ef22eacd7df6b8eb

Add  DevStak installation  guide for the freezer-api project.

Change-Id: I3187b652da0cf9e0b6211d8317d5cf3e50a4aba3

[openstackdocstheme] overriding configured project name (freezer-api) with
name extracted from the package (freezer-api); you can disable this
behavior with the 'openstackdocs_auto_name' option

Change-Id: Icbe9ceff6ad25dc353a3c574f32b26bc007c7294

writing output... [ 33%] cli/freezer-manager-status
[openstackdocstheme] the 'repository_name' config option has been deprecated
 and replaced by the 'openstackdocs_repo_name' option; support for the former
 will be dropped in a future release
[openstackdocstheme] the 'bug_project' config option has been deprecated and
replaced by the 'openstackdocs_bug_project' option; support for the former
 will be dropped in a future release
[openstackdocstheme] the 'bug_tag' config option has been deprecated and
replaced by the 'openstackdocs_bug_tag' option; support for the former will
be dropped in a future release
writing output... [ 66%] cli/index
writing output... [100%] index

Change-Id: I55903e4f914673aba5ac986b845c2a6504830c19

In new release, the project  is used  python38 to replace python37,
so drop py37,add py38 in tox.

Change-Id: Ie08f9bbb98cd21ebace4cc32c6090f2aa249738d

The stestr[1] is parallel Python test runner designed to execute unittest test suites using multiple processes.
Test cases can be executed faster.

[1]https://github.com/mtreinish/stestr

Change-Id: Ic0b210685535f94a70a175385afdd9f399f4d690

Add publish-openstack-docs-pti job in check/gate CI.

Change-Id: I8bbad3d615a3af29ed05d31a2e1cb1d3b99ae460

Change-Id: I454d94f78c0699fe753f9c2acc72e9c82a52d57e

The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I2728250b2646af93c65ac7f18dbf7600fe5a286c

Previous versions of jsonschema (<3.2.0) doesn't support python 3.8 [1].
Python 3.8 is part of the victoria supported runtimes [2] so we now force
to use jsonschema version 3.2.0 to avoid issues, remove ambiguity and ensure
that everything works with python 3 in general.

[1] https://github.com/Julian/jsonschema/pull/627
[2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria

Change-Id: Ic13321bffe2f7af9324b580bb0e769ce244025a9

New theme of docs respects pygments_style.

more info: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html

Change-Id: I4dc7389756a4bfd6da62841456bf1653637b0371

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

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

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for victoria.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I0a4ea9fd989cb553a5c7c7be0e6631b6cc3b0a50