09:02:24 #startmeeting blazar 09:02:25 Meeting started Tue Aug 28 09:02:24 2018 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:02:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:02:28 The meeting name has been set to 'blazar' 09:02:37 #topic RollCall 09:03:28 o/ 09:03:35 o/ 09:03:48 Hello masahito and tetsuro 09:04:18 Today's agenda: 09:04:26 1. Rocky release 09:04:29 2. PTG meeting agenda 09:04:32 3. Team photo at PTG 09:04:36 4. Team dinner at PTG 09:04:41 5. python3-first goal 09:04:44 6. Berlin Summit 09:04:48 7. AOB 09:04:51 Anything else? 09:06:11 Let's start then 09:06:21 #topic Rocky release 09:06:51 The Rocky coordinated release will happen on 30 August 2018, according to https://releases.openstack.org/rocky/schedule.html 09:06:58 That's on Thursday this week. 09:07:54 Any pending actions to complete release, like writing new release notes? 09:08:22 not from me 09:08:32 not from my side 09:09:08 masahito: Will you handle tagging the Rocky final release? 09:10:05 IIRC, sean adds the Rocky final release tag for all projects. 09:10:23 And wants PTL +1 for his patch. 09:10:30 I see. 09:10:40 Will you add the +1 then? 09:10:44 Or should I do it? 09:11:33 ah, I'm not sure who should do. In the Queens release, he added me to the reviewer. 09:12:12 We'll see who he adds. I will keep an eye on open reviews mentioning blazar. 09:12:19 Is it in the openstack/releases repo? 09:12:24 yes. 09:12:51 I try to check the repo, too. 09:13:41 Do you know what's happening with releasing the client with bugfix: https://review.openstack.org/#/c/590760/ 09:15:14 I think the stable/rocky branch for the client was already freezed at the client release. So we should release 2.0.1 on master branch. 09:16:59 Is that the correc\t process? 09:18:01 Reading https://docs.openstack.org/project-team-guide/release-management.html 09:18:10 tagging on a master branch? 09:18:10 Potential new release critical issues have first to get fixed on the master branch. Once merged in master, they can be backported to the release branch. The PROJECTNAME-stable-maint team is tasked with approving such backports. Once all the desired backports (and translations updates) are merged, a new release candidate can be produced. 09:19:44 We've backported the patch to the rocky branch already 09:19:48 The release model is for cycle with development milestones¶ 09:19:54 Maybe we should ask in #openstack-release 09:20:19 blazarclient takes cycle with intermediary release model 09:21:09 "If a critical issue is found in the “final release”, backports can be pushed to the stable branch and a new release be requested there." 09:21:19 That's from the "intermediary releases" section 09:21:37 Looks like it should be tagged in the stable branch, not master. 09:21:52 yeah. looks like same approach with cycle with milestone 09:22:22 As you said, we should ask it in #openstack-release. 09:23:21 Looks like Sean is US-based, so he may be online only later today. 09:23:30 I can ask him if you're offline by then. 09:23:49 got it. thanks. 09:24:30 It would be good to have 2.0.1 released by Thursday 09:24:42 Anything else about Rocky? 09:25:04 If not let's move to the next agenda item 09:25:16 nothing from me 09:25:21 #topic PTG meeting agenda 09:25:55 We will have the full team at the PTG, that's great! 09:26:22 yeah, it's nice! 09:26:31 We have the start of an agenda on Etherpad 09:26:34 #link https://etherpad.openstack.org/p/blazar-ptg-stein 09:27:24 Please add topics that you would like to discuss 09:27:50 I noticed there is a comment from Chris Dent on the page 09:28:00 "If we should set up a time to have a placement/blazar meetup during the PTG, please ask me, Eric, Jay or Ed, we should be able to orchestrate something" 09:28:40 I will get in touch with them to set up a discussion slot 09:29:00 Do you have preferences on the time? I think we could find one hour on Tuesday for example 09:29:31 I'm fine for Tuesday. 09:29:38 Me, too 09:29:54 tetsuro: you've been leading the placement integration work, do you have requests / feedback for them? 09:30:24 Well for instance researvation, everything is fine so far. 09:30:49 Actually, bertys is online present on Tuesday, so maybe we should try to meet them another day 09:31:09 I will send email to ask for options 09:31:33 Monday also works for me. 09:32:34 I'll be there by Thursday so if Tuesday doesn't work another day is also fine to me. 09:32:54 OK sounds good 09:33:05 For host reservation, we'd like to have one more feature in placement, kind of exclusive traits, and that is now being proposed in https://review.openstack.org/#/c/593475/. It is nice to discuss this spec and blazar's requirements with placement team at the time. 09:33:07 IMO, we should start the design to remove blazar-nova filter by using PlacementAPI 09:33:11 Let's try to add all items this week to finalize agenda next Tuesday 09:33:41 OK 09:34:01 Also, remember to register for the PTG and book rooms if you haven't already 09:34:14 But I suppose you have already done that a while ago :-) 09:34:49 Thanks for reminding anyway :) 09:35:05 Anything else about the agenda? 09:35:25 Thanks for heading up. 09:35:54 #topic Team photo at PTG 09:36:09 There is a team photo organized at the PTG like in Dublin 09:36:24 I registered us to have our team photo taken on Tuesday, September 11 at 2 PM (just after lunch) 09:36:41 Please let me know if this time doesn't work for you, there are still other slots available. 09:36:57 It works for me 09:37:24 wfm 09:37:49 I will email bertys to check with him, but he should be there. 09:38:21 #topic Team dinner at PTG 09:38:37 There is an Official PTG Happy Hour on Tuesday, September 11, 5:00-7:00pm 09:38:49 Should we organise a team dinner right after, say 7:30 pm? 09:39:32 sound reasonable. 09:39:36 I believe all three of us are available. 09:39:55 Plus bertys should be there, again I will check with him 09:40:14 Sounds good 09:40:40 Please suggest options for the restaurant, and we can decide next week. 09:41:25 #topic python3-first goal 09:41:31 Denver City Guide: https://wiki.openstack.org/wiki/PTG/Stein/CityGuide 09:41:42 Thanks masahito 09:42:14 Many patches have been submitted to Blazar for the python3-first goal 09:42:24 We should review them soon 09:43:38 See updates from Doug Hellmann on the openstack-dev list as well 09:44:06 I am just back from holiday today so I haven't looked at them yet 09:44:11 Most of them are related to juul job setting. So it's easy to review. 09:45:43 Let's review this week and discuss next week if there are any issues 09:46:38 #topic Berlin Summit 09:46:58 The schedule for the Berlin Summit is out. It looks like none of the Blazar talks were accepted unfortunately. 09:47:30 At least we will have a 20 minutes project update slot, though it is not yet on the schedule. 09:48:09 I haven't looked at the schedule in details, it would be good to share pointers to interesting sessions 09:48:38 Are you both still going to attend? 09:48:41 I received a conformation mail for the project update. Should I replay it? 09:48:47 yes. 09:48:56 Oh, could you forward it to me please? 09:49:09 OK 09:49:15 I guess they got confused with the PTL change 09:49:42 maybe 09:50:07 It's quite likely that I will attend the summit, we can have a mini-meeting there too 09:50:27 Yes, I'm coming to the summit, FYI 09:50:29 Good to hear! 09:51:27 And I think Bertrand should be able to join too. 09:52:01 Anything else to say about the summit? 09:52:15 If not let's move to AOB 09:52:47 #topic AOB 09:53:25 Anyone has updates to share? 09:53:57 I have one about releasenote page. I forgot putting the item on the Rocky release topic. 09:54:32 I pushed a releasenote page patch instead of release bot's proposal. https://review.openstack.org/#/c/590671/ 09:54:45 Bot proposal: https://review.openstack.org/#/c/590287/ 09:55:41 tetsuro proposes that we update the bot proposal instead 09:55:43 My patch includes ignore-note section to avoid unnecessary release notes show up in Rocky releasenote. 09:56:07 tetsuro: I can abandon the bot's proposal instead. 09:56:25 Cool, then I can remove my -1. 09:57:39 Probably only core reviewers can abandon patches 09:58:02 Thanks for submitting masahito, I will review 09:59:03 A few updates from me 09:59:10 I noticed that the User Survey didn’t include Blazar in the list of projects that operators were running or were interested into. I contacted the Foundation to add Blazar to the next one. 09:59:19 priteau: thanks 09:59:33 They haven't replied yet though. 10:00:21 I noticed a mailing list thread about placement, it mentions Blazar so worth reading: http://lists.openstack.org/pipermail/openstack-dev/2018-August/133445.html 10:00:30 I haven't read it fully yet 10:01:14 And finally, I am working on upgrading Chameleon's Blazar version to Rocky, so we will get some early feedback about how well it works 10:01:24 That's all from me 10:01:32 I didn't noticed the thread. thanks. I'll check it. 10:01:43 Anything from you tetsuro? 10:01:54 If not it's time to finish the meeting 10:02:02 nothing 10:02:07 nothing 10:02:19 Thanks everyone! 10:02:22 #endmeeting