18:00:05 <smooge> #startmeeting Infrastructure (2017-07-06)
18:00:05 <zodbot> Meeting started Thu Jul  6 18:00:05 2017 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:05 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:05 <zodbot> The meeting name has been set to 'infrastructure_(2017-07-06)'
18:00:05 <smooge> #meetingname infrastructure
18:00:05 <zodbot> The meeting name has been set to 'infrastructure'
18:00:05 <smooge> #topic aloha
18:00:05 <smooge> #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson
18:00:05 <zodbot> Current chairs: abadger1999 dgilmore nirik pbrobinson pingou puiterwijk relrod smooge threebean
18:00:10 <clime> hey
18:00:19 <smooge> #topic New folks introductions
18:00:24 <smooge> Hello all
18:00:25 <dgilmore> hole
18:00:25 <puiterwijk> Hello
18:00:31 <smooge> #topic aloha
18:00:36 * cverna waves
18:00:40 <smooge> ok back to saying hi before going to new people
18:00:51 * threebean waves :)
18:01:01 <smooge> my email about the meeting today never left my screen so thank you all for showing up
18:01:03 <bgray> hello
18:01:06 <bowlofeggs> suuup
18:01:12 * nirik is sorta here, but mostly in the f26 final go/no-go meeting in #fedora-meeting-2
18:01:51 <nb> .hello nb
18:01:52 <zodbot> nb: nb 'Nick Bebout' <nb@nb.zone>
18:01:59 * nb same as nirik, is in the go/no-go meeting
18:03:46 <smooge> ook next up
18:04:03 <smooge> #topic New folks introductions
18:04:20 <smooge> hi are there any new people here this week who want to do an introduction?
18:04:33 <maxamillion> .hello maxamillion
18:04:35 <zodbot> maxamillion: maxamillion 'Adam Miller' <maxamillion@gmail.com>
18:05:59 <smooge> ok next up
18:06:57 <smooge> #topic announcements and information
18:06:57 <smooge> #info F26 final freeze
18:06:57 <smooge> #info Final freeze is always a hard freeze. Please make sure +2 is given before commits to frozen systems.
18:06:57 <smooge> #info PHX2 Colo Trip coming up, Aug 14-18
18:06:57 <smooge> #info Major outage planned for Aug14->18
18:06:59 <smooge> #info FLOCK at Cape Code  Aug29->Sep01
18:07:01 <smooge> #info
18:07:08 <smooge> OK we are in final freeze and also in a go/no-go meeting
18:07:33 <puiterwijk> #info Auth code for modern-paste written, hopefully soon we'll have auth for paste
18:07:38 <smooge> yay!
18:07:47 <smooge> ipsilon based?
18:08:01 <puiterwijk> Yep
18:08:25 <puiterwijk> Last night I decided to just get it done. Four hours later, the patch was passing the full test suite and submitted.
18:08:42 <puiterwijk> So I'm thinking to apply it in staging tonight, play with it, and then maybe put to prod sometime soon
18:09:47 <smooge> cool
18:10:09 <smooge> so I am guessing the next thing I need to look at is having a nagios ipsilon plugin done
18:10:23 <smooge> but that can wait til tomorrow
18:10:25 <smooge> :)
18:10:27 <puiterwijk> I'd suggest that we should just use mod_auth_oidc for that.
18:10:43 <smooge> what is mod_auth_oidc?
18:10:54 <puiterwijk> That's an Apache-based auth module for OpenID Connect
18:11:11 <puiterwijk> sorry, mod_auth_openidc (multiple appreviations for the same protocol)
18:11:20 <puiterwijk> We should be able to just configure Apache with it and be done
18:11:54 <smooge> ah cool
18:12:14 <smooge> yes. I would like to work on that for the two hosts I have with kerberos currently. will look at that after freeze
18:12:37 <puiterwijk> Sounds good. I can show you how to set this up (it's documented)
18:13:00 <puiterwijk> (though so far the only ones having used that are me and threebean)
18:13:18 <smooge> ok so one thing I want on everyone's radar is that when we get to the Aug14-18 move there are going to be shutdown of services for some amount of time
18:14:03 <puiterwijk> During that time, I will be the primary person to respond to outages not caused by the people on-site
18:14:05 <smooge> they may not be very long if we do everything right.. but they will be big and that is going to affect copr/cloud/build etc
18:14:25 <smooge> and to the outages we cause too
18:14:27 <puiterwijk> I think the plan is to send out notifications well in advance
18:14:32 <puiterwijk> Right.
18:14:47 <smooge> yes we will start messaging this after the freeze is done
18:14:51 <puiterwijk> In short: I'll be the one to respond to any issues :)
18:15:31 * nirik will be available also for issues
18:15:50 <puiterwijk> Ahh, I thought you were also going to PHX2
18:16:16 <smooge> no he will be packing/unpacking
18:16:26 <bgray> for us still learning the env, what are the outage/s for?  server moves?
18:16:28 <puiterwijk> Ah, right. That's around the same time
18:16:28 <nirik> nope, I will be holding down the fort with you... relrod and smooge will go. ;)
18:16:52 <nirik> bgray: we are moving our servers from one set of racks to a new set about 30feet away
18:16:58 <puiterwijk> bgray: yeah, we're moving our racks
18:17:04 <puiterwijk> Yeah, what Kevin said
18:17:05 <smooge> types even slower
18:17:19 <nirik> new space has more power, bigger racks. will allow us to recable and make things pretty
18:17:26 <smooge> #topic Outage in August
18:17:26 <smooge> #info We are moving our servers to new racks in August
18:17:26 <smooge> #info This will require all services to be down for some amount of time
18:17:26 <smooge> #info Working on alternate downloads/updates needs to happen
18:17:41 <smooge> so we are on this topic already and I forgot to change it
18:18:05 <smooge> well they will be having me touch wire so I don't know how pretty
18:18:12 <puiterwijk> Just an idea: would it be smart to setup a spare batcave02 in RDU before we do this?
18:18:23 <smooge> I think relrod's job is to make sure I don't touch the wires
18:18:23 <nirik> yes, thats on my list
18:18:31 <smooge> puiterwijk, yes it is on my list
18:18:34 <puiterwijk> Just in case something happens to the vhost with batcave01 during the move, so we can at least control stuff
18:18:35 <smooge> or its on niriks
18:18:42 <nirik> smooge: oh, I thought it was me... but eiither way. ;)
18:18:49 <puiterwijk> nirik, smooge: let's make sure one of us does it, and we don't end up with batcave05 :D
18:19:26 <nirik> I hope we can schedule days too... one day cloud, one day some prod stuff, one day build system, etc... so people know what to expect being down
18:19:40 <puiterwijk> nirik, smooge: whomever of you is going to set it up, it'd be appreciated if you could let me know, would like to check osme things at the same time
18:19:43 <smooge> it is on nirik's to build the batcave and probably backup db stuff. it is on mine to get the fing network working
18:19:58 <puiterwijk> Okay, sounds good
18:20:00 <smooge> I am to write up all the things and send it to the list next week
18:20:10 <smooge> or tomorrow whichever occurs first
18:20:32 <puiterwijk> I think tomorrow occurs before next week?
18:20:47 <smooge> its always a day away
18:20:48 * sayan is wondering what  smooge meant
18:20:49 <puiterwijk> (yes, I'm annoying)
18:21:12 <nirik> FYI, I am going to be out the 13th to the 17th... will have cell phone and might check in from time to time, but will be moving and not able to do much.
18:21:35 <nirik> and then not sure when net will be live and my new place or when I have to direct movers to unload.
18:21:40 <puiterwijk> nirik: 13th to 17th of July? Or August?
18:21:49 <smooge> sayan, it means that I am trying to get it done as soon as possible.. and maybe tomorrow maybe next week depending on how much I can write tomorrow
18:21:54 <nirik> july
18:21:59 <nirik> ie, next week
18:22:10 <puiterwijk> Right, that's what I thought. Just slightly confused with the talk of 14 - 18 August :)
18:22:22 <puiterwijk> nirik: good luck with moving!
18:22:34 <nirik> I hope I will be ready. ;)
18:23:20 <smooge> nirik, did you want to talk about the bot ideas this week or next week?
18:23:38 <nirik> whatever folks want, but I will not be at the meeting next week.
18:24:09 <x3mboy> .fas x3mboy
18:24:11 <zodbot> x3mboy: x3mboy 'Eduard Lucena' <eduardlucena@gmail.com>
18:24:34 <puiterwijk> Maybe just quickly now?
18:24:35 <smooge> #topic Zodbot and its clones
18:24:58 <smooge> so we are looking to make clones of zod which worked so well in Superman v Batman
18:25:30 <nirik> we have talked about this a number of times, but never done it... because there's not a super (ha!) great way to divide up things between multiple bots.
18:26:14 <nirik> we could make a new one and divide channels 75 / 75
18:26:37 <nirik> we could make one and make it the 'meeting' bot and try and have it in all meeting channels... but we don't know for sure what those are.
18:26:49 <puiterwijk> Well, I would honestly propose to just make a new one and just add it to new channels
18:26:57 <nirik> also, some people expect zodbot, and if they see nonbot they will be confused.
18:27:09 <smooge> maybe call it grodbot?
18:27:28 <smooge> it could answer them in a Flash( ha! ok not as funny)
18:27:55 <nirik> yeah, I suppose we could do a new one and only add it to new channels... at least there we could tell people what the bots name is, etc.
18:28:12 <nirik> however, if it does meetings it must have access to value01's meetbot dir.
18:29:12 <puiterwijk> Right, but we could just use Gluster/NFS for that. Since that's really just write-once with any new file, that shouldn't cause any problems
18:29:48 <smooge> I would go with nfs
18:30:29 <nirik> yep. as long as we made sure not to have them both in the same channel where a meeting happens.
18:30:48 <puiterwijk> Yeah
18:31:07 <smooge> I was thinking that if we had a list of channels and they made a hash of the name and one did even and the other odd..
18:31:14 <puiterwijk> I seem to remember seeing a Limnoria feature where it can abort one if there's two bots in the same channel. But if that's not in there, maybe it's useful to add that
18:31:15 <smooge> but I am also overthinking it
18:32:31 <smooge> I expect most people are autocompleteing so if we end up calling it zodbot2 it would make as much sense to people
18:33:22 <puiterwijk> Or zodbottoo?
18:33:25 <nirik> I guess I'm ok with that plan... make another and just add it to new things...
18:34:23 <smooge> and move stuff over if it makes sense. like all the ansible on one bot, all the XYZ project on one bot
18:35:36 <smooge> anyway.. anything else on this?
18:36:21 <nirik> nope
18:36:38 <smooge> #topic Apprentice Open office hours
18:36:48 <smooge> Hello Apprentices. Thank you for your help this week
18:37:08 <smooge> Our office hour like all academic office hours is open for the next 10 minutes
18:37:18 <bgray> can I get a review of https://pagure.io/fedora-infrastructure/issue/5989 ?
18:37:58 <bgray> i think it's complete. I did attach an infra/ansible patch to remove an unused file.
18:38:57 <smooge> ok this looks like it needs just final feedback from pingou and nirik
18:40:41 <clime> I can apply the patch if everyone is ok with it.
18:41:01 <smooge> clime, where does the patch get applied?
18:41:12 <clime> smooge: ansible
18:41:19 <smooge> well the patch in dist-git
18:41:21 <bgray> smooge: package update via ansible.
18:41:39 <smooge> which machines and such :)
18:41:55 <clime> smooge: oh pkgs02 roles/distgit it should be
18:41:59 <smooge> because if they are frozen, it needs to wait until we are unfrozen
18:42:00 <clime> pkgs playbook
18:42:15 <clime> ye, right
18:42:42 <smooge> Ok I would say that unless it is a mission stopping, we wait until we are unfrozen which will either be next Wednesday or the one after that
18:42:54 <smooge> (eg the 12th or the 19th)
18:43:17 <smooge> bgray, thansk for the work and your patience on it
18:43:32 <bgray> smooge: no problem! thanks for the review!
18:43:33 <smooge> freezes make for long cool downs at times
18:43:58 <smooge> let me put that in the ticket so it is clear
18:44:45 <smooge> ok next up this week is
18:44:50 <smooge> #topic Open Floor
18:45:03 <smooge> are there items for the open floor?
18:46:07 <smooge> ok if not I will close the meeting in 1 minute-ish
18:47:02 <smooge> #endmeeting