Switch to simple upstream releases
This commit changes our release process from the model of having a release commit (and pull request) which also updated the NEWS.md file and bumped the versions in the osbuild.spec and setup.py files to simply pushing a tag. After the tag (containing the release notes) is pushed, a GitHub composite action is triggered that creates a GitHub release with the contents of the git release tag. Furthermore the bumping of the version number now always has to happen directly after a release to avoid having to push a(n untested) commit to main for the release and this is also handled by the GitHub composite action. Finally packit pushes directly to dist-git now on pushing the release tag, so no pull-request needs to be reviewed and merged anymore. Consequently, we also drop the docs/news folder and its content and adjust the PR template.
This commit is contained in:
Simon Steinbeiss
Simon Steinbeiß
parent
93e54cd872
commit
dcb5220329
60 changed files with 16 additions and 1766 deletions
|
|
@ -1,9 +0,0 @@
|
|||
# Koji API: New endpoint for getting the manifests of a compose job
|
||||
|
||||
A new endpoint is available in the Koji API: `GET /compose/{ID}/manifests`.
|
||||
Returns the manifests for a running or finished compose. Returns one manifest
|
||||
for each image in the request, in the order they were defined.
|
||||
|
||||
Relevant PRs:
|
||||
https://github.com/osbuild/osbuild-composer/pull/1155
|
||||
https://github.com/osbuild/osbuild-composer/pull/1165
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
# RHEL 8.4: Update rhel-84 distro to better match imagefactory's qcow2
|
||||
|
||||
There are minor discrepancies between our nightly image and the imagefactory's
|
||||
qcow2. These differences are mainly in the installed packages, enabled services,
|
||||
and disabled services. To remedy these differences the following changes have
|
||||
been made:
|
||||
|
||||
The following packages have been added to our qcow2 image: oddjob,
|
||||
oddjob-mkhomedir, psmisc, authselect-compat, dbxtool.
|
||||
|
||||
The following packages have been removed from our qcow2 image:
|
||||
dnf-plugin-spacewalk, fwupd, nss, and udisks2.
|
||||
|
||||
The following services have been enabled: nfs-convert.service.
|
||||
|
||||
The following services have been removed/disabled: mdmonitor.service,
|
||||
udisks2.service, fwupd-refresh.timer, mdcheck_continue.timer,
|
||||
mdcheck_start.timer, and mdmonitor-oneshot.timer.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
# RHEL 8.4: Include timedatex in qcow2 images
|
||||
|
||||
Timedatex was an excluded package due to an selinux-policy issue that has been
|
||||
fixed. Therefore, timedatex should be in the qcow2 image we build. Our list of
|
||||
excluded packages for RHEL 8.4 was not being included in our nightly builds so
|
||||
we did not realize that timedatex was still being excluded. The issue with the
|
||||
excluded packages is now fixed and timedatex is now removed from this list.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
# Add support for CentOS Stream 8
|
||||
|
||||
OSBuild Composer can now build CentOS Stream 8 images. The image definitions
|
||||
are exactly the same as for the latest supported RHEL 8.y release (8.4
|
||||
currently ).
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
# Cloud API: The compose endopint now allow additional package selection
|
||||
|
||||
The `POST /compose` endpoint has now been extended to allow packages to
|
||||
be requested in addition to the base ones for the image type. Packages
|
||||
can only be requested by name, and the most recent ones that satisfy
|
||||
dependency solving will be chosen.
|
||||
|
||||
Relevant PR:
|
||||
https://github.com/osbuild/osbuild-composer/pull/1208
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Blueprint: Kernel name customization
|
||||
|
||||
When creating ostree commits, only one kernel package can be installed at a
|
||||
time, otherwise creating the commit will fail in rpm-ostree. This prevents
|
||||
ostree type builds (RHEL for Edge and Fedora IoT) to add alternative kernels,
|
||||
in particular, the real-time kernel (`kernel-rt`).
|
||||
|
||||
Blueprints now support defining the name of the kernel to be used in an image,
|
||||
through the `customizations.kernel.name` key. If not specified, the default
|
||||
`kernel` package is included as before.
|
||||
|
||||
Relevant PRs:
|
||||
https://github.com/osbuild/osbuild-composer/pull/1175
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
# CloudAPI now supports /openapi.json and /version endpoints
|
||||
|
||||
These endpoints are useful for deployment in the cloud.redhat.com platform.
|
||||
The platform will use data from the /openapi.json endpoint to automatically
|
||||
generate documentation for the REST API. A user can see the documentation
|
||||
in the cloud.redhat.com web console.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
# OSBuild: spec: update to osbuild version 24
|
||||
|
||||
In order to add the newly supported sysconfig stage, the osbuild dependency
|
||||
needs to be updated to version 24. This update is reflected in both the spec
|
||||
file dependency and in the testing dependency.
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Add support for `org.osbuild.rhsm` osbuild stage
|
||||
|
||||
Add support for `org.osbuild.rhsm` osbuild stage. This stage is available in
|
||||
osbuild since version 24. The stage currently allows only configuring the
|
||||
enablement status of two RHSM DNF plugins, specifically of `product-id` and
|
||||
`subscription-manager` DNF plugins.
|
||||
|
||||
# RHEL 8.3 & 8.4: Disable all RHSM DNF plugins on qcow2 image
|
||||
|
||||
Disable both available RHSM DNF plugins (`product-id` and
|
||||
`subscription-manager`) on rhel-8 and rhel-84 qcow2 images. The reason for
|
||||
disabling these DNF plugins is to make the produced images consistent in this
|
||||
regard, with what had been previously produced by the imagefactory.
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
# OSTree compose types with kernel boot parameters return error
|
||||
|
||||
Previously, specifying Kernel boot parameters in a Blueprint via the
|
||||
`[customizations.kernel]` section and requesting an OSTree image type
|
||||
(`rhel-edge-commit` or `fedora-iot-commit`) would produce an image but the boot
|
||||
parameters would be ignored.
|
||||
|
||||
This combination now returns an error message that the configuration is not
|
||||
supported.
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# RHEL 8.4: add support for org.osbuild.sysconfig stage
|
||||
|
||||
The kernel and network sysconfigs need to have certain values set in RHEL 8.4.
|
||||
Currently, the following values are set for all image types in 8.4:
|
||||
|
||||
kernel:
|
||||
UPDATEDEFAULT=yes
|
||||
DEFAULTKERNEL=kernel
|
||||
|
||||
network:
|
||||
NETWORKING=yes
|
||||
NOZEROCONF=yes
|
||||
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Weldr API: New VMWare upload target
|
||||
|
||||
New upload target is available that allows users to push built VMWare images directly to vSphere without the need to download and push them manually.
|
||||
|
||||
Upload target requires following options:
|
||||
`Username`,
|
||||
`Password`,
|
||||
`Host`,
|
||||
`Datacenter`,
|
||||
`Datastore`,
|
||||
`Cluster`.
|
||||
|
||||
Relevant PR: https://github.com/osbuild/osbuild-composer/pull/1169
|
||||
|
|
@ -1,40 +0,0 @@
|
|||
# Weldr API: Allow parent OSTree commit to be read from repository
|
||||
|
||||
The weldr API for building OSTree based images is extended to optionally take an `url` parameter instead of the current `parent`.
|
||||
|
||||
The `parent` parameter contains the OSTree commit SHA of the parent commit when building an update commit. Obtaining this is cumbersome, so instead the `url` of the repository containing the desired parent commit can be specified. In this case, composer will take the current `HEAD` of the given `ref` as the parent.
|
||||
|
||||
At most one of `parent` and `url` can be specified in a given compose request.
|
||||
|
||||
Before:
|
||||
|
||||
curl --silent \
|
||||
--header "Content-Type: application/json" \
|
||||
--unix-socket /run/weldr/api.socket \
|
||||
http://localhost/api/v1/compose \
|
||||
--data "{ \
|
||||
\"blueprint_name\": \"foo\", \
|
||||
\"compose_type\": \"rhel-edge-commit\", \
|
||||
\"ostree\": {\ \
|
||||
\"parent\": \"b8a69e5c79be5830bb272356809a52b1660d2013c26f6973d549d0a312a8d21a\", \
|
||||
\"ref\": \"fedora/stable/x86_64/iot\" \
|
||||
} \
|
||||
}"
|
||||
|
||||
After:
|
||||
|
||||
curl --silent \
|
||||
--header "Content-Type: application/json" \
|
||||
--unix-socket /run/weldr/api.socket \
|
||||
http://localhost/api/v1/compose \
|
||||
--data "{ \
|
||||
\"blueprint_name\": \"foo\", \
|
||||
\"compose_type\": \"rhel-edge-commit\", \
|
||||
\"ostree\": {\ \
|
||||
\"url\": \"https://d2ju0wfl996cmc.cloudfront.net/\", \
|
||||
\"ref\": \"fedora/stable/x86_64/iot\" \
|
||||
} \
|
||||
}"
|
||||
|
||||
Relevant PRs:
|
||||
https://github.com/osbuild/osbuild-composer/pull/1235
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
# Cloud API: Add support for Google Cloud Platform target
|
||||
|
||||
Added support in Cloud API to upload images to Google Cloud Platform (GCP) and
|
||||
share them with specified accounts. There is currently no GCP-specific image
|
||||
type, since GCP supports importing VHD and VMDK image types already supported by
|
||||
the `osbuild-composer`.
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
# Cloud API: include upload target-specific options in `UploadStatus`
|
||||
|
||||
The `UploadStatus` now includes additional information in its `options` property.
|
||||
The information is specific to the chosen target Cloud provider and it is necessary
|
||||
to successfully identify the built and shared OS image by the end user. Currently
|
||||
this information is returned for both supported targets, **AWS** and **GCP**.
|
||||
|
||||
Information included for **AWS** target:
|
||||
|
||||
- AMI
|
||||
- Region
|
||||
|
||||
Information included for **GCP** target:
|
||||
|
||||
- Image name
|
||||
- Image's source Project ID
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
# RHEL8.4: Fix grub2 kernel selection
|
||||
|
||||
By marking the kernel we install as the `saved_entry`, we make sure that installing additional/subsequent kernels do not unintentionally change the default kernel to be booted into.
|
||||
|
||||
Relevant PR: https://github.com/osbuild/osbuild-composer/pull/1241
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
# Cloud API: Add support for uploading to Azure
|
||||
|
||||
Cloud API now has support for uploading images directly to Azure. Before,
|
||||
composer only supported uploading to Azure using the Weldr API (used by
|
||||
cockpit-composer and composer-cli). Also, it only created a storage
|
||||
blob requiring the user to do one extra step to run a VM.
|
||||
|
||||
The new Azure Image upload target creates a finished Azure Image that can
|
||||
be immediately used to launch a VM. It also uses the Azure OAuth-based
|
||||
authentication that doesn't require the user to give composer any credentials.
|
||||
|
||||
Note that this is currently only available for the Cloud API. If you are
|
||||
a user of the Weldr API, you can still use the older method.
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
# Cloud API: fix `image_status.status` value for running compose
|
||||
|
||||
Previously, the Cloud API endpoint `/v1/compose/{id}` return value's
|
||||
`image_status.status` for a running worker job was "running", which didn't
|
||||
comply with the Cloud API specification. Equivalents allowed by the API
|
||||
specification are "building", "uploading" or "registering".
|
||||
|
||||
Return "building" as the `image_status.status` value for a running compose,
|
||||
instead of "running". Returning the remaining "uploading" and "registering"
|
||||
values is not yet implemented.
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
# Support new OSBuild pipelines and new RHEL for Edge image types
|
||||
|
||||
OSBuild Composer can now generate Manifests that conform to the new OSBuild
|
||||
schema. Two new image types are added that take advantage of the new schema:
|
||||
|
||||
- `rhel-edge-container`: Creates an OCI container with an embedded
|
||||
`rhel-edge-commit`. Running the container starts a web server that serves
|
||||
the commit.
|
||||
|
||||
- `rhel-edge-installer`: Creates a boot ISO image that embeds a
|
||||
`rhel-edge-commit`. The commit is pulled from a URL during the compose of
|
||||
the boot ISO.
|
||||
|
||||
Requesting a `rhel-edge-installer` requires specifying a URL, otherwise the
|
||||
request will fail. Blueprint customizations have no effect on the boot ISO and
|
||||
also cause the request to fail if any are specified.
|
||||
|
||||
Relevant PR: https://github.com/osbuild/osbuild-composer/pull/1244
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
# Improve OSTree Repository URL and Ref parsing
|
||||
|
||||
If the OSTree Repository URL did not end in a `/` the parsing would fail with a less-than-useful error message. This has been fixed. Error messages for different failure cases have also been improved.
|
||||
|
|
@ -1,82 +0,0 @@
|
|||
# Allow image type-specific repositories using Image Type Tags
|
||||
|
||||
The schema of the repository definitions used by *Weldr API*, located in `/usr/share/osbuild-composer/repositories/` or `/etc/osbuild-composer/repositories` is extended with a new field called **`image_type_tags`** and is expected to be an array of strings representing specific image types.
|
||||
|
||||
The behavior of how are defined repositories processed and used by osbuild-composer* is extended in the following way:
|
||||
|
||||
1. If the repository definition does not have the `image_type_tags` field specified, then it will be used for building all types of images for a given distribution and architecture. This is how all repository definitions had been used before this change.
|
||||
|
||||
1. If the repository definition has the `image_type_tags` field specified and set to a non-empty array of strings, then it will be used **only** for building image types, which names are specified in the array.
|
||||
|
||||
An example of a user-defined repository override for Fedora 33 in `/etc/osbuild-composer/repositories/fedora-33.json` follows. In addition to Fedora distribution repositories, it defines an additional repository called `my-custom-repo`, which should be used only for `ami` images built on both architectures.
|
||||
|
||||
```json
|
||||
{
|
||||
"x86_64": [
|
||||
{
|
||||
"name": "fedora",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=fedora-33&arch=x86_64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
},
|
||||
{
|
||||
"name": "updates",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=updates-released-f33&arch=x86_64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
},
|
||||
{
|
||||
"name": "fedora-modular",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=x86_64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
},
|
||||
{
|
||||
"name": "updates-modular",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f33&arch=x86_64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
},
|
||||
{
|
||||
"name": "my-repo",
|
||||
"metalink": "https://repos.example.org/f33/x86_64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true,
|
||||
"image_type_tags": ["ami"]
|
||||
}
|
||||
],
|
||||
"aarch64": [
|
||||
{
|
||||
"name": "fedora",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=fedora-33&arch=aarch64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
},
|
||||
{
|
||||
"name": "updates",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=updates-released-f33&arch=aarch64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
},
|
||||
{
|
||||
"name": "fedora-modular",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-33&arch=aarch64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
},
|
||||
{
|
||||
"name": "updates-modular",
|
||||
"metalink": "https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f33&arch=aarch64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true
|
||||
}
|
||||
{
|
||||
"name": "my-repo",
|
||||
"metalink": "https://repos.example.org/f33/aarch64",
|
||||
"gpgkey": "...",
|
||||
"check_gpg": true,
|
||||
"image_type_tags": ["ami"]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
# RHEL 8.4: Update rhel-84 distro to better match RHEL 8.3
|
||||
|
||||
This restores net-tools to the default package set.
|
||||
|
||||
In RHEL8.3 cloud-init depended on net-tools, but in RHEL8.4,
|
||||
the dependency was dropped. We still want net-tools in the
|
||||
default package set, so add the dependency explicitly.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
# RHEL 8.4: qcow2 images can now be used by older QEMUs
|
||||
|
||||
Previously, the guest image for RHEL 8.4 was only usable by QEMU 1.1 and
|
||||
newer. However, this image should be usable on RHEL 6 that ships an older
|
||||
version of QEMU. This is now fixed and the guest image can be now used by
|
||||
QEMU 0.10 and newer.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
# Add support for RHEL 9
|
||||
|
||||
OSBuild Composer can now build RHEL 9.0 images.
|
||||
Support is currently limited to qcow2 image type.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
# Worker: Set image name as custom metadata on the file uploaded to GCP Storage
|
||||
|
||||
Worker osbuild jobs with GCP upload target now set the chosen image name as
|
||||
custom metadata on the uploaded object. This makes finding the uploaded
|
||||
object using the image name possible. The behavior is useful mainly
|
||||
for cleaning up cloud resources in case of unexpected failures.
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
# Retrieve metadata about a compose through the Cloud API
|
||||
|
||||
A new endpoint is available in the Cloud API at `compose/id/metadata`. This
|
||||
endpoint returns a full package list (NEVRA) for the image that was built and
|
||||
the OSTree commit ID for Edge (OSTree) image types.
|
||||
|
||||
PR: https://github.com/osbuild/osbuild-composer/pull/1490
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
# Support multiple repository subscriptions
|
||||
|
||||
RHEL systems can have multiple subscriptions to different repositories.
|
||||
Each repository can use its certificate authority and require the users
|
||||
to authenticate with a client-side TLS certificate.
|
||||
|
||||
This is common while using Red Hat Satellite, for example.
|
||||
|
||||
osbuild-composer can now work with multiple subscriptions that are available
|
||||
on the host system. If used with a remote worker, the same subscriptions
|
||||
must be available on both systems.
|
||||
|
||||
Relevant PRs:
|
||||
https://github.com/osbuild/osbuild-composer/pull/1405
|
||||
https://github.com/osbuild/osbuild/pull/645
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
# Support for building artifacts for Fedora 32 is now dropped
|
||||
|
||||
Fedora 32 is now EOL so we decided to drop support for building images for it.
|
||||
If you need an image for this distribution, you can use an older version of
|
||||
osbuild-composer.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
# Build Edge commits in Image Builder and upload to S3
|
||||
|
||||
Edge commit image types can now be built through the Cloud API (Image Builder). Edge commits are uploaded to an S3 bucket and are downloadable through a presigned URL that is available for up to 7 days.
|
||||
|
||||
PR: https://github.com/osbuild/osbuild-composer/pull/1439
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
# Add support for new / extended osbuild stages
|
||||
|
||||
Add support for the following new osbuild stages:
|
||||
|
||||
- `org.osbuild.modprobe` - allows to configure modprobe using configuration files
|
||||
- `org.osbuild.dracut.conf` - allows to create dracut configuration files
|
||||
- `org.osbuild.systemd-logind` - allows to create system-logind configuration drop-ins
|
||||
- `org.osbuild.cloud-init` - allows to configure cloud-init
|
||||
- `org.osbuild.authselect` - allows to set system identity and auth sources using authselect
|
||||
|
||||
Add support for new functionality of existing osbuild stages:
|
||||
|
||||
- `org.osbuild.sysconfig` - allows to create network-scripts ifcfg files
|
||||
- `org.osbuild.systemd` - allows to create `.service` file drop-ins
|
||||
- `org.osbuild.chrony` - allows to configure NTP `servers` with lower level configuration options
|
||||
- `org.osbuild.keymap` - allows to configure X11 keyboard layout
|
||||
|
|
@ -1,145 +0,0 @@
|
|||
# Building images for other distributions
|
||||
|
||||
Previously osbuild-composer could only build images for the same distribution
|
||||
as the host. With the addition of the distro field in blueprint it is now
|
||||
possible to build for any supported distribution shipped with osbuild-composer.
|
||||
|
||||
|
||||
## New API route: /distros/list
|
||||
|
||||
The API now supports listing the available distributions. It will return a JSON
|
||||
object listing the installed distro names that can be used by blueprints,
|
||||
sources, and the optional `?distro=` selection on API routes.
|
||||
|
||||
eg. `curl --unix-socket /run/weldr/api.socket http://localhost/api/v1/distros/list`
|
||||
|
||||
{
|
||||
"distros": [
|
||||
"centos-8",
|
||||
"fedora-32",
|
||||
"fedora-33",
|
||||
"rhel-8",
|
||||
"rhel-84",
|
||||
"rhel-85",
|
||||
"rhel-90"
|
||||
]
|
||||
}
|
||||
|
||||
|
||||
## Distribution selection with blueprints
|
||||
|
||||
The blueprint now supports a new `distro` field that will be used to select the
|
||||
distribution to use when composing images, or depsolving the blueprint. If
|
||||
`distro` is left blank it will use the host distribution. If you upgrade the
|
||||
host operating system the blueprints with no `distro` set will build using the
|
||||
new os.
|
||||
|
||||
eg. A blueprint that will always build a fedora-32 image, no matter what
|
||||
version is running on the host:
|
||||
|
||||
name = "tmux"
|
||||
description = "tmux image with openssh"
|
||||
version = "1.2.16"
|
||||
distro = "fedora-32"
|
||||
|
||||
[[packages]]
|
||||
name = "tmux"
|
||||
version = "*"
|
||||
|
||||
[[packages]]
|
||||
name = "openssh-server"
|
||||
version = "*"
|
||||
|
||||
|
||||
## Using sources with specific distributions
|
||||
|
||||
A new optional field has been added to the repository source format. It is a
|
||||
list of distribution strings that the source will be used with when depsolving
|
||||
and building images.
|
||||
|
||||
Sources with no `distros` will be used with all composes. If you want to use a
|
||||
source for a specific distro you set the `distros` list to the distro name(s)
|
||||
to use it with.
|
||||
|
||||
eg. A source that is only used when depsolving or building fedora 32:
|
||||
|
||||
check_gpg = true
|
||||
check_ssl = true
|
||||
distros = ["fedora-32"]
|
||||
id = "f32-local"
|
||||
name = "local packages for fedora32"
|
||||
system = false
|
||||
type = "yum-baseurl"
|
||||
url = "http://local/repos/fedora32/projectrepo/"
|
||||
|
||||
This source will be used for any requests that specify fedora-32, eg. listing
|
||||
packages and specifying fedora-32 will include this source, but listing
|
||||
packages for the host distro will not.
|
||||
|
||||
|
||||
## Optional distribution selection for routes
|
||||
|
||||
Many of the API routes now support selecting the distribution to use when
|
||||
returning results. Add `?distro=<DISTRO-NAME>` to the API request and it will
|
||||
return results using `fedora-32` instead of the host distro.
|
||||
|
||||
The following routes support distro selection:
|
||||
|
||||
* /compose/types
|
||||
* /modules/list
|
||||
* /modules/info
|
||||
* /projects/list
|
||||
* /projects/info
|
||||
* /projects/depsolve
|
||||
|
||||
The compose start uses the distribution specified by the blueprint to select
|
||||
which one to use.
|
||||
|
||||
eg. Show the image types supported by `centos-8`:
|
||||
|
||||
curl --unix-socket /run/weldr/api.socket http://localhost/api/v1/compose/types?distro=centos-8
|
||||
{
|
||||
"types": [
|
||||
{
|
||||
"name": "ami",
|
||||
"enabled": true
|
||||
},
|
||||
{
|
||||
"name": "openstack",
|
||||
"enabled": true
|
||||
},
|
||||
{
|
||||
"name": "qcow2",
|
||||
"enabled": true
|
||||
},
|
||||
{
|
||||
"name": "tar",
|
||||
"enabled": true
|
||||
},
|
||||
{
|
||||
"name": "vhd",
|
||||
"enabled": true
|
||||
},
|
||||
{
|
||||
"name": "vmdk",
|
||||
"enabled": true
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
|
||||
## Unknown Distributions
|
||||
|
||||
If an unknown distribution is selected the response from the API server will be
|
||||
a `DistroError`, like this:
|
||||
|
||||
{
|
||||
"status": false,
|
||||
"errors": [
|
||||
{
|
||||
"id": "DistroError",
|
||||
"msg": "Invalid distro: fedora-1"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
# Add support for RHEL 8.5 Edge images
|
||||
|
||||
OSBuild Composer can now build RHEL 8.5 Edge images. The following image types
|
||||
are supported: edge-commit, edge-container, and edge-installer.
|
||||
|
|
@ -1,61 +0,0 @@
|
|||
# Add support for RHEL 8.5 main image types
|
||||
|
||||
OSBuild Composer can now build RHEL 8.5 images. The following new image types
|
||||
are supported:
|
||||
|
||||
- `qcow2`
|
||||
- `vhd`
|
||||
- `vmdk`
|
||||
- `openstack`
|
||||
- `ami`
|
||||
- `ec2`
|
||||
- `ec2-ha`
|
||||
|
||||
## RHEL-8.5 AWS images
|
||||
|
||||
The `ami` image type have been redefined based on the official RHEL EC2 images.
|
||||
|
||||
Notable changes compared to RHEL-8.4 are:
|
||||
|
||||
- the default user created by cloud-init is `ec2-user`
|
||||
- NTP client configuration uses `169.254.169.123` NTP server by default
|
||||
- the boot mode was changed from hybrid to legacy only
|
||||
|
||||
The `ec2` and `ec2-ha` images represent the official RHEL EC2 images, which are
|
||||
produced as part of RHEL release. These contain RHUI client packages, which are
|
||||
available only from within Red Hat internal network. For this reason, these
|
||||
image types are by default not exposed via Weldr API (in the on-premise use
|
||||
case) for all RHEL releases.
|
||||
|
||||
This default configuration can be overridden by placing the following line in
|
||||
the osbuild-composer configuration `/etc/osbuild-composer/osbuild-composer.toml`:
|
||||
|
||||
```toml
|
||||
[weldr_api.distros."rhel-*"]
|
||||
# no lines below this section
|
||||
```
|
||||
|
||||
## Extended osbuild support
|
||||
To support these image types, the following new types were added to support the
|
||||
functionality in osbuild.
|
||||
|
||||
Stages:
|
||||
- org.osbuild.copy
|
||||
- org.osbuild.truncate
|
||||
- org.osbuild.sfdisk
|
||||
- org.osbuild.qemu
|
||||
- org.osbuild.mkfs.btrfs
|
||||
- org.osbuild.mkfs.ext4
|
||||
- org.osbuild.mkfs.fat
|
||||
- org.osbuild.mkfs.xfs
|
||||
- org.osbuild.grub2.inst
|
||||
|
||||
|
||||
Devices:
|
||||
- org.osbuild.loopback
|
||||
|
||||
Mounts:
|
||||
- org.osbuild.btrfs
|
||||
- org.osbuild.ext4
|
||||
- org.osbuild.fat
|
||||
- org.osbuild.xfs
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
# Add support for RHEL 9.0 Beta
|
||||
|
||||
OSBuild Composer can now build RHEL 9.0 Beta images. All image types are based
|
||||
off RHEL 8.5 ones, thus the same set of image types is supported.
|
||||
|
||||
Note that the test coverage isn't complete at this point. Fully supported is
|
||||
just cross-building RHEL 9 qcow2 images on RHEL 8. Everything else is just
|
||||
a technical preview.
|
||||
|
|
@ -1,24 +0,0 @@
|
|||
# Weldr API: introduce the ablility to limit exposed Image Types by configuration
|
||||
|
||||
Extend Weldr API to accept a map of distribution-specific lists of denied
|
||||
image types, which should not be exposed via API. It is allowed to use
|
||||
globing patterns as Distribution and Image Type names. This functionality
|
||||
is needed to not expose image types which can't be successfully built outside
|
||||
of Red Hat VPN.
|
||||
|
||||
The list of denied Image Types is defined in `osbuild-composer` configuration,
|
||||
`/etc/osbuild-composer/osbuild-composer.toml`.
|
||||
|
||||
Example configuration denying the building of `qcow2` and `vmdk` Image Types
|
||||
via Weldr API for any distribution:
|
||||
```toml
|
||||
[weldr_api.distros."*"]
|
||||
image_type_denylist = [ "qcow2", "vmdk" ]
|
||||
```
|
||||
|
||||
Example configuration denying the building of `qcow2` and `vmdk` Image Types
|
||||
via Weldr API for `rhel-84` distribution:
|
||||
```toml
|
||||
[weldr_api.distros.rhel-84]
|
||||
image_type_denylist = [ "qcow2", "vmdk" ]
|
||||
```
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
# Workers: heartbeat
|
||||
|
||||
Workers check in with composer every 15 seconds to see if their job hasn't been
|
||||
cancelled. We can use this to introduce a heartbeat. If the worker fails to
|
||||
check in for over 2 minutes, composer assumes the worker crashed or was stopped,
|
||||
marking the job as failed.
|
||||
|
||||
This will mitigate the issue where jobs who had their worker crash or stopped,
|
||||
would remain in a 'building' state forever.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
# Workers: oauth2 support
|
||||
|
||||
This change is mainly targeted for getting composer into `cloud.redhat.com`. It
|
||||
allows remote workers to connect to composer starting from a refresh token, and
|
||||
is offered as an alternative to the client certificate authentication.
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
# RHEL-Edge container image now uses nginx and serves on port 8080
|
||||
|
||||
Previously, the edge-container image type was unable to run in unprivileged
|
||||
mode which prevented it from being used on OpenShift 4. The container now uses
|
||||
nginx to serve the commit and a configuration that allows it to run as a
|
||||
non-root user inside the container. The internal web server now uses port
|
||||
`8080` instead of `80`.
|
||||
|
||||
See rhbz#1945238
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
# Add RHEL for Edge Raw Images for 8.5
|
||||
|
||||
OSBuild Composer can now build the RHEL 8.5 Raw Images. This images are
|
||||
compressed raw images, i.e. a file that has a partition layout with an
|
||||
deployed OSTree commit in it. It can be used to flash onto a hard drive
|
||||
or booted in a virtual machine. An existing OSTree commit needs to
|
||||
be provided.
|
||||
The following image new types are supported: edge-raw-image.
|
||||
|
||||
Relevant PR: https://github.com/osbuild/osbuild-composer/pull/1667
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
# Add a new Simplified Installer for RHEL for Edge 8.5
|
||||
|
||||
OSBuild Composer can now build the RHEL 8.5 for Edge Simplified Installer.
|
||||
This installer is optimized for unattended installation to a device, which
|
||||
can be specified via a new blueprint option, `installation_device`. As for
|
||||
the existing RHEL for Edge installer, an existing OSTree commit needs to
|
||||
be provided. A raw image will be created with that commit deployed in it
|
||||
and the installer will flash this raw image to the specified installation
|
||||
device.
|
||||
The following image new types are supported: edge-simplified-installer.
|
||||
|
||||
Relevant PR: https://github.com/osbuild/osbuild-composer/pull/1654
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
# Add custom file system support for RHEL 8.5
|
||||
|
||||
The `weldr` api has been extended to support custom file systems for RHEL 8.5.
|
||||
Filesystem `mountpoints` and minimum partition `size` can be set under blueprint customizations, as below:
|
||||
|
||||
```toml
|
||||
[[customizations.filesystem]]
|
||||
mountpoint = "/"
|
||||
size = 2147483648
|
||||
```
|
||||
|
||||
In addition to the root mountpoint, `/`, the following `mountpoints` and their sub-directories are supported:
|
||||
|
||||
- `/var`
|
||||
- `/home`
|
||||
- `/opt`
|
||||
- `/srv`
|
||||
- `/usr`
|
||||
- `/app`
|
||||
- `/data`
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
# Add custom file system support for RHEL 9.0
|
||||
|
||||
The `weldr` api has been extended to support custom file systems for RHEL 9.0.
|
||||
Filesystem `mountpoints` and minimum partition `size` can be set under blueprint customizations, as below:
|
||||
|
||||
```toml
|
||||
[[customizations.filesystem]]
|
||||
mountpoint = "/"
|
||||
size = 2147483648
|
||||
```
|
||||
|
||||
In addition to the root mountpoint, `/`, the following `mountpoints` and their sub-directories are supported:
|
||||
|
||||
- `/var`
|
||||
- `/home`
|
||||
- `/opt`
|
||||
- `/srv`
|
||||
- `/usr`
|
||||
- `/app`
|
||||
- `/data`
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
# Bootiso: move payload to iso root
|
||||
|
||||
Instead of including the payload, i.e. ostree commits or live images,
|
||||
in the anaconda squashfs, they are now located at the root of the iso.
|
||||
This has several advantages, including shorter build times, more
|
||||
flexibility in payload size and easier access to the actual payload.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
# Fix building of RHEL 9.0 Edge images
|
||||
|
||||
RHEL 9.0 Beta doesn't ship iwl6000-firmware anymore therefore we had to remove
|
||||
it from the edge-commit and edge-installer image definitions.
|
||||
|
|
@ -1,49 +0,0 @@
|
|||
# Composer-api and worker-api: OAuth2 support
|
||||
|
||||
Adding OAuth2 support to composer means both the composer-api and worker-api are now able to authenticate clients using
|
||||
the [JWT](https://jwt.io/) set in the "Authorization" HTTP header. This was added with Red Hat Single Sign-On in mind,
|
||||
but would work for other OAuth2 providers as well (potentially with minor changes).
|
||||
|
||||
## Workflow
|
||||
|
||||
1. A client makes a request to https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token using
|
||||
their offline token.
|
||||
|
||||
2. sso.redhat.com would respond with an `access_token` which is valid for a certain period.
|
||||
|
||||
3. This `access_token` can be set in the "Authorization" HTTP header: "Authorization: Bearer `access_token`".
|
||||
|
||||
4. Composer verifies the token against the certificates returned by
|
||||
https://^Co.redhat.com/auth/realms/redhat-external/protocol/openid-connect/certs.
|
||||
|
||||
## Configuration
|
||||
|
||||
Using [openshift-online/ocm-sdk](https://github.com/openshift-online/ocm-sdk-go) composer-api now supports oauth2
|
||||
authentication. To this end there's 4 new config options for the Worker and Composer API:
|
||||
|
||||
- EnableJWT: Enable or disable OAuth2 authentication.
|
||||
- JWTKeysURL: Location where the certs used to verify the JWT tokens are served.
|
||||
- JWTKeysCA: Path to the CA which should be used when retrieving the certs (optional).
|
||||
- JWTACLFile: Path to a yaml file containing a series of pattern match rules against the claims
|
||||
contained within the JWT (optional).
|
||||
|
||||
### ACL claims pattern matching format
|
||||
|
||||
The ACLFile should contain a list of claims and their required pattern in yaml format. Note that a claim with a specific
|
||||
name can only be specified once. So if for instance a required pattern for the `email` claim is listed twice, only one
|
||||
will pattern will be applied.
|
||||
|
||||
The pattern is verified using the golang regexp package, and follows the [RE2
|
||||
syntax](https://github.com/google/re2/wiki/Syntax).
|
||||
|
||||
Example:
|
||||
```
|
||||
- claim: email
|
||||
pattern: ^.*@redhat\.com$
|
||||
- claim: sub
|
||||
pattern: ^f:b3f7b485-7184-43c8-8169-37bd6d1fe4aa:myuser$
|
||||
- claim: account_number
|
||||
pattern: ^(1000|1001|1002)$
|
||||
- claim: account_id
|
||||
pattern: ^(5000|5005)$
|
||||
```
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
# Install docs in RHEL 8.5 and 9.0 images
|
||||
|
||||
Previously, all packages in all image types were installed using the
|
||||
--excludedocs options. This is great for the image size but it actually
|
||||
causes some issues too: The biggest one is that there are no man pages inside
|
||||
the images. As that is a pretty big regression, we decided to revert
|
||||
the --excludedocs setting now.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
# RHEL-8.5 / RHEL-9.0: RHSM DNF plugins are now enabled by default on `ec2` and `ami` images
|
||||
|
||||
The RHSM DNF plugins `product-id` and `subscription-manager` are now by default enabled
|
||||
on the RHEL-8.5 and RHEL-9.0 `ec2`, `ec2-ha` and `ami` images.
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
# Added support for new osbuild stages required for RHEL EC2 SAP images
|
||||
|
||||
Added support for the following osbuild stages:
|
||||
|
||||
- `org.osbuild.selinux.config` - configures SELinux policy state and type on the system
|
||||
- `org.osbuild.tmpfilesd` - creates tmpfiles.d configuration files
|
||||
- `org.osbuild.pam.limits.conf` - creates configuration files for pam_limits module
|
||||
- `org.osbuild.sysctld` - creates sysctl.d configuration files
|
||||
- `org.osbuild.dnf.config` - configures DNF (currently only variables)
|
||||
- `org.osbuild.tuned` - sets active tuned profile (or more profiles)
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
# Support AWS temporary credentials
|
||||
|
||||
When using AWS and AWS S3 targets, it is possible to use temporary AWS credentials by specifying a `SessionToken` in addition to the usual `AccessKeyId` and `SecretAccessKey`
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
# Add support for official RHEL EC2 SAP image on RHEL-9.0
|
||||
|
||||
OSBuild Composer can now build the RHEL 9.0 EC2 SAP image called `ec2-sap`,
|
||||
which is based on the official RHEL EC2 SAP image. The image type is not
|
||||
exposed through the Weldr API, because its default package set includes the
|
||||
RHUI client packages, which are not publicly available.
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
# Add support for official RHEL EC2 SAP image on RHEL-8.6
|
||||
|
||||
OSBuild Composer can now build the RHEL 8.6 EC2 SAP image called `ec2-sap`,
|
||||
which is based on the official RHEL EC2 SAP image. The image type is not
|
||||
exposed through the Weldr API, because its default package set includes the
|
||||
RHUI client packages, which are not publicly available.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
# Add support for RHEL 8.6
|
||||
|
||||
OSBuild Composer can now build RHEL 8.6 images. All image types are based
|
||||
off RHEL 8.5 ones, thus the same set of image types is supported.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
# Release Notes
|
||||
|
||||
This directory contains release notes for _osbuild-composer_ in the form of
|
||||
short markdown documents, sorted into subdirectories by release.
|
||||
|
||||
When proposing a user-visible change, please add a release note into the
|
||||
`unreleased` directory. The note should explain the change from the perspective
|
||||
of somebody using _osbuild-composer_ and ideally how the change affects them or
|
||||
how they can make use of new functionality.
|
||||
|
||||
When preparing a release, a maintainer will rename the `unreleased` directory
|
||||
and summarize its contents in `NEWS.md`.
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
# Timeout when requesting jobs
|
||||
|
||||
When workers request a new job they make a blocking call to the `/api/worker/v1/jobs`
|
||||
endpoint. There are cases however where a polling approach is more useful, for instance when idle
|
||||
connections get terminated after a certain period of time.
|
||||
|
||||
The new `request_job_timeout` option under the worker config section allows for a timeout on the
|
||||
`/api/worker/v1/jobs` endpoint. It's a string with `"0"` as default, any string which is parseable
|
||||
by `time.Duration.ParseDuration()` is allowed however, for instance `"10s"`.
|
||||
|
||||
Because this is an expected timeout, "204 No Content" will be returned by the worker server in case
|
||||
of such a timeout. The worker client will simply poll again straight away.
|
||||
|
||||
To maintain backwards compatilibity the default behaviour is still a blocking connection without
|
||||
timeout.
|
||||
Loading…
Add table
Add a link
Reference in a new issue