Difference between revisions of "Koji hub on arm"
(→Project Plan) |
(→Project Plan) |
||
| (15 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
== Project Description == | == Project Description == | ||
| − | This project will entail, implementing and documenting the koji build system on the hub, which will allow for the entire build farm to be arm based, with no need for any other processor. | + | This project will entail, implementing and documenting the koji build system on the hub [http://www.globalscaletechnologies.com/t-openrdcdetails.aspx Open-RD], which will allow for the entire build farm to be arm based, with no need for any other processor. This Will be a great achievement, by being able to do this it makes way for a new type of buildfarm, one that is energy efficient, cost efficient, and easy to maintain. |
== Project Leader(s) == | == Project Leader(s) == | ||
| Line 17: | Line 17: | ||
== Project Plan == | == Project Plan == | ||
| − | Tracking mechanism (bugzilla, trac, github, ...): | + | Tracking mechanism (bugzilla, trac, github, ...): I will be using trac for this project. |
Key contacts: | Key contacts: | ||
| Line 24: | Line 24: | ||
Goals for each release and plans for reaching those goals: | Goals for each release and plans for reaching those goals: | ||
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | <!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. --> | ||
| − | * 0.1 To begin research on the Hub, and Koji, to determine what needs to be done in order to | + | * 0.1 To begin research on the Hub, and Koji, to determine what needs to be done in order to begin implementation |
* 0.2 Install all prerequisite services on the HUB needed for Koji to Function | * 0.2 Install all prerequisite services on the HUB needed for Koji to Function | ||
* 0.3 Begin initial builds and configuration of Koji on the Hub and Document all findings along the way | * 0.3 Begin initial builds and configuration of Koji on the Hub and Document all findings along the way | ||
| Line 33: | Line 33: | ||
=== Mailing Lists === | === Mailing Lists === | ||
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | <!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org --> | ||
| + | [https://lists.fedoraproject.org/mailman/listinfo/arm Fedora Arm Mailing List] | ||
| + | |||
| + | === IRC === | ||
| + | 1. #koji on irc.freenode.net | ||
| + | |||
| + | 2. #fedora-devel on irc.freenode.net | ||
| + | |||
| + | 3. #fedora on irc.freenode.net | ||
| + | |||
| + | 4. #fedora-arm on irc.freenode.net | ||
=== Upsteam Wiki and Web === | === Upsteam Wiki and Web === | ||
| Line 39: | Line 49: | ||
=== Links/Bugs/Tracking === | === Links/Bugs/Tracking === | ||
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> | <!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) --> | ||
| + | [https://fedorahosted.org/koji/wiki Koji Project Page] | ||
| + | |||
| + | [http://fedoraproject.org/wiki/Koji Fedora Koji Page] | ||
=== Source Code Control === | === Source Code Control === | ||
| Line 47: | Line 60: | ||
==== Seneca Particpants ==== | ==== Seneca Particpants ==== | ||
| − | Anthony Boccia | + | [http://zenit.senecac.on.ca/wiki/index.php/User:Aeboccia Anthony Boccia] IRC: SHARPY |
==== Non-Seneca Participants ==== | ==== Non-Seneca Participants ==== | ||
Latest revision as of 11:05, 3 February 2011
Contents
Project Name
Koji Hub Arm system
Project Description
This project will entail, implementing and documenting the koji build system on the hub Open-RD, which will allow for the entire build farm to be arm based, with no need for any other processor. This Will be a great achievement, by being able to do this it makes way for a new type of buildfarm, one that is energy efficient, cost efficient, and easy to maintain.
Project Leader(s)
Anthony Boccia
Project Contributor(s)
Project Details
Many things will have to take place on the HUB before Koji setup can begin, mainly the installation of Apache, mod_ssl, and postgressql_server, so the first major step is to get these services implemented and working,before beginning the first attempts at Koji installation.
Project Plan
Tracking mechanism (bugzilla, trac, github, ...): I will be using trac for this project.
Key contacts: Paul Whalen
Goals for each release and plans for reaching those goals:
- 0.1 To begin research on the Hub, and Koji, to determine what needs to be done in order to begin implementation
- 0.2 Install all prerequisite services on the HUB needed for Koji to Function
- 0.3 Begin initial builds and configuration of Koji on the Hub and Document all findings along the way
- 0.4 By the end, one would like to have the Koji arm hub up and running, with fresh documentation for install on ARM
Communication
Mailing Lists
IRC
1. #koji on irc.freenode.net
2. #fedora-devel on irc.freenode.net
3. #fedora on irc.freenode.net
4. #fedora-arm on irc.freenode.net
Upsteam Wiki and Web
Links/Bugs/Tracking
Source Code Control
Blogs
Seneca Particpants
Anthony Boccia IRC: SHARPY
