Winter 2010 Posters/Koji Hub Poster

From CDOT Wiki
Revision as of 22:16, 16 April 2010 by Paul.W (talk | contribs) (Names)
Jump to: navigation, search


Project Name

Koji Hub Installation and Configuration

Name

Paul Whalen

The Koji Build System

At the beginning of the Winter 2010 semester the Software Build and Release 600 class set out to create a Koji build system for the ARM architecture. Koji is the software that builds and tests packages for the Fedora Project. At the center of Koji operations is the Koji Hub. The plan was to initially set up all components of the Koji build system on the one server, with the Koji builder Daemons running on Virtual ARM Machines. After installation and configuration of the PostgreSQL, the Koji Hub would be configured, followed by the other components of Koji including the Koji Web, Kojira and finally the set up of the actual builders themselves.

Koji Components

Koji Hub - an XML-RPC server that receives and relies upon calls from the Koji Builder Daemons and other Koji components to initiate communications.

Koji Web - an interactive web interface that runs on mod_python modules in the Apache Web Server. The Koji Web provides an interface for Koji users to see the status of queued builds and information for trouble shooting unsuccessful build attempts.

Koji Builder Daemon - the build daemon that runs on each of the Koji build machines and is responsible for polling the Koji Hub for build requests. Once a request is received for the Koji Hub the Koji Builder will initiate a test build of the software package ensuring there are no errors, if errors are detected they are logged for further analysis.

Results + What we’ve accomplished

At the close of the semester we currently have a functional Koji Build system. The Koji Hub is successfully dispatching packages to the Koji builder Daemons and Kojira is creating new repositories for use with the ARM architecture. On the path to success some issues encountered included

- Problems using the PostgreSQL database

- After what appeared to be a successful installation and configuration, Koji builders were listed as not being fully functional, this appeared to be an issue with the Koji Hub but was later determined to be a lack of disk space on the Koji builders.

- Authentication using SSL certificates - Various configuration issues

Summary and set of conclusions

Acknowledgements

Dennis Gilmore Chris Tyler

Links

Logos

  • Fedora
  • Seneca