Infrastructure/Meetings/2006-10-19

= Meeting of 2006-10-19 =


 * Time shown in EDT

16:00 We ready to have a meeting? 16:01 < iWolf> mmcgrath: I am here. 16:02 Role call: Who's here? 16:02 * lmacken 16:02 I'm on 16:02 * jwatson is here 16:02 on but away for a min 16:04 Welp, the way these things usually go is we follow the Schedule listed on http://fedoraproject .org/wiki/Infrastructure/Schedule 16:04 Its not a hard and fast rule, but its good to have in front of you while we do the meetings. 16:06 So the first item is the unifying look and feel for admin.fedoraproject.org. 16:06 Its still unclaimed so if any of the new people want it, just put your name as the 'project' lead. 16:07 next item is the Package Database. 16:07 dgilmore: anything to add? Whats going on with that? 16:07 mmcgrath: its comminag along I havent done much yet but the other guys have 16:08 k. 16:08 we'll skip VCS for the moment. 16:08 :) 16:08 iWolf: systems upgrades: anything to report? 16:09 iWolf: i put a fc6 xen guest in for db2 16:09 < iWolf> I have a list of what is using what DB and which config files changed, tested restores on one ofthe earlier xen guests. 16:09 < iWolf> All that went smoothly. 16:09 RHEL4 just did not want to behave for me 16:09 < iWolf> Waiting on word if new hardware pans out. 16:09 < iWolf> dgilmore: Even the reboot of xen2 didn't help, eh? 16:10 hey there 16:10 we should know for sure within a week or so.  I should get shipping information by then. 16:10 abompard: yo 16:10 iWolf: no  it didint 16:10 < iWolf> mmcgrath: sounds great. 16:10 lmacken: around? 16:10 < iWolf> dgilmore: hhmmm 16:10 yup yup 16:10 firewalls 16:10 app1 is now running the pyroman configuration, although as far as I could tell the only traffic app1 was getting was from the load balancer every second or so. 16:10 Whats the word on the firwalls? 16:11 lmacken: did you ever look at the builders? 16:11 shouldn't all of the traffic going to the app servers be from the proxies ? 16:11 yeah, iWolf is going to do a brief audit tonight to find out what state everything is in. 16:11 dgilmore: not yet, definitely this weekend 16:11 awesome 16:11 It could be that all the proxy servers are accidently pointing to one app server. 16:11 most of our machines don't need to be running cups and sendmail :( 16:11 < iWolf> Yep, still planning on poking around on that tonight. 16:11 < iWolf> Plans to help fix that too! 16:11 no they don't. 16:12 we'll discuss that more on the ilst. 16:12 k 16:12 Documentation: I've added some stuff to the wiki as far as the getting started page and the Officers stuff. 16:12 * mmcgrath notes some officers are still mostly blank ;-) 16:12 For the new people, what did you think of the getting started page, what is it missing if anything? 16:13 * dgilmore is guilty 16:13 I found it easy to follow 16:13 The only problem I ran into was getting Wiki Edit access. 16:14 Yeah, that parts kind of a crap shoot. Typically you have to know someone, or be known on the lists to get access. 16:14 it was pretty easy to use 16:14 Though, come to think of it, wiki edit access isn't totally a prerequisite to getting involved with FI. 16:15 but it does help. 16:15 I posted a couple of times in #fedora-websites, but nobody answered. :) I didn't try adding myself to the queue page. 16:15 jwatson: send an email to the list, we'll get you set up. 16:15 The next item is Xen: I think we can move that to done. 16:15 dgilmore: whats the word on the legacy buildsys? 16:16 mmcgrath: we need something to build  and make sure it is working 16:16 Yeah, I think Wiki Edit access could be one of those things that you get access to when you need it.  Maybe not necessary in the Getting Started list. 16:16 push scipts need to be setup also 16:16 if I requested a build right now, what would happen? 16:16 it should build 16:16  * mmcgrath goes to request a build 16:18 Can someone give a short description of the legacy build sys?  Does it build Extras from cvs? 16:18 jwatson: actually the legacy buildsys is to build packages for Fedora-Legacy. 16:19 just as the extras buildsys builds packages for extras. 16:19 they're actually the same buildsys :) 16:19 ok, I'll keep you guys informed about that. 16:20 hmm, it might be nice to have a WikiEdit group in the account system 16:21 dgilmore: something's farked in the makefile I think - Server returned an error: This build server is set up for building CVS checkouts only. 16:21 we'll get back to that. 16:21 One of the big things I wanted to discuss is some priorities on our projects. 16:21 mmcgrath: yeah you need to use a cvs tag to build 16:21 We've got a deadline for a couple of things thats quickly approaching. 16:21 you cant build SRPMS 16:21 dgilmore: that came from a "make plague" :) 16:22 hmm then we need to fix legacy's Makefiles 16:22 yeah 16:22 Ok, so we've got the VCS to choose 16:22 The Accounting System to get under way 16:23 and the package database. 16:23 how are the test VCS's comming along? 16:23 I see these as our 3 biggest areas, anyone have anything to add to that list? 16:23  I need to free up time. 16:23 Although one of the new people pinged me yesterday with some interest in that. 16:24 we need to start getting the developers involved.  It'll probably be them that picks it. 16:24 mmcgrath: id agree they  are our biggest things 16:24 and they are big 16:24 We've got SVN up, they all know how CVS works. 16:24 we're looking at mercurial and possibly git? 16:24 bazzar? 16:24 and bazzar 16:24  * mmcgrath goes to look at the page 16:24 Yeah.  Bazaar is furthest along. 16:24 No one's taken git. 16:25 There's plenty of inhouse (inside RH) knowledge of mercurial but everyone's busy. 16:25 For the new guys: http://fedoraproject.org/wiki/Infrastructure/VersionControl/ArchitectureDraft 16:25 Err... svn might be further than bzr as mmcgrath set it up :-) 16:25 abadger1999: we might want to tap warren and maybe skvidal 16:25 yeah, svn's up and ready :) 16:26 * dgilmore  hasnt done git before  but i guess no time better to learn that the present 16:26 dudes, I'm sorry but I gotta run. No news from me on the Accounting System, I just didn't find the time lately. Sorry, I'll try to free some 16:26 abompard catch ya later 16:26 abompard: no problem. See you around. 16:26 Accounting sys -- do you guys want new helpers? 16:26 in a bit yes 16:26 we've got lots of new people that could aid in that. 16:26 the web site will have to be modified to use LDAP 16:27 LOTS of stuff will have to be modified to use LDAP :) 16:27 mmcgrath: :-) 16:27 I've got a xen instance now 16:27 lmacken: real quick, can you give some info as to what the "update system" is? 16:27 going to work on that today 16:28 the Fedora Update System is the tool used to push core updates 16:28 I'm working on porting it over to TurboGears and allowing it to encompass core/extras/legacy 16:28 lmacken: that would be very cool 16:29 is that something we'd want ready by FC7? 16:29 yeah. I will probably dump my svn repo into our svn repo soon 16:29 cool, Ok. So I'll add that to the top priority list. 16:29 sounds good 16:30 dgilmore: what are your thoughts on the packaging database? 16:30 ready for FC7? 16:30 mmcgrath: i would really hope so 16:30 ok, so. We've got 6 months to put out 4 pretty major projects. 16:30 We should be able to get some form of package DB out before FC7 16:30 starting... like a week ago. 16:31 though we added a few thinks  like a way to generate the comps file from it 16:31 dgilmore: I was already planning on that as a feature :-) 16:31 I don't want to push the accounting system to force it out by FC7 if its not ready, that one could wait until after since we already have a working account system. 16:31 abadger1999: :) 16:31 but the other three I'd like to put a solid deadline on. 16:31 dgilmore: Although I put it in as a "possibly do it later" 16:31 officers, sound good? 16:32 Sounds good. 16:32 < iWolf> Sounds good to me. 16:32 We'll have to hit the devs hard after FC6 gets out the door. 16:32 to help test and all that. 16:33 mmcgrath: sounds good 16:33 Ok, so with that done. I'll open the floor. 16:34 who's got what? 16:34 im going to sit down and do some coding on plague soon  anyone  have anything they want added 16:34 can you make it bake cookies? 16:36 mmmm cookies 16:36 Anyone else have anything? 16:37 yeah 16:37 mmcgrath: no cookies for you 16:37 I added the mirror management frontend to the wishlist. 16:37 I put some basic requirements on the wiki a while back 16:37 http://fedoraproject.org/wiki/Infrastructure/MirrorManagement 16:37 some of which is now being done by seth's check-mirrors code. 16:37 having a web tool to monitor the health of our mirrors would be nice 16:38 any takers? 16:38 if not we can do it onlist 16:38 kind of like: http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=i386&stats=1 16:38 I've been modifying that code heavily since it went out. its kind of on a freeze right now until FC6 is out. 16:39 yeah, that's definitely a start 16:39 would nagios work? 16:39 What about mrtg or cricket? 16:39 nagios could do some of it. Its got a fully functional database back end. 16:39 mmcgrath: ping? 16:39 mmcgrath: whats up with bash? 16:39 f13: pong. 16:39 we were testing the legacy buildsystem. Just a release bump. 16:39 mmcgrath: we also want the mirror admins to be able to self service their mirrors and whatnot 16:40 It failed though so I'll have to find out what happened. 16:40 mmcgrath: the diff was huge 16:40 huh? shouldn't have been. 16:40 link? 16:41 I don't know if it's on viewcvs, but you added something like 15 changelog entries 16:41 I must not be on that list. Forward it to me, I'll take a look. 16:41 lmacken: nod, maybe one of our new devs would like to assist on it. 16:42 f13: OOOHHH, I know what happened... my bad. 16:42 I copied the FC-4 bash.spec to the FC-3 tree. I'll fix it. 16:42 haha, ok. 16:43 it would be nice to start breaking subtasks out of all the development items so we can have things we parcel out to new devs. 16:43 abadger1999: do you want to start taking some of that over? 16:43 Yeah. 16:43 :: whew :: :P 16:43 I've started working on it for the packageDB. 16:43 I can do some of that for VCS as well. 16:44 I'll send a cattle call out to the list to see if anyone has previous GIT experience. If not dgilmore and I will just have to sit down and learn it ;-) 16:44 Acct Sys and Update Sys I'd like feedback from you guys about what tasks you think would go well for a new user. 16:44 What language or methodology do we write things like the Mirror Manager in? Are we standardizing on TurboGears?  Or is it whatever gets the job done? 16:45 mmcgrath: There's also things like writing testing scripts to see how far the various VCS's scale. 16:45 I think TurboGears can really help speed up our development process too.  All we need at firstis an svn repo; turbogears can be run locally without a production envorinment. 16:45 and importers to get data from CVS quickly when the time comes. 16:45 mmcgrath: just chatting with jeremy  we are going to branch extras monday 16:45 and porting the Makefile.common to the new VCS's. 16:45 abadger1999: yeah.  The CVS change is really a big project.  And it will require testing from extras and devel. 16:45 dgilmore: excellent. 16:46 lmacken: svn repo for TG? 16:46 abadger1999: no, for each project 16:47 for now I'd think the tg stuff should go in the fedora cvs. 16:47 lmacken: Just for general management of the code? Like the current cvs stuff? 16:48 abadger1999: yes, you can run local development instances outside of the production code 16:48 great for testing 16:48 lmacken: you mean turbogears has some sort of built-in svn integration? 16:48 mmcgrath: no, no. i was just saying that all it needs is a repo. 16:48 got'cha ;-P 16:49 ok, so we'll get started on that. In the meantime we all need to pick our favorite SVN repo as well. 16:49 err not SVN repo. VCS system. 16:49 lmacken: k. So like fedora cvs but in svn rather than cvs. 16:49 Whatever gets chosen will need to be supported immediately, I'd hate for them to pick GIT andhave no one be familiar with it. 16:49 mmcgrath: Bazaar :-) 16:49 * mmcgrath shutters 16:50 I'm familiar with svn.  Could learn git too. 16:50 email sent. 16:51 We can discuss the rest of this on the list. 16:51 Bazaar was a natural progression from svn for me.  The commands feel more natural than merc urial or git (from my svn background). 16:51 Gotta keep short meeting times :D 16:51 I've never used bazaar in my life. 16:51 ha ha. 16:51 I've been to one before. 16:51 ditto 16:51 (wrt using it) 16:52 Ok, so does anyone have anything else before I close the meeting? 16:52 What about repos for our rpms? 16:52 not I 16:52 Ohhh yeah. 16:52 thanks DGILMORE ;-) 16:52 * dgilmore  nearly forgot that 16:52 * abadger1999 prods mmcgrath 16:52 * iWolf forgot too 16:53 Ok, so I'm going to create a yum repo on fpserv that will get replicated to our app servers. 16:53 The plan right now is to follow the same format/name space as the fedora repos. 16:53 They will be yumable as well. 16:53 I'll send the final info to the list about exactly where the master is. I'll copy all the RPMS in our CVS db to it. 16:53 sound good? 16:54 < iWolf> mmcgrath: sounds good to me. 16:54 yep sounds good to me 16:54 we have yum on the RHEL sevrers? 16:54 sounds good. 16:55 At FESCo someone asked if we're using the vanilla FC3 build of rpms or our own rebuild. 16:55 not yet but we will 16:55 and RHEL5 uses yum by default. 16:55 If it was a rebuild, why not just put the support in the devel branch instead of an FC3. 16:56 abadger1999: I've just been using the extras buildsys. 16:56 mmcgrath: k. So we are using the FC3 built rpm for now? 16:56 abadger1999: yeah. 16:57 Sometimes I use karan's repo. 16:57 FC3 != RHEL4 but they're pretty damn close. 16:57 Ok, one more time. Does anyone have anything else :) 16:58 * dgilmore shuts up this time 16:59 alllrighty.  Then I'll call meeting end in 30 16:59 15 16:59 10 16:59 5 16:59 4 16:59 3 16:59 1.5 16:59 1 16:59 --- END ---