m (1 revision(s)) |
No edit summary |
||
| (10 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{autolang|base=yes}} | |||
{{header|infra}} | |||
= FIGs = | = FIGs = | ||
== What is a FIG? == | == What is a FIG? == | ||
A FIG (Fedora Infrastructure Group) is a cluster of people that work together on a specific part of Fedora's Infrastructure. The organizational structure of a FIG is simple. Sponsors, non sponsors. All of whom have equal access to the environment with | A FIG (Fedora Infrastructure Group) is a cluster of people that work together on a specific part of Fedora's Infrastructure. The organizational structure of a FIG is simple. Sponsors, non sponsors. All of whom have equal access to the environment with one exception, sponsors can grant access to other people for whom they are responsible. | ||
Users in each FIG have access to the machines themselves as well as access to the | Users in each FIG have access to the machines themselves as well as access to the git that hosts configuration management. Each FIG is part of the Fedora Infrastructure Project and all are part of the same team. | ||
== What are the FIGs? == | == What are the FIGs? == | ||
=== sysadmin-build === | === [[ Infrastructure/FIGs/FIG_Build_job_description| sysadmin-build ]] === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-build members] ) | ||
The sysadmin build group is responsible for the entire build environment. This includes the plague and koji masters as well as the various build machines (currently ppc and x86_64). This group has shell access to the machines and configuration environment. | The sysadmin build group is responsible for the entire build environment. This includes the plague and koji masters as well as the various build machines (currently ppc and x86_64). This group has shell access to the machines and configuration environment. | ||
=== [[ Infrastructure/FIGs/FIG_CVS_job_description| sysadmin-cvs]] === | |||
=== sysadmin-cvs === | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-cvs members] ) | ||
([https://admin.fedoraproject.org/accounts/group/ | |||
All members in the sysadmin-cvs group exist to maintain our source control environment and related machines (presently only the cvs box). This includes all packages and lookaside cache. | All members in the sysadmin-cvs group exist to maintain our source control environment and related machines (presently only the cvs box). This includes all packages and lookaside cache. | ||
=== sysadmin-web === | === [[ Infrastructure/FIGs/FIG_WEB_job_description| sysadmin-web]] === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-web members] ) | ||
All of our web sites are maintained by the sysadmin-web group. This includes all web site application servers as well as the proxy servers. This is our busiest group as most of our active changes | All of our web sites are maintained by the sysadmin-web group. This includes all web site application servers as well as the proxy servers. This is our busiest group as most of our active changes are on web servers, which comprise the largest number of servers. | ||
=== sysadmin-hosted === | === [[ Infrastructure/FIGs/FIG_Hosted_job_description| sysadmin-hosted]] === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-hosted members] ) | ||
The sysadmin hosted group maintains the servers that run [https://fedorahosted.org/ Fedora Hosted projects] . Team members handle the creation/administration of Hosted projects/repos and related services. | The sysadmin hosted group maintains the servers that run [https://fedorahosted.org/ Fedora Hosted projects] . Team members handle the creation/administration of Hosted projects/repos and related services. | ||
=== sysadmin-releng === | === sysadmin-releng === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-releng members] ) | ||
The Release Engineering team has a set of servers it uses to create Fedora. This group has shell access to these servers and related configs in puppet. | The Release Engineering team has a set of servers it uses to create Fedora. This group has shell access to these servers and related configs in puppet. | ||
=== sysadmin-main === | === sysadmin-main === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-main members] ) | ||
The sysadmin-main group is the group that has root access to all other machines in our environment. This group is closely monitored and access is highly restricted, no one is admitted directly into the sysadmin-main group without first proving themselves in another group. | The sysadmin-main group is the group that has root access to all other machines in our environment. This group is closely monitored and access is highly restricted, no one is admitted directly into the sysadmin-main group without first proving themselves in another group. | ||
=== sysadmin-dba === | === sysadmin-dba === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-dba members] ) | ||
The DBA group has access to all of our database and LDAP machines. Due to the highly sensitive nature of the database boxes this group, like sysadmin-main, is highly restricted. | The DBA group has access to all of our database and LDAP machines. Due to the highly sensitive nature of the database boxes, this group, like sysadmin-main, is highly restricted. | ||
=== sysadmin-test === | === sysadmin-test === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-test members] ) | ||
sysadmin-test grants access to our bed of test-servers. The test servers (like publictest1) are primarily used to do proof of concept implementations for Fedora Infrastructure or other projects. Anyone filling out an RFR needs to get into this group in order to prove their system should be used in Fedora's production environment. | sysadmin-test grants access to our bed of test-servers. The test servers (like publictest1) are primarily used to do proof of concept implementations for Fedora Infrastructure or other projects. Anyone filling out an RFR needs to get into this group in order to prove their system should be used in Fedora's production environment. | ||
=== sysadmin-devel === | === sysadmin-devel === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-devel members] ) | ||
A great deal is done with development in Fedora's Infrastructure. This group | A great deal is done with development in Fedora's Infrastructure. This group grants write access to the fedora-infrastructure git repo. Working on our scripts and code is especially important when getting to know the group. | ||
=== sysadmin-noc === | === [[ Infrastructure/FIGs/FIG_NOC_job_description| sysadmin-noc ]] === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-noc members] ) | ||
The noc team has access to nagios and cacti (and whatever other monitoring tools we are using) They also have read only access to many of the systems to poke around and see what might be wrong as well as find things that need to be monitored. | The noc team has access to nagios and cacti (and whatever other monitoring tools we are using) They also have read only access to many of the systems to poke around and see what might be wrong as well as find things that need to be monitored. | ||
=== sysadmin-tools === | === sysadmin-tools === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin-tools members] ) | ||
Part of the Infrastructure teams job is to provide tools to make our developers and contributors more efficient. The sysadmin tools group is in charge of these services. Such services might include asterisk (VoIP), gobby, mailman, etc. This team works closely with the sysadmin-web team. | Part of the Infrastructure teams job is to provide tools to make our developers and contributors more efficient. The sysadmin tools group is in charge of these services. Such services might include asterisk (VoIP), gobby, mailman, etc. This team works closely with the sysadmin-web team. | ||
=== sysadmin === | === sysadmin === | ||
([https://admin.fedoraproject.org/accounts/group/ | ([https://admin.fedoraproject.org/accounts/group/members/sysadmin members] ) | ||
The sysadmin group is the base group required by all other FIGs. Nagios notifications are sent to this group, it does not provide any additional access but is a good way to welcome yourself to the team. | The sysadmin group is the base group required by all other FIGs. Nagios notifications are sent to this group, it does not provide any additional access but is a good way to welcome yourself to the team. | ||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
Latest revision as of 13:19, 1 January 2012
FIGs
What is a FIG?
A FIG (Fedora Infrastructure Group) is a cluster of people that work together on a specific part of Fedora's Infrastructure. The organizational structure of a FIG is simple. Sponsors, non sponsors. All of whom have equal access to the environment with one exception, sponsors can grant access to other people for whom they are responsible.
Users in each FIG have access to the machines themselves as well as access to the git that hosts configuration management. Each FIG is part of the Fedora Infrastructure Project and all are part of the same team.
What are the FIGs?
sysadmin-build
(members )
The sysadmin build group is responsible for the entire build environment. This includes the plague and koji masters as well as the various build machines (currently ppc and x86_64). This group has shell access to the machines and configuration environment.
sysadmin-cvs
(members )
All members in the sysadmin-cvs group exist to maintain our source control environment and related machines (presently only the cvs box). This includes all packages and lookaside cache.
sysadmin-web
(members )
All of our web sites are maintained by the sysadmin-web group. This includes all web site application servers as well as the proxy servers. This is our busiest group as most of our active changes are on web servers, which comprise the largest number of servers.
sysadmin-hosted
(members )
The sysadmin hosted group maintains the servers that run Fedora Hosted projects . Team members handle the creation/administration of Hosted projects/repos and related services.
sysadmin-releng
(members )
The Release Engineering team has a set of servers it uses to create Fedora. This group has shell access to these servers and related configs in puppet.
sysadmin-main
(members )
The sysadmin-main group is the group that has root access to all other machines in our environment. This group is closely monitored and access is highly restricted, no one is admitted directly into the sysadmin-main group without first proving themselves in another group.
sysadmin-dba
(members )
The DBA group has access to all of our database and LDAP machines. Due to the highly sensitive nature of the database boxes, this group, like sysadmin-main, is highly restricted.
sysadmin-test
(members )
sysadmin-test grants access to our bed of test-servers. The test servers (like publictest1) are primarily used to do proof of concept implementations for Fedora Infrastructure or other projects. Anyone filling out an RFR needs to get into this group in order to prove their system should be used in Fedora's production environment.
sysadmin-devel
(members )
A great deal is done with development in Fedora's Infrastructure. This group grants write access to the fedora-infrastructure git repo. Working on our scripts and code is especially important when getting to know the group.
sysadmin-noc
(members )
The noc team has access to nagios and cacti (and whatever other monitoring tools we are using) They also have read only access to many of the systems to poke around and see what might be wrong as well as find things that need to be monitored.
sysadmin-tools
(members )
Part of the Infrastructure teams job is to provide tools to make our developers and contributors more efficient. The sysadmin tools group is in charge of these services. Such services might include asterisk (VoIP), gobby, mailman, etc. This team works closely with the sysadmin-web team.
sysadmin
(members )
The sysadmin group is the base group required by all other FIGs. Nagios notifications are sent to this group, it does not provide any additional access but is a good way to welcome yourself to the team.