17:00:34 #startmeeting RELENG (2018-07-05) 17:00:34 Meeting started Thu Jul 5 17:00:34 2018 UTC. 17:00:34 This meeting is logged and archived in a public location. 17:00:34 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:34 The meeting name has been set to 'releng_(2018-07-05)' 17:00:34 #meetingname releng 17:00:34 The meeting name has been set to 'releng' 17:00:34 #chair nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu Kellin dustymabe 17:00:34 #topic init process 17:00:35 Current chairs: Kellin dustymabe masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll 17:00:46 * masta lurks 17:00:46 morning 17:03:29 Okay, lets start 17:03:34 #topic #7605 block libvncserver from epel7 17:03:39 #link https://pagure.io/releng/issue/7605 17:04:00 Okay, its more of a question that I have 17:04:13 Now, when the pkg is moved to RHEL, we block it in epel 17:04:36 But over here, its arch specific 17:04:46 What is the correct action that we have to take here? 17:05:20 nothing. we should not need to block it. 17:05:45 the limited arch ones should be rpm 'older' than the rhel ones... so they shouldn't interfere. 17:05:53 well, we should revert the block I guess here. 17:06:00 Okay 17:06:20 nirik: Thanks, I just want to bring it up and know the right thing to do, before I hastily done anything 17:06:40 #info mboddu will revert the block in epel7 17:07:01 makes sense, so long is the one in RHEL wins the nvr comparison 17:07:02 if I had to do it over I wouldn't have supported these limited arch packages, but we have, so oh well... 17:08:49 nirik: Well, one can expect :) 17:09:08 smooge lurks 17:09:22 #topic Open Floor 17:09:26 nirik: first rule of special requests, they won't be special after the first one =) 17:09:35 * cverna lurks too 17:09:42 Kellin: quite. 17:09:53 cverna: While you are here, any update on container release? 17:10:11 #info nirik cleaned up old torrents, we should add to the EOL sop to remove torrents on release end of life. 17:10:45 nirik: funny you should mention torrents... 17:10:54 =D 17:11:07 nirik: Thanks 17:11:08 mboddu: I am currently deploying a new OSBS to prod 17:11:28 mboddu: so I guess next week we should be able to do a release 17:11:54 I am planning to test bodhi updates for container in stg also 17:12:08 related: https://pagure.io/fedora-infrastructure/issue/7081 17:12:29 indeed :) 17:12:38 Also related to https://pagure.io/releng/issue/7439 17:13:43 and https://pagure.io/fedora-infrastructure/issue/6874 17:13:56 oh my tickets maze 17:13:56 #info container release might be pushed to next week 17:14:57 Anybody got anything else? 17:15:32 do we need to prep anything for mass rebuild? 17:15:34 smooge: Infra outage is done? Or is there anything still remaining to update? 17:15:42 starts next week 17:15:52 all side tags need to be done/merged. 17:16:05 nirik: Yes, I am going to send out an email to devel list and look at all the change requests and side tags 17:16:25 did we need to fix any scripting? I think last time there was some problems? 17:16:42 mboddu: we should pick a small subset of impacted packages and test a small batch to ensure everything does what we expect 17:16:48 nirik: puiterwijk and I worked through most of that 17:16:55 nirik: as far as I know, it should all be fine now 17:17:01 great. yeah, a test might be nice to run... 17:17:05 nirik: Nope, not that I can think of 17:17:41 we need this reviewed: https://pagure.io/releng/pull-request/7345 17:17:46 Kellin: Okay, lets talk about it later 17:17:47 it contains all the changes, we want that merged/ready 17:18:30 Kellin: I didn't know the changes you made during last run, hence I backed out, but I will take a peek 17:18:59 I would feel better if puiterwijk also reviewed it, because he was my constant companion throughout the rebuilds with all the changes we made 17:19:12 most of the changes had to do with permissions/security/etc and making it run more generically with the right security infra in place 17:19:19 can you rebase? 17:19:29 yes, I can 17:19:41 Kellin: I can look in about 15 minutes. 17:19:58 thanks patricku 17:21:10 Mass rebuild always scares me, as there are lot of moving pieces 17:21:17 yep 17:22:08 nirik: rebased and green 17:22:29 you bought some carbon offsets for it? ;) 17:22:30 * nirik runs 17:22:46 yes, I installed an LED bulb last night replacing an incan bulb ;) 17:22:54 #info mboddu and puiterwijk will review the https://pagure.io/releng/pull-request/7345 and mboddu will look side tags and all change requests and will send out an email to devel list about the mass rebuild 17:24:17 I hope we get our added s390x capacity before mass rebuild, but oh well, we will live if not 17:25:11 nirik: I think we can live without it, but it would be a good addition 17:25:55 * nirik nods 17:26:35 Anything else guys? 17:26:42 mboddu: yeah, torrents 17:26:45 https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/995 17:27:26 * nirik reads 17:28:04 nirik: Basically the current torrent script we are using, its for py2 and the upstream library is dead, so we cannot move to py3 17:28:30 Kellin searched for some libraries, but its not fruitful 17:28:34 well, which script are we talking about here? the ini parsing stuff? 17:28:51 nirik: Nope, maketorrent script on torrent.fp.o 17:29:51 ah right... thats part of 'bittorrent' which no longer is open source in any way (we are using the last one that was) 17:30:01 well, we could look at dropping torrents. :) 17:30:11 but last time we tried the council rejected it. 17:30:28 I am open to that - but we need a back up plan because I"m pretty sure rejecting torrents is going to get rejected 17:30:35 one other option: we may be able to outsource it to amazon 17:30:58 oh? they do torrenting? 17:31:25 yeah... looking for the link. 17:31:34 but we are working on setting up cloudfront anyhow... 17:32:01 https://docs.aws.amazon.com/AmazonS3/latest/dev/S3Torrent.html 17:32:42 are any objects over 5GB? 17:32:54 games iso might be? 17:33:08 nope, 4.2 ;) 17:33:58 but that's kind of a ticking timebomb heh 17:34:41 anyhow, I can't think of any other options off hand. 17:34:46 can we theoretically maintain/update the version of BT we have to python3? 17:34:51 the license appears to be open source 17:35:01 yes, but thats a lot of work I am sure. 17:35:34 we have an intern who is interested, but is it worth the effort 17:35:44 Kellin: Probably not 17:35:47 I think we should explore dropping support, then amazon first 17:36:47 yeah, and then perhaps as a last resort writing our own 17:37:27 any other thoughts - nirik mboddu ? 17:37:44 if not, I will update the ticket with our four options 17:37:54 Nope, not from me 17:38:01 one last thing... 17:38:02 Drop Support, Amazon, Update BT Library, ROll our Own 17:38:07 * Kellin listens. 17:38:30 note that bittorrent is what we use to make .torrent files and also seed the content. We use opentracker for the tracker and thats in C. 17:38:50 so, to replace bittorrent we would need at least a seeder / .torrent file maker 17:39:30 OK 17:39:36 Kellin: that plan sounds good to me. we might want to try and gather stats on usage before asking to drop 17:39:58 nirik: who could get that info? 17:40:29 anyone: https://torrent.fedoraproject.org/stats/ 17:40:44 looks like we have back to 2012 17:41:20 nirik: Interesting, I didn't know that 17:41:51 it takes a hourly stat showing each hash and how many seeders / downloaders they have 17:42:04 so some scripting should be able to make a graph... 17:42:19 seed + download vs time 17:42:31 I think I graphed it once, there are some holes in the data 17:42:35 I am betting the trend is down 17:42:41 smooge had some insights, I will have to go dig it back out of my archives 17:42:46 might be. 17:42:48 * Kellin totally forgot 17:44:10 so the torrents is "interesting" 17:44:27 if I won't sidetrack things... 17:44:43 can you put your info into the taiga ticket as a comment? 17:44:51 that way you only have to explain it once, and it's there for posterity 17:45:00 it uses markdown for formatting if you want to pretty it up 17:45:25 what is the ticket? 17:45:49 I will see if I can find the stats script I did also 17:45:50 https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/995 17:49:15 me or smooge? 17:49:20 or both? 17:50:42 I think he is asking smooge but both will be better (more the merrier) :) 17:54:25 sure. I think Kellin's last comment summed up everything nicely. 17:54:35 so it looks good from my viewpoint 17:56:00 thanks nirik, smooge, Kellin 17:56:28 Okay, I want to give you guys 4 mins back 17:56:46 Anything quick that guys want to update? 17:57:02 Thanks guys for joining 17:57:05 #endmeeting