20:01:09 #startmeeting 20:01:12 .startmeeting 20:01:16 how's this thing work again? 20:01:16 :) 20:01:18 I wonder if nirik needs to give you privileges again. 20:01:31 eh, we'll skip it today 20:01:52 sorry, my virtual running it crashed. ;( 20:01:52 it's rejoining now. 20:01:52 * ricky 20:02:00 * lmacken 20:02:08 there it goes. 20:02:30 * sthistle says hi.. 1st time 20:02:40 Welcome :-) 20:02:56 Ok, so lets get started 20:03:00 #topic Infrastructure -- Tickets 20:03:07 I'm here too 20:03:22 .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&status=reopened&group=milestone&keywords=~Meeting&order=priority 20:03:22 mmcgrath: http://tinyurl.com/47e37y 20:03:27 .ticket 1464 20:03:32 mmcgrath: #1464 (Puppet Web Apps Refactoring) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1464 20:03:34 ricky: you want to take this one? 20:03:37 Jorn23: hey 20:03:41 Sure 20:03:47 heya :) 20:03:55 I've been working on converting all of our apps to puppet modules 20:04:06 * dgilmore is here 20:04:14 Right now, most of our applications are running off of the modules under the stg.fedoraproject.org namespaces. 20:04:40 For this first piece, my goal is to only touch the app and proxy servers to keep things manageable. 20:04:44 * abadger1999 here 20:05:22 ricky: if you were to guess, what % done are you? 20:05:24 The way that I'd *like* to move things over is to get the staging environment into the exact configuration that we want, and then just drop it right into the master branch. 20:06:06 I have all of our large apps moved, but I haven't gotten all of the behaviors of our production configs, like some redirects and stuff. 20:06:46 So maybe 70-80% or so. I'm going to try and get the details matched up today, then send an email out asking people ot make sure that *.stg.fedoraproject.org behaves exactly like they want it. 20:07:01 excellent. 20:07:04 ricky: thanks for that 20:07:34 ricky: should we avoid messing staging up much until that's done? 20:08:14 Most of the puppet modules aren't changing much at this point 20:08:31 Just keep in mind if that if you want configuration changes to show up in staging, you need to edit the files in the module 20:08:55 20:08:59 ricky: anything else on that? 20:09:09 Nope, thanks 20:09:19 coolz. 20:10:07 Ok, so thats the last ticket there. 20:10:52 So there's not been too much going on with this in the past month or so but if you've been watching the commit logs you'll notice I've been rebuilding it all. 20:10:58 I'm hoping to get something up and going fairly soon. 20:11:14 I've been using it off and on with mostly success. 20:11:40 There's a whole other web interface that some various people are working on to make it less 'ovirt ui' ish and more 'end user fedora friendly' 20:11:55 No ETA on that. 20:11:56 mmcgrath: :) 20:12:05 What exactly is "cloud stuff" ? 20:12:09 but I am hoping to queue up some of the queues. 20:12:41 Jorn23: http://fedoraproject.org/wiki/XavierLamien/Infrastructure/FedoraCloud 20:12:45 I think that's fairly up to date. 20:12:50 with what we're doing 20:13:00 Cheers, I'll read that up 20:13:01 but it's basically an http://ovirt.org/ setup. 20:13:14 Anyone have any questions on that? 20:13:59 Ok. 20:14:13 so we've had a lot of changes since F11 shipped. 20:14:23 probably more changes in the last couple of weeks then we've ever had. 20:14:31 some have been major, some minor, but there's been a bunch of them. 20:14:41 I only bring it up because we've been shaking out bugs and things 20:14:53 * dgilmore has one coming up that id like to talk about at some point 20:14:54 so keep your eyes open. 20:15:05 and if you find something, please don't assume we know about it. 20:15:49 Thats really all I had on that :) 20:16:02 :) 20:16:05 dgilmore: whats the poop? 20:16:14 mmcgrath: im killing plague tomorrow 20:16:24 * mmcgrath cheers 20:16:25 well sort of. 20:16:32 * nirik jumps up and down in joy. 20:16:34 dgilmore: whats our process going to be for signing and pushing? 20:16:39 do I need to build another signing server? 20:16:41 epel will switch to koji 20:16:46 i think i have bodhi ready 20:16:56 but i need to run some things by lmacken 20:17:01 who i can never get ahold of 20:17:04 Feel free to update it in staging if you have a newer package. 20:17:11 another signing server. ew 20:17:31 * mmcgrath wonders if koji.stg.fedoraproject.org is back up and running. 20:17:31 i need to setup epel_releng 20:17:36 epel-releng1 20:17:40 something like that 20:17:47 dgilmore: thats a group or a host? 20:17:57 mmcgrath: a host 20:18:08 dgilmore: who's going to be able to sign and push? 20:18:10 to do mash and package signing on for epel 20:18:13 how long is that process going to take 20:18:14 etc 20:18:19 mmcgrath: epel_signers 20:18:33 mmcgrath: until we can test not sure 20:18:41 but much shorted than fedora updates 20:18:49 shorter 20:18:50 so maybe we don't want to kill plague until we know the rest of that stuff? :) 20:19:23 dgilmore: so aside from the additional signing server what do we need? 20:19:24 dgilmore, why is it going to be shorter? 20:19:33 less packages? 20:19:35 or do we need another releng box and not a signing server for epel? 20:19:35 jwb: alot less packages 20:19:36 many fewer packages. 20:19:40 ah 20:19:43 less arches too 20:19:47 mmcgrath: just another releng box 20:19:52 i was thikning frequency. not per-push duration 20:19:52 does EPEL do ppc(64) ? 20:19:53 will it? 20:19:57 epel does ppc 20:19:57 f13: it does. 20:20:00 but not ppc64 20:20:01 ah ok 20:20:18 i was approached this weeke about doing s390x for epel also 20:20:22 dgilmore: what about disk? right now releng2 requires direct write access to /mnt/koji 20:20:23 the only weird thing is there is no desktop RHEL for pcc. 20:20:26 ppc 20:20:28 I'd assume we don't want that for EPEL? 20:20:39 mmcgrath: the epel releng box will need to write also 20:20:57 mmcgrath: the process will be the same 20:20:58 :: sigh :: 20:21:06 are we really sure we want fedora's process infecting epels? 20:21:09 and i guess we ould use the existing releng resources 20:21:11 epel used to have such low overhead. 20:21:20 mmcgrath: depends on how y ou look at it 20:21:27 mmcgrath: lots of people want it 20:21:30 mmcgrath: shuffling the repodata around different locations isn't exactly "low" overhead 20:21:41 mmcgrath: updates notifications will be a big win 20:22:01 f13: I look at it as someone who watched jwb freak out a couple of days ago because he started a push that he wasn't sure would finish in time for the pkgdb update which was something like 18 hours away at the time. 20:22:18 also epel has no deltas to worry about. 20:22:21 mmcgrath: we're talking about different orders of magnitute 20:22:26 magnitude 20:22:26 mmcgrath, yeah, what f13 said 20:22:26 right now we are. 20:22:27 the pkgdb update doesn't effect pushing updates 20:22:30 at all 20:22:34 nirik: right at least until we get to rhel 6 20:22:39 also what lmacken said 20:22:40 lmacken: But jwb didn't *know* that. 20:22:46 lmacken: thats my other point. No one was quite sure about that because of how many moving parts were involved. 20:22:46 but i see where mmcgrath is coming from 20:23:04 right 20:23:22 anywho, if we're going forward with it we're going forward with it. 20:23:34 dgilmore: you have a pretty good idea of how a relepel1 would work? 20:23:45 mmcgrath: i think we should go ahead 20:23:48 mmcgrath: i do 20:24:07 k, then we'll go forward. 20:24:48 dgilmore: ping me after the meeting about getting that server up, I'm positive we've got space for it somewhere. 20:24:59 f13: and that reminds me, I owe you a shiny new signing server :) 20:25:07 mmcgrath: :) thanks 20:25:11 mmcgrath: cool 20:25:17 it's racked, I need to throw an OS on there and talk to you about migrating to it whenever you guys are ready. 20:25:29 hell I might just be able to use dd and copy the old signing server over. 20:25:32 mmcgrath: if we get the signing server up and running it should be useable for EPEL as well as fedora 20:25:55 well, this signing server is just different hardware. 20:26:05 as for the signing server software, I think that's still a TODO 20:26:20 dgilmore: anything else on the EPEL move away from plague? 20:26:28 mmcgrath: nope 20:26:37 coolz 20:26:44 #topic Infrastructure -- Signing Server 20:27:01 we have signing server software to start using 20:27:02 f13: since you're here, do you want me to build the new signing server virtual so you guys can still log in and virsh and stuff? 20:27:11 and with the new hardware, now would be a good time to try and deploy it 20:27:15 f13: or do you want it to be physcial and require console access? 20:27:18 oh, excellent. 20:27:33 that's... a good question 20:27:37 can we get back to you on that? (: 20:27:38 f13: that'd probably work best then, it'll allow you guys to keep using the current signing box while the new one is getting ready. 20:27:38 f13: what software? 20:27:45 lmacken: mitr wrote software 20:27:52 f13: where is it? 20:27:53 f13: yeah, I'm on whatever schedule you guys want me to be :) 20:28:25 * ricky had no idea people were working on signing software 20:28:28 https://fedorahosted.org/sigul/browser 20:28:52 oh, nice :) 20:29:09 http://git.fedorahosted.org/git/?p=sigul.git;a=summary if you prefer 20:29:31 it hasn't been touched in a while because we wanted to get F11 out before we disrupted the signing process. 20:29:32 heh 20:30:37 K 20:30:42 we'll take a look at that 20:30:47 any other questions on the signing server? 20:31:08 Alllrighty. 20:31:34 * mmcgrath thinks of anything else... 20:31:41 I think that's really all I've got right now 20:31:47 #topic Infrastructure -- Who's here? 20:31:53 #topic Infrastructure -- Open Floor 20:31:54 oops :) 20:31:55 I have one quick item. 20:31:56 Heh 20:32:30 nirik: have at it 20:33:01 I've been working with the meetbot plugin author... he hopes to have a release in the next few days with more features/cleanups/fixes. At that point I would like to set it up with zodbot and see about having it log to a fedoraproject.org area... also a search engine of some kind on it would be nice. 20:33:26 nirik: its a neat bot 20:33:34 If anyone has feedback for it, let me know. If I need to request anything or get anything approved as far as setting it up, let me know. ;) 20:33:53 I already have it packaged. Just waiting to import it for the changes to land. 20:34:08 nirik: I've been fine with it. 20:34:14 can anyone use the start and stop meeting bits? 20:34:17 yep. 20:34:20 how's that access figured out? 20:34:32 it's open to anyone on a channel where that plugin is enabled. 20:34:48 excellent 20:35:06 however, there are now some native supybot commands to let bot admins close meetings/add chairs 20:35:19 nirik: we'll throw up some sort of web deal for logging 20:35:22 if we haven't already 20:35:24 ricky: have we already? 20:35:29 Not now 20:35:30 so, an admin could override and close a meeting that was mistakenly made 20:36:16 the upstream author is working on converting it to use Restructured text for it's summary... and then spit out html and a text suitable for posting to mailing lists. 20:36:35 anyhow, just thought I would bring it up. Thats it. 20:37:04 nirik: excellent, thanks for keeping up with that 20:37:58 Anyone have anything else they'd like to discuss? 20:38:28 Just had a question for ricky 20:38:41 Or well, not really only for ricky 20:38:42 Anyway 20:39:32 Ask away :-) 20:39:33 Jorn23: have at it 20:39:33 A couple of days ago we talked about me helping with the migrations to ha-proxy, when do you think you have time for that ricky? 20:39:51 Jorn23: yeah we found lots of small odds and ends that were still in balancer :) 20:40:09 There are a few that we could get after the meeting if you're around 20:40:22 It'd be helpful for the work I'm doing in staging, actually. 20:40:31 ricky: yeah, I figure if we could go through one or two with Jorn23 he'd be able to get the rest 20:40:32 There might also be a few that I did in staging that would be good to get live. 20:40:53 That sounds good yeah 20:41:38 But we can discuss the details outside the meeting I imagine. 20:42:19 Jorn23: sounds good, thanks for helping us work on that :) 20:42:24 anyone have anything else they'd like to discuss? 20:44:09 ok, well with that we'll close the meeting 20:44:11 I should bring up autotest 20:44:16 f13: oh, have at it 20:44:21 #topic Infrastructure -- autotest 20:44:32 the QA team and I have been working on getting something ready to go in Fedora Infra for automated testing 20:44:56 There was a work in progress "invented here" effort called AutoQA, however we recently discovered Autotest from the kernel project 20:45:05 it seems to fit our needs nicely and already has an upstream and community around it 20:45:12 so I've spent the week trying to get it packaged 20:45:26 and we plan to deploy it within FI shortly to do some initial automated testing 20:45:31 however there is a bit of a problem 20:45:45 the server side of autotest requires an older Django than what's in Fedora 20:45:55 and building autotest properly requires use of Google Web Toolkit 20:46:11 gwt isn't in Fedora, and will be an extreme pain to get in, due to the snowball effect of piles of java 20:46:20 hahahah 20:46:26 Blech. 20:46:27 this is going to be a pile of fun :) 20:46:36 however gwt is in a RHEL5 product, and I think the Django version available for EL5 matches what we need 20:47:06 so I'm working on a package I can build against RHT's brew that has gwt, to produce something suitable for an EL5 host. gwt isn't needed at rumtime, only a build to translate java files to javascript 20:47:28 we'll continue to try and get gwt into Fedora, but that's going to have to be a project all on its own 20:47:44 f13: k, I'll be happy to help with that when the time comes. We do have a free software policy to make sure we follow - 20:47:47 If I get something built via RHT's brew, would we be able to use it within FI to run an autotest host? 20:47:56 http://infrastructure.fedoraproject.org/csi/free-software-policy/en-US/html-single/ 20:48:10 But yeah, I think we'll have hosts for it and stuff 20:48:19 all the software involved is free, it's just a huge hassle to get packaged. 20:48:32 I think james may have some machines to throw at it too, mostly I was looking for a policy decision 20:49:34 the other thing we've done is had upstream pre-translate the java to javascript. javascript is technically not binary, but it is cheating a bit 20:49:45 yeah, we'll figure something out. 20:49:52 f13: anything else on that for now? 20:49:53 but it did remove our need of gwt during package build. I'd prefer that we stuck with using gwt at build time, from RHT 20:50:09 nope. We'll likely be looking to host it after FUDCon Berlin 20:50:17 f13: sounds good 20:50:25 one last thing, has folks here had enough time to review the proposals that came from the recent FAD? 20:50:37 f13: There were proposals from FAD? 20:50:43 oh my yes 20:51:07 https://fedoraproject.org/wiki/Fedora_Activity_Day_Fedora_Development_Cycle_2009#Resulting_Output 20:51:51 please do read and comment if there are any concerns, as we move these proposals further into planning and polishing up for submitting to FESCo 20:52:11 f13: k, I'll send a note to the infrastructure list and let people to know to read over them, I'll do the same. 20:52:18 f13: Which ones affect FI? 20:52:40 Everything but hte first? 20:52:44 milestone does, as it reduces the freeze points (no more alpha), and yeah 20:52:49 pretty much all of them in one way or another. 20:53:22 f13: was anyone from Infrastructure at FAD? 20:53:32 * mmcgrath isn't sure who attended that 20:53:34 I think skvidal might have been there 20:53:46 I think seth, jesse and luke? 20:54:01 yep 20:54:14 Ah, I see the Attendees section in the link. 20:54:40 K, anyone have anything else to discuss? 20:54:54 If not we'll close in 30 20:55:23 #endmeeting