30
Release osbuild-composer 30. Signed-off-by: Ondřej Budai <ondrej@budai.cz>
This commit is contained in:
Ondřej Budai
Achilleas Koutsou
parent
602b97b2a8
commit
b5c65b687a
11 changed files with 38 additions and 1 deletions
|
|
@ -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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue