bf57492926
If the continuous execution of an event is called just after the lease creation is called, it can fail with the invalid lease status transition error from CREATING to STARTING. This patch adds a check before the event execution whether the lease status of the event is not transitional but stable and pend the execution to the next time if it is transitional. Change-Id: I033dd814d384131de8e7494d22cd42f1ea67112b Closes-Bug: #1820476 |
||
---|---|---|
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/