Infrastructure/Meetings/2006-11-30

= Meeting of 2006-11-30 =


 * Time shown in EST

15:07 everyone here? 15:07 yo 15:07 * mmcgrath is late. 15:07 Who all is here? 15:07 warren, lmacken, mmcgrath, c4chris, iWolf ping 15:07 * lmacken is here 15:08 * jcollie is here - i'm one of the "new guys" 15:08 jcollie: welcome 15:08 schedule is http://fedoraproject.org/wiki/Infrastructure/Schedule 15:08 * teknofile is a "new guy" too 15:08 welcome 15:09 dgilmore: you want to take it today? 15:09 PckageDB c4chris, abadger1999  whats the good word? 15:09 mmcgrath: sure 15:09 ;-) 15:09 I'm orking on the schema 15:09 f13 thinks we might get brew open sourced though. 15:10 And that has implications both for buildsystem and for packageDB. 15:10 abadger1999: :D im getting turbo gears book on monday  so ill be jumping in more then 15:10 abadger1999: yeah 15:10 dgilmore: mine is waiting for me up at school :) 15:10 * iWolf is here for a few minutes, overlapping meetings. 15:10 dgilmore: Cool. I'm going to be playing a bit more with sqlalchemy vs sqlobject and post any questions I have to f-i-l so sopwith can tell me what I'm doing wrong ;-) 15:11 :D sounds good 15:11 so we are making some progress 15:11 yes.  If f13 is here I'd like to hear what's going on with brew though. 15:11 abadger1999, f13:  how goes the VCS stuff 15:11 If brew comes out, it'll be a big lump of stuff that we'll have to figure out how to integrate. 15:12 VCS is in a holding pattern for me as I work on the packageDB. 15:12 abadger1999:  yeah brew will throw a spanner in the works  but give us alot of other functionality also 15:12 abadger1999: PackageDB is more important now 15:12 on the topic of VCS.... 15:12 I think f13 made some good progress/finishing touches but he'll have to speak to that. 15:13 BTW guys, as far as I'm concerned cvs-int is back to where it was.  If you hear of anything not working right or not syncing or killing someone's dog. Let me know. 15:13 abadger1999: we will have to get an update from him on the list he said he was in another meeting this arvo 15:13 -!- japj [n=japj@japj.xs4all.nl] has joined #fedora-admin 15:13 mmcgrath: :) seems to be working ok from my end 15:14 mmcgrath: Did you work out all of f13's hg and git problems? 15:14 abadger1999: afaik yes. 15:14 mmcgrath: any word on getting the old cvs server with an os so we can do db2? 15:14 though I still have no idea why the hg IP changed. 15:14 Yeah.  I'll have to check with stacy and mgalgoci.  I think its ready. 15:14 I'll be building the dedicated backup server soon. 15:15 mmcgrath: :D  any sign of the new builder hardware? 15:15 < iWolf> mmcgrath: just let me know when it's ready and I can get started on it (hardware for db2) 15:15 dgilmore: I thought it was there already. 15:15 mdomsch: ? 15:15 mmcgrath: i have no idea 15:16 i could be   if it is ill get with stacy so i can install and configure it 15:16 xenbuilder1  is running nicely 15:16 solid. 15:16 i need to take a lvm snapshot of it 15:17 mmcgrath: want to send an email to stacy and mgalgoci to see what the hardware status is ? or want me to ? 15:17 dgilmore: Good work! 15:17 I'll drop them a note right now. 15:17 mmcgrath: thanks 15:18 we should have just the two boxes i think 15:18 were we going to use xen on the box for DB2? 15:19 < iWolf> dgilmore: not sure what the final decision was. I can if that's what folks want. 15:20 iWolf: what resouces will db2 need? 15:20 i think it would be nice to do it in xen 15:20 what VCS are we going to? 15:21 teknofile: we are looking at quite a few different ones 15:21 < iWolf> dgilmore: The dbs are small now, the largest backup is near 11mb I think... 15:21 ah, still eval 15:21 teknofile: no decision has been made yet 15:21 iWolf: the would thrive in xenguests i think 15:21 teknofile: Yes. And the scope of evaluation is getting larger: 15:22 with our resouces as they are we need to be extremly flexible 15:22 < iWolf> dgilmore: yeah, I don't think we would lose much by doing it in a xen guest. It just doesn't seem that busy or that intensive. 15:22 teknofile: Before we were concentrating on just porting our existing functionality over. Now we are also talking about trying new thin gs (expanded source trees, etc) Not sure how any of it will end up though. 15:23 iWolf: :D were we going to cluster mysql and postgres in the new setup? 15:23 'k 15:23 < iWolf> dgilmore: I was planning on getting things to the new stuff and then look at doing that. There was a guy that had some good cluster experience with DBs, not sure if he is still hanging out or not. 15:23 any word on when the new fedora-scm list is going to be set up? 15:24 jcollie: probably after fedora 7 timeline now 15:24 we are going to do a merge of core and extras in cvs 15:25 is that hg, git et al can't do partial checkouts? 15:25 jcollie: There shouldn't be any problem there that I can see. 15:25 mmcgrath, it was ordered a couple weeks ago, should have shipped 15:25 * mdomsch looks for the order number 15:25 the tree of repos seems to work? 15:26 jcollie: the hg test seems to be working pretty well 15:26 is the hg repo publically available yet? 15:26 dgilmore, ack, sorry 15:26 jcollie: yes it is 15:27 jcollie: ping f13 for access details 15:27 warren: :D 15:27 jcollie: The issue was that some people wanted to try more than a straight port of what we do in cvs. And want to not have to move to a straight port now only to move to the more experimental version later. 15:28 jcollie: http://www.fedoraproject.org/wiki/Infrastructure/VersionControl/dist-hg 15:28 have some of the new ideas been discussed anywhere? 15:28 jcollie: One of the steps is talking to f13 15:28 * iWolf heads to his work meeting 15:28 jcollie: It was discussed at the fedora-summit. But they deferred most of the experimentation to a fedora-scm SIG. which hasn't been formed yet. 15:29 mdomsch: thanks. 15:29 -!- glezos [n=glezosd@fedora/glezos] has joined #fedora-admin 15:29 anyone have anything else to add on any of the systems stuff? 15:30 I'd like to encourage some of the officers to become more familiar with cvs-int if they get time. 15:30 mmcgrath: ive done a little exploring of it this week 15:30 mmcgrath: I've been poking around on it. 15:30 its an ugly beast 15:30 Its just a good idea considering how farking CRAZY that box is right now. I hope to clean it up quite a bit soon. 15:30 the chroots are neat, though with xen we may want to look at a fully virtualized environment for each? who knows. 15:31 h -- mmcgrath: In cvs-dist there's a git section that points to lockbox. 15:31 Should that point to cvs-int now? 15:31 hmmm, not sure. 15:31 xen virtual servers for everyone! 15:31 * dgilmore hearts xen 15:32 lmacken: your next. 15:32 firewalls 15:32 I haven't had time to finish up the pyroman firewall deployment, and probably won't for another couple of weeks. If anyone is bored and wants to help out with it, please feel free. 15:32 It's only really a matter of running it, seeing what breaks, tweaking the pyroman configs, repeat. Everything should be documented in InfrastructurePrivate/Firewalls. 15:32 the updates system has taken top priority for me at the moment 15:33 lmacken: how is that comming along? 15:33 and while we're ont the topic 15:33 I've been making lots of progress with the new updates system. This is currently my top priority, as it is also going to be used for a new Red Hat product that we are shipping soon. 15:33 I'm hoping to have a prototype out within a couple of weeks. 15:33 I haven't had time to play with the TurboGears deployment on publictest2 yet 15:34 so again, if anyone gets bored.. feel free to play with it :) 15:34 mmcgrath, it should be there... 15:34 Status: Delivered 15:34 Delivered on:  11/20/2006 15:34 2:03 P.M. 15:34 Delivered to:  MESA,  AZ,  US 15:34 Signed by:  RODRIDGUEZ 15:35 cool 15:35 mdomsch: thanks 15:35 abadger1999: on the dist-hg wiki page there is a link to disthg-utils on http://www.fedoraproject.org/wiki/Infrastructure/VersionControl/dist-hg, but this doesn't seem to work... has this server moved? 15:35 np 15:35 legacy buildsys is waiting on a decision from legacy  as far as push scripts 15:36 EPEL buildsys is up and running  there will be some work for push scripts. and getting the final stuff in place 15:36 :: high five :: 15:36 ok, I'm back. 15:36 any of you new guys after things to do there is plenty that can be done for EPEL 15:37 ping mmcgrath or myself for some jobs 15:37 japj: Probably -- ask f13, now that he's here :-) 15:37 dgilmore: what is EPEL? 15:37 teknofile: it is Extra Package for Enterprise Linux 15:38 technofile: http://fedoraproject.org/wiki/Extras/Schedule/EnterpriseExtras 15:38 teknofile: its an effort to have extras packages available for RHEL, CentOS etc 15:39 interesting 15:39 i'll read up on this afternoon 15:39 mmcgrath: any progress on config management 15:39 mmcgrath: ive been meaning to check out the finer details of cfengine 15:40 I don't think anyone's taken a look at glump yet. I'll send a followup email 15:40 i have meant to look at it also but havent :( 15:40 mmcgrath: I took a quick look 15:40 what did you think? 15:41 As you say it is much different than what we currently have. 15:42 but it could be used with it, which is interesting. 15:42 What do we gain from it, though? 15:42 Basically enforcement. 15:42 yes. 15:42 if someone changes a file manually, it'll get changed back. 15:42 mmcgrath: i do like that idea 15:42 forcing them to use the cvs system.  Its not perfect. 15:42 But its better than what we have imho. 15:43 right now cvs is a little out of date. 15:43 That part is good.  But if that was all we wanted we wouldn't need all the rest of glump. 15:43  * f13 chuckles each time he sees "glump" 15:43 dgilmore: thats a whole chunk of this project is getting cvs back up to date. 15:44  * mmcgrath seems to recall a roar of laughter on the phone during the summit. 15:44 abadger1999: "the rest of glump" ? 15:45 If I recall glump constructs a script on a server and then sends it to the client to execute. Is that right? 15:46 naw, its a puller. Each client pulls the configs. 15:46 url for glump? google doesn't turn anything up interesting 15:46 jcollie: its used internally at Duke, they've recently gpl'd it. 15:47 http://linux.duke.edu/projects/mini/glump/? 15:47 http://linux.duke.edu/projects/mini/glump/ 15:47 oh wow, yeah thats it. 15:47 I didn't even know that was out there. 15:48 anyone got anything else to add? 15:48 new guys got any questions? 15:48 Okay. pull vs push. But it still is putting together a script that runs on the client? 15:49 dgilmore: not yet; I will once I read up on EPEL tho 15:49 Its a webapp, the client just needs to know where the script is, the server sends it a manifest of what files it should get and such. 15:49 dgilmore: we should discuss epel in a bit if you have a moment, but its not really fedora-admin related. 15:50 mmcgrath: sure want to do it once the meetings done? 15:50 yeah. 15:51 It just seems that if we just wanted to make sure we were synced with cvs, we could just have a cron script that checked out the files from cvs and then checked whether they were different from what's on the system. 15:52 glump seemed more complex than that and I feel like I'm missing something because there must be a reason why it's done the way it's done. 15:52 seems like some good work has been going on, in regards to getting the wiki behind the proxies 15:53 abadger1999: the main difference is management and backups. 15:53 our current system doesn't make any backups. 15:54 of overwritten files I mean. 15:54 plus, this is something that we can maintain with duke instead of just on our own. 15:54 mmcgrath: i like the idea of glump alot 15:54 dgilmore: before we quit glezos has something he'd like to bring up 15:55 * f13 has some things to report as well. 15:55 mmcgrath: now is the time 15:55 f13, go ahead. I'll wait 15:55 ok. 15:55 Project Hosting 15:55 So, http://hosted.fedoraprojects.org exists, and there are some early testers of our "hosting" services using trac. 15:56 accounts for trac are through the Fedora account system 15:56 an admin is chosen at project creation time, they get an 'admin' tab in trac to do fine tuning of their project space 15:56 is that the right url? i can't look that up... 15:56 We got git and hg repos back up and functional too, but whats missing is making those repos readable by trac for the integrated source view and timeline stuff. 15:56 remove the 's' 15:56 whoops 15:57 hosted.fedoraproject.org 15:57 I write up a wiki page on how to create a new project space 15:57 http://fedoraproject.org/wiki/Infrastructure/ProjectHosting/CreateNewProject 15:57 and an overall page http://fedoraproject.org/wiki/Infrastructure/ProjectHosting 15:57 I mostly did this because I needed project space for pungi (: 15:58 the other missing peices are raw webspace for code drops/yum repos/etc.. and mailing lists 15:58 :P 15:59 I think that for version1 of Feodra Hosted Projects, we can do all the setup by hand (creation of source repo, trac project space, raw webspace, and mailing list). 15:59 that allows us to launch something much sooner rather than waiting until we have a self service or otherwise integrated creation tool. 15:59 If anybody would like to help me with the few missing parts, I'd really appreciate it, because I probably won't be able to focus on it much more 15:59 f13: should we put mailman on hosted 15:59 f13: Does trac just need read-only local access to the repositories? 16:00 abadger1999: yes, readonly. 16:00 f13: We could jsut clone the repos. 16:00 abadger1999: we could yes, things don't update in real time then, but better than nothing. 16:00 abadger1999: or rather just do scheduled rsyncs since git/hg work like that (: 16:00 *grin* 16:02 so... 16:02 that about does it for Project Hosting. Its not a big priority (when compared to other things regarding core<->extras merger. 16:02 but somebody with more experience with say mailing list management and webspace management could look into 16:02 Next is VCS. 16:03 f13: thanks 16:03 This took a backseat as well because of the merger. I'll ping greg/max next week regarding creating the SCM SIG where hand wavy future land can be discussed. 16:04 I'm somewhat convinced though that we'll need to do it in two stages. Stage 1 is current workflow with new SCM of choice, stage 2 is new workflow with said new SCM once new SCM has been beat up on for a bit 16:04 and new ways of doing things have been explored. 16:04 i'm in favor of whatever gets us off cvs sooner 16:04 I'll send announcements when the SIG gets launched, probably create a mailing list for it to keep noisy conversation away from places like maintainer's list. 16:05 I think we may actually want something like git/hg in order to do secondary arches, so that syncing down changes isn't such a huge pain in the ass. 16:05 We'll see what happens. 16:05 --Buildsystem-- 16:05 f13: im really looking forward to the secondary arches stuff :D 16:05 is bzr out of the running? 16:06 jcollie: not as yet 16:06 Jeremy and I met with RH management regarding brew. It turned more into a why are we opening core and what does this really mean, but we did get to opening of brew a bit. Overall it went well, and we're meeting again on Friday to go over somethings more indepth. 16:06 so a "no" wasn't given, neither was a yes. 16:06 hmm 16:06 dgilmore: will you be avail in about 2hr to talk about EPEL? 16:06 f13: thats all we can ask for right now i guess 16:07 jcollie: bzr isn't, but I haven't seen a bzr proof of concept show up yet.. (: 16:07 teknofile: no, but i will be in about 3-4Hrs 16:07 dgilmore: I feel good about the meeting progress, and look forward to Friday 16:07 dgilmore: ok 16:07 teknofile: I'll be around. 16:07 ok, I'll have read the wiki by then 16:07 management knows that time is important and it seems they are prepared to make a decision soon, they just want to be fully aware of what decision they are making.  Hurray for no snap decisions. 16:07 -!- GeroldKa [n=Gerold@fedora/geroldka]  has joined #fedora-admin 16:08 Thats about all I have for infrastructure stuff. 16:08 f13: thanks again 16:08 mmcgrath: your floor 16:09 I don't have anything, glezos? 16:09 um ye.. 16:09 yes 16:09 I'll keep it short because it's already late 16:09 L10N might have some requests in the near future. I guess now it's the best time to bring them to the surface. 16:09 k 16:10 Some tasks are staring to form on http://fedoraproject.org/wiki/L10N/Tasks -- basically the bottom list is more concrete. 16:10 mhmm? 16:10 Some of these need some attention from the Infrastructure team (move CVS to a new root on cvs.fp.org) and the Rel Eng team (integrate translation processes/notifications in package updates)\ 16:11 I have no idea about how things are being done or should be done so I am in no position for suggesting anything. 16:13 There aren't a lot of people willing to really work on these issues, so the team might want some help in the tools, the transition and the general "integrate the l10n process *more* into our development/packaging model than we currently do" 16:13 eof 16:14 -!- lyz [n=lyz@dsl081-149-006.chi1.dsl.speakeasy.net] has quit ["Leaving"] 16:15 So... :) If a Q should be made it would be: What do you guys think is more important/urgent and how can we do it? 16:15 -!- mcanann [n=chatzill@216.68.73.132] has quit ["Chatzilla 0.9.75 [Firefox 1.5.0.8/0000000000] " 16:16 This is a really touchy subject because Red Hat itself is doing a lot of work in this area (or is supposed to) to make it easier for translators 16:17 glezos: thanks 16:17 f13, I'm sure it does. But it is a fact that translators do think we should lower the barrier of entry and increase the quality of the translations in our releases. And I must say, Fedora isn't known for it's good translation processes. :( 16:17 nod 16:18 I just want to make sure that Red Hat and Fedora Community don't go off in completely different directions. 16:18 f13: that would be bad 16:19 f13, nod 16:19 can we get the Red Hat guys on board 16:19 I would hope so. 16:19 hmm 16:20 glezos: make sure you send this to the list, we'll probably discuss it more then 16:20 glezos: I'll point the translation team lead at your wiki page and ask them to work with you, if possible. Is your contact info on those pages? 16:20 Some concrete suggestions that have been discusses are to move the pofiles to fp.org to ease the management and remove bottlenecks, and b) put string freezes and translation deadlines on the Core Schedule. 16:20 B) is easy 16:21 A)... probably not TOO difficult for the packages RH is the upstream for. 16:21 however the real thing we keep hearing is that if we want better translations in Fedora, we need to get better translations upstream 16:21 f13, then B2 could be something like "raise a flag if a package update changes translation strings" :) 16:21 its not like Fedora is replacing tons of strings in applications 16:21 f13, yes. But I'm not the appropriate person to coordinate these things... 16:23 f13, the upstream thing of translations is a very complex one (Ubuntu's rosetta is very, very bad for projects) and more-or-less it could be discussed later on or anyway not in the context of the Infrastructure team.. I guess. 16:23 im going to close the meeting in 30 16:23 glezos: please bring it up on the mailing list 16:23 dgilmore, I'm finished, no problem. 16:23 Will do. 16:23 Thanks. 16:24 20 16:24 mark 16:24 closed meeting thanks guys