14:02:28 #startmeeting sahara 14:02:29 Meeting started Thu Mar 21 14:02:28 2019 UTC and is due to finish in 60 minutes. The chair is jeremyfreudberg. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:33 The meeting name has been set to 'sahara' 14:02:50 o/ 14:02:50 o/ 14:03:00 #topic News/Updates 14:03:41 not much on my side, basically reviewing the final patches, and celebrating that python 3 is in 14:04:31 same here 14:04:39 still battling with grenade, but in the meantime I fixed the kolla support for plugins (and Fedora), puppet support for trustee, unlocked openstack-ansibile-os_sahara gates 14:04:42 later I want to show you all the rc1 patch for sahara with cycle highlights, so you can give me some feedback 14:05:06 tellesnobrega, i'll make it a topic 14:05:12 thanks tosky, i saw some of those 14:05:12 and fixed two breakages in our jobs introduced by Zuul switching to Ansible 2.7 14:06:10 cool, moving on 14:06:17 #topic RC1 and cycle highlights 14:06:30 today is the rc1 deadline, which is also the cycle highlights deadline 14:06:55 yes, I have a -1 on the sahara patch so we can include python 3 and cycle highlights 14:07:12 yup, and sahara-dashboard will need its release patch updated too 14:07:24 feel free to fill us in on the cycle highlights 14:07:35 jeremyfreudberg, yes 14:07:36 - Sahara plugins are removed from core code for easier maintenance and upgrades. 14:07:36 - Release of APIv2. 14:07:36 - Improvements on boot from volume feature. 14:08:02 those are the highlights I have written, please feel free to tweak 14:08:15 i think it's right (and it sounds good), let me just check the git history 14:08:23 also, jeremyfreudberg, do you want to update those patches? 14:09:51 i can update them 14:10:04 i think those highlights are good 14:10:13 maybe just say "Release of APIv2 as stable" 14:10:36 that makes sense 14:10:50 i'll include that when i update the release patch 14:11:04 otherwise it's really good, so thanks for writing 14:11:30 you are welcome :) 14:11:40 anything else on this? 14:12:14 not from me 14:12:41 fine with the proposal 14:12:46 ok, moving on 14:12:50 #topic Virtual PTG 14:13:30 i'm a bit early on this one, but i just wanted to mention it now that i think a virtual PTG is a good idea 14:13:51 I think it was the Rocky PTG where we were successful in doing that 14:14:06 anyway, not much to say here, but just watch for an eventual email about it 14:14:22 jeremyfreudberg, yes, do you have ideas for a date? 14:14:48 I agree that it's an interesting idea 14:15:25 i think some time between may 6 and 10 would be good, but it really could be whenever 14:15:45 unless you think we should do it sooner 14:16:12 may 6-10 was based on the real ptg date, but maybe it's not optimal to be siting here for a month waiting for it to happen 14:16:23 just wanted to make sure it wasn't during PTG time, I'll be traveling back from Denver 14:16:57 I will be back on May 4th 14:17:07 but earlier could be good as well 14:17:15 oh, i didn't realize you were able to go to Denver after all, but yes, it will be at some other time not during the real ptg 14:17:20 I'm on vacation between May 8 and May 13 :) 14:17:32 I won't be at the PTG 14:17:35 just the summit 14:18:08 got it 14:18:45 but now that you mentioned, I believe that earlier could be great 14:18:57 we get a jump start and start train early 14:19:23 maybe you can come up with some options and we can vote on it 14:20:13 earlier would be really good. there are two advantages of May: 1) we can incorporate outcomes from ptg/forum into our planning (but this probably won't be significant) and 2) I'm much less busy in May and will have more time to devote to it 14:20:20 i think you are right, i'll make a poll 14:21:29 awesome 14:21:50 that's it for my topics, really 14:21:53 #topic Open Discussion 14:22:54 anybody have any points? 14:23:19 we have the shortest review queue ever - just a reminder about the 3 sahara-tests patches 14:23:48 without this one, we can't merge anything else on https://review.openstack.org/#/c/640101/ 14:24:07 that reminds me: what do we want to do about pike? 14:24:17 it will switch soon to Extended Maintenance 14:25:50 can you elaborate? what are our choices? 14:26:18 let me quote fungi's answer when I asked yesterday, even if he hinted about rechecking the rules 14:26:36 " tosky: it's up to the ptl to decide whether to have the core reviewers for the project continue maintenance, hand over maintenance to an extended maintenance team, or close down the branch for further development entirely" 14:28:00 i don't really mind keeping it open 14:28:08 but i don't feel particularly strongly either 14:28:46 please don't take my word for it. the official resolution is https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html 14:28:54 I guess we can see the general trend 14:29:21 i'll read through that 14:29:28 i was merely summarizing 14:29:34 oh, i should have tagged that, sorry 14:29:41 #link https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html 2018-03-01 Extended maintenance for stable branches 14:30:22 jeremyfreudberg, might also evaluate the team size, we may not have enough hands to keep it open 14:30:25 but lets see 14:30:35 thanks fungi - I used your words as a starting point for the discussion 14:30:38 yes, we'll see 14:30:52 I guess we can check the general trend, if any 14:31:16 yup 14:31:21 ok - anything else for today? 14:31:37 not from me 14:32:07 nothing from me 14:32:28 ok, good 14:32:30 thanks all 14:32:37 same time next week o/ 14:32:40 o/ 14:32:55 see you 14:32:58 #endmeeting