From Fedora Project Wiki
< Infrastructure | RFR
m (1 revision(s)) |
(fix links to Infrastructure/MirrorManagement article) |
||
| Line 17: | Line 17: | ||
Expiration Date (required): 2 weeks before Fedora 7 release | Expiration Date (required): 2 weeks before Fedora 7 release | ||
Description/Summary: see [ | Description/Summary: see [[Infrastructure/MirrorManagement]] | ||
Project plan (Detailed): see [ | Project plan (Detailed): see [[Infrastructure/MirrorManagement]] | ||
Goals: see [ | Goals: see [[Infrastructure/MirrorManagement]] | ||
== Specific resources needed == | == Specific resources needed == | ||
A vhost or xen guest in PHX with external web (80/tcp and 443/tcp) access. TurboGears, connection to the database server. Database space. Cron jobs to create the mirrorlists and redirector regexp files. Connection to the Account database in PHX. | A vhost or xen guest in PHX with external web (80/tcp and 443/tcp) access. TurboGears, connection to the database server. Database space. Cron jobs to create the mirrorlists and redirector regexp files. Connection to the Account database in PHX. | ||
Revision as of 03:40, 4 June 2008
Project Sponsor
Name: Matt Domsch
Wiki Name: MattDomsch
Fedora Account Name: mdomsch
Group: Infrastructure
Infrastructure Sponsor: Matt Domsch
Project Info
Project Name: Mirror Manager
Target Audience: Mirror System Admins and end users via yum mirrorlist
Expiration Date (required): 2 weeks before Fedora 7 release
Description/Summary: see Infrastructure/MirrorManagement
Project plan (Detailed): see Infrastructure/MirrorManagement
Goals: see Infrastructure/MirrorManagement
Specific resources needed
A vhost or xen guest in PHX with external web (80/tcp and 443/tcp) access. TurboGears, connection to the database server. Database space. Cron jobs to create the mirrorlists and redirector regexp files. Connection to the Account database in PHX.