09:00:14 #startmeeting blazar 09:00:15 Meeting started Tue Sep 4 09:00:14 2018 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:18 The meeting name has been set to 'blazar' 09:00:28 #topic RollCall 09:00:37 o/ 09:00:50 o/ 09:01:10 tetsuro is out of office today 09:01:22 Hello masahito and bertys 09:01:30 masahito: Thanks for letting us know 09:01:40 Today's agenda: 09:01:59 PTG meeting agenda 09:02:01 python3-first goal 09:02:03 Next IRC meeting 09:02:05 AOB 09:02:16 Anything else that you would like to discuss? 09:02:57 #topic PTG meeting agenda 09:03:21 We're finalizing the agenda for the PTG meeting on Monday and Tuesday next week 09:03:25 #link https://etherpad.openstack.org/p/blazar-ptg-stein 09:04:17 bertys: I see you're only available from Tuesday, are there topics in which you want to be involved that we should keep for that day? 09:05:06 priteau: meeting with placement team will be on Tuesday right? 09:05:16 Yes, that's the only day that works for them 09:05:32 priteau: ok happy to join this meeting as well 09:06:03 My question was more about, what should we cover in priority on Monday while you're away? 09:06:44 Candidates are: soft-delete, tempest tests 09:06:59 some internal discussions of placement API use 09:07:24 You added to the Etherpad "Prioritize blueprints for Stein cycle" and "Community wide goals", would you like to be present for these two discussions? 09:08:52 priteau: yes, I am also interested to join the discussion on network / Neutron resource reservation 09:09:10 Lots of things to discuss on Tuesday! 09:10:04 We'll start Monday by finalizing the order of the agenda, and I would suggest we could do a tentative prioritization of Stein blueprints, which we would finalize with you on Tuesday 09:10:22 I am worried that we could have too much to discuss on Tuesday and not enough on Monday ;-) 09:10:39 priteau: fine with me. Thanks 09:11:44 I think the prioritize is good to talk in Monday. 09:12:33 ah, I means the prioritizing is the community wide goal. 09:13:34 Sounds like Monday is a day for Blazar internal things and Tuesday is a day for cross-project things. 09:14:27 On Monday we should also review existing bugs (we have 32 open) and update their information, many are still assigned to Rocky milestones. 09:15:09 right. And it remands me that StoryBoard migration. 09:15:26 Good point, added to the pad 09:16:15 So, on Tuesday we'll have discussion with placements folks, time is still to be decided. 09:16:27 Also, team photo at 2 PM and team dinner in the evening 09:17:45 I have suggested some restaurant options with good reviews in the Etherpad, please vote for your favorites 09:18:09 Thanks for the list. I added +1. 09:18:36 priteau: Do you have a meeting of scientific SIG on Monday. 09:19:13 I notice the SIG has a discussion slot on Monday. 09:19:17 I won't attend the Scientific SIG meeting, unless we've covered everything in the Blazar meeting. A colleague will be there. 09:20:04 Got it. 09:20:57 For the dinner I can make a reservation once we've got all votes. 09:21:13 Anything else for the PTG? 09:21:42 nothing from me 09:21:59 sorry, I have just one. 09:22:38 I've written the design of network resource reservation. 09:23:17 In the Etherpad that you linked? 09:23:24 It's a draft so please feel free to add your idea. It focuses on floating ip reservation. 09:23:31 https://etherpad.openstack.org/p/network-resource-reservation 09:24:27 Thanks, I will review! For Chameleon we need floating IP reservation, but also network segments (VLANs) 09:24:40 thanks masahito, very good start 09:25:06 IMO, we needs to clarifies the requirements for the network resource reservation first. 09:25:10 I can extend to cover this second use case 09:25:37 masahito: you mean user requirements? 09:26:17 Both. user requirements and admin (cloud operators) requirements. 09:27:05 OK. We can discuss them at the PTG 09:28:27 Anything else? 09:29:26 If not let's move on 09:29:32 #topic python3-first goal 09:30:14 I have noticed that the Zuul job settings have been imported on stable branches as well. 09:30:48 The patch for Queens fails CI due to issues with the Tempest tests: https://review.openstack.org/#/c/596241/ 09:31:04 This had been noticed on another of our stable patches as well 09:31:36 Tempest is not branched, so we need to make sure tests are compatible with all Blazar branches 09:31:50 right. 09:32:12 The no branch on the stable branch was my fault. 09:32:13 See https://review.openstack.org/#/c/590599/ as well 09:33:23 If someone has time to look into how to make Tempest tests compatible with all versions, that would be great. 09:33:32 Some of API tests failure comes from API changes in Rocky cycle. 09:34:01 s/API changes/API fixes/ 09:34:22 I'll dig into that later 09:34:33 Maybe we could run Gabbi tests only on Rocky? 09:34:58 Or backport API fixes to Queens. 09:35:34 Stopping Gabbi to Queens looks nice to me. 09:36:15 Backporting the patch has an impact to released API. 09:37:25 I agree it's preferable not to change API responses for bugfix releases. 09:38:57 Thanks masahito for offering to look into it 09:40:03 #topic Next IRC meeting 09:40:59 Obviously we're all in Denver next Tuesday 09:41:27 So we should cancel the IRC meeting, unless you want to get up at 3 AM ;-) 09:41:45 haha. +1 to cancel 09:42:22 The next IRC meeting will be on Tuesday, 18 September at the usual time 09:42:58 #topic AOB 09:43:09 Any other updates? 09:43:58 Rocky was released last week. 09:44:20 Congratulations to everyone for the Rocky release! 09:44:27 Especially to the Rocky PTL masahito :-) 09:44:57 Thank you every one for your great jobs :-> 09:45:05 I have a related update. 09:45:21 Chameleon is now running the Rocky version of Blazar. 09:45:34 Everything's working well so far. 09:45:55 Congratulations! 09:46:01 priteau: nice! 09:46:19 Resource monitoring is not enabled but we may turn it on later after some testing. 09:46:55 To be precise it's running Rocky plus some patches, including the soft-delete series I submitted. 09:48:17 Any other update? 09:49:31 Then we can end the meeting early today. 09:49:39 See you all next week! Have a safe trip. 09:49:56 See you in Denver! 09:50:31 #endmeeting