Comment 5 for bug 1771523

Answers questions in the comment #3 from blazar team.
I also left some comments in a related spec https://review.openstack.org/#/c/593475 about how blazar works with aggregates.

> a server create request with a scheduler hint of the host reservation (lease ID in blazar?)

Well, to be accurate, not lease ID but reservation ID.
For example, 1 “lease”(start_time-end_time) can include 3 “reservation”s, each of which corresponds to 1 host occupancy.

> What I'm unsure of with blazar is if there is a concept of infinite leases

We don’t have such an “infinite” concept explicitly, but you can use a hack to create a lease with something like:

* start_time: "2018-09-01 21:00"
* end_time: “9999-12-31 23:59”

One can delete the lease when he/she doesn’t need it anymore. Deleting a lease during its lease time is supported.