16:03:15 <priteau> #startmeeting blazar
16:03:15 <opendevmeet> Meeting started Thu Aug 12 16:03:15 2021 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:15 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:15 <opendevmeet> The meeting name has been set to 'blazar'
16:03:19 <priteau> #topic Roll cal
16:03:20 <priteau> #topic Roll call
16:03:28 <priteau> Hello.
16:03:49 <mppowers> hello
16:04:46 <priteau> Just you today or Jason as well?
16:05:08 <mppowers> I sent him a ping
16:06:06 <priteau> Hi diurnalist
16:06:36 <priteau> #topic Yoga PTG
16:07:08 <priteau> Just a small announcement: for the upcoming PTG in October, I have created an Etherpad to gather discussion topics
16:07:13 <priteau> #link https://etherpad.opendev.org/p/yoga-ptg-blazar
16:07:42 <priteau> Remember to book time in your calendar: Thursday, October 21, 2021 15-17 UTC
16:08:03 <priteau> And register (free) if not done already: https://openinfra-ptg.eventbrite.com/
16:10:02 <priteau> #topic Xena release
16:10:44 <priteau> Good news, we merged the openstack client support, thanks again mppowers
16:10:51 <diurnalist> :clap:
16:11:01 <mppowers> woo!
16:12:08 <priteau> What should we focus on next for Xena? Is the Horizon dashboard update a good candidate?
16:13:37 <mppowers> Yes, I think it is. I have not had time to work on this. First, I need to check if all the required functionality for it from Chameleon's blazar fork is upstream.
16:13:50 <priteau> It could be too late in the cycle to fully merge it, depending on how advanced it is in Chameleon.
16:14:23 <priteau> Alternatively we can focus on annoying bugs, to get a head start on the pain points goal
16:15:34 <diurnalist> mppowers: if i'm not mistaken, much of the dashboard stuff could be proposed. i think the main issue was we can't show the dropdown filter (b/c that requires an API we haven't submitted upstream, the API for capabilities) and maybe some of the extra fields shown in the tooltip
16:16:19 <mppowers> I don't think blazarclient supports listing allocations, which are required for the calendar.
16:16:49 <priteau> Is it this patch? https://review.opendev.org/c/openstack/python-blazarclient/+/673106
16:19:13 <mppowers> Yes, I think this patch is for the same thing, but our Chameleon version looks pretty different right now.
16:19:50 <diurnalist> blarg
16:20:15 <diurnalist> does Horizon have to use the blazar client? is that how it's normally done? couldn't it go through the raw keystoneauth adapter/session
16:20:55 <priteau> It's more about the HTTP queries than the auth itself.
16:21:15 <diurnalist> yes i know, what i mean is session.get("...") as opposed to blazar.host.allocations.list()
16:21:39 <mppowers> I could focus on getting allocations working with the client first, and the move the dashboard stuff upstream
16:21:43 <diurnalist> not trying to cut corners, it does seem like there's not a strong reason why horizon should be coupled to the client implementations and not just use the HTTP API directly
16:22:07 <priteau> I didn't realise you could do queries with the session object directly
16:22:32 <diurnalist> yep, in fact there is no python API client for placement, they just say "use keystoneauth"
16:22:50 <diurnalist> osc-placement is basically shims for this that plug in to openstacksdk
16:23:04 <priteau> I think it's due to the existing pattern in horizon, which e.g. uses novaclient or cinderclient
16:23:27 <mppowers> I'll look into doing that then for the API calls using allocations.
16:23:38 <priteau> But I don't think it's a blocker that the dashboard doesn't use blazarclient
16:26:09 <priteau> Don't you need API changes to the allocation endpoint to show allocations for other users? Unless the calendar was admin-only?
16:28:31 <diurnalist> that's another good point. it could be controlled via blazar's keystone policy, but then i guess the experience of users not allowed via the policy is not good; we would have to update the dashboard code to render some nicer error state if the allocations cannot be fetched due to permissions
16:30:36 <priteau> By default users see only their own allocations. This could still be a useful display in a context where the cloud is large enough that there is no contention for resources.
16:31:19 <diurnalist> ok
16:33:15 <priteau> Would need to sketch it out to see what it would look like
16:36:58 <priteau> So what steps do we need to take for this? 1) Extract the non-Chameleon-specific features from the current implementation 2) Check API requirements 3) Adapt API and/or calendar
16:38:03 <diurnalist> mppowers: what do you propose?
16:40:13 <mppowers> I was thinking first comparing the Chameleon allocation API to see if there is anything different. If there is anything missing that blocks some of the calendar, that can be updated later. I'll work on getting the calendar working with the current blazar API.
16:41:41 <diurnalist> ok, that sounds like a good plan to me. some of the enhancements to the calendar, such as the filter dropdowns, can be separate patches
16:41:49 <priteau> absolutely
16:41:57 <mppowers> Yes, my plan is a MVP calendar for now
16:42:07 <mppowers> with what works in blazar
16:44:02 <priteau> Should we resume this discussion once you have had the chance to submit some code?
16:44:53 <mppowers> Yes, that would be good
16:45:36 <priteau> #topic Review requests
16:46:09 <priteau> diurnalist: since you are a core reviewer now, I've tried not to merge anything major without your approval
16:46:29 <priteau> There is this small patch pending: https://review.opendev.org/c/openstack/blazar/+/802652
16:46:53 <diurnalist> thanks, i will have a look asap. i need to set up some mail notifications i think
16:48:00 <diurnalist> approved
16:49:11 <priteau> I've added you as reviewer so you should have received an email at that point, but it's easy to miss if you've got many
16:49:28 <diurnalist> i also ensured that i'm added to anything that happens on blazar repos now
16:50:02 <priteau> Thanks
16:50:06 <priteau> #topic AOB
16:50:11 <priteau> Anything else to share today?
16:50:16 <priteau> If not we can finish a bit early
16:50:30 <mppowers> nothing here
16:50:41 <diurnalist> nothing here either
16:52:38 <priteau> Thanks both for joining
16:52:57 <priteau> Ah, I had something
16:53:08 <priteau> For the next meeting I will be on holiday
16:53:30 <priteau> So let's meet again on Sep 9
16:54:01 <priteau> If you want to discuss the calendar before this, I am available via email or IRC of course
16:54:19 <priteau> #endmeeting