18:00:03 #startmeeting Infrastructure (2016-01-28) 18:00:03 Meeting started Thu Jan 28 18:00:03 2016 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:03 The meeting name has been set to 'infrastructure_(2016-01-28)' 18:00:03 #meetingname infrastructure 18:00:03 The meeting name has been set to 'infrastructure' 18:00:03 #topic aloha 18:00:03 #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson 18:00:03 Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pbrobinson pingou puiterwijk relrod smooge threebean 18:00:04 #topic New folks introductions / Apprentice feedback 18:00:51 Any new folks like to give a short one line introduction of themselves? 18:00:58 Or apprentices with questions or comments? 18:02:31 might not be too many folks around today... lots of people traveling to FOSDEM and/or devconf. 18:03:05 * masta looks in 18:03:07 * threebean is here :) 18:03:50 ok, lets go ahead and go on to info/status dump 18:04:09 #topic announcements and information 18:04:09 #info pagure 1.0 deployed and it looks beautiful! (pingou and ryanlerch) 18:04:09 #link https://fedoramagazine.org/pagure-diy-git-project-hosting/ 18:04:10 #info PDC and pdc updater deployed to prod - ralph 18:04:10 #link https://pdc.fedoraproject.org/ 18:04:10 #info koji builder updates in progress this week before mass rebuild next - kevin 18:04:11 #info Some work on adding network config to ansible - doteast/kevin 18:04:22 anything in there folks would like to discuss more, or things to add? 18:04:54 .hello smdeep 18:04:55 smdeep: smdeep 'Sudeep Mukherjee' 18:05:18 The new pagure theme looks completely awesome, IMHO. 18:05:49 absolutely 18:05:57 yep, nice 18:06:27 * nirik wonders if we could ask lwn to do a review of it. Might get some more interest/usage. 18:06:34 * jflory7 has something to mention when other topics are finished 18:07:15 jflory7: FYI, you were mentioned on our first discussion item too... so I guess lets go to that. 18:07:29 #topic Spinning up a second zodbot instance for incoming channels. Odin2016 18:07:29 #info Justin Flory asked about this in the admin channel Saturday figured this would not be a bad thing to discuss with the group. Offered to add it to the next meeting agenda. 18:07:55 it turns out that I looked and we are actually not even close to the limit currently. ;) 18:08:06 so, IMHO we should just not worry about this yet/now. 18:08:18 Oh, this works too -- also have something else later too :) 18:08:21 * jflory7 nods 18:08:25 That's good to know about zodbot 18:08:49 I think we are at 113 channels currently and the limit is 150. 18:09:10 #info at 113 channels, limit is 150, so we can kick this can down the road. 18:09:49 Thats actually all the discussion we had listed... you had another item jflory7 ? 18:09:56 Maybe start thinking of new bot names if the time ever arises. ;) 18:10:01 And yes, shouldn't be too long-- 18:10:27 sure, take it away... 18:11:07 Fedora CommOps is helping sub-projects across Fedora put together "Year in Review" posts for 2015, summing up at least three highlights of 2015 and one (or more) goals for 2016. It would awesome if Infrastructure team put together one to share on the Community Blog. :) 18:11:11 https://communityblog.fedoraproject.org/share-your-year-in-review-with-fedora/ 18:11:27 #topic Year in review 18:11:29 You can find examples of other Year in Review posts here: https://communityblog.fedoraproject.org/tag/year-in-review-2015/ 18:11:34 * threebean clicks 18:11:44 Cool. Yeah, I saw that, but haven't had time to look at doing one for infra... 18:11:55 so I actually was going to do some of the number crunching for the YIR, in terms of tickets opened/closed/outages 18:12:03 I could try or if someone else is interested perhaps they could put it together and I could help out with info. 18:12:06 and I havent gone beyond athat 18:12:15 aikidouke: that would be cool to have. 18:12:20 That first link has a few templates that should make the writing part easy too -- it's just deciding the highlights and goals that will take discussion. :) 18:12:32 one of the things the YIR template wants is accomplishments for the year 18:12:41 aikidouke++ That would be awesome info to have! 18:12:50 hm. nirik I need to put together notes for a YIR-type talk at devconf. maybe I could work on it and pass it to you for review? 18:12:51 we could also gather all the status updates... so know unplanned vs planned outages... 18:12:57 what accomplishments would we want to mention? 18:13:15 threebean: that would be lovely. :) and aikidouke perhaps could help you with stats? 18:13:16 nirik: is that in the ticket system or ? 18:13:18 aikidouke: maybe new services deployed? 18:13:24 * jflory7 wonders if Pagure development could be wrapped under Infra too? 18:13:31 new services... finishing ansible migration... 18:13:31 +1 18:13:33 Seems like a big highlight of the past year. :) 18:13:59 yeah, the ansible migration should be winding down a lot in 2015 18:14:00 rhel7 migration... 18:14:34 ok - I will at least put some numbers in the YIR format and send it to the list (and maybe take a stab at accomplishments) then if threebean and nirik want to edit/add/etc 18:14:36 hyperkitty/mailman3... mirrormanager2 18:14:38 bodhi2 18:14:43 bodhi2. yeah 18:14:47 minor upgrade ;) 18:14:58 just a tad. :) 18:15:19 aikidouke: that would be awesome. thank you :) I'll start working on a project list and send it too. 18:15:25 seem there is plenty to recap 18:15:31 yup 18:15:36 cool. Yeah, we did get a ton done last year. 18:15:42 everyone ++ :) 18:15:46 :) 18:15:49 * doteast wonders of https://fedoraproject.org/wiki/Fedora_Engineering/FY16_Plan would be highlight list 18:15:49 And it doesn't have to be three highlights + one goal, it's totally flexible to as much as you all want to include. :) 18:16:05 doteast: good starting point, yeah :) 18:16:08 doteast: yeah, lots of things are on there, but possibly not all. 18:16:22 we could always categorize 18:17:05 * nirik has also been pondering goals for this year... nothing super concrete yet, but lots of possibilities 18:17:57 Cool. :) Anything else on this? 18:18:04 thanks for bringing it up jflory7 18:18:11 nirik: Gladly! 18:19:05 #topic Learn about 18:19:13 So, I don't have anything lined up today for learn about... 18:19:34 perhaps we could line up some things people want to hear about? Or I'm happy to pontificate about something today if it's something I know well. 18:19:47 anyone have things they would like to know more about? Or would like to teach others on? 18:20:17 lmacken: perhaps we could line you up in some coming week for a bodhi2 overview? 18:20:28 like what machines run what and how they fit together? 18:20:31 nirik: sure sure 18:20:38 next week? or further out? 18:20:49 next week works for me 18:21:08 excellent. 18:22:35 anyone else? things you would like to hear about ? :) 18:23:25 ok, I can try and solict more on the list/in irc. ;) 18:23:29 #topic Open Floor 18:23:56 anyone have anything for open floor? ideas/comments/favorate midevil pole arms? 18:24:27 I'm a bad infra person, but I'd like to announce I'm intending to start looking at and maybe messing with Ansible playbooks, at least for systems I care about/use. 18:24:36 I assume there is a document on that somewhere? 18:24:54 masta: yep. There's a doc and also a README in the ansible repo 18:25:04 coolies, I'll check it out 18:25:09 nirik: i noticed on batcave that there is only an ipv6 link address - when/how should we start thinking about ipv6 for infra ? 18:25:15 https://infrastructure.fedoraproject.org/infra/docs/ansible.rst 18:25:30 and if that is a bigger question than we have time for, I'll understand 18:25:34 aikidouke: our main datacenter (phx2) has no ipv6 support. 18:25:51 so, not until it does there. ;) We do have ipv6 in some other datacenters... 18:26:00 oh...ok, good to know 18:26:13 wish we could tunnel the ipv6 into there. I'm sure HE would be helpful getting that going. 18:26:28 do they have any plans to add it this year? 18:26:31 I think it's on a roadmap, but no idea where it is. 18:27:04 most of our services are reachable via ipv6 due to proxies, etc being in other datacenters. 18:27:05 our benefactor is sadly slow going with v6 18:27:22 so, not sure it's really that urgent. 18:27:29 might be nice to have it for cloud instances... 18:27:34 and koji/pkgs 18:27:57 yeah, v6 could probably be used internally in phx2 18:28:06 I don't see that as gaining us much. 18:28:08 does mirrormanager check for v6 connectivity? 18:28:21 aikidouke: sure. mm is fully ipv6 aware. 18:28:25 cool 18:28:40 ty 18:28:55 nirik, it's not much, but at least v6 link-local is a start 18:29:19 i guess that was an ad hoc learn about ipv6 18:29:30 ha. 18:30:12 ipv6 just reached it's 20th year... and 10% enablement. 18:30:20 it's going to be some slow going I fear. 18:30:38 well, going on that curve...we'll all still be subnetting in 2050 18:30:42 :) 18:30:52 it was something like 2% or 3% last year 18:31:22 anyhow, it will get there someday. ;) 18:32:00 Anyone have anything else, or shall we call it a nice 30min meeting (recommended meeting length by the Red Hat CEO)? 18:32:26 you shall call it nice, yes 18:32:31 ok, have fun everyone. See you all around. ;) 18:32:34 #endmeeting