16:35:33 #startmeeting RELENG (2016-01-04) 16:35:33 Meeting started Mon Jan 4 16:35:33 2016 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:35:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:35:33 The meeting name has been set to 'releng_(2016-01-04)' 16:35:40 #meetingname releng 16:35:40 The meeting name has been set to 'releng' 16:35:40 #chair dgilmore nirik tyll sharkcz bochecha masta pbrobinson pingou maxamillion 16:35:40 Current chairs: bochecha dgilmore masta maxamillion nirik pbrobinson pingou sharkcz tyll 16:35:43 #topic init process 16:35:57 \o/ 16:36:02 * pbrobinson waves 16:36:05 .hello maxamillion 16:36:06 maxamillion: maxamillion 'Adam Miller' 16:36:10 * sharkcz is here 16:36:12 morning. 16:36:20 hello 16:37:00 #topic Secondary Architectures updates 16:37:02 #topic Secondary Architectures update - ppc 16:37:07 pbrobinson: how is ppc? 16:37:43 we're a little behind, overall not bad. 16:38:01 cool 16:38:11 the builders should be bought up to F-23 shortly, just awaiting firmware and one or two other bits 16:38:20 :) cool 16:38:35 I kinda expect all se condaries will be a bit behind after the holidays 16:38:36 possibly some other infra changes, I'm trying to align it all to do together 16:38:47 okay 16:39:05 #info ppc slightly behind currently 16:39:17 #info updating builders to f23 asap 16:39:25 anything else? 16:39:59 nope 16:41:30 #topic Secondary Architectures update - s390 16:41:35 sharkcz: how is s390? 16:42:11 it looks good, should be up-to-date with primary 16:42:35 #info s390 up to date with primary 16:42:36 I'm now working on updating the builders to f23 16:42:46 #infor builders being updated to f23 16:42:52 #info builders being updated to f23 16:43:20 sharkcz: how is the hub? is tehre anything left with teh ansible migration? 16:44:45 I think there is not, after the shared "shadow" vm will be deployed, the hub function itself is ok 16:45:03 but have one question - are you pruning the signed rpms from EOLed distros? 16:45:11 to free some disk space 16:45:14 sharkcz: yes 16:45:54 we purge the signed rpms for EOL releases 16:46:09 ok 16:46:16 the signed headers still exist and the signed rpm can be regenerated 16:46:53 has that caused some issue? 16:47:00 in theory it shouldn't make much difference if the netapp has de-dupe enabled 16:47:04 sharkcz: are there ansible playbooks to deploy shadow koji instances now? 16:47:28 dgilmore: nope, just thinking about space consumption 16:47:29 maxamillion: what do you mean by shadow koji instances 16:48:32 pbrobinson: maybe I don't know, I've still never seen good documentation on just what the hell "shadow koji" is and how to set it up 16:48:33 maxamillion: shadow is a script from koji-utils and a config and lot of know-how :-) 16:48:46 yeah, nvm me 16:49:19 maxamillion: shadow is the process of mirroring builds from primary to secondary koji 16:49:27 maxamillion: there is koji-shadow, which is different from the arch specific koji instances, the later can be deployed with ansible and all of them should be done by the end of the month 16:49:35 maxamillion: I think you mean secondary koji 16:49:47 with the shared shadow vm we will setup a git repos and some processes around it 16:50:07 yeah, we don't need to get into it right now ... this is just another area where koji badly needs documentation 16:50:19 config is eg. http://ppc.koji.fedoraproject.org/shadow/koji-shadow-f24.conf (the long excludelist is generated) 16:50:23 maxamillion: the VM to run koji-shadow for all of those will be ansibled once I've got to it, also hopefully in the next couple of weeks 16:50:31 maxamillion: its nothing to do with koji honestly 16:50:40 dgilmore: how isn't it? 16:50:42 maxamillion: its a fedora specific thing 16:51:10 the whold secondary and koji-shadow work 16:51:13 whole 16:51:28 anyway 16:51:43 #topic Secondary Architectures update - arm 16:52:24 pbrobinson: how is arm? 16:52:45 We didn't get to migrating the hub/db before the break... should be ready to do that anytime we want to schedule it this week. 16:52:48 I know nirik got a new arm hub setup 16:53:04 arm is pretty much up to date in terms of builds 16:53:21 #info arm is up to dat builds wise 16:53:40 nirik: yea, I'm pretty much ready to go, I've got 1 or 2 small things I need to do, how's Wed for you 16:53:50 sure, works for me. 16:53:55 what time? 16:54:32 nirik: I'll cross check stuff tomorrow but once I've done those bits pretty much when ever is good for you 16:54:55 #info arm hub to be migrated to ansible version this week 16:54:55 likely could do it tomorrow or any time after actually if it's better 16:54:56 cool. now that fesco is fridays my wed should be pretty open 16:55:19 so, just ping me when ready and we can get it done. ;) 16:56:15 nirik: I moved the rawhide nightly compose over to a rel-eng ansibled aarch64 box before xmas, so it should have zero special case bits and basically be like primary in that regard now 16:56:42 very nice. ;) 16:57:39 nirik: yep, the hub will be the last bit of non ansible arm.koji infra, and hub/compose boxes the last for PPC and I plan to have them crossed off RSN 16:57:40 cool. anything else? 16:57:55 excellent. 16:58:25 none from me, just awaiting the outcome of the live-media-creator image stuff in koji outcome for aarch64 stuff from my side 16:58:53 dgilmore: not sure if you've any update on that, i'm likely a bit behind 16:59:01 okay, I will cover that in a sec 16:59:21 #topic rawhide changes 16:59:23 cool 16:59:42 so before christmas I spent a lot of time working on changes to make rawhide be a full compose 16:59:52 I have yet to test secondary arches at all 17:00:12 so it turned out that livemedia-creator is not at all suitable for our needs 17:00:27 I can test that once we have it enabled and documented for primary 17:00:33 we do need to move off of livecd-tools and appliance-tools 17:00:52 so we are scaling back the changes for f24 17:01:11 as a sign of goodwill we will move to livemedia-creator 17:01:50 I am going to either write a patch for livemedia-creator or write a wrapper 17:02:02 so what changes will be postponed, what changes will happen, what's missing? 17:02:04 the output from building livecds is not suitable for delivering 17:02:18 bummer. ;( I assume livemedia-creator authors aren't interested in adjusting things much? 17:02:20 pbrobinson: arm disk images are not possibel without virt 17:02:51 there is a meeting lined up between releng and anaconda teams to go over requirements 17:03:12 dgilmore: from a link you provided me before, wasn't it a possibility it could be done some other way but needs some changes (dm-mapper comes to mind?) 17:03:27 huh... I've used LMC to generate arm disk images for aarch64 (without virt) 17:03:31 when is the meeting? 17:03:35 https://www.redhat.com/archives/anaconda-devel-list/2015-December/msg00019.html is where I started communicating with teh anaconda team 17:03:52 the pxe live images might be another story 17:03:57 pbrobinson: we are going to reach out to the lvm team also to see what we can do there 17:04:07 maxamillion: no you did not 17:04:16 masta: ^^^ 17:04:17 dgilmore: what? 17:04:19 sorry maxamillion 17:04:20 oh 17:04:21 rgr 17:04:25 :) 17:04:48 masta: you did not do it in a clean environment provided my a mock chroot 17:05:18 that is correct 17:05:25 masta: so you did not test it 17:05:38 because it is not possible to do what we need 17:06:08 anaconda blows up trying to setup the storage for a arm disk image when run in a chroot 17:06:35 which we need to do to ensure we run the correct version of lorax (provider of livemedia-creator)' 17:06:55 pxe-to-live is super special 17:07:10 right, that I thought was to be solved with special care for populating /dev in the chroot 17:07:11 you have to actally run lmc twice 17:07:15 doesn't pxe-to-live need virt? 17:07:42 you need to build a disk image in one run, then run it a second time to convert it to teh live environment 17:07:58 dgilmore: that is correct 17:08:20 it needs to chain 17:08:59 pxe-to-live really needs to go back to the drawing board and be redesigned to work on a sane manner and provide the output in one run 17:09:50 so for f24 we will only use lmc to make live media 17:10:01 does anyone in our group really understand the process to produce the pxe-to-live well enough to work with those teams to get that done? (I certainly don't) 17:10:32 maxamillion: not sure we need to. 17:10:53 though atomic entirely breaks our rules for how to define things 17:11:55 dgilmore: so appliance-creator will be used for arm images, and livecds will move to lmc? 17:11:57 pungi going forward breaks the rules also 17:12:17 pbrobinson: yes, and we will continue to not do pxe-to-live 17:12:37 dgilmore: which rules are those and is this something where the rules should be revised or something needs fixing? 17:13:04 what is pxe-to-live used for? Is that atomic stuff? 17:13:04 maxamillion: we have stated that all deliverables need to be defined in comps and kickstarts 17:13:14 pbrobinson: yes it is atomic stuff 17:13:40 maxamillion: pungi4 uses xml and atomic is mostly in json files 17:14:40 * pbrobinson awaits the next build tool using yaml ..... 17:14:57 dgilmore: ah 17:14:57 pbrobinson: shut up, it is bound to happen 17:15:01 do not give ideas :P 17:15:05 :) 17:15:06 ha 17:15:23 * maxamillion starts writing koji 2.0 yaml support 17:15:28 >.> 17:15:34 so that is the general status of lmc 17:15:42 * dgilmore kicks maxamillion 17:15:56 pungi I have been hgitting bug after bug 17:16:10 I have been filling issues in pagure as I hit them 17:16:13 pungi is "fun" 17:16:27 maxamillion: sicko! 17:16:32 it's fragile 17:16:34 pbrobinson: note the quotes! 17:17:13 I was hoping to switch rawhide before the break, but I was not confident enough in the output 17:17:50 https://kojipkgs.fedoraproject.org/compose/rawhide/ is the list of composes we currently have 17:18:26 if people could dig through and see anything that they think is wrong please do 17:18:40 the Everything repo currently has no multilib 17:19:25 https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-24-20151218.n.3/ is the last complete compose 17:20:17 we pretty much have 2 weeks to get rawhide switched 17:20:58 Time is running out fast 17:20:59 dgilmore: do you have any notes, anything we should look at specifically, any particular concerns etc? 17:21:33 pbrobinson: some of them like the naming there is a patch that blew up applied 17:22:17 pbrobinson: I still need to ensure that we do things like split out the Cloud install tree from the images 17:23:01 pbrobinson: at this point just having another set of eyes looking over to see if things look odd 17:23:17 some of the oddities we are stuck with 17:23:29 OK, I'll do my best to have a look over tomorrow 17:23:34 https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-24-20151218.n.3/compose/Cloud/i386/iso/ like the manifest file 17:23:47 not sure its a bad thing 17:23:57 just not something we have had before 17:24:18 it is a list of the contents of the iso 17:24:29 what does the .n.3 denote? 17:24:39 the .n is nightly 17:24:50 the .3 is the 4ths run for the day 17:24:53 4th 17:25:03 the first run starts with .0 17:25:12 ah, ok. Wonder if it might be better to just be -hh-mm instead, but whatever. ;) 17:25:15 so generally it should be n.0 17:25:21 generally 17:25:36 unless we need to restart for a blowup 17:26:16 each compose has a composeid 17:26:27 https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-24-20151218.n.3/COMPOSE_ID 17:26:37 Fedora-24-20151218.n.3 for that one 17:27:17 any chance we could have a newer 2016 compose done? 17:27:35 pbrobinson: no. pungi is currently busted completely 17:27:45 ah, useful :-D 17:28:03 I need to work with lsedlar to get his enhancements fixed and working 17:28:27 hopefully we will get one soon, or else we might need to punt to 25. ;( 17:28:37 https://pagure.io/docs/pungi/ has some docs 17:28:44 they still need work 17:29:38 but as new things are added docs come with them 17:29:51 nirik: we have a small window :( 17:30:04 any other questions? 17:30:14 not from me 17:30:15 not sure I totally covered everything? 17:30:38 dgilmore: any other koji enhancement planned for f24? 17:30:53 * nirik has nothing on rawhide changes, have a few small things for open floor. 17:31:01 pbrobinson: just maxamillion's osbs support 17:31:26 and that's just a plugin 17:32:04 okay lets move on 17:32:09 #topic open floor 17:32:14 nirik: you are up? 17:32:22 just 2 quick things: 17:32:53 1. I see there's a gcc change proposed and they are asking for a mass rebuild, but we have no mass rebuild scheduled, so it might need schedule adjustment. 17:33:02 (I guess thats more a fesco thing, but wanted to mention it) 17:33:14 nirik: I filed a ticket with FESCo already 17:33:29 2. Next week smooge and I will be out at the phx2 datacenter... so if there's any hands on work people need, please ask this week so we can schedule things. ;) 17:33:33 https://fedorahosted.org/fesco/ticket/1522 17:33:41 great. :) 17:34:22 nirik: sorry https://fedorahosted.org/fesco/ticket/1519 17:34:34 ok. cool. Anyhow, thats all I had. 17:34:46 the first ticket was the change 17:35:13 okay, I am not sure 100% on DC work 17:37:05 does anyone else have anything? 17:37:26 #info if you need something done in the Data Centre next week please talk to nirik this week 17:40:32 if nothing else I will close the meeting 17:41:14 oh 17:41:17 I kind of do 17:41:52 I'm going to be updating the docker base image for Fedora 23 and Rawhide soon for https://github.com/docker-library/official-images/issues/1235 ... we don't have an official policy around this, so it's a bit ad-hoc 17:42:20 I'm not sure if there's any motivation to craft an official policy around the docker image or not but I thought I'd at least mention it 17:42:54 maxamillion: in my ideal world, when we make a change to any package in it, we update it and push the update 17:43:25 with PDC we should be able to get the knowledge of when something in it changes 17:43:38 dgilmore: I'm all for that, but we need testing ... right now I basically just fire it up and do a couple basic things, call it good enough, and submit a request for docker to pull the latest image 17:44:29 maxamillion: sure, that would be the Base WG (which is basically dead) working with QA on it 17:44:37 fun 17:44:41 alright 17:44:58 the Base WG owns the docker base image 17:45:11 maxamillion: and there are two members here, masta and me 17:45:16 I'll reach out to them on the mailing list to discuss that 17:45:17 oh 17:45:19 o/ 17:45:36 =) 17:46:57 lets wrap up 17:47:02 #endmeeting