From Fedora Project Wiki
Line 28: Line 28:


==== Koji-Hub ====
==== Koji-Hub ====
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 是所有 Koji 操作的核心。它是一个运行在 Apache 服务器的 mod_python 模块下的 XML-RPC 服务器。koji-hub 采用被动方式工作,它只接收 XML-RPC 请求,然后依靠编译守护进程以及其他组件来进行交互。Koji-hub 是唯一可以直接访问数据库的组件,也是两个对文件系统具有写权限的组件之一。


==== Kojid ====
==== Kojid ====
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. Essentially kojid asks koji-hub for work. 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.
kojid 是运行在每一台编译机上的编译守护进程。它的主要任务是查询发送过来的编译请求,根据实际情况进行处理。特别地, kojid 查询 koji-hub 上的信息进行工作。除了编译软件包 Koji 还支持其他的任务,例如制作系统安装文件,这些任务也由 kojid 进行处理。kojid 利用 mock 创建原始的编译环境,并且为每一次编译任务单独创建一个编译环境。kojid 是用 Python 编写的,并且通过 XML-RPC 与 koji-hub 进行通信。


=== Koji-Web ===
=== Koji-Web ===
koji-web is a set of scripts that run in mod_python and use the Cheetah templating engine to provide a web interface to Koji. It acts as a client to koji-hub providing a visual interface to preform a limited amount of administration. koji-web exposes a lot of information and also provides a means for certain operations, such as cancelling builds.
koji-web 是一系列运行在 mod_python 模块下,采用 Cheetah 模板引擎生成的脚本文件,可以对 Koji 提供一套 web 页面接口。它作为 koji-hub 的客户端运行,为一些系统管理命令提供了可视化的接口。通过 koji-web,您可以查看 Koji 系统中很多信息。并且koji-web提供了一种方式完成系统中的部分操作,如取消软件包编译任务。


=== Koji Client ===
=== Koji Client ===
koji-client is a CLI written in Python that provides many hooks into Koji. It allows the user to query much of the data as well as perform actions such as adding users and initiating build requests.
koji-client 是用 Python 写成的命令行终端工具,它提供了操作 Koji 系统的很多命令。它允许用户查询系统中的很多信息,还允许用户向 Koji 提交很多操作,比如:添加用户和初始化编译请求。


=== Kojira ===
=== Kojira ===

Revision as of 13:17, 26 March 2012

Koji

Koji 是一个构建 所有与 Fedora 项目有关的软件包 工具。它使用 Mock 来创建chroot环境以便完成构建。如果您想下载 Koji 的源代码,或者是反馈问题、加入邮件列表等等,请见 Koji 项目的首页

使用手册

在 Fedora 中部署 Koji:

Koji 系统架构

术语

在 Koji 系统中,您有必要区分以下三个概念:一般意义上的软件包、软件包的一次构建、软件包一次构建过程中生成的各个 rpm 文件。准确的说,这三个概念可以描述如下:

软件包(Package)
source rpm 的名称。表示一般意义上的软件包,没有指定软件包的具体版本和编译出的子包。比如:kernel、glibc等等。
构建(Build)
特定版本的软件包。表示软件包在一次构建过程中编译出的所有包,包括所有架构的包和编译出的所有包。比如:kernel-2.6.9-34.EL、glibc-2.3.4-2.19。
RPM包(RPM)
一个特定的 rpm 包。一次构建过程中编译出的特定架构和特定名称的包。比如:kernel-2.6.9-34.EL.x86_64、kernel-devel-2.6.9-34.EL.s390、glibc-2.3.4-2.19.i686、glibc-common-2.3.4-2.19.ia64。

Koji 的组件

Koji 由下列组件构成:

Koji-Hub

koji-hub 是所有 Koji 操作的核心。它是一个运行在 Apache 服务器的 mod_python 模块下的 XML-RPC 服务器。koji-hub 采用被动方式工作,它只接收 XML-RPC 请求,然后依靠编译守护进程以及其他组件来进行交互。Koji-hub 是唯一可以直接访问数据库的组件,也是两个对文件系统具有写权限的组件之一。

Kojid

kojid 是运行在每一台编译机上的编译守护进程。它的主要任务是查询发送过来的编译请求,根据实际情况进行处理。特别地, kojid 查询 koji-hub 上的信息进行工作。除了编译软件包 Koji 还支持其他的任务,例如制作系统安装文件,这些任务也由 kojid 进行处理。kojid 利用 mock 创建原始的编译环境,并且为每一次编译任务单独创建一个编译环境。kojid 是用 Python 编写的,并且通过 XML-RPC 与 koji-hub 进行通信。

Koji-Web

koji-web 是一系列运行在 mod_python 模块下,采用 Cheetah 模板引擎生成的脚本文件,可以对 Koji 提供一套 web 页面接口。它作为 koji-hub 的客户端运行,为一些系统管理命令提供了可视化的接口。通过 koji-web,您可以查看 Koji 系统中很多信息。并且koji-web提供了一种方式完成系统中的部分操作,如取消软件包编译任务。

Koji Client

koji-client 是用 Python 写成的命令行终端工具,它提供了操作 Koji 系统的很多命令。它允许用户查询系统中的很多信息,还允许用户向 Koji 提交很多操作,比如:添加用户和初始化编译请求。

Kojira

kojira is a daemon that keeps the build root repodata updated. It is responsible for removing redundant build roots and cleaning up after a build request is completed.

Package Organization

Tags and Targets

Koji organizes packages using tags:

  • Tags are tracked in the database but not on disk
  • Tags support multiple inheritance
  • Each tag has its own list of valid packages (inheritable)
  • Package ownership can be set per-tag (inheritable)
  • Tag inheritance is more configurable
  • When you build you specify a target rather than a tag

A build target specifies where a package should be built and how it should be tagged afterwards. This allows target names to remain fixed as tags change through releases. You can get a full list of build targets with the following command:

$ koji list-targets

You can see just a single target with the --name option:

$ koji list-targets --name dist-fc7

Name                           Buildroot                      Destination
---------------------------------------------------------------------------------------------
dist-fc7                       dist-fc7-build                 dist-fc7

This tells you a build for target dist-fc7 will use a buildroot with packages from the tag dist-fc7-build and tag the resulting packages as dist-fc7.

You can get a list of tags with the following command:

$ koji list-tags

Package lists

As mentioned above, each tag has its own list of packages that may be placed in the tag. To see that list for a tag, use the list-pkgs command:

$ koji list-pkgs --tag dist-fc7

Package                 Tag                     Extra Arches     Owner
----------------------- ----------------------- ---------------- ----------------
ElectricFence           dist-fc6                                 pmachata
GConf2                  dist-fc6                                 rstrode
lucene                  dist-fc6                                 dbhole
lvm2                    dist-fc6                                 lvm-team
ImageMagick             dist-fc6                                 nmurray
m17n-db                 dist-fc6                                 majain
m17n-lib                dist-fc6                                 majain
MAKEDEV                 dist-fc6                                 clumens
[...] 

The first column is the name of the package, the second tells you which tag the package entry has been inherited from, and the third tells you the owner of the package.

查看最近的构建任务

如果您想查看包含某些标签的最近构建任务,请使用 latest-pkg 命令查看:

$ koji latest-pkg --all dist-fc7

Build                                     Tag                   Built by
----------------------------------------  --------------------  ----------------
ConsoleKit-0.1.0-5.fc7                    dist-fc7              davidz
ElectricFence-2.2.2-20.2.2                dist-fc6              jkeating
GConf2-2.16.0-6.fc7                       dist-fc7              mclasen
ImageMagick-6.2.8.0-3.fc6.1               dist-fc6-updates      nmurray
MAKEDEV-3.23-1.2                          dist-fc6              nalin
MySQL-python-1.2.1_p2-2                   dist-fc7              katzj
NetworkManager-0.6.5-0.3.cvs20061025.fc7  dist-fc7              caillon
ORBit2-2.14.6-1.fc7                       dist-fc7              mclasen

The output gives you not only the latest builds, but which tag they have been inherited from and who built them (note: for builds imported from beehive the "built by" field may be misleading).

Documentation

We've tried to make Koji self-documenting wherever possible. The command line tool will print a list of valid commands and each command supports --help. For example:

$ koji help

Koji commands are:
build                Build a package from source
cancel-task          Cancel a task
help                 List available commands
latest-build         Print the latest rpms for a tag
latest-pkg           Print the latest builds for a tag
[...] 
$ koji build --help

usage: koji build [options]  tag URL
(Specify the --help global option for a list of other help options)

options:
-h, --help            show this help message and exit
--skip-tag            Do not attempt to tag package
--scratch             Perform a scratch build
--nowait              Don't wait on build
[...] 

You can see administrator-only command help with --admin. Most users will never use these additional commands, but if you're setting up your own Koji system, you may find them very useful.

$koji help --admin
Available commands:
        add-external-repo         Create an external repo and/or add one to a tag
        add-group                 Add a group to a tag
        add-group-pkg             Add a package to a group's package listing
[...]

不仅如此

Koji 本身可被部署在许多地方,我们欢迎您在 这个页面 添加您的部署经历。