Re: F10 Beta release
Paul W. Frields said the following on 09/30/2008 02:40 PM Pacific Time: Great job with the release this morning, guys. I know there were some gremlins in a torrent or two, but overall very painless and you guys made it look easy (as always). Hurrah, another milestone on the path to Cambridge! If anyone has any issues, we could plant them on a page for the next release day planning group call. One idea I had... could we be very explicit when we tell people where to file bugs by giving them a full URL to rawhide so they don't have navigate the bugzilla gauntlet? Does anyone know how to format the URL so it goes straight to new bug for rawhide? John ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10 Beta release
On Tue, 30 Sep 2008, Paul W. Frields wrote: Great job with the release this morning, guys. I know there were some gremlins in a torrent or two, but overall very painless and you guys made it look easy (as always). Hurrah, another milestone on the path to Cambridge! If anyone has any issues, we could plant them on a page for the next release day planning group call. I'd like to give a shout out to Seth Vidal and the guys at ibiblio for getting the new torrent server installed and ready in a very short time span. Also, unrelated to torrent, I'd like to point out some other metrics I've been putting together for release days: https://admin.fedoraproject.org/zabbix/charts.php?fullscreen=0groupid=0hostid=10071graphid=380 and https://admin.fedoraproject.org/zabbix/charts.php?fullscreen=0groupid=0hostid=10071graphid=379 Those are updated every 30 seconds (right now at least) and give a view of hits / second for mirrors and the wiki. This is something we can watch on release day instead of sitting around saying things like are they here yet? :) In the future it may also help diagnose problems. -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10 Beta release
On Tuesday 30 September 2008 23:59:40 John Poelstra wrote: One idea I had... could we be very explicit when we tell people where to file bugs by giving them a full URL to rawhide so they don't have navigate the bugzilla gauntlet? Does anyone know how to format the URL so it goes straight to new bug for rawhide? How about this URL? https://bugzilla.redhat.com/enter_bug.cgi?product=Fedoraversion=rawhide You can also go to create new bug report, select Fedora and then notice the remember values and create bookmarkable template button to preselect more. Regards, TIll signature.asc Description: This is a digitally signed message part. ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10?
On Mon, 2008-05-19 at 23:44 -0400, Ricky Zhou wrote: * Asterisk coolness? I'm almost always available and willing to help out with Asterisk stuff... Let me know if/when you need any help, and I'd be willing to put in some time to add all kinds of Asterisk coolness. -Jared ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10?
Things I'd like but probably can't work on myself: * GeoIP/DNS based proxying. I'm in Europe and request admin.fedoraproject.org I get the European app server. I'm in the US I get PHX or tummy. - This might make it possible for us to have app servers around the world. We'd still have latency from database calls having to get replies from PHX but for calls between apps all requests would stay in the same colo. Things I'll have a hand in: * New python-fedora API with exception-like error handling client-side and more standardization server-side. - Porting all our web apps to the new architecture. * Optimize db calls within TG applications to make them as snappy as possible. I can do this for SQLAlchemy but SQLObject isn't flexible enough. Any page which is for viewing data and is returning multiple records is potentially a good candidate. * OpenID auth provider for our TG apps (if it's faster/better than our current jsonfas provider). We don't gain any features from an OpenID provider unless we want to allow other OpenID servers to authenticate our users. * pkgdb: I'm going to concentrate on refactoring existing pkgdb code. I'm hoping mapleoin will keep up the good work he's been doing adding new features. * New koji db server. * Moving TG apps from supervisor to mod_wsgi -Toshio ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10?
On Tue, May 20, 2008 at 09:15:28AM -0700, Toshio Kuratomi wrote: Things I'd like but probably can't work on myself: [...] * Optimize db calls within TG applications to make them as snappy as possible. I can do this for SQLAlchemy but SQLObject isn't flexible enough. Any page which is for viewing data and is returning multiple records is potentially a good candidate. Speaking of stuff I'd love to see happen, but don't have the time for :) - Port bodhi to SQLAlchemy luke ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10?
On Tue, May 20, 2008 at 02:18:53PM -0400, Yaakov Nemoy wrote: On Tue, May 20, 2008 at 1:54 PM, Luke Macken [EMAIL PROTECTED] wrote: On Tue, May 20, 2008 at 09:15:28AM -0700, Toshio Kuratomi wrote: Things I'd like but probably can't work on myself: [...] * Optimize db calls within TG applications to make them as snappy as possible. I can do this for SQLAlchemy but SQLObject isn't flexible enough. Any page which is for viewing data and is returning multiple records is potentially a good candidate. Speaking of stuff I'd love to see happen, but don't have the time for :) - Port bodhi to SQLAlchemy Depends on how complicated your stuff is already. If it's mostly just a bunch of tables, and the oddball query, I can probably do it in about a day. If it's alot of complicated composite tables with composite keys, custom data types, custom rules, and massive dependencies, then it could take 2-3 days. Let me know when you need help. Cool. Give me a week or so to finish up some major bodhi changes that I have underway, and the releng2 migration. I've created a ticket so we can track this task, and I'll let you know when it's safe to dive in. https://fedorahosted.org/bodhi/ticket/202 Thanks! luke ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10?
On 2008-05-19 10:27:52 PM, Mike McGrath wrote: All in all I feel it was a good release. So my question to the team, what would you all like to see over the next 6 months? * New wiki :-) * More/better documentation * FAS improvements + Certificate Authority * A more complete test environment? * Asterisk coolness? Thanks, Ricky pgpbJ8SLsLyMq.pgp Description: PGP signature ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: F10?
Mike McGrath wrote: So F9 is out the door and we had a very exciting last 6 months. Here's the short list: * FAS2 * /mnt/koji migration and deployment * Backup system up and running * Collaboration servers brought up (gobby and asterisk POC) * UTC switch The focus for this last release was mostly around sanity. Cleaning up some configs, things like that. We actually did a very good job of that. All in all I feel it was a good release. So my question to the team, what would you all like to see over the next 6 months? I agree, the release went smoothly, compared to what I remember a year back when I was helping out. Some of the 'would be nice' items I guess are: * Logical separation of apps/services - i.e. app2's load really spikes when msgmerge runs (I'm assuming this is l10n stuff, why should this have to run on the same server that runs the wiki etc, if possible it'd be nice to have a similar setup like rel-eng has) * Better load balancing, I'm assuming http://fedoraproject.org/wiki/Infrastructure/Architecture is still technically correct, it'd be nice to have the proxy servers randomly choosing an App server, is this even possible? * Something that Debian has as a service to packagers is machines of various architectures that can be used for debugging/solving build problems, koji scratch builds solve part of the problem, but access to the chroot or something like that would be even better, I know people offer this sort of setup on a 'by request' basis, but if we retiring builders etc in the future, instead of sending them to the graveyard, this is an option. And of course some of the upcoming stuff: * Mediawiki * New DB Server for Koji * Network storage for tarball uploads * Elections App (expect a call for testers soon) - Nigel ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
