The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Qixiang Wan 80fa723b1d Include phase name in log for some phases
Phases createiso, liveimages, image_build, ostree_installer and osbs are
done in parallel, logs from these phases are mixed and and it's not
obvious which log message belongs to which phase. This change adds phase
name in log message for these phases.

The new mixin 'PhaseLoggerMixin' is added to extend a Pungi phase with a
logging logger which copy handlers from compose's logger but with
formatter changed.

Fixes: #58
Signed-off-by: Qixiang Wan <qwan@redhat.com>
2016-11-23 16:47:22 +08:00
bin Include phase name in log for some phases 2016-11-23 16:47:22 +08:00
doc Expose lorax's --rootfs-size argument 2016-11-17 10:17:39 -05:00
pungi Include phase name in log for some phases 2016-11-23 16:47:22 +08:00
share variants: Allow multiple explicit optional variants 2016-09-19 12:21:19 +02:00
tests Include phase name in log for some phases 2016-11-23 16:47:22 +08:00
.gitignore Update makefile targets for testing 2016-02-23 13:03:11 +01:00
AUTHORS extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
COPYING Remove FSF address from comments 2016-09-23 10:26:43 +02:00
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 2015-06-25 07:50:03 -04:00
MANIFEST.in Include test data in tarball 2016-11-16 08:53:10 +01:00
Makefile Create git tags without release 2016-09-27 09:01:13 +02:00
README.md Add README 2016-03-08 16:38:40 +01:00
RELEASE-NOTES Rename product_* to release_*. 2015-07-09 06:58:30 -04:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
git-changelog Allow running scripts with any python in PATH 2015-11-27 08:38:47 +01:00
pungi.spec 4.1.11 release 2016-11-15 15:12:02 -06:00
setup.py 4.1.11 release 2016-11-15 15:12:02 -06:00
tox.ini Ignore module imports not at top of file 2016-08-22 10:55:48 +02:00

README.md

Pungi

Pungi is a distribution compose tool.

Composes are release snapshots that contain release deliverables such as:

  • installation trees
    • RPMs
    • repodata
    • comps
  • (bootable) ISOs
  • kickstart trees
    • anaconda images
    • images for PXE boot

Tool overview

Pungi consists of multiple separate executables backed by a common library.

The main entry-point is the pungi-koji script. It loads the compose configuration and kicks off the process. Composing itself is done in phases. Each phase is responsible for generating some artifacts on disk and updating the compose object that is threaded through all the phases.

Pungi itself does not actually do that much. Most of the actual work is delegated to separate executables. Pungi just makes sure that all the commands are invoked in the appropriate order and with correct arguments. It also moves the artifacts to correct locations.