8e6f9c7186
Under Python 3 print is a function, and the linter does not want to have white space between the function name and the paren indicating the call. Remove the space. Change-Id: I1f262e5d9ff35b6824483cdc401b3f7a80798212 Signed-off-by: Doug Hellmann <doug@doughellmann.com> |
||
---|---|---|
api-ref/source | ||
config-generator | ||
devstack | ||
doc | ||
etc/freezer | ||
freezer_api | ||
playbooks/legacy | ||
releasenotes | ||
specs | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.pylintrc | ||
.testr.conf | ||
.zuul.yaml | ||
LICENSE | ||
README.rst | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
OpenStack Freezer-API
OpenStack Freezer-api is a RESTFUL API to Store information and metadata about Backups, Jobs, Clients, Sessions. It helps keeping backup/restore jobs organized and maintain the status of the backups.
To learn how to use Freezer's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Freezer, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
Any new code must follow the development guidelines detailed in the HACKING.rst file and OpenStack general development guidelines, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for freezer can be found at: