At a high level, my understanding is that blazar has a nova scheduler filter which gets loaded and can link a server create request with a scheduler hint of the host reservation (lease ID in blazar?) to an isolated tenant host aggregate so that the server is created on that dedicated host.
What I'm unsure of with blazar is if there is a concept of infinite leases, i.e. I want a dedicated host on-demand with no expiration on the lease - I will give it up when I'm done using it.
What overlap exists with the Blazar project and it's concept of dedicated hosts?
https:/ /docs.openstack .org/blazar/ latest/ cli/host- reservation. html
https:/ /docs.openstack .org/blazar/ latest/ specs/pike/ new-instance- reservation. html
At a high level, my understanding is that blazar has a nova scheduler filter which gets loaded and can link a server create request with a scheduler hint of the host reservation (lease ID in blazar?) to an isolated tenant host aggregate so that the server is created on that dedicated host.
What I'm unsure of with blazar is if there is a concept of infinite leases, i.e. I want a dedicated host on-demand with no expiration on the lease - I will give it up when I'm done using it.