infrastructure July 2006

infrastructure@lists.fedoraproject.org

27 participants
41 discussions

[Fedora-infrastructure-list] AccountSystem2 updated
by TomLy 07 Jul '06

07 Jul '06

The AccountSystem2 wiki page has been updated with the discussion that occurred today. http://fedoraproject.org/wiki/Infrastructure/AccountSystem2 ~lyz

2 2

[Fedora-infrastructure-list] Meeting log - 2006-07-06
by Elliot Lee 07 Jul '06

07 Jul '06

Hey all, Here's the log from yesterday's meeting in case you missed it... Thanks to everyone who came! Best, -- Elliot

1 0

[Fedora-infrastructure-list] Source file consolidation on CVS
by Mike McGrath 07 Jul '06

07 Jul '06

I'll be working to consolidate some of the source files on the CVS box over the next couple of days. Pay attention and let me know immediately if something breaks. I don't foresee any issues. Right now legacy, cvs, and dist all have individual sources in them. The sources are stored by file name and md5sum, for example: putty-0.58.tar.gz/ffb78a7db7e4802896189b2112714a9f/putty-0.58.tar.gz A collision between the different trees is unlikely. The purpose for this consolidation is to ease the efforts of the legacy team and provide them a proper development and build environment. In the end a source tarball is a source tarball, it makes sense to store them in one spot. Currently the dist repo is 73G and the extras repo is 12G. It seems a shame to make a copy of all of that when the exact same files would be a directory away. Send objections, comments, suggestions and consecutive unmarked-bills my way. -Mike

2 1

[Fedora-infrastructure-list] Firewall tool update
by Luke Macken 06 Jul '06

06 Jul '06

A couple of meetings ago someone mentioned the tool pyroman[0] in regard to managing the firewalls on our infrastructure. Since then, I've been playing around with this tool, and have been fairly impressed. I've imported pyroman 0.3 along with a _basic_ Fedora infrastructure profile into cvs. I've added all of our PHX machines listed on InfrastructurePrivate, and added some other minor tweaks. It's not 100% ready for deployment yet, it still needs: o to allow traffic to most services on our machines o profiles for our machines at Duke o to be compared against our current rc.firewall script - I've ported over most of it (the stuff I could actually understand), but there might be some stuff I missed o LOTS of testing The more testing and the more eyes we can get on this, the better. You should be able to hop on any machine and check it out of cvs: cvs -d cvs-int.fedora.phx.redhat.com:/cvs/fedora co pyroman >From here, you can run `./pyroman --dump`, which will spit out all of the chains instead of just trying to load them. Hack away, infrastructure ninjas! luke [0]: http://pyroman.alioth.debian.org

1 1

[Fedora-infrastructure-list] Legacy CVS
by Mike McGrath 06 Jul '06

06 Jul '06

The Legacy CVS is up now. Just set the following: export CVSROOT=":ext:YOURUSERNAME@cvs.fedora.redhat.com:/cvs/legacy/" export CVS_RSH="ssh" You'll have to be in the legacy group to commit. You should be able to co FC-3, packages, and rpms. Jesse feel free to tweak it however you need it if there are other changes you need me to make or find anything I missed let me know. This repo was based off of the dist repo so its using those Makefiles. -Mike

2 1

[Fedora-infrastructure-list] Backup update
by Dennis Gilmore 05 Jul '06

05 Jul '06

Hey All, Ive setup a page on the wiki to gather all the information on backup options. http://www.fedoraproject.org/wiki/Infrastructure/Backup -- Dennis Gilmore, RHCE Proud Australian

1 0

[Fedora-infrastructure-list] Dell server donation deadline approaching
by Matt Domsch 05 Jul '06

05 Jul '06

Greetings. As I mentioned on IRC and on email a bit back, Dell would like to donate a couple servers to the Fedora project, to be used wherever hardware (not people) are the bottleneck towards progress. We've got budgeted enough for 2 moderately configured PowerEdge 2950 servers, and have until about July 18 to get them ordered (else we lose the money). I'd be happy to work with whomever appropriate to get the order placed. Please cc: me explicitly as I'm not on f-i-l. 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

5 5

[Fedora-infrastructure-list] Account system updates
by TomLy 05 Jul '06

05 Jul '06

I started up the wiki page for the requirements on the new account system. It is at http://fedoraproject.org/wiki/Infrastructure/AccountSystem2 . There isn't that much there now. The last time I sent the list of enhancements request out, I really didn't get many enhancements back. There was just a discussion on what the backend technology should be. I did pull out one feature. Give more information about a user when deciding to sponsor a person. EG. bugzilla enteries This time around I would like you all to just give me a list of enhancements and not worry about the implementation details as much :) . I really want to have some good stuff to report in tomorrow's meeting. Please help me out :). ~lyz

4 6

[Fedora-infrastructure-list] Cacti's running
by Mike McGrath 03 Jul '06

03 Jul '06

I'd been meaning to add this for a while with Nagios. Cacti is up and running and monitoring some of our servers. For those that don't know Cacti will allow us to get good trending information from the servers. We can easily track things like drive space, CPU/Load, and mem usage over a period of time (even years if we need to). It's presently open to anyone in the sysadmin group. https://admin.fedoraproject.org/cacti/ Feel free to add more hosts if you're familiar with Cacti. Eventually we can also setup monitoring for our databases to see how and when they're getting hit hard. We can lock the security on cacti down tighter if need be but I figured I'd keep it fairly open for now. Don't go breaking it! -Mike

2 1

[Fedora-infrastructure-list] Extras Package Database
by Elliot Lee 02 Jul '06

02 Jul '06

Hi all, http://fedoraproject.org/wiki/Infrastructure/PackageDatabase has been out there for a bit... I've put together a strawman schema (as a TurboGears model.py) to help move things along - apologies if someone else has beaten me to it. I think at this point the right questions to be asking are long the lines of "will this schema support feature X or use case Y?". From a quick glance at the web page, I *think* it mostly will. There are some problems with this still, but open source is all about fixing those problems :) class Collection(SQLObject): name = StringCol(length=128, notNone=True) # "Core", "Extras", or whatever names-for-grouping you want class Package(SQLObject): name = StringCol(length=128, notNone=True) # "Core", "Extras", or whatever names-for-grouping you want created = DateTimeCol(default=sqlbuilder.func.NOW(), notNone=True) status = EnumCol(enumValues=('awaitingreview', 'approved', 'denied'), default='awaitingreview', notNone=True) class PackageHistory(SQLObject): # Records changes to packages package = ForeignKey('Package', notNone=True) by_user_id = IntCol(notNone=True) # Foreign key into account database - user who made the change action = EnumCol(enumValues=('added', 'removed', 'statuschanged'), notNone=True) status = StringCol(length=128, notNone=True) # Not EnumCol, but could be changed to be one. when = DateTimeCol(default=sqlbuilder.func.NOW(), notNone=True) class PackageListing(SQLObject): package = ForeignKey('Package', notNone=True) collection = ForeignKey('Collection', notNone=True) created = DateTimeCol(default=sqlbuilder.func.NOW(), notNone=True) status = EnumCol(enumValues=('awaitingreview', 'awaitingbranch', 'approved', 'denied'), default='awaitingreview', notNone=True) class PackageListingHistory(SQLObject): # Records changes to packages package_listing = ForeignKey('PackageListing', notNone=True) by_user_id = IntCol(notNone=True) # Foreign key into account database - user who made the change action = EnumCol(enumValues=('added', 'removed', 'statuschanged'), notNone=True) status = StringCol(length=128, notNone=True) # Not EnumCol, but could be changed to be one. when = DateTimeCol(default=sqlbuilder.func.NOW(), notNone=True) class PackageVersion(SQLObject): # A specific version on a specific branch package_listing = ForeignKey('PackageListing', notNone=True) version = StringCol(length=128, notNone=True) status = EnumCol(enumValues=('awaitingdevel', 'awaitingreview', 'awaitingqa', 'awaitingpublish', 'approved', 'denied', 'obsolete'), default='awaitingdevel', notNone=True) created = DateTimeCol(default=sqlbuilder.func.NOW(), notNone=True) class PackageVersionHistory(SQLObject): # Records changes to packages package_version = ForeignKey('PackageVersion', notNone=True) by_user_id = IntCol(notNone=True) # Foreign key into account database - user who made the change action = EnumCol(enumValues=('added', 'statuschanged'), notNone=True) status = StringCol(length=128, notNone=True) # Not EnumCol, but could be changed to be one. when = DateTimeCol(default=sqlbuilder.func.NOW(), notNone=True) class PackageInterest(SQLObject): # Note: PackageInterestHistory table assumes that records will never be removed from here. # Instead, set the status to 'obsolete' user_id = IntCol(notNone=True) package_listing = ForeignKey('PackageListing', notNone=True) status = EnumCol(enumValues=('awaitingreview', 'approved', 'denied', 'obsolete'), default='awaitingreview', notNone=True) role = EnumCol(enumValues=('watcher', 'owner'), default='watcher', notNone=True) # Used for authorization class PackageInterestHistory(SQLObject): package_interest = ForeignKey('PackageInterest', notNone=True) action = EnumCol(enumValues=('added', 'statuschanged'), notNone=True) status = StringCol(length=128, notNone=True) # Not EnumCol, but could be changed to be one. when = DateTimeCol(default=sqlbuilder.func.NOW(), notNone=True) Best, -- Elliot

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure July 2006