Open main menu

CDOT Wiki β

SBR600 Potential Projects

Revision as of 15:44, 16 January 2011 by Chris Tyler (talk | contribs) (→‎Introduction)
Important.png
This is a draft only!
It is still under construction and content may change. Do not rely on this information.

Introduction

This is a list of potential projects related to the SBR600 course that need people.

Students: Please select a project that you're interested in and add an entry to the project table/participants page.

Open Source Community Members: We welcome your recommendations for potential projects. Please create an account on this Wiki and create a description for your proposed project below. Please list your contact info (just an IRC or FAS2 name is OK) as well as links to any related web pages as Resources for the proposed project. (Questions? Ask Chris Tyler).

Notes

Each project listing contains a general description, plus this information:

  • Maximum number of students - Do not exceed this number without approval from your professor
  • Skills required - This is a rough list of some of the skills required for this project. This list may be incomplete or inaccurate, but it will give you a starting point in evaluating whether this project is a good fit for you. It is not assumed that you will have all of these skills at the outset of the project -- some of them will be picked up as you do the project.
  • Resources - An initial list of computer and information resources to get started on the project.
  • Expected result - A rough indication of what is expected at the conclusion of the project.
  • Initial contacts - Who to initially talk to about this project. These contacts may refer you on to other people with the respective open source communities.

You will have an opportunity to investigate, expand upon, and fine-tune this information as you prepare your initial project plan. For example, you may come up with a more detail list of expected results (deliverables), resources, and contacts during your planning.

Sample Project

This is a sample project stub. You can use the template for Sample Project in order to create a project page for one of the projects listed below. This is how you 'sign-up' for a project.

NOTE: if someone has already created the project page, speak to this person and see if you can join them. If so, simply add your name to the Project Leader(s) section on the project page. Otherwise, you can become a contributor later.

Fedora-ARM Projects

System Administration Tools for the ARM Build Farm

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.

Koji Hub on ARM

The Fedora ARM Koji Buildsystem system uses HongKong, an x86_64 system, as the Koji hub, along with a group of ARM builders.

Ideally, it would be nice to prove the ability of the Fedora-ARM project to be entirely self-hosting by using an ARM system as the Koji hub (this is sometimes called "Eating your own dogfood" in the industry). This project involves configuring the OpenRD-Client system as Koji hub and determining if this is a viable configuration.

  • Maximum number of students: 1
  • Skills required: Linux system administration, problem solving, documentation writing
  • Resources: wiki notes from previous 2 semesters, access to the OpenRD and a GuruPlug or BeagleBoard
  • Expected result: koji-hub running on the OpenRD; a recommendation on whether the OpenRD is suitable for use as a hub for the Fedora-ARM project
  • Initial contacts: ctyler, PaulW

Device Support and Testing: PandaBoard

Various ARM devices need different driver sets and/or kernels. This project will test the Fedora-ARM system on the PandaBoard, creating a kernel that works well with it, and figuring out how to use as many of the built-in peripherals as possible.

  • Maximum number of students: 1
  • Skills required: Linux system administration, kernel building, research, documentation writing
  • Resources: a PandaBoard, notes from other PanadaBoard support projects,
  • Expected result: a kernel (or kernels) for use with the PanadaBoard and the Fedora 12 or Fedora 13 root filesystems; user documentation on how to set up the PandaBoard with Fedora; wiki notes on setting up other ARM devices
  • Initial contacts: ctyler, PaulW

Add PandaBoards to the Fedora-ARM Build System

We have 15 PandaBoards on order for the Fedora-ARM build farm. These machines need to be configured and added into the farm, and then optimized to build packages as quickly as possible.

  • Maximum number of students: 2
  • Skills required: system administration, network administration, troubleshooting, benchmarking
  • Resources: PandaBoard systems
  • Expected result: a filesystem image and documented standard operating procedure for adding PanadaBoards to the build farm; new PandaBoards actively building
  • Initial contacts: ctyler, PaulW

iSCSI/AoE Support

iSCSI (SCSI over TCP/IP) and AoE (ATA-over-ethernet) are different SAN protocols that can be used on a standard ethernet network.iSCSI did not work reliably in Fedora 12 on ARM systems, but will be needed by future ARM server systems. AoE has not been well-tested on ARM systems.

Goals of this project: (1) iSCSI and AoE need to be tested for stability and performance. (2) The ARM builders, which currently use loopback-mounted filessystems on top of NFS, should be reconfigured to use iSCSI or AoE (whichever is the optimal solution) providing it is faster than the current solution.

  • Maximium number of students: 2
  • Skills required: Linux system administration, debugging and troubleshooting, kernel building, benchmarking, documentation writing
  • Resources: an ARM system, CDOT PC systems
  • Expected result: iSCSI on ARM fixed and tested, and changes pushed upstream; AoE tested on ARM; report comparing iSCSI and AoE performance on ARM; ARM buildsystem configured to use a high-performing iSCSI or AoE storage solution in place of the existing NFS system
  • Initial contacts: ctyler, PaulW

CreateRepo Performance Improvements

The Fedora-ARM build farm consists of the koji-hub/koji-web system (on HongKong, an x86_64 machine) and a group of ARM builders. HongKong also handles the [CreateRepo] tasks, which heavily load that machine. It might make sense to move those tasks to another machine, but doing so makes the CreateRepo jobs take a lot longer (15 minutes on HongKong vs. 55 minutes on another x86_64 server). This is presumably due to the overhead of sharing files between HongKong and the other server over NFS on the 100 Mbps Seneca network.

This project involves figuring out how to run the CreateRepo jobs more quickly. Possible solutions include a 1 Gbps LAN, a redistribution of the file storage or a change to a different file storage technology, or optimizing the CreateRepo tasks on HongKong for best speed.

  • Maximum number of students: 1
  • Skills required: system administration, benchmarking
  • Resources: CDOT server systems (HongKong, Ireland, Scottland)
  • Expected result: significant reduction in CreateRepo times, especially when multiple CreateRepo tasks are running
  • Initial contacts: ctyler, PaulW

RPM-based Kernels for Fedora ARM

On PC architecture systems (x86_64 and i386), Fedora manages and updates kernels as RPM packages, which modify grub boot parameters and the initial ram disk (initrd, configured by fedora:Dracut dracut).

On Fedora-ARM systems, the kernel is not managed via RPMs, grub is not used, and the initrd system is rarely used.

This project involves understanding how the PC (i386/x86_64) kernel/boot/initrd system works, determining which pieces can be reused on Fedora-ARM and which pieces need to be adapted or replaced, and implementing RPM-based kernel management for ARM.

  • Maximum number of students: 3
  • Skills required: Linux system administration, script writing, RPM packaging, kernel building, initrd debugging
  • Resources: an ARM system
  • Expected result: RPM-based Kernels work on Fedora-ARM, with changes committed upstream; documentation about the differences between kernel management on ARM and on PCs
  • Initial contacts: ctyler, PaulW

Fedora-ARM Communication

We're not doing a great job of communicating how the [:fedora:Architectures/ARM Fedora-ARM] project is doing, especially how [current builds] are progressing. The status page is very bare-bones and doesn't convey a lot of information, the Fedora-ARM wiki pages (on the fedora:Architectures/ARM Fedora and Seneca wikis) need to be made more useful to prospective users, and we need an effective communication strategy with the rest of the Fedora community. This project involves writing some web scripts to create a easy-to-use, informative status page (showing, for example, the current state and progress of the ARM builds), creating user documentation on the Fedora wiki, and fostering effective communication within the Fedora-ARM project and the larger Fedora community.

  • Maximum number of students: 2
  • Skills required: Apache administration, script-writing, effective written communication skills
  • Resources: the web server on HongKong, various data sources within the Fedora-ARM build system, Fedora project communication tools, access to ARM systems
  • Expected result: a useful (easy-to-use, informative) and automatically-updated Fedora-ARM status page; improved user documentation on the Fedora wiki (e.g., how to set up Fedora-ARM on common devices); better communication on the arm@lists.fedoraproject.org mailing list and the #fedora-arm IRC channel
  • Initial contacts: ctyler, PaulW

Automatic ExclusiveArch Addition/Removal

RPM packages may be specified as being suitable only for particular architectures through the use of ExclusiveArch and ExcludeArch tags in the spec file. If a base package, such as a language (interpreter or compiler) or a library does not build on a particular architecture, then dozens or hundreds of other packages cannot be built. These packages should all be marked as ExcludeArch in the upstream git package repository. Later, if that base package is updated to work on that arch, the ExcludeArch lines will need to be removed.

This project involves writing a script that will mass-add or mass-remove ExcludeArch tags (or, if those tags exist, add or remove a particular architecture), pushing the changes to the upstream git repo.

  • Maximum number of students: 1
  • Skills required: scripting (Python and/or bash), packaging
  • Expected result: a script that will do mass adds/removals of ExcludeArch tags given a list of packages
  • Resources: fedpkg libraries and source, Fedora package repo
  • Initial contacts: PaulW, ctyler

Fedora-ARM Package Building and Troubleshooting

The Fedora-ARM project is building Fedora 13/14/15 for the ARM architecture. As this proceeds, various problems arise. For example:

  • Some packages fail to build for ARM. They can be fixed up to build successfully on ARM, or if that's not possible, marked as unsuitable for ARM (ExlcudeArch).
  • If a group of packages is built to work with a specific version of a library, and a newer version of that library replaces the older version, then the packages that rely on that library can break. This can often be remedied simply by rebuilding the broken package; in other cases, patches are required.

Note that one package build issue will often block many other packages.

This project involves working with other members of the Fedora ARM build team to resolve package build problems and get F13/F14/F15 released for ARM as soon as possible.

  • Maximum number of students: 4
  • Skills required: packaging, troubleshooting
  • Expected result: problems with the Fedora-ARM builds are cleared as quickly as possible; F14-ARM released by the end of the semester
  • Resources: Fedora-ARM Koji build system, arm@lists.fedoraproject.org mailing list
  • Initial contacts: PaulW, ctyler

Fedora Projects

Package the Weave Server

Mozilla Sync is a technology for synchronizing personal data (bookmarks, passwords, form values, and cookies) across multiple machines. It uses a server known as Weave.

This project involves packaging Weave for Fedora and getting it through the package review process. (Why package the Weave server? So that people can run a private version, either for enhanced security or for testing).

  • Maximum number of students: 1
  • Skills required: Apache administration, packaging
  • Resources: CDOT systems
  • Expected result: the Weave server will be available in the main Fedora repositories (yum install weave)
  • Initial contacts: User:Mhoye mhoye

Package Hadoop

Apache Hadoop is a set of tools used for large-scale distributed computing. It would be great to get this packaged for Fedora.

  • Maximum number of students: 3
  • Skills required: packaging, system administration; familiarity with Java programming/packaging
  • Resources: CDOT Development Systems, devel mailing list (some work on Hadoop packaging has already been done)
  • Expected result: the three Apache Hadoop subprojects (Hadoop Common, HDFS, and MapReduce) will be available in the main Fedora repositories (yum install hadoop-common hdfs mapreduce)
  • Initial contacts: ctyler

Package the WIX Toolchain

[WIX] is an open-source packaging system for Microsoft Windows software. It is used to prepare software packages that can be installed on a Windows machine. However, the WIX tools themselves can run on Linux, which is useful for cross-development (writing software on Linux for use on Windows, e.g., the virt-manager utilities for Windows virtual machine guests).

This project involves packaging WIX for Fedora and getting it through the package review process.

  • Maximum number of students: 1
  • Skills required: packaging
  • Resources: CDOT Development Systems
  • Expected result: the WIX software will be available in the main Fedora repositories (yum install wix)
  • Initial contacts: mhoye, sdowne

Koji Setup Documentation

The Koji documentation is obsolete and needs a overhaul. This project involves reading the current documentation, updating and editing it, and testing it by setting up a Koji system.

  • Maximum number of students: 2
  • Skills required: writing, system administration
  • Resources: CDOT Development Systems, Fedora wiki
  • Expected result: a complete, well-written guide to setting up a Koji system (from A-Z)
  • Initial contacts: ctyler, dgilmore

AutoQA

AutoQA is an automated test system for Fedora. At present there are event watchers for koji builds, bodhi updates, repo changes, and nightly installed images; these events trigger a small number of tests, but more tests are needed.

  • Maximum number of students: 3
  • Skills requires: Python scripting, scripting, system administration, packaging
  • Resources: CDOT systems
  • Expected results: additional tests for AutoQA, accepted/committed into the main AutoQA codebase
  • Initial contacts: JLaska

Fedora-Mozilla Projects

Repository Setup for Mozilla Nightlies and Betas

Many web developers want access to the latest Firefox pre-releases, including the nightly builds and beta releases. Mozilla's build team wants to make these accessible as parallel-installable binaries, released through a Fedora-compatible repository. Last semester, a group of SBR600 students set most of this up; this project involves extending and improving their work.

See bug 600317.

  • Maximum number of students: 2
  • Skills required: system administration, scripting, packaging
  • Resources: scripts and configuration from the previous semester
  • Expected result: fully-functioning repository configuration ready for installation on Mozilla's systems; well-written documentation
  • Initial contacts: armenzg, ctyler


Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=SBR600_Potential_Projects&oldid=55110"