4253cb0fd2
We are going to add API tests using Gabbi to the blazar-tempest-plugin. But if the Gabbi tests are executed by different workers, their order gets violated. This patch changes Tempest concurrency to 1 to ensure the Gabbi tests are executed in the order specified in the YAML file. This can increase test execution time, but it should be negligible. Change-Id: Id4dc3cc8640e8f902f96130a85e50008b5e8b96d |
||
---|---|---|
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/