Koschei is a software for running a service for scratch-rebuilding RPM packages in Koji instance when their build-dependencies change or after some time elapse.
Python code dependencies: - alembic - fedmsg - flask - flask-sqlalchemy - hawkey - jinja2 - koji - librepo - psycopg2 - rpm - sqlalchemy - six
Test dependencies (optional): - nose - mock
Infrastructure: - httpd with mod_wsgi (other WSGI servers should work too, but were not tested) - postgresql (can be external service) - koji hub (can be external service) - fedmsg (optional) - systemd (optional)
Koschei git repository includes a Vagrantfile, which can be used to provision
a VM with the following:
- initialized empty database with rawhide collection
- the source attached at
- everything necessary symlinked to be able to run admin script, backend
services and frontend out-of-the-box
- httpd running with the frontend on port 5000 on your machine
How to use it:
- Install vagrant:
dnf install vagrant-libvirt vagrant-sshfs ansible
- Frontend is already running on port 80, mapped to port 5000 on your local
- The admin script can be run as
koschei-admin (it's symlink to the actual
source file in
- Backend services can be run with
python -m koschei.backend.main
service_name. If you need to run services that need a Koji certificate,
you'll need to scp your certificates into
/etc/koschei in the machine.
- There is a helper script
koschei-ipython that drops you into ipython shell
with koschei backend initialized and database and koji sessions bound to
k, respectively. This can be useful for development since
you don't need to run full service to test a particular function or code
The configuration is formed by merging default configuration values and the
local configuration in
/etc/koschei/. The backend, frontend and admin script
have separate configuration files in
config-admin.cfg, respectively. The cfg files are
regular Python files that expect assignment to
config dictionary variable. The
default configuration file is stored at
contains comments documenting possible configuration options. Keep in mind that
the merging of configurations is recursive, it merges all dictionaries, not
just the top-level ones.
For production deployment install koschei RPM packages. Development snapshots are available at https://copr.fedorainfracloud.org/coprs/msimacek/koschei/
Koschei is split into multiple components that can function independently - backend, frontend and admin. Each are installed as separate RPM, configured separately and can be deployed on different machines.
Setting up the database:
- Install PostgreSQL server with
dnf install postgresql-server. Other
database servers are not supported and won't work.
postgresql-setup initdb to initialize the database
- Enable the service with
systemctl enable postgresql-server
and start it with
systemctl start postgresq-server
- Create the database with
- If your database is on separate host or you didn't follow the steps here
exactly, you'll need to configure the database connection in respective
configuration files of backend, frontend and admin (see configuration section).
- Populate DB schema with
- Create at least one package collection using
(see its help for parameters)
Koschei administration script
koschei-admin is shipped in koschei-admin RPM
package and can be installed independently from other services. It is used to
perform various administration tasks such as adding packages or creating
collections. See its help (
-h option) for list of commands and help of
individual commands (such as
koschei-admin create-collection -h).
Koschei backend consists of multiple systemd services that can be started
For fully working instance you'll want to start all of them, for passive
instance that doesn't submit builds, you'll want to skip koschei-scheduler.
For submiting builds, you need to install a koji certificate at
/home/koschei/.fedora.cert (and also the CA and server CA certificates). The
cert files have the same layout as when generated using fedora-cert and using
fedpkg or koji client. If you want to use different locations, you can specify
them in the
The web frontend is a WSGi application, which can be run within Apache Server.
koschei-frontend RPM package ships httpd configuration file that should work
out-of-the-box as you start httpd. You should override the
application secret used for authentication in
After a koschei package update to a newer version, you need to manually stop
the services (including httpd) and execute DB migrations. Migrations are
alembic -c /usr/share/koschei/alembic.ini upgrade head on the
koschei-admin is installed (it's using
/etc/koschei/config-admin.cfg configuration). Then the services can be started
Koschei is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version.
Koschei is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
A copy of the GNU General Public License is contained in the LICENSE.txt file.