|
Size: 4951
Comment:
|
Size: 2308
Comment: Adding schedule links
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Infrastructure = | # acl Known:read |
| Line 3: | Line 3: |
| == About Us == The Infrastructure Team consists of dedicated volunteers and professionals who provide servers, tools and utilities for the RPM Fusion Repository. We are the people that maintain the servers that run the RPM Fusion Infrastructure. We're located all over the globe so we communicate primarily by: |
= About Us = |
| Line 6: | Line 5: |
| * IRC You can find the #rpmfusion channel on [http://freenode.net/ freenode]. |
The Infrastructure Team consists of dedicated volunteers and professionals who provide servers, tools and utilities for the RPM Fusion Repositories. We are the people that maintain the servers that run the RPM Fusion Infrastructure. We're located all over the globe so we communicate primarily by: |
| Line 9: | Line 7: |
| ## We should talk about an potential Fedora-infrastructure-list@ or Admin@ to add ## ## * Mailing list ## The mailing list for the RPM Fusion Infrastructure is [http://rpmfusion.org/mailman/listinfo/rpmfusion-infrastructure-list ##rpmfusion-infrastructure-list@rpmfusion.org]. |
* '''IRC''' You can find the #rpmfusion channel on [[http://freenode.net/|freenode]]. |
| Line 14: | Line 10: |
| == Our Infrastructure == === Servers and Services === |
* '''Mailing list''' The mailing list for the RPM Fusion Infrastructure is [[http://lists.rpmfusion.org/mailman/listinfo/rpmfusion-sysadmin|sysadmin@rpmfusion.org]]. = Contribute to RPM Fusion Infrastructure = Ready to work with the RPM Fusion Infrastructure team? We're looking for smart, volunteers, dedicated system administrators and developers to help maintain our systems and also write some code. The RPM Fusion Infrastructure team is also a way to give back to the community. Go take a look at our [[Infrastructure/GettingStarted|Started page]]. = Our Architecture = == Servers and Services == === From 2008 to 2011 === |
| Line 25: | Line 32: |
| * `puppet1.rpmfusion.org` * System Management server (!PuppetMaster) |
|
| Line 26: | Line 35: |
| === Domain Names === | === Starting 2011 === * `hv01.ovh.rpmfusion.net` * KVM Hypervisor * [[Infrastructure/Architecture/Proposal|Next-step Architecture]] * [[Infrastructure/Team/Schedule|Schedule]] == Domain Names == |
| Line 31: | Line 48: |
| === Email Addresses === | == Email Addresses == |
| Line 34: | Line 51: |
| * `buildsys@` : ThorstenLeemhuis | * `buildsys@` : Build system list |
| Line 36: | Line 53: |
| * `cvsadmin@` : XavierLamien | * `cvsadmin@` : CVS Admin list |
| Line 39: | Line 56: |
| == Pending == | == Mailing Lists == |
| Line 41: | Line 58: |
||<rowstyle="color: white; background-color: #3074c2; font-weight: bold; text-align: center;"> '''Task''' || '''Owner''' || '''Status''' || '''Notes''' || ||||||||<rowstyle="color: black; background-color: #eeeff1; text-align: center"> '''Work in Progress / To do''' || ||<rowstyle="text-align: center"> FDS || MatthiasSaou ||<bgcolor="#00FF00"> Done || Set up the Fedora Directory Services || ||<rowstyle="text-align: center"> Plague Server || ThorstenLeemhuis ||<bgcolor="#00FF00"> Done || Set up the build system || ||<rowstyle="text-align: center"> FAS version 2 || XavierLamien ||<bgcolor="#00FF00"> Done || Set up the Fedora Account System 2 || ||<rowstyle="text-align: center"> [FAS2] database || XavierLamien ||<bgcolor="#00FF00"> Done || Set up the new database for fas2 || ||<rowstyle="text-align: center"> [FAS2] fas-Client || '''Unassigned''' ||<#FF0000> 0% || Fas-client needs to be installed on other rpmfusion box|services ---> {i} XL : I currently unable to do that as thias is the only one who has all the keys || ||<rowstyle="text-align: center"> [CVS] Modules || XavierLamien ||<bgcolor="#00FF00"> Done || Add script to create new modules on cvs repo || ||<rowstyle="text-align: center"> [CVS] Branches || XavierLamien ||<bgcolor="#00FF00"> Done || Add script to [create|add] branches on pkgs || ||<rowstyle="text-align: center"> [CVS] Upload.cgi || XavierLamien ||<bgcolor="#00FF00"> Done || Make the cvs works against CA certification || ||<rowstyle="text-align: center"> [CVS] cvs-import || XavierLamien ||<bgcolor="#00FF00"> Done || Merge script to deals with rpmfusion Infra || ||<rowstyle="text-align: center"> [CVS] Sources || XavierLamien ||<#00FF00> Done || Currently stored on cvs.rpmfusion.org box || ||<rowstyle="text-align: center"> Repository || ThorstenLeemhuis/Pix ||<#FF0000> 0% || Where to host the Repository ?<<BR>>knurd will talk to Pix?<<BR>>Do we want to reuse thias stuff as well? || ||<rowstyle="text-align: center"> Merge of packages || '''Unassigned''' ||<#FF0000> 0% || Availability of packages into rpmfusion repo|| ||<rowstyle="text-align: center"> [FAS2] Theme || XavierLamien || 15% || Add something which match with RPM fusion logo || ||<rowstyle="text-align: center"> [Bugzilla v3] Theme || '''Unassigned''' ||<#FF0000> 0% || Add Something cute to have a better view on all comment and flags. ---> {i} note that bugzilla's theme isn't the most important thing for now || ||<rowstyle="text-align: center"> Mailling list || '''Unassigned''' ||<#FF0000> ?? || {i} Add an rpmfusion-infrastructure-list@ or Admin@, cvs-changes-list@, cvs-admin-list@ || ||<rowstyle="text-align: center"> Irc Channel || '''Unassigned''' ||<#FF0000> ?? || {i} Add and rpmfusion-admin channel ?? <<BR>> ThorstenLeemhuis: I'd say we can create channels like #rpmfusion-{devel,admin,...} when really needed || ||||||||<rowstyle="color: black; background-color: #eeeff1; text-align: center"> '''Tasks Closed''' || ||<rowstyle="text-align: center"> FAS - Userbox || XavierLamien ||<#0000FF> 50% || Make the FAS able to create shell account on new users ---> {i} Canceled || ||<rowstyle="text-align: center"> FAS - Groupbox || XavierLamien ||<#0000FF> 50% || Fix group list on user edit page ---> {i} Canceled || |
See [[http://lists.rpmfusion.org|Mailing Lists]]. |
About Us
The Infrastructure Team consists of dedicated volunteers and professionals who provide servers, tools and utilities for the RPM Fusion Repositories. We are the people that maintain the servers that run the RPM Fusion Infrastructure. We're located all over the globe so we communicate primarily by:
IRC
You can find the #rpmfusion channel on freenode.
Mailing list
The mailing list for the RPM Fusion Infrastructure is sysadmin@rpmfusion.org.
Contribute to RPM Fusion Infrastructure
Ready to work with the RPM Fusion Infrastructure team? We're looking for smart, volunteers, dedicated system administrators and developers to help maintain our systems and also write some code. The RPM Fusion Infrastructure team is also a way to give back to the community. Go take a look at our Started page.
Our Architecture
Servers and Services
From 2008 to 2011
se01.es.rpmfusion.net
Web server (MoinMoin wiki, apache with mod_python) : http://rpmfusion.org/
Bugzilla server (MySQL, apache with SSL and mod_perl) : https://bugzilla.rpmfusion.org/
se02.es.rpmfusion.net
Account server (FDS, apache with SSL, PostgreSQL, FAS version 2) : https://fas.rpmfusion.org/ (aka ldap.rpmfusion.org)
CVS server (apache) : http://cvs.rpmfusion.org/
se03.es.rpmfusion.net
Build server (Plague, apache, MySQL) : http://buildsys.rpmfusion.org/
puppet1.rpmfusion.org
System Management server (PuppetMaster)
Starting 2011
hv01.ovh.rpmfusion.net
- KVM Hypervisor
Domain Names
rpmfusion.org : For all visible services.
rpmfusion.net : For all non-visible services (low level hostnames for example).
Email Addresses
These are all @rpmfusion.org email addresses :
buildsys@ : Build system list
accounts@ : XavierLamien
cvsadmin@ : CVS Admin list
noreply@ : /dev/null
Mailing Lists
See Mailing Lists.