Open main menu

CDOT Wiki β

Changes

Fedora Arm Secondary Architecture/Koji Builders

37 bytes added, 09:51, 28 April 2010
Start Kojid
[[Category:Fedora ARM Secondary Architecture]][[Category:Winter 2010 SBR600]]= Goal = To configure a Koji Configuration - Builder =builder system (either VM or physical hardware).
Kojid is the build daemon that runs on each of the build machines. Its primary responsibility is polling for incoming build requests and handling them accordingly. Koji also has support for tasks other than building. Creating install images is one example. kojid is responsible for handling these tasks as well. kojid uses mock for building. It also creates a fresh buildroot for every build. kojid is written in Python and communicates with koji-hub via XML-RPC.
'''= Configuration Files:'''=
* /etc/kojid/kojid.conf - Koji Daemon Configuration
* /etc/sysconfig/kojid - Koji Daemon Switches
= Steps to Perform =
== Storage Space ==
== Install kojid ==
<pre>root@localhost$ yum install koji-builder</pre>
== NFS Configuration ==
/etc/kojid/kojid.conf:
''This needs to point at your koji-hub.''
<pre>
; The URL for the xmlrpc server
server=http://hongkong/kojihub
; The URL for the xmlrpc server server=http://hongkong/kojihub ; the username has to be the same as what you used with add-host ; in this example follow as below user = arm-001-001 ;Matches your VM name ; The URL for the packages tree pkgurl=http://hongkong/yum/arm_built/base/12/arm/</pre> ; ''This item may be changed, but may not be the same as KojiDir on the kojihub.conf file (although it can be something under KojiDir, just not the same as KojiDir)''<pre> ; The directory root for temporary storage workdir=/tmp/koji</pre>
==== SSL Certificates For Authentication ====
Copy the appropriate certificatcertificate(s) from <code>HongKong:/etc/pki/koji/certs/</code>
/etc/kojid/kojid.conf:
''If using SSL, these settings need to be valid.''
<pre>
;client certificate
; This should reference the builder certificate we created above, for
; kojibuilder1.example.com
cert = /etc/kojid/arm-001-008.pem
;client certificate ; This should reference the builder certificate we created above, for ; kojibuilder1.example.com cert = /etc/kojid/arm-001-008.pem ;certificate of the CA that issued the client certificate ca = /etc/kojid/koji_ca_cert.crt ;certificate of the CA that issued the HTTP server certificate serverca = /etc/kojid/koji_ca_cert.crt
;certificate of ==== Start Kojid ===={{Admon/important|Koji Host Entry|Before starting Kojid, make sure that the CA that issued entry for your builder is in the HTTP server certificateserverca = /etc/kojiddatabase. The command to do this (as ''kojiadmin'' on HongKong) is <code>koji add-host ''hostname'' armv5tel</koji_ca_cert.crtcode>}}
</pre>After, start Kojid and configure it to start at each boot:==== Start Kojid ==== service kojid start{{Admon/important|Koji Host Entry|Before starting Kojid, make sure that the entry for your builder is in the database. The command to do this (as ''kojiadmin'' chkconfig kojid on HongKong) is <code>koji add-host ''hostname''</code>}}
After, start Kojid:<pre>root@localhost$ /sbin/service kojid start</pre>== Testing ==
Check <code>/var/log/kojid.log</code> on the builder to verify that kojid has started successfully.
Finally, check the [http://hongkong.proximity.on.ca/koji/hosts Koji hosts web display] on HongKong to see that the host is working properly -- it should be enabled, ready, and checking it.