7dc9a6a7bf
In Nova, "service host" is where nova-compute is running and "hypervisor_hostname" represent each physical node that the virt driver reports. They can be different in some of the hypervisor backends where one nova-compute corresponds to multiple physical nodes. Blazar holds the values separately as "service_name" and "hypervisor_hostname". Since Nova aggreate is associated to nova-compute service, we used "service_name" with aggregate solution for reservation. However, now we can use "hypervisor_hostname" with placement api solution for reservation. This patch switches it. Change-Id: I0e089c764e81894f065872e7b44a4ea8cfa49bd6 Closes-Bug: #1814594
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/