From dennis at ausil.us Tue Aug 1 05:38:02 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Tue, 1 Aug 2006 00:38:02 -0500 Subject: [Fedora-infrastructure-list] Extras Buildsys Update Message-ID: <200608010038.03674.dennis@ausil.us> Hey Guys, all of the builders are now updated. They all now implement the minimal buildroot as approved by FESCO. So for those maintainers out there that have done nothing about the broken builds by Matt Domsch. You need to fix your packages before we ask everyone to rebuild for FC6 very soon now. -- Dennis Gilmore, RHCE Proud Australian From mmcgrath at fedoraproject.org Thu Aug 3 00:13:41 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 2 Aug 2006 19:13:41 -0500 Subject: [Fedora-infrastructure-list] Shorter meeting? Message-ID: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> Hey guys, so here's the list of current items on the schedule. In an effort to make some shorter meetings, below is the schedule. If you have nothing to report or would like to report it on the list instead of in the meeting, do so. Anything not brought up on the list will be covered at tomorows meeting. Just trying to keep things shorter. minimal buildroot's - DennisGilmore Unifying the web look & feel of infrastructure pieces - PasqualMilvaques Upgrading systems - JeffreyTadlock Firewall system rewrite - LukeMacken Get TurboGears packaged nicely - LukeMacken Documenting infrastructure - Everyone Backups - DennisGilmore Free Servers - MikeMcGrath Metrics - RyanOrdway [:Infrastructure/MirrorManagement: MirrorManagement] - JasonHartley Hardware reporting tool - DamianMyerscough SSL for fedoraproject.org - Infrastructure Team rhlinux.redhat.com migration - BerndGroh Translator's compendium - Infrastructure Team account system rewrite/enhancements - Upgrading systems - JeffreyTadlock Free Servers - MaxSpevack From ryan.ordway at oregonstate.edu Thu Aug 3 16:20:41 2006 From: ryan.ordway at oregonstate.edu (Ryan Ordway) Date: Thu, 03 Aug 2006 09:20:41 -0700 Subject: [Fedora-infrastructure-list] Shorter meeting? In-Reply-To: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> References: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> Message-ID: <1154622042.3229.7.camel@everclear.library.oregonstate.edu> On Wed, 2006-08-02 at 19:13 -0500, Mike McGrath wrote: > Metrics - RyanOrdway Nothing to report yet. -- Ryan Ordway Unix Systems Administrator E-mail: ryan.ordway at oregonstate.edu Oregon State University Libraries rordway at library.oregonstate.edu 121 The Valley Library Corvallis, OR 97331 Desk: 541.737.8972 From damian.myerscough at gmail.com Thu Aug 3 17:00:18 2006 From: damian.myerscough at gmail.com (Damian Myerscough) Date: Thu, 3 Aug 2006 18:00:18 +0100 Subject: [Fedora-infrastructure-list] Shorter meeting? In-Reply-To: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> References: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> Message-ID: <8c9e56490608031000j55fc7ee0r4b92afe5e51a948d@mail.gmail.com> Hardware tracker is still under development On 8/3/06, Mike McGrath wrote: > Hey guys, so here's the list of current items on the schedule. In an > effort to make some shorter meetings, below is the schedule. If you > have nothing to report or would like to report it on the list instead > of in the meeting, do so. Anything not brought up on the list will be > covered at tomorows meeting. Just trying to keep things shorter. > > minimal buildroot's - DennisGilmore > Unifying the web look & feel of infrastructure pieces - PasqualMilvaques > Upgrading systems - JeffreyTadlock > Firewall system rewrite - LukeMacken > Get TurboGears packaged nicely - LukeMacken > Documenting infrastructure - Everyone > Backups - DennisGilmore > Free Servers - MikeMcGrath > Metrics - RyanOrdway > [:Infrastructure/MirrorManagement: MirrorManagement] - JasonHartley > Hardware reporting tool - DamianMyerscough > SSL for fedoraproject.org - Infrastructure Team > rhlinux.redhat.com migration - BerndGroh > Translator's compendium - Infrastructure Team > account system rewrite/enhancements - > Upgrading systems - JeffreyTadlock > Free Servers - MaxSpevack > > _______________________________________________ > Fedora-infrastructure-list mailing list > Fedora-infrastructure-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list > From linux at elfshadow.net Thu Aug 3 17:06:12 2006 From: linux at elfshadow.net (Jeffrey Tadlock) Date: Thu, 03 Aug 2006 13:06:12 -0400 Subject: [Fedora-infrastructure-list] Shorter meeting? In-Reply-To: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> References: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> Message-ID: <44D22D04.40901@elfshadow.net> Mike McGrath wrote: > Upgrading systems - JeffreyTadlock Once the new servers are in-house Curtis and I will be working on getting the db server upgraded. -Jeffrey From lmacken at redhat.com Thu Aug 3 17:14:27 2006 From: lmacken at redhat.com (Luke Macken) Date: Thu, 3 Aug 2006 13:14:27 -0400 Subject: [Fedora-infrastructure-list] Shorter meeting? In-Reply-To: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> References: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> Message-ID: <20060803171427.GA4898@crow.nc.rr.com> On Wed, Aug 02, 2006 at 07:13:41PM -0500, Mike McGrath wrote: > Hey guys, so here's the list of current items on the schedule. In an > effort to make some shorter meetings, below is the schedule. If you > have nothing to report or would like to report it on the list instead > of in the meeting, do so. Anything not brought up on the list will be > covered at tomorows meeting. Just trying to keep things shorter. I'm not positive that I will be able to make it to the meeting today, so here are my updates just in case. > Firewall system rewrite - LukeMacken It looks like pyroman has been deployed on a handful of systems (thanks mmcgrath/dgilmore!). I've added a Deployment and Testing section to InfrastructurePrivate/Firewall with some basic instructions on deploying pyroman and the configuration using dist-conf. I currently don't know how many machines it is running on, so if you do happen to deploy it somewhere, please keep the Deployment Status up to date on the wiki. I'm going to try and find some time this weekend to push it out to more systems. > Get TurboGears packaged nicely - LukeMacken I did a bunch of testing locally with TG 0.9a8 and all of the new deps. Everything seemed to work fine. We're still waiting on the python-{simplejson,paste-{deploy,script}} bugs to make their way through the extras review process. Once those get through, I'll commit my TurboGears changes. I plan on updating bug #189338 with my patch to the TG spec for those who would like to test it out in the mean time. luke From toshio at tiki-lounge.com Thu Aug 3 18:56:40 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Thu, 03 Aug 2006 11:56:40 -0700 Subject: [Fedora-infrastructure-list] Shorter meeting? In-Reply-To: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> References: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> Message-ID: <1154631400.2973.26.camel@localhost> On Wed, 2006-08-02 at 19:13 -0500, Mike McGrath wrote: > Hey guys, so here's the list of current items on the schedule. I've added the new Packaging Version Control System to the list and I'm giving the update here. Mike McGrath has an svn implementation up and I've got a bzr implementation in prototype form. ATM I need access to a machine where I can host the prototype. I'll need the following on the machines: * web server (I've created the prototype using apache so I know how to configure it but other webservers would likely work as well.) * A filesystem mounted with acl support. * About 1.5GB to setup the prototype for HEAD of extras. More than that to setup with historical data for the repository or to include Core as well as Extras. * permission to setup a chroot environment. * sftp+scponly access. * Ability to add users to the system so they can login to the chroot environment via ssh. * root access to change the sshd_config (To place the ssh keys outside of the home directory and enable sftp) and apache config (To work within the repository directory). I'm interested in working on a mercurial implementation too but am currently lacking in time. If someone has time to start putting that together now it would be great otherwise I'll start working on it after I get the bzr implementation to the place where people can feel comfortable understanding what it offers. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Matt_Domsch at dell.com Thu Aug 3 19:47:46 2006 From: Matt_Domsch at dell.com (Matt Domsch) Date: Thu, 3 Aug 2006 14:47:46 -0500 Subject: [Fedora-infrastructure-list] Shorter meeting? In-Reply-To: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> References: <3237e4410608021713r1206db4bv695450142a80c2d9@mail.gmail.com> Message-ID: <20060803194746.GA11367@lists.us.dell.com> On Wed, Aug 02, 2006 at 07:13:41PM -0500, Mike McGrath wrote: > Free Servers - MikeMcGrath > Free Servers - MaxSpevack Hi folks. I have to apologize, there was a last-minute change of my budget (surprise!). There will be at least 1 PE1950 coming your way, maybe more, but the 2 PE2950s won't. While a 1950 can make a fine database server, you may want to look for other hardware if you think the demands would be more than that. Sorry about that. Next time I'll keep my mouth shut until after the units ship out the door. :-) Thanks to Mike who took the time to help config up the 2950s. Thanks, Matt -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com From rassylkaformazaj at ukr.net Thu Aug 3 22:28:46 2006 From: rassylkaformazaj at ukr.net (rassylkaformazaj at ukr.net) Date: Fri, 4 Aug 2006 01:28:46 +0300 Subject: [Fedora-infrastructure-list] Hello. Message-ID: <1783402101.20060804012846@ukr.net> Hello, everybody! About 3 weeks ago I saw this: > Looking for a few good women (and men) > > Elliot Lee announces in fedora-announce-list: > > The Fedora Infrastructure and Administration Project is looking for > people who want to help create & maintain infrastructure that will > take Fedora to the next level. If you're willing to help regularly in > your spare time, and think you have some skills to lend (web app > coders especially wanted), please see > http://fedoraproject.org/wiki/Infrastructure, or e-mail > > if you have any questions. I am very interested to be involved with fedora project, because I like this system, and use it for long. 2 words about me: I am system administrator with more then 5 years experience, that uses Fedora since FC1 (actually I started with RedHat8). I have couple hours everyday and great will to help you in your infrastructure. Please guide me how can I start helping you, I can do many things that is concerned to system administration, although I am not very good programmer in Perl, Python or other. Yes I can script and automate my tasks, but i wouldn't call myself 'good'. Feel free to ask me to help to do your task, or any other. I want somehow to start ;) Thanks. p.s. Call me mazaj ;) (pronounced like [mazaj], last letter pronounced not like [dzhei], but like short [j] ) From gauret at free.fr Fri Aug 4 10:02:54 2006 From: gauret at free.fr (Aurelien Bompard) Date: Fri, 4 Aug 2006 12:02:54 +0200 Subject: [Fedora-infrastructure-list] IANA number for Fedora Message-ID: <200608041202.54707.gauret@free.fr> Hello *, For the new LDAP schema, we'll need to add attributes to the standard ones, and to do so cleanly we need an OID for Fedora. Do we already have one ? If we don't we can get one for free here : http://www.iana.org/cgi-bin/enterprise.pl The OID is usually attributed and sent by email within 2 weeks. Aur?lien -- http://aurelien.bompard.org ~~~~ Jabber : abompard at jabber.fr "Make everything as simple as possible, but not simpler." -- Albert Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From toshio at tiki-lounge.com Fri Aug 4 16:05:34 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Fri, 04 Aug 2006 09:05:34 -0700 Subject: [Fedora-infrastructure-list] Package Version Control Scripts Message-ID: <1154707534.4373.35.camel@localhost> Following up on what was discussed in the meeting and the list of requirements from the previous email, here are the scripts I'm currently working on to setup the bzr repository. * scponly-repo.sh: This is the first script to run. It sets up the chroot environment. A portion of this script should be made into a cron job that periodically refreshes the programs and libraries within the chroot (to limit the time that the chroot is vulnerable to exploits.) - A portion of this script needs to be run by root. - This script labels files for SELinux. If SELinux is not enabled on the server this lands on we'll want to comment that out. - A portion of the script sets up a passwd and group file within the chroot. I suspect that this is not necessary. * setup-repo.sh: This script imports one of the cvs-seed tarballs from cvs.fedora.redhat.com into the new repository. It sets up a sample within the embargo directory as well. * repo.conf: Apache configuration file to enable access to the repo over http. Note that this allows bzr to access the repository over ssh. It is not a web-front end. There is a separate cgi script which I haven't yet worked with that can be used for that. * user.sh: Sets up one user with an account on the system; adding them to appropriate groups and etc. This is incomplete until I tie it into the accounts system to retrieve the ssh key. In the future, user information should be created by the accountsdb. * user-setup.sh: This script sets up default groups (vcsuser and security) that are used by the acls. It also creates a vcsguest account that allows anonymous logins. After implementing http retrieval on my test machine, I don't think this is necessary any longer. Anonymous access can use http to retrieve public information. Read-write access and access to private information will go through sftp. * sshd_config: Replacement sshd configuration. Changes: - AuthorizedKeysFile is changed to explicitly reference /home/%u instead of the user's home directory. This is so vcusers have their keys extracted from /home/%u instead of their home directory (which is within the chroot). vcsusers do not have access to change ssh keys on the server, this has to be done through the accounts db. - PermitEmptyPasswords, PasswordAuthentication: This is to enable anonymous ssh login to the chroot. Since anonymous access is going to happen over http, this should no longer be necessary. - Subsystem sftp: enabled sftp for bzr. Everything is a work in progress but my main thrust right now is creating good ACLs and testing what the limitations are. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: setup-repo.sh Type: application/x-shellscript Size: 2725 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: setup-repo.sh Type: application/x-shellscript Size: 2725 bytes Desc: not available URL: -------------- next part -------------- AliasMatch ^/repos(/.*)?$ "/pkgs/bzr/chroot/pkgs$1" Options Indexes AllowOverride None Order allow,deny Allow from all -------------- next part -------------- A non-text attachment was scrubbed... Name: user.sh Type: application/x-shellscript Size: 667 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: user-setup.sh Type: application/x-shellscript Size: 595 bytes Desc: not available URL: -------------- next part -------------- # $OpenBSD: sshd_config,v 1.72 2005/07/25 11:59:40 markus Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options change a # default value. #Port 22 #Protocol 2,1 Protocol 2 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: # HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_dsa_key # Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 1h #ServerKeyBits 768 # Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH SyslogFacility AUTHPRIV #LogLevel INFO # Authentication: #LoginGraceTime 2m PermitRootLogin no #StrictModes yes #MaxAuthTries 6 #RSAAuthentication yes #PubkeyAuthentication yes AuthorizedKeysFile /home/%u/.ssh/authorized_keys # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #RhostsRSAAuthentication no # similar for protocol version 2 #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # RhostsRSAAuthentication and HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes PermitEmptyPasswords yes PasswordAuthentication yes # Change to no to disable s/key passwords #ChallengeResponseAuthentication yes ChallengeResponseAuthentication no # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no GSSAPIAuthentication yes #GSSAPICleanupCredentials yes GSSAPICleanupCredentials yes # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication mechanism. # Depending on your PAM configuration, this may bypass the setting of # PasswordAuthentication, PermitEmptyPasswords, and # "PermitRootLogin without-password". If you just want the PAM account and # session checks to run without PAM authentication, then enable this but set # ChallengeResponseAuthentication=no #UsePAM no UsePAM yes #AllowTcpForwarding yes #GatewayPorts no #X11Forwarding no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PrintMotd yes #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #UsePrivilegeSeparation yes #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS yes #PidFile /var/run/sshd.pid #MaxStartups 10 #ShowPatchLevel no # no default banner path #Banner /some/path # override default of no subsystems Subsystem sftp /usr/libexec/openssh/sftp-server -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From skvidal at linux.duke.edu Sat Aug 5 21:50:09 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Sat, 05 Aug 2006 17:50:09 -0400 Subject: [Fedora-infrastructure-list] fpserv, extras64 saturday around noon (EDT) Message-ID: <1154814609.3092.7.camel@cutter> Hey, Today around noon fpserv and extras64 went off line due to a power event in the room where they are racked. The UPS for that room appeared to have smoked itself so we had an exciting day at duke. Things are back online now but we may require another downtime when the new ups comes online. I'll let everyone know what I hear. Thanks, -sv From pasqual.milvaques at gmail.com Mon Aug 7 14:53:16 2006 From: pasqual.milvaques at gmail.com (Pasqual Milvaques) Date: Mon, 7 Aug 2006 16:53:16 +0200 Subject: [Fedora-infrastructure-list] Hello. In-Reply-To: <1783402101.20060804012846@ukr.net> References: <1783402101.20060804012846@ukr.net> Message-ID: hi mazaj thanks for your interest. if you want to learn how you can help the fedora project and start being involved I suggest you to start assisting to the regular irc meetings. the meetings happen on Thursdays at 20:00 (utc time), here you can find more information: http://fedoraproject.org/wiki/Infrastructure/Meetings I suggest you to take a look to the main infrastructure wiki page here: http://fedoraproject.org/wiki/Infrastructure specially to the schedule. you can also subscribe to the mailing list here: http://www.redhat.com/mailman/listinfo/fedora-infrastructure-list on the meetings you will know the people already involved and you will take a more deep knowledge about how you can help kind regards pasqual 2006/8/4, rassylkaformazaj at ukr.net : > > Hello, everybody! > > About 3 weeks ago I saw this: > > > Looking for a few good women (and men) > > > > Elliot Lee announces in fedora-announce-list: > > > > The Fedora Infrastructure and Administration Project is looking for > > people who want to help create & maintain infrastructure that will > > take Fedora to the next level. If you're willing to help regularly in > > your spare time, and think you have some skills to lend (web app > > coders especially wanted), please see > > http://fedoraproject.org/wiki/Infrastructure, or e-mail > > > > if you have any questions. > > I am very interested to be involved with fedora project, because I like > this system, and use it for long. > > 2 words about me: > > I am system administrator with more then 5 years experience, that uses > Fedora since FC1 (actually I started with RedHat8). I have couple > hours everyday and great will to help you in your infrastructure. > > Please guide me how can I start helping you, I can do many things that > is concerned to system administration, although I am not very good > programmer in Perl, Python or other. Yes I can script and automate my > tasks, but i wouldn't call myself 'good'. > > Feel free to ask me to help to do your task, or any other. I want > somehow to start ;) > > Thanks. > > p.s. Call me mazaj ;) (pronounced like [mazaj], last letter pronounced > not like [dzhei], but like short [j] ) > > > _______________________________________________ > Fedora-infrastructure-list mailing list > Fedora-infrastructure-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmcgrath at fedoraproject.org Wed Aug 9 03:09:18 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Tue, 8 Aug 2006 22:09:18 -0500 Subject: [Fedora-infrastructure-list] Legacy CVS FC-4 branch created Message-ID: <3237e4410608082009h2e6a7795k9bd6592e45b575f4@mail.gmail.com> The FC-4 Branch for legacy has been created. /cvs/legacy/ I still haven't completely automated this branch creation process but I'm close. I'll defaintly be able to automate it for FC-5 when it goes to legacy. The lookaside cache should be done by the end of the night, I'll send a follow up when it is. -Mike From jkeating at redhat.com Wed Aug 9 03:10:55 2006 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 8 Aug 2006 23:10:55 -0400 Subject: [Fedora-infrastructure-list] Re: Legacy CVS FC-4 branch created In-Reply-To: <3237e4410608082009h2e6a7795k9bd6592e45b575f4@mail.gmail.com> References: <3237e4410608082009h2e6a7795k9bd6592e45b575f4@mail.gmail.com> Message-ID: <200608082310.59180.jkeating@redhat.com> On Tuesday 08 August 2006 23:09, Mike McGrath wrote: > /cvs/legacy/ > > I still haven't completely automated this branch creation process but > I'm close. ?I'll defaintly be able to automate it for FC-5 when it > goes to legacy. ?The lookaside cache should be done by the end of the > night, I'll send a follow up when it is. Rock! -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mmcgrath at fedoraproject.org Wed Aug 9 05:08:57 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 9 Aug 2006 00:08:57 -0500 Subject: [Fedora-infrastructure-list] Re: Legacy CVS FC-4 branch created In-Reply-To: <200608082310.59180.jkeating@redhat.com> References: <3237e4410608082009h2e6a7795k9bd6592e45b575f4@mail.gmail.com> <200608082310.59180.jkeating@redhat.com> Message-ID: <3237e4410608082208l7ed657f6o567387a22a01583b@mail.gmail.com> On 8/8/06, Jesse Keating wrote: > On Tuesday 08 August 2006 23:09, Mike McGrath wrote: > > /cvs/legacy/ > > > > I still haven't completely automated this branch creation process but > > I'm close. I'll defaintly be able to automate it for FC-5 when it > > goes to legacy. The lookaside cache should be done by the end of the > > night, I'll send a follow up when it is. Follow up: look-aside cache for FC-4 legacy is done, presently FC-[3-4] look-aside cache is 6.4G. Jesse, let me know if anything is broken. Also as per our discussion on IRC, let me know when that other SRPM is available. -Mike From gauret at free.fr Wed Aug 9 13:09:52 2006 From: gauret at free.fr (Aurelien Bompard) Date: Wed, 9 Aug 2006 15:09:52 +0200 Subject: [Fedora-infrastructure-list] LDAP Schema Proposal Message-ID: <200608091509.58481.gauret@free.fr> Hey admins, I've been thinking about a possible LDAP schema for the new Account System, I've discussed it with Lyz and we agree it should be able to do the job. I'd like to discuss it with you now. Here's a description of this new schema : http://fedoraproject.org/wiki/Infrastructure/AccountSystem2/Schema#head-5061a68a5fd14fa1666b4170abf6f96d850eaea4 I have not described the additions to the inetOrgPerson yet, because they are minor. I'd like to validate the groups system with you first. Opinions ? Aur?lien -- http://aurelien.bompard.org ~~~~ Jabber : abompard at jabber.fr No, I coded it crappily on purpose, just so that I could say: "There's plenty of room for optimization." -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mmcgrath at fedoraproject.org Wed Aug 9 15:32:10 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 9 Aug 2006 10:32:10 -0500 Subject: [Fedora-infrastructure-list] LDAP Schema Proposal In-Reply-To: <200608091509.58481.gauret@free.fr> References: <200608091509.58481.gauret@free.fr> Message-ID: <3237e4410608090832g635ad63cy37b8de8a3d4ca61e@mail.gmail.com> On 8/9/06, Aurelien Bompard wrote: > Hey admins, > > I've been thinking about a possible LDAP schema for the new Account System, > I've discussed it with Lyz and we agree it should be able to do the job. > I'd like to discuss it with you now. > > Here's a description of this new schema : > http://fedoraproject.org/wiki/Infrastructure/AccountSystem2/Schema#head-5061a68a5fd14fa1666b4170abf6f96d850eaea4 > > I have not described the additions to the inetOrgPerson yet, because they > are minor. I'd like to validate the groups system with you first. > > Opinions ? > > Aur?lien This looks good. One thing that was brought up at the last meeting is to find some sort of good ldap guide for programmers. I've been looking for one but have as of yet come up with exactly what I'm looking for. I think it might ease some anxiety we're having about using LDAP. Also, under the allowed attributes, are we allowed to have multiples of these attributes? For example, could I have multiple pgp keys, managers, and employee types? I was thinking some of those could be used to set up dynamic groups during implementation. -Mike From gauret at free.fr Wed Aug 9 20:04:42 2006 From: gauret at free.fr (Aurelien Bompard) Date: Wed, 9 Aug 2006 22:04:42 +0200 Subject: [Fedora-infrastructure-list] LDAP Schema Proposal In-Reply-To: <3237e4410608090832g635ad63cy37b8de8a3d4ca61e@mail.gmail.com> References: <200608091509.58481.gauret@free.fr> <3237e4410608090832g635ad63cy37b8de8a3d4ca61e@mail.gmail.com> Message-ID: <200608092204.51047.gauret@free.fr> > This looks good. Thanks > One thing that was brought up at the last meeting is > to find some sort of good ldap guide for programmers. I've been > looking for one but have as of yet come up with exactly what I'm > looking for. I think it might ease some anxiety we're having about > using LDAP. There is some doc for python here : http://python-ldap.sourceforge.net/docs.shtml > Also, under the allowed attributes, are we allowed to have multiples > of these attributes? For example, could I have multiple pgp keys, > managers, and employee types? I was thinking some of those could be > used to set up dynamic groups during implementation. By default the attributes may contain multiple values. It can be specified otherwise in the schema if needed, but it's the common case. Aur?lien -- http://aurelien.bompard.org ~~~~ Jabber : abompard at jabber.fr No, I coded it crappily on purpose, just so that I could say: "There's plenty of room for optimization." -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From toshio at tiki-lounge.com Wed Aug 9 20:36:30 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Wed, 09 Aug 2006 13:36:30 -0700 Subject: [Fedora-infrastructure-list] LDAP Schema Proposal In-Reply-To: <200608092204.51047.gauret@free.fr> References: <200608091509.58481.gauret@free.fr> <3237e4410608090832g635ad63cy37b8de8a3d4ca61e@mail.gmail.com> <200608092204.51047.gauret@free.fr> Message-ID: <1155155790.3027.103.camel@localhost> On Wed, 2006-08-09 at 22:04 +0200, Aurelien Bompard wrote: > > One thing that was brought up at the last meeting is > > to find some sort of good ldap guide for programmers. I've been > > looking for one but have as of yet come up with exactly what I'm > > looking for. I think it might ease some anxiety we're having about > > using LDAP. > > There is some doc for python here : > http://python-ldap.sourceforge.net/docs.shtml Everything I look at has information on querying but nothing on schema creation and design. I'm beginning to think that LDAP is nothing like SQL :-) Are these accurate: Where SQL lets you associate pieces of data as the whim strikes you, LDAP has predetermined what pieces of data are relevant to each other. Your queries in LDAP are selecting these predetermined pieces of data which you then filter or make new queries to get more data. There is no query language in LDAP. Instead you have a set function interface that let's you interact with the server. What's the answer to these: Are there keys in LDAP? Are there constraints (Entries into this field must be digits. Entries into that field must be dates. Entries into this field must follow this regexp)? Can you search by regexp? Does this depend on the LDAP server? If there is no query language in LDAP, then that's probably a big reason why SQL people don't understand LDAP. Even now, I'm trying to wrap my brain around the concept of a database without a query language but my gut just doesn't understand how that could be. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From gauret at free.fr Wed Aug 9 21:29:59 2006 From: gauret at free.fr (Aurelien Bompard) Date: Wed, 9 Aug 2006 23:29:59 +0200 Subject: [Fedora-infrastructure-list] LDAP Schema Proposal In-Reply-To: <1155155790.3027.103.camel@localhost> References: <200608091509.58481.gauret@free.fr> <200608092204.51047.gauret@free.fr> <1155155790.3027.103.camel@localhost> Message-ID: <200608092329.59990.gauret@free.fr> > > There is some doc for python here : > > http://python-ldap.sourceforge.net/docs.shtml > > Everything I look at has information on querying but nothing on schema > creation and design. True, schema creation and design is not really programming. Here's some good links about it: http://www.ldapman.org/ http://www.skills-1st.co.uk/papers/ldap-schema-design-feb-2005/ldap-schema-design-feb-2005.html http://yolinux.com/TUTORIALS/LinuxTutorialLDAP-DefineObjectsAndAttributes.html ftp://ftp.isi.edu/in-notes/rfc2252.txt > I'm beginning to think that LDAP is nothing like > SQL :-) Yep, it's very different indeed. > Are these accurate: > > Where SQL lets you associate pieces of data as the whim strikes you, > LDAP has predetermined what pieces of data are relevant to each other. > Your queries in LDAP are selecting these predetermined pieces of data > which you then filter or make new queries to get more data. Yes, AFAICT. > There is no query language in LDAP. Instead you have a set function > interface that let's you interact with the server. No, there is a query language, which is more of a query syntax actually. For example: - In SQL: SELECT uid FROM fedoraMembership WHERE cn = 'group1' - In LDAP : (&(objectClass=fedoraMembership)(cn=group1)) selecting only the uid attribute is not part of this syntax but it is always possible. > Are there keys in LDAP? There can be mandatory attributes in your schema (for example you uid is mandatory, but not your phone number) You can define indexes to maintain in the config file to speed up your searches. > Are there constraints (Entries into this field must be digits. Entries > into that field must be dates. Entries into this field must follow this > regexp)? Yes. You can also define how it should match in a search (case-sensitive, space-sensitive, anything). See http://ldap.akbkhome.com and http://www.openldap.org/doc/admin23/schema.html#Attribute%20Type%20Specification > Can you search by regexp? Does this depend on the LDAP server? No, searching depends on the type of match defined for your attribute. > If there is no query language in LDAP, then that's probably a big reason > why SQL people don't understand LDAP. Even now, I'm trying to wrap my > brain around the concept of a database without a query language but my > gut just doesn't understand how that could be. There is a query syntax. Keep in mind that LDAP is a tree. To search you need 4 things : - the starting point (a branch or the top of the tree) - the scope : only this entry (called "one"), the items right under this entry (called "base"), or all the subtree (call "sub") - the list of attributes you want to retrieve from the entries you've found - the search string itself : you search for entries having attributes matching your search. Examples : - (uid=toshio) : search for all entries with the uid attribute matching "toshio" - (&(sn=Kuratomi)(mail=*@tiki-lounge.com)) : search for all entries with the sn (SurName) attribute matching Kuratomi, and the mail attribute ending in @tiki-lounge.com. - and it could get more complicated when you add AND and OR requests. There are two other things that are non-obvious to SQL people : - any entry can have a sub-entry. No concept of file != folder. - unless specified otherwise, every attribute can have multiple values. I'm probably skipping many other specificities, but I hope it clears up the concept. If you have more questions, feel free to ask, I'm sure there's plenty of hardcore SQLers out there :) Aur?lien -- http://aurelien.bompard.org ~~~~ Jabber : abompard at jabber.fr The only "intuitive" interface is the nipple. After that it's all learned. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From skvidal at linux.duke.edu Thu Aug 10 11:52:11 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Thu, 10 Aug 2006 07:52:11 -0400 Subject: [Fedora-infrastructure-list] backups Message-ID: <1155210731.11572.69.camel@cutter> Hi Folks, whats the status of getting the backups online? Is it ready to go, yet? I'm backing up fpserv and extras64 using rdiff-backup right now to a server I have here but it's not accessible to all the infrastructure folks and I'd like to not be the only guy who can get to it for the future so the backups on lockbox would make sense. thanks, -sv From jason at 3dogs.us Fri Aug 11 01:12:32 2006 From: jason at 3dogs.us (Jason Hartley) Date: Thu, 10 Aug 2006 21:12:32 -0400 (EDT) Subject: [Fedora-infrastructure-list] Today's Meeting Message-ID: <45236.192.168.0.10.1155258752.squirrel@www.3dogs.us> I just wanted to send my apologies for missing today's meeting. Currently, I have work related meetings that back up to the Fedora Admin meeting. So, it is going to be hit and miss on my attendance for a while. Also, I have been disengaged for the past month, and I have been trying to keep up with what is going on through the list and weekly meetings. A number of home projects have taken their toll on my time. I am hoping in the near future to become more active. In the meantime I just wanted to make sure everyone knew I was still around. Best Regards, Jason Hartley From mmcgrath at fedoraproject.org Fri Aug 11 23:19:42 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Fri, 11 Aug 2006 18:19:42 -0500 Subject: [Fedora-infrastructure-list] Package Version Control Scripts In-Reply-To: <1154707534.4373.35.camel@localhost> References: <1154707534.4373.35.camel@localhost> Message-ID: <3237e4410608111619j4ba7ebd8r6eac3bc9a6da75a5@mail.gmail.com> On 8/4/06, Toshio Kuratomi wrote: > Following up on what was discussed in the meeting and the list of > requirements from the previous email, here are the scripts I'm currently > working on to setup the bzr repository. > > * scponly-repo.sh: This is the first script to run. It sets up the > chroot environment. A portion of this script should be made into a cron > job that periodically refreshes the programs and libraries within the > chroot (to limit the time that the chroot is vulnerable to exploits.) > - A portion of this script needs to be run by root. > - This script labels files for SELinux. If SELinux is not enabled on > the server this lands on we'll want to comment that out. > - A portion of the script sets up a passwd and group file within the > chroot. I suspect that this is not necessary. > > * setup-repo.sh: This script imports one of the cvs-seed tarballs from > cvs.fedora.redhat.com into the new repository. It sets up a sample > within the embargo directory as well. > > * repo.conf: Apache configuration file to enable access to the repo over > http. Note that this allows bzr to access the repository over ssh. It > is not a web-front end. There is a separate cgi script which I haven't > yet worked with that can be used for that. > > * user.sh: Sets up one user with an account on the system; adding them > to appropriate groups and etc. This is incomplete until I tie it into > the accounts system to retrieve the ssh key. In the future, user > information should be created by the accountsdb. > > * user-setup.sh: This script sets up default groups (vcsuser and > security) that are used by the acls. It also creates a vcsguest account > that allows anonymous logins. After implementing http retrieval on my > test machine, I don't think this is necessary any longer. Anonymous > access can use http to retrieve public information. Read-write access > and access to private information will go through sftp. > > * sshd_config: Replacement sshd configuration. Changes: > - AuthorizedKeysFile is changed to explicitly reference /home/%u > instead of the user's home directory. This is so vcusers have their > keys extracted from /home/%u instead of their home directory (which is > within the chroot). vcsusers do not have access to change ssh keys on > the server, this has to be done through the accounts db. > - PermitEmptyPasswords, PasswordAuthentication: This is to enable > anonymous ssh login to the chroot. Since anonymous access is going to > happen over http, this should no longer be necessary. > - Subsystem sftp: enabled sftp for bzr. > > Everything is a work in progress but my main thrust right now is > creating good ACLs and testing what the limitations are. > > -Toshio Hey Toshio, I'm going to have some free time to set this up soon, I seem to remember you mentioning you had updated scripts. If they happen to be ready now send them to the list and I'll get them started. -Mike From toshio at tiki-lounge.com Fri Aug 11 23:40:39 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Fri, 11 Aug 2006 16:40:39 -0700 Subject: [Fedora-infrastructure-list] Package Version Control Scripts In-Reply-To: <3237e4410608111619j4ba7ebd8r6eac3bc9a6da75a5@mail.gmail.com> References: <1154707534.4373.35.camel@localhost> <3237e4410608111619j4ba7ebd8r6eac3bc9a6da75a5@mail.gmail.com> Message-ID: <1155339640.2646.43.camel@localhost> On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote: > Hey Toshio, I'm going to have some free time to set this up soon, I > seem to remember you mentioning you had updated scripts. If they > happen to be ready now send them to the list and I'll get them > started. > Hey Mike, Tarball here: http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz or checkout from bzr: bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/ When do you think you'll be starting so I can be around a computer as well? -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mmcgrath at fedoraproject.org Sat Aug 12 02:50:34 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Fri, 11 Aug 2006 21:50:34 -0500 Subject: [Fedora-infrastructure-list] Package Version Control Scripts In-Reply-To: <1155339640.2646.43.camel@localhost> References: <1154707534.4373.35.camel@localhost> <3237e4410608111619j4ba7ebd8r6eac3bc9a6da75a5@mail.gmail.com> <1155339640.2646.43.camel@localhost> Message-ID: <3237e4410608111950t61f2e561vb0ccd1dbc8b703d0@mail.gmail.com> On 8/11/06, Toshio Kuratomi wrote: > On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote: > > Hey Toshio, I'm going to have some free time to set this up soon, I > > seem to remember you mentioning you had updated scripts. If they > > happen to be ready now send them to the list and I'll get them > > started. > > > Hey Mike, > > Tarball here: > http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz > > or checkout from bzr: > bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/ We've hit a snag. While building bzr for RHEL4 it bombs with a message stating that it requires python 2.4, presently python-2.3.4-14.2 is installed. Suggestions on how to proceed from here? -Mike From dennis at ausil.us Sat Aug 12 03:02:31 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Fri, 11 Aug 2006 22:02:31 -0500 Subject: [Fedora-infrastructure-list] Package Version Control Scripts In-Reply-To: <3237e4410608111950t61f2e561vb0ccd1dbc8b703d0@mail.gmail.com> References: <1154707534.4373.35.camel@localhost> <1155339640.2646.43.camel@localhost> <3237e4410608111950t61f2e561vb0ccd1dbc8b703d0@mail.gmail.com> Message-ID: <200608112202.31922.dennis@ausil.us> On Friday 11 August 2006 9:50 pm, Mike McGrath wrote: > On 8/11/06, Toshio Kuratomi wrote: > > On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote: > > > Hey Toshio, I'm going to have some free time to set this up soon, I > > > seem to remember you mentioning you had updated scripts. If they > > > happen to be ready now send them to the list and I'll get them > > > started. > > > > Hey Mike, > > > > Tarball here: > > http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz > > > > or checkout from bzr: > > bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/ > > We've hit a snag. While building bzr for RHEL4 it bombs with a > message stating that it requires python 2.4, presently > python-2.3.4-14.2 is installed. Suggestions on how to proceed from > here? Backport to python2.3, package python 2.4 in such a way as it is parallel installable with 2.3 ( there is to many things linked to the version of python that is in a distro to upgrade it to 2.4, or use FC5 -- Dennis Gilmore, RHCE Proud Australian From skvidal at linux.duke.edu Sat Aug 12 03:29:44 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Fri, 11 Aug 2006 23:29:44 -0400 Subject: [Fedora-infrastructure-list] Package Version Control Scripts In-Reply-To: <200608112202.31922.dennis@ausil.us> References: <1154707534.4373.35.camel@localhost> <1155339640.2646.43.camel@localhost> <3237e4410608111950t61f2e561vb0ccd1dbc8b703d0@mail.gmail.com> <200608112202.31922.dennis@ausil.us> Message-ID: <1155353384.21416.2.camel@cutter> On Fri, 2006-08-11 at 22:02 -0500, Dennis Gilmore wrote: > On Friday 11 August 2006 9:50 pm, Mike McGrath wrote: > > On 8/11/06, Toshio Kuratomi wrote: > > > On Fri, 2006-08-11 at 18:19 -0500, Mike McGrath wrote: > > > > Hey Toshio, I'm going to have some free time to set this up soon, I > > > > seem to remember you mentioning you had updated scripts. If they > > > > happen to be ready now send them to the list and I'll get them > > > > started. > > > > > > Hey Mike, > > > > > > Tarball here: > > > http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs-0.1.tar.gz > > > > > > or checkout from bzr: > > > bzr branch http://www.tiki-lounge.com/~toshio/fedora/fedora-vcs/ > > > > We've hit a snag. While building bzr for RHEL4 it bombs with a > > message stating that it requires python 2.4, presently > > python-2.3.4-14.2 is installed. Suggestions on how to proceed from > > here? > Backport to python2.3, package python 2.4 in such a way as it is parallel > installable with 2.3 ( there is to many things linked to the version of > python that is in a distro to upgrade it to 2.4, or use FC5 if this is for the primary bzr server let's not use fc5 for it. We need to be able to keep it up for a long-ish time. -sv From dennis at ausil.us Sat Aug 12 03:32:13 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Fri, 11 Aug 2006 22:32:13 -0500 Subject: [Fedora-infrastructure-list] Package Version Control Scripts In-Reply-To: <1155353384.21416.2.camel@cutter> References: <1154707534.4373.35.camel@localhost> <200608112202.31922.dennis@ausil.us> <1155353384.21416.2.camel@cutter> Message-ID: <200608112232.14536.dennis@ausil.us> On Friday 11 August 2006 10:29 pm, seth vidal wrote: > On Fri, 2006-08-11 at 22:02 -0500, Dennis Gilmore wrote: > > > > Backport to python2.3, package python 2.4 in such a way as it is > > parallel installable with 2.3 ( there is to many things linked to the > > version of python that is in a distro to upgrade it to 2.4, or use FC5 > > if this is for the primary bzr server let's not use fc5 for it. We need > to be able to keep it up for a long-ish time. thats my inclination also. it will take more work but porting bzr to python 2.3 or making a parallel installable 2.4 would be best options. Just throwing out there what i see as the possible options, I didint say they were good ideas :D -- Dennis Gilmore, RHCE Proud Australian From mmcgrath at fedoraproject.org Sat Aug 12 03:32:58 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Fri, 11 Aug 2006 22:32:58 -0500 Subject: [Fedora-infrastructure-list] Package Version Control Scripts In-Reply-To: <1155353384.21416.2.camel@cutter> References: <1154707534.4373.35.camel@localhost> <1155339640.2646.43.camel@localhost> <3237e4410608111950t61f2e561vb0ccd1dbc8b703d0@mail.gmail.com> <200608112202.31922.dennis@ausil.us> <1155353384.21416.2.camel@cutter> Message-ID: <3237e4410608112032p11b6b323t157a6b3d052d0634@mail.gmail.com> On 8/11/06, seth vidal wrote: > > if this is for the primary bzr server let's not use fc5 for it. We need > to be able to keep it up for a long-ish time. > > -sv > As of right now its just as a prototype. We've got the SVN server up and running. Long term we could use RHEL5(ish) when it comes out but it would be nice to get this up for the dev's and us to test so see what they think and see what it can do. -Mike From pasqual.milvaques at gmail.com Sat Aug 12 17:32:31 2006 From: pasqual.milvaques at gmail.com (Pasqual Milvaques) Date: Sat, 12 Aug 2006 19:32:31 +0200 Subject: [Fedora-infrastructure-list] Re: presentation and draft of page https://admin.fedoraproject.org/ In-Reply-To: <44B92A3E.90306@gmail.com> References: <44B92A3E.90306@gmail.com> Message-ID: hi there has been some changes in my work and for some time I will not have time available for continuing with the job I had assigned in the project. I have updated the schedule to reflect it. perhaps when I would have time again I will contact you again kind regards pasqual 2006/7/15, pasqual milvaques : > > hi people > > my name is pasqual milvaques, I'm a spanish dba and software developer > and I'm going to try to give a hand to you in creating a homepage for > the fedora infrastructure project and in other things I can help. > > I have created a draft for the page which I send attached with this > mail. The idea is to have in this page a list of all infrastructure > pieces which are being used with their links and some basic information. > the draft has not all the links, I will review it to add more links that > I have seen in the fedora infrastructure mailing list and (of course) > any link you indicate to me. In the next days I will review it and will > take deeper look to the wiki to search for more information (all this > system is bigger than I expected) and to define the work methodology. > > well, take a look to the draft as in it you will find some of my doubts > (what is docs-rawhide? where is nagios?) and make me any comments you > find relevant > > regards and will be in contact > > pasqual > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmcgrath at fedoraproject.org Sat Aug 12 22:45:41 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Sat, 12 Aug 2006 17:45:41 -0500 Subject: [Fedora-infrastructure-list] Test LDAP instance Message-ID: <3237e4410608121545g7cec0094v5bedd817ef0c4ce9@mail.gmail.com> Ok, I have a virgin install of FDS up and running on bastion. It's actually running under its own dir in my home directory so we can move it around/back it up as needed. Connection info is fairly simple. Since this is just a test I figure no need to request firewall changes. SSH should be able to take care of it. Step 1: From mmcgrath at fedoraproject.org Sat Aug 12 22:58:35 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Sat, 12 Aug 2006 17:58:35 -0500 Subject: [Fedora-infrastructure-list] Re: Test LDAP instance In-Reply-To: <3237e4410608121545g7cec0094v5bedd817ef0c4ce9@mail.gmail.com> References: <3237e4410608121545g7cec0094v5bedd817ef0c4ce9@mail.gmail.com> Message-ID: <3237e4410608121558m5c025bd8o75a8875a16009335@mail.gmail.com> On 8/12/06, Mike McGrath wrote: > Ok, I have a virgin install of FDS up and running on bastion. It's > actually running under its own dir in my home directory so we can move > it around/back it up as needed. Connection info is fairly simple. > Since this is just a test I figure no need to request firewall > changes. SSH should be able to take care of it. > Stupid send button right next to the save button Step 1: Install sun's java. I've been testing with jre1.5.0_08. Step 2: Install fedora's directory server on your workstation (for the admin console) Step 3: add "bastion.fedora.phx.redhat.com" to your /etc/hosts file for 127.0.0.1 Step 4: Create the ssh tunnel: ssh -L 18739:bastion:18739 -L 17388:bastion:17388 -N bastion.fedora.redhat.com LDAP port - 18739 Admin port (HTTP) - 17388 Step 5: Test the admin port by pointing your browser to http://localhost:17388/ Step 6: Start the console: cd /opt/fedora-ds/ ./startconsole -u admin -a http://localhost:17388/ contact me for a username and password. Don't make any changes wihout consulting lyz or abompard, this their instance to play with. lyz and abompard, I need to get you setup with shell access for bastion, contact me for more info. -Mike -Mike Don't make any changes without running it by lyz or abompard. From jkeating at redhat.com Sat Aug 12 22:59:53 2006 From: jkeating at redhat.com (Jesse Keating) Date: Sat, 12 Aug 2006 18:59:53 -0400 Subject: [Fedora-infrastructure-list] Re: Test LDAP instance In-Reply-To: <3237e4410608121558m5c025bd8o75a8875a16009335@mail.gmail.com> References: <3237e4410608121545g7cec0094v5bedd817ef0c4ce9@mail.gmail.com> <3237e4410608121558m5c025bd8o75a8875a16009335@mail.gmail.com> Message-ID: <200608121859.56932.jkeating@redhat.com> On Saturday 12 August 2006 18:58, Mike McGrath wrote: > Step 1: > Install sun's java. ?I've been testing with jre1.5.0_08. The directory server itself doesn't need java does it? And if it does, we can't use Sun's java, we'd have to use something FOSS.... -- Jesse Keating Release Engineer: Fedora -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mmcgrath at fedoraproject.org Sat Aug 12 23:29:51 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Sat, 12 Aug 2006 18:29:51 -0500 Subject: [Fedora-infrastructure-list] Re: Test LDAP instance In-Reply-To: <200608121859.56932.jkeating@redhat.com> References: <3237e4410608121545g7cec0094v5bedd817ef0c4ce9@mail.gmail.com> <3237e4410608121558m5c025bd8o75a8875a16009335@mail.gmail.com> <200608121859.56932.jkeating@redhat.com> Message-ID: <3237e4410608121629h18b09927id09e8969f354e882@mail.gmail.com> On 8/12/06, Jesse Keating wrote: > On Saturday 12 August 2006 18:58, Mike McGrath wrote: > > Step 1: > > Install sun's java. I've been testing with jre1.5.0_08. > > The directory server itself doesn't need java does it? And if it does, we > can't use Sun's java, we'd have to use something FOSS.... > Nope, actually I *think* you can do just about everything through standard ldap queries and the web interface. But the console has a pretty good interface. Hopefully it'll be able to use java-gcj in the not so distant future. -Mike From dennis at ausil.us Sun Aug 13 13:19:02 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Sun, 13 Aug 2006 08:19:02 -0500 Subject: [Fedora-infrastructure-list] Re: Test LDAP instance In-Reply-To: <200608121859.56932.jkeating@redhat.com> References: <3237e4410608121545g7cec0094v5bedd817ef0c4ce9@mail.gmail.com> <3237e4410608121558m5c025bd8o75a8875a16009335@mail.gmail.com> <200608121859.56932.jkeating@redhat.com> Message-ID: <200608130819.02704.dennis@ausil.us> On Saturday 12 August 2006 5:59 pm, Jesse Keating wrote: > On Saturday 12 August 2006 18:58, Mike McGrath wrote: > > Step 1: > > Install sun's java. ?I've been testing with jre1.5.0_08. > > The directory server itself doesn't need java does it? And if it does, we > can't use Sun's java, we'd have to use something FOSS.... java is needed for the admin console. currently you have to use Sun's or IBM's my understanding is that the FDS team is working on making the admin console work with gcj but at the moment it doesnt -- Dennis Gilmore, RHCE Proud Australian From wtogami at redhat.com Tue Aug 15 21:42:22 2006 From: wtogami at redhat.com (Warren Togami) Date: Tue, 15 Aug 2006 17:42:22 -0400 Subject: [Fedora-infrastructure-list] More Servers for PHX Colo Message-ID: <44E23FBE.1080303@redhat.com> Hey folks, I talked with Max Spevack today about the status of the Dell server donation. To his knowledge as of yesterday nothing has arrived for him yet. Max agreed generally that we need more boxes in the colo, and he wants information of what type of servers (features, U sizes, cost). I assume the type of serial console with access to BIOS is an important requirement, but otherwise we need standard rackmount boxes? Does anyone know any more details about our colo? We need to get this information together, then Max can figure out if it fits within budget, and coordinate with Red Hat GIS to get it installed into the colo. Warren Togami wtogami at redhat.com From mspevack at redhat.com Wed Aug 16 18:49:57 2006 From: mspevack at redhat.com (Max Spevack) Date: Wed, 16 Aug 2006 14:49:57 -0400 (EDT) Subject: [Fedora-infrastructure-list] More Servers for PHX Colo In-Reply-To: <44E23FBE.1080303@redhat.com> References: <44E23FBE.1080303@redhat.com> Message-ID: On Tue, 15 Aug 2006, Warren Togami wrote: > Hey folks, > > I talked with Max Spevack today about the status of the Dell server > donation. To his knowledge as of yesterday nothing has arrived for him > yet. > > Max agreed generally that we need more boxes in the colo, and he wants > information of what type of servers (features, U sizes, cost). I assume > the type of serial console with access to BIOS is an important > requirement, but otherwise we need standard rackmount boxes? Does > anyone know any more details about our colo? I don't particularly care about all the technical specs of the boxes -- I just need to know what we need in general, what we plan to use it for, and how much it's going to cost. There shouldn't be any budget issues for a couple of thousand dollars worth of boxes, but that's only if I can give a useful accounting of what the money is buying us. --Max -- Max Spevack + http://fedoraproject.org/wiki/MaxSpevack + gpg key -- http://spevack.org/max.asc + fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21 From sbranden at redhat.com Wed Aug 16 19:29:18 2006 From: sbranden at redhat.com (Stacy J. Brandenburg) Date: Wed, 16 Aug 2006 15:29:18 -0400 Subject: [Fedora-infrastructure-list] More Servers for PHX Colo In-Reply-To: References: <44E23FBE.1080303@redhat.com> Message-ID: <44E3720E.30105@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am also covering the other needed costs for switching/pdus/racks/etc.... Nate and Warren are speaking now about specific HW. As an FYI, I would like the ok to take the fedora infrastructure off line, for a day, the last week of this month. I have "acquired" (don't ask me questions on this) a full rack. I would like to move your stuff from the current half height rack gafton and I "acquired" a few years ago and move it into the full height unit. This will require about 6 hours of downtime while we move stuff. Honestly, maybe much less, but I need to be safe. I will jump on the meeting tomorrow on IRC and also talk about it so everyone knows and approves.... Max Spevack wrote: | On Tue, 15 Aug 2006, Warren Togami wrote: | |> Hey folks, |> |> I talked with Max Spevack today about the status of the Dell server |> donation. To his knowledge as of yesterday nothing has arrived for him |> yet. |> |> Max agreed generally that we need more boxes in the colo, and he wants |> information of what type of servers (features, U sizes, cost). I |> assume the type of serial console with access to BIOS is an important |> requirement, but otherwise we need standard rackmount boxes? Does |> anyone know any more details about our colo? | | | I don't particularly care about all the technical specs of the boxes -- | I just need to know what we need in general, what we plan to use it for, | and how much it's going to cost. | | There shouldn't be any budget issues for a couple of thousand dollars | worth of boxes, but that's only if I can give a useful accounting of | what the money is buying us. | | --Max | - -- ======================================================== = Stacy J. Brandenburg Red Hat Inc. = = Manager, Network Operations sbranden at redhat.com = = 919-754-4313 http://www.redhat.com = ======================================================== Key ID 0x1828D94D Fingerprint 03F7 43BE 1150 CCFA F57B 54DD AEDB 1C27 1828 D94D -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFE43INrtscJxgo2U0RAth6AJ9I1Z6r2od63we9At0bakeBpJT2lgCdElQO xH4ThD3PCtbw6fK7tCQ/UE0= =cKaQ -----END PGP SIGNATURE----- From mmcgrath at fedoraproject.org Wed Aug 16 22:26:05 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 16 Aug 2006 17:26:05 -0500 Subject: [Fedora-infrastructure-list] More Servers for PHX Colo In-Reply-To: References: <44E23FBE.1080303@redhat.com> Message-ID: <3237e4410608161526w56bfeceex51540cf7acf7f65b@mail.gmail.com> On 8/16/06, Max Spevack wrote: > On Tue, 15 Aug 2006, Warren Togami wrote: > > > Hey folks, > > > > I talked with Max Spevack today about the status of the Dell server > > donation. To his knowledge as of yesterday nothing has arrived for him > > yet. > > > > Max agreed generally that we need more boxes in the colo, and he wants > > information of what type of servers (features, U sizes, cost). I assume > > the type of serial console with access to BIOS is an important > > requirement, but otherwise we need standard rackmount boxes? Does > > anyone know any more details about our colo? > > I don't particularly care about all the technical specs of the boxes -- I > just need to know what we need in general, what we plan to use it for, and > how much it's going to cost. > > There shouldn't be any budget issues for a couple of thousand dollars > worth of boxes, but that's only if I can give a useful accounting of what > the money is buying us. > > --Max > > -- As far as generals any sort of remote management would be fine by me, serial bios support, DRAC, or IP based KVM would be fine. One thing I'm not sure on, and Stace would know more, is how much space is left on our PDU's. Though in the near future we could really use a Xen box. Which, in general needs drive space and plenty of RAM. -Mike From mmcgrath at fedoraproject.org Wed Aug 16 22:36:39 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 16 Aug 2006 17:36:39 -0500 Subject: [Fedora-infrastructure-list] More Servers for PHX Colo In-Reply-To: <44E3720E.30105@redhat.com> References: <44E23FBE.1080303@redhat.com> <44E3720E.30105@redhat.com> Message-ID: <3237e4410608161536u5e45aff2leb381e1ae602819d@mail.gmail.com> One more thing we need to address in the not-to-distant future is a DR plan. I'm sure we don't need anything fancy, as far as essentials we'd need our primary mirror, builders, accounting and VCS. We'd also need our primary website (wiki) to communicate with our developers and end users. At present the wiki is at Duke. I'll probably start backing it up to the colo weekly with incrementals so we can mitigate that risk if Duke goes bye bye. I'm not sure where this is on our radar but the Phoenix colo is our primary site and if something happened to it, the Fedora Project as a whole might be in trouble. Unless there are some internal backups being done I'm not aware of. Well, except for Core. I'm not sure where the primary core cvs/look aside cache resides. -Paranoid Mike :) From sbranden at redhat.com Wed Aug 16 23:01:28 2006 From: sbranden at redhat.com (Stacy J. Brandenburg) Date: Wed, 16 Aug 2006 19:01:28 -0400 Subject: [Fedora-infrastructure-list] More Servers for PHX Colo In-Reply-To: <3237e4410608161536u5e45aff2leb381e1ae602819d@mail.gmail.com> References: <44E23FBE.1080303@redhat.com> <44E3720E.30105@redhat.com> <3237e4410608161536u5e45aff2leb381e1ae602819d@mail.gmail.com> Message-ID: <44E3A3C8.6040003@redhat.com> CVS is not backed up. The fedora bits released are. As for failover, (KNOCK ON WOOD), we have not had a failure in the DC. Not to mention if we do, fedora is least of our worries honestly.... We can leverage TPA if needed and you can free up servers for it though. Mike McGrath wrote: > One more thing we need to address in the not-to-distant future is a DR > plan. I'm sure we don't need anything fancy, as far as essentials > we'd need our primary mirror, builders, accounting and VCS. We'd also > need our primary website (wiki) to communicate with our developers and > end users. At present the wiki is at Duke. I'll probably start > backing it up to the colo weekly with incrementals so we can mitigate > that risk if Duke goes bye bye. > > I'm not sure where this is on our radar but the Phoenix colo is our > primary site and if something happened to it, the Fedora Project as a > whole might be in trouble. Unless there are some internal backups > being done I'm not aware of. Well, except for Core. I'm not sure > where the primary core cvs/look aside cache resides. > > -Paranoid Mike :) -- ======================================================== = Stacy J. Brandenburg Red Hat Inc. = = Manager of Network Operations sbranden at redhat.com = = 919-754-4313 http://www.redhat.com = ======================================================== Key ID 0x1828D94D Fingerprint 03F7 43BE 1150 CCFA F57B 54DD AEDB 1C27 1828 D94D From skvidal at linux.duke.edu Thu Aug 17 01:31:16 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Wed, 16 Aug 2006 21:31:16 -0400 Subject: [Fedora-infrastructure-list] More Servers for PHX Colo In-Reply-To: <3237e4410608161536u5e45aff2leb381e1ae602819d@mail.gmail.com> References: <44E23FBE.1080303@redhat.com> <44E3720E.30105@redhat.com> <3237e4410608161536u5e45aff2leb381e1ae602819d@mail.gmail.com> Message-ID: <1155778276.15276.4.camel@cutter> On Wed, 2006-08-16 at 17:36 -0500, Mike McGrath wrote: > One more thing we need to address in the not-to-distant future is a DR > plan. I'm sure we don't need anything fancy, as far as essentials > we'd need our primary mirror, builders, accounting and VCS. We'd also > need our primary website (wiki) to communicate with our developers and > end users. At present the wiki is at Duke. I'll probably start > backing it up to the colo weekly with incrementals so we can mitigate > that risk if Duke goes bye bye. Shouldn't our backups in general cover the disaster recovery process? and in the event of a real disaster how is the response time going to be at the coloc for drive replacement, etc? -sv From mmcgrath at fedoraproject.org Thu Aug 17 15:06:44 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Thu, 17 Aug 2006 10:06:44 -0500 Subject: [Fedora-infrastructure-list] Meeting Today Message-ID: <3237e4410608170806t634179d9nf4d9279cd3e91050@mail.gmail.com> Hey guys, I'm going to miss the meeting today unless my train happens to have an internet connection. The backups are mostly up and running. Right now we're getting about 120G worth of backups. Now we just have to go over the individual machines and make sure we're getting all the important stuff like keys the database etc. db1, fpserv and bastion are all I have left to add. Mirror list: The mirror list has been working fine for the most part. Every once in a while though it grabs a bad mirror (http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/development/$ARCH/os/) I've only caught it happening once. Lyz, Abompard. Sign up for the group "sysadmin-general". This will allow you guys to access my LDAP install on bastion. -Mike From mspevack at redhat.com Fri Aug 18 01:55:52 2006 From: mspevack at redhat.com (Max Spevack) Date: Thu, 17 Aug 2006 21:55:52 -0400 (EDT) Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: <44E4E76D.8040509@redhat.com> References: <44E4E76D.8040509@redhat.com> Message-ID: Adding the fedora-infrastructure-list -- those would be the best people to look into it. It certainly seems like there's a problem -- hopefully we can resolve it ASAP. --Max ===================== On Thu, 17 Aug 2006, Nathan Kinder wrote: > Hi Max, > > Our checkins to the /cvs/dirsec repository on cvs.fedora.redhat.com > usually end up sending commit messages to the fedora-directory-commits > mailing list. This notification mechanism no longer seems to be working. > I'm not sure when it stopped working exactly, but the last notification > that was received was on 08/09. I have checked with some other team > members, and they have experienced the same thing. > > Is this a problem on the cvs server? > > Thanks, > -NGK -- Max Spevack + http://fedoraproject.org/wiki/MaxSpevack + gpg key -- http://spevack.org/max.asc + fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21 From wtogami at redhat.com Fri Aug 18 03:02:35 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 17 Aug 2006 23:02:35 -0400 Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: References: <44E4E76D.8040509@redhat.com> Message-ID: <44E52DCB.3050306@redhat.com> Max Spevack wrote: >> >> Our checkins to the /cvs/dirsec repository on cvs.fedora.redhat.com >> usually end up sending commit messages to the fedora-directory-commits >> mailing list. This notification mechanism no longer seems to be >> working. I'm not sure when it stopped working exactly, but the last >> notification that was received was on 08/09. I have checked with some >> other team members, and they have experienced the same thing. >> >> Is this a problem on the cvs server? >> >> Thanks, >> -NGK > /cvs/dirsec/CVSROOT/loginfo contains: DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} cvsdirsec at fedora.redhat.com https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html This address goes through an alias to reach fedora-directory-commits list. Looks like my test message hit the list without me being subscribed, you don't have any spam problems? I also see CVS mail from August 17th here, so mail is definitely hitting the list. Are you sure your personal subscription or mail filters aren't in error? ^ldapserver $CVSROOT/CVSROOT/dolog.pl -r /cvs/dirsec foxworth at redhat.com foxworth is no longer at the company, should this be redirected to somebody else or deleted? Warren Togami wtogami at redhat.com From wtogami at redhat.com Fri Aug 18 03:39:41 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 17 Aug 2006 23:39:41 -0400 Subject: [Fedora-infrastructure-list] Status of Two New Dell Servers Message-ID: <44E5367D.7030701@redhat.com> Dell U2 rackmount Red Hat is purchasing: Two dual core 5050 Xeon's 8GB RAM 4 x 146GB drives Hopefully will be delivered in time for Stacy's visit to the colo late August. Dell's Donated 1950 1U rackmount: Two dual core Woodcrest Xeon's 4GB RAM (reportedly) 2 x 73GB drives Currently being shipped from LWE San Francisco to Raleigh, NC. (Oops) Being redirected back to the colo in Arizona, should definitely arrive in time for Stacy's visit to the colo late August. Both boxes will make great Xen hosts. We can figure what to run and where later. Warren Togami wtogami at redhat.com From mmcgrath at fedoraproject.org Fri Aug 18 04:10:53 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Thu, 17 Aug 2006 23:10:53 -0500 Subject: [Fedora-infrastructure-list] Status of Two New Dell Servers In-Reply-To: <44E5367D.7030701@redhat.com> References: <44E5367D.7030701@redhat.com> Message-ID: <3237e4410608172110o2244617cp41c4cfa8165d5171@mail.gmail.com> > Both boxes will make great Xen hosts. We can figure what to run and > where later. > Sweeeet. Thanks Red Hat :) -Mike From wtogami at redhat.com Fri Aug 18 04:11:48 2006 From: wtogami at redhat.com (Warren Togami) Date: Fri, 18 Aug 2006 00:11:48 -0400 Subject: [Fedora-infrastructure-list] Status of Two New Dell Servers In-Reply-To: <3237e4410608172110o2244617cp41c4cfa8165d5171@mail.gmail.com> References: <44E5367D.7030701@redhat.com> <3237e4410608172110o2244617cp41c4cfa8165d5171@mail.gmail.com> Message-ID: <44E53E04.8080904@redhat.com> Mike McGrath wrote: >> Both boxes will make great Xen hosts. We can figure what to run and >> where later. >> > > Sweeeet. Thanks Red Hat :) > > -Mike Don't forget thanks Dell :) Warren From dennis at ausil.us Fri Aug 18 21:53:12 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Fri, 18 Aug 2006 16:53:12 -0500 Subject: [Fedora-infrastructure-list] Meeting Log 2006-08-17 Message-ID: <200608181653.12742.dennis@ausil.us> Hey guys, attached is the log from the meeting yesterday. We covered a fairly large amount of things which was good. We really need someone to step up and replace pasqual with unifying the look and feel of the websites. as well as to get things rolling on the FPD. Thanks to all those who participated. Regards Dennis -------------- next part -------------- [Thu Aug 17 2006] [15:02:17] everyone ready for the meeting? [Thu Aug 17 2006] [15:02:28] * pick is [Thu Aug 17 2006] [15:02:30] schedule is http://fedoraproject.org/wiki/Infrastructure/Schedule [Thu Aug 17 2006] [15:02:50] yep [Thu Aug 17 2006] [15:03:23] Item 1 [Thu Aug 17 2006] [15:03:51] we need a new person to step up and help with unifing the look and feel of our websites [Thu Aug 17 2006] [15:04:10] html coder ? [Thu Aug 17 2006] [15:04:19] * iWolf wanders in. [Thu Aug 17 2006] [15:04:34] or some admin help with sites? [Thu Aug 17 2006] [15:04:50] mazaj: we we want some way to apply a css style sheet to everything so they look the same [Thu Aug 17 2006] [15:05:06] ahh..ok not me [Thu Aug 17 2006] [15:05:08] :( [Thu Aug 17 2006] [15:05:17] cacti, nagios, a few other things make everything much more unified [Thu Aug 17 2006] [15:05:27] its a coding job [Thu Aug 17 2006] [15:05:36] pasqual was doing it but had to step down [Thu Aug 17 2006] [15:06:11] Quit mspevack has left this server (Remote closed the connection). [Thu Aug 17 2006] [15:06:58] abadger1999, c4chris, cweyl, f13, lyz, rordway, skvidal, tibbs, warren: ping [Thu Aug 17 2006] [15:07:06] yello [Thu Aug 17 2006] [15:07:06] dgilmore: pong [Thu Aug 17 2006] [15:07:09] I are here [Thu Aug 17 2006] [15:07:13] What's up? [Thu Aug 17 2006] [15:07:18] here [Thu Aug 17 2006] [15:07:27] Nick pick is now known as stacy. [Thu Aug 17 2006] [15:07:30] here [Thu Aug 17 2006] [15:07:31] meeting we need a new unifiying the web look and feel guy [Thu Aug 17 2006] [15:07:44] hey stacy [Thu Aug 17 2006] [15:07:57] hey [Thu Aug 17 2006] [15:08:09] had some nuts and bolts stuff for when we get down the list [Thu Aug 17 2006] [15:08:17] cool :) [Thu Aug 17 2006] [15:08:31] is mike here today? [Thu Aug 17 2006] [15:08:31] dgilmore, I'm not that good at CSS, but if someone needs a spotter, I'll help out [Thu Aug 17 2006] [15:08:51] warren no [Thu Aug 17 2006] [15:08:53] I have absolutely zero web design talent. [Thu Aug 17 2006] [15:09:01] lyz: ok it probably really needs to be a few person job [Thu Aug 17 2006] [15:09:08] He was on a train he said and I dont think it had internet access [Thu Aug 17 2006] [15:09:15] yeah [Thu Aug 17 2006] [15:09:24] lete move this to the list see if we can find some people [Thu Aug 17 2006] [15:09:27] lets [Thu Aug 17 2006] [15:09:29] You can see thiefmissions.com for my web design resume. [Thu Aug 17 2006] [15:09:50] Item2 : VCS [Thu Aug 17 2006] [15:09:56] anything to report [Thu Aug 17 2006] [15:10:00] tibbs, :) [Thu Aug 17 2006] [15:10:26] We tried to install bzr on one of our servers this weekend but we don't have a recent enough python. [Thu Aug 17 2006] [15:10:40] if someone need assistant in SVN - call me [Thu Aug 17 2006] [15:10:51] The two new servers we should have installed late August will be running FC6 [Thu Aug 17 2006] [15:11:00] mazaj: we have svn installed and setup for testing i believe [Thu Aug 17 2006] [15:11:16] warren is looking into a new server for some Xen guests that we can set up within. [Thu Aug 17 2006] [15:11:22] warren: cool so that will let us test things better [Thu Aug 17 2006] [15:11:44] so nothing else to report here? [Thu Aug 17 2006] [15:12:13] Item3: Upgrading systems [Thu Aug 17 2006] [15:12:25] warren: which two new servers are coming in late August? [Thu Aug 17 2006] [15:12:42] db1 upgrade is waiting on the new hardware. I believe that everything else is done [Thu Aug 17 2006] [15:12:58] One thing about VCS -- it depends on the packaging database. [Thu Aug 17 2006] [15:13:24] stacy, did Max and Nate complete the order today? [Thu Aug 17 2006] [15:13:29] abadger1999: lots of things are waiting on the packaging database. It really needs to eb a top priority [Thu Aug 17 2006] [15:13:38] So getting a new VCS deployed by FC7-testX means getting the packaging db up and running [Thu Aug 17 2006] [15:13:55] dgilmore: yep :-) [Thu Aug 17 2006] [15:13:56] yes.. lots of work =( [Thu Aug 17 2006] [15:14:20] max is putting the req in this morning warren [Thu Aug 17 2006] [15:14:21] and its not in our schedule [Thu Aug 17 2006] [15:14:36] stacy, morning? [Thu Aug 17 2006] [15:14:40] we have not heard from finance yet [Thu Aug 17 2006] [15:14:43] this morning [Thu Aug 17 2006] [15:14:45] oh [Thu Aug 17 2006] [15:14:53] now [Thu Aug 17 2006] [15:14:57] might ask max [Thu Aug 17 2006] [15:15:01] but that is what nate and I were told [Thu Aug 17 2006] [15:15:10] We had to make the order today if it was possible to delivery [Thu Aug 17 2006] [15:15:14] sure [Thu Aug 17 2006] [15:15:17] might poke him [Thu Aug 17 2006] [15:15:43] But the Dell donation coming from LWE might suffice for infastructure team's needs meanwhile. [Thu Aug 17 2006] [15:15:47] ok [Thu Aug 17 2006] [15:15:52] I sent the addr for that to be sent to [Thu Aug 17 2006] [15:15:55] you should have it now [Thu Aug 17 2006] [15:16:01] dgilmore: Right. Who's in charge of it? What's the status? [Thu Aug 17 2006] [15:16:06] mspevack_hm, around? [Thu Aug 17 2006] [15:16:19] abadger1999: i guess warren is in charge of it [Thu Aug 17 2006] [15:16:39] I'll coordinate with RH people regarding the servers. [Thu Aug 17 2006] [15:16:39] status trying to work out the exact requirements [Thu Aug 17 2006] [15:16:57] max is not answering at his desk [Thu Aug 17 2006] [15:17:01] warren: were you looking after the package db or someone else? [Thu Aug 17 2006] [15:17:58] abadger1999: if no one else wants it put me down [Thu Aug 17 2006] [15:18:56] dgilmore: I'm interested in it too, but if I work on it I can't work on the VCS stuff (esp. getting mercurial off the ground.) [Thu Aug 17 2006] [15:19:28] Join mspevack has joined this channel (n=mspevack at nat-pool-rdu.redhat.com). [Thu Aug 17 2006] [15:19:29] Do you want to drive and you can call on me if you need someone to help code? [Thu Aug 17 2006] [15:19:35] abadger1999: put me down, everyone can help [Thu Aug 17 2006] [15:19:44] sure [Thu Aug 17 2006] [15:19:54] Package Database is important to our future, but so is VCS. VCS is probably easier. [Thu Aug 17 2006] [15:20:08] mspevack, hey Max, did we manage to make the order today? [Thu Aug 17 2006] [15:21:03] package db, VCS - i can help any time , just tell exactly what to do ;) [Thu Aug 17 2006] [15:21:34] warren: yeah, what a total disaster our purchase order system is [Thu Aug 17 2006] [15:21:55] not to mention the fact that if you're running Fedora, you CAN'T EVEN PLACE ONE [Thu Aug 17 2006] [15:22:05] warren: VCS hooks to the Package DB, though... Administration of the permissions in the VCS should be done in the PackageDB at least. [Thu Aug 17 2006] [15:22:08] mspevack: wtf :( [Thu Aug 17 2006] [15:22:28] dgilmore: hey, it's ordered so all's well that ends well [Thu Aug 17 2006] [15:22:35] :) [Thu Aug 17 2006] [15:22:40] mspevack, what is the req number? [Thu Aug 17 2006] [15:22:42] mspevack, it is their job to make it as difficult as possible to spend money. [Thu Aug 17 2006] [15:22:43] I can track it down [Thu Aug 17 2006] [15:22:45] Could have the VCS hook into a prerelease package db that's meant just to drive that aspect of the VCS, though. [Thu Aug 17 2006] [15:22:53] abadger1999: yeah it should be done there [Thu Aug 17 2006] [15:23:38] abadger1999, we can do VCS capabilities without FPD, we just design hooks to replace later. [Thu Aug 17 2006] [15:24:15] warren: Yeah. But we'd probably want to have it hook to some sort of DB so it's easy to pull the permissions to the real package db later. [Thu Aug 17 2006] [15:24:51] Otherwise we'll have to capture the information from the repository which is possible but more work. [Thu Aug 17 2006] [15:24:54] hmm... this first DB would give a clearer picture of one aspect in the final FPD [Thu Aug 17 2006] [15:25:08] That is true. A prototype of what's needed later. [Thu Aug 17 2006] [15:25:09] keep in mind that the first implementation of anything will probably be rewritten [Thu Aug 17 2006] [15:26:15] So maybe we should try to get a package db that isn't perfect, but it's enough to identify issues and get the new VCS running. [Thu Aug 17 2006] [15:26:26] :) yep so we need to get a rough alpha FPD in place sometime pretty soon [Thu Aug 17 2006] [15:26:30] Quit xDamox has left this server ("Leaving"). [Thu Aug 17 2006] [15:27:40] I don't think we need a database to get an idea of VCS capabilities, DB driven permissions is the second step really. [Thu Aug 17 2006] [15:28:54] nope but it would help with having it close to final implementation [Thu Aug 17 2006] [15:29:28] Part fermar has left this channel ("Ex-Chat"). [Thu Aug 17 2006] [15:29:31] yes, exactly [Thu Aug 17 2006] [15:30:19] So the topic of VCS, we will test capabilities of both mercurial and bzr when we have the servers installed. [Thu Aug 17 2006] [15:30:36] yep and we have svn installed somewhere already [Thu Aug 17 2006] [15:30:41] Sounds good. [Thu Aug 17 2006] [15:30:49] I think after we choose one based upon capabilities and judgements of future maintainability, we can work on the database aspects. [Thu Aug 17 2006] [15:31:13] we can always make it work with our systems somehow. [Thu Aug 17 2006] [15:31:27] lmacken: whats the status of pyroman? [Thu Aug 17 2006] [15:31:32] Without anybody able to focus 100% on FPD, we may have to build FPD from the ground up to get a clearer idea of what we need. Then rewrite it. [Thu Aug 17 2006] [15:31:53] then rewrite it again [Thu Aug 17 2006] [15:31:58] dgilmore: I haven't deployed our configuration on anymore systems. I'm going to make time this weekend to do it. [Thu Aug 17 2006] [15:32:14] lmacken: cool what systems are left? [Thu Aug 17 2006] [15:32:32] i think i remember someone saying that they deployed it on a bunch of the systems that just got rebuilt.. but the deployment status on the wiki isn't updated :( [Thu Aug 17 2006] [15:32:46] i'm going to try to find some time this weekend just to crank through them [Thu Aug 17 2006] [15:32:48] lmacken: i think its on all the builders [Thu Aug 17 2006] [15:33:01] ah, ok [Thu Aug 17 2006] [15:33:05] mmcgrath put them in place after i rebuilt them [Thu Aug 17 2006] [15:33:22] but we should double check with him and have him update the status [Thu Aug 17 2006] [15:33:42] sounds good [Thu Aug 17 2006] [15:34:04] lmacken: your next also TurboGears [Thu Aug 17 2006] [15:34:28] oh yes, TurboGears is probably very relevant to FPD [Thu Aug 17 2006] [15:34:30] python-simplejson made it though the review process. still waiting on python-paste-{script,deploy} [Thu Aug 17 2006] [15:34:39] waiting on a naming issue wrt python submodules [Thu Aug 17 2006] [15:35:05] i've been keeping my local TurboGears spec up to date with the latest releases, so once they make it through i can get it right out [Thu Aug 17 2006] [15:35:25] cool [Thu Aug 17 2006] [15:35:58] Doesn't look like the Packaging Committee is realy aware of the naming issue. [Thu Aug 17 2006] [15:36:10] I'll see if I can bring that to their attention this week. [Thu Aug 17 2006] [15:36:27] cool, thanks [Thu Aug 17 2006] [15:36:32] abadger1999: can you push to get this resolved quickly please [Thu Aug 17 2006] [15:36:56] Documenting Infrastructure: [Thu Aug 17 2006] [15:37:01] dgilmore: Will do. I'll send an email and hopefully vote on it next week. [Thu Aug 17 2006] [15:37:14] dgilmore, I owe that to warren [Thu Aug 17 2006] [15:37:16] I know i need to finish my report on the process [Thu Aug 17 2006] [15:37:19] that is part of why I am here [Thu Aug 17 2006] [15:37:28] owe what? [Thu Aug 17 2006] [15:37:30] from a physical/access standpoint [Thu Aug 17 2006] [15:37:37] the documentation [Thu Aug 17 2006] [15:37:51] #6 Documenting infrastructure [Thu Aug 17 2006] [15:37:53] opps [Thu Aug 17 2006] [15:38:03] of what i did rebuilding the builders [Thu Aug 17 2006] [15:38:07] oh, I thought I was blamed for something =) [Thu Aug 17 2006] [15:38:11] nah :) [Thu Aug 17 2006] [15:38:16] Once we rebuild the rack there [Thu Aug 17 2006] [15:38:34] We'll have the space to add more servers [Thu Aug 17 2006] [15:38:40] including the two heading there [Thu Aug 17 2006] [15:38:42] I will make sure the methods for access and documents around the physical build are sent to you [Thu Aug 17 2006] [15:38:45] stacy: how much space do we have? [Thu Aug 17 2006] [15:38:46] yep [Thu Aug 17 2006] [15:38:50] right now [Thu Aug 17 2006] [15:38:51] 0U [Thu Aug 17 2006] [15:38:56] after the end of the month [Thu Aug 17 2006] [15:38:56] :( [Thu Aug 17 2006] [15:38:57] cool, thanks [Thu Aug 17 2006] [15:38:58] at least another 20U [Thu Aug 17 2006] [15:39:07] we have a half height rack now for fedora [Thu Aug 17 2006] [15:39:14] I "reappropriate" a full rack [Thu Aug 17 2006] [15:39:16] cool so we really dont have room for the servers we are getting [Thu Aug 17 2006] [15:39:20] and new PDUs/Cyclades for fedora [Thu Aug 17 2006] [15:39:30] from another project at a big named company with a hat [Thu Aug 17 2006] [15:39:40] stacy: cool. [Thu Aug 17 2006] [15:39:40] and I am going to move the gear into it [Thu Aug 17 2006] [15:39:43] to make room [Thu Aug 17 2006] [15:39:46] stacy: nice! [Thu Aug 17 2006] [15:39:47] make maint easier [Thu Aug 17 2006] [15:39:55] and give a lights out access method [Thu Aug 17 2006] [15:40:01] stacy: did you manage to check out the bios over serial port for the hammers? [Thu Aug 17 2006] [15:40:11] but don't tell Charlie Peters :) [Thu Aug 17 2006] [15:40:19] not yet [Thu Aug 17 2006] [15:40:26] I am out there the last week of the month [Thu Aug 17 2006] [15:40:28] I will do it then [Thu Aug 17 2006] [15:40:38] I am also moving across country to be close to that site [Thu Aug 17 2006] [15:40:44] Then we can get hands on anytime [Thu Aug 17 2006] [15:40:57] cool. i got by without it when i rebuilt them buty was concerend we could end up without one of them [Thu Aug 17 2006] [15:40:59] and I have more time to nudge gnome out of the way for fedora ;) [Thu Aug 17 2006] [15:41:12] dgilmore, I always have a way [Thu Aug 17 2006] [15:41:17] if you get in that position call me [Thu Aug 17 2006] [15:41:19] or email me [Thu Aug 17 2006] [15:41:23] sbranden at redhat.com [Thu Aug 17 2006] [15:41:34] I have methods for gaining access [Thu Aug 17 2006] [15:41:42] :) good to know [Thu Aug 17 2006] [15:41:54] I am your POC for any physical needs [Thu Aug 17 2006] [15:41:59] * dgilmore would like stacy's job i think [Thu Aug 17 2006] [15:42:03] feel free to add that to the docs [Thu Aug 17 2006] [15:42:07] no [Thu Aug 17 2006] [15:42:09] you would not :) [Thu Aug 17 2006] [15:42:20] stacy, I am very glad that GIS is taking Fedora infrastructure needs very seriously. =) [Thu Aug 17 2006] [15:42:29] we try [Thu Aug 17 2006] [15:42:37] as a company it is not really a priority from where I sit [Thu Aug 17 2006] [15:42:40] but that is shit [Thu Aug 17 2006] [15:42:51] Exactly [Thu Aug 17 2006] [15:43:10] I will make things happen if we need to [Thu Aug 17 2006] [15:43:10] * dgilmore applied for a IS/IT job in Boston the other week [Thu Aug 17 2006] [15:43:17] really? [Thu Aug 17 2006] [15:43:18] anyways [Thu Aug 17 2006] [15:43:20] yeah [Thu Aug 17 2006] [15:43:23] send me your resume [Thu Aug 17 2006] [15:43:27] I sit next to the hiring manager [Thu Aug 17 2006] [15:43:33] I can nudge it [Thu Aug 17 2006] [15:43:35] :) cool [Thu Aug 17 2006] [15:43:41] i will get it to you [Thu Aug 17 2006] [15:44:01] anyone have anything to add on documentation? [Thu Aug 17 2006] [15:44:21] BTW back to the order with Max - Just confirmed it is ordered and ready for shipment to phx [Thu Aug 17 2006] [15:44:31] :D awsome [Thu Aug 17 2006] [15:44:41] Quit JSchmitt has left this server (Remote closed the connection). [Thu Aug 17 2006] [15:45:05] * c4chris is back, scrolls back a bit and starts to read.... [Thu Aug 17 2006] [15:45:14] ok moving on? [Thu Aug 17 2006] [15:45:17] skvidal, you around? [Thu Aug 17 2006] [15:45:36] dgilmore, backups? [Thu Aug 17 2006] [15:46:07] currently BackupPC is installed and mmcgrath has done an initial install and configuration [Thu Aug 17 2006] [15:46:20] * dgilmore doesnt have the access to do that. [Thu Aug 17 2006] [15:46:44] we need to review whats being backed up and ensure we are getting everything we need to [Thu Aug 17 2006] [15:47:11] we also need to setup access to restore stuff for those in charge of the different systems [Thu Aug 17 2006] [15:48:15] stacy: is there anyway we can get something at a site other than the colo for DR purposes? [Thu Aug 17 2006] [15:48:26] yes [Thu Aug 17 2006] [15:48:35] I have a DC in TPA as well that we can place some limited stuff at [Thu Aug 17 2006] [15:48:58] cool it could be nice to have at least the last full backup there [Thu Aug 17 2006] [15:49:31] ACK, my internet became packet phobic for a few minutes there. [Thu Aug 17 2006] [15:49:48] warren: we did that to you on purpose :D [Thu Aug 17 2006] [15:51:18] ok next [Thu Aug 17 2006] [15:51:23] Servers from Dell [Thu Aug 17 2006] [15:51:42] mspevack: do you know when you should get them [Thu Aug 17 2006] [15:52:00] dgilmore, both are to be shipped directly to the colo. [Thu Aug 17 2006] [15:52:20] warren: cool last i knew they were going to max [Thu Aug 17 2006] [15:52:25] dgilmore, stacy is going to install pre-FC6 on both, cleanup our rack and have them installed at the end of August. [Thu Aug 17 2006] [15:52:34] more efficient to go right to phx [Thu Aug 17 2006] [15:52:36] warren: are those the 2950's? [Thu Aug 17 2006] [15:52:42] the donated one is 1950 [Thu Aug 17 2006] [15:52:57] warren: and is one of those supposed to be the new DB server or is that different hardware? [Thu Aug 17 2006] [15:53:05] warren: so we are buying one and having one donated? [Thu Aug 17 2006] [15:53:20] yes [Thu Aug 17 2006] [15:53:29] warren will pre-FC6 be posted publically? [Thu Aug 17 2006] [15:53:41] ie will it use the storage methods for general FC releases? [Thu Aug 17 2006] [15:53:45] I can use that for KS [Thu Aug 17 2006] [15:53:50] if not I will need CDs [Thu Aug 17 2006] [15:53:57] stacy, test2 would be fine, we can upgrade into what we need. [Thu Aug 17 2006] [15:54:01] ok [Thu Aug 17 2006] [15:54:11] are you going to build a KS.cfg? [Thu Aug 17 2006] [15:54:28] good question [Thu Aug 17 2006] [15:54:35] iWolf: i think we were going to install a xen instance for db [Thu Aug 17 2006] [15:54:37] if so, you can set up a PXE/KS server [Thu Aug 17 2006] [15:54:44] and then all you need to do is go to bios and reboot [Thu Aug 17 2006] [15:54:50] BAM you have a new server in 5 min [Thu Aug 17 2006] [15:54:57] that is the way we do our stuff [Thu Aug 17 2006] [15:55:07] dgilmore: Cool, that works to! I was just hoping we were sticking with RHEL for the DB. [Thu Aug 17 2006] [15:55:11] but I am not sure we can leverage the PXE/KS server we have there as it is on a secure network from fedora [Thu Aug 17 2006] [15:55:22] This might be a little unpredictable given that FC6 is still changing. [Thu Aug 17 2006] [15:55:40] stacy, that would be a good plan a little later I think. [Thu Aug 17 2006] [15:55:46] ok [Thu Aug 17 2006] [15:55:57] iWolf, I hope to run xen on both boxes. [Thu Aug 17 2006] [15:56:10] hmm, we should put another 2GB RAM into the donated box. [Thu Aug 17 2006] [15:56:23] iWolf, then we can have the FPD development testing in a guest somewhere. [Thu Aug 17 2006] [15:56:29] stacy: i used mirrors.kernel.org when i installed fc5 on the builders but the nfs share could have been used also [Thu Aug 17 2006] [15:56:47] ok [Thu Aug 17 2006] [15:56:52] warren: sounds good. thanks! [Thu Aug 17 2006] [15:57:10] if mirrors.kernel.org has it, fedora should be able to access the master in PHX :) [Thu Aug 17 2006] [15:57:52] stacy, any idea how much 2GB more RAM for a 1950 would cost? [Thu Aug 17 2006] [15:57:55] stacy: i think that there is a firewall issue using download.fedora.redhat.com from the fedora side [Thu Aug 17 2006] [15:58:43] dgilmore, I am the FW master :) [Thu Aug 17 2006] [15:58:49] * stacy makes things happen if needed [Thu Aug 17 2006] [15:58:49] Quit lyz has left this server (Remote closed the connection). [Thu Aug 17 2006] [15:59:17] stacy: cool mmcgrath knows much more about the issue of fedora servers talking to redhat ones [Thu Aug 17 2006] [15:59:50] anything more on the servers? [Thu Aug 17 2006] [15:59:59] 2GB costs about 400 [Thu Aug 17 2006] [16:00:11] if not the next two items are kind of releated [Thu Aug 17 2006] [16:00:20] It sounds like many of our projects are being held back by inability to deploy them in the public and test it. [Thu Aug 17 2006] [16:00:39] warren: thats one of the issues [Thu Aug 17 2006] [16:01:04] mspevack, could we pony up the extra $400 for more RAM for the donated box, so both servers would be flexible and useful for Xen? [Thu Aug 17 2006] [16:01:06] another is having the people with the skills for what we need [Thu Aug 17 2006] [16:01:40] with 4GB, we could comfortably run 3 or 4 guests on the donated box, although slower. Devel projects can run there. The beefy box can run guests with some real performance, even a decent production service is fine there. [Thu Aug 17 2006] [16:02:39] warren: how about we do this, the bigger box will host db2, and the vcs instances [Thu Aug 17 2006] [16:03:01] the donated box can be the test bed for things like ldap, FPD [Thu Aug 17 2006] [16:03:18] Directory Server is pretty RAM intensive [Thu Aug 17 2006] [16:03:39] but for testing it should be ok [Thu Aug 17 2006] [16:03:41] all [Thu Aug 17 2006] [16:03:44] I can buy the ram [Thu Aug 17 2006] [16:03:47] mdomsch informs me that the donated box may already have a crazy amount of RAM =) [Thu Aug 17 2006] [16:03:51] Once I get to PHX I can run over to Frys and get it [Thu Aug 17 2006] [16:03:54] much easier [Thu Aug 17 2006] [16:03:58] I will just expense it [Thu Aug 17 2006] [16:04:00] cool [Thu Aug 17 2006] [16:04:11] so lets see what it has [Thu Aug 17 2006] [16:04:13] and if we need more [Thu Aug 17 2006] [16:04:15] OK, if it doesn't, stacy can fix that problem quickly. [Thu Aug 17 2006] [16:04:18] I can pick it up pretty easy [Thu Aug 17 2006] [16:04:21] 400 is mouse nuts [Thu Aug 17 2006] [16:04:25] cool [Thu Aug 17 2006] [16:04:34] dgilmore, regarding what runs where, we can figure that out easily later. Let's figure out what we have first. [Thu Aug 17 2006] [16:04:47] warren: :) ok [Thu Aug 17 2006] [16:04:49] mmmm... mouse nuts? [Thu Aug 17 2006] [16:04:59] mdomsch thinks it has 4GB minimum, so we're probably fine [Thu Aug 17 2006] [16:05:34] so we are settled on server issues? [Thu Aug 17 2006] [16:05:43] think so [Thu Aug 17 2006] [16:05:54] next two issues are kinda releated [Thu Aug 17 2006] [16:05:58] k [Thu Aug 17 2006] [16:06:14] I need to setup mock configs and plague configs for legacy [Thu Aug 17 2006] [16:06:27] so that they can build on the builders [Thu Aug 17 2006] [16:06:44] for 1 it brings them closer and 2 they dont have ppc machines [Thu Aug 17 2006] [16:07:06] who does not have PPC? [Thu Aug 17 2006] [16:07:15] aand i need to get somewher to rsync legacy updates and put them in the mock configs for FE3 and FE4 [Thu Aug 17 2006] [16:07:23] fedora legacy [Thu Aug 17 2006] [16:07:27] ah [Thu Aug 17 2006] [16:07:36] 2 dual-core Xeon 5110 4MB cache 1.6GHz, 4GB RAM minimum, 2x73GB SCSI drives [Thu Aug 17 2006] [16:07:37] you know you have at least one right ;) [Thu Aug 17 2006] [16:07:47] Aside from the storage, this is more powerful than the server we ordered. [Thu Aug 17 2006] [16:08:03] warren: sorry, i was afk [Thu Aug 17 2006] [16:08:07] warren: yes, we can get 400 [Thu Aug 17 2006] [16:08:13] mspevack, actually, wont need it =) [Thu Aug 17 2006] [16:08:29] warren: in that case, $400 worth of ipods. :-) (just kidding) [Thu Aug 17 2006] [16:08:34] * stacy laughs [Thu Aug 17 2006] [16:08:39] mspevack, oh, so 1.5 ipods? =) [Thu Aug 17 2006] [16:08:44] you get the .5 [Thu Aug 17 2006] [16:08:45] mspevack: id rather something that plays ogg [Thu Aug 17 2006] [16:08:46] I get the 1st one [Thu Aug 17 2006] [16:09:05] ok what else [Thu Aug 17 2006] [16:09:11] it is past beer o'clock [Thu Aug 17 2006] [16:09:25] lets quickly run over lower priority things [Thu Aug 17 2006] [16:09:29] sure [Thu Aug 17 2006] [16:09:31] rordway: metrics? [Thu Aug 17 2006] [16:10:07] dgilmore: not much headway, still poking along when I get time. I've been putting in about 70 hour weeks the last few weeks [Thu Aug 17 2006] [16:10:17] summer will be over soon [Thu Aug 17 2006] [16:10:18] rordway: :( ok [Thu Aug 17 2006] [16:10:39] mirror management i think has seen some good progress [Thu Aug 17 2006] [16:11:04] f13: fc6t2 is using the mirror management stuff right? [Thu Aug 17 2006] [16:11:27] anyone know anything about the hardware reporting tool? [Thu Aug 17 2006] [16:11:50] dgilmore: that's usuall xDamox [Thu Aug 17 2006] [16:12:11] iWolf: cool he dropped off earlier [Thu Aug 17 2006] [16:12:24] anyone got anything else to add? [Thu Aug 17 2006] [16:12:35] anything [Thu Aug 17 2006] [16:12:38] in general? [Thu Aug 17 2006] [16:12:40] yes [Thu Aug 17 2006] [16:12:47] I was letting you finish the list first [Thu Aug 17 2006] [16:12:49] stacy: shoot the floor is yours [Thu Aug 17 2006] [16:12:49] if we are there [Thu Aug 17 2006] [16:12:52] ok [Thu Aug 17 2006] [16:12:59] I propose an outage on the 30th [Thu Aug 17 2006] [16:13:08] dgilmore: yes. [Thu Aug 17 2006] [16:13:12] We can put up a static HTML page that says - fedora is offline for maint [Thu Aug 17 2006] [16:13:16] during the time [Thu Aug 17 2006] [16:13:19] and what I want to do [Thu Aug 17 2006] [16:13:25] is move everything to the new larger rack [Thu Aug 17 2006] [16:13:32] get everything in a single easily managed rack [Thu Aug 17 2006] [16:13:40] stacy, what time do you fly that day? [Thu Aug 17 2006] [16:13:41] should take about 4 hours [Thu Aug 17 2006] [16:13:45] stacy: im ok with that [Thu Aug 17 2006] [16:13:49] I leave on the 1st [Thu Aug 17 2006] [16:13:53] ahh, ok [Thu Aug 17 2006] [16:14:00] this gives me time if I make a mistake - to fix it [Thu Aug 17 2006] [16:14:05] on the 31st [Thu Aug 17 2006] [16:14:09] problem is [Thu Aug 17 2006] [16:14:22] I have a meeting with the pres of AT&T that day to speak about his inability to make me happy. [Thu Aug 17 2006] [16:14:35] so I may need a little extra time in the middle for his royalness [Thu Aug 17 2006] [16:14:40] stacy: they dont make me happy either [Thu Aug 17 2006] [16:14:46] so I would like to say [Thu Aug 17 2006] [16:14:51] start at 9:00a MTN [Thu Aug 17 2006] [16:15:01] and end no later than 5pm MTN [Thu Aug 17 2006] [16:15:09] I am sure we can move faster [Thu Aug 17 2006] [16:15:14] but need to be safe [Thu Aug 17 2006] [16:15:21] is that ok with everyone? [Thu Aug 17 2006] [16:15:26] fine with me [Thu Aug 17 2006] [16:15:30] ok [Thu Aug 17 2006] [16:15:49] who can send me a static page to put up for the outage content? [Thu Aug 17 2006] [16:15:51] we will need to send announcements to probably every mailing list but thats not a huge deal [Thu Aug 17 2006] [16:15:54] stacy: gppd with me, sounds like it is for the greater good. [Thu Aug 17 2006] [16:16:02] or are you ok with one of the prodops guys just making one up? [Thu Aug 17 2006] [16:16:19] iWolf, this will be much goodness afterwards [Thu Aug 17 2006] [16:16:30] * iWolf dreams of goodness [Thu Aug 17 2006] [16:16:31] also frees up a rack space on the floor for future needs ;) [Thu Aug 17 2006] [16:16:35] abadger1999: you want to do a static off line page [Thu Aug 17 2006] [16:16:46] or i can or anyone can really [Thu Aug 17 2006] [16:17:12] http://66.187.224.110/ [Thu Aug 17 2006] [16:17:21] we can use that and just modify the RHN centric info [Thu Aug 17 2006] [16:17:23] Would you be willing to? I'm juggling a few other responsibilities right now. [Thu Aug 17 2006] [16:17:25] to say fedora [Thu Aug 17 2006] [16:17:39] stacy: ill get you a static page [Thu Aug 17 2006] [16:17:42] ok [Thu Aug 17 2006] [16:19:01] I gotta run, I'll catchup later. adios [Thu Aug 17 2006] [16:19:16] I have to go [Thu Aug 17 2006] [16:19:22] ok [Thu Aug 17 2006] [16:19:30] so are we done? [Thu Aug 17 2006] [16:19:31] thanks everyone [Thu Aug 17 2006] [16:19:34] indeed thanks [Thu Aug 17 2006] [16:19:38] * stacy is away: I'm F@*&'n busy drinking a beer! [Thu Aug 17 2006] [16:19:40] Part stacy has left this channel ("Gone in search of beer"). From neuro at well.com Fri Aug 18 23:40:18 2006 From: neuro at well.com (William Anderson) Date: Sat, 19 Aug 2006 00:40:18 +0100 Subject: [Fedora-infrastructure-list] Meeting Log 2006-08-17 In-Reply-To: <200608181653.12742.dennis@ausil.us> References: <200608181653.12742.dennis@ausil.us> Message-ID: <44E64FE2.8000407@well.com> Dennis Gilmore wrote: > Hey guys, > > attached is the log from the meeting yesterday. We covered a fairly large > amount of things which was good. > > We really need someone to step up and replace pasqual with unifying the look > and feel of the websites. > > [snip] > [Thu Aug 17 2006] [15:03:23] Item 1 > [Thu Aug 17 2006] [15:03:51] we need a new person to step up and help with unifing the look and feel of our websites I can happily look at this if permitted :) -- _ __/| William Anderson | Tim: Your cheese game is strong. \`O_o' neuro at well dot com | Zane: My cheese game. It's all about the =(_ _)= http://neuro.me.uk/ | cheese platter. U - Thhbt! GPG 0xFA5F1100 | -- Tim Westwood, Zane Lowe, R1, Dec 2005 From mmcgrath at fedoraproject.org Sat Aug 19 15:40:20 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Sat, 19 Aug 2006 10:40:20 -0500 Subject: [Fedora-infrastructure-list] Welcome new people Message-ID: <3237e4410608190840l18607c5fo344d09a28445c767@mail.gmail.com> I've noticed many new people showing interest in our infrastructure and wanted to make sure to welcome everyone. If you haven't sent some sort of introduction email to the list feel free to do it. Also include exactly what stuff you're interested in working on. I've altered the schedule page: http://fedoraproject.org/wiki/Infrastructure/Schedule I've changed "owner" to "project leader" since really many of these tasks should be multi person. Also many people go to the project page and see that all the tasks are 'taken' not realizing that there's still much much work to be done. Anyone who has already taken leadership with one project I'd encourage a status report sent to the list if you're inters ted in some more hands on it. The multi-tier security stuff is coming soon so we should be able to open up our resources to more people without putting us at any additional risk :) To the new people, welcome. Most of our communication happens here, in the Thursday meetings or on the Wiki. The lay of the land is pretty simple, make sure you're vocal about what you want to work on and let the infrastructure-list/project leader know. People come and go all the time and any help that can be lended will be useful. Become familiar with the wiki page. If you have any questions feel free to ask me or anyone else on the list. It may seem like everything is taken but really everyone could use a hand from time to time. -Mike From rassylkaformazaj at ukr.net Sun Aug 20 14:56:16 2006 From: rassylkaformazaj at ukr.net (=?utf-8?Q?=D0=9C=D0=B0=D0=B7=D0=B0=D0=B9?=) Date: Sun, 20 Aug 2006 17:56:16 +0300 Subject: [Fedora-infrastructure-list] Welcome new people In-Reply-To: <3237e4410608190840l18607c5fo344d09a28445c767@mail.gmail.com> References: <3237e4410608190840l18607c5fo344d09a28445c767@mail.gmail.com> Message-ID: <05288194.20060820175616@ukr.net> Hello Mike, Thanks for your letter. I guess new people could save some time for "Leaders" for other job, or finish some projects faster. Just let us know ;) [dd] MM> I've changed "owner" to "project leader" since really many of these MM> tasks should be multi person. Also many people go to the project page MM> and see that all the tasks are 'taken' not realizing that there's MM> still much much work to be done. Anyone who has already taken MM> leadership with one project I'd encourage a status report sent to the MM> list if you're inters ted in some more hands on it. Or place a note in a Wiki if help is needed. MM> The multi-tier MM> security stuff is coming soon so we should be able to open up our MM> resources to more people without putting us at any additional risk :) MM> To the new people, welcome. Most of our communication happens here, MM> in the Thursday meetings or on the Wiki. The lay of the land is MM> pretty simple, make sure you're vocal about what you want to work on MM> and let the infrastructure-list/project leader know. People come and MM> go all the time and any help that can be lended will be useful. MM> Become familiar with the wiki page. If you have any questions feel MM> free to ask me or anyone else on the list. It may seem like MM> everything is taken but really everyone could use a hand from time to MM> time. From rmeggins at redhat.com Fri Aug 18 14:39:54 2006 From: rmeggins at redhat.com (Richard Megginson) Date: Fri, 18 Aug 2006 08:39:54 -0600 Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: <44E52DCB.3050306@redhat.com> References: <44E4E76D.8040509@redhat.com> <44E52DCB.3050306@redhat.com> Message-ID: <44E5D13A.6010308@redhat.com> Warren Togami wrote: > Max Spevack wrote: >>> >>> Our checkins to the /cvs/dirsec repository on cvs.fedora.redhat.com >>> usually end up sending commit messages to the >>> fedora-directory-commits mailing list. This notification mechanism >>> no longer seems to be working. I'm not sure when it stopped working >>> exactly, but the last notification that was received was on 08/09. >>> I have checked with some other team members, and they have >>> experienced the same thing. >>> >>> Is this a problem on the cvs server? >>> >>> Thanks, >>> -NGK >> > > /cvs/dirsec/CVSROOT/loginfo contains: > > DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} > cvsdirsec at fedora.redhat.com > > https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html > > This address goes through an alias to reach fedora-directory-commits > list. Looks like my test message hit the list without me being > subscribed, you don't have any spam problems? No, I don't think so. > I also see CVS mail from August 17th here, so mail is definitely > hitting the list. Are you sure your personal subscription or mail > filters aren't in error? I haven't changed mine. What's interesting is that I saw some commits from Bob Relyea in the coolkey project. But none from ldapserver. > > ^ldapserver $CVSROOT/CVSROOT/dolog.pl -r /cvs/dirsec > foxworth at redhat.com > > foxworth is no longer at the company, should this be redirected to > somebody else or deleted? Yes, it should be redirected. Could this be the problem? For now, send them to rmeggins at redhat.com > > Warren Togami > wtogami at redhat.com > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3178 bytes Desc: S/MIME Cryptographic Signature URL: From nkinder at redhat.com Fri Aug 18 15:20:32 2006 From: nkinder at redhat.com (Nathan Kinder) Date: Fri, 18 Aug 2006 08:20:32 -0700 Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: <44E5D13A.6010308@redhat.com> References: <44E4E76D.8040509@redhat.com> <44E52DCB.3050306@redhat.com> <44E5D13A.6010308@redhat.com> Message-ID: <44E5DAC0.5090403@redhat.com> Richard Megginson wrote: > Warren Togami wrote: >> Max Spevack wrote: >>>> >>>> Our checkins to the /cvs/dirsec repository on cvs.fedora.redhat.com >>>> usually end up sending commit messages to the >>>> fedora-directory-commits mailing list. This notification mechanism >>>> no longer seems to be working. I'm not sure when it stopped working >>>> exactly, but the last notification that was received was on 08/09. >>>> I have checked with some other team members, and they have >>>> experienced the same thing. >>>> >>>> Is this a problem on the cvs server? >>>> >>>> Thanks, >>>> -NGK >>> >> >> /cvs/dirsec/CVSROOT/loginfo contains: >> >> DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} >> cvsdirsec at fedora.redhat.com >> >> https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html >> >> This address goes through an alias to reach fedora-directory-commits >> list. Looks like my test message hit the list without me being >> subscribed, you don't have any spam problems? > No, I don't think so. >> I also see CVS mail from August 17th here, so mail is definitely >> hitting the list. Are you sure your personal subscription or mail >> filters aren't in error? > I haven't changed mine. What's interesting is that I saw some commits > from Bob Relyea in the coolkey project. But none from ldapserver. I saw exactly the same thing here. >> >> ^ldapserver $CVSROOT/CVSROOT/dolog.pl -r /cvs/dirsec >> foxworth at redhat.com >> >> foxworth is no longer at the company, should this be redirected to >> somebody else or deleted? > Yes, it should be redirected. Could this be the problem? For now, > send them to rmeggins at redhat.com I think this may be the problem. >> >> Warren Togami >> wtogami at redhat.com >> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3241 bytes Desc: S/MIME Cryptographic Signature URL: From email.ahmedkamal at googlemail.com Fri Aug 18 19:02:32 2006 From: email.ahmedkamal at googlemail.com (Ahmed Kamal) Date: Fri, 18 Aug 2006 22:02:32 +0300 Subject: [Fedora-infrastructure-list] Join the project Message-ID: <3da3b5b40608181202o152f9d13raf7eac6287d195ad@mail.gmail.com> Hi everyone, I would like to lend a helping hand to your project. I believe this is the best way since I am not primarily a programmer, and I just read an interview on /. saying Fedora doesn't need more packagers :) Here is a quick introduction: 1- My name is Ahmed Kamal. I live in Cairo, Egypt. I am 26 years old. 2- I have a degree in Electronics engineering. 3- I have done some scripting mainly perl, tcl/tk, awk and shell. 4- I currently work in Linux-plus.com as a system engineer, and I instruct RH253 course (I am an RHCE of course) 5- Since at work I do a lot of consulting for Egyptian companies, I tend to interact with a lot of stuff (networking, security, monitoring, email, ldap, ... pretty much everything) but then again, I can't claim to be an expert in any field. My main target for helping, is two fold, giving back to the community, and of course learning and leveraging my skill set interacting with a huge project such as fedora. Well, that's basically my introduction. I'd like to help. At least at first, I think I will only be able to help at weekends, so I'd rather focus on the nice to haves, over the immediately importants :) Viewing the schedule, there doesn't seem to be much priority 2 tasks, for priority 3 ones, maybe I can work on getting SSL support for fedoraproject.org. Let me know guys if I can work on that and how to start. Best Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugs.michael at gmx.net Tue Aug 22 08:44:36 2006 From: bugs.michael at gmx.net (Michael Schwendt) Date: Tue, 22 Aug 2006 10:44:36 +0200 Subject: [Fedora-infrastructure-list] when to use OTRS (Was: Re: FESCo, hello? - [was: Re: Buildsys status pages down]) In-Reply-To: References: <44C8F9BA.3050101@cora.nwra.com> <20060728220925.c65be643.bugs.michael@gmx.net> <44CA7498.4020609@leemhuis.info> Message-ID: <20060822104436.78357b5c.bugs.michael@gmx.net> On Fri, 28 Jul 2006 16:42:28 -0400, Elliot Lee wrote: > To help clarify things, yesterday I disabled new bug reports in > bugzilla's "Fedora Infrastructure" product. > > Most of the infrastructure issues lend themselves better to the > "report via e-mail and have an open issue for each person" model that > OTRS facilitates. Is it still the case that the reporters don't get any feedback nor status updates when tickets are closed? From nils at breun.nl Tue Aug 22 08:54:43 2006 From: nils at breun.nl (Nils Breunese) Date: Tue, 22 Aug 2006 10:54:43 +0200 Subject: [Fedora-infrastructure-list] when to use OTRS (Was: Re: FESCo, hello? - [was: Re: Buildsys status pages down]) In-Reply-To: <20060822104436.78357b5c.bugs.michael@gmx.net> References: <44C8F9BA.3050101@cora.nwra.com> <20060728220925.c65be643.bugs.michael@gmx.net> <44CA7498.4020609@leemhuis.info> <20060822104436.78357b5c.bugs.michael@gmx.net> Message-ID: Michael Schwendt wrote: > Is it still the case that the reporters don't get any feedback nor > status > updates when tickets are closed? In my own OTRS setup I reply to the 'customer' when closing a ticket and set the nexy ticket state to be 'closed succesfully'. It is also possible to setup notifications to the 'customer' upon certain state changes. In the current setup however it seems possible to just close a ticket without sending any notification. Either the 'agents' should be told to not close a ticket by just changing the state, but by sending a reply and setting the next state by that, or notifications for state changes to 'closed' should be set up. Nils Breunese. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Dit deel van het bericht is digitaal ondertekend URL: From mmcgrath at fedoraproject.org Tue Aug 22 12:25:01 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Tue, 22 Aug 2006 07:25:01 -0500 Subject: [Fedora-infrastructure-list] when to use OTRS (Was: Re: FESCo, hello? - [was: Re: Buildsys status pages down]) In-Reply-To: <20060822104436.78357b5c.bugs.michael@gmx.net> References: <44C8F9BA.3050101@cora.nwra.com> <20060728220925.c65be643.bugs.michael@gmx.net> <44CA7498.4020609@leemhuis.info> <20060822104436.78357b5c.bugs.michael@gmx.net> Message-ID: <3237e4410608220525p66e2d105w3f61c0772dd898bb@mail.gmail.com> On 8/22/06, Michael Schwendt wrote: > On Fri, 28 Jul 2006 16:42:28 -0400, Elliot Lee wrote: > > > To help clarify things, yesterday I disabled new bug reports in > > bugzilla's "Fedora Infrastructure" product. > > > > Most of the infrastructure issues lend themselves better to the > > "report via e-mail and have an open issue for each person" model that > > OTRS facilitates. > > Is it still the case that the reporters don't get any feedback nor status > updates when tickets are closed? > Its a process/training issue. I've been meaning to set up an automated response on close but haven't gotten around to it, rordway. Would you be interested in this? -Mike From nils at breun.nl Tue Aug 22 12:46:31 2006 From: nils at breun.nl (Nils Breunese) Date: Tue, 22 Aug 2006 14:46:31 +0200 Subject: [Fedora-infrastructure-list] when to use OTRS (Was: Re: FESCo, hello? - [was: Re: Buildsys status pages down]) In-Reply-To: <3237e4410608220525p66e2d105w3f61c0772dd898bb@mail.gmail.com> References: <44C8F9BA.3050101@cora.nwra.com> <20060728220925.c65be643.bugs.michael@gmx.net> <44CA7498.4020609@leemhuis.info> <20060822104436.78357b5c.bugs.michael@gmx.net> <3237e4410608220525p66e2d105w3f61c0772dd898bb@mail.gmail.com> Message-ID: <2A9BDD6E-2A65-4A0C-B1AE-1B0174B12B02@breun.nl> Mike McGrath wrote: > On 8/22/06, Michael Schwendt wrote: >> On Fri, 28 Jul 2006 16:42:28 -0400, Elliot Lee wrote: >> >> > To help clarify things, yesterday I disabled new bug reports in >> > bugzilla's "Fedora Infrastructure" product. >> > >> > Most of the infrastructure issues lend themselves better to the >> > "report via e-mail and have an open issue for each person" model >> that >> > OTRS facilitates. >> >> Is it still the case that the reporters don't get any feedback nor >> status >> updates when tickets are closed? >> > Its a process/training issue. I've been meaning to set up an > automated response on close but haven't gotten around to it, rordway. > Would you be interested in this? Check out http://doc.otrs.org/2.0/en/html/x991.html Nils Breunese. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Dit deel van het bericht is digitaal ondertekend URL: From mmcgrath at fedoraproject.org Wed Aug 23 13:02:47 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 23 Aug 2006 08:02:47 -0500 Subject: [Fedora-infrastructure-list] Stuff to do Message-ID: <3237e4410608230602x20447b7cycd6d5b7b6fc5a4d@mail.gmail.com> Hello everyone. For those looking for stuff to do, have a look at the ticketing system for open tickets. Many of these issues are still un-owned: https://admin.fedoraproject.org/tickets/customer.pl?Action=CustomerTicketOverView&SortBy=&Order=&Limit=&ShowClosedTickets=0&Type=CompanyTickets You must have a Fedora account to access this system. -Mike From mmcgrath at fedoraproject.org Wed Aug 23 13:57:56 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 23 Aug 2006 08:57:56 -0500 Subject: [Fedora-infrastructure-list] when to use OTRS (Was: Re: FESCo, hello? - [was: Re: Buildsys status pages down]) In-Reply-To: <3237e4410608220525p66e2d105w3f61c0772dd898bb@mail.gmail.com> References: <44C8F9BA.3050101@cora.nwra.com> <20060728220925.c65be643.bugs.michael@gmx.net> <44CA7498.4020609@leemhuis.info> <20060822104436.78357b5c.bugs.michael@gmx.net> <3237e4410608220525p66e2d105w3f61c0772dd898bb@mail.gmail.com> Message-ID: <3237e4410608230657q2e6e541blf641f086122a40df@mail.gmail.com> On 8/22/06, Mike McGrath wrote: > On 8/22/06, Michael Schwendt wrote: > > On Fri, 28 Jul 2006 16:42:28 -0400, Elliot Lee wrote: > > > > > To help clarify things, yesterday I disabled new bug reports in > > > bugzilla's "Fedora Infrastructure" product. > > > > > > Most of the infrastructure issues lend themselves better to the > > > "report via e-mail and have an open issue for each person" model that > > > OTRS facilitates. > > > > Is it still the case that the reporters don't get any feedback nor status > > updates when tickets are closed? > > Tickets now send a closed status update. Users are allowed to re-open tickets. This was actually enabled on most of the queues already, I'm not sure why some of them were disabled. Just a reminder to the admins working on tickets, use the email reply link to send emails to users. The "note" link is for internal notes only, end users won't see them. -Mike From mspevack at redhat.com Wed Aug 23 20:01:14 2006 From: mspevack at redhat.com (Max Spevack) Date: Wed, 23 Aug 2006 16:01:14 -0400 (EDT) Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: <44E5DAC0.5090403@redhat.com> References: <44E4E76D.8040509@redhat.com> <44E52DCB.3050306@redhat.com> <44E5D13A.6010308@redhat.com> <44E5DAC0.5090403@redhat.com> Message-ID: Did we ever resolve this problem? --Max On Fri, 18 Aug 2006, Nathan Kinder wrote: > Richard Megginson wrote: >> Warren Togami wrote: >>> Max Spevack wrote: >>>>> >>>>> Our checkins to the /cvs/dirsec repository on cvs.fedora.redhat.com >>>>> usually end up sending commit messages to the fedora-directory-commits >>>>> mailing list. This notification mechanism no longer seems to be working. >>>>> I'm not sure when it stopped working exactly, but the last notification >>>>> that was received was on 08/09. I have checked with some other team >>>>> members, and they have experienced the same thing. >>>>> >>>>> Is this a problem on the cvs server? >>>>> >>>>> Thanks, >>>>> -NGK >>>> >>> >>> /cvs/dirsec/CVSROOT/loginfo contains: >>> >>> DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} >>> cvsdirsec at fedora.redhat.com >>> >>> https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html >>> This address goes through an alias to reach fedora-directory-commits list. >>> Looks like my test message hit the list without me being subscribed, you >>> don't have any spam problems? >> No, I don't think so. >>> I also see CVS mail from August 17th here, so mail is definitely hitting >>> the list. Are you sure your personal subscription or mail filters aren't >>> in error? >> I haven't changed mine. What's interesting is that I saw some commits from >> Bob Relyea in the coolkey project. But none from ldapserver. > I saw exactly the same thing here. >>> >>> ^ldapserver $CVSROOT/CVSROOT/dolog.pl -r /cvs/dirsec >>> foxworth at redhat.com >>> >>> foxworth is no longer at the company, should this be redirected to >>> somebody else or deleted? >> Yes, it should be redirected. Could this be the problem? For now, send >> them to rmeggins at redhat.com > I think this may be the problem. >>> >>> Warren Togami >>> wtogami at redhat.com >>> > > -- Max Spevack + http://fedoraproject.org/wiki/MaxSpevack + gpg key -- http://spevack.org/max.asc + fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21 From mspevack at redhat.com Wed Aug 23 20:05:41 2006 From: mspevack at redhat.com (Max Spevack) Date: Wed, 23 Aug 2006 16:05:41 -0400 (EDT) Subject: [Fedora-infrastructure-list] fp.org email addresses coming up as spam Message-ID: Anyone else seen complaints of things like this? I have my settings quite low, and we're still getting flagged. 2.7 HELO_DYNAMIC_DHCP Relay HELO'd using suspicious hostname (DHCP) 3.3 HELO_DYNAMIC_HCC Relay HELO'd using suspicious hostname (HCC) http://www.google.com/search?q=HELO_DYNAMIC_DHCP Thought I'd throw this out there for anyone who's interested in doing some digging, see under what circumstances fp.o emails are triggering these flags. --Max ---------- Forwarded message ---------- Received: from localhost by mspevack.rdu.redhat.com with SpamAssassin (version 3.1.3); Wed, 23 Aug 2006 15:20:47 -0400 From: Jack Aboutboul To: Markster at digium.com Subject: *****SPAM***** Fedora and Asterisk Date: Wed, 23 Aug 2006 15:19:38 -0400 Message-Id: <1156360778.23913.8.camel at deepfort> X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on mspevack.rdu.redhat.com X-Spam-Level: ***** X-Spam-Status: Yes, score=5.9 required=5.0 tests=HELO_DYNAMIC_DHCP, HELO_DYNAMIC_HCC,UNPARSEABLE_RELAY autolearn=no version=3.1.3 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------=_44ECAA8F.C1433263" Spam detection software, running on the system "mspevack.rdu.redhat.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hey Mark, I am at Red Hat HQ for the week and part of our Fedora meetings have been regarding how we can help make Fedora a viable platform for innovation for certain key technologies which have the most potential. Naturally, voip came up and a number of people spoke about Asterisk and how we can work together with you guys. [...] Content analysis details: (5.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 2.7 HELO_DYNAMIC_DHCP Relay HELO'd using suspicious hostname (DHCP) 3.3 HELO_DYNAMIC_HCC Relay HELO'd using suspicious hostname (HCC) 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines From wtogami at redhat.com Wed Aug 23 20:17:33 2006 From: wtogami at redhat.com (Warren Togami) Date: Wed, 23 Aug 2006 16:17:33 -0400 Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: References: <44E4E76D.8040509@redhat.com> <44E52DCB.3050306@redhat.com> <44E5D13A.6010308@redhat.com> <44E5DAC0.5090403@redhat.com> Message-ID: <44ECB7DD.3050609@redhat.com> I thought I established that this was a problem on the receiver's end? Warren Max Spevack wrote: > Did we ever resolve this problem? > > --Max > > On Fri, 18 Aug 2006, Nathan Kinder wrote: > >> Richard Megginson wrote: >>> Warren Togami wrote: >>>> Max Spevack wrote: >>>>>> >>>>>> Our checkins to the /cvs/dirsec repository on >>>>>> cvs.fedora.redhat.com usually end up sending commit messages to >>>>>> the fedora-directory-commits mailing list. This notification >>>>>> mechanism no longer seems to be working. I'm not sure when it >>>>>> stopped working exactly, but the last notification that was >>>>>> received was on 08/09. I have checked with some other team >>>>>> members, and they have experienced the same thing. >>>>>> >>>>>> Is this a problem on the cvs server? >>>>>> >>>>>> Thanks, >>>>>> -NGK >>>>> >>>> >>>> /cvs/dirsec/CVSROOT/loginfo contains: >>>> >>>> DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} >>>> cvsdirsec at fedora.redhat.com >>>> >>>> https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html >>>> This address goes through an alias to reach fedora-directory-commits >>>> list. Looks like my test message hit the list without me being >>>> subscribed, you don't have any spam problems? >>> No, I don't think so. >>>> I also see CVS mail from August 17th here, so mail is definitely >>>> hitting the list. Are you sure your personal subscription or mail >>>> filters aren't in error? >>> I haven't changed mine. What's interesting is that I saw some >>> commits from Bob Relyea in the coolkey project. But none from >>> ldapserver. >> I saw exactly the same thing here. >>>> >>>> ^ldapserver $CVSROOT/CVSROOT/dolog.pl -r /cvs/dirsec >>>> foxworth at redhat.com >>>> >>>> foxworth is no longer at the company, should this be redirected to >>>> somebody else or deleted? >>> Yes, it should be redirected. Could this be the problem? For now, >>> send them to rmeggins at redhat.com >> I think this may be the problem. >>>> >>>> Warren Togami >>>> wtogami at redhat.com >>>> >> >> > From linux at elfshadow.net Wed Aug 23 21:25:40 2006 From: linux at elfshadow.net (Jeffrey Tadlock) Date: Wed, 23 Aug 2006 17:25:40 -0400 Subject: [Fedora-infrastructure-list] fp.org email addresses coming up as spam In-Reply-To: References: Message-ID: <44ECC7D4.8080608@elfshadow.net> Max Spevack wrote: > Anyone else seen complaints of things like this? I have my settings > quite low, and we're still getting flagged. > > 2.7 HELO_DYNAMIC_DHCP Relay HELO'd using suspicious hostname (DHCP) > 3.3 HELO_DYNAMIC_HCC Relay HELO'd using suspicious hostname (HCC) > > http://www.google.com/search?q=HELO_DYNAMIC_DHCP > > Thought I'd throw this out there for anyone who's interested in doing > some digging, see under what circumstances fp.o emails are triggering > these flags. The fedoraproject.org addresses are forwarding only. When someone sends an email from their fedoraproject.org account they are really setting the From/Reply To address in their email client to have replies sent back to their @fedoraproject.org address (which forwards to the email address they have setup in the Fedora Accounts System). They continue to use their own SMTP servers for the actual sending of the email. Their own SMTP servers used for sending email could potentially trigger spam filter flags. In this case it looks like the sender possibly sent the email from a server hosted on dynamic IP range (possibly a small home server or small business) and that is what triggered the spamassassin flags. --Jeffrey From wtogami at redhat.com Thu Aug 24 02:05:43 2006 From: wtogami at redhat.com (Warren Togami) Date: Wed, 23 Aug 2006 22:05:43 -0400 Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: <44ECBC77.30201@redhat.com> References: <44E4E76D.8040509@redhat.com> <44E52DCB.3050306@redhat.com> <44E5D13A.6010308@redhat.com> <44E5DAC0.5090403@redhat.com> <44ECB7DD.3050609@redhat.com> <44ECBC77.30201@redhat.com> Message-ID: <44ED0977.6080108@redhat.com> https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html Hmmm, OK I see that mail stopped on August 18th according to the archives here. There is something wrong on the CVS server side... but I suspect there has been more than one issue going on here. I will figure this out tomorrow. Warren Togami wtogami at redhat.com Nathan Kinder wrote: > Warren Togami wrote: >> I thought I established that this was a problem on the receiver's end? > The "dolog.pl" program spits out an error whenever anything is checked > into ldapserver. Here is the output: > > [nkinder at crunch ldapserver]$ cvs commit -lm "Test for commits mailing > list - ignore." pumpkin.pl > For more information on using the Fedora source code repositories, > please visit http://fedoraproject.org/wiki/UsingCvs > Enter passphrase for key '/home/nkinder/.ssh/id_rsa': > Checking in pumpkin.pl; > /cvs/dirsec/ldapserver/pumpkin.pl,v <-- pumpkin.pl > new revision: 1.5; previous revision: 1.4 > done > sh: /cvs/dirsec/CVSROOT/dolog.pl: No such file or directory > Running syncmail... > Mailing relnotes at fedoraproject.org... > ...syncmail done. > > -NGK >> >> Warren >> >> Max Spevack wrote: >>> Did we ever resolve this problem? >>> >>> --Max >>> >>> On Fri, 18 Aug 2006, Nathan Kinder wrote: >>> >>>> Richard Megginson wrote: >>>>> Warren Togami wrote: >>>>>> Max Spevack wrote: >>>>>>>> >>>>>>>> Our checkins to the /cvs/dirsec repository on >>>>>>>> cvs.fedora.redhat.com usually end up sending commit messages to >>>>>>>> the fedora-directory-commits mailing list. This notification >>>>>>>> mechanism no longer seems to be working. I'm not sure when it >>>>>>>> stopped working exactly, but the last notification that was >>>>>>>> received was on 08/09. I have checked with some other team >>>>>>>> members, and they have experienced the same thing. >>>>>>>> >>>>>>>> Is this a problem on the cvs server? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> -NGK >>>>>>> >>>>>> >>>>>> /cvs/dirsec/CVSROOT/loginfo contains: >>>>>> >>>>>> DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} >>>>>> cvsdirsec at fedora.redhat.com >>>>>> >>>>>> https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html >>>>>> This address goes through an alias to reach >>>>>> fedora-directory-commits list. Looks like my test message hit the >>>>>> list without me being subscribed, you don't have any spam problems? >>>>> No, I don't think so. >>>>>> I also see CVS mail from August 17th here, so mail is definitely >>>>>> hitting the list. Are you sure your personal subscription or mail >>>>>> filters aren't in error? >>>>> I haven't changed mine. What's interesting is that I saw some >>>>> commits from Bob Relyea in the coolkey project. But none from >>>>> ldapserver. >>>> I saw exactly the same thing here. >>>>>> >>>>>> ^ldapserver $CVSROOT/CVSROOT/dolog.pl -r /cvs/dirsec >>>>>> foxworth at redhat.com >>>>>> >>>>>> foxworth is no longer at the company, should this be redirected to >>>>>> somebody else or deleted? >>>>> Yes, it should be redirected. Could this be the problem? For now, >>>>> send them to rmeggins at redhat.com >>>> I think this may be the problem. >>>>>> >>>>>> Warren Togami >>>>>> wtogami at redhat.com >>>>>> >>>> >>>> >>> >> > From ryan.ordway at oregonstate.edu Thu Aug 24 02:36:36 2006 From: ryan.ordway at oregonstate.edu (Ryan Ordway) Date: Wed, 23 Aug 2006 19:36:36 -0700 Subject: [Fedora-infrastructure-list] meeting tomorrow In-Reply-To: <3237e4410608230602x20447b7cycd6d5b7b6fc5a4d@mail.gmail.com> References: <3237e4410608230602x20447b7cycd6d5b7b6fc5a4d@mail.gmail.com> Message-ID: <44ED10B4.6090707@oregonstate.edu> I may not be able to make the meeting tomorrow, I have a lunch meeting up in Portland. I'll catch up with the IRC logs afterwards. Still not much progress on metrics, I haven't had much bandwidth lately between OSU and a couple of consulting jobs. From mmcgrath at fedoraproject.org Thu Aug 24 21:01:31 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Thu, 24 Aug 2006 16:01:31 -0500 Subject: [Fedora-infrastructure-list] Infrastructure Package Management Message-ID: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> So in the meeting today we've discussed what to do about our package management. At present FC3 will be EOL'd in april(ish). At that time many of the packages we use in our environment will become out of date. So options are an upgrade to RHEL5 when it is released (which we aren't even done upgrading everything to RHEL4 yet), building and supporting our own repo, or try to foster support for centos.karan.org or https://extras.108.redhat.com/ As always this is an open discussion, I'd encourage anyone with ideas to participate. The meeting notes will be out shortly. -Mike From mmcgrath at fedoraproject.org Thu Aug 24 21:10:39 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Thu, 24 Aug 2006 16:10:39 -0500 Subject: [Fedora-infrastructure-list] Meeting log Aug-24-2006 Message-ID: <3237e4410608241410w7c2ee1e1m8550ede8faf6cee6@mail.gmail.com> Small meeting, not too many people were able to attend. The biggest item was package managment. -Mike -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: meeting.txt URL: From skvidal at linux.duke.edu Thu Aug 24 23:40:45 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Thu, 24 Aug 2006 19:40:45 -0400 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> Message-ID: <1156462845.2031.3.camel@cutter> On Thu, 2006-08-24 at 16:01 -0500, Mike McGrath wrote: > So in the meeting today we've discussed what to do about our package > management. At present FC3 will be EOL'd in april(ish). At that time > many of the packages we use in our environment will become out of > date. So options are an upgrade to RHEL5 when it is released (which > we aren't even done upgrading everything to RHEL4 yet), building and > supporting our own repo, or try to foster support for centos.karan.org > or https://extras.108.redhat.com/ > > As always this is an open discussion, I'd encourage anyone with ideas > to participate. The meeting notes will be out shortly. 1. how many packages do we use? (yum list extras should help with that) 2. are the newer versions of those packages in fc5 not workable for us? 3. If fedora extras cvs started making it possible for us to build and release RHEL/Centos 4 packages is anyone interested in helping maintain a branch for that distro? -sv From a.badger at gmail.com Thu Aug 24 23:43:45 2006 From: a.badger at gmail.com (Toshio Kuratomi) Date: Thu, 24 Aug 2006 16:43:45 -0700 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> Message-ID: <1156463025.2641.30.camel@localhost> On Thu, 2006-08-24 at 16:01 -0500, Mike McGrath wrote: > So in the meeting today we've discussed what to do about our package > management. At present FC3 will be EOL'd in april(ish). At that time > many of the packages we use in our environment will become out of > date. FC3 packages are already out of date, only FC5 and devel are consistently at close to the latest versions right now. When it goes EOL, they will start to have unfixed security holes as well as simply lagging relative to upstream version. > So options are an upgrade to RHEL5 when it is released (which > we aren't even done upgrading everything to RHEL4 yet), building and > supporting our own repo, or try to foster support for centos.karan.org > or https://extras.108.redhat.com/ > To some extent we are going to have to figure out how to keep packages updated separate from Fedora Extras unless we migrate to Fedora Core on the servers instead of RHEL. We are going to want the latest versions of some packages and they won't be available in the relevant FE release. It would be nice to be able to share resources and manpower with some other group, though. Currently, centos.karan.org and Extras have packages and infrastructure to provide updated packages. But there needs to be manpower (and possibly policy) to allow this. If we stayed within the Fedora Extras realm, I think we could continue to use the existing infrastructure (VCS, buildsystem, lookaside cache, etc) but we'd need to have separate targets RHELX or Infrastructure that branched from the packages in the Extras tree. Otherwise we'll conflict with Extras policies surrounding Legacy branches. We need to hear more from z00dax and quaid to evaluate what policies, manpower, or infrastructure limitations would exist to maintaining packages within the centos.karan.org or extra.108 space. -Toshio Note: I don't think it would be technically difficult to do this within Extras infrastructure and the planned additions to that infrastructure (package database, distributed vcs) should make this even easier. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From a.badger at gmail.com Thu Aug 24 23:48:34 2006 From: a.badger at gmail.com (Toshio Kuratomi) Date: Thu, 24 Aug 2006 16:48:34 -0700 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <1156462845.2031.3.camel@cutter> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> Message-ID: <1156463314.2641.35.camel@localhost> On Thu, 2006-08-24 at 19:40 -0400, seth vidal wrote: > 2. are the newer versions of those packages in fc5 not workable for us? > Some things like python had major version upgrades between fc3 and fc5. At minimum, we would have to rebuild the fc5 packages on fc3 to account for this. Some fc5 packages won't function with the older version at all (such as bzr). > 3. If fedora extras cvs started making it possible for us to build and > release RHEL/Centos 4 packages is anyone interested in helping maintain > a branch for that distro? > I can help maintain a branch for things we're working with in infrastructure. I don't run RHEL or Centos here, though. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From skvidal at linux.duke.edu Thu Aug 24 23:57:14 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Thu, 24 Aug 2006 19:57:14 -0400 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <1156463314.2641.35.camel@localhost> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> <1156463314.2641.35.camel@localhost> Message-ID: <1156463834.2031.17.camel@cutter> On Thu, 2006-08-24 at 16:48 -0700, Toshio Kuratomi wrote: > On Thu, 2006-08-24 at 19:40 -0400, seth vidal wrote: > > 2. are the newer versions of those packages in fc5 not workable for us? > > > Some things like python had major version upgrades between fc3 and fc5. > At minimum, we would have to rebuild the fc5 packages on fc3 to account > for this. Some fc5 packages won't function with the older version at > all (such as bzr). true. But the first thing to get a handle on is what we need to be taking care of. > > 3. If fedora extras cvs started making it possible for us to build and > > release RHEL/Centos 4 packages is anyone interested in helping maintain > > a branch for that distro? > > > I can help maintain a branch for things we're working with in > infrastructure. I don't run RHEL or Centos here, though. we have configs for mock for centos. So you can easily build the package in there. I build some almost everyday. -sv From mmcgrath at fedoraproject.org Fri Aug 25 00:05:58 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Thu, 24 Aug 2006 19:05:58 -0500 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <1156463834.2031.17.camel@cutter> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> <1156463314.2641.35.camel@localhost> <1156463834.2031.17.camel@cutter> Message-ID: <3237e4410608241705t5660319brb72de196fc1a0772@mail.gmail.com> On 8/24/06, seth vidal wrote: > On Thu, 2006-08-24 at 16:48 -0700, Toshio Kuratomi wrote: > > On Thu, 2006-08-24 at 19:40 -0400, seth vidal wrote: > > > 2. are the newer versions of those packages in fc5 not workable for us? > > > > > Some things like python had major version upgrades between fc3 and fc5. > > At minimum, we would have to rebuild the fc5 packages on fc3 to account > > for this. Some fc5 packages won't function with the older version at > > all (such as bzr). > > true. But the first thing to get a handle on is what we need to be > taking care of. > > > > > > 3. If fedora extras cvs started making it possible for us to build and > > > release RHEL/Centos 4 packages is anyone interested in helping maintain > > > a branch for that distro? > > > > > I can help maintain a branch for things we're working with in > > infrastructure. I don't run RHEL or Centos here, though. > > we have configs for mock for centos. > > So you can easily build the package in there. I build some almost > everyday. > > > -sv I'll go ahead and ask the question. If I proposed a Fedora Project called Fedora Enterprise or Fedora Enterprise Extras who here would help me maintain it? We could then merge Z00dax's current infrastructure and work with some of Fedora's stuff. With quaid's help we might get some support/buy-in from inside Red Hat. Operating completely independently of Extras or with them. Perhaps one of the branch requests could be "RHEL4" or "FEE4". (I'm not sure about how RH would feel about Fedora producing RH branded packages). We can open it up to extras maintainers and follow the same lifecycle of whatever branch we're creating. I'd be happy to write up some guidelines do the administrative tasks and all the overhead that would come along with a project like this. I'm not kidding myself, this is a lot of work but, IMHO, I think there's a real market out there not just inside of the FP Infrastructure. Ball of worms? Crazy Idea? Yeah, but its so crazy it just might work. Especially if we can leverage the knowledge and people we already have. Seth, I'm going to do an audit of the packages we're currently using or want to use and send them to the list tonight. -Mike From a.badger at gmail.com Fri Aug 25 00:38:10 2006 From: a.badger at gmail.com (Toshio Kuratomi) Date: Thu, 24 Aug 2006 17:38:10 -0700 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <1156463834.2031.17.camel@cutter> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> <1156463314.2641.35.camel@localhost> <1156463834.2031.17.camel@cutter> Message-ID: <1156466290.2641.38.camel@localhost> On Thu, 2006-08-24 at 19:57 -0400, seth vidal wrote: > On Thu, 2006-08-24 at 16:48 -0700, Toshio Kuratomi wrote: > > I can help maintain a branch for things we're working with in > > infrastructure. I don't run RHEL or Centos here, though. > > we have configs for mock for centos. > > So you can easily build the package in there. I build some almost > everyday. Yah. I was thinking more in terms of testing the packages once built :-). -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From mmcgrath at fedoraproject.org Fri Aug 25 01:03:24 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Thu, 24 Aug 2006 20:03:24 -0500 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <3237e4410608241705t5660319brb72de196fc1a0772@mail.gmail.com> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> <1156463314.2641.35.camel@localhost> <1156463834.2031.17.camel@cutter> <3237e4410608241705t5660319brb72de196fc1a0772@mail.gmail.com> Message-ID: <3237e4410608241803jc1ecd7dvdfdb63173fd062ae@mail.gmail.com> On 8/24/06, Mike McGrath wrote: > On 8/24/06, seth vidal wrote: > > On Thu, 2006-08-24 at 16:48 -0700, Toshio Kuratomi wrote: > > > On Thu, 2006-08-24 at 19:40 -0400, seth vidal wrote: > > I'll go ahead and ask the question. If I proposed a Fedora Project > called Fedora Enterprise or Fedora Enterprise Extras who here would > help me maintain it? > > We could then merge Z00dax's current infrastructure and work with some > of Fedora's stuff. With quaid's help we might get some support/buy-in > from inside Red Hat. Operating completely independently of Extras or > with them. Perhaps one of the branch requests could be "RHEL4" or > "FEE4". (I'm not sure about how RH would feel about Fedora producing > RH branded packages). We can open it up to extras maintainers and > follow the same lifecycle of whatever branch we're creating. I'd be > happy to write up some guidelines do the administrative tasks and all > the overhead that would come along with a project like this. I'm not > kidding myself, this is a lot of work but, IMHO, I think there's a > real market out there not just inside of the FP Infrastructure. > > Ball of worms? Crazy Idea? Yeah, but its so crazy it just might > work. Especially if we can leverage the knowledge and people we > already have. > > Seth, I'm going to do an audit of the packages we're currently using > or want to use and send them to the list tonight. > > -Mike > I talked to z00dax. He's in and thinks that he knows of others that would be interested from places like ATrpms and nrpms. He's also volunteered his infrastructure should this thing not take off in Fedora or through RH. We also think there should be different rules around this then the current extras packaging. While we'd both be creating packages I think our goals are different enough to warrant different rules, steering committees, etc. -Mike From skvidal at linux.duke.edu Fri Aug 25 12:00:55 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Fri, 25 Aug 2006 08:00:55 -0400 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <3237e4410608241803jc1ecd7dvdfdb63173fd062ae@mail.gmail.com> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> <1156463314.2641.35.camel@localhost> <1156463834.2031.17.camel@cutter> <3237e4410608241705t5660319brb72de196fc1a0772@mail.gmail.com> <3237e4410608241803jc1ecd7dvdfdb63173fd062ae@mail.gmail.com> Message-ID: <1156507255.2031.46.camel@cutter> On Thu, 2006-08-24 at 20:03 -0500, Mike McGrath wrote: > On 8/24/06, Mike McGrath wrote: > > On 8/24/06, seth vidal wrote: > > > On Thu, 2006-08-24 at 16:48 -0700, Toshio Kuratomi wrote: > > > > On Thu, 2006-08-24 at 19:40 -0400, seth vidal wrote: > > > > I'll go ahead and ask the question. If I proposed a Fedora Project > > called Fedora Enterprise or Fedora Enterprise Extras who here would > > help me maintain it? > > > > We could then merge Z00dax's current infrastructure and work with some > > of Fedora's stuff. With quaid's help we might get some support/buy-in > > from inside Red Hat. Operating completely independently of Extras or > > with them. Perhaps one of the branch requests could be "RHEL4" or > > "FEE4". (I'm not sure about how RH would feel about Fedora producing > > RH branded packages). We can open it up to extras maintainers and > > follow the same lifecycle of whatever branch we're creating. I'd be > > happy to write up some guidelines do the administrative tasks and all > > the overhead that would come along with a project like this. I'm not > > kidding myself, this is a lot of work but, IMHO, I think there's a > > real market out there not just inside of the FP Infrastructure. > > > > Ball of worms? Crazy Idea? Yeah, but its so crazy it just might > > work. Especially if we can leverage the knowledge and people we > > already have. > > > > Seth, I'm going to do an audit of the packages we're currently using > > or want to use and send them to the list tonight. > > > > -Mike > > > > I talked to z00dax. He's in and thinks that he knows of others that > would be interested from places like ATrpms and nrpms. He's also > volunteered his infrastructure should this thing not take off in > Fedora or through RH. We also think there should be different rules > around this then the current extras packaging. While we'd both be > creating packages I think our goals are different enough to warrant > different rules, steering committees, etc. The thing in fedora/rh for rhel extras has a fair bit of support behind it. Talk to Karsten Wade some. If we need it for some fedora infrastructure bits it just helps that initiative. Karsten, What was the last holdup on making rhel extras happen in the fedora cvs infrastructure? I think we've gotten co-maintenance out of the way. What was left? -sv From ryan.ordway at oregonstate.edu Fri Aug 25 17:27:46 2006 From: ryan.ordway at oregonstate.edu (Ryan Ordway) Date: Fri, 25 Aug 2006 10:27:46 -0700 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <3237e4410608241705t5660319brb72de196fc1a0772@mail.gmail.com> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> <1156463314.2641.35.camel@localhost> <1156463834.2031.17.camel@cutter> <3237e4410608241705t5660319brb72de196fc1a0772@mail.gmail.com> Message-ID: <1156526866.11186.168.camel@vodka.library.oregonstate.edu> On Thu, 2006-08-24 at 19:05 -0500, Mike McGrath wrote: > On 8/24/06, seth vidal wrote: > > On Thu, 2006-08-24 at 16:48 -0700, Toshio Kuratomi wrote: > > > On Thu, 2006-08-24 at 19:40 -0400, seth vidal wrote: > > > > 2. are the newer versions of those packages in fc5 not workable for us? > > > > > > > Some things like python had major version upgrades between fc3 and fc5. > > > At minimum, we would have to rebuild the fc5 packages on fc3 to account > > > for this. Some fc5 packages won't function with the older version at > > > all (such as bzr). > > > > true. But the first thing to get a handle on is what we need to be > > taking care of. > > > > > > > > > > 3. If fedora extras cvs started making it possible for us to build and > > > > release RHEL/Centos 4 packages is anyone interested in helping maintain > > > > a branch for that distro? > > > > > > > I can help maintain a branch for things we're working with in > > > infrastructure. I don't run RHEL or Centos here, though. > > > > we have configs for mock for centos. > > > > So you can easily build the package in there. I build some almost > > everyday. > > > > > > -sv > > I'll go ahead and ask the question. If I proposed a Fedora Project > called Fedora Enterprise or Fedora Enterprise Extras who here would > help me maintain it? I can help. I run both RHEL 4 and CentOS 4 on x86 and soon on amd64. > We could then merge Z00dax's current infrastructure and work with some > of Fedora's stuff. With quaid's help we might get some support/buy-in > from inside Red Hat. Operating completely independently of Extras or > with them. Perhaps one of the branch requests could be "RHEL4" or > "FEE4". (I'm not sure about how RH would feel about Fedora producing > RH branded packages). We can open it up to extras maintainers and > follow the same lifecycle of whatever branch we're creating. I'd be > happy to write up some guidelines do the administrative tasks and all > the overhead that would come along with a project like this. I'm not > kidding myself, this is a lot of work but, IMHO, I think there's a > real market out there not just inside of the FP Infrastructure. Hell yeah, I would love to be able to get "extras" for RHEL and CentOS. And I'm sure there are boatloads of other people that would as well. Ryan -- Ryan Ordway E-mail: ryan.ordway at oregonstate.edu Unix Systems Administrator rordway at library.oregonstate.edu Oregon State University Libraries 121 The Valley Library Office: The Valley Library #4657 Corvallis, OR 97331 Desk Phone: 541.737.8972 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From skvidal at linux.duke.edu Fri Aug 25 17:31:01 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Fri, 25 Aug 2006 13:31:01 -0400 Subject: [Fedora-infrastructure-list] Infrastructure Package Management In-Reply-To: <1156526866.11186.168.camel@vodka.library.oregonstate.edu> References: <3237e4410608241401o5db9d098i897c84e09f32ec33@mail.gmail.com> <1156462845.2031.3.camel@cutter> <1156463314.2641.35.camel@localhost> <1156463834.2031.17.camel@cutter> <3237e4410608241705t5660319brb72de196fc1a0772@mail.gmail.com> <1156526866.11186.168.camel@vodka.library.oregonstate.edu> Message-ID: <1156527061.7038.8.camel@cutter> On Fri, 2006-08-25 at 10:27 -0700, Ryan Ordway wrote: > On Thu, 2006-08-24 at 19:05 -0500, Mike McGrath wrote: > > On 8/24/06, seth vidal wrote: > > > On Thu, 2006-08-24 at 16:48 -0700, Toshio Kuratomi wrote: > > > > On Thu, 2006-08-24 at 19:40 -0400, seth vidal wrote: > > > > > 2. are the newer versions of those packages in fc5 not workable for us? > > > > > > > > > Some things like python had major version upgrades between fc3 and fc5. > > > > At minimum, we would have to rebuild the fc5 packages on fc3 to account > > > > for this. Some fc5 packages won't function with the older version at > > > > all (such as bzr). > > > > > > true. But the first thing to get a handle on is what we need to be > > > taking care of. > > > > > > > > > > > > > > 3. If fedora extras cvs started making it possible for us to build and > > > > > release RHEL/Centos 4 packages is anyone interested in helping maintain > > > > > a branch for that distro? > > > > > > > > > I can help maintain a branch for things we're working with in > > > > infrastructure. I don't run RHEL or Centos here, though. > > > > > > we have configs for mock for centos. > > > > > > So you can easily build the package in there. I build some almost > > > everyday. > > > > > > > > > -sv > > > > I'll go ahead and ask the question. If I proposed a Fedora Project > > called Fedora Enterprise or Fedora Enterprise Extras who here would > > help me maintain it? > > I can help. I run both RHEL 4 and CentOS 4 on x86 and soon on amd64. > > > We could then merge Z00dax's current infrastructure and work with some > > of Fedora's stuff. With quaid's help we might get some support/buy-in > > from inside Red Hat. Operating completely independently of Extras or > > with them. Perhaps one of the branch requests could be "RHEL4" or > > "FEE4". (I'm not sure about how RH would feel about Fedora producing > > RH branded packages). We can open it up to extras maintainers and > > follow the same lifecycle of whatever branch we're creating. I'd be > > happy to write up some guidelines do the administrative tasks and all > > the overhead that would come along with a project like this. I'm not > > kidding myself, this is a lot of work but, IMHO, I think there's a > > real market out there not just inside of the FP Infrastructure. > > Hell yeah, I would love to be able to get "extras" for RHEL and CentOS. > And I'm sure there are boatloads of other people that would as well. > Then help on the enterprise extras project that quaid (on irc) is trying to get rolling. please! -sv From nkinder at redhat.com Wed Aug 23 20:37:11 2006 From: nkinder at redhat.com (Nathan Kinder) Date: Wed, 23 Aug 2006 13:37:11 -0700 Subject: [Fedora-infrastructure-list] Re: Fedora CVS - Not sending out commit messages In-Reply-To: <44ECB7DD.3050609@redhat.com> References: <44E4E76D.8040509@redhat.com> <44E52DCB.3050306@redhat.com> <44E5D13A.6010308@redhat.com> <44E5DAC0.5090403@redhat.com> <44ECB7DD.3050609@redhat.com> Message-ID: <44ECBC77.30201@redhat.com> Warren Togami wrote: > I thought I established that this was a problem on the receiver's end? The "dolog.pl" program spits out an error whenever anything is checked into ldapserver. Here is the output: [nkinder at crunch ldapserver]$ cvs commit -lm "Test for commits mailing list - ignore." pumpkin.pl For more information on using the Fedora source code repositories, please visit http://fedoraproject.org/wiki/UsingCvs Enter passphrase for key '/home/nkinder/.ssh/id_rsa': Checking in pumpkin.pl; /cvs/dirsec/ldapserver/pumpkin.pl,v <-- pumpkin.pl new revision: 1.5; previous revision: 1.4 done sh: /cvs/dirsec/CVSROOT/dolog.pl: No such file or directory Running syncmail... Mailing relnotes at fedoraproject.org... ...syncmail done. -NGK > > Warren > > Max Spevack wrote: >> Did we ever resolve this problem? >> >> --Max >> >> On Fri, 18 Aug 2006, Nathan Kinder wrote: >> >>> Richard Megginson wrote: >>>> Warren Togami wrote: >>>>> Max Spevack wrote: >>>>>>> >>>>>>> Our checkins to the /cvs/dirsec repository on >>>>>>> cvs.fedora.redhat.com usually end up sending commit messages to >>>>>>> the fedora-directory-commits mailing list. This notification >>>>>>> mechanism no longer seems to be working. I'm not sure when it >>>>>>> stopped working exactly, but the last notification that was >>>>>>> received was on 08/09. I have checked with some other team >>>>>>> members, and they have experienced the same thing. >>>>>>> >>>>>>> Is this a problem on the cvs server? >>>>>>> >>>>>>> Thanks, >>>>>>> -NGK >>>>>> >>>>> >>>>> /cvs/dirsec/CVSROOT/loginfo contains: >>>>> >>>>> DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv} >>>>> cvsdirsec at fedora.redhat.com >>>>> >>>>> https://www.redhat.com/archives/fedora-directory-commits/2006-August/thread.html >>>>> This address goes through an alias to reach >>>>> fedora-directory-commits list. Looks like my test message hit the >>>>> list without me being subscribed, you don't have any spam problems? >>>> No, I don't think so. >>>>> I also see CVS mail from August 17th here, so mail is definitely >>>>> hitting the list. Are you sure your personal subscription or mail >>>>> filters aren't in error? >>>> I haven't changed mine. What's interesting is that I saw some >>>> commits from Bob Relyea in the coolkey project. But none from >>>> ldapserver. >>> I saw exactly the same thing here. >>>>> >>>>> ^ldapserver $CVSROOT/CVSROOT/dolog.pl -r /cvs/dirsec >>>>> foxworth at redhat.com >>>>> >>>>> foxworth is no longer at the company, should this be redirected to >>>>> somebody else or deleted? >>>> Yes, it should be redirected. Could this be the problem? For now, >>>> send them to rmeggins at redhat.com >>> I think this may be the problem. >>>>> >>>>> Warren Togami >>>>> wtogami at redhat.com >>>>> >>> >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3241 bytes Desc: S/MIME Cryptographic Signature URL: From splinux at fedoraproject.org Sat Aug 26 17:11:28 2006 From: splinux at fedoraproject.org (Damien Durand) Date: Sat, 26 Aug 2006 19:11:28 +0200 Subject: [Fedora-infrastructure-list] A cvs space for the Usability Sig Message-ID: Hello, I would like to ask for a cvs space for the Usability Sig so as to host temporarily some documentations, codes and patches, allowing a more efficient and productive work. Thanks in advance Damien Durand -------------- next part -------------- An HTML attachment was scrubbed... URL: From rassylkaformazaj at ukr.net Sat Aug 26 22:04:54 2006 From: rassylkaformazaj at ukr.net (=?utf-8?Q?=D0=9C=D0=B0=D0=B7=D0=B0=D0=B9?=) Date: Sun, 27 Aug 2006 01:04:54 +0300 Subject: [Fedora-infrastructure-list] Stuff to do In-Reply-To: <3237e4410608230602x20447b7cycd6d5b7b6fc5a4d@mail.gmail.com> References: <3237e4410608230602x20447b7cycd6d5b7b6fc5a4d@mail.gmail.com> Message-ID: <462312005.20060827010454@ukr.net> Hello Mike, Having these days a bit rest, I missed some interesting objects. "For those looking for stuff to do, have a look at the ticketing system for open tickets." I have already account ("mazaj", aka Dmitry Lisnichenko) but when I try to access the page of OTRS I see "Error: Need CustomerID!!!" and none of thing I can work on. Also I missed to reply on "[15:07:22] any new people ou there?". Hello! I am here :)).. Sorry for delayed reply ;) Wednesday, August 23, 2006, 4:02:47 PM, you wrote: MM> Hello everyone. For those looking for stuff to do, have a look at the MM> ticketing system for open tickets. Many of these issues are still MM> un-owned: MM> https://admin.fedoraproject.org/tickets/customer.pl?Action=CustomerTicketOverView&SortBy=&Order=&Limit=&ShowClosedTickets=0&Type=CompanyTickets MM> You must have a Fedora account to access this system. MM> -Mike -- ? ?????????, ?????. MAZ-RIPE mailto:rassylkaformazaj at ukr.net From nman64 at n-man.com Sun Aug 27 05:52:09 2006 From: nman64 at n-man.com (Patrick W. Barnes) Date: Sun, 27 Aug 2006 00:52:09 -0500 Subject: [Fedora-infrastructure-list] A cvs space for the Usability Sig In-Reply-To: References: Message-ID: <200608270052.11290.nman64@n-man.com> On Saturday 26 August 2006 12:11, "Damien Durand" wrote: > > I would like to ask for a cvs space for the Usability Sig so as to host > temporarily some documentations, codes and patches, allowing a more > efficient and productive work. > CVS isn't for temporary storage. You need to work with other projects to keep things where they belong. Documentation should be kept in packages, with the Documentation Project, or on the wiki. Patches should be provided through Bugzilla to appropriate maintainers or directly to upstream. Efficiency is achieved through collaboration and management, not version control. Unless the Usability SIG starts producing stand-alone packages, and I don't see any reason that it ever should, I can't imagine why it would have any real need for its own CVS repository. -- Patrick "The N-Man" Barnes nman64 at n-man.com http://www.n-man.com/ LinkedIn: http://www.linkedin.com/in/nman64 Have I been helpful? Rate my assistance! http://rate.affero.net/nman64/ -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mmcgrath at fedoraproject.org Sun Aug 27 16:12:31 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Sun, 27 Aug 2006 11:12:31 -0500 Subject: [Fedora-infrastructure-list] A cvs space for the Usability Sig In-Reply-To: <200608270052.11290.nman64@n-man.com> References: <200608270052.11290.nman64@n-man.com> Message-ID: <3237e4410608270912y616ecb5etc403ea3f7c52d87d@mail.gmail.com> On 8/27/06, Patrick W. Barnes wrote: > On Saturday 26 August 2006 12:11, "Damien Durand" > wrote: > > > > I would like to ask for a cvs space for the Usability Sig so as to host > > temporarily some documentations, codes and patches, allowing a more > > efficient and productive work. > > > > CVS isn't for temporary storage. You need to work with other projects to keep > things where they belong. Documentation should be kept in packages, with the > Documentation Project, or on the wiki. Patches should be provided through > Bugzilla to appropriate maintainers or directly to upstream. Efficiency is > achieved through collaboration and management, not version control. > > Unless the Usability SIG starts producing stand-alone packages, and I don't > see any reason that it ever should, I can't imagine why it would have any > real need for its own CVS repository. I have to agree with patrick on this, can you give very specific examples of what the CVS is going to be used for and why what currently exists is insufficient? -Mike From splinux at fedoraproject.org Sun Aug 27 16:21:46 2006 From: splinux at fedoraproject.org (Damien Durand) Date: Sun, 27 Aug 2006 18:21:46 +0200 Subject: Fwd: [Fedora-infrastructure-list] A cvs space for the Usability Sig In-Reply-To: References: <200608270052.11290.nman64@n-man.com> Message-ID: ---------- Forwarded message ---------- From: Damien Durand Date: 27 ao?t 2006 12:18 Subject: Re: [Fedora-infrastructure-list] A cvs space for the Usability Sig To: "Patrick W. Barnes" Hi, "temporary storage" aren't the good words, I'm actually starting an application for "Fedora Usability" called "fusability". It's like bug-buddy but allow to produce usability repports. Yes actually I can host this on a my web access because it's not usable. Bugzilla allow to conserve patchs or other? I don't think that it's the best solution but now that can be acceptable because the Usability Sigs has an existance of 2 weeks. The "Usability packages" is a good idea, We can produce "unofficial" packages for testing the application massively... I'm agree with you, cvs is not essential actually because usability is too young but that can be good for a efficient and productive work. Send the sources by mail etc... is not really great. 2006/8/27, Patrick W. Barnes : > On Saturday 26 August 2006 12:11, "Damien Durand" < > splinux at fedoraproject.org> > wrote: > > > > I would like to ask for a cvs space for the Usability Sig so as to host > > temporarily some documentations, codes and patches, allowing a more > > efficient and productive work. > > > > CVS isn't for temporary storage. You need to work with other projects to > keep > things where they belong. Documentation should be kept in packages, with > the > Documentation Project, or on the wiki. Patches should be provided through > Bugzilla to appropriate maintainers or directly to upstream. Efficiency > is > achieved through collaboration and management, not version control. > > Unless the Usability SIG starts producing stand-alone packages, and I > don't > see any reason that it ever should, I can't imagine why it would have any > real need for its own CVS repository. > > -- > Patrick "The N-Man" Barnes > nman64 at n-man.com > > http://www.n-man.com/ > > LinkedIn: > http://www.linkedin.com/in/nman64 > > Have I been helpful? Rate my assistance! > http://rate.affero.net/nman64/ > -- > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtogami at redhat.com Mon Aug 28 18:44:32 2006 From: wtogami at redhat.com (Warren Togami) Date: Mon, 28 Aug 2006 14:44:32 -0400 Subject: [Fedora-infrastructure-list] Partitioning for New Servers Message-ID: <44F33990.5030304@redhat.com> RH Kernel Engineer Rik van Riel recommended that we use LVM on our new servers for flexibility in both the host and guest partitions. If we reserve two non-LVM partitions on the primary system disk, then we will be able to safely remote install a new OS later. We can boot anaconda automated with kickstart or driven with VNC and reinstall without harming the existing OS. If we fail, simply fallback thanks to grub savedefault --once. After install, grub chainloading to the second /boot can boot the second OS. After we confirm the new OS is working fine, we can blow away the original host OS and reclaim the space thanks to LVM. The purchased Dell box has four disks. The donated Dell box has two disks. Here's how I envision the first two disks would be partitioned: /dev/sda1 /dev/sdb1 => /dev/md1 /boot 200MB /dev/sda2 /dev/sdb2 => /dev/md2 /boot2 200MB (reserved for later) /dev/sda3 /dev/sdb3 => /dev/md3 vg0 LVM vg0 contains: swap 2GB / 10GB for host OS All remaining space can be allocated later for Xen guests or to grow the root partition of the host as needed. The server with the additional two disks can software RAID-1 the entire disk, and provide additional flexible storage as vg1 LVM. Xen guests can go on either vg0 or vg1. We can migrate stuff as needed to balance I/O load. Due to instability of Xen in rawhide in the short-term, we should avoid upgrading the host OS until it has stabilized as we approach FC6-final. It should be relatively safe because the host OS is running only sshd and is accessible only via bastion. Later we will be able to safely install a host into another LVM partition to see if it runs our guests, so risk and hassle is really minimal here. This is just ideas from my head. If anybody here has better ideas please suggest. Warren Togami wtogami at redhat.com From mmcgrath at fedoraproject.org Mon Aug 28 18:53:21 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Mon, 28 Aug 2006 13:53:21 -0500 Subject: [Fedora-infrastructure-list] Partitioning for New Servers In-Reply-To: <44F33990.5030304@redhat.com> References: <44F33990.5030304@redhat.com> Message-ID: <3237e4410608281153h60861103r8908727ab2e2456@mail.gmail.com> On 8/28/06, Warren Togami wrote: > RH Kernel Engineer Rik van Riel recommended that we use LVM on our new > servers for flexibility in both the host and guest partitions. > > If we reserve two non-LVM partitions on the primary system disk, then we > will be able to safely remote install a new OS later. We can boot > anaconda automated with kickstart or driven with VNC and reinstall > without harming the existing OS. If we fail, simply fallback thanks to > grub savedefault --once. After install, grub chainloading to the second > /boot can boot the second OS. After we confirm the new OS is working > fine, we can blow away the original host OS and reclaim the space thanks > to LVM. > > The purchased Dell box has four disks. > The donated Dell box has two disks. > > Here's how I envision the first two disks would be partitioned: > /dev/sda1 /dev/sdb1 => /dev/md1 /boot 200MB > /dev/sda2 /dev/sdb2 => /dev/md2 /boot2 200MB (reserved for later) > /dev/sda3 /dev/sdb3 => /dev/md3 vg0 LVM > > vg0 contains: > swap 2GB > / 10GB for host OS > > All remaining space can be allocated later for Xen guests or to grow the > root partition of the host as needed. > > The server with the additional two disks can software RAID-1 the entire > disk, and provide additional flexible storage as vg1 LVM. Xen guests > can go on either vg0 or vg1. We can migrate stuff as needed to balance > I/O load. > > Due to instability of Xen in rawhide in the short-term, we should avoid > upgrading the host OS until it has stabilized as we approach FC6-final. > It should be relatively safe because the host OS is running only sshd > and is accessible only via bastion. Later we will be able to safely > install a host into another LVM partition to see if it runs our guests, > so risk and hassle is really minimal here. > > This is just ideas from my head. If anybody here has better ideas > please suggest. > > Warren Togami > wtogami at redhat.com > WORKSFORME, I've done similar things with my Xen servers. -Mike From wtogami at redhat.com Mon Aug 28 20:07:31 2006 From: wtogami at redhat.com (Warren Togami) Date: Mon, 28 Aug 2006 16:07:31 -0400 Subject: Fwd: [Fedora-infrastructure-list] A cvs space for the Usability Sig In-Reply-To: References: <200608270052.11290.nman64@n-man.com> Message-ID: <44F34D03.1000205@redhat.com> Damien Durand wrote: > > > ---------- Forwarded message ---------- > From: *Damien Durand* > > Date: 27 ao?t 2006 12:18 > Subject: Re: [Fedora-infrastructure-list] A cvs space for the Usability Sig > To: "Patrick W. Barnes" > > > Hi, > > "temporary storage" aren't the good words, I'm actually starting an > application for "Fedora Usability" called "fusability". It's like > bug-buddy but allow to produce usability repports. Yes actually I can > host this on a my web access because it's not usable. > > Bugzilla allow to conserve patchs or other? I don't think that it's the > best solution but now that can be acceptable because the Usability Sigs > has an existance of 2 weeks. > > The "Usability packages" is a good idea, We can produce "unofficial" > packages for testing the application massively... > > I'm agree with you, cvs is not essential actually because usability is > too young but that can be good for a efficient and productive work. Send > the sources by mail etc... is not really great. If your goal is unofficial side packages for usability, it may be best to wait for the next generation VCS that we hope to deploy before FC7. It will be one of the distributed VCS, which is extremely well suited for these kind of temporary branches. It could be done then with far less ugliness. Please do the best you can with Bugzilla, Wiki's and 3rd hosted space until then. Warren Togami wtogami at redhat.com From email.ahmedkamal at googlemail.com Mon Aug 28 23:10:40 2006 From: email.ahmedkamal at googlemail.com (Ahmed Kamal) Date: Tue, 29 Aug 2006 02:10:40 +0300 Subject: [Fedora-infrastructure-list] GPG key server Message-ID: <3da3b5b40608281610x672172cfgcd43243aa09dab86@mail.gmail.com> Hi, I am a new member. While registering my gpg key to pgp.mit.edu, it would not accept my key!! The problem turns out that it doesn't understand GPG keys with a photo-ID. After some googling, it turns out: 1- pgp.mit.edu doesnot accept some key formats 2- pgp.mit.edu mangles other keys 3- hkp://subkeys.pgp.net is a much better alternative, as it load balances over many physical servers 4- hkp://subkeys.pgp.net is the chosen default server now in GnuPG configuration. I am suggesting recommending that server on the web pages http://fedoraproject.org/wiki/Infrastructure/AccountSystem/NewAccount http://fedoraproject.org/wiki/DocsProject/UsingGpg/CreatingKeys Best Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From splinux at fedoraproject.org Mon Aug 28 23:24:23 2006 From: splinux at fedoraproject.org (Damien Durand) Date: Tue, 29 Aug 2006 01:24:23 +0200 Subject: Fwd: [Fedora-infrastructure-list] A cvs space for the Usability Sig In-Reply-To: <44F34D03.1000205@redhat.com> References: <200608270052.11290.nman64@n-man.com> <44F34D03.1000205@redhat.com> Message-ID: Sorry for the confusion in my previous mails. Well, I spoke with the Usability team about a cvs space and I'm able to provide somes answers and what we need. First, one of goals of the Usability sig is to redefine the system-config-* tools and Fedora applications for more intuitivity, accessibility... and more. The problem is that the system-config-* tools are hosted on the red hat cvs. We don't an acces or provide somes modifications to this cvs and we don't have an acces to it. It would be better that Fedora Usability has its own cvs space not to interfere with RH's work and to ease the collaboration between Fedora Usability contributors, and by consequent hosted some documentations, patchs and other tools related to usability. Next, cvs provide a good quality of work, with this we can work efficient and obtained a productive work. Currently, we're exchanging sources through mails which is not a solution. We also need an usability component on Bugzilla, to collect requests and bug reports from users. Then an usability group in the fedora account system will help to shape the organisation of the project and to restrain cvs acces to registered contributors. Thanks for your patience, Damien Durand 2006/8/28, Warren Togami : > > Damien Durand wrote: > > > > > > ---------- Forwarded message ---------- > > From: *Damien Durand* > > > > Date: 27 ao?t 2006 12:18 > > Subject: Re: [Fedora-infrastructure-list] A cvs space for the Usability > Sig > > To: "Patrick W. Barnes" < nman64 at n-man.com > > > > > Hi, > > > > "temporary storage" aren't the good words, I'm actually starting an > > application for "Fedora Usability" called "fusability". It's like > > bug-buddy but allow to produce usability repports. Yes actually I can > > host this on a my web access because it's not usable. > > > > Bugzilla allow to conserve patchs or other? I don't think that it's the > > best solution but now that can be acceptable because the Usability Sigs > > has an existance of 2 weeks. > > > > The "Usability packages" is a good idea, We can produce "unofficial" > > packages for testing the application massively... > > > > I'm agree with you, cvs is not essential actually because usability is > > too young but that can be good for a efficient and productive work. Send > > > the sources by mail etc... is not really great. > > If your goal is unofficial side packages for usability, it may be best > to wait for the next generation VCS that we hope to deploy before FC7. > It will be one of the distributed VCS, which is extremely well suited > for these kind of temporary branches. It could be done then with far > less ugliness. > > Please do the best you can with Bugzilla, Wiki's and 3rd hosted space > until then. > > Warren Togami > wtogami at redhat.com > > _______________________________________________ > Fedora-infrastructure-list mailing list > Fedora-infrastructure-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt_Domsch at dell.com Tue Aug 29 00:00:58 2006 From: Matt_Domsch at dell.com (Matt Domsch) Date: Mon, 28 Aug 2006 19:00:58 -0500 Subject: [Fedora-infrastructure-list] GPG key server In-Reply-To: <3da3b5b40608281610x672172cfgcd43243aa09dab86@mail.gmail.com> References: <3da3b5b40608281610x672172cfgcd43243aa09dab86@mail.gmail.com> Message-ID: <20060829000058.GA10490@lists.us.dell.com> On Tue, Aug 29, 2006 at 02:10:40AM +0300, Ahmed Kamal wrote: > Hi, > > I am a new member. While registering my gpg key to pgp.mit.edu, it > would not accept my key!! The problem turns out that it doesn't understand > GPG keys with a photo-ID. After some googling, it turns out: > 1- pgp.mit.edu doesnot accept some key formats > 2- pgp.mit.edu mangles other keys > 3- hkp://subkeys.pgp.net is a much better alternative, as it load balances > over many physical servers > 4- hkp://subkeys.pgp.net is the chosen default server now in GnuPG > configuration. > > I am suggesting recommending that server on the web pages > http://fedoraproject.org/wiki/Infrastructure/AccountSystem/NewAccount > http://fedoraproject.org/wiki/DocsProject/UsingGpg/CreatingKeys +1. The OLS keysignings recommended subkeys.pgp.net as well. They should all sync to each other eventually. -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com From toshio at tiki-lounge.com Tue Aug 29 05:13:17 2006 From: toshio at tiki-lounge.com (Toshio Kuratomi) Date: Mon, 28 Aug 2006 22:13:17 -0700 Subject: [Fedora-infrastructure-list] Package DB TurboGears/SQLObject schema Message-ID: <1156828397.3098.3.camel@localhost> Greetings all, Elliot in particular, I started to parse the owners.list file in preparation for setting up some sort of ACL system on the new VCS and decided to look into how this is going to interact with the PackageDB. For starters, I took the TurboGears schema that Elliot posted and added comments. Are the comments in this file accurate? Can you explain what the "status" fields in the *History classes represent? -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: pkgdb-schema.py Type: text/x-python Size: 5772 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From wtogami at redhat.com Tue Aug 29 23:16:45 2006 From: wtogami at redhat.com (Warren Togami) Date: Tue, 29 Aug 2006 19:16:45 -0400 Subject: [Fedora-infrastructure-list] Yum mirror list is safe from outage Message-ID: <44F4CADD.8020409@redhat.com> I just talked with Matthew Galgoci and confirmed that... - fedora.redhat.com where FC5 and earlier default mirror lists are located are not a proxy redirector, and should survive the duration of the outage. - download.fedora.redhat.com are also unaffected by the outage. So we should be fine on that front. Pretty much only development infrastructure will be down, I think? Warren Togami wtogami at redhat.com From sbranden at redhat.com Tue Aug 29 23:38:22 2006 From: sbranden at redhat.com (Stacy J. Brandenburg) Date: Tue, 29 Aug 2006 19:38:22 -0400 Subject: [Fedora-infrastructure-list] Yum mirror list is safe from outage In-Reply-To: <44F4CADD.8020409@redhat.com> References: <44F4CADD.8020409@redhat.com> Message-ID: <44F4CFEE.9090201@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Correct. Also it will be down 1 or 2 servers at a time. We will move the DB/Proxy/App servers, and if we have time the HAM/CVS/PPC machines as well. I may have missed a few, but we will try to do as many as we can during that window. If you can - set your DNS to 300 sec or so tonight so caches update. Then tomorrow as we move things, we will provide you a IP to shift the DNS to. I am sorry but I do not have it handy or I would post it.... Warren, lets do the discussions on the open IRC server, rather than devserv. That way others can play along. Talk to you more tomorrow! Warren Togami wrote: | I just talked with Matthew Galgoci and confirmed that... | | - fedora.redhat.com where FC5 and earlier default mirror lists are | located are not a proxy redirector, and should survive the duration of | the outage. | - download.fedora.redhat.com are also unaffected by the outage. | | So we should be fine on that front. Pretty much only development | infrastructure will be down, I think? | | Warren Togami | wtogami at redhat.com | | _______________________________________________ | Fedora-infrastructure-list mailing list | Fedora-infrastructure-list at redhat.com | https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list - -- ======================================================== = Stacy J. Brandenburg Red Hat Inc. = = Manager, Network Operations sbranden at redhat.com = = 919-754-4313 http://www.redhat.com = ======================================================== Fingerprint 03F7 43BE 1150 CCFA F57B 54DD AEDB 1C27 1828 D94D -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFE9M/urtscJxgo2U0RAth+AKCjPgfwABahzj+f4rqqXsmWNOujpgCdEDrj WSQroF1BNp31K/Ds83PBUj4= =BFCS -----END PGP SIGNATURE----- From wtogami at redhat.com Tue Aug 29 23:48:47 2006 From: wtogami at redhat.com (Warren Togami) Date: Tue, 29 Aug 2006 19:48:47 -0400 Subject: [Fedora-infrastructure-list] Yum mirror list is safe from outage In-Reply-To: <44F4CFEE.9090201@redhat.com> References: <44F4CADD.8020409@redhat.com> <44F4CFEE.9090201@redhat.com> Message-ID: <44F4D25F.7090200@redhat.com> Stacy J. Brandenburg wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Correct. > > Also it will be down 1 or 2 servers at a time. We will move the > DB/Proxy/App servers, and if we have time the HAM/CVS/PPC machines as > well. I may have missed a few, but we will try to do as many as we can > during that window. > > If you can - set your DNS to 300 sec or so tonight so caches update. > Then tomorrow as we move things, we will provide you a IP to shift the > DNS to. I am sorry but I do not have it handy or I would post it.... I am a little confused. IP addresses will change in this move? Our DNS server is at Duke, so we shouldn't have any problem there, right? > > Warren, lets do the discussions on the open IRC server, rather than > devserv. That way others can play along. > We're in #fedora-admin on freenode. Warren Togami wtogami at redhat.com From sbranden at redhat.com Wed Aug 30 05:43:24 2006 From: sbranden at redhat.com (Stacy J. Brandenburg) Date: Wed, 30 Aug 2006 01:43:24 -0400 Subject: [Fedora-infrastructure-list] Yum mirror list is safe from outage In-Reply-To: <44F4D25F.7090200@redhat.com> References: <44F4CADD.8020409@redhat.com> <44F4CFEE.9090201@redhat.com> <44F4D25F.7090200@redhat.com> Message-ID: <44F5257C.8010405@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Warren Togami wrote: | | I am a little confused. IP addresses will change in this move? | | Our DNS server is at Duke, so we shouldn't have any problem there, right? Yes if you want the sorry page to display you need to redirect the *.fedoraproject.com to the new IP of the server serving the content, through the outage window. | We're in #fedora-admin on freenode. See you there... - -- ======================================================== = Stacy J. Brandenburg Red Hat Inc. = = Manager, Network Operations sbranden at redhat.com = = 919-754-4313 http://www.redhat.com = ======================================================== Fingerprint 03F7 43BE 1150 CCFA F57B 54DD AEDB 1C27 1828 D94D -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFE9SV8rtscJxgo2U0RAt8sAJ9veZibl2ynhEkerGW1PQEjvQmGsgCgs0CE VNXKoQZt2VXGwYbOPbtxiUc= =A01Z -----END PGP SIGNATURE----- From damian.myerscough at gmail.com Wed Aug 30 11:26:49 2006 From: damian.myerscough at gmail.com (Damian Myerscough) Date: Wed, 30 Aug 2006 12:26:49 +0100 Subject: [Fedora-infrastructure-list] Yum mirror list is safe from outage In-Reply-To: <44F5257C.8010405@redhat.com> References: <44F4CADD.8020409@redhat.com> <44F4CFEE.9090201@redhat.com> <44F4D25F.7090200@redhat.com> <44F5257C.8010405@redhat.com> Message-ID: <8c9e56490608300426ifb2ac49n51a156fef26e5a0a@mail.gmail.com> Hi Stacy, I think last week on IRC you said the IP would be: 66.187.224.110 while there is an outage. On 8/30/06, Stacy J. Brandenburg wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > Warren Togami wrote: > > | > | I am a little confused. IP addresses will change in this move? > | > | Our DNS server is at Duke, so we shouldn't have any problem there, right? > Yes if you want the sorry page to display you need to redirect the > *.fedoraproject.com to the new IP of the server serving the content, > through the outage window. > > | We're in #fedora-admin on freenode. > See you there... > > - -- > ======================================================== > = Stacy J. Brandenburg Red Hat Inc. = > = Manager, Network Operations sbranden at redhat.com = > = 919-754-4313 http://www.redhat.com = > ======================================================== > > Fingerprint > 03F7 43BE 1150 CCFA F57B 54DD AEDB 1C27 1828 D94D > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.7 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iD8DBQFE9SV8rtscJxgo2U0RAt8sAJ9veZibl2ynhEkerGW1PQEjvQmGsgCgs0CE > VNXKoQZt2VXGwYbOPbtxiUc= > =A01Z > -----END PGP SIGNATURE----- > > _______________________________________________ > Fedora-infrastructure-list mailing list > Fedora-infrastructure-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list > From mgalgoci at redhat.com Wed Aug 30 14:45:50 2006 From: mgalgoci at redhat.com (Matthew Galgoci) Date: Wed, 30 Aug 2006 10:45:50 -0400 Subject: [Fedora-infrastructure-list] "sorry" server ip address Message-ID: Hello, The "sorry" server ip address for the outage today is the following: 66.187.224.150 It currently resolves to www.redhat.com but that is ok, it is a name vhost. Put this in your /etc/hosts file to test: 66.187.224.150 www.fedoraproject.org We're adding a wildcard ServerAlias for *.fedoraproject.org also - that change is in flight and will land in about 20 min. -- Matthew Galgoci IS Production Operations Red Hat, Inc 919.754.3700 x44155 From mmcgrath at fedoraproject.org Wed Aug 30 14:53:59 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 30 Aug 2006 09:53:59 -0500 Subject: [Fedora-infrastructure-list] "sorry" server ip address In-Reply-To: References: Message-ID: <3237e4410608300753p1a3b9926l38bcb8cc23331562@mail.gmail.com> On 8/30/06, Matthew Galgoci wrote: > > Hello, > > The "sorry" server ip address for the outage today is the following: > > 66.187.224.150 > > It currently resolves to www.redhat.com but that is ok, it is a name vhost. > > Put this in your /etc/hosts file to test: > > 66.187.224.150 www.fedoraproject.org > > We're adding a wildcard ServerAlias for *.fedoraproject.org also - that change > is in flight and will land in about 20 min. > > -- > Matthew Galgoci > IS Production Operations > Red Hat, Inc > 919.754.3700 x44155 > I'll get on this soon. -Mike From mspevack at redhat.com Wed Aug 30 17:29:36 2006 From: mspevack at redhat.com (Max Spevack) Date: Wed, 30 Aug 2006 13:29:36 -0400 (EDT) Subject: [Fedora-infrastructure-list] coverity code checker in Extras Message-ID: The folks over at Coverity have offered to allow Fedora Extras to use their services, and would like a yes or no. Rather than make this decision in a vacuum, I believe that the Fedora Extras Steering Committee has earned the right to make this decision for themselves. If we can get a decision by the end of the week, that would be great. What follows is my own analysis, for whatever it's worth. PROS + It's good technology, and has been used in Linux projects previously with success. Google "coverity linux" or something similar. + If we act on the results, it could be a great boon for the FE code quality in general. + It doesn't cost us anything. + It forms a relationship between Coverity and Red Hat, and sets the table for more work partnership later, if things go well. + Bugs are bugs, and flaws are flaws. We should be happy to know about them, however they are found, and we should fix them. CONS + It's not open source, but there is no free alternative that can do the same thing. + We need to make sure it doesn't disrupt or break our build system too much. So that will require some technical work and time from certain folks. My gut is that we should say that we're interested, and start hashing out the technical details of how it will all work with them. If we go ahead, I think that in addition to the Board, someone in FESCO needs to "own" this and be our point person for technical questions, etc. Thanks, Max -- Max Spevack + http://fedoraproject.org/wiki/MaxSpevack + gpg key -- http://spevack.org/max.asc + fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21 From kwade at redhat.com Wed Aug 30 18:27:32 2006 From: kwade at redhat.com (Karsten Wade) Date: Wed, 30 Aug 2006 11:27:32 -0700 Subject: [Fedora-infrastructure-list] Re: Fedora Outage Notice for August 30th, 2006 In-Reply-To: <44F4C2D2.7080505@redhat.com> References: <44F4C2D2.7080505@redhat.com> Message-ID: <1156962452.2545.125.camel@erato.phig.org> On Tue, 2006-08-29 at 18:42 -0400, Warren Togami wrote: > Date: August 30th, 2006 > Time: 8:00AM - 8:00PM Mountain Standard Time (UTC -7) Thanks all for your hard work here. A request to please check the Documentation and Translation schedules when planning outages. We have schedules that are tied to the Core schedule, but off by appropriate times for various things: http://fedoraproject.org/wiki/DocsProject/Schedule I note this because we are supposed to be pushing content into CVS today to make a Translation freeze for tomorrow. In all likelihood, we can work unaffected by the outage. But <24 hours to plan our work around was unexpected. Thanks again, this is honestly not a complaint, just wanted you to be aware of other schedules affected by outage planning. Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Matt_Domsch at dell.com Wed Aug 30 19:08:58 2006 From: Matt_Domsch at dell.com (Matt Domsch) Date: Wed, 30 Aug 2006 14:08:58 -0500 Subject: [Fedora-infrastructure-list] coverity code checker in Extras In-Reply-To: References: Message-ID: <20060830190858.GA9496@lists.us.dell.com> On Wed, Aug 30, 2006 at 01:29:36PM -0400, Max Spevack wrote: > The folks over at Coverity have offered to allow Fedora Extras to use > their services, and would like a yes or no. +1. More eyes (in this case, even electronic eyes) is good. > CONS > > + We need to make sure it doesn't disrupt or break our build system too > much. So that will require some technical work and time from certain > folks. I thought their checking work was being done not on the build environment but on their own servers using SCM access. No? scan.coverity.com also requires personal registration (sends an email with your name, email address, and "reason for needing access") for each project the list (which looks like it's one project per program/app, I don't see a category like "Fedora Extras" to sign up for blanketwise) in order to see the list of bugs. Any chance we could relax that somewhat, tie it into the FE accounts system or something? Else everyone wanting to look at that list needs to register at coverity's site, yes? The current registration looks like: To get access to the FOOBAR report please supply your: Full Name: Email: Your association with the project and purpose of access: There's no privacy policy listed (though their main page's "subscribe to our mailing list" does say "We will NEVER share your e-mail with anyone and you can unsubscribe at any time." there's no similar statement or opt-out for sales calls made using the info you provide. Otherwise, I do like the idea. Thanks, Matt -- Matt Domsch Software Architect Dell Linux Solutions linux.dell.com & www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com From sbranden at redhat.com Wed Aug 30 19:13:24 2006 From: sbranden at redhat.com (Stacy J. Brandenburg) Date: Wed, 30 Aug 2006 15:13:24 -0400 Subject: [Fedora-infrastructure-list] Re: Fedora Outage Notice for August 30th, 2006 In-Reply-To: <1156962452.2545.125.camel@erato.phig.org> References: <44F4C2D2.7080505@redhat.com> <1156962452.2545.125.camel@erato.phig.org> Message-ID: <44F5E354.8080300@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Karsten, I would like to invite you to the weekly meetings on IRC. I was unaware of the schedule you have. This is the type of thing I was hoping to avoid, and thus why I made the request and was granted by all in attendance this time - last week during that meeting. We are starting to move the devices right now. We will need about 6-8 hours to finish. If needed we can do a little today, and try to do a little tomorrow. I am moving the PRX/APP/DB servers in the next 2 hours. After that I will move the build boxes. Please let me know if you would like me to stop with the first set today and hit the second tomorrow. I am ok with that and it will probably actually help me... Looking for your quick reply. Thanks, Karsten Wade wrote: | On Tue, 2006-08-29 at 18:42 -0400, Warren Togami wrote: | |>Date: August 30th, 2006 |>Time: 8:00AM - 8:00PM Mountain Standard Time (UTC -7) | | | Thanks all for your hard work here. | | A request to please check the Documentation and Translation schedules | when planning outages. We have schedules that are tied to the Core | schedule, but off by appropriate times for various things: | | http://fedoraproject.org/wiki/DocsProject/Schedule | | I note this because we are supposed to be pushing content into CVS today | to make a Translation freeze for tomorrow. In all likelihood, we can | work unaffected by the outage. But <24 hours to plan our work around | was unexpected. | | Thanks again, this is honestly not a complaint, just wanted you to be | aware of other schedules affected by outage planning. | | Karsten | | | ------------------------------------------------------------------------ | | _______________________________________________ | Fedora-infrastructure-list mailing list | Fedora-infrastructure-list at redhat.com | https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list - -- ======================================================== = Stacy J. Brandenburg Red Hat Inc. = = Manager, Network Operations sbranden at redhat.com = = 919-754-4313 http://www.redhat.com = ======================================================== Fingerprint 03F7 43BE 1150 CCFA F57B 54DD AEDB 1C27 1828 D94D -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFE9eNUrtscJxgo2U0RAjkHAJ9aS1038o/N3B5Y9MS9dSjWn0//xwCgsoXv APpdqUleCLBxdsKbratbdWA= =f7r4 -----END PGP SIGNATURE----- From mmcgrath at fedoraproject.org Wed Aug 30 19:32:05 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 30 Aug 2006 14:32:05 -0500 Subject: [Fedora-infrastructure-list] Re: Fedora Outage Notice for August 30th, 2006 In-Reply-To: <44F5E354.8080300@redhat.com> References: <44F4C2D2.7080505@redhat.com> <1156962452.2545.125.camel@erato.phig.org> <44F5E354.8080300@redhat.com> Message-ID: <3237e4410608301232u1a0f04a8j15c31342386f1c0b@mail.gmail.com> On 8/30/06, Stacy J. Brandenburg wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Karsten, > > > I would like to invite you to the weekly meetings on IRC. I was unaware > of the schedule you have. This is the type of thing I was hoping to > avoid, and thus why I made the request and was granted by all in > attendance this time - last week during that meeting. > > We are starting to move the devices right now. We will need about 6-8 > hours to finish. If needed we can do a little today, and try to do a > little tomorrow. > > I am moving the PRX/APP/DB servers in the next 2 hours. After that I > will move the build boxes. Please let me know if you would like me to > stop with the first set today and hit the second tomorrow. I am ok with > that and it will probably actually help me... > Next time we should probably announce an outage like this on the Fedora-Announce list at least a week maybe two in advance. It just kind of slipped our minds to do that (mine too) -Mike From sbranden at redhat.com Wed Aug 30 20:16:32 2006 From: sbranden at redhat.com (Stacy J. Brandenburg) Date: Wed, 30 Aug 2006 16:16:32 -0400 Subject: [Fedora-infrastructure-list] Re: Fedora Outage Notice for August 30th, 2006 In-Reply-To: <3237e4410608301232u1a0f04a8j15c31342386f1c0b@mail.gmail.com> References: <44F4C2D2.7080505@redhat.com> <1156962452.2545.125.camel@erato.phig.org> <44F5E354.8080300@redhat.com> <3237e4410608301232u1a0f04a8j15c31342386f1c0b@mail.gmail.com> Message-ID: <44F5F220.6090107@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sounds good. Mike McGrath wrote: | On 8/30/06, Stacy J. Brandenburg wrote: | |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA1 |> |> Karsten, |> |> |> I would like to invite you to the weekly meetings on IRC. I was unaware |> of the schedule you have. This is the type of thing I was hoping to |> avoid, and thus why I made the request and was granted by all in |> attendance this time - last week during that meeting. |> |> We are starting to move the devices right now. We will need about 6-8 |> hours to finish. If needed we can do a little today, and try to do a |> little tomorrow. |> |> I am moving the PRX/APP/DB servers in the next 2 hours. After that I |> will move the build boxes. Please let me know if you would like me to |> stop with the first set today and hit the second tomorrow. I am ok with |> that and it will probably actually help me... |> | | Next time we should probably announce an outage like this on the | Fedora-Announce list at least a week maybe two in advance. It just | kind of slipped our minds to do that (mine too) | | -Mike - -- ======================================================== = Stacy J. Brandenburg Red Hat Inc. = = Manager, Network Operations sbranden at redhat.com = = 919-754-4313 http://www.redhat.com = ======================================================== Fingerprint 03F7 43BE 1150 CCFA F57B 54DD AEDB 1C27 1828 D94D -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFE9fIgrtscJxgo2U0RAqotAJ9TLdNpTV4jeR3UxQt/115o+CKn4gCfdIF3 qhUuz5BOif2qRVP2oUA8/M4= =UAEq -----END PGP SIGNATURE----- From drepper at redhat.com Wed Aug 30 19:22:38 2006 From: drepper at redhat.com (Ulrich Drepper) Date: Wed, 30 Aug 2006 12:22:38 -0700 Subject: [Fedora-infrastructure-list] coverity code checker in Extras In-Reply-To: <20060830190858.GA9496@lists.us.dell.com> References: <20060830190858.GA9496@lists.us.dell.com> Message-ID: <44F5E57E.10100@redhat.com> Matt Domsch wrote: > I thought their checking work was being done not on the build > environment but on their own servers using SCM access. No? This setup would be separate and independent from the scan.coverity.com setup and access to the bug database would also be under FC/FE committee control. -- ? Ulrich Drepper ? Red Hat, Inc. ? 444 Castro St ? Mountain View, CA ? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From Axel.Thimm at ATrpms.net Wed Aug 30 19:57:48 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Wed, 30 Aug 2006 21:57:48 +0200 Subject: [Fedora-infrastructure-list] Fedora's FLOSS prociples (was: coverity code checker in Extras) In-Reply-To: References: Message-ID: <20060830195748.GH1004@neu.nirvana> On Wed, Aug 30, 2006 at 01:29:36PM -0400, Max Spevack wrote: > + It's not open source, but there is no free alternative that can do the > same thing. I don't want to spoil anything and I'm not the activest FLOSS agitators, but I see a conflict of goals and tools. The kernel-uses-bitkeeper-technology created more noise than it served good and bitkeeper was closer to open source than coverity while Linus was less pondering on FLOSS principles than the Fedora goals do, so projecting that to the future I see endless threads about the pure-FLOSS Linux using non-FLOSS tools. There is an argument often brought up in these situations which goes like "since no FLOSS alternative exists, we need to use that". But the same is true about ipw* firmwares/closed source daemons, closed source 3D graphics and so on. There is even discussion of not allowing external kernel modules, even fully FLOSSed ones, in Fedora to demonstrate Fedora's embracement and loyality to FLOSS. If we want to open the backdoor to non-FLOSS bits we will be blamed on being selective and non-open ourselves serving only our needs at hand. Don't get me wrong, as I said I'm no FLOSS die-hard agitator, and I would personally welcome a code checker. But it does conflict with Fedora's manifesto and will create a flood of noise and bad marketing. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jwboyer at jdub.homelinux.org Wed Aug 30 20:05:47 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Wed, 30 Aug 2006 15:05:47 -0500 Subject: [Fedora-infrastructure-list] Re: Fedora's FLOSS prociples (was: coverity code checker in Extras) In-Reply-To: <20060830195748.GH1004@neu.nirvana> References: <20060830195748.GH1004@neu.nirvana> Message-ID: <1156968347.2003.48.camel@zod.rchland.ibm.com> On Wed, 2006-08-30 at 21:57 +0200, Axel Thimm wrote: > On Wed, Aug 30, 2006 at 01:29:36PM -0400, Max Spevack wrote: > > + It's not open source, but there is no free alternative that can do the > > same thing. > > I don't want to spoil anything and I'm not the activest FLOSS > agitators, but I see a conflict of goals and tools. > > The kernel-uses-bitkeeper-technology created more noise than it served > good and bitkeeper was closer to open source than coverity while Linus > was less pondering on FLOSS principles than the Fedora goals do, so > projecting that to the future I see endless threads about the > pure-FLOSS Linux using non-FLOSS tools. > > There is an argument often brought up in these situations which goes > like "since no FLOSS alternative exists, we need to use that". But the > same is true about ipw* firmwares/closed source daemons, closed source > 3D graphics and so on. There is even discussion of not allowing > external kernel modules, even fully FLOSSed ones, in Fedora to > demonstrate Fedora's embracement and loyality to FLOSS. Not quite. Yes, Fedora's mantra is upstream in regards to kernel modules simply because it benefits everyone in the long run. But the current issue stems from maintenance in the long run and resource issues for the Core kernel devs. Please don't confuse that with FLOSS zealotry. > > If we want to open the backdoor to non-FLOSS bits we will be blamed on > being selective and non-open ourselves serving only our needs at hand. > > Don't get me wrong, as I said I'm no FLOSS die-hard agitator, and I > would personally welcome a code checker. But it does conflict with > Fedora's manifesto and will create a flood of noise and bad marketing. There are two major items you're ignoring. 1) Coverity is not required by any means. Your bitkeeper analogy is flawed because it was the _only_ SCM tool being used for the kernel. It was essentially a gate. 2) Fedora isn't shipping coverity. It doesn't taint the distribution in any way. josh From wtogami at redhat.com Wed Aug 30 22:10:37 2006 From: wtogami at redhat.com (Warren Togami) Date: Wed, 30 Aug 2006 18:10:37 -0400 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: References: Message-ID: <44F60CDD.6050405@redhat.com> We have been trying to keep Fedora's Infrastructure completely FOSS for the purpose of making it reproducible and easy to contribute improvements. This is a noble goal. Comparing Coverity to Bitkeeper is not a fair comparison because Fedora and any projects that reproduce it would not depend on it. Coverity would in part protect Fedora, but this really is a tool for improving upstream projects, and Fedora would just make it easier to funnel analysis and reports. We have long wanted to implement post-build check reports in order to improve package quality in an automated fashion. Coverity could just be another post-build check in that list. On the other hand, we may want to implement Coverity in a different way than post-check. The output needs to be kept private to the individual package owners and possibly security group people so security embargoes can be handled in a responsible way in cooperation with upstream projects. We also want to avoid slowing down the build, sign and push process any further. My Proposal ========== A good compromise would be for Coverity to be run outside of the scope of the Fedora Project as just a Red Hat thing. It would run asynchronously on the binary RPMS in pushed repositories. If Fedora contributors are interested in helping to better automate this they are free to do so. This way Fedora and upstream benefits from Coverity analysis, and Fedora remains ideologically pure. Thoughts? Warren Togami wtogami at redhat.com From Christian.Iseli at licr.org Wed Aug 30 22:13:29 2006 From: Christian.Iseli at licr.org (Christian Iseli) Date: Thu, 31 Aug 2006 00:13:29 +0200 Subject: [Fedora-infrastructure-list] coverity code checker in Extras In-Reply-To: References: Message-ID: <20060831001329.6b106ea3@ludwig-alpha> On Wed, 30 Aug 2006 13:29:36 -0400 (EDT), Max Spevack wrote: > My gut is that we should say that we're interested, and start hashing out > the technical details of how it will all work with them. > > If we go ahead, I think that in addition to the Board, someone in FESCO > needs to "own" this and be our point person for technical questions, etc. I agree on both points. Christian From skvidal at linux.duke.edu Thu Aug 31 02:47:09 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Wed, 30 Aug 2006 22:47:09 -0400 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <1156992076.2693.17.camel@vader.jdub.homelinux.org> References: <44F60CDD.6050405@redhat.com> <1156992076.2693.17.camel@vader.jdub.homelinux.org> Message-ID: <1156992429.6552.10.camel@cutter> On Wed, 2006-08-30 at 21:41 -0500, Josh Boyer wrote: > On Wed, 2006-08-30 at 18:10 -0400, Warren Togami wrote: > > We have been trying to keep Fedora's Infrastructure completely FOSS for > > the purpose of making it reproducible and easy to contribute > > improvements. This is a noble goal. > > Which infrastructure? Extras or Core. Because if you mean Fedora in > general, then I'm sorry but that's a bit off. The Core buildsys is not > open sourced. Yes, but not b/c we chose it. That's just a function of managerial stupidity. There will be a reckoning. oh yes, there will be a reckoning. -sv From mmcgrath at fedoraproject.org Thu Aug 31 02:49:29 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Wed, 30 Aug 2006 21:49:29 -0500 Subject: [Fedora-infrastructure-list] CVS outage Message-ID: <3237e4410608301949pfc94a20n7c309a6fd238f443@mail.gmail.com> The migration today went fairly well, few bumps but all infrastructure should be back up now except for the CVS box. He's hurt, hurt bad. The issue is with booting and because many things at the colo are still in a transition right now we cannot access PDU's to restart it. We will be addressing this issue first thing tomorrow morning (US morning) when the techs are back in the data center. Outages are never fun and we apologize for any inconvenience this has caused but once everything is back up we will be in a better spot for future expandability of the Fedora Project's infrastructure. -Mike From nils at breun.nl Thu Aug 31 09:07:45 2006 From: nils at breun.nl (Nils Breunese) Date: Thu, 31 Aug 2006 11:07:45 +0200 Subject: [Fedora-infrastructure-list] Fedora's FLOSS prociples (was: coverity code checker in Extras) In-Reply-To: <20060830195748.GH1004@neu.nirvana> References: <20060830195748.GH1004@neu.nirvana> Message-ID: Axel Thimm wrote: > The kernel-uses-bitkeeper-technology created more noise than it served > good and bitkeeper was closer to open source than coverity while Linus > was less pondering on FLOSS principles than the Fedora goals do, so > projecting that to the future I see endless threads about the > pure-FLOSS Linux using non-FLOSS tools. > > There is an argument often brought up in these situations which goes > like "since no FLOSS alternative exists, we need to use that". But the > same is true about ipw* firmwares/closed source daemons, closed source > 3D graphics and so on. There is even discussion of not allowing > external kernel modules, even fully FLOSSed ones, in Fedora to > demonstrate Fedora's embracement and loyality to FLOSS. Well, maybe Fedora should ditch apache, wireshark, perl, python, samba, subversion, vim, xmms and a lot of other packages then, as they are already checked by Coverity. Check the banner on scan.coverity.com, even the Linux kernel is. Nils Breunese. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Dit deel van het bericht is digitaal ondertekend URL: From wtogami at redhat.com Thu Aug 31 15:15:28 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 31 Aug 2006 11:15:28 -0400 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <1156992132.4667.0.camel@localhost.localdomain> References: <44F60CDD.6050405@redhat.com> <1156992132.4667.0.camel@localhost.localdomain> Message-ID: <44F6FD10.10900@redhat.com> Matthias Clasen wrote: > On Wed, 2006-08-30 at 18:10 -0400, Warren Togami wrote: >> My Proposal >> ========== >> A good compromise would be for Coverity to be run outside of the scope >> of the Fedora Project as just a Red Hat thing. It would run >> asynchronously on the binary RPMS in pushed repositories. If Fedora >> contributors are interested in helping to better automate this they are >> free to do so. >> >> This way Fedora and upstream benefits from Coverity analysis, and Fedora >> remains ideologically pure. >> >> Thoughts? > > Warren, its a _source_ analysis tool. Running it on binary packages > won't do much good... > Same thing in principle. Why does Coverity need to be in our build system? It could very well work asynchronously outside of Fedora from our SRPMS. Warren Togami wtogami at redhat.com From wtogami at redhat.com Thu Aug 31 15:35:26 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 31 Aug 2006 11:35:26 -0400 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <44F70143.3030709@redhat.com> References: <44F60CDD.6050405@redhat.com> <1156992132.4667.0.camel@localhost.localdomain> <44F6FD10.10900@redhat.com> <44F70143.3030709@redhat.com> Message-ID: <44F701BE.4030502@redhat.com> Ulrich Drepper wrote: > Warren Togami wrote: >> Same thing in principle. Why does Coverity need to be in our build >> system? It could very well work asynchronously outside of Fedora from >> our SRPMS. > > If you don't do it in the build system there is no guarantee that the > tests actually test the same thing as the code which is shipped. > How so? mock putting together its own buildroots and doing rpmbuild -bp is not the same thing? Warren Togami wtogami at redhat.com From wtogami at redhat.com Thu Aug 31 15:48:11 2006 From: wtogami at redhat.com (Warren Togami) Date: Thu, 31 Aug 2006 11:48:11 -0400 Subject: [Fedora-infrastructure-list] Service Cleanup Message-ID: <44F704BB.4060904@redhat.com> Any objections to blanket disabling of this stuff across all servers? Warren Togami wtogami at redhat.com isdn pcmcia apmd rawdevices microcode_ctl Utterly useless to us. atd anacron Do we want to keep these? I've always turned them off personally. messagebus haldaemon cups acpid xfs Only relevant to desktops? xinetd Only turn this on if we actually use anything that requires it? arptables_jf Have or will we ever use this? From dennis at ausil.us Thu Aug 31 15:55:09 2006 From: dennis at ausil.us (Dennis Gilmore) Date: Thu, 31 Aug 2006 10:55:09 -0500 Subject: [Fedora-infrastructure-list] Service Cleanup In-Reply-To: <44F704BB.4060904@redhat.com> References: <44F704BB.4060904@redhat.com> Message-ID: <200608311055.10153.dennis@ausil.us> On Thursday 31 August 2006 10:48, Warren Togami wrote: > Any objections to blanket disabling of this stuff across all servers? > > Warren Togami > wtogami at redhat.com > > isdn pcmcia apmd rawdevices microcode_ctl > Utterly useless to us. i agree > atd anacron > Do we want to keep these? I've always turned them off personally. anacron could be useful if the boxes are down when they are supposed to run things but probably not needed. does anyone use at for anything on the servers? > messagebus haldaemon cups acpid xfs > Only relevant to desktops? should be ok, i have cups on my file and print server but thats it as far as servers go > xinetd > Only turn this on if we actually use anything that requires it? sounds fine to me > arptables_jf > Have or will we ever use this? probably not if we need it we can re-enable it. we should definitely have only what we need enabled. everything else should be off. Dennis From mmcgrath at fedoraproject.org Thu Aug 31 16:06:10 2006 From: mmcgrath at fedoraproject.org (Mike McGrath) Date: Thu, 31 Aug 2006 11:06:10 -0500 Subject: [Fedora-infrastructure-list] Service Cleanup In-Reply-To: <200608311055.10153.dennis@ausil.us> References: <44F704BB.4060904@redhat.com> <200608311055.10153.dennis@ausil.us> Message-ID: <3237e4410608310906y79d2fd8bod91adb4fd9dd7fdc@mail.gmail.com> On 8/31/06, Dennis Gilmore wrote: > On Thursday 31 August 2006 10:48, Warren Togami wrote: > > Any objections to blanket disabling of this stuff across all servers? > > > > Warren Togami > > wtogami at redhat.com > > > > isdn pcmcia apmd rawdevices microcode_ctl > > Utterly useless to us. > i agree > > atd anacron > > Do we want to keep these? I've always turned them off personally. > anacron could be useful if the boxes are down when they are supposed to run > things but probably not needed. does anyone use at for anything on the > servers? > > > messagebus haldaemon cups acpid xfs > > Only relevant to desktops? > should be ok, i have cups on my file and print server but thats it as far as > servers go > > > xinetd > > Only turn this on if we actually use anything that requires it? > sounds fine to me > > arptables_jf > > Have or will we ever use this? > > probably not if we need it we can re-enable it. > > we should definitely have only what we need enabled. everything else should > be off. > > Dennis > There's plenty of stuff running we should disable. I mean, cups? CUPS?!?! -Mike From skvidal at linux.duke.edu Thu Aug 31 16:13:13 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Thu, 31 Aug 2006 12:13:13 -0400 Subject: [Fedora-infrastructure-list] Service Cleanup In-Reply-To: <44F704BB.4060904@redhat.com> References: <44F704BB.4060904@redhat.com> Message-ID: <1157040793.10742.14.camel@cutter> On Thu, 2006-08-31 at 11:48 -0400, Warren Togami wrote: > Any objections to blanket disabling of this stuff across all servers? > > Warren Togami > wtogami at redhat.com > > isdn pcmcia apmd rawdevices microcode_ctl > Utterly useless to us. > > atd anacron > Do we want to keep these? I've always turned them off personally. > > messagebus haldaemon cups acpid xfs > Only relevant to desktops? > > xinetd > Only turn this on if we actually use anything that requires it? > > arptables_jf > Have or will we ever use this? > we disable or remove all of these from the systems I run here at duke. isdn, pcmcia, apmd and cups should all be removed unless they are being used. -sv From mclasen at redhat.com Thu Aug 31 02:42:12 2006 From: mclasen at redhat.com (Matthias Clasen) Date: Wed, 30 Aug 2006 22:42:12 -0400 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <44F60CDD.6050405@redhat.com> References: <44F60CDD.6050405@redhat.com> Message-ID: <1156992132.4667.0.camel@localhost.localdomain> On Wed, 2006-08-30 at 18:10 -0400, Warren Togami wrote: > My Proposal > ========== > A good compromise would be for Coverity to be run outside of the scope > of the Fedora Project as just a Red Hat thing. It would run > asynchronously on the binary RPMS in pushed repositories. If Fedora > contributors are interested in helping to better automate this they are > free to do so. > > This way Fedora and upstream benefits from Coverity analysis, and Fedora > remains ideologically pure. > > Thoughts? Warren, its a _source_ analysis tool. Running it on binary packages won't do much good... From jwboyer at jdub.homelinux.org Thu Aug 31 02:41:16 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Wed, 30 Aug 2006 21:41:16 -0500 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <44F60CDD.6050405@redhat.com> References: <44F60CDD.6050405@redhat.com> Message-ID: <1156992076.2693.17.camel@vader.jdub.homelinux.org> On Wed, 2006-08-30 at 18:10 -0400, Warren Togami wrote: > We have been trying to keep Fedora's Infrastructure completely FOSS for > the purpose of making it reproducible and easy to contribute > improvements. This is a noble goal. Which infrastructure? Extras or Core. Because if you mean Fedora in general, then I'm sorry but that's a bit off. The Core buildsys is not open sourced. > > Comparing Coverity to Bitkeeper is not a fair comparison because Fedora > and any projects that reproduce it would not depend on it. Coverity > would in part protect Fedora, but this really is a tool for improving > upstream projects, and Fedora would just make it easier to funnel > analysis and reports. Yes. > We have long wanted to implement post-build check reports in order to > improve package quality in an automated fashion. Coverity could just be > another post-build check in that list. Yes. > On the other hand, we may want to implement Coverity in a different way > than post-check. The output needs to be kept private to the individual > package owners and possibly security group people so security embargoes > can be handled in a responsible way in cooperation with upstream > projects. We also want to avoid slowing down the build, sign and push > process any further. > > My Proposal > ========== > A good compromise would be for Coverity to be run outside of the scope > of the Fedora Project as just a Red Hat thing. It would run > asynchronously on the binary RPMS in pushed repositories. If Fedora > contributors are interested in helping to better automate this they are > free to do so. Erm... doesn't coverity need _source_? > > This way Fedora and upstream benefits from Coverity analysis, and Fedora > remains ideologically pure. *cough* Core buildsys *cough* josh From jwboyer at jdub.homelinux.org Thu Aug 31 03:11:32 2006 From: jwboyer at jdub.homelinux.org (Josh Boyer) Date: Wed, 30 Aug 2006 22:11:32 -0500 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <1156992429.6552.10.camel@cutter> References: <44F60CDD.6050405@redhat.com> <1156992076.2693.17.camel@vader.jdub.homelinux.org> <1156992429.6552.10.camel@cutter> Message-ID: <1156993892.2693.22.camel@vader.jdub.homelinux.org> On Wed, 2006-08-30 at 22:47 -0400, seth vidal wrote: > On Wed, 2006-08-30 at 21:41 -0500, Josh Boyer wrote: > > On Wed, 2006-08-30 at 18:10 -0400, Warren Togami wrote: > > > We have been trying to keep Fedora's Infrastructure completely FOSS for > > > the purpose of making it reproducible and easy to contribute > > > improvements. This is a noble goal. > > > > Which infrastructure? Extras or Core. Because if you mean Fedora in > > general, then I'm sorry but that's a bit off. The Core buildsys is not > > open sourced. > > Yes, but not b/c we chose it. That's just a function of managerial > stupidity. I never intended to imply otherwise :) > > There will be a reckoning. > > oh yes, there will be a reckoning. I look forward to the day. :) josh From Axel.Thimm at ATrpms.net Thu Aug 31 11:15:25 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Thu, 31 Aug 2006 13:15:25 +0200 Subject: [Fedora-infrastructure-list] Re: Fedora's FLOSS principles (was: coverity code checker in Extras) In-Reply-To: <1156968347.2003.48.camel@zod.rchland.ibm.com> References: <20060830195748.GH1004@neu.nirvana> <1156968347.2003.48.camel@zod.rchland.ibm.com> Message-ID: <20060831111525.GA28961@neu.nirvana> On Wed, Aug 30, 2006 at 03:05:47PM -0500, Josh Boyer wrote: > On Wed, 2006-08-30 at 21:57 +0200, Axel Thimm wrote: > > On Wed, Aug 30, 2006 at 01:29:36PM -0400, Max Spevack wrote: > > > + It's not open source, but there is no free alternative that can do the > > > same thing. > > > > I don't want to spoil anything and I'm not the activest FLOSS > > agitators, but I see a conflict of goals and tools. > > > > The kernel-uses-bitkeeper-technology created more noise than it served > > good and bitkeeper was closer to open source than coverity while Linus > > was less pondering on FLOSS principles than the Fedora goals do, so > > projecting that to the future I see endless threads about the > > pure-FLOSS Linux using non-FLOSS tools. > > > > There is an argument often brought up in these situations which goes > > like "since no FLOSS alternative exists, we need to use that". But the > > same is true about ipw* firmwares/closed source daemons, closed source > > 3D graphics and so on. There is even discussion of not allowing > > external kernel modules, even fully FLOSSed ones, in Fedora to > > demonstrate Fedora's embracement and loyality to FLOSS. > > Not quite. Yes, Fedora's mantra is upstream in regards to kernel > modules simply because it benefits everyone in the long run. But the > current issue stems from maintenance in the long run and resource issues > for the Core kernel devs. Please don't confuse that with FLOSS > zealotry. > > > > > If we want to open the backdoor to non-FLOSS bits we will be blamed on > > being selective and non-open ourselves serving only our needs at hand. > > > > Don't get me wrong, as I said I'm no FLOSS die-hard agitator, and I > > would personally welcome a code checker. But it does conflict with > > Fedora's manifesto and will create a flood of noise and bad marketing. > > There are two major items you're ignoring. > > 1) Coverity is not required by any means. Your bitkeeper analogy is > flawed because it was the _only_ SCM tool being used for the kernel. It > was essentially a gate. That's debatable. From a user's POV the SCM used is not seen. And precicely because of the reasons you outline and the FLOSS ideology of several kernel developers there were gateways to other SCMs as well as simple diff&patch submissions. > 2) Fedora isn't shipping coverity. It doesn't taint the distribution in > any way. That doesn't matter, the kernel tarballs didn't contain bitkeeper, too. The cause does not justify the means. Furthermore the fact that you mentioned in other posts to this thread, that FC uses beehive which is closed source, has its truth and shame, but whenever this was (seldomly) addressed in the past people kept saying that they would iron it out and open-source it. Meanwhile there emerged better open source technologies on the market, so the demand and motivation to do so is low. But I'm sure that in principle RH would go through the effort to open-source it if it was worth while, just as they did with much larger formerly closed source projects like gfs and ds. Anyway to cut a long story short it boilds down to a matter of principles. Ask yourself *why* Fedora has a certain FLOSS ideology that disallows for example packaging and shipping of non-FLOSS software and the answer will be applying to why Fedora should not be using/supporting non-FLOSS in any other way. See also the discussion of using non-open media formats on redhat.com. It all spins around a chosen core ideology. Again: Don't mistake me for a FLOSS zealot, I'm just seeing these issues coming up. As I see it it will either lead to confirming the strict endorsement of FLOSS ideology and officially refuse any non-FLOSS contributions or it will lead to a softening of Fedora's definition of FLOSS goals to allow for using non-FLOSS technology. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From drepper at redhat.com Thu Aug 31 15:33:23 2006 From: drepper at redhat.com (Ulrich Drepper) Date: Thu, 31 Aug 2006 08:33:23 -0700 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <44F6FD10.10900@redhat.com> References: <44F60CDD.6050405@redhat.com> <1156992132.4667.0.camel@localhost.localdomain> <44F6FD10.10900@redhat.com> Message-ID: <44F70143.3030709@redhat.com> Warren Togami wrote: > Same thing in principle. Why does Coverity need to be in our build > system? It could very well work asynchronously outside of Fedora from > our SRPMS. If you don't do it in the build system there is no guarantee that the tests actually test the same thing as the code which is shipped. -- ? Ulrich Drepper ? Red Hat, Inc. ? 444 Castro St ? Mountain View, CA ? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From drepper at redhat.com Thu Aug 31 16:02:03 2006 From: drepper at redhat.com (Ulrich Drepper) Date: Thu, 31 Aug 2006 09:02:03 -0700 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <44F701BE.4030502@redhat.com> References: <44F60CDD.6050405@redhat.com> <1156992132.4667.0.camel@localhost.localdomain> <44F6FD10.10900@redhat.com> <44F70143.3030709@redhat.com> <44F701BE.4030502@redhat.com> Message-ID: <44F707FB.8060703@redhat.com> Warren Togami wrote: > How so? mock putting together its own buildroots and doing rpmbuild -bp > is not the same thing? The nature of the two tasks running independently automatically makes it impossible to guarantee that the same code is analyzed and shipped. The nice thing about the way the tools work is that they can work transparently while building the actual packages. This not only guarantees the same sources are analyzed and shipped, it also significantly reduces the resources needed since the build root and untarred packages don't have to be created again. Also note that the actual Coverity tool isn't run at the time of the data collection. This is only a tiny little piece which collects the data. The actual analysis is done in a separate step. -- ? Ulrich Drepper ? Red Hat, Inc. ? 444 Castro St ? Mountain View, CA ? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From sopwith at gmail.com Thu Aug 31 17:10:25 2006 From: sopwith at gmail.com (Elliot Lee) Date: Thu, 31 Aug 2006 13:10:25 -0400 Subject: [Fedora-infrastructure-list] Service Cleanup In-Reply-To: <44F704BB.4060904@redhat.com> References: <44F704BB.4060904@redhat.com> Message-ID: I think you'll find that some of those will break stuff if they get turned off. And others do useful stuff. And a few can be turned off. But don't just do a blanket disable because you're not sure that they're useful... Best, -- Elliot On 31/08/2006, at 11:48 AM, Warren Togami wrote: > Any objections to blanket disabling of this stuff across all servers? > > Warren Togami > wtogami at redhat.com > > isdn pcmcia apmd rawdevices microcode_ctl > Utterly useless to us. > > atd anacron > Do we want to keep these? I've always turned them off personally. > > messagebus haldaemon cups acpid xfs > Only relevant to desktops? > > xinetd > Only turn this on if we actually use anything that requires it? > > arptables_jf > Have or will we ever use this? > > _______________________________________________ > Fedora-infrastructure-list mailing list > Fedora-infrastructure-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list From skvidal at linux.duke.edu Thu Aug 31 22:19:10 2006 From: skvidal at linux.duke.edu (seth vidal) Date: Thu, 31 Aug 2006 18:19:10 -0400 Subject: [Fedora-infrastructure-list] Service Cleanup In-Reply-To: References: <44F704BB.4060904@redhat.com> Message-ID: <1157062751.10742.55.camel@cutter> On Thu, 2006-08-31 at 13:10 -0400, Elliot Lee wrote: > I think you'll find that some of those will break stuff if they get > turned off. And others do useful stuff. And a few can be turned off. > But don't just do a blanket disable because you're not sure that > they're useful... > umm, no they won't. isdn, pcmcia, apmd and microcode_ctl won't hurt anything rawdevices is really only used by oracle. atd only matters for things using at queuing - if we have something doing that we should find it and stop it. anacron - bah! and ick dbus and hal only matter if we were using of the network fun, which we're not. They matter more in the future but they don't right now and on rhel4 boxes it's all kudzu-riffic, still. cups - obviously - no acpid - has some meaning in the event we have acpi devices that need to be negotiated with for different system power states - not on these boxes, though. xfs - if there is no x the the x font server matters not. > > xinetd > > Only turn this on if we actually use anything that requires it? xinetd - obvious > > > > arptables_jf > > Have or will we ever use this? We aren't controllowing which arp requests/replies are going on so this doesn't matter. I've turned off each and every one of these one my servers without fault. -sv From dcbw at redhat.com Thu Aug 31 20:20:12 2006 From: dcbw at redhat.com (Dan Williams) Date: Thu, 31 Aug 2006 16:20:12 -0400 Subject: [Fedora-infrastructure-list] Re: coverity code checker in Extras In-Reply-To: <44F60CDD.6050405@redhat.com> References: <44F60CDD.6050405@redhat.com> Message-ID: <1157055612.9720.8.camel@localhost.localdomain> On Wed, 2006-08-30 at 18:10 -0400, Warren Togami wrote: > We have been trying to keep Fedora's Infrastructure completely FOSS for > the purpose of making it reproducible and easy to contribute > improvements. This is a noble goal. > > Comparing Coverity to Bitkeeper is not a fair comparison because Fedora > and any projects that reproduce it would not depend on it. Coverity > would in part protect Fedora, but this really is a tool for improving > upstream projects, and Fedora would just make it easier to funnel > analysis and reports. > > We have long wanted to implement post-build check reports in order to > improve package quality in an automated fashion. Coverity could just be > another post-build check in that list. > > On the other hand, we may want to implement Coverity in a different way > than post-check. The output needs to be kept private to the individual > package owners and possibly security group people so security embargoes > can be handled in a responsible way in cooperation with upstream > projects. We also want to avoid slowing down the build, sign and push > process any further. > > My Proposal > ========== > A good compromise would be for Coverity to be run outside of the scope > of the Fedora Project as just a Red Hat thing. It would run > asynchronously on the binary RPMS in pushed repositories. If Fedora > contributors are interested in helping to better automate this they are > free to do so. Note that we may not be able to deploy the Coverity bits on the same build machines that Extras packages are built on right now; mainly because the people who have access to those machines are not employed by Red Hat. There's an open question as to whether Coverity will permit non-Red Hat contributors access to machines that run the proprietary Coverity binaries (which contain a fair amount of their IP and trade secrets and such) without signing some legal document. The sensitive bits are precisely those that run during the package build. I think the easiest solution at the current time is to run the Coverity scans on one or two parallel machines that harvest successful build results from the actual Extras buildsystem, and which non-Red Hat people don't have shell access to. Furthermore, this ensures that released Extras packages are fully externally reproducible, since the Coverity scanner sits between the build scripts and GCC. The web-based reports portal would be still be accessible to package maintainers of course. Like Warren says, then there's no slowdown for the build system, we stay clear of any difficult contractual or legal issues related to access to Coverity binaries, and the packages are completely externally reproducible. Is there any extra hardware available? The Coverity bits don't run on PPC yet either, they are i386 & x86-64 only right now, so we don't need any more OpenPOWER boxes, only a few more Dells. Dan > This way Fedora and upstream benefits from Coverity analysis, and Fedora > remains ideologically pure. > > Thoughts? > > Warren Togami > wtogami at redhat.com >