20:00:35 #startmeeting infrastructure 20:00:35 Meeting started Thu Nov 4 20:00:35 2010 UTC. The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:49 #chair mmcgrath 20:00:49 Current chairs: mmcgrath smooge 20:00:55 yay! meeting 20:00:56 * nirik is hanging around. 20:00:59 #meetingname infrastructure 20:00:59 The meeting name has been set to 'infrastructure' 20:01:10 #topic Robot Roll Call 20:01:19 crowbot here 20:01:44 * CodeBlock[s] here 20:01:48 * waltJ is still awake 20:01:51 * ninjazjb here 20:01:52 * goozbach here 20:02:09 heading to class though; be back in about 5 20:02:19 ah the wonders of technology. 20:02:26 XD 20:02:33 the ability to do something constructive in class 20:02:38 i know! :D 20:02:44 #topic Release 14 cycle 20:02:52 ok the release happened on tuesday 20:02:59 smooge: It's a personal health class; I think I can handle discussing something I care about while I learn to not smoke. 20:03:18 :-) 20:03:20 * mdomsch needs a sugar+caffiene kick, bbiab 20:03:25 https://fedorahosted.org/fedora-infrastructure/report/9 20:04:01 * skvidal is here 20:04:04 sorry for the delay 20:04:20 the only tickets open at the moment are lessons learned, two web tickets, and I missed closing 11->archives 20:04:42 how did the release go for people? 20:04:48 quiet for me 20:05:00 went fine... smooth release 20:05:12 from an outsider's perspective it went really well 20:05:22 preupgrade worked like a charm 20:05:35 Mine as well 20:05:54 ok lessons learned: 1) mmcgrath wrote a nice checklist that if followed works. 20:06:51 anything else? 20:07:14 ok next topic 20:07:32 #topic adding a new report to the trac 20:07:47 I am going to add a meeting keyword and report 20:08:36 I am not as good as Glorious Leader at keeping things separated to keep meetings going. 20:09:14 Next week I would like to get some tickets reviewed and added to the meeting so we can go through and fix and/or close our old ones 20:09:35 #topic download server changes 20:09:56 Ok this will affect sugar fix mdomsch the most 20:10:21 but we have new hardware in PHX2 and soon in RDU that will be moving upstream downloads to. 20:10:51 ? 20:10:52 I am hoping to get them configured next week and hten we can move over in December for PHX2 and January for RDU 20:10:54 hi 20:11:14 basically RHIT's download servers will be phased out and replaced with Fedora download servers 20:11:24 * mdomsch hears angels singing 20:11:37 too much sugar in the coffee 20:12:01 oh to be in control of all our own download servers... 20:12:19 we will still be using RHIT's netapps in RDU and PHX2 but the front ends will be ours. 20:13:06 so I will be helping mdomsch in what he wants and using lessons learned from warthog9 to get things set up 20:13:48 ok questions? 20:13:59 nice. 20:14:01 * nirik cheers 20:14:06 #idea we will need a new rsync module for the combination of epel, enchilada, and archive content 20:14:09 that's a good time to do it 20:14:27 fedora-bellgrande ? 20:14:35 now that they're all on the same underlying netapp file system 20:14:48 tengallon 20:15:00 bbiab 20:15:43 spew 20:15:53 spew-stew 20:16:22 #topic updating hardware 20:16:29 * CodeBlock[s] has returned 20:17:04 we also have some replacement hardware that has arrived in PHX2 to update our soon to be out of warranty boxes. 20:17:38 I am looking for help on best way to play the update-two-step. 20:17:59 as in we have xen01 going away and new hardware for it. How to migrate its children etc. 20:18:13 also do we put RHEL-5 on the new box or go to RHEL-6 and KVM? 20:18:46 I would like to make 1 box a RHEL-6 box so we can move a fas onto it. 20:18:54 If 6, let's...make sure it doesn't reboot randomly like fas does ^^ 20:19:04 Mainly to see if we get rid of our nightly frak storms 20:20:36 smooge: okay - so I do have one problem with that, personally 20:20:48 there is nothing in our charter to suggest we need to be QA for rhel 20:20:48 ok 20:20:53 and we're down one person 20:21:43 to me 20:21:57 it makes more sense to fallback to rhel5 until the rhel6 thing gets sorted 20:22:03 yeah. I don't plan to move too much to EL-6.I think FAS is currnelty EL-6 due to various libs not being in EL-5 20:22:05 but not make it be a nightly mess until then 20:23:00 what about RHEL-5 and KVM ? 20:24:29 can't remember if KVM is tech-preview or fully supported in EL-5. Been doing too much EL6 stuff lately 20:25:11 think it is supported but a quite old version. not sure. 20:25:44 I thought it was fully supported as of 5.4 20:26:26 the bigger issue though is that FAS is still EL-6 and would require a bunch of work to make it EL-5 (I believe). abadger1999 ? 20:26:28 smooge: Yeah, that's the story for fas. Rather than backporting all sorts of stuff, we went to rhel6. 20:27:16 We could theoretically start rebuilding all of those packages for el-5 and stick them in the infrastructure repo. 20:27:20 the issue we have is that hosts are rebooting nightly(?) and we don't have a real good cause 20:28:16 I don't know what all the packages are, though -- and it would be a big change from what we're running now since we have the rhel6 stack underneath it which means tons of things all the way down to python itself will be different. 20:28:18 the cause seems to be el-6 kernel in xen 20:28:38 okay 20:28:56 so - could we also do rhel6 on the bare metal + kvm to support fas? 20:29:26 that was what I was thinking for one of the new boxes. 20:29:40 that seems like a good plan to me 20:29:45 20:29:54 +1 20:29:55 if we can reasonably verify that rhel6 + kvm makes it all work 20:29:56 we have it currently on xen13 but that hardware has had MULTIPLE replacemtns so I have not tried it there 20:30:09 understood 20:30:10 the new boxes 20:30:12 Minimize the update to just what we have problems with now to see if it makes things better. 20:30:16 what's the blockers there? 20:31:02 boxes need to be racked and wired. new names/ip addresses given to them. 20:31:18 okay 20:31:23 systems then need to be 'built' and configured 20:31:32 nod 20:31:42 we have an excellent new sysadmin in the PHX2 facility so that won't be a problem 20:31:58 great. Do they have an ETA? 20:32:22 the boxes arrived last week. He is working on the download servers currnetly. 20:32:40 I will need to open a new ticket and see about getting it done in the next 2 weeks. 20:33:40 so quick question.. do we want to call them xenXX or something else? 20:33:52 kvm is NOT a good name. 20:34:04 virt##? 20:34:09 vmXX ? 20:34:10 virthost## 20:34:22 since they are not guests 20:34:33 virthost makes sense 20:35:13 and for the silly geek question.. C arrays or Fortran arrays :) [eg start with 00 or 01?] 20:35:43 * skvidal doesn't care 20:36:00 but if anyone changes the frelling width of the numbers they will taste wrath :) 20:36:09 looks like 01 is what we use all over 20:36:13 bastion01 20:36:15 puppet01 20:36:16 people01 20:36:20 let's stick w/that 20:36:44 yeah. I can rename xen13 to virthost00 since its crap hardware :). 20:37:02 umm 20:37:05 wait why? 20:37:17 just call it 01 20:37:18 or 0N 20:37:24 whatever the next number is 20:37:35 why break track with what we do everywhere else? 20:39:13 sorry I was being silly. 20:39:20 oh - I didn't catch the joke 20:39:42 np my humour is rough.. which means the pain medicine is wearing off. 20:39:52 ok i think htat is it at the moment. 20:39:58 #topic Open Floor 20:40:14 I'd like to introduce myself 20:40:19 hello goozbach 20:40:22 how are you? 20:40:35 I've been using fedora for a good long while and wanna join in on the infrastructure fun 20:40:39 so I 20:40:45 am looking for a sponsor 20:40:49 hello 20:41:04 smooge: doing well. excited to be here 20:41:16 I've already signed up for the infra list 20:41:27 is there anything else I need to do to get started? 20:42:38 well say hi on the list, find out what you would work on, and listen regularly on #feodra-admin and #feodra-noc for problems 20:42:42 goozbach: take a look on https://fedorahosted.org/fedora-infrastructure/report/1?sort=created&asc=0 and see if anything sparks your interest basically 20:43:17 Our big issues will be keeping up documentation, figuring out where things are not clear, and making them more clear. 20:43:37 I've already read the "getting started" guide. 20:44:09 ninjazjb, is a new fellow too and so is waltJ. CodeBlock is actually turning into an old-timer :). 20:44:26 * ninjazjb waves 20:44:46 welp, I've joined both channels, I'll craft an email to the list. 20:45:46 smooge: mind if I make an announcement? 20:46:07 smooge: :D 20:46:27 ke4qqq, sure 20:46:35 smooge: I've had so much fun here, I don't plan on leaving any time soon... if I'm not yet, I will soo be an old-timer ;) 20:46:41 soon* 20:46:47 ke4qqq, I mean "I do not mind if you make an announcement." 20:47:06 So, FAmSCo manages a bit of budget and we regularly don't spend it all. In addition there's talk of us taking on more of Fedora's budget responsibilities. 20:47:41 cool 20:48:01 And rather than effectively lose that which we don't spend, (which we recognize as lost opportunity) we wnat to make sure that other groups in Fedora know they can come obtain resources. So if you need something to help your efforts in Fedora, please don't hesitate to ask 20:48:20 Be that attending a conference like LISA or Pycon, or some piece of hardware. 20:48:37 smooge: can we tackle/discuss infra #2461 (it has the meeting keyword, not sure if you saw it) 20:48:48 ok ke4qqq where to ask? 20:48:55 I'll send a message to the list about this as well, but wanted to get it in front of you. 20:49:09 smooge: the easiest way is to talk to a famsco member or a ticket on famsco's trac 20:49:12 * ke4qqq goes to get a link 20:49:27 https://fedorahosted.org/famsco/ 20:49:32 #link https://fedorahosted.org/famsco/ 20:49:36 thanks 20:49:45 EOF - thanks smooge 20:50:23 your welcome. I look forward to seeing about USENIX stuff :) 20:50:41 CodeBlock, ok ticet 2461 20:50:47 .ticket 2461 20:50:48 smooge: #2461 (Allow some people outside of sysadmin-main to increase people01 quotas) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2461 20:51:28 * CodeBlock[s] talks briefly 20:51:58 I see requests for that quite a lot, and I'd like to help with that/be able to increase those... mmcgrath said that maybe we could allow -tools to do that or something along those lines 20:53:06 it's a sudo thing - it's not hard 20:53:14 though we don't get many requests 20:53:25 and I don't remember when the last one went un-answered for more than like an hour 20:53:30 skvidal: I see quite a lot on the tracker for those 20:53:44 CodeBlock[s]: un fulfilled? 20:53:55 skvidal, since you deal with this a lot.. this looks workable just a policy and guidelines issue and then dealing with people02 when it comes up. 20:54:07 oh, I have something to mention I guess too. 20:54:07 smooge: yah - I'm fine with that 20:54:17 skvidal: https://fedorahosted.org/fedora-infrastructure/ticket/2421 https://fedorahosted.org/fedora-infrastructure/ticket/2423 https://fedorahosted.org/fedora-infrastructure/ticket/2411 20:54:18 and added people02 back onto my todo list too 20:54:22 three that have gone for days 20:54:31 CodeBlock[s]: hmm - I hadn't seen them 20:54:33 which is odd 20:54:35 b/c I get the emails 20:54:38 * skvidal grumbles 20:54:44 me either.. so looks like another issue to deal wioth 20:55:31 #action find out where email tickets are going 20:55:42 #action work on SOP and policy 20:55:48 'assigned to nobody' 20:56:24 we have 3 minutes untiul the cloud meeting 20:56:28 looking at ticket 2413: Does http://fpaste.org/pb0j/ look like everything to do to rename that list? 20:56:52 * nirik is happy to have folks look and give feedback out of band. 20:57:14 smooge: is -tools going to be allowed to do that then, or what? 20:57:33 sorry I'm kind of fading in and out here between class and here 20:57:48 CodeBlock, a) probably yes. b) need to figure out changes first 20:58:01 smooge: alright sounds good 20:58:01 one last thing 20:58:08 meeting time next week 20:58:14 I would like to keep it at the same UTC 20:58:25 does that work or kill people? 20:58:35 WFM 20:58:37 :) 20:58:43 mmm, that would be what EST? 20:58:57 * CodeBlock[s] adds the 4 hours in his head I guess 20:59:06 well 20:59:10 it's +1 hour right? 20:59:12 ble 20:59:15 bleh* have to go 20:59:17 correct 20:59:21 see you 20:59:28 rbergeron, you ready to take over? 20:59:44 ok I am going to end this and put it on the list 20:59:48 see you next week. 20:59:52 #endmeeting