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