No description
Find a file
Lars Karlitski 17ca73ab14 osbuild-pipeline: validate distro when fetching it
We were verifying two things: if the passed distroArg exists in the
distribution mapping in common/types.go and if the it is an actually
registered distro. Since you cannot have distros registered that don't
correspond to a type, the first test is unnecessary.

Merge the two tests by moving the (much better) error message down into
the second test. This makes DistributionExists redundant, because
Registry.GetDistro() checks this implicitly.

Also, move ListDistributions() to the Registry object, because we want
to show distributions that are actually registered.

Add a test which checks that Registry.List() works and that all included
distributions register correctly.
2020-03-03 16:21:13 +01:00
.github/workflows ci: add golangci-lint 2020-03-02 14:28:55 +01:00
cmd osbuild-pipeline: validate distro when fetching it 2020-03-03 16:21:13 +01:00
distribution distribution: set CACHE_DIRECTORY in the .service file 2020-03-03 14:25:26 +01:00
docs README: Define terminology as a base for internal refactoring 2020-01-30 14:42:25 +01:00
internal osbuild-pipeline: validate distro when fetching it 2020-03-03 16:21:13 +01:00
osbuild@bd6e6bde56 update osbuild submodule 2020-02-24 20:17:50 +01:00
repositories distro: add rhel-8.1 support 2020-02-29 01:17:50 +01:00
test update osbuild submodule 2020-02-24 20:17:50 +01:00
tools tools: add prepare-source.sh 2020-02-17 16:09:17 +01:00
vendor Use semver to enforce blueprint version numbers 2020-02-25 09:00:35 +01:00
.gitignore gitignore: ignore directories used for RPM build 2020-02-24 12:03:25 +01:00
.gitmodules image-info: add test 2019-10-05 14:47:35 +02:00
.golangci.yml ci/lint: disable govet/composites 2020-03-02 14:28:55 +01:00
.packit.yaml add packit 2019-11-29 12:16:27 +01:00
.travis.yml tools: add prepare-source.sh 2020-02-17 16:09:17 +01:00
dnf-json dnf-json: avoid randomizing package order 2020-03-02 17:44:36 +01:00
go.mod Use semver to enforce blueprint version numbers 2020-02-25 09:00:35 +01:00
go.sum Use semver to enforce blueprint version numbers 2020-02-25 09:00:35 +01:00
golang-github-osbuild-composer.spec Add osbuild-weldr-tests to run the weldr integration tests 2020-03-03 12:21:40 +01:00
LICENSE Revert "Fill in the license template" 2019-11-15 15:26:51 +01:00
Makefile Add osbuild-weldr-tests to run the weldr integration tests 2020-03-03 12:21:40 +01:00
README.md Add quick README about testing 2020-02-19 23:41:58 +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

Testing

See test/README.md