16:00:21 <priteau> #startmeeting blazar
16:00:22 <openstack> Meeting started Thu Nov 21 16:00:21 2019 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:26 <openstack> The meeting name has been set to 'blazar'
16:02:07 <priteau> #topic Roll call
16:11:45 <priteau> Hi jakecoll
16:11:58 <jakecoll> good morning
16:12:27 <jakecoll> oh my, I think I now realize daylights savings has me confused
16:12:43 <jakecoll> I didn't update my calendar
16:13:46 <priteau> To avoid this you can define the meeting at the UTC time. You can download an ICS file from http://eavesdrop.openstack.org/#Blazar_Team_Meeting
16:14:09 <priteau> We discussed Ussuri planning at the meeting earlier this week
16:14:11 <jakecoll> oh nice
16:15:02 <priteau> We set some tentative schedule on the priority features, it's at the top of https://etherpad.openstack.org/p/blazar-ptg-ussuri
16:15:42 <priteau> We've marked some items as owned by you (network reservation and calendar), do you think the tentative schedule is feasible?
16:16:15 <priteau> In particular, updated network reservation spec by end of November
16:16:26 <priteau> I realize that may be difficult with Thanksgiving coming up.
16:16:55 <jakecoll> Yea, I think there were only some minor edits for that though so shouldn't be too much of a problem.
16:18:02 <priteau> And Tetsuro asked if we could get a spec for the calendar, in particular to describe limitations
16:18:47 <jakecoll> Does calendar view only work for baremetal?
16:19:12 <jakecoll> That would make sense
16:19:33 <jakecoll> If it is by end of year, that should be fine
16:19:35 <priteau> It should work fine for host reservation whether baremetal or KVM, but for instance reservation the current visualization is not appropriate since there are multiple kinds of resources to consider (CPUs, memory, disk)
16:20:03 <jakecoll> right right
16:20:13 <priteau> I think it's better to have something than nothing, so the spec would just explain what is displayed and what isn't
16:22:24 <priteau> If you want we can make a common draft together before submitting
16:22:52 <priteau> I can create an Etherpad for it
16:22:54 <priteau> https://etherpad.openstack.org/p/blazar-spec-calendar-view
16:23:06 <jakecoll> Yes, that would be helpful
16:23:23 <jakecoll> thank you
16:24:37 <priteau> I also wanted to talk briefly about:
16:24:43 <priteau> #topic Stable backports
16:24:59 <priteau> I believe you are using Stein and planning to migrate to Train soon?
16:25:15 <jakecoll> yea, working on that now. Already have dev running blazar Train
16:26:07 <priteau> We learned of a cloud planning to run a small Blazar deployment using Rocky
16:26:20 <jakecoll> Which cloud?
16:26:25 <priteau> Nectar
16:26:31 <priteau> So if you run into bugs and have relevant fixes, please share so we can backport
16:26:40 <jakecoll> Oh nice. I met one of the guys from there. Forget his name.
16:27:36 <jakecoll> I think the allocations api optimization would be the main one
16:28:10 <priteau> Not really a bug fix but we can consider it.
16:28:35 <jakecoll> I imagine that call would take even longer if you've got a lot of intance reservations
16:29:40 <priteau> Feel free to submit a backport patch.
16:30:55 <jakecoll> Can do. We had this running on rocky
16:31:45 <priteau> Thanks
16:31:58 <priteau> Anything else you would like to discuss today?
16:33:10 <jakecoll> Not on my end
16:33:29 <priteau> Thanks for you time!
16:33:36 <priteau> Bye
16:33:37 <priteau> #endmeeting