python/diskimage-builder
SHA256
15
0
Fork 0
forked from pool/diskimage-builder
Code Pull Requests Activity

Accepting request 1275540 from home:dgarcia:branches:devel:languages:python

Browse Source 
- Update to 3.37.0:
  - Supports Gentoo profile 23.0 and removes support for the
    nonworking 17.1 and 17.0 profiles.
  - Gentoo element updated to avoid using testing (~arch) packages.
  - Gentoo element now uses upstream binary package host by default.
  - Fixes an issue where an image using the manifest element could
    fail to build when using a non-root user. See bug 2069956.
  - Fixed an issue where the growroot element on openrc init systems
    would not function.
  - Fixed an issue where the devuser element was unable to grant sudo
    capabilities on gentoo images.
  - Fixed an issue in Gentoo implmentation for install-packages
    element where build time would grow linearly with each additional
    package removal. Now, all removed packages are deselected and
    removed in a single transaction.
- 3.36.0:
  - The vm element is no longer included dependency of the
    rocky-container, almalinux-container and fedora-container
    elements. You will need to update your build configuration to
    include this element if you still wish to create partitioned disk
    based images.
- 3.34.0:
  - Adds the ability for diskimage-builder to create images with
    different block sizes. By default, this remains at the default of
    512 bytes, but some newer devices require 4096 bytes to be used,
    which impacts the overall layout rendering 512 byte images
    incompatible. This setting can also be asserted and overridden
    using the DIB_BLOCK_SIZE environment variable, but alternatively
    exists as a new block_size parameter for local_loop section in
    block device YAML documents.

OBS-URL: https://build.opensuse.org/request/show/1275540
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/diskimage-builder?expand=0&rev=69
This commit is contained in:
Steve Kowalik
2025-05-12 06:06:51 +00:00
committed by Git OBS Bridge
parent 8ee3c8b1ad
commit e2a3fb8ce5
4 changed files with 165 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

149
diskimage-builder.changes
View File

@@ -1,3 +1,152 @@
-------------------------------------------------------------------
Thu May 8 12:06:24 UTC 2025 - Daniel Garcia <daniel.garcia@suse.com>
- Update to 3.37.0:
- Supports Gentoo profile 23.0 and removes support for the
nonworking 17.1 and 17.0 profiles.
- Gentoo element updated to avoid using testing (~arch) packages.
- Gentoo element now uses upstream binary package host by default.
- Fixes an issue where an image using the manifest element could
fail to build when using a non-root user. See bug 2069956.
- Fixed an issue where the growroot element on openrc init systems
would not function.
- Fixed an issue where the devuser element was unable to grant sudo
capabilities on gentoo images.
- Fixed an issue in Gentoo implmentation for install-packages
element where build time would grow linearly with each additional
package removal. Now, all removed packages are deselected and
removed in a single transaction.
- 3.36.0:
- The vm element is no longer included dependency of the
rocky-container, almalinux-container and fedora-container
elements. You will need to update your build configuration to
include this element if you still wish to create partitioned disk
based images.
- 3.34.0:
- Adds the ability for diskimage-builder to create images with
different block sizes. By default, this remains at the default of
512 bytes, but some newer devices require 4096 bytes to be used,
which impacts the overall layout rendering 512 byte images
incompatible. This setting can also be asserted and overridden
using the DIB_BLOCK_SIZE environment variable, but alternatively
exists as a new block_size parameter for local_loop section in
block device YAML documents.
- A new element autoupdates is added to DIB. This element, with
proper configuration, will enable and configure cloud images to
have a system that automatically updates the image, from the
upstream binaries. To this end, DIB_DEB_UPDATES_CONF or
DIB_YUM_UPDATES_CONF must be set during build time.
- Adds the ability to disable serial console logging from being
setup in the bootloader element by setting the
DIB_BOOTLOADER_USE_SERIAL_CONSOLE environment variable to False.
- Adds logic to permit the removal of consoles when the bootloader
element when no configuration has been expressed which requests
it, and serial console is disabled. This involves
DIB_BOOTLOADER_VIRTUAL_TERMINAL being set to an empty string and
DIB_BOOTLOADER_USE_SERIAL_CONSOLE is set to False.
- The new element replace-partition has been added which allows a
diskimage-builder built image to be used as the base image so that
it can be copied to a new partition layout. This allows the
content to be copied from one image to a new one without making
any package changes. The element replace-partition-redhat has a
documented example for redhat family images.
- It is no longer possible to build images using CentOS 7 or RHEL 7
as a base image as these reached EOL on 30th June 2024. The centos
and centos-minimal elements now default to a DIB_RELEASE value of
9-stream.
- DIB_GRUB_TIMEOUT defaulting to 1 second, GRUB_TIMEOUT was
duplicated in the /etc/defaults/grub the original intension of
DIB_GRUB_TIMEOUT default was to match the typical image default
which is one 1 second instead of 5 second today.
- The bootloader element now strips prior explicit console settings
from the /etc/default/grub file, in order to prevent accidential
re-introduction of prior settings when grub configuration is
manually updated later.
- The default release for the centos element is now “9-stream”
instead of “8”. This is a result of Centos8 having reached End of
Life.
- The autoupdates element has only been tested in Rocky and Ubuntu
images. In addition, the element does not check the validity of
the configuration files in any way.
- 3.33.0:
- Fixes an issue where if an operator set a cloud-init data source
to ConfigDrive, the host might not properly configure as automatic
metadata collection still attempts to operate. We now disable that
by default, when ConfigDrive is passed as an argument.
- 3.32.0:
- A new fail2ban element has been added which has has been tested on
Debian and Rocky images. The usage of a new variable
DIB_FAIL2BAN_CONF is now mandatory during built time.
- The bootloader element will explicitly set the timeout style to
hidden to hide the menu. Set DIB_GRUB_TIMEOUT_STYLE to menu to
display the menu and then wait for the timeout expire before
booting the default entry.
- Use of the simple-init element now removes cloud-init, in order to
prevent the two tools from clashing when booting a workload.
- Added a DIB_DEBIAN_CLOUD_INIT_HELPER variable that controls
whether debian element will attempt to pre-create required users
and sudoers file for the default cloud-init user. This should not
be needed for any modern Debian distro.
- Value of DIB_DEBIAN_ALT_INIT_PACKAGE has been switched to
systemd-sysv for Debian releases older then Jessie. If you still
need to build a version of Debian that is relying on sysvinit
please override the DIB_DEBIAN_ALT_INIT_PACKAGE variable for that.
- 3.31.0:
- The usage of the DIB_CHECKSUM variable is extended. Now to be more
specific the variable can be set to the sha256 or md5 value to
generate only one checksum file. There also can be provided a
comma-separated list of the values, but only sha256 and md5
supported. For backward compatibility using DIB_CHECKSUM=1 or
option --checksum in the command line still can be used to
generate all supported checksums.
- The deploy-baremetal, deploy-kexec, deploy-tgtadm, and
deploy-targetcli elements are deprecated and will be removed in a
future release of diskimage-builder. The origins of the elemenets
largely dates back to the early efforts to support baremetal
deployment, and the methods have been long ago moved away from.
- As NetworkManager can’t automatically create default connection
profiles for InfiniBand interfaces, we are adding
nm-dhcp-ib-interfaces element to install
NetworkManager-system-connections-infiniband.nmconnection to
NetworkManager to create a wildcard InfiniBand connection profile.
- 3.30.0:
- Added environment variable REG_SAT_REPO to the rhel-common
element. Sets the repository label for Satellite client tools.
- The bootloader element now has variable
DIB_BOOTLOADER_VIRTUAL_TERMINAL to customize or suppress the
console=tty0 kernel argument.
- The Satellite Client reposotories replaces the Satellite Tools
repository since Satellite 6.11. The default repo labels in the
rhel-common element has been updated to reflect this change. See
Red Hat Satellite 6.11 Release Notes.
- To enable users that need to use the legacy Satellite Tools
repository, the REG_SAT_REPO environment variable has been added
to enable manual override of the Satellite repository.
- 3.28.0:
- Adds a fips element which attempts to enable FIPS mode
configuration into the disk image being created.
- A new command diskimage-builder is now provided (also aliased to
dib). It provides a YAML file based interface to disk-image-create
and ramdisk-image-create. All arguments can be specified as yaml
dictionary entries, along with environment variable overrides
which are applied over the provided environment.
- Adds swap as a valid “filesystem” for block devices
- Fixed the ubuntu-minimal target to also run autoremove at the end
of an image build.
- Fixes a possible case with a FIPS enabled disk image where the
cryptographic policies may be applied for enforcement of FIPS
mode, but the underlying kernel command line may be missing. This
in particular was discovered when testing on Rocky Linux. We now
test, and add the FIPS kernel command line flag if it is otherwise
enabled.
- Fixes the GRUB2 bootloader kernel command line where a prior boot
parameter could cause issues with bootloader configuration when an
image is rebuilt and the bootloader element is utilized. We now
remove any prior boot parameter in /etc/default/grub when
executing the bootloader element, and then assert a valid entry
boot parameter if a /boot partition is defined as part of the
image build.
-------------------------------------------------------------------
Sat Jan 28 19:45:48 UTC 2023 - Dirk Müller <dmueller@suse.com>