No description
Find a file
Tom Gundersen 6d94028976 weldr: include build and base packages in final depsolve
The packag selection shown in the UI does not include the base
packages that will be included in the image, and they cannot,
because the base packages depends on the output type, and the UI
packages shown in the UI are independent of the output type.

It is possible to select packages incompatible with the base
packages. Discover this sooner rather than later, by including
the base packages in the final depsolve before creating the
pipeline.

In the future the result of the depsolve will be used to create
the pipeline, so this is another prerequisite for moving from
the dnf to the rpm stage.

Also depsolve the build packages for the same reason. Note that we
always set clean to false in this case, as the depsolving of the
main packages would have performed any cleaning necessary.

Also extend dnf-json to support excluding packages from depsolving.

Signed-off-by: Tom Gundersen <teg@jklm.no>
2020-02-14 14:43:27 +01:00
cmd dnf-json: make independent from the host 2020-02-14 14:43:27 +01:00
distribution service: adjust the IO and CPU scheduling classes 2019-12-13 20:13:15 +01:00
docs README: Define terminology as a base for internal refactoring 2020-01-30 14:42:25 +01:00
internal weldr: include build and base packages in final depsolve 2020-02-14 14:43:27 +01:00
osbuild@e0bb65dd71 submodule: bump to current osbuild master 2019-12-15 20:57:40 +01:00
repositories repositories: install the base repositories in the filesystem 2020-01-03 22:35:52 +01:00
test distro: add custom image size 2020-01-23 00:57:31 +01:00
tools image-info: mount ESP at /boot/efi if found 2019-12-09 18:08:52 +01:00
.gitignore add makefile targets for rpm build 2019-12-02 13:45:07 +01:00
.gitmodules image-info: add test 2019-10-05 14:47:35 +02:00
.packit.yaml add packit 2019-11-29 12:16:27 +01:00
.travis.yml travis: disable PPC tests 2019-12-11 15:23:24 +01:00
dnf-json dnf-json: make independent from the host 2020-02-14 14:43:27 +01:00
go.mod weldr: add support for toml blueprints 2019-12-03 01:27:00 +01:00
go.sum weldr: add support for toml blueprints 2019-12-03 01:27:00 +01:00
golang-github-osbuild-composer.spec tests: add basic integration tests 2020-01-03 22:35:52 +01:00
LICENSE Revert "Fill in the license template" 2019-11-15 15:26:51 +01:00
Makefile repositories: install the base repositories in the filesystem 2020-01-03 22:35:52 +01:00
README.md README: Define terminology as a base for internal refactoring 2020-01-30 14:42:25 +01:00

osbuild-composer

An HTTP service for building bootable OS images. It provides the same API as lorax-composer but in the background it uses osbuild to create the images.

You can control it in Cockpit or using the composer-cli. To get started on Fedora, run:

# dnf install cockpit-composer golang-github-osbuild-composer composer-cli
# systemctl enable --now cockpit.socket
# systemctl enable --now osbuild-composer.socket

Now you can access the service using composer-cli, for example:

composer-cli status show

or using a browser: http://localhost:9090

API documentation

Please refer to the lorax-composer's documenation as osbuild-composer is a drop-in replacement.

High-level overview

overview

Frontends

osbuild-composer is meant to be used with 2 different front-ends. The primary one, which is meant for general use, is cockpit-composer. It is part of the Cockpit project and unless you have a strong reason not to use it, you should use it. composer-cli is a command line tool that can be used with osbuild-composer.

Compose

  • Compose is what the user submits over one of the frontends
  • It contains of one or more image builds
  • It contains zero or more upload actions

Image build

Job

  • What composer submits to a worker
  • Is a unit of work performed by osbuild (internally it is a single execution of osbuild)
  • Consists of one image build and zero or more Upload actions

Image type

  • In the cockpit-composer, for examples these are image types:
    • Openstack
    • Azure
    • AWS
  • As of now, we name them internally by their file format: vhd, ami, etc.
  • You can see a list of types by executing: composer-cli compose types

Upload action

  • Each image can be, but does not have to be, uploaded to a remote location
  • One image can be uploaded to multiple locations