Difference between revisions of "System Administration Tools for the ARM Build Farm"
(Created page with ' = Project Name = <!-- Replace "Project Name" with the actual name of the project in the line above. --> == Project Description == <!-- Description should be no longer than a …') |
|||
| Line 1: | Line 1: | ||
| + | = System Administration Tools for the ARM Build Farm = | ||
| + | <!-- Replace "Project Name" with the actual name of the project in the line above. --> | ||
| + | == Project Description == | ||
| − | + | The [[Fedora ARM Koji Buildsystem]] or "farm" consists of 23 ARM builder systems which will grow to 38 by the end of this semester. As it grows, the need for efficient system management tools increases. The previous semesters' students started the work of setting up [http://www.nagios.org/ nagios] (monitoring) and [[https://fedorahosted.org/func/ func]] (group control) tools. | |
| − | |||
| − | + | This project involves configuring these tools to work with all of the systems in the ARM build farm, as well as setting up and configuring the [http://www.puppetlabs.com/ puppet] (configuration management) tool. | |
| + | * Maximum number of students: 2 | ||
| + | * Skills required: Linux system administration, problem solving, documentation writing | ||
| + | * Resources: wiki notes from previous semesters (e.g., [[How to Setup and configure Nagios]]), [[Fedora ARM Koji Buildsystem]],[[CDOT Development Systems]] | ||
| + | * Expected result: nagios, func, and puppet working across the entire ARM build farm; documentation on how to use these tools on the farm and how to add additional devices | ||
| + | * Initial contacts: [[User:Chris Tyler|ctyler]], [[User:Paul.W|PaulW]] | ||
<!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. --> | <!-- Description should be no longer than a paragraph. Include links to any relevant on-line resources. For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. --> | ||
== Project Leader(s) == | == Project Leader(s) == | ||
| + | |||
| + | |||
| + | Not sure who the primary Project Leader(s) are for this project but according to the project description primary contacts are;<br /> | ||
| + | *Chris Tyler<br /> | ||
| + | *Paul W | ||
| + | |||
| + | |||
| + | |||
| + | Students that will be working on this project are listed below;<br /> | ||
| + | *Gian-Luca Casella | ||
| + | *Tim Furzer | ||
| + | *Pirathapan Sivalingam | ||
<!-- Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki and to blog sites. --> | <!-- Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki and to blog sites. --> | ||
Revision as of 22:04, 2 February 2011
Contents
System Administration Tools for the ARM Build Farm
Project Description
The Fedora ARM Koji Buildsystem or "farm" consists of 23 ARM builder systems which will grow to 38 by the end of this semester. As it grows, the need for efficient system management tools increases. The previous semesters' students started the work of setting up nagios (monitoring) and [func] (group control) tools.
This project involves configuring these tools to work with all of the systems in the ARM build farm, as well as setting up and configuring the puppet (configuration management) tool.
- Maximum number of students: 2
- Skills required: Linux system administration, problem solving, documentation writing
- Resources: wiki notes from previous semesters (e.g., How to Setup and configure Nagios), Fedora ARM Koji Buildsystem,CDOT Development Systems
- Expected result: nagios, func, and puppet working across the entire ARM build farm; documentation on how to use these tools on the farm and how to add additional devices
- Initial contacts: ctyler, PaulW
Project Leader(s)
Not sure who the primary Project Leader(s) are for this project but according to the project description primary contacts are;
- Chris Tyler
- Paul W
Students that will be working on this project are listed below;
- Gian-Luca Casella
- Tim Furzer
- Pirathapan Sivalingam
Project Contributor(s)
Project Details
Project Plan
Tracking mechanism (bugzilla, trac, github, ...):
Key contacts:
Goals for each release and plans for reaching those goals:
- 0.1
- 0.2
- 0.3
