14:03:49 #startmeeting RDO meeting - 2020-09-02 14:03:50 Meeting started Wed Sep 2 14:03:49 2020 UTC and is due to finish in 60 minutes. The chair is amoralej. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:54 The meeting name has been set to 'rdo_meeting___2020_09_02' 14:04:13 #topic roll call 14:04:18 o/ 14:04:19 #chair spotz 14:04:20 Current chairs: amoralej spotz 14:04:32 o/ 14:04:40 #chair jcapitao 14:04:40 Current chairs: amoralej jcapitao spotz 14:04:53 you still have some time to add topics to https://etherpad.opendev.org/p/RDO-Meeting 14:05:26 o/ 14:05:57 #chair ykarel 14:05:58 Current chairs: amoralej jcapitao spotz ykarel 14:06:11 let's start with first topic 14:06:28 #topic RDO Victoria Release Preparation 14:06:53 #link https://releases.openstack.org/victoria/schedule.html 14:07:10 one more release is coming 14:07:14 ykarel, all yours 14:07:23 \o/ 14:07:32 Yeah so victoria release is approaching 14:07:43 This week no client libraries are being released 14:07:56 31 Aug - 04 Sept - Final release for non-client libraries 14:08:08 So we need to get RDO ready for it 14:08:32 We created trello card and etherpad to track the work around it 14:08:37 #link https://review.rdoproject.org/etherpad/p/victoria-release-preparation 14:08:51 #link https://trello.com/c/gfYmxwO2/742-victoria-release-preparation 14:09:19 That's it for now, in coming days we will see progress with it 14:09:28 Any queries/concerns? 14:09:55 So kinda of a cross question with events. Do we still want to try to have a test days with RC1? 14:10:31 My concern is timing so we help the release vs take resources away 14:10:43 I think that can go along with release prep + test day 14:10:45 what would be the plan for test day? 14:11:30 Well we could run through docs and see if we have doc bugs or find bugs which I think is the historical test days. Or we do more of a hackfest with some bugs to be targeted 14:12:02 We finally have the hopin.to platform we can leverage 14:12:04 i try to understand what'd be the effort 14:12:31 historial tests days didn't take too much time 14:12:38 just to make sure repos are ready 14:12:45 and be available 14:12:48 Ok that seems easy enough 14:12:57 if anyone asks on irc 14:13:24 if we want to go for hackfest, we'd need to figure out what's needed 14:14:25 So we just need to get it up on the calendar and out to the lists, make sure we have a doc for proceedures, etc. Yeah hackfest is new territory and with not having a platform it might be better to test day and then maybe after the start of Wallaby do a hackfest with a few targeted topics 14:15:25 Well not having had a platform until now 14:15:58 ok 14:16:11 so i'd vote for going with regular test days 14:16:27 and we can consider hackfest post GA 14:16:28 ? 14:16:31 And we'll organize and hackfest with some goals later 14:16:44 +1 14:16:47 +1 14:17:47 + 14:17:53 +1 14:18:39 we have quorum, good :) 14:18:54 Ok so we'll need to pick a day which helps aid the release, so y'all would have a better idea of when the test day would be most beneficial and we'll get it out there asap 14:19:20 And review the instructions:) 14:19:39 probalby 1-2 october will be good timing 14:20:39 Ok just a warning 10/1 is Open Source Day at GHC though I can probably be in 2 places at once. 10/2 I'm off though 14:20:56 ok 14:21:02 no problem in moving it 14:21:09 5-6 14:21:14 would that work? 14:21:23 But I'm just a guider and a tester. And we could actually have a group of mentees maybe do the Test day:) 14:21:54 5-6 will work, let me look at the test days instructions and see if we can't combine:) 14:21:59 ok 14:22:26 Yatin Karel proposed rdoinfo master: Update ansible to 2.9.13 for Victoria https://review.rdoproject.org/r/28929 14:22:36 Cause we were planning on doing peer programming for GHC, but depending on the test day instructions we could have some mentees do that as well 14:23:34 how do you plan to do the peer programming? 14:23:38 No matter what I'm off on 10/2 so GHC could maybe be some pre-test days work 14:24:30 I think we've managed to get 6 mentors and were going to do shadowing with slack/meet/etc video sessions 14:25:05 I'll figure out hot to add to the RDO calendar later today so we can get the 5-6 out there 14:25:13 ok 14:25:18 thx spotz 14:25:27 ykarel, going back to Victoria preparation 14:25:51 so, next week is final releases for clients 14:25:56 yes 14:26:05 so, next week we can start doing reqchecks 14:26:23 it'd be good to start updating deps already 14:26:27 i mean to match u-c 14:26:34 +1 14:26:37 i think that's current priority 14:26:39 jcapitao, ^ 14:26:49 now that we have a nice report :) 14:26:57 yeah ! 14:27:05 i'll take care of that 14:27:06 could we create a list of deps to be updated in some etherpad 14:27:10 hmm we have lists now, so just prioritize/build/promote 14:27:11 and start working 14:27:18 yep 14:27:24 we will need to work in parallel 14:27:32 yeap 14:27:34 and coordinate to propose promotions 14:28:38 how do we get the order list ? 14:29:20 Is there an older one we can adjust? 14:30:15 i think so but i don't know if we have a tool that does this from scratch 14:30:39 wdym 14:30:43 order list? 14:31:09 Do this then this... 14:31:22 so, we first need to create the full list 14:31:34 and then prioritize it manually 14:31:40 just based on previous experience 14:31:45 for what to do first 14:32:05 ok that answer my question 14:32:18 i guess that's what ykarel meant 14:32:23 yeap right 14:33:22 Does it make sense to start with Ussuri's list so there's some basic structure? 14:33:54 #link http://dashboards.rdoproject.org/report-uc 14:34:25 so we have report and tool created by jcapitao to create initial list 14:34:28 spotz, yes 14:34:42 current master branch is using the ussuri ones 14:34:45 #link https://github.com/rdo-infra/releng/blob/master/scripts/report-uc.py 14:34:45 that's the starting point 14:34:54 ok cool 14:37:35 at the end of next week we can start working in reqcheck and branches for libs and clients 14:37:46 ok, i think we can move to next topic 14:37:50 anything else ykarel ? 14:37:57 nope let's move to next 14:38:09 #topic Events and Mascot update 14:38:20 we already started discussing about test days :) 14:38:25 spotz, 14:39:31 Yep so test days is discussed. Jason and I have both reached out to the person is OSPO who does graphics to get us our duck mascot:) No contact back so I'll follow up again as I'd really like to have something in place for GHC and the Test days 14:40:14 Contract for hopin.to is finally done so we can hold any workshops or events we want there 14:41:07 ok, nice 14:41:18 When we reached out for Doc Days the only reply was I think beyond the scope of what we can do, aka all configuration options in TripleO but maybe we'll circle back on that after summit and ptg 14:41:39 nice 14:41:58 ok 14:42:05 In the mean time when we do our release I'll go through installation and put up patches to keep us up to date. 14:42:36 I think we'll have 2 weeks between test days and Summit and then the following week is PTG so October I think will be fairly busy 14:43:37 We could maybe have a virtual happy hour type even during Summit and/or PTG if there's interest. It won't be the same as in person though 14:44:18 +1 14:45:04 +1 14:45:20 could be great 14:45:37 what would we do in virtual happy hour? i didn't attend any :) 14:45:54 Ok I'll see what we can do even if it's just an hour on Google Meet or something. Still waiting to hear what timezone summit will be on 14:46:42 amoralej: Well BYOB of course:) But just hang out and chat. We do one with my team weekly just to chat and while some drink I usually have tea or something:) 14:46:59 ok, that's what i expected :) 14:47:10 If we want to do more then 1 hour we could probably do oneline trivia or something 14:47:23 With prizes.... ooh there's an idea:) 14:47:50 :) 14:48:14 interesting :) 14:48:14 virtual social interactions are appreciated with covid restrictions :) 14:48:29 amoralej: Yeah and that's why I suggested it:) 14:49:14 Ok I'll put that on my todo list to see what we can do. And if we have our stuff in the cool stuff store we could do prizes directly from there 14:49:30 ok, nice 14:49:32 That's it for me 14:49:38 thanks spotz! 14:49:48 My pleasure:) 14:50:00 #topic New dashboard reporting U-C status! 14:50:12 #link https://dashboards.rdoproject.org/report-uc 14:50:20 thanks jcapitao for this 14:50:33 you want to introduce our new friend? :) 14:50:52 hehe :) 14:51:14 so basically, the report displays a comparison between upper constraints of the upstream development release and their associated packages in master repo 14:51:35 it looks really great 14:51:55 this will show us a quick overview of the status of our packages in comparison to upstream 14:52:04 my main concern is when there is more that one line for the same module 14:52:14 as openstackdocstheme 14:52:19 it'd be good to handle that 14:52:21 other than that 14:52:25 looks really nice 14:53:14 User vakwetu proposed rdoinfo master: Unpin novajoin-tempest-plugin https://review.rdoproject.org/r/29119 14:53:25 you mean to show as a subline ? 14:53:42 no 14:53:46 to shoul only one line 14:53:49 with the newest 14:54:01 which would be the one actually installed 14:54:22 One question on the dashboard, is there a pattern to the colors as I'm missing it:( 14:54:54 :) 14:55:00 oh yes, we can only display the lastest one 14:55:02 that could be improved too 14:55:20 User vakwetu proposed rdoinfo master: Unpin novajoin-tempest-plugin https://review.rdoproject.org/r/29119 14:55:23 yeah i noticed this issue as well 14:55:25 spotz, it's just even and odd iiuc, but some lines are removed 14:55:45 so, it doesn't follow any patter 14:55:48 pattern 14:55:49 i think it's caused by the filter we put 14:56:02 which can be missleading 14:56:09 yeap 14:56:10 Ahh ok cause it wasn't every other one, it wasn't status, or source:) 14:56:34 It's the ops in me I look for logic:) 14:56:59 i had the same and that's how i discovered it 14:57:17 ok, so we are almost out of time 14:57:24 let's move to open floor 14:57:29 #topic open floor 14:57:36 anything else you'd like to share? 14:57:46 I'm good:) 14:58:07 good too 14:58:12 me too 14:59:00 volunteer to chair next meeting? 14:59:36 i can take it 14:59:51 #action jcapitao to chair next week 14:59:55 i'm closing the meeting 15:00:01 thanks all for joining! 15:00:12 #endmeeting