15:00:36 #startmeeting RDO meeting - 2019-11-13 15:00:36 Meeting started Wed Nov 13 15:00:36 2019 UTC. 15:00:36 This meeting is logged and archived in a public location. 15:00:36 The chair is ykarel. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:36 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:36 The meeting name has been set to 'rdo_meeting_-_2019-11-13' 15:00:37 Meeting started Wed Nov 13 15:00:36 2019 UTC and is due to finish in 60 minutes. The chair is ykarel. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:40 The meeting name has been set to 'rdo_meeting___2019_11_13' 15:01:38 o/ 15:01:44 o/ 15:01:45 o/ 15:01:48 #chair jpena jcapitao amoralej 15:01:48 Current chairs: amoralej jcapitao jpena ykarel 15:01:49 Current chairs: amoralej jcapitao jpena ykarel 15:02:03 please add missing topics to agenda, https://etherpad.openstack.org/p/RDO-Meeting 15:02:11 #topic roll call 15:04:33 * ykarel wait for 1-2 minute to move 15:06:34 ok let's start 15:06:50 #topic CentOS8 Updates 15:06:56 it's me 15:07:08 #info Not much progress on it, as per the last update from centos-meeting there is no clear ETA yet for CentOS8 CBS availability for use by SIGs 15:07:22 #link https://www.centos.org/minutes/2019/November/centos-meeting.2019-11-11-14.00.log.txt 15:07:39 so ^^ is the last update we received from CentOS Team 15:07:53 and we need to wait more to move RDO to CentOS8 15:08:59 any queries on this? 15:09:14 any suggestion we can do in this case? 15:09:37 ykarel, the only think i can think of is to start working in a copr 15:09:42 temporarily 15:09:54 the problem is that there is no pure centos8 copr target 15:10:02 there are epel8 or centos streams 15:10:19 we could use the streams one 15:10:24 at least to start building deps 15:11:08 other than that, not much to do from our side, i'd say 15:11:33 there is a lot of difference between c8-stream and c8 ? 15:11:40 hmm copr is an option, but i think it will not be reusable(apart from testing deps and setting up DLRN) for us once we move to CBS 15:12:06 copr could help with some basic ordering and spec issues 15:12:16 so we can have them ironed out once cbs is available 15:12:36 hmm agree with ^^ 15:12:36 ykarel, nop we can't reuse 15:12:48 just preparation work 15:13:07 well and in best case bootstrap dlrn 15:14:23 Today morning Alan shared folks are using copr https://copr.fedorainfracloud.org/coprs/nmstate/ovs-el8/packages/ 15:14:43 in our case it's too many deps 15:15:17 i would have wanted to avoid duplicate work with copr and CBS 15:15:29 but since we don't have any ETA, we can think of other option 15:15:52 the other option is to just wait and keep doing other stuff 15:15:59 maybe moving ci jobs to centos8 images 15:16:18 jpena, there are already centos8 images we can use? 15:16:26 to move bots and other jobs? 15:16:33 yes we could start other stuffs for which we are not blocked 15:16:41 yes, we have one upstream-centos-8 image available 15:17:06 although maybe we could set a deadline 15:17:10 and revisit to copr or other options in coming weeks, hopefully we will have more update by then 15:17:16 to start working in copr 15:17:33 let's review the status next week 15:17:47 ack +1 15:19:10 anything else on this, or shall we move to next topic? 15:19:55 ack let's move 15:20:09 #topic Change meeting time? 15:20:12 jpena, ^^ 15:20:46 This was meant to be an open question. After DST ended, the meeting time is conflicting with 2 other meetings for me, and I wondered if that was the case for the rest 15:21:07 I see leanderthal proposed to send an email to the mailing list, which looks like a good option 15:21:24 ...unless everyone else says this time suits them perfectly well, then I'll assume it's just me :) 15:21:30 i'm fine with changing it 15:21:47 me too 15:22:04 i am fine with both, though changing it will make me last 1 hr more :) 15:22:27 what time is it in India? 15:22:35 20:52 15:22:42 currently 15:22:49 wow, then it might be too late if we move it 1h later 15:22:52 UTC+5:30 15:22:55 let's leave it as it is, then 15:23:01 we also could move it eariler 15:23:04 instead of later 15:23:17 hm, that could also work 15:23:21 I'll propose that 15:23:28 i can manage if it's ok for everyone else, mail list to discuss would be good 15:24:16 #action jpena to send e-mail to mailing list, proposing to hold the meeting 1h earlier 15:25:02 ok let's move to next 15:25:06 #topic RDO legacy zuul jobs migration to native zuulv3 15:25:10 amoralej, ^^ 15:25:40 i've seen moving legacy jobs to zuulv3 has been proposed as community goal in openstarck upstream 15:25:55 so i think we probably should do the same 15:26:07 just in case legacy mode is removed at some point 15:26:23 for the jobs we use 15:26:38 i think we still have some jobs using legacy stuff 15:27:08 hmm need to check if we rely on legacy upstream jobs 15:27:14 i'm not sure if rdo infra team is checking 15:27:21 yes i noticed in playbooks we still have some legacy stuff 15:27:25 ykarel, i'm more thinking in rdo jobs using legacy 15:27:32 more that using upstream legacy jobs 15:27:42 although we may have also 15:28:01 amoralej, hmm got it, i was mainly thinking of effect on upstream removing it 15:28:06 as with that we have to rush 15:28:31 in fact, it'd be good to check both 15:28:35 afaik, the "legacy" jobs in review.rdo all inherit from a legacy-base job defined in review.rdo's config repo, so there's no dependency on upstream 15:29:07 i need to check migration guide 15:29:15 okk it's good then, but good to cross check and have a plan 15:29:15 tbh, i'm not sure about the complexity of the migration 15:29:21 but i think it can be a good time 15:29:29 until we get centos8 buildroots :) 15:29:48 an initial migration was done earlier but it kept some items 15:30:01 not sure if there is a migration guide for pending items 15:30:13 what needs to be clear 15:30:27 like zuul-cloner, legacy env vars etc 15:30:49 https://docs.openstack.org/infra/manual/zuulv3.html 15:30:54 that's what i was checking 15:31:07 i was thinking in legacy env vars specially 15:31:16 +1 to have a plan 15:31:21 we removed zuul-cloner usage iirc 15:31:36 although there may be used in some places 15:32:16 mm https://docs.openstack.org/infra/manual/zuulv3.html#converting-other-legacy-changes 15:32:22 hmm we mainly need this 15:32:37 i've just created https://trello.com/c/W3JBarr4/726-migrate-zuul-jobs-with-legacy-mode-to-native-zuulv3 15:32:45 nice, too quick 15:33:55 amoralej, i have seen zuul-cloner usage in some of our jobs 15:34:03 iirc weirdo 15:34:07 but we can check again 15:34:13 i think in some cases we have conditionals 15:34:22 if zuul-cloner doesn't exist 15:34:23 but yeah 15:34:25 need to check 15:34:45 #info card has been created to track migration tasks https://trello.com/c/W3JBarr4/726-migrate-zuul-jobs-with-legacy-mode-to-native-zuulv3 15:35:07 #agreed ok let's plan and finish the migration 15:35:30 we can first do a high level assesment of how many jobs are still using legacy stuff 15:35:40 and then digging deeper 15:36:16 +1 15:36:54 i can start an etherpad and list initial issues and changes we need to start 15:37:18 ofcourse if no one is starting it 15:37:27 nop 15:37:39 ok ykarel please open it and let us know 15:37:49 sure i will start my morning tomorrow 15:38:21 ok 15:38:49 #action ykarel to create etherpad about the topic 15:39:13 ok let's move to next 15:39:23 #topic chair for next meeting? 15:39:30 * ykarel will be out for next two meetings 15:39:37 i'll be out next week too 15:40:02 i can take it 15:40:12 #action jcapitao to chair next week 15:40:15 Thanks jcapitao 15:40:30 just a quick note on zuul v3 - I'm waiting for the feedback on the community goal proposal, but anyway, feel free to ping me 15:40:41 but I'm pretty sure you won't have any issue with the conversion of the jobs 15:40:46 #chair tosky 15:40:46 Current chairs: amoralej jcapitao jpena tosky ykarel 15:40:47 Current chairs: amoralej jcapitao jpena tosky ykarel 15:41:01 Thanks tosky 15:41:15 tosky, thanks for the note 15:41:41 ok let's move 15:41:45 #topic open floor 15:41:51 feel free to bring any topic now 15:43:22 i have a patch for review, review please https://review.rdoproject.org/r/#/c/23617/ 15:44:08 i will be pushing similar for other pending jobs tomorrow after testing 15:45:04 ykarel, ack 15:45:09 i'll check 15:45:18 ack Thanks 15:45:26 we tested in dnm, right? 15:45:30 yeah, i see it 15:46:12 amoralej, yes 15:47:29 any thing else or we close, and everyone gets' 12 minutes back 15:48:33 ok let's close 15:48:36 Thanks everyone 15:48:39 #endmeeting