16:33:13 #startmeeting RELENG (2016-01-25) 16:33:13 Meeting started Mon Feb 22 16:33:13 2016 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:33:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:33:13 The meeting name has been set to 'releng_(2016-01-25)' 16:33:13 #meetingname releng 16:33:13 #chair dgilmore nirik tyll sharkcz bochecha masta pbrobinson pingou maxamillion 16:33:13 The meeting name has been set to 'releng' 16:33:13 Current chairs: bochecha dgilmore masta maxamillion nirik pbrobinson pingou sharkcz tyll 16:33:16 #topic init process 16:33:32 o/ 16:33:33 * nirik is sort of here, but also trying to fight monday morning fires. 16:33:35 Hi there 16:33:39 * sharkcz is here 16:33:41 .hello maxamillion 16:33:42 maxamillion: maxamillion 'Adam Miller' 16:33:55 * pbrobinson is here.... sort of! 16:35:19 lets get started 16:35:33 there is no tickets for meeting 16:35:40 #topic branching 16:36:01 #info tomorrow is f24 branching 16:36:03 * pingou has something for this 16:36:11 so we need to deliver composes 16:36:15 pingou: shoot 16:36:26 so few ideas: do we want to turn off fedmsg before branching to avoid spamming everyone? 16:36:56 by default the script that adjusts the branch on repo takes the first commit in the repo, that's probably not something we want for branching 16:36:58 we didn't the last few times and it took a while to catch up. ;) 16:37:21 (iirc it's something we ran into last time, the branch pointed to the wrong commit) 16:37:50 pingou: we can not turn off fedmsg 16:38:18 not without locking everyone out from git 16:38:30 I suppose we want the master/head commit... which might be ahead of what actually built in rawhide, but should be close. 16:38:51 for mass branching we want what is HEAD for master 16:39:10 but for regular branches where there is no built content we want to first commit 16:39:27 dgilmore: we could turn off fedmsg during the branching, run the script afterward to sync the git repos (manually) and restart fedmsg 16:39:55 pingou: we can not 16:40:14 pingou: not unless we turn off all access to git during branching 16:40:20 dgilmore: why? 16:40:23 which we used to do with CVS 16:40:28 git doesn't rely on fedmsg 16:40:36 pingou: because other people can commit 16:40:38 yeah, true. 16:40:41 because you don't want people not gettign notifications of commits 16:40:43 and those notifications have to get out 16:40:53 ah ok for this aspect 16:41:02 true there 16:41:25 so we'll spam everyone for the branching 16:41:26 wqew either lock it down and send no notifications, or leave it open and send all 16:41:31 yeah 16:41:46 but we still probably want to turn off fedmsg-hubs on pkgs01 during the branching 16:41:55 to avoid creating the branch at the wrong commit 16:42:24 pingou: okay 16:42:44 we do want the branch to have the rigth commit 16:42:59 I can take care of doing this part if people are ok with it 16:43:11 (branching in pkgdb and then adjust the git repos) 16:43:16 pingou: we will need to coordinate it but sure 16:43:25 cool 16:43:50 just fmy, when is it supposed to start? 15UTC? 16:44:02 pingou: no set time 16:44:05 k 16:44:10 pingou: we do it when everything is ready 16:44:27 I can practice in stg in the morning so hopefully ducks are in line when you come online 16:44:45 pingou: we are likely going to do it late to try get the golang rebuild in first 16:45:28 ok 16:45:31 #info branching will start late to let golang rebuild finish 16:45:39 then I might not make it 16:45:56 pingou: understandable 16:45:59 if so, I'll document the procedure and send it around 16:46:07 (from what I did in stg) 16:46:23 #info fedmsg for branching cannot be turned off because notifications of other commits need to be sent 16:46:32 looking at the golang build now, I'm not sure we'll be too late, but I'm not convinced the list given me is correct, will know more about it in a few hours 16:47:01 I have a compose running right now. I am hoping taht it has everything we need, except atomic that needs to be bolted on 16:47:05 but it doesn't look more than around 100 odd packages (which is why I'm not convinced it's correct) 16:48:19 if it does not work out, it does not work out 16:48:28 but if we can make less work we should do it 16:49:19 we also need to actually test a secondary arch compose today 16:49:35 yes, so it only looks to be a few 100 packages 16:49:52 #info golang is ~100 packages 16:50:09 #topic Secondary Architectures updates 16:50:11 #topic Secondary Architectures update - ppc 16:50:18 lets get the secondaries done 16:50:22 how is ppc? 16:51:13 we're around 6K behind on mass rebuilds, so a little to go, getting there, not as fast as I would like 16:51:27 okay 16:51:29 should be done this week one way or the other (or I might go insane) 16:51:48 got some changes to infra to do this week 16:52:05 should be ready to compose by end of the week 16:52:47 cool 16:53:12 ppc hub is not yet moved to ansible, right? 16:54:06 nope, should be happening this week with a move of IPs etc 16:54:11 cool 16:54:22 pbrobinson: if I can help with redoing ppc8-01 or ppc hub,etc, let me know 16:54:26 #info ppc koji hub to be ansibilised soon, likely this week 16:54:28 * nirik would love to get that done too. 16:54:34 nirik: you will be ;-) 16:54:59 nirik: plan is to get initial infra ticket for vlan move done tonight, just trying to get other stuff out of the way 16:55:32 ok. 16:55:35 nirik: and move the compose devices too so we can get rid of the last of the P7 stuff 16:55:47 * pbrobinson needs more hours in the week! 16:55:56 pbrobinson: that or more clones 16:55:59 cool. We actually should be able to just add the new vlan on another interface and use it... 16:56:04 :-) 16:56:20 * nirik wonders if those p8's for cloud have shown up yet... I couldn't figure out how to track them 16:56:36 nirik: I'm not sure we have enough patched in, we're already using 3, will look later this evening 16:56:42 nirik: its teh cloud, its magic 16:57:00 I am pretty sure theres at least one more connected, but also if not, we could ask DC folks to connect them for us. 16:57:06 "git push to the motha fuckin' cloud" - threebean 16:57:16 that's basically my favorite quote like ... ever 16:57:16 threebean++ 16:57:17 dgilmore: Karma for ralph changed to 25 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:57:45 anything ppc wise we need to discuss? 16:57:55 nope 16:58:00 #topic Secondary Architectures update - s390 16:58:09 sharkcz: how is teh world acording to s390 16:58:22 dead? 16:58:26 * pbrobinson hides 16:58:29 mass rebuild in progress, first gcc6 s390 specific bug appeared 16:58:39 * dgilmore notes that he cleaned up eol releases and moved them to archive 16:58:49 which freed up lots of disk for s390 16:58:59 yep 16:59:04 sharkcz: s390 bugs sound fun 16:59:18 I think there will ppc ones too ... 16:59:27 no doubt 17:00:35 remaining issue is how to mount /mnt/koji for the composer 17:01:27 sharkcz: yeah. I am really not sure how we are going to do that 17:01:43 sharkcz: pungi does have a yum repo mode 17:01:56 but I am not sure how we could make it work 17:02:21 sharkcz: we will have to work with nirik, I wonder if we can put a s390 node on the fedora vpn 17:02:28 and do nfs over vpn 17:02:40 pretty ugly 17:02:44 I don't think that will help any. 17:02:52 gluster replica? 17:03:00 nirik: why not? 17:03:04 I think the only way to make it work is to do work, copy, do work back 17:03:28 networking folks are dead set against vpn over the wan. 17:03:34 sorry nfs 17:03:47 which is why I said over fedora vpn 17:03:53 then they do not have to know 17:03:59 but it is not great 17:03:59 * nirik frowns 17:04:20 I get their concerns 17:04:32 we will have to look at all options 17:04:41 and likely s390 will be some special child 17:04:42 so it has to be run on that arch? 17:04:43 not sure we can fix it in this meeting 17:04:49 nirik: some of it does 17:05:18 same as some of it has to be run on x86_64, i386, armhfp etc 17:05:30 I doubt we can fix it now 17:05:43 nirik: maybe we should all have a meeting to look at it later 17:05:51 yeah, all I can think of is splitting it and doing a sync over and back... but thats not great either 17:06:06 anything over the wan is going to be dirt slow 17:06:11 yeah 17:06:28 qemu s390 in phx2? ;) 17:06:31 * nirik runs 17:06:39 the making of teh boot.iso and install repo and the dvd are what needs s390x 17:06:49 nirik: it may be fast enough :P 17:06:57 run it on ppc64be 17:07:21 it could be an option 17:07:48 +1, especially if the user-space emulation would work, not the full system 17:07:50 #info we need to figure out some s390 compose issues 17:08:16 anything else anyone wants to discuss in s390 land? 17:08:31 not from me 17:08:33 #topic Secondary Architectures update - arm 17:08:37 pbrobinson: how is arm? 17:08:49 about 5K packages to go 17:08:51 the hub moved to being ansibilised correct? 17:08:53 mostly looking OK 17:08:59 the hub is now ansible 17:09:04 awesome 17:09:12 in fact 100% of the arm.koji infra is now ansible 17:09:14 #info arm hub managed by infra ansible 17:09:34 #info arm koji infra 100% managed by infra ansible 17:09:56 that's awesome 17:09:59 we have a couple of minor issues around redirects that have issues with the hub post rebuild, I need to work with nirik to work out the last of the issue and get them fixed up 17:10:25 sure 17:10:40 cool 17:10:52 then next up once I've dealt with the PPC stuff is to get the moonshot commissioned 17:11:22 * nirik nods. 17:11:23 there's still some kernel work I need to chase on that one to work out the details 17:11:31 but we should be OK RSN 17:11:39 cool 17:12:22 basically next up on the list there is pungi4/images and friends 17:12:28 okay 17:12:38 we should dig into that today if you have time 17:12:46 I don't have time today 17:12:49 okay 17:13:18 I am planning to setup branched to use the new process 17:13:19 I have some key bits I need today before branching and have a house inspection tomorrow 17:13:20 is the plan to land pungi4 today before branching? 17:13:35 nirik: that is my goal 17:13:39 cool. 17:13:57 dgilmore: does that mean we need to reinstall branched-composer and rawhide-composer as f23? 17:14:05 at the least setup branched with it 17:14:09 I'll ensure I get to pungi4 mid week but I don't have enough hours for that in secondaries today 17:14:15 and have rawhide follow soon 17:14:25 ok, IMHO it would be nice ot move them both at once. 17:15:49 it would 17:16:00 and thats what I am going to aim to do 17:16:18 anything aarch64 related? 17:17:21 #topic Open Floor 17:17:21 not from me 17:17:29 I have one thing for open floor 17:17:33 so to continue on 17:17:44 #info compose process is aiming to change today 17:17:52 maxamillion: go for it 17:18:00 I'm going to be deploying the koji-containerbuild plugin to stage today so I *might* break stage koji intermittently through out the day, my appologies in advance 17:18:32 maxamillion: :D no problem 17:18:38 :) 17:18:40 oh, I had 2 quick things. 17:18:47 nirik: go for it 17:18:51 have 1 item too 17:19:25 1) I've gotten most of the builders reinstalled. Hoping to do buildhw's today... arm socs seem a bit unstable of late, but I am not sure why yet. 17:19:34 I have one also 17:19:41 #info it was great seeing many of you folks during the DevConf.cz trip and Brno meetings :) 17:19:42 nirik: cool, thanks 17:19:54 decause++ 17:19:54 maxamillion: Karma for decause changed to 20 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:20:05 2) I am planning on reinstalling all of staging in the next few days. Will try and ping everyone that might be using it before I do... but if you have unfinished junk on any staging machine, make sure you save it somewhere else too 17:21:11 nirik: cool. thanks. I think I have everything moved to prod now 17:21:26 nirik: but maxamillion is messing around in stage 17:21:30 ok. I will make sure I don't break maxamillion's stuff. ;) 17:21:39 and lsedlar has been trying to get composes working in stage 17:21:55 nirik: it'll be broken already, don't worry :) 17:22:13 nirik: it'll all be in ansible though so if you re-install everything, it should just all magically work 17:22:21 *should* 17:22:23 maxamillion: :D 17:22:32 famous last words 17:22:42 nirik: or at the very least, be equally as broken as it previously was 17:22:46 right. I plan to nuke everything (except db hosts) and ansible reinstall it all 17:22:57 cool 17:23:17 anything else? 17:23:27 pull requests in dist-git, there was a discussion on fedora devel list and the outcome was they would help in number of situations, how to make it an official RFE? 17:23:53 sharkcz: there was a discussion on teh infra list also 17:24:16 sharkcz: someone would need to work with pingou and get it developed and setup in stg 17:24:19 ah, seems I'm not subscribed there 17:24:36 once we were sure of it working we could promote to prof 17:24:37 prod 17:24:56 is there already a ticket? 17:25:15 nirik: ^ 17:25:19 not sure if tehre is 17:25:28 there's been a lot of discussion... not sure if there's a ticket. 17:25:48 we would need to work out a bunch of things first, so I would prefer we finish discussing before we file a ticket 17:25:54 I do not remeber a ticket 17:26:03 nirik++ 17:26:21 there was more discussion about it in pingou's recent gitolite stuff 17:26:24 I think it is something we shoudl work towards 17:26:32 I think it would be nice, yeah 17:26:53 but until we have a concrete plan we should hold off assigning work 17:27:35 being able to do PR's could be a nice way to find comaintainers and also make sure people submitting patches get credit, and bugs get fixed faster. 17:27:51 nirik: +1000 17:28:13 nirik: indeed 17:28:29 small package patches in bugzilla do not work well 17:29:06 dgilmore: it's not too bad with git-bz... but pull requests still would work much better :) 17:29:31 bochecha: I have seen patches sit forever in bz 17:29:42 pull requests may not fix that 17:29:47 sure, I don't think that's a problem with bugzilla itself though 17:29:49 but it should make it more visible 17:29:55 then something could be done 17:30:02 agreed 17:30:40 #info everyone agrees we should move to enabling pull requests for dist-git 17:30:51 anything else? 17:31:07 https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject.org/thread/LMCW5NVNCCCGQTB6ONRTCB2QP2IOBIAJ/ 17:31:26 just wanted to make sure everyone saw that thread 17:31:36 and chimied in if the had concerns or ideas? 17:32:19 haven't much time yet to read it carefully 17:32:51 I still have not fully caught up from Fosdem and devconf 17:33:10 but jwboyer pinged me and I made sure I followed up on it 17:33:21 it is a big change in how we do things 17:34:20 it should probibly get comment from devel list sometime before we do it too. 17:34:27 nirik: indeed 17:34:41 I had suggested starting on releng tor efine it a bit 17:34:46 then take to devel 17:35:11 we will not make any change before f25 17:35:21 but it may not be until f26 17:35:30 I would like to see things happen a bit sooner 17:38:08 anyway 17:38:15 if nothing else I will end teh meeting 17:38:32 #endmeeting