90993a3872
We have migrated the zuulv3 job to Bionic during Dec/Jan month. - http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000837.html - https://etherpad.openstack.org/p/devstack-bionic But that effort does not move all gate job to Bionic as there are large amount of jobs are still legacy jobs. All the legacy jobs still use Xenial as nodeset. As per the decided runtime for Stein, we need to test everything on openstack CI/CD on Bionic - https://governance.openstack.org/tc/reference/runtimes/stein.html Below patch move the legacy base jobs to bionic which will move the derived jobs automatically to bionic. These jobs are modified with branch variant so that they will use Bionic node from stein onwards and xenial for all other stable branches until stable/rocky. - https://review.openstack.org/#/c/639096 This commit rename the ubuntu based gate job so that we do not need to rename them on every new distro migration. Making failed job n-v till story#2005227 More Details: - https://etherpad.openstack.org/p/legacy-job-bionic - http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003614.html Depends-On: https://review.openstack.org/#/c/639096 Change-Id: I9dd6e178e512c1bba3b6de65532be13d321cd9de |
||
---|---|---|
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: