The utility for building of AlmaLinux distributions (repos, ISO images).
0483f914c4
I did a time map of a Fedora compose today, and noticed that we spend about an hour waiting for the ostree_install phase to complete before we start up the compose_images_phase which does all the other image builds. This is unnecessary. Nothing else depends on ostree_install; it should be fine to start up the extra_phase (which contains compose_images_phase) while the ostree stuff is still running. This implements that by splitting the ostree phases out of the essentials_phase which contains the real precursors to the extra_phase. We start the essentials and ostree phases together, but only wait for the essentials phase to complete before kicking off extra_phase, so it can start while the ostree phase is still running. One tweak we have to make to accommodate this is to move image_checksum_phase out of extra_phase, to avoid it potentially running before all ostree installer images are built. The checksum phase is quite fast - it takes about five minutes - and any time benefit of running it in parallel with the osbs and repoclosure phases seems like it must be smaller than the time loss of waiting for ostree_install before kicking off extra. Merges: https://pagure.io/pungi/pull-request/1790 Signed-off-by: Adam Williamson <awilliam@redhat.com> (cherry picked from commit 18bda22fcb842c00a606e5f357aeb9f3d02aa626) |
||
|---|---|---|
| contrib | ||
| doc | ||
| pungi | ||
| pungi_utils | ||
| share | ||
| tests | ||
| .gitignore | ||
| 1860.patch | ||
| AUTHORS | ||
| COPYING | ||
| git-changelog | ||
| GPL | ||
| Makefile | ||
| MANIFEST.in | ||
| pungi.spec | ||
| README.md | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| sources | ||
| test-requirements.txt | ||
| TODO | ||
| tox.ini | ||
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.
Links
- Documentation: https://docs.pagure.org/pungi/
- Upstream GIT: https://pagure.io/pungi/
- Issue tracker: https://pagure.io/pungi/issues
- Questions can be asked in the #fedora-releng IRC channel on irc.libera.chat
or in the matrix room
#releng:fedoraproject.org