16:44:11 #startmeeting RELENG (2015-03-16) 16:44:11 Meeting started Mon Mar 16 16:44:11 2015 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:44:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:44:20 #meetingname releng 16:44:20 The meeting name has been set to 'releng' 16:44:20 #chair dgilmore nirik tyll sharkcz bochecha masta pbrobinson pingou 16:44:20 Current chairs: bochecha dgilmore masta nirik pbrobinson pingou sharkcz tyll 16:44:21 #topic init process 16:44:33 who is here? 16:44:45 * sharkcz is here 16:45:13 * nirik is here. 16:45:29 #topic #5931 [Proposal] Move new branch and unretire requests to pkgdb2 16:45:35 https://fedorahosted.org/rel-eng/ticket/5931 16:45:41 * masta is here 16:46:07 need pingu for this 16:46:15 nirik: have we deployed it yet? 16:46:31 no. he was out last week... 16:46:40 I can ask him for status tomorrow 16:46:45 okay 16:46:56 #info hopefully deployed this week 16:47:07 #topic #6016 Use fedpkg-minimal in Fedora buildroots 16:47:14 https://fedorahosted.org/rel-eng/ticket/6016 16:47:20 #info this is now done 16:47:38 nice 16:47:48 how much faster was it? 16:48:14 masta: about 1 minute on arm and 20 seconda on x86 16:48:33 cool, might seem small butin a mass build it will be noticed. 16:48:44 yep 16:48:55 and makes the srpm buildroot less fragile 16:49:01 #topic #5963 Orphaned vulnerable packages in EPEL 16:49:07 https://fedorahosted.org/rel-eng/ticket/5963 16:49:25 AFAIK this has been done now, though there was some complaints about it 16:49:35 yeah, its done 16:50:08 #info this has now been done 16:50:47 #topic #6119 AtomicHost rel-eng integration 16:50:53 https://fedorahosted.org/rel-eng/ticket/6119 16:51:03 SO this has some pretty major issues 16:51:17 rpm-ostree-toolbox is a great tool for end users 16:51:26 but has zero integration into koji 16:51:41 or any of the releng tooling or processes 16:52:26 this needs to be sorted before beta? or ? 16:52:31 we make the existing images using ImageFactory that same as rpmos-tree-toolbox does 16:52:37 nirik: I guess 16:53:04 It should have been sorted for Alpha 16:53:24 since the feature is supposed to be testable by Alpha 16:53:44 we currently make the atomic trees in a mockchroot, which is not really okay 16:53:53 it needs to be a koji task 16:54:04 so we get public logging and visability 16:54:17 so, we just need someone to write that patch? 16:54:30 threebean: yes 16:55:12 there is the other piece that is making the atomic install iso and pxe tree 16:55:25 that really needs to be integrated into pungi 16:56:18 I can look at the koji half and report back next week. 16:56:58 it's already being accomplished in the releng scripts right now, so it won't hold up Beta if it doesn't work out, correct? it's just currently being accomplished in an undesirable way? 16:57:02 there is a reason why we are not using livemedia-creator years after it was written, and it seems that this has gone off and repeated history by walters going off and writing something rather than asking what the requirements are and working with us to come up with an acceptable solution 16:57:15 threebean: right 16:57:36 threebean: the main issue is the desire for the install iso and network install tree 16:58:32 i didn't write livemedia-creator fwiw 16:58:33 I would rather do it once and right, than hack something in, because if we hack something in the chances are high that we won't fix it 16:58:41 walters: I am not saying you did 16:58:49 i'm pretty sure you just did 16:58:57 walters: I am saying you did the same thing, went off and wrote something we can not use 16:59:08 walters: not at all 16:59:17 if you read it as that I am sorry 17:00:03 I think rpm-ostree-toolbox is a great end user tool 17:00:14 it just does not fit into what we need in Fedora 17:00:15 ok let's focus on actionable items here 17:00:26 do you have a concise link/description to the livemedia-creator issues? 17:00:29 the image part we have handled already 17:00:55 walters: there was a few issues with livemedia-creator, biggest being that it could not be run in mock 17:00:57 (would have been nice to get a ping when the topic is discussed at the start btw) 17:01:05 walters: that is fixed and we now need koji integration 17:01:37 walters: we need inteagration into pungi to make the install iso 17:01:52 ah, we're using docker for the chroot creation currently 17:01:52 and we need to have integration into koji to make the atomic tree 17:02:30 walters: we do not currently have anything using docker and without major work its not a suitable means of doing things 17:03:07 we need to be able to cleaning make the compose environment using the needed pieces 17:04:01 i think the mock/docker needs a more detailed discussion 17:04:01 walters: so when we have a new lorax, anaconda, pungi, mash, etc we have to make sure we are using that new version 17:04:22 walters: it is something that can be looked at down the road, but not today 17:05:05 this doesn't really feel like a discussion, but more a list of decisions you've already made 17:05:07 walters: we need to make sure that we can make the deliverable for all possible arches 17:05:25 (and not put in the ticket) 17:05:49 walters: perhaps, it is how we do things, we have long term plans to change that. but short term we do not have the ability to change 17:06:13 walters: I have been nusy and trying to think of the best way to communicate the concerns 17:06:15 does it need to be a custom task, or can we leverage runroot? 17:06:21 s/nusy/busy/ 17:06:40 walters: does it need any special root privs? 17:06:50 everything involving rpm needs root 17:06:56 masta: we do not have runroot working 17:07:14 dgilmore: oh my bad, ok then... custom task for now 17:07:15 (gnome-continuous doesn't, source code all the way to disk images as non-root) 17:07:28 we need pungi integration to make the install tree 17:07:42 fixing that is a much more interesting task 17:07:53 hmm 17:08:10 walters: how gnome-continuos and Fedora do things are very different, they have different concerns and targets 17:08:17 isn't it enough that they share lorax? 17:08:52 walters: we can look at how things are done to see what we can learn, but we have our existing workflows and processes and we need to fit within them 17:09:44 walters: no. though we are going to use a majorly different version of pungi in f23 and it will have to have tighter coupling there 17:09:59 so potentially we can look at something short term for Fedora 22 17:11:38 walters: we have to use the target os to compose teh target os 17:11:55 which I guess seems somewhat strange, but that is how we do thing 17:12:02 did you need me here at the meeting? why not just summarize all of the decisions beforehand in the ticket? 17:12:12 we use mash to make the yum repos 17:13:28 we then use those yum repos to make the install tress, livecds, arm images and atomic repo, we use the install trees and atomic repo to make the cloud images 17:13:41 i'll try to do that now 17:13:45 walters: you are the one taht added teh item to the meeting. 17:14:08 walters: had you come and talked at the start we could have told you the requirements 17:14:23 rather than showing up and saying here is this thing go and use it 17:14:39 that's not *at all* what i was saying 17:14:52 walters: I think that the what you have done is great for end users to make their own trees, images and installers 17:14:58 i was looking for compromise, discussion, cooperation 17:15:00 It is not at all wasted effort 17:15:24 that's why i'm here on irc now, to have a conversation 17:16:16 walters: I am willing to look at doing something for f22. f23 is going to have massively changed compose processes 17:16:24 and i'm willing to change code 17:16:56 walters: not sure you need to change the rpm-ostree-toolbox code. it seems to be a great end user tool 17:17:40 walters: https://git.fedorahosted.org/cgit/pungi.git/log/?h=pungi-4-devel is the pungi rewrite we are working on for f23 17:18:18 we will need to have everything integrated into it 17:18:59 perhaps for f22 we can run lorax in a mock chroot 17:19:04 it is not ideal 17:19:13 so, really here we need: f22 actions and then look more at f23? 17:19:17 because it does give us public visability 17:19:23 nirik: right 17:19:36 so what are those? /me is kinda lost here. 17:19:41 and of the things the only thing we do not currently do is the install media 17:19:56 at least if i understand it correctly 17:20:08 and pxetolive 17:20:20 walters: is that correct? we just need to make the install media? 17:20:41 pxetolive as well 17:21:13 walters: the pxe tree is part of the lorax output when making the install media correct? 17:21:21 that's pxe-to-install 17:21:30 pxe-to-live is for diskless servers 17:21:46 okay, and how is that made? 17:21:50 livemedia-creator 17:22:11 conceptually anaconda itself is a live system, it's a stripped down desktop that runs one app 17:22:22 ::sigh:: okay, apparently we can now run that in a chroot 17:22:33 so livemedia-creator is a slight abstraction of that that drops out the desktop app part and is more configurable 17:22:49 so in theory we will need to run lorax and livemedia-creator in a mock chroot 17:23:08 and that needs a koji plugin to do that? or runroot working? 17:23:12 it's been working fine inside docker containers, FWIW 17:23:32 i'm not opposed to using mock either 17:23:33 nirik: well quickest way is to do it like we are doing pungi 17:23:43 oh yeah. gross. ok. 17:23:53 it is going to make the compose process longer 17:24:06 walters: we can not use docker today 17:24:21 the entire thing needs consolidation and re-writing. I don't think anyone will disagree. ;) 17:24:22 not without a massive amount of work 17:25:06 walters: we have no tooling to make anything but a docker base image 17:25:35 https://github.com/projectatomic/rpm-ostree-toolbox/blob/master/src/py/rpmostreecompose/docker_image.py 17:25:43 and I guess we could make a base image as part of the compose process that had everything we needed in it 17:25:47 it's the ~100 lines of trivial code to yum --installroot + docker load 17:25:57 but it is more work that I am willing to do for f22 17:26:16 (i don't think anaconda should be involved in docker base images myself, but that's a different discussion) 17:26:42 but the above is how -toolbox synthesizes correctly up to date images, like mock does 17:26:52 walters: that is the it was decided internally to make docker base images. we inherited it 17:27:55 the way it was 17:28:17 anyway so for f22 we will run lorax and livemedia-creator in a mock chroot 17:28:29 there may be some good advantages to replacing mock with docker... but not in f22. 17:28:32 ok, so not using -toolbox as it is today 17:28:37 walters: we will need either one or two kickstarts 17:28:42 walters: no 17:28:49 i think i could pretty easily extract the raw code to use lorax for the installer 17:29:45 hmm, what if I made "rpm-ostree-toolbox installer-raw" or so? That rel-eng could run inside mock? 17:30:27 walters: I would rather just feed lorax and livemedia-creator kickstarts and getting the output 17:31:13 #action walters to look at running lorax and livemedia without -toolbox 17:31:32 walters: do you have kickstarts? 17:31:37 yep 17:32:08 https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-cloud-atomic-pxetolive.ks 17:32:53 walters: its the same kickstart for both? 17:33:04 there's quite a lot that's suboptimal about the above, which circles back to my desire to be writing code and fixing content issues 17:33:26 a kickstart for the installer? 17:33:41 it's just lorax, except for https://github.com/projectatomic/rpm-ostree-toolbox/blob/master/src/py/lorax-embed-repo.tmpl 17:34:26 walters: a kickstart for lorax and one for livemedia-creator 17:34:52 lorax doesn't take kickstarts (that I'm aware of), it has templates that come with the tool itself 17:35:01 walters: so we need two kickstarts in spin-kickstarts 17:35:28 walters: we do not use lorax directly in fedora, pungi takes kickstarts 17:35:51 so i don't want to take over this whole meeting time, this seems like something where we should be determining high level requirements, allowing each other to work on action items asychronously? 17:36:36 and IMHO those should be 'get it working enough now in f22 in existing processes' and also 'make it use a better process potentially in f23+' 17:36:46 walters: --add-template=ADD_TEMPLATES Additional template to execute 17:36:59 so we will need a lorax templace in spin-kickstarts 17:37:18 and we will add it when executing lorax 17:37:55 walters: we should make a directory for teh lorax template 17:38:27 walters: for f23 we will need to integrate into pungi 17:40:15 spin-kickstarts/atomic-installer/lorax-embed-repo.tmpl ? 17:40:16 #action dgilmore and walters to get things lined up in spin-kickstarts and have the tasks running in mock 17:40:23 walters: that is fine 17:40:40 okay lets move on 17:41:08 #topic #6130 Remove all permissions when packages are retired in a branch 17:41:11 thanks, pushed 17:41:15 https://fedorahosted.org/rel-eng/ticket/6130 17:41:46 I think we should get pingou's input here. I seem to recall we had it doing that at first and it caused problems. 17:41:52 great, thanks for the feedback, i'll see what i can do to extract some bits from -toolbox for use in mock. (FWIW I think -toolbox is not the best code in the world, but it is tested and working, so the key is to keep that aspect while moving forwards) 17:41:53 yeah 17:42:31 walters: I think toolbox is a great tool for people to build and deploy thier own atomic repos 17:43:01 nirik: yeah, I think the request has a bit too much emotion behind it 17:43:17 and we need some technical opinion 17:43:56 #info neeed to have some feedback from at least pingu and need to look into it closer to see the technical pros and cons for making such a change. 17:44:08 #topic Secondary Architectures updates 17:44:09 #topic Secondary Architectures update - ppc 17:44:19 sharkcz: any update here? 17:44:32 yes, a bit 17:45:34 pbrobinson tried a compose last week, the process worked, but we hadn't enough content in the f22-Alpha tag cloned from primary like anaconda (in the exact NVR), so it failed, we should get this fixed this week 17:46:13 the last known big endian related bug in gcc was fixed last friday, so should be safe using the llatest gcc 17:46:33 cool 17:47:14 #topic Secondary Architectures update - s390 17:47:41 how is s390 sharkcz? 17:48:13 I tried a compose last Thursday mainly to see whether the tools work, and they do, we also hadn't the complete f22-Alpha so it was from the actual content 17:48:22 okay 17:48:31 how far behind is s390 and ppc? 17:50:06 haven't measured it today, but should be ~200 builds for s390 (it has updates-testing too since today) and a bit more for ppc 17:50:15 okay 17:50:20 we got behind due the gcc 17:50:25 so maybe Alpha next week? 17:51:18 yes for ppc, for s390 I'll probably skip it due the known bugs (kernel panic at the end and couple more), or include the latest kernel, will see 17:51:26 okay 17:51:32 #topic Secondary Architectures update - arm 17:52:00 http://armpkgs.fedoraproject.org/compose/22_Alpha_RC1/ 17:52:08 there is a RC1 compose for Alpha 17:52:19 I asume pwhalen is getting people to test it 17:52:28 cool 17:52:46 though it looks like it may have failed 17:52:48 dgilmore, no, incomplete 17:53:01 pwhalen: any idea what the holdup is? 17:53:42 there are some kernel hang issues pbrobinson was fighting for the compose, I havent talked to him today 17:53:42 xorg-x11-drv-qxl is needed by xorg-x11-drivers-7.7-12.fc22.aarch64 is in the log 17:53:58 :( okay 17:53:58 my understanding was he hacked aroudn that for now 17:54:32 alright 17:54:44 hopefully Alpha for aarch64 next week also 17:54:47 #topic Open Floor 17:54:55 anyone have anything for open floor 17:55:53 I guess I have one thing 17:56:26 rawhide is installable right now, we are using pungi 4.0 development branch in rawhide 17:56:38 so it is using a very different code base 17:58:48 anyway 17:58:52 #endmeeting