Fedora-Meeting
LOGS

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