1
edit
Changes
→Components Required By Koji
= Project Name =
Koji Hub Installation and ConfigurationBuild System for Fedora ARM
= Name =
= The Koji Build System =
= Koji Components =
Apache Web Server - The most popular web server on the internet Apache is responsible for serving the pages provided by the Koji Web scripts. Apache is configured to use a variety of modules including SSL and mod_python. The SSL modules facilitates authentication of users and the different components of the Koji Build System.
PostgreSQL - PostgreSQL is the back-end database used by the Koji Build System. It stores tables of information including users, packages and build categories.
Mock - mock is a tool that creates a protected and minimal Linux file system that is used to test build software packages. = Results Problems Encountered =At * Initially the close of Virtual Machines had no network connectivity, network settings and devices had to be added manually before becoming functional. * Problems using the semester we currently have PostgreSQL database - installation for use with Koji required a functional Koji Build systemstandard installation. The After the first attempt PostgreSQL was reinstalled successfully and Koji Hub is was successfully dispatching packages able to the Koji builder Daemons and Kojira is creating new repositories for use interact with the ARM architecturedatabase. On the path to success some issues encountered included
* 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. Disk space was reallocated and distributed amongst the ARM VM's.
* Various configuration issues - After what appeared to be a successful installation and throughout the process the different configuration, Koji builders files that required editing were listed as not being fully functionalmis-configured, this appeared or needed to be an issue edited multiple times to work correctly with the Koji Hub but was later determined to be a lack of disk space on the Koji buildersconfiguration.
* The creation of repositories by Kojira was failing after 2919/12788 software packages (RPMS), additional memory was added to the Virtual ARM Machines an the repository creation continued. * Lack of documentation - Authentication using SSL certificatesbecause this is the second Koji Build System for the ARM architecture, there are limited resources. Within weeks of starting work and blogging on Koji, our blogs became the top results when searching the internet.- Various configuration issues* Understanding the relationship of package creation and Koji's method of organizing software packages in the database. This is still a learning process as Koji has just become fully functional.
= Summary Results =Currently we 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. Eight VM's and the Open-RD Client are online and set of conclusions =are listed as Ready and Enabled using the Koji command line tool and the web interface through Koji Web. Koji Web can be used to monitor all Koji operations and provide real time log information that can be used to troubleshoot problems as they arise.
= Acknowledgements =
*Dennis Gilmore *Chris Tyler
= Links =
*Fedora Project - http://fedoraproject.org/wiki/Koji/ServerHowTo* Paul Whalen's SBR600 Blog - http://paulfedora.wordpress.com/* Software Build and Release 600 wiki - http://zenit.senecac.on.ca/wiki/index.php/SBR600 * Fedora Arm Secondary Architecture wiki - http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architecture
= Logos =
* Fedora
* Seneca
* Apache
* PostgreSQL
= Images =
* Open-RD Client Board - http://www.einfochips.com/marvell/images/OpenRD-Client-Zoom.png
* RPM Package Logo - http://www.linux-support.com/cms/images/stories/illutrations/rpm-package.png