563e4a8da2
This patch adds global_request_id to the constructor for nova client, keystone client, neutron client and placement client which will pass the global_request_id to these respective services on all API calls. Supporting global_request_id makes debugging easier when requests reach many different OpenStack services. The blazar global_request_id will be sent to these services in the request header like below and it will be available with context.global_request_id: -H "X-OpenStack-Request-ID: req-1a9b7b24-02ed-4400-bcc3-cc1bcbb59147" Sample log output of neutron service for ``POST v1/floatingips`` API which logs global request ID `req-e19f8f4f-40e7-441e-b776-7b43ed15c7dd` is shown at: http://paste.openstack.org/show/753807 Oslo spec I65de8261746b25d45e105394f4eeb95b9cb3bd42 Change-Id: I5bb3631c4fb178293ee8eefbe1aa8b819a196a9f
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/