16:00:13 <priteau> #startmeeting blazar
16:00:14 <openstack> Meeting started Thu Sep 12 16:00:13 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:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:18 <openstack> The meeting name has been set to 'blazar'
16:00:29 <priteau> #topic Roll call
16:03:42 <diurnalist> o/
16:04:00 <priteau> Hi diurnalist
16:05:12 <priteau> Is Jake planning to join?
16:05:43 <diurnalist> I presume so; I am WFH today so we are not in the same room
16:07:15 <priteau> Maybe he has issues accessing IRC, let's give him a few minutes
16:08:33 <diurnalist> I was wondering is anybody from Blazar going to be at the summit?
16:09:13 <priteau> Yes, there will be Masahito Muroi, Tetsuro Nakamura, and Bertrand Souville.
16:09:20 <priteau> Are you planning to attend?
16:10:33 <diurnalist> I wasn't planning personally, but we're considering if it makes sense for Chameleon to send a rep, possibly Jake
16:12:40 <priteau> We're not yet planning to have technical discussions for Blazar. There will be a Project Update session in the Summit and also a Project Onboarding session in the PTG.
16:14:41 <priteau> We're going to have a virtual PTG, maybe just before or just after the PTG in Shanghai. It would be good to have Jake involved, but it could be very difficult with timezones :/
16:19:29 <diurnalist> Where do the discussions/announcements about what types of activities will happen at the summit for which PTGs?
16:21:42 <priteau> There is usually a page on the wiki that tracks all the Etherpads. For Train it was https://wiki.openstack.org/wiki/PTG/Train/Etherpads
16:22:04 <priteau> There is no such page for Ussuri yet. I assume everyone is busy with releasing Train
16:22:14 <jakecoll> Hey priteau, sorry I'm late
16:22:20 <priteau> Hi Jake
16:23:09 <priteau> For the agenda today I wanted to talk about what we can ship in Train
16:23:13 <priteau> #topic Train release
16:23:27 <priteau> This is the release schedule
16:23:28 <priteau> #topic https://releases.openstack.org/train/schedule.html
16:23:50 <priteau> This week is the deadline for final release for client libraries (so for python-blazarclient)
16:24:36 <priteau> As well as feature freeze in the main service, though we can make exceptions
16:25:52 <priteau> So as priority I would like to release python-blazarclient with 1) support for floating IP reservation update 2) the host allocation patch from Jake
16:26:22 <priteau> jakecoll: Overall I think https://review.opendev.org/#/c/673106/ looks good, but needs a bit of reworking to handle missing parameters
16:26:59 <jakecoll> yea, getting on that now
16:27:37 <priteau> Then for the main service, I think the DB query optimization is good to merge, and hopefully my last revision to the floating IP reservation update patch will be approved by Tetsuro.
16:28:06 <priteau> But I am less worried for the service since we still have a couple of weeks until the rc1
16:29:11 <priteau> jakecoll: Would https://review.opendev.org/#/c/678755/ be sufficient for fixing bug https://bugs.launchpad.net/blazar/+bug/1838025
16:29:12 <openstack> Launchpad bug 1838025 in Blazar "Blazar resource allocations API call very slow (15+ seconds)" [High,New]
16:29:48 <priteau> i.e. would you abandon https://review.opendev.org/#/c/672994/ if Tetsuro's patch merged?
16:30:05 <jakecoll> Yes. I can do that now actually
16:31:02 <jakecoll> it's abandoned
16:32:01 <priteau> Thank you
16:33:01 <priteau> I am afraid it's now to late in the cycle to merge network reservation. If we merge it early in Ussuri, we can release a beta version to make it easier for you to package.
16:35:47 <priteau> For other patches from Chameleon more work is required, some don't pass checks
16:36:49 <priteau> Anything else that we should focus on for the Train release?
16:37:17 <jakecoll> Yea, I wasn't able to get to soft delete
16:38:50 <jakecoll> Not on our end
16:39:00 <priteau> diurnalist: Are you planning to update Chameleon to Train (maybe just for Blazar) soon?
16:40:07 <jakecoll> We're only operating Blazar on stein as of now
16:40:59 <jakecoll> We haven't discuss an upgrade for anything in awhile on Chameleon
16:41:18 <priteau> So you have Stein for Blazar and Rocky for everything else?
16:41:39 <jakecoll> Yep
16:41:39 <diurnalist> yes. i would say train isn't on our radar immediately, but we need to start moving to make sure we keep on top of releases again
16:43:02 <diurnalist> the main addition we still need to talk about would be extracting the usage mechanism. but it sounds like that's still up in the air
16:43:07 <diurnalist> *usage enforcement
16:43:28 <priteau> Yeah, I haven't had any time to look into this.
16:44:00 <priteau> Rocky goes into extended maintenance end of Feb 2020, you might want to use this date as a target for upgrading to Stein or Train
16:46:49 <priteau> I don't think there is any requirement in Blazar for other services being more recent than Rocky, so you should be able to run Blazar Train with other services on Rocky
16:48:08 <priteau> That's all I had to discuss today. Looking forward to your updated client patch jakecoll!
16:50:17 <priteau> Thanks for joining
16:50:22 <priteau> #endmeeting