8d2f4a0f0e
This patch adds a valid state transition from ERROR to TERMINATING, which should allow a lease in the ERROR state to at least attempt to clean itself up upon lease end. If this state transition is not allowed, leases in the ERROR state effectively will not be cleaned up and their hosts will stay in the corresponding aggregate instead of being returned to the freepool. This is compounded by the fact that leases can easily go into ERROR state because of bug https://bugs.launchpad.net/blazar/+bug/1786031. Change-Id: I1fbd922d921b7a643379c93ca6b2ebb4edde9c7a Closes-Bug: #1793560 |
||
---|---|---|
api-ref/source | ||
blazar | ||
devstack | ||
doc | ||
etc/blazar | ||
playbooks/legacy | ||
releasenotes | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
.zuul.yaml | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
lower-constraints.txt | ||
pylintrc | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
Blazar
Blazar is a resource reservation service for OpenStack. Blazar enables users to reserve a specific type/amount of resources for a specific time period and it leases these resources to users based on their reservations.
The following two resource types are currently supported:
- Compute host: reserve and lease with a unit of a whole host
- Instance: reserve and lease with a unit of a flavor
Please see the following resources to learn more.
API
See Blazar API reference.
Operators
To learn how to deploy and configure Blazar, see the installation guide and the configuration reference.
Developers
To learn how to contribute to Blazar, see the contributor guide.
Other Resources
- Source code:
- Blueprints/Bugs: https://launchpad.net/blazar
- Documentation: https://docs.openstack.org/blazar/latest/
- Release notes: https://docs.openstack.org/releasenotes/blazar/