18:00:11 #startmeeting Infrastructure (2014-05-22) 18:00:11 Meeting started Thu May 22 18:00:11 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:11 #meetingname infrastructure 18:00:11 #topic aloha 18:00:11 #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 18:00:11 The meeting name has been set to 'infrastructure' 18:00:11 Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 18:00:45 hola 18:01:01 hi 18:01:08 Buenas tardes 18:01:10 Hello ! 18:01:16 Hi :) 18:01:19 * bwood09 is here 18:01:23 Good afternoon. 18:01:29 Hello everybody! :) 18:01:29 hllo 18:01:31 hello everyone. 18:01:32 hi all 18:01:37 #topic New folks introductions and Apprentice tasks. 18:01:49 any new folks like to introduce themselves in a line or two? 18:02:00 or apprentices with questions or comments? 18:02:11 (waiting for new folks first) 18:02:17 Hello everyone, I am Mayank from India, would be hacking on bugspad this summer! 18:02:24 Hi everyone. I am Charul and have started working on Shumgrepper project. 18:02:27 * relrod here 18:02:40 * danofsatx-work is here 18:02:45 Hello, This is Hammad, Working on fedora-college, that inherently comes under infra. 18:03:00 Hizo everyone i am Gonzalo from Bolivia 18:03:20 great! welcome everyone. 18:03:51 Those of you doing summer coding, would you have links to your projects for us to read up on? 18:04:04 Hello guys, My name is Bruno! I am from Brazil, but living in Los Angeles,Ca! 18:04:44 https://github.com/kushaldas/bugspad the project I would be working on! 18:04:51 making a UI for it. 18:04:55 https://github.com/hammadhaleem/fedora-college Fedora College. 18:05:24 https://github.com/fedora-infra/shumgrepper for Shumgrepper 18:05:47 great. :) 18:06:10 hello everyone 18:06:34 good luck in your coding. ;) 18:06:51 ready for the apprentices ? 18:06:56 I and my mentor kushal, were discussing about some revisions in the timeline of the project, to include the suggestions received from the infra team, for 18:06:57 thanks nirik :) 18:07:14 ootbro: sure, fire away... 18:07:20 following up from the map/landscape/overview "new project" item last week (and the e-mail I sent to the mailing list)..... I haven't gotten any additional source material, so I'll start with what I listed in the e-mail. 18:07:26 and will be discussing tomorrow! 18:07:34 mapyth: ok. Might be good to post to the list on it and that way we can get replies from anyone intrested... 18:07:58 ootbro: sounds good. 18:08:59 nirik has already said that the first two steps sounded good -- an overall list of servers with a location, function, production status (prod, staging, testing, etc.) 18:09:10 which starts to put the pieces on the table. 18:09:15 * nirik nods. 18:09:32 and add a basic description for each general function that tells what that family of servers does. 18:09:32 nirik: okay sure! shall I put it on summer-coding mailing list? 18:09:57 mapyth: I'd say the infrastructure list if you want infrastructure input into things... 18:10:50 In getting my ssh access fixed (thanks, again, nirik :) )... I found an update that needs to be done to the sshaccess.txt file 18:10:55 For any other new folks, do see: http://fedoraproject.org/wiki/Infrastructure/GettingStarted if you haven't already, and we can point you in the right direction in #fedora-admin and/or #fedora-apps agter the meeting. 18:11:37 ootbro: those docs are in the 'infra-docs' git repo... which actually apprentices do have write access to. ;) Just go to lockbox01 and 'git clone /git/infra-docs' and modify it and commit and push. 18:12:04 nirik: okay. will finalize with my mentor tomorrow and post. 18:12:06 ok. thanks. that was my next question -- how to get an update posted. :D 18:12:26 ootbro: easy peasy. ;) (Hopefully) 18:12:50 I'll dig into the documentation for the "how" part of commit and push 18:13:09 yep. should be lots of git docs out there... possibly too many. :) 18:13:16 :) 18:13:22 (done) 18:13:31 ok, any other new folks or apprentices with questions ? 18:13:36 welcome again to all new folks. 18:14:02 #topic Applications status / discussion 18:14:18 * nirik sees most if not all our applications folks aren't around. ;( 18:14:29 There continues to be some fallout from the pkgdb2 rollout. 18:14:46 #info process-epel-requests script being worked on to work with pkgdb2 18:14:51 hi @ I am new, I am actually writing my introduction right now! :-) 18:15:04 #info bugzilla component sync is also not working right, still need to investigate. 18:15:09 brnzi: cool. ;) 18:15:14 I am looking for a sponsor.. :-) 18:15:42 look for something interesting to you to work on first. ;) 18:15:52 :-) 18:16:21 any other applications news today? 18:16:51 #topic Sysadmin status / discussion 18:16:59 on the sysadmin side... 18:17:11 we did a mass reboot tuesday, everything seems to have gone just fine. 18:17:43 Our build system is 100% working for the first time in a while... all our arm SOC's, buildvm's, buildhw are all up and running along nicely. 18:17:55 yay! 18:17:58 the ansible migration is rolling along 18:18:18 I'm hoping to move the last things off our old app servers soon and retire them all. 18:18:35 that will be nice. 18:18:49 yay 18:19:02 Sound good 18:19:58 our backup server almost ran out of inodes last night... will be trying to clean up what we can there. 18:20:14 * threebean arrives late 18:20:15 what was that a recursive backup? 18:20:24 someone not playing nice? 18:20:37 smooge: there was one gnome backup taking up a lot, it's now been fixed... 18:20:53 but there's still a lot of inodes taken up. If my find ever finishes I can see what dirs have a lot. 18:21:36 #info mass reboot last tuesday, went fine. 18:21:50 for (i=0; i #info buildsys is 100% up and operational. All arm, buildvm, buildhw boxes working 18:22:09 #info smooge and relrod got all the new download servers in place and working 18:22:35 now I am dealing with hardware problems on the RDU download servers 18:22:38 that was mostly smooge 18:22:47 relrod, you did the ansible stuff 18:23:18 ok, any other sysadmin side items to mention? 18:23:21 nirik: question re: app servers ; are the last things simply shifting as a group to new hosts or are they shifting to separate hosts? 18:23:47 abadger1999: most of the last things are moving to the sundries servers... the big apps already moved to their own things 18:23:53 18:23:57 smooge: doing ansible stuff is easier than looking at a screen and trying to hit f12 in a vnc window within 5 seconds ;) 18:23:58 the last thing is freemedia. which is just a php/cgi 18:24:24 I was thinking once I get that moved to power them off for a few days... see if anything breaks or still depends on them. 18:24:36 nirik: Cool. One thought about that -- we may want to upgrade to rhel7 before mirrormanager is ported away from tg1. 18:24:48 current items on my task list: fix download RDU server hardware issues, rebuild RDU servers to be ansible, build new log server, get stuff off old log server, and move virthost box over to cloud 18:25:05 nirik: So we may want to split that away from the other sundries stuff i nthe future. 18:25:36 (we can cross that bridge when we start thinking about rhel7 migration, though :-) 18:26:08 abadger1999: ok. yeah. MM has 3 parts: mirrorlists (already moved to their own instances), mirrormanager adminwebapp (moved to sundries) and backend/cron stuff thats still on bapp02... still need to move that. 18:26:19 Hello. Sorry to be late! 18:26:33 henderbj: no worries. welcome. 18:26:38 (for those who haven't followed -- I'm not planning on maintaining TurboGears1 on EPEL7. So mirrormanager nad FAS will be stuck on RHEL6 until we port them to a newer framework). 18:27:08 * oddshocks here late 18:27:13 * oddshocks roommate troubles 18:27:20 abadger1999: we will have lots of other things to migrate, so we can save those for last. 18:27:23 welcome oddshocks 18:27:29 18:27:36 * mapyth is pissed by my troublesome internet connection 18:28:22 (went business-class for my home connection and it's usually very stable) 18:28:46 ok, lets see how nagios treated us this last week... 18:28:53 #topic nagios/alerts recap 18:28:54 * threebean cringes 18:29:01 https://admin.fedoraproject.org/nagios/cgi-bin//summary.cgi?report=1&displaytype=3&timeperiod=last7days&smon=5&sday=1&syear=2014&shour=0&smin=0&ssec=0&emon=5&eday=15&eyear=2014&ehour=24&emin=0&esec=0&hostgroup=all&servicegroup=all&host=all&alerttypes=3&statetypes=2&hoststates=3&servicestates=56&limit=25 18:29:09 .tiny https://admin.fedoraproject.org/nagios/cgi-bin//summary.cgi?report=1&displaytype=3&timeperiod=last7days&smon=5&sday=1&syear=2014&shour=0&smin=0&ssec=0&emon=5&eday=15&eyear=2014&ehour=24&emin=0&esec=0&hostgroup=all&servicegroup=all&host=all&alerttypes=3&statetypes=2&hoststates=3&servicestates=56&limit=25 18:29:10 nirik: http://tinyurl.com/q8j48o9 18:29:33 yeah, the new fedmsg monitoring was a bit shouty. ;) 18:30:04 but I think we have that mostly tuned better now? 18:30:10 mirrorlist-serverbeach is always swaping? 18:30:20 yeah.. there were actual problems it was reporting in the beginning.. those seem mostly worked out, but the periodic UNKNOWNs from badges-backend01 is still a mystery. 18:30:23 ha. Just got another feedmsg alert. ;) 18:30:57 henderbj: yeah, it's proving troublesome. I am not sure why it's having trouble where the other instances aren't. ;( I guess I could just destroy it and make one somewhere else. 18:31:23 I've tried various things to make it happier. (Fewer threads, etc) 18:32:10 nirik: Maybe some processes are running there that are not present on those others 18:32:14 and the telia stuff is typical. Our phx2 main datacenter to telia often has network issues. 18:32:33 nirik: maybe some backups? 18:32:40 henderbj: very unlikely. They are configured from the same ansible playbook, so they should be pretty much identical. 18:32:49 nirik: ok 18:33:24 The main difference is that is in another datacenter on different hardware. 18:33:33 Ah... i finished (at least i think) work for ticket #4325: https://fedorahosted.org/fedora-infrastructure/ticket/4325 18:33:37 and the serverbeach hardware can at times get odd 18:33:39 so it could be that that hw/network just sucks. ;( 18:33:57 henderbj: cool. ;) I saw, but haven't had time to look yet. 18:34:35 nirik: Please check it and if it works, then we are done and can close the ticket 18:35:10 so, on nagios: tune fedmsg alerts more and figure out badges-backend timeout, move or do something with mirrorlist-serverbeach, and sigh at telia. ;) 18:35:16 it's on my list, yep. 18:35:38 #topic Upcoming Tasks/Items 18:35:38 https://apps.fedoraproject.org/calendar/list/infrastructure/ 18:35:47 anyone have upcoming items they want to note or schedule? 18:36:27 Oh, I'll be out on vacation tomorrow. 18:36:27 we have our FAD coming up in just a few weeks... 18:36:36 https://fedoraproject.org/wiki/FAD_Bodhi2_Taskotron_2014 18:36:38 also Monday is a US holiday, so things might be quiet around then too. 18:37:04 oh yeah, true... 18:37:36 i'm not actually travelling, so I might poke my head into channel here and there.. :) 18:38:00 * nirik should be around, but might be playing video games or watching movies or whatever. ;) 18:38:04 #topic Open Floor 18:38:24 anyone have any items for open floor? questions? comments? 18:38:34 nirik has time to play video games??? 18:38:40 (crickets chirping) 18:38:42 sometimes. ;) 18:38:59 on weekends. If I get to the gaming system before my GF does. ;) 18:38:59 ansible, and nagios wonderfull ;) 18:39:17 maybe you need two gaming systems? 18:39:41 that would need 2 tv's... 18:39:55 space would be a problem with that 18:40:01 ho... or use multiseat consoles ;) 18:40:10 yeah. Where's our virtual reality headsets! 18:40:22 i have a multiseat fedora machine... that's great thing to have ;) 18:40:42 anyhow, lets continue over in #fedora-admin, #fedora-apps and #fedora-noc... Thanks for coming everyone! 18:40:44 #endmeeting