We're (Chameleon) heavy users of Openstack Blazar, and I wanted to propose adding support for it here, in order to consume gophercloud downstream prometheus exporters and terraform.
How "complete" would an implementation need to be? From the blazar APIs, even supporting only GET v1/leases and GET v1/os-hosts would be useful.
Previously this came up here: #316, but it requires the user to specify a reservation UUID manually; consuming the Blazar API would allow more flexible use in terraform such as "get a reservation ID from one of my active leases".
Thanks!
-Mike
We're (Chameleon) heavy users of Openstack Blazar, and I wanted to propose adding support for it here, in order to consume gophercloud downstream prometheus exporters and terraform.
How "complete" would an implementation need to be? From the blazar APIs, even supporting only
GET v1/leasesandGET v1/os-hostswould be useful.Previously this came up here: #316, but it requires the user to specify a reservation UUID manually; consuming the Blazar API would allow more flexible use in terraform such as "get a reservation ID from one of my active leases".
Thanks!
-Mike