17:00:45 <mboddu> #startmeeting RELENG (2018-04-19)
17:00:45 <zodbot> Meeting started Thu Apr 19 17:00:45 2018 UTC.  The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:45 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:00:45 <zodbot> The meeting name has been set to 'releng_(2018-04-19)'
17:00:46 <mboddu> #meetingname releng
17:00:46 <mboddu> #chair dgilmore nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu Kellin dustymabe
17:00:46 <mboddu> #topic init process
17:00:46 <zodbot> The meeting name has been set to 'releng'
17:00:46 <zodbot> Current chairs: Kellin dgilmore dustymabe masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll
17:00:55 * nirik is sort of here.
17:01:28 <mboddu> I want Randy to join here as I have something to discuss
17:05:28 <nirik> might ping him in another channel to join...
17:06:03 <mboddu> nirik: Yeah, just waiting if anyone else joins
17:06:19 <mboddu> As I have only 1 topic to discuss
17:07:07 * Kellin is here, just drinking wonderful oolong tea.
17:07:27 <mboddu> Okay, lets start
17:07:29 <bowlofeggs> sup!
17:07:40 <mboddu> bowlofeggs: Thanks for joining
17:07:43 <mboddu> we are just starting
17:07:46 <mboddu> #topic #7439 Bodhi can now manage containers
17:07:52 <bowlofeggs> wewt
17:07:54 <mboddu> #link https://pagure.io/releng/issue/7439
17:07:59 <bowlofeggs> (except not buildroot overrides yet)
17:08:52 <nirik> do we need this before f28 release?
17:08:54 <bowlofeggs> that ticket was mostly an FYI so you knew it was an option available to you now - it's up to you whether you want to turn it on now or wait for BRO support. imo, it's still useful even without BRO support
17:09:19 <bowlofeggs> nirik: i don't think there's a specific time it is needed - it's meant to eliminate the need for releng to manually push containers around
17:09:29 <nirik> right.
17:09:30 <mboddu> bowlofeggs: Yes, but bodhi-manage-releases is updated to add the tags?
17:09:36 <bowlofeggs> so imo, it could wait for freeze
17:09:48 <nirik> but if we try and get it working now, we run the risk of slowing down or messing up things.
17:09:54 <bowlofeggs> mboddu: it still can't add that one tag (i have a task to fix that before f29) but it can add the other tags
17:10:01 <bowlofeggs> i can manually fix that up for you like i di dlast time
17:10:14 <bowlofeggs> nirik: yeah true, might be wise to wait until after freeze
17:10:22 <mboddu> I agree with nirik and add it later than now
17:10:36 <mboddu> I mean after freeze
17:10:51 <mboddu> bowlofeggs: How is the tagging structure works?
17:11:10 <bowlofeggs> mboddu: haha i was assuming you'd know that
17:11:26 <bowlofeggs> mboddu: the koji tags are less important for containers than they are for rpms
17:11:32 <bowlofeggs> since pungi is not involved
17:11:46 <mboddu> bowlofeggs: Okay, I think we need to sit and talk about it then
17:11:46 <bowlofeggs> bodhi doesn't use the koji tags to know what to do, it just uses its own states to know what to do
17:11:54 <bowlofeggs> the koji tags are kinda vistigial for containers
17:12:09 <bowlofeggs> you could probably just make the tags be analogous to the rpm releases and it'd be fine
17:12:17 <bowlofeggs> that's what i did in my testing
17:12:21 <mboddu> bowlofeggs: Okay, but to understand where the container stands, its better to use to tags and also be close to the rpms style
17:12:35 <bowlofeggs> yeah it's convenient to just make it be the same as for rpms imop
17:12:37 <bowlofeggs> *imo
17:12:52 <bowlofeggs> like, f27c-updates-testing, f27-updates, etc.
17:12:59 <bowlofeggs> err, f27c-updates
17:13:09 <bowlofeggs> the tags do need to be different than the rpm versions
17:13:19 <mboddu> bowlofeggs: Okay, awesome, is it okay if I schedule a meeting sometime after freeze to go over it(before we enable the container support in bodhi)
17:13:20 <bowlofeggs> so i just slapped a "c" on there during testing
17:13:33 <mboddu> bowlofeggs: Same as "m" for modular
17:13:34 <bowlofeggs> you can probably name it as you like though, bodhi doesn't care what its called
17:13:41 <bowlofeggs> yeah exactly
17:13:58 <bowlofeggs> but again, bodhi is not opinionated about the name of the tag, so long as it is unique to the release/content type
17:14:13 <mboddu> bowlofeggs: Cool, thanks for the info
17:15:09 <mboddu> bowlofeggs: In that case, I will just ping you the tag names and you can add it to bodhi
17:15:24 <bowlofeggs> yeah i can do taht
17:15:38 <mboddu> bowlofeggs: Okay, thats all I need to know
17:15:41 <bowlofeggs> there already are some tags for containers in koji i think
17:15:52 <bowlofeggs> maybe not all we need, but they are already tagged in there to some degree
17:16:06 <mboddu> bowlofeggs: Yes, but one is for BR and the other is to hold the containers
17:16:33 <mboddu> So, you build a container against f29-container-build and it will be available in f29-container tag
17:16:43 <bowlofeggs> cool
17:16:46 <mboddu> Thats all we have at the moment
17:17:19 <mboddu> bowlofeggs: Also, we should include Patrick and see if we can enable signing as well
17:17:33 <bowlofeggs> yeah
17:18:15 <mboddu> #info We will enable container support in bodhi after freeze
17:18:30 <nirik> will be nice to have them using the same process...
17:19:02 <mboddu> #info mboddu will create a list of tag names and give it to bowlofeggs to update them in the bodhi configs
17:19:28 <mboddu> #info We should sync up with puiterwijk to see how we can enable signing on containers
17:19:41 <mboddu> nirik: Yup, thats what I want as well
17:20:17 * masta looks in
17:20:39 <mboddu> bowlofeggs: ^ Did I miss anything?
17:20:49 * mboddu waves to masta
17:20:52 <bowlofeggs> nope, sounds good to me
17:21:07 <cverna> bowlofeggs: have tested it in stg ?
17:21:24 * cverna just pass by :)
17:22:08 <bowlofeggs> cverna: i have not specifically tested this in stg yet - to do that we'd need to get some auth stuff set up. i tested it in dev though, fairly extensively, just against a local registry
17:22:36 <bowlofeggs> i'll file a ticket to request that
17:22:51 <cverna> bowlofeggs: ok, would be nice during freeze to try and test it on stg
17:22:56 <bowlofeggs> actually we need prod configured for it too
17:23:02 <bowlofeggs> so i should def file that ticket
17:23:08 <bowlofeggs> yeah agreed
17:23:23 * cverna needs to fix OSBS stg first :s
17:24:20 <mboddu> bowlofeggs, cverna : So, I have a process question here
17:25:15 <mboddu> Currently cverna files a ticket and asks releng to do the container releases, then we do the base container release and then rebuild layered containers and release them
17:25:33 <mboddu> So, how bodhi is going to play in now that it got the container support?
17:26:37 <cverna> mboddu: I am not sure how this will work to be honest
17:27:13 <nirik> well, I assume we would move to a more maintainer model?
17:27:19 <cverna> how does it work when there is a mass rebuild ?
17:27:28 <nirik> maintainer builds, submits update, gets karma in testing, goes to stable?
17:27:47 <cverna> nirik: we can ask the maintainer to push an update every 2 weeks
17:27:59 <nirik> mass rebuilds are done in rawhide only, so no bodhi. (yet)
17:28:02 <mboddu> nirik: Yeah, thats what I am thinking, but can we expect to get constant updates?
17:28:14 <cverna> we want to rebuild all containers when the base image has changed
17:28:34 <bowlofeggs> mboddu: one thing i forgot to mention but that we did discuss a few weeks ago in -releng - bodhi will not manage the base container image
17:29:04 <bowlofeggs> it may be possible to add support for that later if desired, but the base image is different and special in the registry for some reason so the current code does not manage it
17:29:18 <cverna> mboddu: so I think the 2 weeks thing will stay the same
17:29:46 <bowlofeggs> the mass rebuild is probably a separate issue to consider
17:30:08 * mboddu thinks there are more things needs to be discussed here regarding the process
17:30:14 <bowlofeggs> bodhi will be able to handle publishing the mass rebuild if we want, but we probably want more automation around that
17:30:27 <bowlofeggs> to me that's a bit of a different thing than "packager wants to release an update"
17:30:41 <cverna> so bodhi will be used if a maintainer wants to update the container between the 2 weeks release cycle
17:30:47 <mboddu> cverna: mass rebuilds can be done as the same way we are doing now and then create an update for all of them
17:31:01 <mboddu> cverna: Seems like it
17:31:44 <cverna> mboddu: yeah maybe we need to change the ansible so that it submits the updates automatically
17:31:55 <bowlofeggs> to automate mass rebuilds we will probably want buildroot override support in bodhi
17:32:03 <bowlofeggs> whcih i hit a snag with
17:32:30 * cverna thinks we need to play with in in staging
17:32:37 <cverna> s/in/it
17:34:17 <mboddu> cverna: True
17:36:26 <bowlofeggs> alright, i'm gonna take off for lunch
17:36:27 <bowlofeggs> enjoy!
17:36:51 <mboddu> bowlofeggs: Okay
17:37:00 <mboddu> Enjoy your lunch :)
17:37:08 <cverna> bowlofeggs: bon appetit :)
17:37:30 <mboddu> #info There is more than meets the eye's here, we have to think about the process and come up with a plan
17:38:01 <mboddu> bowlofeggs: I will ping you on #fedora-releng as I need some info on other ticket
17:38:06 * nirik has to prep for infra meeting in 20m
17:38:31 <mboddu> nirik: I dont have much, jumping to open floor
17:38:36 <mboddu> #topic Open Floor
17:38:40 <mboddu> Anybody got anything
17:38:54 <Kellin> is the other ticket to ping on the thing I asked about?
17:39:08 <nirik> oh, those mistagged packages from after beta... we should retag those. There's not likely any other fix pending
17:41:10 <mboddu> Kellin: Yes
17:41:53 <mboddu> nirik: Are you talking about older nvr builds getting tagged later than the newer nvr builds?
17:43:15 <nirik> yes
17:46:16 <mboddu> nirik: How can we figure them out? I was just retagging them as they file tickets
17:46:25 <mboddu> all of them*
17:49:42 <nirik> i am not sure sadly.
17:50:51 <mboddu> nirik: Okay, I will see if I can write a script or something to find them out
17:51:49 <nirik> yeah, it's not an easy problem tho. ;(
17:52:04 <mboddu> #info There are some package builds whose older nvr got tagged later than newer nvr and creating problems, should look at on how to find those packages and fix them
17:52:10 <mboddu> nirik: Yeah :(
17:52:14 <mboddu> Anything else?
17:52:16 <Kellin> I had a question wrt/Pungi. mboddu tells me that we always produce certain DVDs with createiso even though it's turned off.  #1) Am I understanding that correctly and #2) Is this expected behavior or is this a known bug in pungi?
17:52:35 <Kellin> s/turned off/marked skipcreateiso/
17:52:50 <nirik> which dvds? the server one should be the only one I would think...
17:53:29 <mboddu> Yeah, Server is snowflake and probably hardcoded in pungi to create the DVD without specifying anything in the configs
17:53:40 <Kellin> mboddu: it looks like it's allowed in the skipcreateiso
17:53:42 * mboddu not sure about it 100%
17:53:44 <Kellin> it has source and no *
17:53:49 <Kellin> so it's not blocking, it's just blocking sr
17:54:40 * Kellin is trying to parse out hearsay from fact.  also things like buildinstall make a ton of images, but they appear to be boot.isos that are fed into other deliverables
17:55:06 <Kellin> so are those considered "release engineering deliverables" on their own merit, or should they be included in other deliverables when creating the list of our deliverable artifacts
17:56:06 <nirik> I think only those things we sync out are deliverables... but some things are needed to make those...
17:56:55 * Kellin nods some.
17:57:11 <Kellin> that's all I had
17:57:20 <mboddu> Okay
17:57:32 <mboddu> I will give back the 3 min to you guys
17:57:36 <mboddu> Thanks for joining
17:57:39 <mboddu> #endmeeting