18:01:41 <smooge> #startmeeting Infrastructure (2017-07-13)
18:01:41 <zodbot> Meeting started Thu Jul 13 18:01:41 2017 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:41 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:01:41 <zodbot> The meeting name has been set to 'infrastructure_(2017-07-13)'
18:01:42 <smooge> #meetingname infrastructure
18:01:42 <zodbot> The meeting name has been set to 'infrastructure'
18:01:42 <smooge> #topic aloha
18:01:42 <smooge> #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson
18:01:42 <zodbot> Current chairs: abadger1999 dgilmore nirik pbrobinson pingou puiterwijk relrod smooge threebean
18:01:59 <puiterwijk> Hi
18:02:03 <relrod> .hello codeblock
18:02:06 <relrod> or not
18:02:12 <zodbot> relrod: codeblock 'Ricky Elrod' <codeblock@elrod.me>
18:02:13 * relrod is here :)
18:02:18 <bgray> hello
18:02:42 <smooge> poor zodbot.. not as super as he says he is
18:03:48 * threebean waves
18:04:05 <smooge> #topic New folks introductions
18:04:28 <smooge> Hi are there any new people here?
18:05:38 <smooge> ok I am thinking today will be a very quiet and quick meeting
18:05:51 <smooge> #topic announcements and information
18:05:51 <smooge> #info F26 is released. Mirrors did well
18:05:51 <smooge> #info Final freeze is over
18:05:51 <smooge> #info PHX2 Colo Trip coming up, Aug 14-18
18:05:52 <smooge> #info Major outage planned for Aug14->18
18:05:53 <smooge> #info FLOCK at Cape Code  Aug29->Sep01
18:05:54 <smooge> #info Kevin is moving across country and away from keyboard
18:05:56 <smooge> #info fedmsg-0.19.0 released, watch for issues on F26+ (no m2crypto)
18:06:19 <puiterwijk> \o/ py3 support for fedmsg!
18:06:41 <smooge> \O/ no more freeze
18:07:43 <pingou> \
18:07:45 <pingou> o/ flock
18:08:00 <puiterwijk> \o/ 4 days of outage!
18:08:06 <puiterwijk> Oh wait, that's a /o\
18:08:23 <smooge> especially since I don't know if the people in charge of the f27 schedule know it
18:08:42 <puiterwijk> That might be a good thing to inform them about
18:09:21 <pingou> outage for my birthday, how kind!
18:09:41 <puiterwijk> :-)
18:09:44 <puiterwijk> pingou: all for you!
18:09:52 <pingou> is it a single outage or multiple small one?
18:10:03 <puiterwijk> It's a very complicated set of outages
18:10:11 <pingou> k
18:10:15 <puiterwijk> We're moving all our racks a few meters away
18:10:29 <pingou> but not a single large one: as if: we're moving the entire datacenter in trucks
18:10:40 <pingou> or on the back of smooge 's truck
18:10:57 <puiterwijk> No, it's in the same physical vicinity. But it is a complicated operation, with lots of moving parts
18:11:01 <smooge> (┛◉Д◉)┛彡┻━┻ is my guess to what will happen when they find out
18:11:01 <puiterwijk> (physically and virtually)
18:11:10 <puiterwijk> smooge: yep. Sounds about right
18:11:21 <pingou> ^^
18:11:34 <pingou> is 4 days the dates they gave us?
18:11:35 <smooge> I guess no one wants to tell mattdm
18:11:40 <jwboyer> i have a question when there is an open floor opportunity or appropriate subject
18:11:55 <pingou> or did we plan a little extra time ?
18:12:00 <puiterwijk> jwboyer: today's meeting is going to be quite short, so we should have enough time
18:12:07 <jwboyer> ok
18:12:12 <puiterwijk> pingou: that's pretty much what we're told as being the planning to get stuff moved I think
18:12:23 <smooge> pingou, currently it will be those 4 days but it may be longer or shorter in parts depending on how much it takes
18:12:37 <sayan> .fas sayanchowdhury
18:12:37 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
18:12:44 <pingou> puiterwijk: smooge: would it make sense to plan an extra day, best case we finish early?
18:12:47 * puiterwijk notes I'm going to get to fix koji, so might respond slower
18:13:08 <smooge> pingou, the days there are dependant on our budget for the move which is maxed out
18:13:09 * mattdm looks at schedule.
18:13:13 * mattdm looks at the above.
18:13:30 <mattdm> so... major outage right during planned branch?
18:13:53 <jwboyer> this is what happens when you slip a release and try to account for it by cutting it out of the next release
18:13:53 <puiterwijk> Yep, pretty much
18:14:23 <mattdm> jwboyer: which is? because that branch date hasn't changed since fesco set it
18:14:24 <pingou> mattdm: when will we stop branching? f28?
18:14:53 <mattdm> pingou: and have everything in modules?
18:15:04 <jwboyer> mattdm, correct, but there is literally no better timing because everything in f27 is so compacted
18:15:23 <pingou> mattdm: but w/ arbitrary branches we don't need everything in modules no?
18:15:33 <smooge> mattdm, we have talked with releng and they were looking to move the branch back a week
18:15:44 <smooge> dgilmore is in meetings so I don't know the status of that
18:16:20 <smooge> jwboyer, conversations about compact schedules can go to #fedora-devel please :)
18:17:05 <jwboyer> smooge, overall, sure.  but mattdm is eyeing your outage schedule and it's impacts on the f27 schedule.  i thought that was relevant here.  anyway, i'll shut up
18:17:12 <pingou> smooge: I've more questions about this outage but I guess I can ask them outside of this meeting, they are more for my personal curiosity
18:17:24 <smooge> in this case, there were 2 weeks we could do the outage and the other was flock
18:17:42 <mattdm> it definitely increases my worry level by another notch.
18:19:46 <smooge> ok anything else on the announcements?
18:20:05 <pingou> koji upgrade planned next week
18:20:12 <pingou> pagure on dist-git the week after
18:20:32 <smooge> #info koji upgrade planned next week 2017-07-17
18:20:38 <smooge> #info pagure after that
18:21:04 * pingou trying to fix tests before doing a new pagure release and pushing 3.x to prod
18:21:06 <puiterwijk> #info Koji stg upgraded to 1.13 last night
18:21:11 * pingou looking forward for 3.x in prod
18:21:39 <smooge> #topic Apprentice Open office hours
18:21:55 <smooge> Any apprentice here or questions?
18:22:24 <smooge> if not we can move to open floor and talk with jwboyer
18:23:17 <smooge> #topic Open Floor
18:23:50 <jwboyer> topic: ppc64le OpenQA machine
18:24:16 <jwboyer> a while ago, IBM sent a loaner machine for the purposes of getting ppc6le added to OpenQA
18:24:33 <jwboyer> apparently they asked why it isn't installed and available today
18:24:48 <jwboyer> the machine was sent months ago, so that confuses/concerns me as well
18:24:54 <jwboyer> does anyone have info on this?
18:25:21 <smooge> One of the issues I have run into the past is that IBM will send stuff but never tell us
18:25:30 <puiterwijk> smooge: that wasn't the case here
18:25:36 <smooge> I expected so
18:26:04 <puiterwijk> There was a case of miscommunication, where I thought KEvin was on it, and he thought I was on it. So then last week I tried to work on it after finding that out, and found it didn't reply on serial.
18:27:00 <smooge> ah..
18:27:18 <puiterwijk> So, at this moment I'm waiting on dcops to confirm that they did indeed send the correct information, and if that's the case, if it's turned off.
18:27:20 <smooge> is it needing one of those special IBM serial connectors?
18:27:49 <puiterwijk> smooge: no. It was connected to an opengear, just like the others we have. The others work just fine, this one doesn't
18:28:27 <puiterwijk> jwboyer: so, I'm sorry for dropping the ball on that. I'll try to get more info on this within the coming week
18:28:41 <jwboyer> ok
18:28:45 <jwboyer> i would appreciate that
18:29:10 <jwboyer> is there a better way we can track the addition of hardware?
18:29:25 <jwboyer> i'm not sure if tickets were submitted or if it is tracked some other way
18:29:31 <puiterwijk> I guess ideally we could open an Infra ticket
18:29:45 <puiterwijk> There is no ticket created by anyone yet, and it's not being tracked anywhere that I know of.
18:30:40 <puiterwijk> jwboyer: now it is: https://pagure.io/fedora-infrastructure/issue/6155
18:31:17 <smooge> jwboyer, so yeah. in the future it would be good for hardware like this to be given a ticket
18:31:37 <jwboyer> would you like IBM to open the ticket once they have shipped it?
18:32:08 <puiterwijk> Maybe it's easier if the community person receiving the machine opens a ticket once they're aware, so we can start planning the rackspace etc
18:32:37 <smooge> I would go with before hand because we need to be able to say "We can't take it" in the case that happens
18:33:05 <marc84> +1 for smooge
18:33:14 <smooge> if we were not doing this move next month that would have been something we would need to do on more hardware
18:33:19 <jwboyer> puiterwijk, who's the community person in this case?  adamw?  or?
18:33:38 <puiterwijk> jwboyer: I think adamw was the first to know we were going to be sent this?
18:33:39 <smooge> Well who 'owns' ppc relationship?
18:33:48 <jwboyer> puiterwijk, yeah, but sometimes a single machine fulfills multiple people's needs
18:33:53 <puiterwijk> Basically, whomever knows we'll be getting it
18:33:56 <puiterwijk> Right
18:34:04 <jwboyer> smooge, it depends.
18:34:16 <puiterwijk> So, in that case, just anyone opens the ticket. The creator doesn't really matter I'd say
18:34:24 <smooge> jwboyer, Well I expect that is also the answer too :)
18:34:24 <jwboyer> ok
18:35:04 <adamw> if this is about the ppc machine for openqa...
18:35:11 <puiterwijk> adamw: it is.
18:35:13 <adamw> i'm not gonna be 'receiving' it, since i have no sort of access to phx2
18:35:24 <jwboyer> receiving in the usage sense
18:35:26 <adamw> ah
18:35:33 <adamw> then yeah, ultimately that'd be mne
18:36:35 <jwboyer> smooge, puiterwijk: ok.  we'll keep this in mind going forward.  since sharkcz talks with IBM weekly, we can likely get wind of any future needs/additions and get a ticket opened one way or another
18:36:46 <jwboyer> but there is always the chance for surprise hardware :)
18:37:05 <puiterwijk> Right, thanks!
18:37:19 <smooge> ok thanks. I would appreciate that we know about surprise hardware as we have had IBM upset we didn't use the hardware they forgot was a surprise
18:37:51 <smooge> alright anything else for open floor?
18:38:15 <smooge> if not I would like to thank everyone for coming this week and I will make sure to have the invitation for next week early
18:38:23 <pingou> ++
18:38:27 * pingou won't be there next week :)
18:39:10 <smooge> #endmeeting