Koji will consume copious amounts of disk space under the primary KojiDir directory (as set in the kojihub.conf file). However, as koji makes use of mock on the backend to actually create build roots and perform the builds in those build roots, it might come to a surprise to users that a running koji server will consume large amounts of disk space under /var/lib/mock and /var/cache/mock as well. Users should either plan the disk and filesystem allocations for this, or plan to modify the default mock build directory in the kojid.conf file. If you change the location, ensure that the new directories are owned by the group "mock" and have 02755 permission.

+

Koji will consume copious amounts of disk space under the primary KojiDir directory (as set in the kojihub.conf file - defaults to /mnt/koji). However, as koji makes use of mock on the backend to actually create build roots and perform the builds in those build roots, it might come to a surprise to users that a running koji server will consume large amounts of disk space under /var/lib/mock and /var/cache/mock as well. Users should either plan the disk and filesystem allocations for this, or plan to modify the default mock build directory in the kojid.conf file. If you change the location, ensure that the new directories are owned by the group "mock" and have 02755 permission.

== Koji Authentication Selection ==

== Koji Authentication Selection ==

Line 39:

Line 38:

The decision on how to authenticate users will affect all other actions you take in setting up koji. For this reason it is a decision best made up front.

The decision on how to authenticate users will affect all other actions you take in setting up koji. For this reason it is a decision best made up front.

−

For Kerberos authentication, a working Kerberos environment (the user is assumed to either already have this or know how to set it up themselves, instructions for it are not included here) and the Kerberos credentials of the initial admin user will be necessary to bootstrap the user database.

+

'''For Kerberos authentication''', a working Kerberos environment (the user is assumed to either already have this or know how to set it up themselves, instructions for it are not included here) and the Kerberos credentials of the initial admin user will be necessary to bootstrap the user database.

−

For SSL authentication, SSL certificates for the xmlrpc server, for the various koji components, and one for the admin user will need to be setup (the user need not know how to create certificate chains already, we include the instructions for this below).

+

'''For SSL authentication''', SSL certificates for the xmlrpc server, for the various koji components, and one for the admin user will need to be setup (the user need not know how to create certificate chains already, we include the instructions for this below).

=== Setting up SSL Certificates for authentication ===

=== Setting up SSL Certificates for authentication ===

Line 70:

Line 69:

default_days = 3650

default_days = 3650

default_crl_days = 30

default_crl_days = 30

−

default_md = md5

+

default_md = sha256

preserve = no

preserve = no

policy = policy_match

policy = policy_match

Line 126:

Line 125:

Although it is not required, it is recommended that you edit the default values in the '''[req_distinguished_name]''' section of the configuration to match the information for your own server. This will allow you to accept most of the default values when generating certificates later. The other sections can be left unedited.

Although it is not required, it is recommended that you edit the default values in the '''[req_distinguished_name]''' section of the configuration to match the information for your own server. This will allow you to accept most of the default values when generating certificates later. The other sections can be left unedited.

When generating certs for a user, the user will need the ${user}.pem, the ${caname}_ca_cert.crt, and the ${user}_browser_cert.p12 files which were generated above. The ${user}.pem file would normally be installed as ~/.fedora.cert, the ${caname}_ca_cert.crt file would be installed as both ~/.fedora-upload-ca.cert and ~/.fedora-server-ca.cert, and the user would import the ${user}_brower_cert.p12 into their web browser as a personal certificate.

When generating certs for a user, the user will need the ${user}.pem, the ${caname}_ca_cert.crt, and the ${user}_browser_cert.p12 files which were generated above. The ${user}.pem file would normally be installed as ~/.fedora.cert, the ${caname}_ca_cert.crt file would be installed as both ~/.fedora-upload-ca.cert and ~/.fedora-server-ca.cert, and the user would import the ${user}_brower_cert.p12 into their web browser as a personal certificate.

−

'''Copy certificates into ~/.koji for kojiadmin'''

'''Copy certificates into ~/.koji for kojiadmin'''

−

You're going to want to be able to send admin commands to the kojihub. In order to do so, you'll need to use the newly created certificates to authenticate with the hub. Create the kojiadmin user then copy the certificates for the koji CA and the kojiadmin user to ~/.koji:

You're going to want to be able to send admin commands to the kojihub. In order to do so, you'll need to use the newly created certificates to authenticate with the hub. Create the kojiadmin user then copy the certificates for the koji CA and the kojiadmin user to ~/.koji:

Line 261:

Line 257:

<pre>

<pre>

root@localhost$ useradd koji

root@localhost$ useradd koji

−

root@localhost$ passwd -d koji

+

root@localhost$ passwd koji

</pre>

</pre>

'''Setup PostgreSQL and populate schema:'''

'''Setup PostgreSQL and populate schema:'''

−

The following commands will create the '''koji''' user within PostgreSQL and will then create the koji database using the schema within the /usr/share/doc/koji*/docs/schema.sql directory

+

The following commands will:

+

* create the koji user within PostgreSQL

+

* create the koji database within PostgreSQL

+

* set a password for the koji user

+

* create the koji schema using the provided /usr/share/doc/koji*/docs/schema.sql file

'''NOTE:''' When issuing the command to import the psql schema into the new database it is important to ensure that the directory path /usr/share/doc/koji*/docs/schema.sql remains intact and is not resolved to a specific version of koji. In test it was discovered that when the path is resolved to a specific version of koji then not all of the tables were created correctly

+

'''NOTE:''' When issuing the command to import the psql schema into the new database it is important to ensure that the directory path /usr/share/doc/koji*/docs/schema.sql remains intact and is not resolved to a specific version of koji. In test it was discovered that when the path is resolved to a specific version of koji then not all of the tables were created correctly.

+

'''NOTE:''' When issuing the command to import the psql schema into the new database it is important to ensure that you are logged in as the koji database owner. This will ensure all objects are owned by the koji database user. Upgrades may be difficult if this was not done correctly.

'''Authorize Koji-web and Koji-hub resources:'''

'''Authorize Koji-web and Koji-hub resources:'''

Line 291:

Line 294:

''Add:''

''Add:''

<pre>

<pre>

−

host koji koji 127.0.0.1/32 trust

+

#TYPE DATABASE USER CIDR-ADDRESS METHOD

−

host koji koji ::1/128 trust

+

host koji koji 127.0.0.1/32 trust

+

host koji koji ::1/128 trust

</pre>

</pre>

It may also be necessary to add an entry for your machine's external IP address:

It may also be necessary to add an entry for your machine's external IP address:

<pre>

<pre>

−

host koji koji $IP_ADDRESS/32 trust

+

host koji koji $IP_ADDRESS/32 trust

−

</post>

+

</pre>

''You can also use UNIX socket access. The DBHost variable must be unset to use this method.''

''You can also use UNIX socket access. The DBHost variable must be unset to use this method.''

Line 304:

Line 308:

local koji apache trust

local koji apache trust

local koji koji trust

local koji koji trust

+

</pre>

+

+

'''NOTE:''' To enforce password based logins to the database, change <tt>trust</tt> to <tt>md5</tt>.

+

<pre>

+

#TYPE DATABASE USER CIDR-ADDRESS METHOD

+

host koji koji 127.0.0.1/32 md5

+

host koji koji ::1/128 md5

+

host koji koji $IP_ADDRESS/32 md5

</pre>

</pre>

'''Make auth changes live:'''

'''Make auth changes live:'''

−

The following commands let postgreSQL know that changes have been made and forces it to reload its configuration so that changes become active

+

You must reload the PostgreSQL configuration for these changes to become active.

<pre>

<pre>

−

root@localhost$ su - postgres

+

root@localhost$ service postgresql reload

−

postgres@localhost$ pg_ctl reload

+

−

postgres@localhost$ exit

+

</pre>

</pre>

'''Bootstrapping the initial koji admin user into the PostgreSQL database:'''

'''Bootstrapping the initial koji admin user into the PostgreSQL database:'''

−

The initial admin user must be manually added to the user database using sql commands. Once they are added and given admin privilege, they may add additional users and change privileges of those users via the koji command line tool's administrative commands. However, if you choose to use the simple user/pass method of authentication, then any password setting/changing must be done manually via sql commands as there is no password manipulation support exposed through the koji tools.

+

The initial admin user must be manually added to the user database using sql commands. Once added and given admin privilege, you may add additional users and change privileges of those users via the koji command line tool's administrative commands.

+

+

However, if you decided to use the simple user/pass method of authentication, then any password setting/changing must be done manually via sql commands as there is no password manipulation support exposed through the koji tools.

The sql commands you need to use vary by authentication mechanism.

The sql commands you need to use vary by authentication mechanism.

−

'''User/Password Authentication:'''

+

'''Set User/Password Authentication:'''

<pre>

<pre>

root@localhost$ su - koji

root@localhost$ su - koji

Line 351:

Line 363:

</pre>

</pre>

−

Note: If you do not know the ID of the admin user, you can get the ID by running the query:

+

'''Note:''' If you do not know the ID of the admin user, you can get the ID by running the query:

<pre>

<pre>

koji=> select * from users;

koji=> select * from users;

Line 358:

Line 370:

You can't actually log in and perform any actions until kojihub is up and running in your web server. In order to get to that point you still need to complete the authentication setup and the kojihub configuration. If you wish to access koji via a web browser, you will also need to get kojiweb up and running.

You can't actually log in and perform any actions until kojihub is up and running in your web server. In order to get to that point you still need to complete the authentication setup and the kojihub configuration. If you wish to access koji via a web browser, you will also need to get kojiweb up and running.

−

'''Miscellaneous permissions'''

+

'''Set Database To Listen On All Addresses'''

−

Edit /var/lib/pgsql/data/postgresql.conf and change listen_addresses to equal '*' and uncomment the line. Then restart postgresql with

+

The koji-hub service will attempt to connect to the database server in the manner you configure. If you use the system hostname, then the database will need to be avalible on that address. To configure this please perform the following:

+

+

* Edit /var/lib/pgsql/data/postgresql.conf

+

* Set <tt>listen_addresses = '*'</tt>

+

* Reload the postgresql service

<pre>

<pre>

service postgresql restart

service postgresql restart

Line 366:

Line 382:

== Koji Hub ==

== Koji Hub ==

−

'''NOTE:''' Koji 1.7 uses mod_wsgi by default, which is not reflected here.

+

'''NOTE:''' Koji 1.7 and greater uses mod_wsgi. Any mod_python configurations will need to be migrated.

−

+

−

Koji-hub is the center of all Koji operations. It is an XML-RPC server running under mod_python in Apache. koji-hub is passive in that it only receives XML-RPC calls and relies upon the build daemons and other components to initiate communication. Koji-hub is the only component that has direct access to the database and is one of the two components that have write access to the file system.

+

+

Koji-hub is the center of all Koji operations. It is an XML-RPC server running under mod_wsgi in Apache. koji-hub is passive in that it only receives XML-RPC calls and relies upon the build daemons and other components to initiate communication. Koji-hub is the only component that has direct access to the database and is one of the two components that have write access to the file system.

'''Configuration Files:'''

'''Configuration Files:'''

+

* /etc/koji-hub/hub.conf

* /etc/httpd/conf/httpd.conf

* /etc/httpd/conf/httpd.conf

* /etc/httpd/conf.d/kojihub.conf

* /etc/httpd/conf.d/kojihub.conf

* /etc/httpd/conf.d/ssl.conf (when using ssl auth)

* /etc/httpd/conf.d/ssl.conf (when using ssl auth)

−

* /etc/koji-hub/hub.conf

−

'''Install koji-hub:'''

'''Install koji-hub:'''

<pre>

<pre>

−

root@localhost$ yum install koji-hub httpd mod_ssl mod_python

+

root@localhost$ yum install koji-hub httpd mod_ssl

</pre>

</pre>

Line 388:

Line 402:

'''/etc/httpd/conf/httpd.conf:'''

'''/etc/httpd/conf/httpd.conf:'''

−

The apache web server has two places that it sets maximum requests a server will handle before the server restarts. The xmlrpc interface in kojihub is a python application, and mod_python can sometimes grow outrageously large when it doesn't reap memory often enough. As a result, it is strongly recommended that you set both instances of MaxRequestsPerChild in httpd.conf to something reasonable in order to prevent the server from becoming overloaded and crashing (at 100 the httpd processes will grow to about 75MB resident set size before respawning).

+

The apache web server has two places that it sets maximum requests a server will handle before the server restarts. The xmlrpc interface in kojihub is a python application, and processes can sometimes grow outrageously large when it doesn't reap memory often enough. As a result, it is strongly recommended that you set both instances of MaxRequestsPerChild in httpd.conf to something reasonable in order to prevent the server from becoming overloaded and crashing (at 100 the httpd processes will grow to about 75MB resident set size before respawning).

<pre>

<pre>

Line 401:

Line 415:

</pre>

</pre>

−

You'll need to make /mnt/koji/packages web-accessible, either here on the hub, or on koji-web, or on another web server altogether. This URL will later go into the builders' pkgurl config option.

+

'''/etc/httpd/conf.d/kojihub.conf:'''

+

+

The koji-hub package provides this configuration file. You will need to modify it based on your authentication type. Instructions are contained within the file and should be simple to follow.

+

+

'''/etc/httpd/conf.d/ssl.conf:'''

+

+

If using SSL you will also need to add the needed SSL options for apache. These options should point to where the certificates are located on the hub.

+

<pre>

<pre>

−

Alias /packages/ /mnt/koji/packages/

+

SSLCertificateFile /etc/pki/koji/certs/kojihub.crt

−

<Directory "/mnt/koji/packages">

+

SSLCertificateKeyFile /etc/pki/koji/certs/kojihub.key

−

Options Indexes

+

SSLCertificateChainFile /etc/pki/koji/koji_ca_cert.crt

−

AllowOverride None

+

SSLCACertificateFile /etc/pki/koji/koji_ca_cert.crt

−

Order allow,deny

+

SSLVerifyClient require

−

Allow from all

+

SSLVerifyDepth 10

−

</Directory>

+

</pre>

</pre>

Line 419:

Line 439:

DBName = koji

DBName = koji

DBUser = koji

DBUser = koji

+

DBPass = mypassword

DBHost = db.example.com

DBHost = db.example.com

KojiDir = /mnt/koji

KojiDir = /mnt/koji

Line 424:

Line 445:

KojiWebURL = http://kojiweb.example.com/koji

KojiWebURL = http://kojiweb.example.com/koji

</pre>

</pre>

+

If kojihub is running on the same server as the koji db, then DBHost should be set to 127.0.0.1

−

==== Optional Configuration ====

+

==== Authentication Configuration ====

−

/etc/koji-hub/hub.conf:

+

'''/etc/koji-hub/hub.conf:'''

−

''If using Kerberos, these settings need to be valid and inline with other services configurations.''

+

+

If using Kerberos, these settings need to be valid and inline with other services configurations.

<pre>

<pre>

AuthPrincipal host/kojihub@EXAMPLE.COM

AuthPrincipal host/kojihub@EXAMPLE.COM

Line 435:

Line 458:

</pre>

</pre>

−

/etc/koji-hub/hub.conf:

+

If using SSL auth, these settings need to be valid and inline with other services configurations for kojiweb to allow logins.

−

''If using SSL auth, these settings need to be valid and inline with other services configurations for kojiweb to allow logins.

+

ProxyDNs should be set to the DN of the kojiweb certificate. The exact format depends on your mod_ssl version. For mod_ssl < 2.3.11 use:

(More details on this format change, including handling of special characters, can be found in the [https://httpd.apache.org/docs/trunk/mod/mod_ssl.html#ssloptions Apache mod_ssl documentation]. See LegacyDNStringFormat there.)

−

If running in Enforcing mode, you will need to allow apache to connect to the postgreSQL server. Even if you are not currently running in Enforcing mode it is still recommended to run the following command to ensure that there are no future issues with SELinux if Enforcing mode is later enabled.

+

−

+

−

<pre>

+

−

root@localhost$ setsebool -P httpd_can_network_connect_db 1

+

−

</pre>

+

==== Koji filesystem skeleton ====

==== Koji filesystem skeleton ====

Line 480:

Line 485:

</pre>

</pre>

+

==== SELinux Configuration ====

+

If running in Enforcing mode:

+

* you will need to allow apache to connect to the postgreSQL server

+

* you will need to allow apache to write some files to disk

+

+

Even if you are not currently running in Enforcing mode, it is still recommended to configure the SELinux settings so that there are no future issues with SELinux if Enforcing mode is enabled later on.

If you've placed /mnt/koji on an NFS share you may also need to set <tt>httpd_use_nfs</tt>.

+

+

==== Check Your Configuration ====

At this point, you can now restart apache and you should have at least minimal operation. The admin user should be able to connect via the command line client, add new users, etc. It's possible at this time to undertake initial administrative steps such as adding users and hosts to the koji database.

At this point, you can now restart apache and you should have at least minimal operation. The admin user should be able to connect via the command line client, add new users, etc. It's possible at this time to undertake initial administrative steps such as adding users and hosts to the koji database.

−

Ensure that your client is configured to work with your server. The system-wide koji client configuration file is ''/etc/koji.conf'', and the user-specific one is in ''~/.koji/config''. You may also use the "-c" option when using the Koji client to specify an alternative configuration file. The following command will test your login to the hub:

+

So we will need a working client to test with.

−

koji call getLoggedInUser

+

== Koji cli - The standard client ==

+

+

The koji cli is the standard client. It can perform most tasks and is essential to the successful use of any koji environment.

+

+

Ensure that your client is configured to work with your server. The system-wide koji client configuration file is ''/etc/koji.conf'', and the user-specific one is in ''~/.koji/config''. You may also use the "-c" option when using the Koji client to specify an alternative configuration file.

If you are using SSL for authentication, you will need to edit the Koji client configuration to tell it which URLs to use for the various Koji components and where their SSL certificates can be found.

If you are using SSL for authentication, you will need to edit the Koji client configuration to tell it which URLs to use for the various Koji components and where their SSL certificates can be found.

+

+

For a simple test, all we need is the ''server'' and authentication sections.

<pre>

<pre>

Line 492:

Line 518:

;url of XMLRPC server

;url of XMLRPC server

−

server = http://hongkong.proximity.on.ca/kojihub

+

server = http://koji-hub.example.com/kojihub

;url of web interface

;url of web interface

−

weburl = http://hongkong.proximity.on.ca/koji

+

weburl = http://koji-web.example.com/koji

;url of package download site

;url of package download site

−

pkgurl = http://hongkong.proximity.on.ca/packages

+

topurl = http://koji-filesystem.example.com/kojifiles

;path to the koji top directory

;path to the koji top directory

topdir = /mnt/koji

topdir = /mnt/koji

−

;configuration for SSL athentication

+

; configuration for Kerberos authentication

−

authtype = ssl

+

+

;the service name of the principal being used by the hub

+

;krbservice = host

+

+

; configuration for SSL athentication

+

;client certificate

;client certificate

cert = ~/.koji/client.crt

cert = ~/.koji/client.crt

Line 515:

Line 546:

</pre>

</pre>

−

It is important to note that the kojira component needs repo privileges, but if you just let the account get auto created the first time you run kojira, it won't have that privilege, so you should pre-create the account and grant it the repo privilege now.

+

The following command will test your login to the hub:

<pre>

<pre>

−

kojiadmin@localhost$ koji add-user kojira

+

root@localhost$ koji moshimoshi

−

kojiadmin@localhost$ koji grant-permission repo kojira

+

−

</pre>

+

−

+

−

For similar technical reasons, you need to add-host each build host prior to starting kojid on that host the first time and could also do that now.

Koji-web is a set of scripts that run in mod_python and use the Cheetah templating engine to provide an web interface to Koji. koji-web exposes a lot of information and also provides a means for certain operations, such as cancelling builds.

+

'''NOTE:''' Koji 1.7 and greater uses mod_wsgi. Any mod_python configurations will need to be migrated.

+

+

Koji-web is a set of scripts that run in mod_wsgi and use the Cheetah templating engine to provide an web interface to Koji. koji-web exposes a lot of information and also provides a means for certain operations, such as cancelling builds.

'''Configuration Files:'''

'''Configuration Files:'''

Line 538:

Line 562:

* /etc/httpd/conf.d/kojiweb.conf

* /etc/httpd/conf.d/kojiweb.conf

* /etc/httpd/conf.d/ssl.conf

* /etc/httpd/conf.d/ssl.conf

+

* /etc/kojiweb/web.conf

'''Install Koji-Web:'''

'''Install Koji-Web:'''

Line 545:

Line 570:

==== Required Configuration ====

==== Required Configuration ====

−

'''/etc/kojiweb/web.conf''': You will need to edit the kojiweb configuration file to tell kojiweb which URLs it should use to access the hub, the koji packages and its own web interface. You will also need to tell kojiweb where it can find the SSL certificates for each of these components. If you are using SSL authentication, the "WebCert" line below must contain both the public ''and'' private key. You will also want to change the last line in the example below to a unique password.

+

'''/etc/httpd/conf.d/kojiweb.conf:'''

−

<pre>

+

−

KojiHubURL = http://hub.example.com/kojihub

+

−

KojiWebURL = http://www.example.com/koji

+

−

KojiPackagesURL = http://server.example.com/mnt/koji/packages

+

+

The koji-web package provides this configuration file. You will need to modify it based on your authentication type. Instructions are contained within the file and should be simple to follow.

−

WebCert = /etc/pki/koji/kojiweb.pem

+

{{admon/tip|RHEL 5's mod_python publisher does not support non-basic auth, so Kerberos authentication does not currently work in EPEL 5's Koji-web. See [https://bugzilla.redhat.com/682319 BZ #682319].}}

−

ClientCA = /etc/pki/koji/koji_ca_cert.crt

+

−

KojiHubCA = /etc/pki/koji/koji_ca_cert.crt

+

−

LoginTimeout = 72

+

'''/etc/httpd/conf.d/ssl.conf:'''

−

Secret = CHANGE_ME

+

+

If you are using SSL you will need to add the needed SSL options for apache.

+

<pre>

+

SSLVerifyClient require

+

SSLVerifyDepth 10

</pre>

</pre>

−

==== Optional Configuration ====

+

'''/etc/kojiweb/web.conf:'''

−

You will also need to edit the '''/etc/httpd/conf.d/kojiweb.conf''' to configure it for the authentication scheme you have selected at the beginning of the setup.

+

You will need to edit the kojiweb configuration file to tell kojiweb which URLs it should use to access the hub, the koji packages and its own web interface. You will also need to tell kojiweb where it can find the SSL certificates for each of these components. If you are using SSL authentication, the "WebCert" line below must contain both the public ''and'' private key. You will also want to change the last line in the example below to a unique password.

+

<pre>

+

[web]

+

SiteName = koji

+

# KojiTheme =

+

# Necessary urls

+

KojiHubURL = https://koji-hub.example.com/kojihub

+

KojiFilesURL = http://koji-filesystem.example.com/kojifiles

−

/etc/httpd/conf.d/kojiweb.conf:

+

## Kerberos authentication options

−

''If using Kerberos, these settings need to be valid and inline with other services configurations.''

+

; WebPrincipal = koji/web@EXAMPLE.COM

−

<pre>

+

; WebKeytab = /etc/httpd.keytab

−

<Location /koji/login>

+

; WebCCache = /var/tmp/kojiweb.ccache

−

AuthType Kerberos

+

−

AuthName "Koji Web UI"

+

−

KrbMethodNegotiate on

+

−

KrbMethodK5Passwd off

+

−

KrbServiceName HTTP

+

−

KrbAuthRealm EXAMPLE.COM

+

−

Krb5Keytab /etc/httpd.keytab

+

−

KrbSaveCredentials off

+

−

Require valid-user

+

−

ErrorDocument 401 /koji-static/errors/unauthorized.html

+

−

</Location>

+

−

</pre>

+

−

{{admon/tip|RHEL 5's mod_python publisher does not support non-basic auth, so Kerberos authentication does not currently work in EPEL 5's Koji-web. See [https://bugzilla.redhat.com/682319 BZ #682319].}}

+

## SSL authentication options

+

; WebCert = /etc/pki/koji/koji-web.pem

+

; ClientCA = /etc/pki/koji/ca_cert.crt

+

; KojiHubCA = /etc/pki/koji/ca_cert.crt

+

+

LoginTimeout = 72

+

+

# This must be set before deployment

+

#Secret = CHANGE_ME

+

+

LibPath = /usr/share/koji-web/lib

−

/etc/httpd/conf.d/kojiweb.conf:

−

''If using SSL, these settings need to be valid and inline with other services configurations. You can uncomment these lines in /etc/httpd/conf.d/kojiweb.conf''

−

<pre>

−

<Location /koji/login>

−

SSLOptions +StdEnvVars

−

</Location>

</pre>

</pre>

−

/etc/httpd/conf.d/ssl.conf:

+

==== Filesystem Configuration ====

−

''If you are using SSL you will need to add the needed SSL options for apache.''

+

+

You'll need to make <tt>/mnt/koji/</tt> web-accessible, either here, on the hub, or on another web server altogether.

+

This URL will go into various clients such as:

+

* /etc/kojiweb/web.conf as KojiFilesURL

+

* /etc/kojid/kojid.conf as topurl

+

* /etc/koji.conf as topurl

<pre>

<pre>

−

SSLVerifyClient require

+

Alias /kojifiles/ /mnt/koji/

−

SSLVerifyDepth 10

+

<Directory "/mnt/koji/">

+

Options Indexes

+

AllowOverride None

+

# Apache < 2.4

+

# Order allow,deny

+

# Allow from all

+

# Apache >= 2.4

+

Require all granted

+

</Directory>

</pre>

</pre>

+

+

Wherever you configure this, please go back and set it correctly in /etc/kojiweb/web.conf now.

==== Web interface now operational ====

==== Web interface now operational ====

Line 605:

Line 643:

== Koji Daemon - Builder ==

== Koji Daemon - Builder ==

−

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 such as creating livecd images or raw disk images, and kojid is responsible for handling these tasks as well. kojid uses mock for creating pristine build environments and creates a fresh one for every build, ensuring that artifacts of build processes cannot contaminate each other. kojid is written in Python and communicates with koji-hub via XML-RPC.

+

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 such as creating livecd images or raw disk images, and kojid is responsible for handling these tasks as well. The kojid service uses mock for creating pristine build environments and creates a fresh one for every build, ensuring that artifacts of build processes cannot contaminate each other. All of kojid is written in Python and communicates with koji-hub via XML-RPC.

'''Configuration Files:'''

'''Configuration Files:'''

Line 619:

Line 657:

==== Required Configuration ====

==== Required Configuration ====

−

/etc/kojid/kojid.conf:

+

'''Add the host entry for the koji builder to the database'''

−

''The configuration file for each koji builder must be edited so that the line below points to the URL for the koji hub. The user tag must also be edited to point to the username used to add the koji builder.''

+

+

You will now need to add the koji builder to the database so that they can be utilized by kojij hub. Make sure you do this before you start kojid for the first time, or you'll need to manually remove entries from the sessions and users table before it can be run successfully.

The first argument used after the ''add-host'' command should the username of the builder. The second argument is used to specify the architecture which the builder uses.

+

+

+

'''/etc/kojid/kojid.conf:'''

+

+

The configuration file for each koji builder must be edited so that the line below points to the URL for the koji hub. The user tag must also be edited to point to the username used to add the koji builder.

<pre>

<pre>

; The URL for the xmlrpc server

; The URL for the xmlrpc server

Line 630:

Line 678:

</pre>

</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)''

+

The koji filesystem may also be needed over http. Set this as it was configured about.

+

<pre>

+

# The URL for the file access

+

topurl=http://koji-filesystem.example.com/kojifiles

+

</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>

<pre>

; The directory root for temporary storage

; The directory root for temporary storage

Line 636:

Line 690:

</pre>

</pre>

−

==== Optional Configuration (SSL certificates) ====

+

The root of the koji build directory (ie, /mnt/koji) must be mounted on the builder. A Read-Only NFS mount is the easiest way to handle this.

+

<pre>

+

# The directory root where work data can be found from the koji hub

+

topdir=/mnt/koji

+

</pre>

+

+

==== Authentication Configuration (SSL certificates) ====

+

+

'''/etc/kojid/kojid.conf:'''

−

/etc/kojid/kojid.conf:

+

If you are using SSL, these settings need to be edited to point to the certificates you generated at the beginning of the setup process.

−

''If you are using SSL, these settings need to be edited to point to the certificates you generated at the beginning of the setup process.''

+

<pre>

<pre>

;client certificate

;client certificate

Line 655:

Line 716:

It is important to note that if your builders are hosted on seperate machines from koji hub and koji web, you will need to scp the certificates mentioned in the above configuration file from the /etc/kojid/ directory on koji hub to the /etc/koji/ directory on the local machine so that the builder can be authenticated.

It is important to note that if your builders are hosted on seperate machines from koji hub and koji web, you will need to scp the certificates mentioned in the above configuration file from the /etc/kojid/ directory on koji hub to the /etc/koji/ directory on the local machine so that the builder can be authenticated.

−

==== Optional Configuration (Kerberos Authentication) ====

+

==== Authentication Configuration (Kerberos) ====

−

/etc/kojid/kojid.conf:

+

'''/etc/kojid/kojid.conf:'''

−

''If using Kerberos, these settings need to be valid and inline with other services configurations.''

+

+

If using Kerberos, these settings need to be valid and inline with other services configurations.

<pre>

<pre>

Line 671:

Line 733:

'''Note:''' Kojid will not attempt kerberos authentication to the koji-hub unless the username field is commented out

'''Note:''' Kojid will not attempt kerberos authentication to the koji-hub unless the username field is commented out

−

==== Add the host entry for the koji builder to the database ====

+

==== Optional Configuration SourceCodeManagement ====

−

You will now need to add the koji builder to the database so that they can be utilized by kojij hub. Make sure you do this before you start kojid for the first time,

+

−

or you'll need to manually remove entries from the sessions and users

+

'''/etc/kojid/kojid.conf:'''

−

table before it can be run successfully.

+

+

The pattern is as follows: hostname:/path/match:checkout /common?, hostname2:/path/match:checkout /common?

The first argument used after the ''add-host'' command should the username of the builder. The second argument is used to specify the architecture which the builder uses.

==== Add the host to the createrepo channel ====

==== Add the host to the createrepo channel ====

Line 690:

Line 762:

==== A note on capacity ====

==== A note on capacity ====

−

The default capacity of a host added to the host database is 2. This means that once the load average on that machine exceeds 2, kojid will not accept any additional tasks. This is separate from the maxjobs item in the configuration file. Before kojid will accept a job, it must pass both the test to ensure the load average is below capacity and that the current number of jobs it is already processing is less than maxjobs. However, in today's modern age of quad core and higher CPUs, a load average of 2 is generally insufficient to fully utilize hardware. As there is not an option to set the capacity of the host via the command line tools, it must be done manually in psql.

+

The default capacity of a host added to the host database is 2. This means that once the load average on that machine exceeds 2, kojid will not accept any additional tasks. This is separate from the maxjobs item in the configuration file. Before kojid will accept a job, it must pass both the test to ensure the load average is below capacity and that the current number of jobs it is already processing is less than maxjobs. However, in today's modern age of quad core and higher CPUs, a load average of 2 is generally insufficient to fully utilize hardware.

<pre>

<pre>

−

koji@localhost$ psql koji

+

koji edit-host --capacity=16 kojibuilder1.example.com

−

koji=# select (id, name, capacity) from host;

+

−

row

+

−

--------------------------------

+

−

(1,kojibuilder1.example.com,2)

+

−

(2,kojibuilder2.example.com,2)

+

−

(2 rows)

+

−

+

−

koji=# update host set capacity = 16 where id = 1;

+

−

UPDATE 1

+

−

koji=#

+

</pre>

</pre>

+

+

The koji-web interface also offers the ability to edit this value to admin accounts.

==== Start Kojid ====

==== Start Kojid ====

−

Once the builder has been added to the database you must start kojira

+

Once the builder has been added to the database you must start kojid

<pre>

<pre>

−

root@localhost$ /sbin/service kojid start

+

root@localhost$ service kojid start

</pre>

</pre>

Check /var/log/kojid.log to verify that kojid has started successfully. If the log does not show any errors then the koji builder should be up and ready. You can check this by pointing your web browser to the web interface and clicking on the hosts tab. This will show you a list of builders in the database and the status of each builder.

Check /var/log/kojid.log to verify that kojid has started successfully. If the log does not show any errors then the koji builder should be up and ready. You can check this by pointing your web browser to the web interface and clicking on the hosts tab. This will show you a list of builders in the database and the status of each builder.

Line 726:

Line 790:

==== Required Configuration ====

==== Required Configuration ====

+

+

'''Add the user entry for the kojira user'''

+

+

The kojira user requires the '''repo''' permission to function.

+

<pre>

+

kojiadmin@localhost$ koji add-user kojira

+

kojiadmin@localhost$ koji grant-permission repo kojira

+

</pre>

/etc/kojira/kojira.conf:

/etc/kojira/kojira.conf:

Line 731:

Line 803:

<pre>

<pre>

; The URL for the xmlrpc server

; The URL for the xmlrpc server

−

server=http://hub.example.com/kojihub

+

server=http://koji-hub.example.com/kojihub

</pre>

</pre>

Line 740:

Line 812:

* There should only be one instance of kojira running at any given time.

* There should only be one instance of kojira running at any given time.

* It is not recommended that kojira run on the builders, as builders only should require read-only access to /mnt/koji.

* It is not recommended that kojira run on the builders, as builders only should require read-only access to /mnt/koji.

+

* Kojira may need to be restarted when new tags are added in order to detect those tags correctly.

−

==== Optional Configuration ====

+

==== Authentication Configuration ====

/etc/kojira/kojira.conf:

/etc/kojira/kojira.conf:

−

''If using SSL, these settings need to be valid.''

+

+

'''If using SSL,''' these settings need to be valid.

<pre>

<pre>

;client certificate

;client certificate

Line 757:

Line 831:

</pre>

</pre>

−

''If using Kerberos, these settings need to be valid.''

+

'''If using Kerberos,''' these settings need to be valid.

<pre>

<pre>

; For Kerberos authentication

; For Kerberos authentication

Line 767:

Line 841:

/etc/sysconfig/kojira:

/etc/sysconfig/kojira:

−

''The local user kojira runs as needs to be able to read and write to /mnt/koji/repos/.

+

+

The local user kojira runs as needs to be able to read and write to /mnt/koji/repos/.

If the volume that directory resides on is root-squashed or otherwise unmodifiable

If the volume that directory resides on is root-squashed or otherwise unmodifiable

−

by root, you can set '''RUNAS=''' to a user that has the required privileges.''

+

by root, you can set '''RUNAS=''' to a user that has the required privileges.

−

+

−

==== Add the user entry for the kojira user ====

+

−

If you did not already do so above, create the kojira user, and grant it the '''repo''' permission.

+

−

<pre>

+

−

kojiadmin@localhost$ koji add-user kojira

+

−

kojiadmin@localhost$ koji grant-permission repo kojira

+

−

</pre>

+

=== Start Kojira ===

=== Start Kojira ===

<pre>

<pre>

−

root@localhost$ /sbin/service kojira start

+

root@localhost$ service kojira start

</pre>

</pre>

Check /var/log/kojira/kojira.log to verify that kojira has started successfully.

Check /var/log/kojira/kojira.log to verify that kojira has started successfully.

Revision as of 23:52, 16 November 2013

The Koji components may live on separate resources as long as all resources are able to communicate. This document will cover how to setup each service individually, however, all services may live on the same resource.

Knowledge Prerequisites

Basic knowledge about creating a database in PostgreSQL and importing a schema

Working with psql

Basic knowledge about Apache configuration

Basic knowledge about yum/createrepo/mock - else you'll not be able to debug problems!

Basic knowledge about using command line

Basic knowledge about RPM building

Simple usage of the Koji client

For an overview of yum, mock, Koji (and all its subcomponents), mash, and how they all work together, see the excellent slides put together by Steve Traylen at CERN [1].

Package Prerequisites

On the server (koji-hub/koji-web)

httpd

mod_ssl

postgresql-server

mod_wsgi

On the builder (koji-builder)

mock

setarch (for some archs you'll require a patched version)

rpm-build

createrepo

A note on filesystem space

Koji will consume copious amounts of disk space under the primary KojiDir directory (as set in the kojihub.conf file - defaults to /mnt/koji). However, as koji makes use of mock on the backend to actually create build roots and perform the builds in those build roots, it might come to a surprise to users that a running koji server will consume large amounts of disk space under /var/lib/mock and /var/cache/mock as well. Users should either plan the disk and filesystem allocations for this, or plan to modify the default mock build directory in the kojid.conf file. If you change the location, ensure that the new directories are owned by the group "mock" and have 02755 permission.

Koji Authentication Selection

Koji primarily supports Kerberos and SSL Certificate authentication. For basic koji command line access, plain user/pass combinations are possible. However, kojiweb does not support plain user/pass authentication and once either Kerberos or SSL Certificate authentication is enabled for kojiweb, the plain user/pass method will stop working entirely. For this reason we encourage skipping the plain user/pass method altogether and properly configuring either Kerberos or SSL Certification authentication from the start.

The decision on how to authenticate users will affect all other actions you take in setting up koji. For this reason it is a decision best made up front.

For Kerberos authentication, a working Kerberos environment (the user is assumed to either already have this or know how to set it up themselves, instructions for it are not included here) and the Kerberos credentials of the initial admin user will be necessary to bootstrap the user database.

For SSL authentication, SSL certificates for the xmlrpc server, for the various koji components, and one for the admin user will need to be setup (the user need not know how to create certificate chains already, we include the instructions for this below).

Setting up SSL Certificates for authentication

Certificate generation

Create the /etc/pki/koji directory and copy-and-paste the ssl.cnf listed here, and save it in the new directory. This configuration file is used along with the openssl command to generate the SSL certificates for the various koji components.

Although it is not required, it is recommended that you edit the default values in the [req_distinguished_name] section of the configuration to match the information for your own server. This will allow you to accept most of the default values when generating certificates later. The other sections can be left unedited.

Generate CA

The CA is the Certificate Authority. It's the key/cert pair used to sign all the other certificate requests. When configuring the various koji components, both the client CA and the server CA will be a copy of the CA generated here. The CA certificate will be placed in the /etc/pki/koji directory and the certificates for the other components will be placed in the /etc/pki/koji/certs directory. The index.txt file which is created is a database of the certificates generated and can be used to view the information for any of the certificates simply by viewing the contents of index.txt.

The last command above will ask you to confirm a number of items about the certificate you are generating. Presumably you already edited the defaults for the country, state/province, locale, and organization in the ssl.cnf file and you only needed to hit enter. It's the organizational unit and the common name that we will be changing in the various certs we create. For the CA itself, these fields don't have a hard requirement. One suggestion for this certificate is to use the FQDN of the server.

If you are trying to automate this process via a configuration management tool, you can create the cert in one command with a line like this:

Each koji component needs its own certificate to identify it. Two of the certificates (kojihub and kojiweb) are used as server side certificates that authenticate the server to the client. For this reason, you want the common name on both of those certs to be the fully qualified domain name of the web server they are running on so that clients don't complain about the common name and the server not being the same. You can set the OU for these two certificates to be kojihub and kojiweb for identification purposes.

For the other certificates (kojira, kojid, the initial admin account, and all user certificates), the cert is used to authenticate the client to the server. The common name for these certs should be set to the login name for that specific component. For example the common name for the kojira cert should be set to kojira so that it matches the username. The reason for this is that the common name of the cert will be matched to the corresponding user name in the koji database. If there is not a username in the database which matches the CN of the cert the client will not be authenticated and access will be denied.

When you later use koji add-host to add a build machine into the koji database, it creates a user account for that host even though the user account doesn't appear in the user list. The user account created must match the common name of the certificate which that component uses to authenticate with the server. When creating the kojiweb certificate, you'll want to remember exactly what values you enter for each field as you'll have to regurgitate those into the /etc/koji-hub/hub.conf file as the ProxyDNs entry.

When you need to create multiple certificates it may be convenient to create a loop or a script like the on listed below and run the script to create the certificates. You can simply adjust the number of kojibuilders and the name of the admin account as you see fit. For much of this guide, the admin account is called "kojiadmin".

When generating certs for a user, the user will need the ${user}.pem, the ${caname}_ca_cert.crt, and the ${user}_browser_cert.p12 files which were generated above. The ${user}.pem file would normally be installed as ~/.fedora.cert, the ${caname}_ca_cert.crt file would be installed as both ~/.fedora-upload-ca.cert and ~/.fedora-server-ca.cert, and the user would import the ${user}_brower_cert.p12 into their web browser as a personal certificate.

Copy certificates into ~/.koji for kojiadmin

You're going to want to be able to send admin commands to the kojihub. In order to do so, you'll need to use the newly created certificates to authenticate with the hub. Create the kojiadmin user then copy the certificates for the koji CA and the kojiadmin user to ~/.koji:

kojiadmin@localhost$ mkdir ~/.koji
kojiadmin@localhost$ cp /etc/pki/koji/kojiadmin.pem ~/.koji/client.crt # NOTE: It is IMPORTANT you use the PEM and NOT the CRT
kojiadmin@localhost$ cp /etc/pki/koji/koji_ca_cert.crt ~/.koji/clientca.crt
kojiadmin@localhost$ cp /etc/pki/koji/koji_ca_cert.crt ~/.koji/serverca.crt

Note: See /etc/koji.conf for the current system wide koji client configuration. Copy /etc/koji.conf to ~/.koji/config if you wish to change the config on a per user basis.

Setting up Kerberos for authentication

The initial configuration of a kerberos service is outside the scope of this document, however there are a few specific things required by koji.

DNS

The koji builders (kojid) use DNS to find the kerberos servers for any given realm.

_kerberos._udp IN SRV 10 100 88 kerberos.EXAMPLE.COM.

The trailing dot denotes DNS root and is needed if FQDN is used.

Principals and Keytabs

It should be noted that in general you will need to use the fully qualified domain name of the hosts when generating the keytabs for services.

You will need the following principals extracted to a keytab for a fully kerberized configuration, the requirement for a host key for the koji-hub is currently hard coded into the koji client.

host/kojihub@EXAMPLE.COM

Used by the koji-hub server when communicating with the koji client

HTTP/kojiweb@EXAMPLE.COM

Used by the koji-web server when performing a negotiated Kerberos authentication with a web browser. This is a service principal for Apache's mod_auth_kerb.

koji/kojiweb@EXAMPLE.COM

Used by the koji-web server during communications with the koji-hub. This is a user principal that will authenticate koji-web to Kerberos as "koji/kojiweb@EXAMPLE.COM". Koji-web will proxy the mod_auth_kerb user information to koji-hub (the ProxyPrincipals koji-hub config option).

koji/kojira@EXAMPLE.COM

Used by the kojira server during communications with the koji-hub

compile/builder1@EXAMPLE.COM

Used on builder1 to communicate with the koji-hub

PostgreSQL Server

Once the authentication scheme has been setup your will need to install and configure a PostgreSQL server and prime the database which will be used to hold the koji users.

Configuration Files:

/var/lib/pgsql/data/pg_hba.conf

/var/lib/pgsql/data/postgresql.conf

Install PostgreSQL:

root@localhost$ yum install postgresql-server

Initialize PostgreSQL DB:

The following commands will initialize PostgreSQL and will start the database service

NOTE: When issuing the command to import the psql schema into the new database it is important to ensure that the directory path /usr/share/doc/koji*/docs/schema.sql remains intact and is not resolved to a specific version of koji. In test it was discovered that when the path is resolved to a specific version of koji then not all of the tables were created correctly.

NOTE: When issuing the command to import the psql schema into the new database it is important to ensure that you are logged in as the koji database owner. This will ensure all objects are owned by the koji database user. Upgrades may be difficult if this was not done correctly.

Authorize Koji-web and Koji-hub resources:In this example, Koji-web and Koji-hub are running on localhost.

/var/lib/pgsql/data/pg_hba.conf:
These settings need to be valid and inline with other services configurations.Please note, the first matching auth line is used so this line must be above any other potential matches.Add:

You must reload the PostgreSQL configuration for these changes to become active.

root@localhost$ service postgresql reload

Bootstrapping the initial koji admin user into the PostgreSQL database:

The initial admin user must be manually added to the user database using sql commands. Once added and given admin privilege, you may add additional users and change privileges of those users via the koji command line tool's administrative commands.

However, if you decided to use the simple user/pass method of authentication, then any password setting/changing must be done manually via sql commands as there is no password manipulation support exposed through the koji tools.

Note: If you do not know the ID of the admin user, you can get the ID by running the query:

koji=> select * from users;

You can't actually log in and perform any actions until kojihub is up and running in your web server. In order to get to that point you still need to complete the authentication setup and the kojihub configuration. If you wish to access koji via a web browser, you will also need to get kojiweb up and running.

Set Database To Listen On All Addresses
The koji-hub service will attempt to connect to the database server in the manner you configure. If you use the system hostname, then the database will need to be avalible on that address. To configure this please perform the following:

Edit /var/lib/pgsql/data/postgresql.conf

Set listen_addresses = '*'

Reload the postgresql service

service postgresql restart

Koji Hub

NOTE: Koji 1.7 and greater uses mod_wsgi. Any mod_python configurations will need to be migrated.

Koji-hub is the center of all Koji operations. It is an XML-RPC server running under mod_wsgi in Apache. koji-hub is passive in that it only receives XML-RPC calls and relies upon the build daemons and other components to initiate communication. Koji-hub is the only component that has direct access to the database and is one of the two components that have write access to the file system.

Configuration Files:

/etc/koji-hub/hub.conf

/etc/httpd/conf/httpd.conf

/etc/httpd/conf.d/kojihub.conf

/etc/httpd/conf.d/ssl.conf (when using ssl auth)

Install koji-hub:

root@localhost$ yum install koji-hub httpd mod_ssl

Required Configuration

/etc/httpd/conf/httpd.conf:

The apache web server has two places that it sets maximum requests a server will handle before the server restarts. The xmlrpc interface in kojihub is a python application, and processes can sometimes grow outrageously large when it doesn't reap memory often enough. As a result, it is strongly recommended that you set both instances of MaxRequestsPerChild in httpd.conf to something reasonable in order to prevent the server from becoming overloaded and crashing (at 100 the httpd processes will grow to about 75MB resident set size before respawning).

This file contains the configuration information for the hub. You will need to edit this configuration to point Koji Hub to the database you are using and to setup Koji Hub to utilize the authentication scheme you selected in the beginning.

If using SSL auth, these settings need to be valid and inline with other services configurations for kojiweb to allow logins.
ProxyDNs should be set to the DN of the kojiweb certificate. The exact format depends on your mod_ssl version. For mod_ssl < 2.3.11 use:

(More details on this format change, including handling of special characters, can be found in the Apache mod_ssl documentation. See LegacyDNStringFormat there.)

Koji filesystem skeleton

Above in the kojihub.conf file we set KojiDir to /mnt/koji. For certain reasons, if you change this, you should make a symlink from /mnt/koji to the new location (note: this is a bug and should be fixed eventually). However, before other parts of koji will operate properly, we need to create a skeleton filesystem structure for koji as well as make the file area owned by apache so that the xmlrpc interface can write to it as needed.

SELinux Configuration

If running in Enforcing mode:

you will need to allow apache to connect to the postgreSQL server

you will need to allow apache to write some files to disk

Even if you are not currently running in Enforcing mode, it is still recommended to configure the SELinux settings so that there are no future issues with SELinux if Enforcing mode is enabled later on.

If you've placed /mnt/koji on an NFS share you may also need to set httpd_use_nfs.

Check Your Configuration

At this point, you can now restart apache and you should have at least minimal operation. The admin user should be able to connect via the command line client, add new users, etc. It's possible at this time to undertake initial administrative steps such as adding users and hosts to the koji database.

So we will need a working client to test with.

Koji cli - The standard client

The koji cli is the standard client. It can perform most tasks and is essential to the successful use of any koji environment.

Ensure that your client is configured to work with your server. The system-wide koji client configuration file is /etc/koji.conf, and the user-specific one is in ~/.koji/config. You may also use the "-c" option when using the Koji client to specify an alternative configuration file.

If you are using SSL for authentication, you will need to edit the Koji client configuration to tell it which URLs to use for the various Koji components and where their SSL certificates can be found.

For a simple test, all we need is the server and authentication sections.

Koji Web - Interface for the Masses

NOTE: Koji 1.7 and greater uses mod_wsgi. Any mod_python configurations will need to be migrated.

Koji-web is a set of scripts that run in mod_wsgi and use the Cheetah templating engine to provide an web interface to Koji. koji-web exposes a lot of information and also provides a means for certain operations, such as cancelling builds.

Configuration Files:

/etc/httpd/conf.d/kojiweb.conf

/etc/httpd/conf.d/ssl.conf

/etc/kojiweb/web.conf

Install Koji-Web:

root@localhost$ yum install koji-web mod_ssl

Required Configuration

/etc/httpd/conf.d/kojiweb.conf:

The koji-web package provides this configuration file. You will need to modify it based on your authentication type. Instructions are contained within the file and should be simple to follow.

RHEL 5's mod_python publisher does not support non-basic auth, so Kerberos authentication does not currently work in EPEL 5's Koji-web. See BZ #682319.

/etc/httpd/conf.d/ssl.conf:

If you are using SSL you will need to add the needed SSL options for apache.

SSLVerifyClient require
SSLVerifyDepth 10

/etc/kojiweb/web.conf:

You will need to edit the kojiweb configuration file to tell kojiweb which URLs it should use to access the hub, the koji packages and its own web interface. You will also need to tell kojiweb where it can find the SSL certificates for each of these components. If you are using SSL authentication, the "WebCert" line below must contain both the public and private key. You will also want to change the last line in the example below to a unique password.

Wherever you configure this, please go back and set it correctly in /etc/kojiweb/web.conf now.

Web interface now operational

At this point you should be able to point your web browser at the kojiweb URL and be presented with the koji interface. Many operations should work in read only mode at this point, and any configured users should be able to log in.

Koji Daemon - Builder

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 such as creating livecd images or raw disk images, and kojid is responsible for handling these tasks as well. The kojid service uses mock for creating pristine build environments and creates a fresh one for every build, ensuring that artifacts of build processes cannot contaminate each other. All of 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

Install kojid:

root@localhost$ yum install koji-builder

Required Configuration

Add the host entry for the koji builder to the database

You will now need to add the koji builder to the database so that they can be utilized by kojij hub. Make sure you do this before you start kojid for the first time, or you'll need to manually remove entries from the sessions and users table before it can be run successfully.

The first argument used after the add-host command should the username of the builder. The second argument is used to specify the architecture which the builder uses.

/etc/kojid/kojid.conf:

The configuration file for each koji builder must be edited so that the line below points to the URL for the koji hub. The user tag must also be edited to point to the username used to add the koji builder.

; The URL for the xmlrpc server
server=http://hub.example.com/kojihub
; the username has to be the same as what you used with add-host
; in this example follow as below
user = kojibuilder1.example.com

The koji filesystem may also be needed over http. Set this as it was configured about.

# The URL for the file access
topurl=http://koji-filesystem.example.com/kojifiles

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)

; The directory root for temporary storage
workdir=/tmp/koji

The root of the koji build directory (ie, /mnt/koji) must be mounted on the builder. A Read-Only NFS mount is the easiest way to handle this.

# The directory root where work data can be found from the koji hub
topdir=/mnt/koji

Authentication Configuration (SSL certificates)

/etc/kojid/kojid.conf:

If you are using SSL, these settings need to be edited to point to the certificates you generated at the beginning of the setup process.

;client certificate
; This should reference the builder certificate we created on the kojihub CA, for kojibuilder1.example.com
; ALSO NOTE: This is the PEM file, NOT the crt
cert = /etc/kojid/kojid.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

It is important to note that if your builders are hosted on seperate machines from koji hub and koji web, you will need to scp the certificates mentioned in the above configuration file from the /etc/kojid/ directory on koji hub to the /etc/koji/ directory on the local machine so that the builder can be authenticated.

Authentication Configuration (Kerberos)

/etc/kojid/kojid.conf:

If using Kerberos, these settings need to be valid and inline with other services configurations.

; the username has to be the same as what you used with add-host
;user =
host_principal_format=compile/%s@EXAMPLE.COM

By default it will look for the Kerberos keytab in /etc/kojid/kojid.keytab

Note: Kojid will not attempt kerberos authentication to the koji-hub unless the username field is commented out

Optional Configuration SourceCodeManagement

/etc/kojid/kojid.conf:

The pattern is as follows: hostname:/path/match:checkout /common?, hostname2:/path/match:checkout /common?

Add the host to the createrepo channel

Channels are a way to control which builders process which tasks. By default
hosts are added to the default channel. At least some build hosts also needs to be added
to the createrepo channel so there will be someone to process repo creation tasks initiated by kojira.

A note on capacity

The default capacity of a host added to the host database is 2. This means that once the load average on that machine exceeds 2, kojid will not accept any additional tasks. This is separate from the maxjobs item in the configuration file. Before kojid will accept a job, it must pass both the test to ensure the load average is below capacity and that the current number of jobs it is already processing is less than maxjobs. However, in today's modern age of quad core and higher CPUs, a load average of 2 is generally insufficient to fully utilize hardware.

koji edit-host --capacity=16 kojibuilder1.example.com

The koji-web interface also offers the ability to edit this value to admin accounts.

Start Kojid

Once the builder has been added to the database you must start kojid

root@localhost$ service kojid start

Check /var/log/kojid.log to verify that kojid has started successfully. If the log does not show any errors then the koji builder should be up and ready. You can check this by pointing your web browser to the web interface and clicking on the hosts tab. This will show you a list of builders in the database and the status of each builder.

; The URL for the xmlrpc server
server=http://koji-hub.example.com/kojihub

Additional Notes:

Kojira needs read-write access to /mnt/koji.

There should only be one instance of kojira running at any given time.

It is not recommended that kojira run on the builders, as builders only should require read-only access to /mnt/koji.

Kojira may need to be restarted when new tags are added in order to detect those tags correctly.

Authentication Configuration

/etc/kojira/kojira.conf:

If using SSL, these settings need to be valid.

;client certificate
; This should reference the kojira certificate we created above
cert = /etc/pki/koji/kojira.pem
;certificate of the CA that issued the client certificate
ca = /etc/pki/koji/koji_ca_cert.crt
;certificate of the CA that issued the HTTP server certificate
serverca = /etc/pki/koji/koji_ca_cert.crt

If using Kerberos, these settings need to be valid.

; For Kerberos authentication
; the principal to connect with
principal=koji/kojira@EXAMPLE.COM
; The location of the keytab for the principal above
keytab=/etc/kojira.keytab

/etc/sysconfig/kojira:

The local user kojira runs as needs to be able to read and write to /mnt/koji/repos/.
If the volume that directory resides on is root-squashed or otherwise unmodifiable
by root, you can set RUNAS= to a user that has the required privileges.

Start Kojira

root@localhost$ service kojira start

Check /var/log/kojira/kojira.log to verify that kojira has started successfully.

Bootstrapping the Koji build environment

For instructions on importing packages and preparing Koji to run builds, see Server Bootstrap .

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.