ALP Release Notes #
This document provides an overview of high-level general features, capabilities, and limitations of ALP and important product updates.
1 About the release notes #
These Release Notes are identical across all architectures, and the most recent version is always available online at https://www.suse.com/releasenotes.
Entries are only listed once but they can be referenced in several places if they are important and belong to more than one section.
Release notes usually only list changes that happened between two subsequent releases. +
This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.
ALP Release Notes #
This document provides an overview of high-level general features, capabilities, and limitations of ALP and important product updates.
1 About the release notes #
These Release Notes are identical across all architectures, and the most recent version is always available online at https://www.suse.com/releasenotes.
Entries are only listed once but they can be referenced in several places if they are important and belong to more than one section.
Release notes usually only list changes that happened between two subsequent releases. Certain important entries from the release notes of previous product versions are repeated. To make these entries easier to identify, they contain a note to that effect.
However, repeated entries are provided as a courtesy only. Therefore, if you are skipping one or more service packs, check the release notes of the skipped service packs as well. If you are only reading the release notes of the current release, you could miss important changes.
1.1 Documentation and other information #
1.1.1 Available on the product media #
Read the READMEs on the media.
Get the detailed change log information about a particular package from the RPM (where
FILENAME.rpmis the name of the RPM):rpm --changelog -qp FILENAME.rpm
Check the
ChangeLogfile in the top level of the installation medium for a chronological log of all changes made to the updated packages.Find more information in the
docudirectory of the installation medium of ALP . -This directory includes PDF versions of the ALP Installation Quick Start Guide.Get list of manual pages with usage information about a particular package from the RPM (where
FILENAME.rpmis the name of the RPM):rpm --docfiles -qp FILENAME.rpm | grep man
1.1.2 Online documentation #
For the most up-to-date version of the documentation for ALP , see:
2 SUSE Linux Micro #
SUSE Linux Micro is a modern operating system primarily targeted for edge computing. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Micro 6.0.
2.1 Changes affecting all architectures #
Information in this section applies to all architectures supported by SL Micro 6.0.
2.2 Installation #
2.2.1 Installation media #
Image based deployment images
Base OS Image (Base OS + podman only)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image (Base OS, salt-minion, KVM + libvirt packages)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image with RT kernel (x86_64 only), no KVM support on this image
Base OEM image – self-installation image (Base OS + podman only) for x86_64
OEM image – self-installation image (Base OS, salt-minion, KVM + libvirt packages) for x86_64
OEM image with RT kernel – self-installation image, no KVM support on this image for x86_64
Images other than QCOW or VMDK target bare metal deployments.
2.2.2 Additional container images #
SUSE Toolbox container for debugging, based on current SLE 15 SP, provided via registry.suse.com
PCP container image (unmodified)
2.2.3 High-level requirements #
Use of SLE Micro without a container runtime is only supported when SLE Micro is used as a KVM host and workloads are installed into KVM virtual machines. +This directory includes PDF versions of the ALP Installation Quick Start Guide.
Get list of manual pages with usage information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --docfiles -qp FILENAME.rpm | grep man
1.1.2 Online documentation #
For the most up-to-date version of the documentation for ALP , see:
2 SUSE Linux Micro #
SUSE Linux Micro is a modern operating system primarily targeted for edge computing. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Micro 6.0.
2.1 Changes affecting all architectures #
Information in this section applies to all architectures supported by SL Micro 6.0.
2.2 Installation #
2.2.1 Installation media #
Image based deployment images
Base OS Image (Base OS + podman only)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image (Base OS, salt-minion, KVM + libvirt packages)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image with RT kernel (x86_64 only), no KVM support on this image
Base OEM image – self-installation image (Base OS + podman only) for x86_64
OEM image – self-installation image (Base OS, salt-minion, KVM + libvirt packages) for x86_64
OEM image with RT kernel – self-installation image, no KVM support on this image for x86_64
Images other than QCOW or VMDK target bare metal deployments.
2.2.2 Additional container images #
SUSE Toolbox container for debugging, based on current SLE 15 SP, provided via registry.suse.com
PCP container image (unmodified)
2.2.3 High-level requirements #
Use of SLE Micro without a container runtime is only supported when SLE Micro is used as a KVM host and workloads are installed into KVM virtual machines. Running workloads directly on the OS is not supported, with the exception of system management software.
2.2.4 Installation modes #
SUSE Linux Micro 6.0 only supports deployment via images. An installer based installation method is not offered.
Customization of the installation process with the provided images can be done with Ignition and Combustion (pre-configured images and self-installing images).
We will offer select images with support for cloud-init with a later milestone.
2.2.5 Supported architectures #
Intel/AMD 64bit (
x86_64)Arm 64bit (
aarch64)IBM Z (
s390x)
2.2.6 Upgrade path #
An online migration of existing SUSE Linux Micro 5.5 installations to SUSE Linux Micro 6.0 is possible and is fully supported.
Upgrading from SUSE Linux Micro 5.5 is only possible via the transactional-update tool.
@@ -104,7 +104,8 @@
The command will destroy all images, networks and all containers.
For a complete overview of the changes, please check out the upstream 4.0.0 but also 4.1.1, 4.2.0 and 4.3.0 to be informed about all the new features and changes.
2.3.7 Legacy BIOS boot support is deprecated #
With SUSE Linux Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
2.3.8 LTTng is deprecated #
SUSE Linux Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Micro version in favor of alternative solutions for tracing like bpftrace.
2.3.9 Cockpit web-based node management system #
For web-based management of a single node, Cockpit is included. For details, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/article-administration-slemicro.html#sec-admin-Cockpit.
There have been new Cockpit modules added to the product. Due to the amount of dependencies, not all of the Cockpit modules are part of the raw images and some have to be installed additionally.
When enabling a firewall via the Cockpit user interface, be aware that your connection to the host may be interrupted unless the Cockpit port is configured to be open in advance.
The SELinux module for Cockpit provides basic functionality for users to troubleshoot their configuration.
With this release the functionality has been extended with the introduction of the setroubleshoot-server package.
2.3.10 Managing SUSE Linux Micro with SUSE Manager #
SUSE Manager can be used to manage SUSE Linux Micro hosts. There are certain limitations:
SUSE Linux Micro host cannot be monitored with SUSE Manager
SUSE Manager does not provide integrated container management yet. As a workaround, you can use Salt via cmd.run podman.
SUSE Manager can manage the SUSE Linux Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Micro on SUSE Manager.
2.3.11 Public Cloud Images #
The Public Cloud instance initialization code has been changed from using Ignition and Afterburn to cloud-init in AWS EC2, cloud-init and the Azure agent in Azure, and the Google guest environment for GCE. This means configuration of instances through user data now behaves the same as SUSE Linux Enterprise Server, any version, instances. This also addresses the issue in Azure with the state detection of the VM. The web console will now properly show a VM in "Running" state instead of appearing to be stuck in "Provisioning". This also allows user configuration through the web console in Azure and user configuration using the customary ways in AWS EC2 and GCE.
2.3.12 Default container registries #
The container registry entries for Docker Hub and openSUSE Registry, which were previously included by default, have now been removed.
-If you want to pull container images from either of them, add them to the /etc/containers/registries.conf file.
2.4 Arm 64-bit-specific features and fixes (AArch64) #
Information in this section applies to SL Micro 6.0.
2.4.1 System-on-Chip driver enablement #
SL Micro 6.0 includes driver enablement for the following
+If you want to pull container images from either of them, add them to the /etc/containers/registries.conf file.
2.3.13 Miscellaneous #
2.3.13.1 IMA EVM signing plugin #
A RPM plugin for IMA (Integrity Measurement Architecture)/EVM (Linux Extended Verification Module) signing has been added. +The plugin is installed as part of the following package:
rpm-imaevmsign
2.4 Arm 64-bit-specific features and fixes (AArch64) #
Information in this section applies to SL Micro 6.0.
2.4.1 System-on-Chip driver enablement #
SL Micro 6.0 includes driver enablement for the following System-on-Chip (SoC) chipsets:
Ampere* X-Gene*, eMAG*, Altra*, Altra Max, AmpereOne*
AWS* Graviton, Graviton2, Graviton3
Broadcom* BCM2837/BCM2710, BCM2711
Fujitsu* A64FX
Huawei* Kunpeng* 916, Kunpeng 920
Marvell* ThunderX*, ThunderX2*; OCTEON TX*; Armada* 7040, Armada 8040
NVIDIA* Grace; Tegra* X1, Tegra X2, Xavier*, Orin; BlueField*, BlueField-2, BlueField-3
NXP* i.MX 8M, 8M Mini; Layerscape* LS1012A, LS1027A/LS1017A, LS1028A/LS1018A, LS1043A, LS1046A, LS1088A, LS2080A/LS2040A, LS2088A, LX2160A
Rockchip RK3399
Socionext* SynQuacer* SC2A11
Xilinx* Zynq* UltraScale*+ MPSoC
Driver enablement is done as far as available and requested. Refer to the following sections for any known limitations.
Some systems might need additional drivers for external chips, such as a Power Management Integrated Chip (PMIC), which may differ between systems diff --git a/main/html/release-notes-micro/index.html b/main/html/release-notes-micro/index.html index 602bc8e..9581010 100644 --- a/main/html/release-notes-micro/index.html +++ b/main/html/release-notes-micro/index.html @@ -91,14 +91,14 @@ useBR: false }); -
This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.
Release Notes #
SUSE Linux Micro is a modern operating system primarily targeted for edge computing. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Micro 6.0.
This product will be released in TBD. +
This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.
Release Notes #
SUSE Linux Micro is a modern operating system primarily targeted for edge computing. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Micro 6.0.
This product will be released in TBD. The latest version of these release notes is always available at https://www.suse.com/releasenotes. Drafts of the general documentation can be found at https://susedoc.github.io/doc-sle/main.
1 About the release notes #
These Release Notes are identical across all architectures, and the most recent version is always available online at https://www.suse.com/releasenotes.
Entries are only listed once but they can be referenced in several places if they are important and belong to more than one section.
Release notes usually only list changes that happened between two subsequent releases. Certain important entries from the release notes of previous product versions are repeated. To make these entries easier to identify, they contain a note to that effect.
However, repeated entries are provided as a courtesy only. Therefore, if you are skipping one or more service packs, check the release notes of the skipped service packs as well. If you are only reading the release notes of the current release, you could miss important changes.
1.1 Documentation and other information #
1.1.1 Available on the product media #
Read the READMEs on the media.
Get the detailed change log information about a particular package from the RPM (where
FILENAME.rpmis the name of the RPM):rpm --changelog -qp FILENAME.rpm
Check the
ChangeLogfile in the top level of the installation medium for a chronological log of all changes made to the updated packages.Find more information in the
docudirectory of the installation medium of SUSE Linux Micro 6.0. -This directory includes PDF versions of the SUSE Linux Micro 6.0 Installation Quick Start Guide.Get list of manual pages with usage information about a particular package from the RPM (where
FILENAME.rpmis the name of the RPM):rpm --docfiles -qp FILENAME.rpm | grep man
1.1.2 Online documentation #
For the most up-to-date version of the documentation for SUSE Linux Micro 6.0, see:
https://susedoc.github.io/doc-sle/main (draft version).
2 Changes affecting all architectures #
Information in this section applies to all architectures supported by SL Micro 6.0.
3 Installation #
3.1 Installation media #
Image based deployment images
Base OS Image (Base OS + podman only)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image (Base OS, salt-minion, KVM + libvirt packages)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image with RT kernel (x86_64 only), no KVM support on this image
Base OEM image – self-installation image (Base OS + podman only) for x86_64
OEM image – self-installation image (Base OS, salt-minion, KVM + libvirt packages) for x86_64
OEM image with RT kernel – self-installation image, no KVM support on this image for x86_64
Images other than QCOW or VMDK target bare metal deployments.
3.2 Additional container images #
SUSE Toolbox container for debugging, based on current SLE 15 SP, provided via registry.suse.com
PCP container image (unmodified)
3.3 High-level requirements #
Use of SLE Micro without a container runtime is only supported when SLE Micro is used as a KVM host and workloads are installed into KVM virtual machines. +This directory includes PDF versions of the SUSE Linux Micro 6.0 Installation Quick Start Guide.
Get list of manual pages with usage information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --docfiles -qp FILENAME.rpm | grep man
1.1.2 Online documentation #
For the most up-to-date version of the documentation for SUSE Linux Micro 6.0, see:
https://susedoc.github.io/doc-sle/main (draft version).
2 Changes affecting all architectures #
Information in this section applies to all architectures supported by SL Micro 6.0.
3 Installation #
3.1 Installation media #
Image based deployment images
Base OS Image (Base OS + podman only)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image (Base OS, salt-minion, KVM + libvirt packages)
Plus QCOW version of this image (x86_64, aarch64. S390x)
Plus VMware (VMDK) version of this image (x86_64)
OS image with RT kernel (x86_64 only), no KVM support on this image
Base OEM image – self-installation image (Base OS + podman only) for x86_64
OEM image – self-installation image (Base OS, salt-minion, KVM + libvirt packages) for x86_64
OEM image with RT kernel – self-installation image, no KVM support on this image for x86_64
Images other than QCOW or VMDK target bare metal deployments.
3.2 Additional container images #
SUSE Toolbox container for debugging, based on current SLE 15 SP, provided via registry.suse.com
PCP container image (unmodified)
3.3 High-level requirements #
Use of SLE Micro without a container runtime is only supported when SLE Micro is used as a KVM host and workloads are installed into KVM virtual machines. Running workloads directly on the OS is not supported, with the exception of system management software.
3.4 Installation modes #
SUSE Linux Micro 6.0 only supports deployment via images. An installer based installation method is not offered.
Customization of the installation process with the provided images can be done with Ignition and Combustion (pre-configured images and self-installing images).
We will offer select images with support for cloud-init with a later milestone.
3.5 Supported architectures #
Intel/AMD 64bit (
x86_64)Arm 64bit (
aarch64)IBM Z (
s390x)
3.6 Upgrade path #
An online migration of existing SUSE Linux Micro 5.5 installations to SUSE Linux Micro 6.0 is possible and is fully supported.
Upgrading from SUSE Linux Micro 5.5 is only possible via the transactional-update tool.
@@ -124,7 +124,8 @@
The command will destroy all images, networks and all containers.
For a complete overview of the changes, please check out the upstream 4.0.0 but also 4.1.1, 4.2.0 and 4.3.0 to be informed about all the new features and changes.
4.7 Legacy BIOS boot support is deprecated #
With SUSE Linux Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
4.8 LTTng is deprecated #
SUSE Linux Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Micro version in favor of alternative solutions for tracing like bpftrace.
4.9 Cockpit web-based node management system #
For web-based management of a single node, Cockpit is included. For details, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/article-administration-slemicro.html#sec-admin-Cockpit.
There have been new Cockpit modules added to the product. Due to the amount of dependencies, not all of the Cockpit modules are part of the raw images and some have to be installed additionally.
When enabling a firewall via the Cockpit user interface, be aware that your connection to the host may be interrupted unless the Cockpit port is configured to be open in advance.
The SELinux module for Cockpit provides basic functionality for users to troubleshoot their configuration.
With this release the functionality has been extended with the introduction of the setroubleshoot-server package.
4.10 Managing SUSE Linux Micro with SUSE Manager #
SUSE Manager can be used to manage SUSE Linux Micro hosts. There are certain limitations:
SUSE Linux Micro host cannot be monitored with SUSE Manager
SUSE Manager does not provide integrated container management yet. As a workaround, you can use Salt via cmd.run podman.
SUSE Manager can manage the SUSE Linux Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Micro on SUSE Manager.
4.11 Public Cloud Images #
The Public Cloud instance initialization code has been changed from using Ignition and Afterburn to cloud-init in AWS EC2, cloud-init and the Azure agent in Azure, and the Google guest environment for GCE. This means configuration of instances through user data now behaves the same as SUSE Linux Enterprise Server, any version, instances. This also addresses the issue in Azure with the state detection of the VM. The web console will now properly show a VM in "Running" state instead of appearing to be stuck in "Provisioning". This also allows user configuration through the web console in Azure and user configuration using the customary ways in AWS EC2 and GCE.
4.12 Default container registries #
The container registry entries for Docker Hub and openSUSE Registry, which were previously included by default, have now been removed.
-If you want to pull container images from either of them, add them to the /etc/containers/registries.conf file.
5 Arm 64-bit-specific features and fixes (AArch64) #
Information in this section applies to SL Micro 6.0.
5.1 System-on-Chip driver enablement #
SL Micro 6.0 includes driver enablement for the following
+If you want to pull container images from either of them, add them to the /etc/containers/registries.conf file.
4.13 Miscellaneous #
4.13.1 IMA EVM signing plugin #
A RPM plugin for IMA (Integrity Measurement Architecture)/EVM (Linux Extended Verification Module) signing has been added. +The plugin is installed as part of the following package:
rpm-imaevmsign
5 Arm 64-bit-specific features and fixes (AArch64) #
Information in this section applies to SL Micro 6.0.
5.1 System-on-Chip driver enablement #
SL Micro 6.0 includes driver enablement for the following System-on-Chip (SoC) chipsets:
Ampere* X-Gene*, eMAG*, Altra*, Altra Max, AmpereOne*
AWS* Graviton, Graviton2, Graviton3
Broadcom* BCM2837/BCM2710, BCM2711
Fujitsu* A64FX
Huawei* Kunpeng* 916, Kunpeng 920
Marvell* ThunderX*, ThunderX2*; OCTEON TX*; Armada* 7040, Armada 8040
NVIDIA* Grace; Tegra* X1, Tegra X2, Xavier*, Orin; BlueField*, BlueField-2, BlueField-3
NXP* i.MX 8M, 8M Mini; Layerscape* LS1012A, LS1027A/LS1017A, LS1028A/LS1018A, LS1043A, LS1046A, LS1088A, LS2080A/LS2040A, LS2088A, LX2160A
Rockchip RK3399
Socionext* SynQuacer* SC2A11
Xilinx* Zynq* UltraScale*+ MPSoC
Driver enablement is done as far as available and requested. Refer to the following sections for any known limitations.
Some systems might need additional drivers for external chips, such as a Power Management Integrated Chip (PMIC), which may differ between systems @@ -162,5 +163,5 @@ SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2024-2024 SUSE LLC.
This release notes document is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License (CC-BY-ND-4.0). You should have received a copy of the license along with this document. If not, see https://creativecommons.org/licenses/by-nd/4.0/.
SUSE has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at https://www.suse.com/company/legal/ and one or more additional patents or pending patent applications in the U.S. and other countries.
For SUSE trademarks, see the SUSE Trademark and Service Mark list (https://www.suse.com/company/legal/). -All third-party trademarks are the property of their respective owners.