Infrastructure/Meetings/2006-03-02

= Meeting of 2006-03-02 =


 * Time shown in CST

[14:05:49]   Alllrighty, we ready to start? [14:06:12]   yea [14:06:13]  Who's here? [14:06:14]  I am. [14:06:19]  ready [14:06:20]   me [14:06:47]   nman64 iwolf: we're starting without sopwith, you guys still here? [14:06:47]  I am [14:07:23]   Item one on the agenda is the systems upgrades. [14:07:37]  I've been working with Sopwith on this for Proxy1. We've hit some bumps. [14:07:51]  just got access to proxy3 [14:07:57]  Right now we're waiting on Stacy to get PXE setup I think so we can pxeboot that machine. [14:08:10]  I've been extremely busy, so I'm waiting and watching your efforts on proxy1 before I tackle app2. [14:08:16]  Make sure you know whether the machine is using lilo or grub before you boot. I thought mine was using grub but it turned out to be lilo [14:08:19]  mmcgrath: I'm sortof here. [14:08:25]  f13: k [14:08:38]    Back again. [14:08:44]  welcome back. [14:09:02]  Did everyone have a chance to look at my kickstart scripts? [14:09:07]  yes [14:09:26]   Yep. [14:09:30]   I need to have a look over it just uni have seem to through alot of assignments out this year :( [14:09:32]   Personally I'm still apathetic as to whether or not to use a ks or whether to just use a VNC install. [14:09:36]    but ill hav a look overit [14:09:49]   are we going to decide on what packages to install as a base [14:10:13]    I think a set base might be good.  That way we know what we can count on being on every machine. [14:10:15]   I'm actually leaning towards a VNC install because we don't really know how good a shape these machines are in and an interactive install might be more useful as far as troubleshooting goes if the install runs into any problems. [14:10:20]    And then add based on the role of the server. [14:10:31]    I also lean towards the VNC install. [14:10:49]   but Its really up to you guys and your individual needs. I'm fine with a minimal install, get rid of all the packages we dont' need (as are listed in the ks script) and then adding packagese from there. [14:10:59]   mmcgrath, yea VNC sounds good [14:11:03]  mmcgrath: VNC install sounds good. [14:11:05]  err not really individual need but preference. [14:11:24]  rule no.1 on of SA always install what you need exclude rest [14:11:27]  k, VNC it is. We can always revisit ks later but we're doing 10's of installs, not 100's. [14:12:04]   mmcgrath, I am sure each of us could take a machine [14:12:06]  Feel free to get started on your installs if you want. Mine's kind of on hold right now. [14:12:14]  I think most people already have a machine from the last meeting. [14:12:22]   mmcgrath: Are you documenting your steps so far? [14:12:23]   I never got one :( [14:12:48]    mmcgrath: So we don't work over the same hurdles? [14:13:02]   xDamonx I think there's probably some to go around. Take a look at last weeks meeting and see which boxes haven't been claimed yet. [14:13:12]    ok [14:13:24]   I've been mindful of the steps so far but haven't actually documented them. I'll post to the list when we get a successful install. [14:13:50]   A big problem I've been having is I can't get the cyclades serial interface to work correctly... [14:14:01]   mmcgrath:  that would be great!  Do we a place to store documentation? [14:14:08]    Sounds good.  That will hopefully keep us from hitting the same roadblocks along the way and maybe make it easier in the future. [14:14:25]   The wiki for the most part I guess. [14:14:39]   though some of it might be considered 'security sensitive' passwords and things for example. [14:14:47]  I'll talk to sopwith after we get my box installed. [14:14:50]  mmcgrath: wasn't sure if the wiki would be proper [14:15:08]  <iWolf+ I would have thought the wiki a little too public. [14:15:31]  <ja8sun^ That was my thought as well [14:15:34]  We wouldn't store passwords out there. We also have documentation in the cvs that you guys could look at. [14:15:55]  mmcgrath: what module [14:16:06]  * mmcgrath checking... [14:16:07]  <iWolf+ that may be the best place to store build steps and such as well. [14:16:35]  its under fedora-config [14:16:51]  mmcgrath: thanks, I'll take a look [14:16:52]  there's a kickstart dir that has an "auto-ks" script. [14:17:29]  that auto-ks script is a good starting point to see where to put the kernel, initrd.img and how to setup lilo or grub to boot to the installer (just remember to append vnc to the kernel params) [14:17:42]  anywho, next subject: OTRS. [14:18:02]  If anyone here has reviewer powers in extras please review OTRS for me, I'm still waiting on someone in Extras. [14:18:15]  I'm going to try to put emphasis on it for Sunday's "review day" but we'll see. [14:18:30]  The problem is no one is really familiar with it and people don't tend to like reviewing things they've never used before. [14:18:37]  So thats still on hold. [14:19:08]  The next item is seth's redhat boxes. [14:19:29]  pining skvidal :-) [14:19:57]   ***  skvidal has joined chat #fedora-admin. [14:19:58]   he's comin [14:20:04]   what's up? [14:20:21]   skvidal: we're just going down the list here, I was wondering how the integration is going of your boxes and the other fedora boxes. [14:20:34]   fpserv.linux.duke.edu is integrated [14:20:42]   still waiting on extras64 though? [14:20:49]   fpserv is supposed to replace fedora.linux.duke.edu - we were only waiting on the plan from the website folks [14:21:05]   extras64 was put on hold pending FC5 release [14:21:17]   I didn't think it was wise to mess with it while builds are ongoing [14:21:24]   I thought sopwith and you agreed, too. [14:21:27]   was I mistaken? [14:21:38]   No I think thats good, I misread the notes. [14:21:43]   okie doke [14:21:59]   I would like to have fpserv.linux.duke.edu running sooner than later [14:22:09]   if only b/c fedora.linux.duke.edu is a little aged [14:22:20]  yeah, is fpserv just sitting there now not doing anything? [14:22:22]  fpserv is up and happy - just waiting to know what the hell we have to install on it [14:22:24]   yep [14:22:28]  sitting there looking pretty [14:22:30]  it's on [14:22:32]   you can login [14:22:38]  it occasionally makes annoying cron noises [14:23:00]  <xDamox> heh [14:23:01]  heh. what all needs to be done on it? Anything we can help with? [14:23:12]  I don't have anything to do on it [14:23:29]   I was told that the website folks were still making a decision about cms stuff [14:23:38]  and that we would install whatever they finally settled on [14:23:39]   seems we have a lot machines like that right now. Yeah, last I checked they still don't know. [14:23:46]  ooooookie doke [14:23:50]  so two options [14:24:10]  1. we just migrate things as they are from fedora.linux.duke.edu to fpserv.l.d.e [14:24:18]   2. we continue to wait for the website folks [14:24:41]  I'd say 2. Its working fine as it is right now so there's no immediate need to migrate right? [14:24:48]  <xDamox> I would suggest waiting for the web folks [14:24:53]  yah - we can [14:24:58]  but that has to have an upper limit [14:25:03]  keep in mind [14:25:03]  <xDamox> just incase they bitch about the migration [14:25:12]  fedora.l.d.e is not new [14:25:19]  it's a dual 1ghz with 1gb of ram [14:25:22]  yeah. Maybe we should light a fire under their butts. Who's the main contact over there? [14:25:28]  huzza. [14:25:36]  I thought it was nman64 or maybe quaid [14:25:43]  I thought nman64 too. [14:25:55]  he was here earlier, maybe he'll be back. I'll ask him next time I see him. [14:25:58]  * nman64 awakens. [14:26:08]  there he is. [14:26:34]  nman64: whats the word on the new cms system? [14:26:51]  The Websites team wants to stage Zope+Plone to start testing. [14:27:21]  is it a proof of concept or do you want us to set up a place on the permanent server? [14:27:58]  We simply need a server that is ready for the job and packages built for the correct distribution release. The goal is testing right now. We can put it on a permanent location, but it would be easy to move later. [14:28:36]  well its permanent location currently has nothing on it. So I'd assume if we put it there all we'd have to do before you guys went live is refresh any templates and wipe the database? [14:28:54]  I don't think we'd even have to do that much. [14:29:22]  I'll add it to the schedule. Hopefully we'll get it done soon. skvidal: do you want to do this or should someone else? [14:29:27]  If all goes well, we'd just have to flip the proverbial switch. [14:29:57]  mmcgrath: you can add it to the schedule [14:30:04]  <xDamox> damn got to go Ill post the progress of Pootypedia on the mailing list [14:30:09]  <xDamox> is that ok? [14:30:13]  k, will do. [14:30:18]  sounds good xDamonx [14:30:26]  <xDamox> ok c ya all later [14:30:32]  The rest of the stuff on this list is pretty much where it was last week. [14:30:35]  <xDamox> Ill email by tommorow about pootypedia [14:30:42]  <xDamox> c ya [14:30:47]   monitoring: nagios is ready but we're waiting for lockbox to get ready [14:30:58]  IDWeb: Sopwith is working on that. [14:31:00]  ***  xDamox has left chat #fedora-admin ("Leaving"). [14:31:20]  Metrics, anyone know anything else about metrics and bouncer? [14:31:46]  I have not had much of a chance to work on it [14:31:57]   seems like its been a busy time for everyone. [14:32:10]  emailed mike morgan, but no response [14:32:29]  how much longer should we wait on bouncer before we start looking at other options? [14:32:42]  I also need to email elliot on whether he has talked t mike about the changes [14:32:46]  to bouncer [14:33:20]  ***  Sopwith has joined chat #fedora-admin. [14:33:28]  other then that, not much else to tell.. [14:33:33]  <Sopwith> Sorry guys, just realized I'm very late... [14:33:34]  k sounds good [14:33:38]  sopwith: yooo sopwith! [14:33:44]  sopwith: hey [14:33:52]  <iWolf+ hola. [14:34:04]  we just got to metrics and bouncer [14:34:30]  sopwith: how's IDWeb going? [14:34:34]  <Sopwith> I even had an alarm set, and just dismissed it and went back to hacking for "just a few more minutes" :) [14:34:54]   my alarm stopped working. [14:35:03]   <Sopwith> idweb is going OK. Bill Baronius thinks it is so close to being finished, but I'm not so sure. :) [14:35:23]  heh. [14:35:24]  <Sopwith> idweb is not as high a priority now, for reasons that will hopefully become clear soon. [14:35:39]  mysterious! [14:35:52]  ja8sun anything you need to talk to Sopwith about for bouncer? [14:36:18]  yeah, have you talked with Mike Morgan on the changes to bouncer? [14:36:32]  <Sopwith> Not recently. [14:36:40]  <Sopwith> Did he get back to you about the account? [14:37:01]  <ja8sun^ no, but I was not sure if I had blind-sided him either [14:37:19]  it has been a busy week and I had not followed up with him [14:38:04]  sopwith: Was he cool with us making changes to the code? [14:38:09]  <Sopwith^ OK, I'll try pinging him now. [14:38:17]  <Sopwith> He seemed very enthusiastic about having anyone interested at all. [14:38:28]  sopwith:cool :) [14:39:02]   xDamonx is going to mail to the list with whats going on with pootypedia [14:39:12]   <Sopwith> I just /msg'd morgamic about it and his reply was "I'll look at it right now" [14:39:12]   ssl is still waiting for fp.org [14:39:20]   awesome. [14:39:32]   <Sopwith> Stacy is working on fixing RHN access for the PHX machines [14:39:44]   is PXE all set up now? [14:39:46]   sopwith: wasn't sure on what kind of information he needed from me [14:40:14]   to grant access [14:41:21]   <Sopwith> And you can now mount the netapp to get the install tree directly (instead of going through HTTP on bastion) [14:41:41]   <Sopwith> mmcgrath: No, I'd like RHN set up for that (although I suppose we could install the packages manually) [14:42:00]   Sopwith: sounds like fun [14:42:47]   moving the accounts and cvs is still stalled is it? (item "rhlinux.redhat.com migration") [14:43:42]  <Sopwith> Yup [14:45:23]  whats the word on the translator's compendium? [14:45:36]  <Sopwith> ja8sun: Maybe to get started, you should do an anonymous checkout and that way you'll have the code to hack on as much as you like. [14:45:44]  <Sopwith> morgamic: Just trying to get roadblocks outta your way :) [14:46:10]   <ja8sun^ I have checked out the code, but have not had the time to work with it [14:46:22]   <Sopwith> OK [14:46:26]   <ja8sun^ should have some time this weekend [14:46:30]   <Sopwith> Cool :) [14:46:44]  <Sopwith> It's spring break here next week, so I hope to have a bit more spare time to stick into this stuff [14:47:36]  There's really not much else on the list: account system rewrite. [14:48:01]  I don't think anyone has been doing much work on that though? [14:48:31]  <Sopwith> nope, although someone (was it warren?) mentioned to me the need to allow accounts to list multiple e-mail addresses [14:48:53]  just curious, what for? [14:50:14]  <Sopwith> Mainly because people have been using different e-mail addresses for their bugzilla accounts versus their Fedora accounts [14:50:20]  <Sopwith> And we need to be able to tie the two together. [14:50:28]  got'cha. I'm actually guilty of that. [14:51:35]  Welp thats the schedule's list. Anyone have anything else? [14:52:11]  <Sopwith> Just got a report of cvs-via-ssh not working - trying to fix now [14:52:46]  sopwith: I planted the seed for the next review day and OTRS. We'll see if anyone actually reviews it. [14:52:53]  <Sopwith> xinetd[30413] : FAIL: ssh service_limit from=10.8.34.200 [14:52:53]  <Sopwith> Cool [14:53:14]  <Sopwith> xinetd[30413] : FAIL: ssh service_limit from=10.8.34.200 [14:53:14]  <Sopwith> doh [14:54:00]  more firewall issues? [14:54:23]  I know proxy4 can't resolve dns right now. [14:54:28]  its in the logs too: [14:54:34]  Mar 2 13:47:11 proxy4 sendmail[1808] : k1Q912tF028544: to=admin@fedoraproject.org, ctladdr=<root@proxy4.fedora.phx.redhat.com> (0/0), delay=4+11:46:09, xdelay=00:00:00, mailer=esmtp, pri=9750867, relay=mx3.fedoraproject.org., dsn=4.0.0, stat=Deferred: Connection timed out with mx3.fedoraproject.org. [14:55:19]  Well aside from a few broken systems, I'll close the meeting unless anyone has any objections or anything to add? [14:55:22]  30 seconds. [14:55:38]  15 [14:55:44]   10 [14:55:50]   5 [14:55:51]   4 [14:55:52]   3 [14:55:53]   2 [14:55:53]   1 [14:55:57]   Meeting end.