09:00:49 <masahito> #startmeeting blazar
09:00:50 <openstack> Meeting started Tue Jul 24 09:00:49 2018 UTC and is due to finish in 60 minutes.  The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:54 <openstack> The meeting name has been set to 'blazar'
09:01:08 <tetsuro> o/
09:01:09 <masahito> hi blazar folks, time to blazar meeting :-)
09:01:17 <masahito> #topic RollCall
09:01:43 <priteau> o/
09:01:44 <hiro-kobayashi> o/
09:01:46 <bertys> o/
09:02:01 <masahito> tetsuro, priteau, hiro-kobayashi, bertys: hello
09:02:08 <masahito> Today's agenda is
09:02:18 <masahito> 1. Rocky-3 milestone
09:02:28 <masahito> 2. Project Update in the Berlin
09:02:32 <masahito> 3. PTG schedule
09:02:39 <masahito> 4. PTL election for Stein
09:02:44 <masahito> 5. AOB
09:02:47 <masahito> anything else?
09:03:27 <masahito> Lots of items, but most of these are just announcement.
09:04:45 <masahito> #topic R-3 milestone
09:05:48 <masahito> This week is R-3 milestone week. And final release week for pythonclient as well.
09:06:57 <masahito> I plan to push a patch for tagging 2.0.0.0b3 for blazar repo tomorrow and put 2.0.0 for python-blazarclient repo
09:07:47 <masahito> Does someone have any patch to go before r-3?
09:08:17 <masahito> I can see no patch for blazarclient in the gerrit.
09:08:20 <priteau> I noticed that the version number for blazar-nova got changed to 1.1.1
09:08:29 <masahito> right.
09:09:16 <priteau> The reason is in comments at https://review.openstack.org/#/c/583159/
09:09:23 <masahito> The release team asked me blazar-nova shouldn't upgrade 1.x.y to 2.0.0 because no code change from 1.1.0
09:10:58 <priteau> I am working on a patch to add DB soft delete to Blazar. It's almost done but we may want to keep it for early Stein cycle
09:11:36 <masahito> Of course, we have code change for blazarclient and blazar server. So it's allowed to update the major version.
09:11:52 <masahito> priteau: Nice!
09:12:36 <tetsuro> I have no patch locally for blazar client
09:12:48 <masahito> I'm always thinking it's good to use soft delete instead of hard delete.
09:12:56 <priteau> Oh wait, I have one for python-blazarclient
09:12:59 <masahito> tetsuro: thanks
09:13:48 <priteau> I can submit my patch today
09:14:14 <masahito> okay, will check it and try to merge it before r-3
09:14:14 <priteau> It's about setting the start_date to a better value to avoid some failures
09:14:52 <masahito> thanks
09:15:16 <tetsuro> sounds good
09:15:40 <masahito> For blazar server repo, we have two big features, one is allocation API and another is placement-api support.
09:16:55 <masahito> The placement-api support doesn't touch the existing code now, so I think it's okay to merge even after r-3.
09:17:23 <masahito> Of course, unless it doesn't change current code base.
09:18:09 <masahito> s/current code base/ lots of code base/
09:18:31 <priteau> +1
09:18:41 <hiro-kobayashi> +1
09:18:45 <masahito> If possible, I want to merge the allocation API patches even after r-3.  How do you think?
09:19:08 <masahito> It touches some of current code base, especially host APIs.
09:19:44 <priteau> I think it's fine since we've been discussing it for a while
09:19:49 <masahito> It's just GET type of API.
09:20:03 <priteau> Also, it's only new APIs, no change of format / values for existing endpoints
09:20:59 <priteau> The client should remain completely compatible
09:21:20 <tetsuro> "no change of format / values for existing endpoints" Okay, this sells me.
09:22:11 <priteau> Maybe we can mark the new API as experimental if we're not sure it's tested enough
09:22:19 <masahito> Thank.
09:23:02 <masahito> priteau: right. I'm thinking to add a releasenote that says it's an experimental release.
09:23:50 <masahito> anything else?
09:24:22 <masahito> all right.
09:24:32 <masahito> #topic Project Update in the Berlin summit
09:25:06 <masahito> I confirmed that the Berlin summit has project update session by foundation stuff.
09:25:45 <masahito> The number of slots are not decided yet. Once it's been fixed, they will announce it to PTL.
09:27:09 <masahito> it's just a fyi
09:27:32 <hiro-kobayashi> thank you for confirming it
09:27:42 <priteau> Thanks masahito for looking into it
09:27:56 <masahito> Let's move on to next :-)
09:28:06 <masahito> #topic PTG schedule
09:28:46 <masahito> The PTG schedule is officially announced. The Blazar team meeting is placed on Monday and Tuesday.
09:28:52 <masahito> https://www.openstack.org/ptg/#tab_schedule
09:29:52 <masahito> I'll be there from Sunday. So it's okay to start from Monday morning.
09:30:15 <tetsuro> me too
09:30:37 <masahito> And feel free to add the PTG topic: https://etherpad.openstack.org/p/blazar-ptg-stein
09:31:07 <masahito> I forgot to announce the etherpad page in openstack-dev ML. I'll do that.
09:32:14 <tetsuro> thx!
09:32:32 <masahito> any comment?
09:32:39 <masahito> if nothing we can go next.
09:33:44 <masahito> #topic PTL election for the Stein cycle
09:34:11 <masahito> Stein PTL election will happen soon. https://governance.openstack.org/election/
09:34:51 <masahito> The nomination starts in half of day and end at 31 Jul.
09:35:42 <masahito> If you're interested in that, don't forget to nominate :-)
09:36:46 <masahito> any comment or question?
09:38:44 <masahito> #topic AOB
09:39:08 <masahito> Does someone have something to share or discuss?
09:39:39 <priteau> My client patch is ready for review!
09:39:40 <priteau> https://review.openstack.org/#/c/585189/
09:40:01 <masahito> priteau: Nice, thanks
09:42:15 <tetsuro> I found nova should be updated to use the latest microversion of placement here https://github.com/openstack/nova/blob/master/nova/scheduler/client/report.py#L51 to enable blazar's custom resource on flavor extra specs
09:43:45 <tetsuro> so I -W'ed the top of the patch in the series https://review.openstack.org/#/c/584744/, but others can go.
09:44:22 <tetsuro> I should address some merge conflicts and hiro's feedback though.
09:44:28 <masahito> tetsuro: thanks for letting me know
09:44:55 <tetsuro> Yup, just FYI.
09:45:26 <masahito> The W-1 patch looks changing the instance reservation plugin. So could wait until S cycle.
09:46:01 <tetsuro> Ack. Fair point.
09:46:40 <masahito> Okay, I share my update.
09:47:27 <masahito> I pushed the allocations API patches. It enables to call the List and Get APIs.
09:48:20 <masahito> And https://review.openstack.org/#/c/585187/ also makes the APIs support lease_id query parameter.
09:49:06 <hiro-kobayashi> cool! thank you!
09:49:40 <masahito> I plan to push patches to support reservation_id and terminated in this week, then put the releasenote patch on top of these.
09:49:45 <masahito> that's from my side
09:50:36 <masahito> last 10 mins
09:51:37 <masahito> anything else?
09:54:01 <masahito> looks nothing more.
09:54:15 <masahito> Let's finish early today.
09:54:24 <masahito> Thanks all!
09:54:44 <masahito> See you in next week ;-)
09:54:51 <masahito> #endmeeting