16:01:00 <mboddu> #startmeeting RELENG (2019-10-03)
16:01:00 <zodbot> Meeting started Wed Oct  2 16:01:00 2019 UTC.
16:01:00 <zodbot> This meeting is logged and archived in a public location.
16:01:00 <zodbot> The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:00 <zodbot> The meeting name has been set to 'releng_(2019-10-03)'
16:01:01 <mboddu> #meetingname releng
16:01:01 <mboddu> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
16:01:01 <mboddu> #topic init process
16:01:01 <zodbot> The meeting name has been set to 'releng'
16:01:01 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
16:03:10 <nirik> morning
16:05:25 * dustymabe waves
16:06:10 <mboddu> Hello guys
16:07:51 <mboddu> I just wanna bring up one issue and then we can go to backlog
16:08:02 <mboddu> #topic #8851 RFE: When the retirement commit is reverted before a package gets blocked, don't block it
16:08:08 <mboddu> #link https://pagure.io/releng/issue/8851
16:08:35 <mboddu> How can we achieve this?
16:08:42 <nirik> yeah, I think this is perhaps possible... but will require reworking the listener
16:09:04 <mboddu> But what would be the logic?
16:09:07 <nirik> it could just do those checks...
16:09:26 <nirik> when it sees a revert of a dead.package commit, check how long ago it was retired/blocked...
16:10:20 <mboddu> But you cannot push if the eol is set to a past date, so the listener cannot see that commit
16:10:43 <nirik> ah true...
16:11:00 <nirik> so it would have to be in the eol hook...
16:11:28 <nirik> so yeah, perhaps this isn't too possible after all
16:11:41 <mboddu> Right
16:11:48 <mboddu> Its not easy as we think it will be
16:13:00 <nirik> perhaps this could be done similar to the way branch requests/etc are done... with a pagure plugin...
16:14:53 <mboddu> I think, in order to get away from the confusion, we should update fedpkg retire to set the eol date of yesterday's date than today's date
16:15:30 <mboddu> That way, people cannot immediately git revert the retire commit, and then they can file a ticket to unretire it (like we do normally)
16:16:20 <mboddu> It is a special snowflake to retirement case and should be considered as retirement only
16:17:11 <nirik> hum, yeah... I wonder if we replace pdc if we could add another state.
16:17:31 <nirik> "active" "retired" "retired_less_than_8_weeks"
16:18:00 <nirik> and have the eol hook allow reverting the one but not the other... dunno.
16:18:31 <mboddu> True
16:18:56 <mboddu> Or another thing we can do is automate the entire damn thing (at least retired less than 8 week)
16:19:14 <nirik> automation++
16:19:14 <zodbot> nirik: Karma for automation changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:19:18 <nirik> ha. oops
16:19:32 <mboddu> So, that people can unretire stuff by themselves and if its more than 8 weeks, ask them to file the releng ticket
16:19:48 <mboddu> Its a nice nick to have, we will get more cookies :D
16:20:37 <nirik> not as much as if someone had the nick 'C'
16:21:20 <mboddu> Hahaha :D
16:21:29 <mboddu> So, what are our options here:
16:21:43 <mboddu> 1. Set the eol date to last day in fedpkg retire for now
16:21:44 <nirik> I don't think there's an easy short term fix...
16:21:51 <mboddu> 2. Automate the <8 weeks thing
16:22:14 <nirik> yeah, 1 would at least avoid some confusion...
16:22:16 <mboddu> Yeah, which is why I am suggesting 1 for now
16:23:42 <nirik> yeah, lets do one and look to automate when we can
16:23:43 <mboddu> #info When fedpkg retire is called, set the eol date to previous date so that immediate reverts are not allowed. This is a temporary fix until we get to automate the unretirement for less than 8 weeks.
16:24:04 <mboddu> #info mohanboddu will file a fedpkg ticket
16:24:16 <mboddu> Or probably patch it myself
16:24:24 <mboddu> I mean send the PR
16:24:25 <nirik> is it fedpkg?
16:24:26 <mizdebsk> i think it's job for pdc-updater not fedpkg
16:24:28 <nirik> or is it the listener?
16:24:35 <nirik> right
16:24:39 <mboddu> Oh right
16:24:41 <nirik> fedpkg / user has no token
16:24:44 <mboddu> #undo
16:24:44 <zodbot> Removing item from minutes: INFO by mboddu at 16:24:04 : mohanboddu will file a fedpkg ticket
16:25:07 <mboddu> Thanks mizdebsk :)
16:25:09 <nirik> I'm glad our processes are so clear! NOT.
16:25:30 <mboddu> haha :)
16:25:56 <mboddu> #topic Open Floor
16:26:11 <mboddu> #info Next Tue, Oct 8th is the f31 final freeze
16:26:17 <nirik> so I had 2 things...
16:26:23 * dustymabe has one
16:26:29 <dustymabe> can I go real quick?
16:26:36 <nirik> let me do one, then dusty then my longer one?
16:26:41 <dustymabe> +1
16:26:47 <nirik> this will be quick...
16:26:59 <nirik> FYI, I have scheduled a koji outage later today (21UTC)
16:27:14 <nirik> I'm going to update prod to 1.18.0 and also give db-koji01 more memory.
16:27:22 <nirik> should be down only a few min.
16:27:35 <nirik> Thats it on that... dustymabe go ahead.
16:27:40 <dustymabe> https://hackmd.io/5uB7hOJKSjGUt65iLgPnbA#Existing-requests-for-Fedora-Releng
16:27:53 <dustymabe> can we make some progess on the final comment in #8811
16:27:59 <dustymabe> https://pagure.io/releng/issue/8811#comment-598901
16:28:10 <mboddu> #info nirik updating koji in prod to 1.18.0 and there will be a short outage later today at around 21UTC
16:29:31 <nirik> dustymabe: I can try and do that this week... friday?
16:29:46 <dustymabe> nirik: sounds good to me.. mind adding a comment to the ticket?
16:29:52 <nirik> sure thing.
16:29:57 * mboddu would like to follow it, if its a simple thing
16:30:35 <mboddu> #info nirik and dustymabe will work on https://pagure.io/releng/issue/8811#comment-598901 on Friday this week
16:31:15 <dustymabe> +1
16:31:15 <nirik> sure, sounds good. following is good.
16:31:21 * dustymabe runs off to run another meeting
16:31:38 <mboddu> Thanks dustymabe for joining
16:31:39 <nirik> we can even pick a time...
16:31:56 <mboddu> nirik: I got only 1 meeting on Fri, so anytime would work for me
16:32:09 * mboddu feels happy to say that he has only 1 meeting :D
16:32:17 <nirik> say 10am my time / 1pm east?
16:33:01 <mboddu> nirik: That would work, and I am also in pacific for this week, I am in CA :D
16:33:07 <mboddu> pacific time*
16:34:09 * mboddu waiting for nirik's bigger stuff to discuss
16:34:14 <nirik> oh really? cool. just touristing around?
16:34:31 <nirik> can someone toss a meeting invite out on calendar if 10am PDT is ok?
16:34:40 <nirik> So, the other thing I had was backlog.
16:35:04 <nirik> Just like for the infra side I marked some old releng tickets backlog and we can try and focus on them one or two at a time and get some done.
16:35:41 <nirik> my thought was actually to mix these with the infra stuff... to more cross train the teams... but if you prefer we can keep them seperate.
16:35:52 <nirik> https://board.net/p/fedora-infra-backlog has a list
16:36:28 <nirik> so do we want to pick one and see if we can make progress by next wed?
16:36:46 <mboddu> nirik: Came here on some personal work - regarding CA visit
16:37:02 * mboddu can also send the invite
16:37:35 <mboddu> nirik: Sounds good to me
16:37:38 * mboddu checks
16:37:54 <nirik> any of them suit your fancy?
16:38:27 <mboddu> May be 7718 or 7793?
16:38:39 <nirik> ok.
16:38:42 <mboddu> Or 6746
16:38:45 <mboddu> I like all of them :D
16:38:55 <nirik> 6746 is an old one...
16:39:02 <mboddu> And useful one
16:39:11 <mboddu> Lets take a look at 6746
16:39:23 <mboddu> I can get something done
16:39:31 <nirik> yep. I think adamw already re-implemented it in openqa... butwe can try and come up with a better/more generic way
16:39:42 <mboddu> Yup
16:40:01 <nirik> I think the thing to do is schedule an actual time to work on it, and gather everyone interested... we can sort out a plan and all help
16:40:57 <nirik> so, perhaps send to infra/releng lists we are gonna work on it, pick a time next week and see who shows?
16:41:10 <mboddu> Okay, I will do that
16:41:30 <nirik> were we going to try and use odcs for this?
16:41:54 <mboddu> We can
16:42:06 <mboddu> Not sure if that an overkill or not
16:42:21 <nirik> except that just gives a repo right? not images...
16:42:31 <nirik> but could use odcs to make a repo and from that make images...
16:42:56 <mboddu> My initial plan was, listen to fedmsg, call a pungi script with a config and put it under /mnt/koji/compose/<something>
16:43:19 <nirik> we could also use loopabull...
16:44:11 <nirik> which now that I think of it, needs porting to fedora-messaging
16:44:45 <nirik> anyhow, we can discuss and decide what the best plan is.
16:44:53 <nirik> we can also look at adamw's implementation.
16:45:07 <mboddu> Lets take a look at ODCS, we never used it anywhere in fedora infra/releng, may be we can move other stuff to ODCS as well
16:45:28 <nirik> sure.
16:45:34 <mboddu> ODCS can also take raw pungi configs
16:45:58 <nirik> thats all I had... although like I said I'd like to see cross training/work between releng and infra.
16:46:01 <mboddu> So, it can create the repo as well images
16:46:11 <mboddu> I would love that as well
16:48:54 <mboddu> nirik: Who is maintaining pdcupdater now?
16:49:02 <nirik> no one
16:49:37 <nirik> cverna is working on a pdc replacement, but it's not at all ready yet
16:49:50 <mboddu> Yeah, ^ this I know
16:50:14 <mboddu> All that it needs is adding "- timedelta(1)" to https://github.com/fedora-infra/pdc-updater/blob/develop/pdcupdater/handlers/retirement.py#L192
16:50:17 <nirik> and pdc is also somewhat broken... it's not been importing composes right for a while
16:50:33 <mboddu> it = our first ticket
16:51:14 <nirik> so might be easier to just patch that in ansible... but I suppose we could talk to others and see if we can do a new pdc release...
16:52:06 <mboddu> May be, since the last commit on that project is on May 11 2018
16:52:21 * nirik has to go take a dog out... back in a bit.
16:53:25 <mboddu> Okay, thanks for joining nirik
16:53:31 <mboddu> #endmeeting