Repository navigation
RFE: Support for blazar service #3304
Description
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
Activity
github-actions commentedon Feb 17, 2025
Thank you for reporting your first issue! Be sure that we will be looking at it, but keep in mind
this sometimes takes a while.
Please let the maintainers know if your issue has not got enough attention after a few days.
If any doubt, please consult our issue tutorial.
EmilienM commentedon Feb 17, 2025
PRs will be welcomed! note that we heavily rely on CI to trust PRs are well functioning. So please have a look at the Github workflows for each component, and add testing for Blazar as well.
Thanks
winiciusallan commentedon May 15, 2025
@msherman64 Are you working on this? Can I assign it to myself?
msherman64 commentedon May 15, 2025
Go for it! I haven't had time to work on it myself, but would be happy to contribute if you get a stub going.
winiciusallan commentedon May 15, 2025
Since it is my first contribution to the repository, I'll push a WIP pull request to get feedback from core reviewers. If you'd like, you can rebase and push commits.
I've already started working on this, so I will probably have made some progress over this weekend.
winiciusallan commentedon May 16, 2025
@EmilienM What do we need for an MVP? Basic methods (list, get, update and delete) for Leases and Reservations hosts? +doc and unit tests for sure =)
winiciusallan commentedon Jun 2, 2025
hi @msherman64! I opened a pull request with the work that I have done until now. There is still a lot of work to be done, but I'm afraid that I won't have time to put it in over the next months. Feel free to pick the job or ask if you need some help!
barnes-c commentedon Aug 27, 2026
Hi all, I would like to pick this up.
I see that @winiciusallan already did lots of work in #3406 and invites for someone to continue
The MVP question was raised earlier in this thread, Im proposing and you can tell me if it's wrong.
Before I start building on what's already in #3406 I would add a DevStack workflow for Blazar (like you mentioned @EmilienM), and then continue with:
I would leave floating IPs, allocations and resource properties for future follow-ups.
winiciusallan commentedon Aug 27, 2026
Hey @barnes-c, feel free to pick this up, I'll be happy in review your changes!
I agree that having the leases and hosts APIs is a good starting point. We could do this incrementally and add other APIs on demand. Having the bulk of the work done make the rest a little bit easier.
If you need some feedback, we're also on
#gophercloudin the kubernetes Slack workspace. Feel free to ping us there!barnes-c commentedon Aug 27, 2026
Thanks, thats really helpful!
My current plan is:
functional-reservationworkflowreservation/v1/leasesreservation/v1/hostsI joined the
#gophercloudchannel so I will take future questions there :)