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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
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.
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 SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLES 15 SP5 and SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/main/html/release-notes-micro/index.html b/main/html/release-notes-micro/index.html
new file mode 100644
index 0000000..b24f462
--- /dev/null
+++ b/main/html/release-notes-micro/index.html
@@ -0,0 +1,167 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
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.
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 SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLES 15 SP5 and SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
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.
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 SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLES 15 SP5 and SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/main/single-html/release-notes-all/release-notes-all_draft.html b/main/single-html/release-notes-all/release-notes-all_draft.html
new file mode 100644
index 0000000..f1c467f
--- /dev/null
+++ b/main/single-html/release-notes-all/release-notes-all_draft.html
@@ -0,0 +1,147 @@
+
+ALP Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
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.
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 SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLES 15 SP5 and SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/main/single-html/release-notes-micro/index.html b/main/single-html/release-notes-micro/index.html
new file mode 100644
index 0000000..a9f770a
--- /dev/null
+++ b/main/single-html/release-notes-micro/index.html
@@ -0,0 +1,167 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
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.
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 SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLES 15 SP5 and SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/main/single-html/release-notes-micro/release-notes-micro_draft.html b/main/single-html/release-notes-micro/release-notes-micro_draft.html
new file mode 100644
index 0000000..a9f770a
--- /dev/null
+++ b/main/single-html/release-notes-micro/release-notes-micro_draft.html
@@ -0,0 +1,167 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
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.
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 SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLES 15 SP5 and SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/pubCloud/html/release-notes-all/index.html b/pubCloud/html/release-notes-all/index.html
new file mode 100644
index 0000000..d44a60e
--- /dev/null
+++ b/pubCloud/html/release-notes-all/index.html
@@ -0,0 +1,99 @@
+
+ALP Release Notes
+
+
+
+
+
+
+
+
+
+
+
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.4 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/pubCloud/html/release-notes-dolomite/changelog.html b/pubCloud/html/release-notes-dolomite/changelog.html
new file mode 100644
index 0000000..f8fa19c
--- /dev/null
+++ b/pubCloud/html/release-notes-dolomite/changelog.html
@@ -0,0 +1,39 @@
+
+ALP 1.0 | Release Notes | Changelog for 6.0
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
\ No newline at end of file
diff --git a/pubCloud/html/release-notes-dolomite/index.html b/pubCloud/html/release-notes-dolomite/index.html
new file mode 100644
index 0000000..9e06c9a
--- /dev/null
+++ b/pubCloud/html/release-notes-dolomite/index.html
@@ -0,0 +1,63 @@
+
+ALP 1.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
This document provides an overview of high-level general features, capabilities, and limitations of ALP 1.0 and important product updates.
This product will be released in June 2024.
+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://example.com/.
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.
The default sudoers/root configuration was confusing due to it duplicating the first user’s password for the root account and relied on a unique sudoers setting (Defaults targetpw) that asked for the root’s password instead of the user’s for sudo commands.
+This approach was uncommon and surprising compared to other distributions that either did not set a root password or set a separate one and used the user’s password for sudo, aligning with most users' expectations.
This has been changed and by default targetpw is not used.
ALP 1.0 uses cgroup v2 by default and v1 is unsupported.
+If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/pubCloud/html/release-notes-micro/index.html b/pubCloud/html/release-notes-micro/index.html
new file mode 100644
index 0000000..6353c6d
--- /dev/null
+++ b/pubCloud/html/release-notes-micro/index.html
@@ -0,0 +1,108 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
5 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.4 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/pubCloud/single-html/release-notes-all/release-notes-all_draft.html b/pubCloud/single-html/release-notes-all/release-notes-all_draft.html
new file mode 100644
index 0000000..c81db21
--- /dev/null
+++ b/pubCloud/single-html/release-notes-all/release-notes-all_draft.html
@@ -0,0 +1,99 @@
+
+ALP Release Notes
+
+
+
+
+
+
+
+
+
+
+
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.4 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/pubCloud/single-html/release-notes-dolomite/index.html b/pubCloud/single-html/release-notes-dolomite/index.html
new file mode 100644
index 0000000..d0ae3d9
--- /dev/null
+++ b/pubCloud/single-html/release-notes-dolomite/index.html
@@ -0,0 +1,63 @@
+
+ALP 1.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
This document provides an overview of high-level general features, capabilities, and limitations of ALP 1.0 and important product updates.
This product will be released in June 2024.
+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://example.com/.
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.
The default sudoers/root configuration was confusing due to it duplicating the first user’s password for the root account and relied on a unique sudoers setting (Defaults targetpw) that asked for the root’s password instead of the user’s for sudo commands.
+This approach was uncommon and surprising compared to other distributions that either did not set a root password or set a separate one and used the user’s password for sudo, aligning with most users' expectations.
This has been changed and by default targetpw is not used.
ALP 1.0 uses cgroup v2 by default and v1 is unsupported.
+If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/pubCloud/single-html/release-notes-dolomite/release-notes-dolomite_draft.html b/pubCloud/single-html/release-notes-dolomite/release-notes-dolomite_draft.html
new file mode 100644
index 0000000..d0ae3d9
--- /dev/null
+++ b/pubCloud/single-html/release-notes-dolomite/release-notes-dolomite_draft.html
@@ -0,0 +1,63 @@
+
+ALP 1.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
This document provides an overview of high-level general features, capabilities, and limitations of ALP 1.0 and important product updates.
This product will be released in June 2024.
+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://example.com/.
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.
The default sudoers/root configuration was confusing due to it duplicating the first user’s password for the root account and relied on a unique sudoers setting (Defaults targetpw) that asked for the root’s password instead of the user’s for sudo commands.
+This approach was uncommon and surprising compared to other distributions that either did not set a root password or set a separate one and used the user’s password for sudo, aligning with most users' expectations.
This has been changed and by default targetpw is not used.
ALP 1.0 uses cgroup v2 by default and v1 is unsupported.
+If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/pubCloud/single-html/release-notes-micro/index.html b/pubCloud/single-html/release-notes-micro/index.html
new file mode 100644
index 0000000..92a8f2f
--- /dev/null
+++ b/pubCloud/single-html/release-notes-micro/index.html
@@ -0,0 +1,108 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
5 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/pubCloud/single-html/release-notes-micro/release-notes-micro_draft.html b/pubCloud/single-html/release-notes-micro/release-notes-micro_draft.html
new file mode 100644
index 0000000..92a8f2f
--- /dev/null
+++ b/pubCloud/single-html/release-notes-micro/release-notes-micro_draft.html
@@ -0,0 +1,108 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
5 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/refs,pull,4,merge/html/release-notes-all/index.html b/refs,pull,4,merge/html/release-notes-all/index.html
new file mode 100644
index 0000000..d44a60e
--- /dev/null
+++ b/refs,pull,4,merge/html/release-notes-all/index.html
@@ -0,0 +1,99 @@
+
+ALP Release Notes
+
+
+
+
+
+
+
+
+
+
+
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.4 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/refs,pull,4,merge/html/release-notes-dolomite/changelog.html b/refs,pull,4,merge/html/release-notes-dolomite/changelog.html
new file mode 100644
index 0000000..f8fa19c
--- /dev/null
+++ b/refs,pull,4,merge/html/release-notes-dolomite/changelog.html
@@ -0,0 +1,39 @@
+
+ALP 1.0 | Release Notes | Changelog for 6.0
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
\ No newline at end of file
diff --git a/refs,pull,4,merge/html/release-notes-dolomite/index.html b/refs,pull,4,merge/html/release-notes-dolomite/index.html
new file mode 100644
index 0000000..9e06c9a
--- /dev/null
+++ b/refs,pull,4,merge/html/release-notes-dolomite/index.html
@@ -0,0 +1,63 @@
+
+ALP 1.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
This document provides an overview of high-level general features, capabilities, and limitations of ALP 1.0 and important product updates.
This product will be released in June 2024.
+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://example.com/.
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.
The default sudoers/root configuration was confusing due to it duplicating the first user’s password for the root account and relied on a unique sudoers setting (Defaults targetpw) that asked for the root’s password instead of the user’s for sudo commands.
+This approach was uncommon and surprising compared to other distributions that either did not set a root password or set a separate one and used the user’s password for sudo, aligning with most users' expectations.
This has been changed and by default targetpw is not used.
ALP 1.0 uses cgroup v2 by default and v1 is unsupported.
+If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/refs,pull,4,merge/html/release-notes-micro/index.html b/refs,pull,4,merge/html/release-notes-micro/index.html
new file mode 100644
index 0000000..6353c6d
--- /dev/null
+++ b/refs,pull,4,merge/html/release-notes-micro/index.html
@@ -0,0 +1,108 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
5 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.4 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/refs,pull,4,merge/single-html/release-notes-all/release-notes-all_draft.html b/refs,pull,4,merge/single-html/release-notes-all/release-notes-all_draft.html
new file mode 100644
index 0000000..c81db21
--- /dev/null
+++ b/refs,pull,4,merge/single-html/release-notes-all/release-notes-all_draft.html
@@ -0,0 +1,99 @@
+
+ALP Release Notes
+
+
+
+
+
+
+
+
+
+
+
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.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory 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.rpm is the name of the RPM):
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
2.2.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.4 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/refs,pull,4,merge/single-html/release-notes-dolomite/index.html b/refs,pull,4,merge/single-html/release-notes-dolomite/index.html
new file mode 100644
index 0000000..d0ae3d9
--- /dev/null
+++ b/refs,pull,4,merge/single-html/release-notes-dolomite/index.html
@@ -0,0 +1,63 @@
+
+ALP 1.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
This document provides an overview of high-level general features, capabilities, and limitations of ALP 1.0 and important product updates.
This product will be released in June 2024.
+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://example.com/.
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.
The default sudoers/root configuration was confusing due to it duplicating the first user’s password for the root account and relied on a unique sudoers setting (Defaults targetpw) that asked for the root’s password instead of the user’s for sudo commands.
+This approach was uncommon and surprising compared to other distributions that either did not set a root password or set a separate one and used the user’s password for sudo, aligning with most users' expectations.
This has been changed and by default targetpw is not used.
ALP 1.0 uses cgroup v2 by default and v1 is unsupported.
+If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/refs,pull,4,merge/single-html/release-notes-dolomite/release-notes-dolomite_draft.html b/refs,pull,4,merge/single-html/release-notes-dolomite/release-notes-dolomite_draft.html
new file mode 100644
index 0000000..d0ae3d9
--- /dev/null
+++ b/refs,pull,4,merge/single-html/release-notes-dolomite/release-notes-dolomite_draft.html
@@ -0,0 +1,63 @@
+
+ALP 1.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
This document provides an overview of high-level general features, capabilities, and limitations of ALP 1.0 and important product updates.
This product will be released in June 2024.
+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://example.com/.
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.
The default sudoers/root configuration was confusing due to it duplicating the first user’s password for the root account and relied on a unique sudoers setting (Defaults targetpw) that asked for the root’s password instead of the user’s for sudo commands.
+This approach was uncommon and surprising compared to other distributions that either did not set a root password or set a separate one and used the user’s password for sudo, aligning with most users' expectations.
This has been changed and by default targetpw is not used.
ALP 1.0 uses cgroup v2 by default and v1 is unsupported.
+If you need to use cgroup v1, SLES 15 SP6 can be switched to hybrid mode using a boot parameter.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/refs,pull,4,merge/single-html/release-notes-micro/index.html b/refs,pull,4,merge/single-html/release-notes-micro/index.html
new file mode 100644
index 0000000..92a8f2f
--- /dev/null
+++ b/refs,pull,4,merge/single-html/release-notes-micro/index.html
@@ -0,0 +1,108 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
5 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
\ No newline at end of file
diff --git a/refs,pull,4,merge/single-html/release-notes-micro/release-notes-micro_draft.html b/refs,pull,4,merge/single-html/release-notes-micro/release-notes-micro_draft.html
new file mode 100644
index 0000000..92a8f2f
--- /dev/null
+++ b/refs,pull,4,merge/single-html/release-notes-micro/release-notes-micro_draft.html
@@ -0,0 +1,108 @@
+
+SUSE Linux Enterprise Micro 6.0 | Release Notes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise 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 Enterprise Micro 6.0.
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.
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise Micro 6.0.
+This directory includes PDF versions of the SUSE Linux Enterprise 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):
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.
SUSE Linux Enterprise 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.
An online migration of existing SUSE Linux Enterprise Micro 5.5 installations to SUSE Linux Enterprise Micro 6.0 is possible and is fully supported.
+Upgrading from SUSE Linux Enterprise Micro 5.5 is only possible via the transactional-update tool.
+For the upgrade procedure, refer to https://documentation.suse.com/sle-micro/6.0/html/SLE-Micro-all/book-upgrade-slemicro.html
With previous releases we supported manual installation via a YaST based image.
+With SLE Micro we have dropped support for this installation method and only focus on RAW image based deployments.
+The SelfInstall image variant has been extended to allow setting of various parameters to direct it and also enable an unattended installation using the SelfInstall image.
3.8.1 Unattended installation with Yomi (technology preview)#
To learn how to install a system with Yomi, see the SUSE Manager documentation, section Install using Yomi.
+Installation with Yomi is a technology preview.
SLE Micro is provided as raw images which can be deployed directly to a storage device, for example, a memory card, a USB stick, or a hard drive.
+SLE Micro is also provided as images for specific hardware device with a customized software selection.
SLE Micro is focused on distributed infrastructures/Edge deployments, which means systems running SLE Micro are not necessarily within DCs or secure locations.
+We therefore have improved our security story and added support for full disk encryption (FDE) to SLE
+Micro.
Since SUSE Linux Enterprise Micro is positioned to be used within decentralized infrastructures including Edge use cases and Industrial Edge, a system management based on current YaST2 is not within scope.
+Specifically, for Industrial Edge, a basic web-based system management was required. We have chosen the cockpit project as a base for that.
+Therefore, the cockpit packages are added to the common code base and adjusted for the Immutable OS setup of SUSE Linux Enterprise Micro.
For the Intel/AMD 64bit architecture (x86_64) the real-time (rt) kernel is provided in addition to the default kernel.
+Support for RT includes support for Kernel Live Patching on the RT kernel.
+Note: When using the RT kernel, KVM is not supported, and workloads need to be run within containers
+Containers need special treatment with RT.
With SUSE Linux Enterprise we fully support AppArmor and in addition provide the framework for SELinux – without providing and supporting a policy for SELinux.
+On SUSE Linux Enterprise Micro we do not support AppArmor.
+SUSE Linux Enterprise Micro only supports SELinux and in addition we ship a supported policy.
+On top of that, we will look into providing dedicated SELinux policies for the containers we already provide or support on top of SUSE Linux Enterprise Micro (PCP and Nvidia).
+SUSE Linux Enterprise Micro 6.0 will have SELinux in enforced mode as a default.
Podman 4.x brings a new container network stack based on Netavark, the new container network stack and Aardvark DNS server in addition to the existing container network interface (CNI) stack used by Podman 3.x.
+The new stack brings 3 important improvements:
Better support for containers in multiple networks
Better IPv6 support
Better performance
To ensure that nothing breaks with this major change, the old CNI stack will remain the default on existing installations. Bear in mind that Netavark will be released as part of a maintenance update.
Warning
Before testing Podman 4 and the new network stack, you will have to destroy all your current containers, images, and networks.
+You must export/save any import containers or images on a private registry, or make sure that your Dockerfiles are available for rebuilding and scripts/playbooks/states to reapply any settings, regenerate secrets, etc.
If you have run Podman 3.x before upgrading to Podman 4, Podman will continue to use CNI plugins as it had before.
+To begin using Podman 4 with Netavark, you need to run the command podman system reset.
+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.
With SUSE Linux Enterprise Micro 6.0 legacy BIOS boot support on Intel/AMD 64bit systems (x86_64) is deprecated and will be removed with a later release.
SUSE Linux Enterprise Micro 6.0 provides support for LTTng (Linux Trace Toolkit: next generation). Support for LTTng will however be removed in a later SUSE Linux Enterprise Micro version in favor of alternative solutions for tracing like bpftrace.
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 Enterprise Micro with SUSE Manager#
SUSE Manager can be used to manage SUSE Linux Enterprise Micro hosts. There are certain limitations:
SUSE Linux Enterprise 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 Enterprise Micro hosts only with the Salt stack; the traditional stack is not supported
Ansible control node cannot be installed on SUSE Linux Enterprise Micro
We intend to resolve these issues in the future maintenance updates of SUSE Linux Enterprise Micro on SUSE Manager.
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.
5 Arm 64-bit-specific features and fixes (AArch64)#
Information in this section applies to SLE Micro 6.0.
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
+with the same SoC chipset.
For booting, systems need to fulfill either the Server Base Boot Requirements (SBBR)
+or the Embedded Base Boot Requirements (EBBR),
+that is, the Unified Extensible Firmware Interface (UEFI) either
+implementing the Advanced Configuration and Power Interface (ACPI) or
+providing a Flat Device Tree (FDT) table. If both are implemented, the kernel
+will default to the Device Tree; the kernel command line argument acpi=force can
+override this default behavior.
Check for SUSE YES! certified systems,
+which have undergone compatibility testing.
SLE Micro 5.5 added initial enablement for the
+NVIDIA Orin* SoC (T234), which is found on Jetson* AGX Orin,
+Jetson Orin NX and Jetson Orin Nano System-on-Modules (SoM)
+as well as NVIDIA IGX Orin based systems.
NVIDIA JetPack* 6.0 boot firmware and Linux kernel 6.5
+changed the Application Binary Interface (ABI)
+for numbering General Purpose Input/Output (GPIO) pins — specifically the main GPIO ports X, Y, Z, AC, AD, AE, AF and AG — referenced in the machine-specific vendor Device Tree (DT) binary
+for NVIDIA Orin based systems.
SLE Micro 6.0 adopts the behavior of the latest kernels
+and requires NVIDIA JetPack 6.0 or later boot firmware to be flashed
+on any NVIDIA Orin based platforms.
Refer to your system vendor’s documentation for how to enter Recovery Mode and
+to flash the boot firmware.
+For example: sudo ./flash.sh device-identifier-and-boot-medium external
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-micro/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
+
+ */
+ console.groupCollapsed(`addBugLinks ${index}`);
+ var url = "";
+ var icons = this.getElementsByClassName("icons")[0];
+ var icon_reportbug = icons.getElementsByClassName("icon-reportbug")[0];
+ var permalink = this.getElementsByClassName("permalink")[0];
+ var title_number_name = this.getElementsByClassName("title-number-name")[0];
+ var firsttitle = this.getElementsByClassName("title")[0];
+
+ if (permalink == undefined) {
+ // If permalink is not available, use the global URL
+ permalink = document.createElement("span");
+ permalink.setAttribute("href", window.location.href)
+ permalink.textContent = "#";
+ }
+
+ console.log("title-number-name:", title_number_name,
+ "\npermalink:", permalink.href,
+ "\ntitle-number:",
+ // We need to check first as titles can have no div
+ // with "title-number-name" class
+ title_number_name != undefined ? title_number_name.getElementsByClassName("title-number")[0] : "n/a",
+ );
+
+ // Create empty element
+ var sectionName = document.createElement("span");
+
+ if (title_number_name != undefined) {
+ sectionName = title_number_name.getElementsByClassName("title-name")[0];
+ }
+ else if (firsttitle != undefined) {
+ sectionName = firsttitle;
+ }
+
+ if (bugtrackerType == 'bsc') {
+ url = bugzillaUrl(sectionName.innerText, permalink.href);
+ }
+ else {
+ url = githubUrl(sectionName.innerText, permalink.href);
+ }
+
+ if (icon_reportbug != undefined) {
+ icon_reportbug.setAttribute("href", url);
+ }
+
+ console.groupEnd();
+ return true;
+ });
+
+}
diff --git a/sle-ha-15_SP4/html/release-notes/index.html b/sle-ha-15_SP4/html/release-notes/index.html
new file mode 120000
index 0000000..43e2831
--- /dev/null
+++ b/sle-ha-15_SP4/html/release-notes/index.html
@@ -0,0 +1 @@
+release-notes.html
\ No newline at end of file
diff --git a/sle-ha-15_SP4/html/release-notes/release-notes.html b/sle-ha-15_SP4/html/release-notes/release-notes.html
new file mode 100644
index 0000000..eadbd01
--- /dev/null
+++ b/sle-ha-15_SP4/html/release-notes/release-notes.html
@@ -0,0 +1,105 @@
+
+Release Notes | SUSE Linux Enterprise High Availability Extension 15 SP4
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise High Availability Extension is an enterprise-level clustering solution to implement highly available Linux clusters and eliminate single points of failure. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Enterprise High Availability Extension 15 SP4, and highlights important product updates.
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.
2 SUSE Linux Enterprise High Availability Extension#
SUSE Linux Enterprise High Availability Extension 15 SP4 is an industry-leading open source high availability clustering system.
+It is designed to virtually eliminate unplanned downtime, be easy to use and be deployed in both physical and virtual environments.
+Also included are geo clustering capabilities, designed to manage cluster servers in data centers anywhere in the world.
+High availability clustering helps to minimize data loss due to corruption or failure by protecting your data assets using your existing IT infrastructure.
High availability clustering is used to automate application and data recovery.
+You can use our flexible, policy-driven clustering solution to implement highly available Linux clusters and eliminate single points of failure.
+Your servers are continuously monitored, and when a fault or failure occurs, the workload is transferred from one server to another, or the application is automatically restarted on a known working system.
+This helps you maintain business continuity and minimize unplanned downtime.
SUSE Linux Enterprise High Availability Extension 15 introduces many innovative changes compared to SUSE Linux Enterprise High Availability Extension 12.
+The most important changes are listed below.
SUSE Linux Enterprise High Availability Extension 15 SP4 introduces changes compared to SUSE Linux Enterprise High Availability Extension SP3.
+The most important changes are listed below.
In addition to these release notes, make sure to also review the release notes for the base product, SUSE Linux Enterprise Server 15 SP4.
+They are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP4 (these release notes are identical across all supported hardware architectures).
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise High Availability Extension 15 SP4.
+This directory includes PDF versions of the SUSE Linux Enterprise High Availability Extension 15 SP4 Installation Quick Start Guide.
For the most up-to-date version of the documentation for SUSE Linux Enterprise High Availability Extension 15 SP4, see https://documentation.suse.com/sle-ha-15.
SUSE Linux Enterprise High Availability Extension is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.
SUSE Linux Enterprise High Availability Extension 15 has a 13-year life cycle, with 10 years of General Support and 3 years of Extended Support.
+The current version (SP4) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise High Availability Extension 15 SP4.
If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support duration.
+You can buy an additional 12 to 36 months in twelve month increments.
+This means, you receive a total of 3 to 5 years of support per Service Pack.
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
L2
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
L3
Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.
For contracted customers and partners, SUSE Linux Enterprise High Availability Extension is delivered with L3 support for all packages, except for the following:
Some packages shipped as part of the module Workstation Extension are L2-supported only
Packages with names ending in -devel (containing header files and similar developer resources) will only be supported together with their main packages.
SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.
Certain software delivered as part of SUSE Linux Enterprise High Availability Extension may require an external contract.
+Check the support status of individual packages using the RPM metadata that can be viewed with rpm, zypper, or YaST.
Major packages and groups of packages affected by this are:
PostgreSQL (all versions, including all subpackages)
SUSE Linux Enterprise High Availability Extension 15 SP4 (and the SUSE Linux Enterprise modules) includes the following software that is shipped only under a GNU AGPL software license:
Ghostscript (including subpackages)
SUSE Linux Enterprise High Availability Extension 15 SP4 (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:
Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations.
+Technology previews are included for your convenience to give you a chance to test new technologies within your environment.
+We would appreciate your feedback!
+If you test a technology preview, contact your SUSE representative and let them know about your experience and use cases.
+Your input is helpful for future development.
Technology previews come with the following limitations:
Technology previews are still in development.
+Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.
Technology previews are not supported.
Technology previews may only be available for specific hardware architectures.
+Details and functionality of technology previews are subject to change.
+As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.
Technology previews can be removed from a product at any time.
+This may be the case, for example, if SUSE discovers that a preview does not meet the customer or market needs, or does not comply with enterprise standards.
This section comprises information about modules and extensions for SUSE Linux Enterprise High Availability Extension 15 SP4. Modules and extensions add parts or functionality to the system.
The SLE 15 SP4 product line is made up of modules that contain software packages.
+Each module has a clearly defined scope.
+Modules differ in their life cycles and update timelines.
Not all SLE modules are available with a subscription for SUSE Linux Enterprise High Availability Extension 15 SP4 itself (see the column Available for).
Extensions add extra functionality to the system and require their own registration key, usually at additional cost.
+Usually, extensions have their own release notes documents that are available from https://www.suse.com/releasenotes.
The following extensions are available for SUSE Linux Enterprise High Availability Extension 15 SP4:
Additionally, there is the following extension which is not covered by SUSE support agreements, available at no additional cost and without an extra registration key:
This sections lists derived and related products.
+Usually, these products have their own release notes documents that are available from https://www.suse.com/releasenotes.
This section includes information related to the initial installation of SUSE Linux Enterprise High Availability Extension 15 SP4.
+Make sure to also review the respective section of the release notes for the base product, SUSE Linux Enterprise Server 15 SP4 which are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP4.
Important: Installation Documentation
The following release notes contain additional notes regarding the installation of SUSE Linux Enterprise High Availability Extension.
+However, they do not document the installation procedure itself.
This section includes upgrade-related information for SUSE Linux Enterprise High Availability Extension 15 SP4.
+Make sure to also review the respective section of the release notes for the base product, SUSE Linux Enterprise Server 15 SP4 which are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP4.
Important: Upgrade Documentation
The following release notes contain additional notes regarding the upgrade of SUSE Linux Enterprise High Availability Extension.
+However, they do not document the upgrade procedure itself.
5.2.1 Make Sure the Current System Is Up-To-Date Before Upgrading#
Upgrading the system is only supported from the most recent patch level.
+Make sure the latest system updates are installed by either running zypper patch or by starting the YaST module Online-Update.
+An upgrade on a system not fully patched may fail.
Skipping service packs during an upgrade is only supported if you have a Long Term Service Pack Support contract.
+Otherwise you first need to upgrade to SP3 before upgrading to SP4.
This section lists cluster-related information for SUSE Linux Enterprise High Availability Extension 15 SP4.
6.1 Improve the graceful shutdown for the whole cluster#
There are several common use cases that might not result in a graceful shutdown of the whole cluster:
When a user takes down the cluster nodes one by one a diskless-sbd cluster, the nodes get fenced unexpectedly once the cluster is inquorate.
In the dlm cluster, with the highly suggested configuration no-quorum-policy=freeze, the cluster shutdown will hang once the cluster is inquorate.
+A new option set_config of dlm_tools is expected to help this situation.
To shutdown the normal cluster, the system admin often takes down the cluster nodes one by one.
+This might create unnecessary the resources migration chaos among nodes.
To help with some of these, a new --all options has been added to crmsh.
+The --all option tries to simplify the procedure and to make it more smoothly and reliable.
Warning
The --all option alone does not guarantee a graceful shutdown because the unforeseeable resource stop-failure might happen at the application level, which is out of the scope of the --all option.
+This means that users may need to take additional steps to match their product expectation.
Until now it was possible only to by bring up the whole OCFS2 cluster stack.
In SUSE Linux Enterprise HA 15 SP4, the nocluster mount option has been added.
+This, for example, allows to access a OCFS2 file system on a standalone server where it is not necessary to have a fully functional cluster stack.
This section lists features and packages that got removed from SUSE Linux Enterprise High Availability Extension or
+will be removed in upcoming versions.
The following features and packages had been deprecated with a previous release and have been removed with SUSE Linux Enterprise High Availability Extension 15 SP4.
pssh has been removed. Use crm cluster run instead.
The following features and packages are deprecated and will be removed with a future service pack of SUSE Linux Enterprise High Availability Extension.
8.2.1 `ha-cluster-* commands have been deprecated#
The implementation has been moved to crmsh:
ha-cluster-init is now crm cluster init
ha-cluster-remove is now crm cluster remove
ha-cluster-join is now crm cluster join
ha-cluster-geo-init is now crm cluster geo-init
ha-cluster-geo-join is now crm cluster geo-join
ha-cluster-geo-init-arbitrator is now crm cluster geo-init-arbitrator
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-ha/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
a",n=d.getElementsByTagName("*")||[],r=d.getElementsByTagName("a")[0],!r||!r.style||!n.length)return t;s=a.createElement("select"),u=s.appendChild(a.createElement("option")),o=d.getElementsByTagName("input")[0],r.style.cssText="top:1px;float:left;opacity:.5",t.getSetAttribute="t"!==d.className,t.leadingWhitespace=3===d.firstChild.nodeType,t.tbody=!d.getElementsByTagName("tbody").length,t.htmlSerialize=!!d.getElementsByTagName("link").length,t.style=/top/.test(r.getAttribute("style")),t.hrefNormalized="/a"===r.getAttribute("href"),t.opacity=/^0.5/.test(r.style.opacity),t.cssFloat=!!r.style.cssFloat,t.checkOn=!!o.value,t.optSelected=u.selected,t.enctype=!!a.createElement("form").enctype,t.html5Clone="<:nav>"!==a.createElement("nav").cloneNode(!0).outerHTML,t.inlineBlockNeedsLayout=!1,t.shrinkWrapBlocks=!1,t.pixelPosition=!1,t.deleteExpando=!0,t.noCloneEvent=!0,t.reliableMarginRight=!0,t.boxSizingReliable=!0,o.checked=!0,t.noCloneChecked=o.cloneNode(!0).checked,s.disabled=!0,t.optDisabled=!u.disabled;try{delete d.test}catch(h){t.deleteExpando=!1}o=a.createElement("input"),o.setAttribute("value",""),t.input=""===o.getAttribute("value"),o.value="t",o.setAttribute("type","radio"),t.radioValue="t"===o.value,o.setAttribute("checked","t"),o.setAttribute("name","t"),l=a.createDocumentFragment(),l.appendChild(o),t.appendChecked=o.checked,t.checkClone=l.cloneNode(!0).cloneNode(!0).lastChild.checked,d.attachEvent&&(d.attachEvent("onclick",function(){t.noCloneEvent=!1}),d.cloneNode(!0).click());for(f in{submit:!0,change:!0,focusin:!0})d.setAttribute(c="on"+f,"t"),t[f+"Bubbles"]=c in e||d.attributes[c].expando===!1;d.style.backgroundClip="content-box",d.cloneNode(!0).style.backgroundClip="",t.clearCloneStyle="content-box"===d.style.backgroundClip;for(f in x(t))break;return t.ownLast="0"!==f,x(function(){var n,r,o,s="padding:0;margin:0;border:0;display:block;box-sizing:content-box;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;",l=a.getElementsByTagName("body")[0];l&&(n=a.createElement("div"),n.style.cssText="border:0;width:0;height:0;position:absolute;top:0;left:-9999px;margin-top:1px",l.appendChild(n).appendChild(d),d.innerHTML="
diff --git a/sle-ha-15_SP5/html/release-notes/index.html b/sle-ha-15_SP5/html/release-notes/index.html
new file mode 120000
index 0000000..43e2831
--- /dev/null
+++ b/sle-ha-15_SP5/html/release-notes/index.html
@@ -0,0 +1 @@
+release-notes.html
\ No newline at end of file
diff --git a/sle-ha-15_SP5/html/release-notes/release-notes.html b/sle-ha-15_SP5/html/release-notes/release-notes.html
new file mode 100644
index 0000000..f6a66b1
--- /dev/null
+++ b/sle-ha-15_SP5/html/release-notes/release-notes.html
@@ -0,0 +1,106 @@
+
+Release Notes | SUSE Linux Enterprise High Availability 15 SP5 (prerelease)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise High Availability is an enterprise-level clustering solution to implement highly available Linux clusters and eliminate single points of failure. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Enterprise High Availability 15 SP5 (prerelease), and highlights important product updates.
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.
SUSE Linux Enterprise High Availability 15 SP5 (prerelease) is an industry-leading open source high availability clustering system.
+It is designed to virtually eliminate unplanned downtime, be easy to use and be deployed in both physical and virtual environments.
+Also included are geo clustering capabilities, designed to manage cluster servers in data centers anywhere in the world.
+High availability clustering helps to minimize data loss due to corruption or failure by protecting your data assets using your existing IT infrastructure.
High availability clustering is used to automate application and data recovery.
+You can use our flexible, policy-driven clustering solution to implement highly available Linux clusters and eliminate single points of failure.
+Your servers are continuously monitored, and when a fault or failure occurs, the workload is transferred from one server to another, or the application is automatically restarted on a known working system.
+This helps you maintain business continuity and minimize unplanned downtime.
SUSE Linux Enterprise High Availability 15 introduces many innovative changes compared to SUSE Linux Enterprise High Availability 12.
+The most important changes are listed below.
SUSE Linux Enterprise High Availability 15 SP5 (prerelease) introduces changes compared to SUSE Linux Enterprise High Availability SP4.
+The most important changes are listed below.
In addition to these release notes, make sure to also review the release notes for the base product, SUSE Linux Enterprise Server 15 SP5 (prerelease).
+They are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP5 (these release notes are identical across all supported hardware architectures).
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise High Availability 15 SP5 (prerelease).
+This directory includes PDF versions of the SUSE Linux Enterprise High Availability 15 SP5 (prerelease) Installation Quick Start Guide.
For the most up-to-date version of the documentation for SUSE Linux Enterprise High Availability 15 SP5 (prerelease), see https://susedoc.github.io/doc-sleha/main (draft version).
SUSE Linux Enterprise High Availability is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.
SUSE Linux Enterprise High Availability 15 has a 13-year life cycle, with 10 years of General Support and 3 years of Extended Support.
+The current version (SP5) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise High Availability 15 SP6.
If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support duration.
+You can buy an additional 12 to 36 months in twelve month increments.
+This means, you receive a total of 3 to 5 years of support per Service Pack.
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
L2
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
L3
Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.
For contracted customers and partners, SUSE Linux Enterprise High Availability is delivered with L3 support for all packages, except for the following:
Some packages shipped as part of the module Workstation Extension are L2-supported only
Packages with names ending in -devel (containing header files and similar developer resources) will only be supported together with their main packages.
SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.
Certain software delivered as part of SUSE Linux Enterprise High Availability may require an external contract.
+Check the support status of individual packages using the RPM metadata that can be viewed with rpm, zypper, or YaST.
Major packages and groups of packages affected by this are:
PostgreSQL (all versions, including all subpackages)
SUSE Linux Enterprise High Availability 15 SP5 (prerelease) (and the SUSE Linux Enterprise modules) includes the following software that is shipped only under a GNU AGPL software license:
Ghostscript (including subpackages)
SUSE Linux Enterprise High Availability 15 SP5 (prerelease) (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:
Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations.
+Technology previews are included for your convenience to give you a chance to test new technologies within your environment.
+We would appreciate your feedback!
+If you test a technology preview, contact your SUSE representative and let them know about your experience and use cases.
+Your input is helpful for future development.
Technology previews come with the following limitations:
Technology previews are still in development.
+Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.
Technology previews are not supported.
Technology previews may only be available for specific hardware architectures.
+Details and functionality of technology previews are subject to change.
+As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.
Technology previews can be removed from a product at any time.
+This may be the case, for example, if SUSE discovers that a preview does not meet the customer or market needs, or does not comply with enterprise standards.
This section comprises information about modules and extensions for SUSE Linux Enterprise High Availability 15 SP5 (prerelease). Modules and extensions add parts or functionality to the system.
3.1 Modules in the SLE 15 SP5 (prerelease) Product Line#
The SLE 15 SP5 (prerelease) product line is made up of modules that contain software packages.
+Each module has a clearly defined scope.
+Modules differ in their life cycles and update timelines.
The modules available within the product line based on SUSE Linux Enterprise 15 SP5 (prerelease) at the release of SUSE Linux Enterprise High Availability 15 SP5 (prerelease) are listed in the Modules and Extensions Quick Start at https://susedoc.github.io/doc-sle/main/html/SLES-modulesquick/ (draft version).
Not all SLE modules are available with a subscription for SUSE Linux Enterprise High Availability 15 SP5 (prerelease) itself (see the column Available for).
Extensions add extra functionality to the system and require their own registration key, usually at additional cost.
+Usually, extensions have their own release notes documents that are available from https://www.suse.com/releasenotes.
The following extensions are available for SUSE Linux Enterprise High Availability 15 SP5 (prerelease):
Additionally, there is the following extension which is not covered by SUSE support agreements, available at no additional cost and without an extra registration key:
This sections lists derived and related products.
+Usually, these products have their own release notes documents that are available from https://www.suse.com/releasenotes.
This section includes information related to the initial installation of SUSE Linux Enterprise High Availability 15 SP5 (prerelease).
+Make sure to also review the respective section of the release notes for the base product, SUSE Linux Enterprise Server 15 SP5 (prerelease) which are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP5.
Important: Installation Documentation
The following release notes contain additional notes regarding the installation of SUSE Linux Enterprise High Availability.
+However, they do not document the installation procedure itself.
This section includes upgrade-related information for SUSE Linux Enterprise High Availability 15 SP5 (prerelease).
+Make sure to also review the respective section of the release notes for the base product, SUSE Linux Enterprise Server 15 SP5 (prerelease) which are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP5.
Important: Upgrade Documentation
The following release notes contain additional notes regarding the upgrade of SUSE Linux Enterprise High Availability.
+However, they do not document the upgrade procedure itself.
5.2.1 Make Sure the Current System Is Up-To-Date Before Upgrading#
Upgrading the system is only supported from the most recent patch level.
+Make sure the latest system updates are installed by either running zypper patch or by starting the YaST module Online-Update.
+An upgrade on a system not fully patched may fail.
Skipping service packs during an upgrade is only supported if you have a Long Term Service Pack Support contract.
+Otherwise you first need to upgrade to SP4 before upgrading to SP5.
This section lists cluster-related information for SUSE Linux Enterprise High Availability 15 SP5 (prerelease).
6.1 Improve the graceful shutdown for the whole cluster#
There are several common use cases that might not result in a graceful shutdown of the whole cluster:
When a user takes down the cluster nodes one by one a diskless-sbd cluster, the nodes get fenced unexpectedly once the cluster is inquorate.
In the dlm cluster, with the highly suggested configuration no-quorum-policy=freeze, the cluster shutdown will hang once the cluster is inquorate.
+A new option set_config of dlm_tools is expected to help this situation.
To shutdown the normal cluster, the system admin often takes down the cluster nodes one by one.
+This might create unnecessary the resources migration chaos among nodes.
To help with some of these, a new --all options has been added to crmsh.
+The --all option tries to simplify the procedure and to make it more smoothly and reliable.
Warning
The --all option alone does not guarantee a graceful shutdown because the unforeseeable resource stop-failure might happen at the application level, which is out of the scope of the --all option.
+This means that users may need to take additional steps to match their product expectation.
Until now it was possible only to by bring up the whole OCFS2 cluster stack.
In SUSE Linux Enterprise HA 15 SP5 (prerelease), the nocluster mount option has been added.
+This, for example, allows to access a OCFS2 file system on a standalone server where it is not necessary to have a fully functional cluster stack.
Do not upgrade ReaR or change the software used by ReaR without also checking that your existing disaster recovery procedure still works.
+See also the SUSE support for Relax-and-Recover and Version upgrades with Relax-and-Recover sections in https://en.opensuse.org/SDB:Disaster_Recovery.
In SUSE Linux Enterprise HA 15 SP5 (prerelease), the online defragmenter for the OCFS2 (Oracle Cluster Filesystem 2) filesystem, called defragfs.ocfs2, has been enabled.
The following features and packages had been deprecated with a previous release and have been removed with SUSE Linux Enterprise High Availability 15 SP5 (prerelease).
pssh has been removed. Use crm cluster run instead.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-ha/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
diff --git a/sle-ha-15_SP6/html/release-notes/index.html b/sle-ha-15_SP6/html/release-notes/index.html
new file mode 120000
index 0000000..43e2831
--- /dev/null
+++ b/sle-ha-15_SP6/html/release-notes/index.html
@@ -0,0 +1 @@
+release-notes.html
\ No newline at end of file
diff --git a/sle-ha-15_SP6/html/release-notes/release-notes.html b/sle-ha-15_SP6/html/release-notes/release-notes.html
new file mode 100644
index 0000000..41238a9
--- /dev/null
+++ b/sle-ha-15_SP6/html/release-notes/release-notes.html
@@ -0,0 +1,106 @@
+
+Release Notes | SUSE Linux Enterprise High Availability 15 SP6 (prerelease)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise High Availability is an enterprise-level clustering solution to implement highly available Linux clusters and eliminate single points of failure. This document provides a high-level overview of features, capabilities, and limitations of SUSE Linux Enterprise High Availability 15 SP6 (prerelease), and highlights important product updates.
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.
SUSE Linux Enterprise High Availability 15 SP6 (prerelease) is an industry-leading open source high availability clustering system.
+It is designed to virtually eliminate unplanned downtime, be easy to use and be deployed in both physical and virtual environments.
+Also included are geo clustering capabilities, designed to manage cluster servers in data centers anywhere in the world.
+High availability clustering helps to minimize data loss due to corruption or failure by protecting your data assets using your existing IT infrastructure.
High availability clustering is used to automate application and data recovery.
+You can use our flexible, policy-driven clustering solution to implement highly available Linux clusters and eliminate single points of failure.
+Your servers are continuously monitored, and when a fault or failure occurs, the workload is transferred from one server to another, or the application is automatically restarted on a known working system.
+This helps you maintain business continuity and minimize unplanned downtime.
SUSE Linux Enterprise High Availability 15 introduces many innovative changes compared to SUSE Linux Enterprise High Availability 12.
+The most important changes are listed below.
SUSE Linux Enterprise High Availability 15 SP6 (prerelease) introduces changes compared to SUSE Linux Enterprise High Availability SP5.
+The most important changes are listed below.
In addition to these release notes, make sure to also review the release notes for the base product, SUSE Linux Enterprise Server 15 SP6 (prerelease).
+They are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP6 (these release notes are identical across all supported hardware architectures).
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise High Availability 15 SP6 (prerelease).
+This directory includes PDF versions of the SUSE Linux Enterprise High Availability 15 SP6 (prerelease) Installation Quick Start Guide.
For the most up-to-date version of the documentation for SUSE Linux Enterprise High Availability 15 SP6 (prerelease), see https://susedoc.github.io/doc-sleha/main (draft version).
SUSE Linux Enterprise High Availability is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.
SUSE Linux Enterprise High Availability 15 has a 13-year life cycle, with 10 years of General Support and 3 years of Extended Support.
+The current version (SP6) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise High Availability 15 SP7.
If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support duration.
+You can buy an additional 12 to 36 months in twelve month increments.
+This means, you receive a total of 3 to 5 years of support per Service Pack.
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
L2
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
L3
Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.
For contracted customers and partners, SUSE Linux Enterprise High Availability is delivered with L3 support for all packages, except for the following:
Some packages shipped as part of the module Workstation Extension are L2-supported only
Packages with names ending in -devel (containing header files and similar developer resources) will only be supported together with their main packages.
SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.
Certain software delivered as part of SUSE Linux Enterprise High Availability may require an external contract.
+Check the support status of individual packages using the RPM metadata that can be viewed with rpm, zypper, or YaST.
Major packages and groups of packages affected by this are:
PostgreSQL (all versions, including all subpackages)
SUSE Linux Enterprise High Availability 15 SP6 (prerelease) (and the SUSE Linux Enterprise modules) includes the following software that is shipped only under a GNU AGPL software license:
Ghostscript (including subpackages)
SUSE Linux Enterprise High Availability 15 SP6 (prerelease) (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:
Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations.
+Technology previews are included for your convenience to give you a chance to test new technologies within your environment.
+We would appreciate your feedback!
+If you test a technology preview, contact your SUSE representative and let them know about your experience and use cases.
+Your input is helpful for future development.
Technology previews come with the following limitations:
Technology previews are still in development.
+Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.
Technology previews are not supported.
Technology previews may only be available for specific hardware architectures.
+Details and functionality of technology previews are subject to change.
+As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.
Technology previews can be removed from a product at any time.
+This may be the case, for example, if SUSE discovers that a preview does not meet the customer or market needs, or does not comply with enterprise standards.
This section comprises information about modules and extensions for SUSE Linux Enterprise High Availability 15 SP6 (prerelease). Modules and extensions add parts or functionality to the system.
3.1 Modules in the SLE 15 SP6 (prerelease) Product Line#
The SLE 15 SP6 (prerelease) product line is made up of modules that contain software packages.
+Each module has a clearly defined scope.
+Modules differ in their life cycles and update timelines.
The modules available within the product line based on SUSE Linux Enterprise 15 SP6 (prerelease) at the release of SUSE Linux Enterprise High Availability 15 SP6 (prerelease) are listed in the Modules and Extensions Quick Start at https://susedoc.github.io/doc-sle/main/html/SLES-modulesquick/ (draft version).
Not all SLE modules are available with a subscription for SUSE Linux Enterprise High Availability 15 SP6 (prerelease) itself (see the column Available for).
Extensions add extra functionality to the system and require their own registration key, usually at additional cost.
+Usually, extensions have their own release notes documents that are available from https://www.suse.com/releasenotes.
The following extensions are available for SUSE Linux Enterprise High Availability 15 SP6 (prerelease):
Additionally, there is the following extension which is not covered by SUSE support agreements, available at no additional cost and without an extra registration key:
This sections lists derived and related products.
+Usually, these products have their own release notes documents that are available from https://www.suse.com/releasenotes.
This section includes information related to the initial installation of SUSE Linux Enterprise High Availability 15 SP6 (prerelease).
+Make sure to also review the respective section of the release notes for the base product, SUSE Linux Enterprise Server 15 SP6 (prerelease) which are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP6.
Important: Installation Documentation
The following release notes contain additional notes regarding the installation of SUSE Linux Enterprise High Availability.
+However, they do not document the installation procedure itself.
This section includes upgrade-related information for SUSE Linux Enterprise High Availability 15 SP6 (prerelease).
+Make sure to also review the respective section of the release notes for the base product, SUSE Linux Enterprise Server 15 SP6 (prerelease) which are published at https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP6.
Important: Upgrade Documentation
The following release notes contain additional notes regarding the upgrade of SUSE Linux Enterprise High Availability.
+However, they do not document the upgrade procedure itself.
5.2.1 Make Sure the Current System Is Up-To-Date Before Upgrading#
Upgrading the system is only supported from the most recent patch level.
+Make sure the latest system updates are installed by either running zypper patch or by starting the YaST module Online-Update.
+An upgrade on a system not fully patched may fail.
Skipping service packs during an upgrade is only supported if you have a Long Term Service Pack Support contract.
+Otherwise you first need to upgrade to SP5 before upgrading to SP6.
This section lists cluster-related information for SUSE Linux Enterprise High Availability 15 SP6 (prerelease).
6.1 Improve the graceful shutdown for the whole cluster#
There are several common use cases that might not result in a graceful shutdown of the whole cluster:
When a user takes down the cluster nodes one by one a diskless-sbd cluster, the nodes get fenced unexpectedly once the cluster is inquorate.
In the dlm cluster, with the highly suggested configuration no-quorum-policy=freeze, the cluster shutdown will hang once the cluster is inquorate.
+A new option set_config of dlm_tools is expected to help this situation.
To shutdown the normal cluster, the system admin often takes down the cluster nodes one by one.
+This might create unnecessary the resources migration chaos among nodes.
To help with some of these, a new --all options has been added to crmsh.
+The --all option tries to simplify the procedure and to make it more smoothly and reliable.
Warning
The --all option alone does not guarantee a graceful shutdown because the unforeseeable resource stop-failure might happen at the application level, which is out of the scope of the --all option.
+This means that users may need to take additional steps to match their product expectation.
Until now it was possible only to by bring up the whole OCFS2 cluster stack.
In SUSE Linux Enterprise HA 15 SP6 (prerelease), the nocluster mount option has been added.
+This, for example, allows to access a OCFS2 file system on a standalone server where it is not necessary to have a fully functional cluster stack.
Do not upgrade ReaR or change the software used by ReaR without also checking that your existing disaster recovery procedure still works.
+See also the SUSE support for Relax-and-Recover and Version upgrades with Relax-and-Recover sections in https://en.opensuse.org/SDB:Disaster_Recovery.
In SUSE Linux Enterprise HA 15 SP6 (prerelease), the online defragmenter for the OCFS2 (Oracle Cluster Filesystem 2) filesystem, called defragfs.ocfs2, has been enabled.
The following features and packages had been deprecated with a previous release and have been removed with SUSE Linux Enterprise High Availability 15 SP6 (prerelease).
pssh has been removed. Use crm cluster run instead.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-ha/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
diff --git a/sle-hpc-15_SP4/html/release-notes/index.html b/sle-hpc-15_SP4/html/release-notes/index.html
new file mode 120000
index 0000000..43e2831
--- /dev/null
+++ b/sle-hpc-15_SP4/html/release-notes/index.html
@@ -0,0 +1 @@
+release-notes.html
\ No newline at end of file
diff --git a/sle-hpc-15_SP4/html/release-notes/release-notes.html b/sle-hpc-15_SP4/html/release-notes/release-notes.html
new file mode 100644
index 0000000..3cf9d90
--- /dev/null
+++ b/sle-hpc-15_SP4/html/release-notes/release-notes.html
@@ -0,0 +1,519 @@
+
+Release Notes | SUSE Linux Enterprise for High-Performance Computing 15 SP4
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise for High-Performance Computing is a highly-scalable, high-performance open-source operating system designed to utilize the power of parallel computing. This document provides an overview of high-level general features, capabilities, and limitations of SUSE Linux Enterprise for High-Performance Computing 15 SP4 and important product updates.
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.
2 SUSE Linux Enterprise for High-Performance Computing#
SUSE Linux Enterprise for High-Performance Computing is a highly scalable, high performance open-source operating system designed to utilize the power of parallel computing for modeling, simulation and advanced analytics workloads.
SUSE Linux Enterprise for High-Performance Computing 15 SP4 provides tools and libraries related to High Performance Computing. This includes:
Workload manager
Remote and parallel shells
Performance monitoring and measuring tools
Serial console monitoring tool
Cluster power management tool
A tool for discovering the machine hardware topology
System monitoring
A tool for monitoring memory errors
A tool for determining the CPU model and its capabilities (x86-64 only)
User-extensible heap manager capable of distinguishing between different kinds of memory (x86-64 only)
Serial and parallel computational libraries providing the common standards BLAS, LAPACK, …
Various MPI implementations
Serial and parallel libraries for the HDF5 file format
SUSE Linux Enterprise for High-Performance Computing is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.
SUSE Linux Enterprise for High-Performance Computing 15 has a 13-year life cycle, with 10 years of General Support and 3 years of Extended Support.
+The current version (SP4) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise for High-Performance Computing 15 SP5.
Any release package is fully maintained and supported until the availability of the next release.
Extended Service Pack Overlay Support (ESPOS) and Long Term Service Pack Support (LTSS) are also available for this product. If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support (LTSS) can extend the support you get by an additional 12 to 36 months in 12-month increments, providing a total of 3 to 5 years of support on any given Service Pack.
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
L2
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
L3
Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.
For contracted customers and partners, SUSE Linux Enterprise for High-Performance Computing is delivered with L3 support for all packages, except for the following:
Certain software delivered as part of SUSE Linux Enterprise for High-Performance Computing may require an external contract.
+Check the support status of individual packages using the RPM metadata that can be viewed with rpm, zypper, or YaST.
SUSE Linux Enterprise for High-Performance Computing 15 SP4 (and the SUSE Linux Enterprise modules) includes the following software that is shipped only under a GNU AGPL software license:
Ghostscript (including subpackages)
SUSE Linux Enterprise for High-Performance Computing 15 SP4 (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise for High-Performance Computing 15 SP4.
+This directory includes PDF versions of the SUSE Linux Enterprise for High-Performance Computing 15 SP4 Installation Quick Start Guide.
This section comprises information about modules and extensions for SUSE Linux Enterprise for High-Performance Computing 15 SP4
+Modules and extensions add functionality to the system.
The SLE 15 SP4 product line is made up of modules that contain software packages. Each module has a clearly defined scope. Modules differ in their life cycles and update timelines.
Not all SLE modules are available with a subscription for SUSE Linux Enterprise for High-Performance Computing 15 SP4 itself (see the column Available for).
The following extension is not covered by SUSE support agreements, available at no additional cost and without an extra registration key: SUSE Package Hub, see https://packagehub.suse.com/.
This sections lists related products. Usually, these products have their own release notes documents that are available from https://www.suse.com/releasenotes.
Technology previews are packages, stacks, or features delivered by SUSE which are not supported.
+They may be functionally incomplete, unstable or in other ways not suitable for production use.
+They are included for your convenience and give you a chance to test new technologies within an enterprise environment.
Whether a technology preview becomes a fully supported technology later depends on customer and market feedback.
+Technology previews can be dropped at any time and SUSE does not commit to providing a supported version of such technologies in the future.
Give your SUSE representative feedback about technology previews, including your experience and use case.
SUSE Linux Enterprise for High-Performance Computing for Arm 12 SP2 and later kernels have used a page size of 4K.
+This offers the widest compatibility also for small systems with little RAM,
+allowing to use Transparent Huge Pages (THP) where large pages make sense.
As a technology preview, SUSE Linux Enterprise for High-Performance Computing for Arm 15 SP4 adds a kernel flavor
+64kb, offering a page size of 64 KiB and physical/virtual address size
+of 52 bits.
+Same as the default kernel flavor, it does not use preemption.
Main purpose at this time is to allow for side-by-side benchmarking for
+High Performance Computing, Machine Learning and other Big Data use cases.
+Contact your SUSE representative if you notice performance gains
+for your specific workloads.
Important: Swap needs to be re-initialized
After booting the 64K kernel, any swap partitions need to re-initialized to be usable.
+To do this, run the swapon command with the --fixpgsz parameter on the swap partition.
+Note that this process deletes data present in the swap partition (for example, suspend data).
+In this example, the swap partition is on /dev/sdc1:
swapon --fixpgsz /dev/sdc1
Important: Btrfs file system uses page size as block size
It is currently not possible to use Btrfs file systems across page sizes.
+Block sizes below page size are not yet supported and block sizes above
+page size might never be supported.
During installation, change the default partitioning proposal and choose
+another file system, such as Ext4 or XFS, to allow rebooting from the
+default 4K page size kernel of the Installer into kernel-64kb and back.
See the Storage Guide for a discussion of supported file systems.
Warning: RAID 5 uses page size as stripe size
It is currently not yet possible to configure stripe size on volume creation.
+This will lead to sub-optimal performance if page size and block size differ.
Avoid RAID 5 volumes when benchmarking 64K vs. 4K page size kernels.
See the Storage Guide for more information on software RAID.
The HPC module contains HPC specific packages. These include the workload manager Slurm, the node deployment tool clustduct, munge for user authentication, the remote shell mrsh, the parallel shell pdsh, as well as numerous HPC libraries and frameworks.
This module is available with the SUSE Linux Enterprise for High-Performance Computing only. It is selected by default during the installation. It can be added or removed using the YaST UI or the SUSEConnect CLI tool. Refer to the system administration guide for further details.
The NVIDIA Compute Module provides the NVIDIA CUDA repository for SUSE Linux Enterprise 15. Note that that any software within this repository is under a 3rd party EULA. For more information check https://docs.nvidia.com/cuda/eula/index.html.
This module is not selected for addition by default when installing SUSE Linux Enterprise for High-Performance Computing. It may be selected manually during installation from the Extension and Modules screen. You may also select it on an installed system using YaST. To do so, run from a shell as root yast registration, select: Select Extensions and search for NVIDIA Compute Module and press Next.
Important
Do not attempt to add this module with the SUSEConnect CLI tool. This tool is not yet capable of handling 3rd party repositories.
Once you have selected this module you will be asked to confirm the 3rd party license and verify the repository signing key.
As of 15 SP4, SUSE Linux Enterprise for High-Performance Computing is no longer a separate product. As a result:
the HPC Module can now be enabled in SUSE Linux Enterprise Server
when migrating from SUSE Linux Enterprise for High-Performance Computing 15 SP3, SP4, and SP5, only SUSE Linux Enterprise Server 15 SP6 will be available as migration target.
+The result of such a migration will be an installation of SUSE Linux Enterprise Server with all the previously enabled modules.
6.2 Enriched system visibility in the SUSE Customer Center (SCC)#
SUSE is committed to helping provide better insights into the consumption of SUSE subscriptions regardless of where they are running or how they are managed; physical or virtual, on-prem or in the cloud, connected to SCC or Repository Mirroring Tool (RMT), or managed by SUSE Manager.
+To help you identify or filter out systems in SCC that are no longer running or decommissioned, SUSEConnect now features a daily “ping”, which will update system information automatically.
Installing the following packages automatically opens the following ports:
dolly - TCP ports 9997 and 9998
slurm - TCP ports 6817, 6818, and 6819
Important
These release notes only document changes in SUSE Linux Enterprise for High-Performance Computing compared to the immediate previous service pack of SUSE Linux Enterprise for High-Performance Computing.
+The full changes and fixes can be found on the respective web site of the packages.
dolly has been updated to version 0.63.6.
+It includes some fixes for hostname resolution, a better documentation and now provides a default configuration for firewall.
Spack’s traditional
+package
+preferences are soft, but we’ve added hard requriements to
+packages.yaml and spack.yaml . Package requirements use the same
+syntax as specs:
spack install in an environment will no longer add to the specs:
+list; you’ll need to either use spack add <spec> or
+spack install --add <spec>.
Similarly, spack uninstall will not remove from your environment’s
+specs: list; you’ll need to use spack remove or
+spack uninstall --remove.
This will make it easier to manage an environment, as there is clear
+separation between the stack to be installed (spack.yaml/spack.lock)
+and which parts of it should be installed (spack install /
+spack uninstall).
concretizer:unify:true is now the default mode for new environments
We see more users creating unify:true environments now. Users who need
+unify:false can add it to their environment to get the old behavior.
+This will concretize every spec in the environment independently.
Include environment configuration from URLs (
+docs)
You can now include configuration in your environment directly from a
+URL:
Currently, compiler flags and variants are inconsistent: compiler flags
+set for a package are inherited by its dependencies, while variants are
+not. We should have these be consistent by allowing for inheritance to
+be enabled or disabled for both variants and compiler flags.
Example syntax:
+* package ++variant: enabled variant that will be propagated to
+dependencies
+* package +variant: enabled variant that will NOT be propagated to
+dependencies
+* package ~~variant: disabled variant that will be propagated to
+dependencies
+* package ~variant: disabled variant that will NOT be propagated to
+dependencies
+* package cflags==-g: cflags will be propagated to dependencies
+* package cflags=-g: cflags will NOT be propagated to dependencies
+
+Syntax for non-boolan variants is similar to compiler flags. More in the
+docs for
+variants
+and
+compiler
+flags.
Enhancements to git version specifiers
v0.18.0 added the ability to use git commits as versions. You can
+now use the git. prefix to specify git tags or branches as versions.
+All of these are valid git versions in v0.19 :
foo@abcdef1234abcdef1234abcdef1234abcdef1234 # raw commit
+foo@git.abcdef1234abcdef1234abcdef1234abcdef1234 # commit with git prefix
+foo@git.develop # the develop branch
+foo@git.0.19 # use the 0.19 tag
v0.19 also gives you more control over how Spack interprets git
+versions, in case Spack cannot detect the version from the git
+repository. You can suffix a git version with =<version> to force
+Spack to concretize it as a particular version :
# use mybranch, but treat it as version 3.2 for version comparison
+foo@git.mybranch=3.2
+
+# use the given commit, but treat it as develop for version comparison
+foo@git.abcdef1234abcdef1234abcdef1234abcdef1234=develop
Cray machines have historically had their own platform within Spack,
+because we needed to go through the module system to leverage compilers
+and MPI installations on these machines. The Cray EX programming
+environment now provides standalone craycc executables and proper
+mpicc wrappers, so Spack can treat EX machines like Linux with extra
+packages .
We expect this to greatly reduce bugs, as external packages and
+compilers can now be used by prefix instead of through modules. We will
+also no longer be subject to reproducibility issues when modules change
+from Cray PE release to release and from site to site. This also
+simplifies dealing with the underlying Linux OS on cray systems, as
+Spack will properly model the machine’s OS as either SuSE or RHEL.
Improvements to tests and testing in CI
spack ci generate --tests will generate a .gitlab-ci.yml file that
+not only does builds but also runs tests for built packages . Public
+GitHub pipelines now also run tests in CI.
spack test run --explicit will only run tests for packages that are
+explicitly installed, instead of all packages.
Experimental binding link model
You can add a new option to config.yaml to make Spack embed absolute
+paths to needed shared libraries in ELF executables and shared libraries
+on Linux (
+docs):
This can improve launch time at scale for parallel applications, and it
+can make installations less susceptible to environment variables like
+LD_LIBRARY_PATH, even especially when dealing with external libraries
+that use RUNPATH. You can think of this as a faster, even
+higher-precedence version of RPATH.
Support for Python 3.5 is dropped . Only Python 2.7 and 3.6+ are
+officially supported.
This is the last Spack release that will support Python 2 . Spack
+v0.19 will emit a deprecation warning if you run it with Python 2, and
+Python 2 support will soon be removed from the develop branch.
LD_LIBRARY_PATH is no longer set by default by spack load or
+module loads.
Setting LD_LIBRARY_PATH in Spack environments/modules can cause
+binaries from outside of Spack to crash, and Spack’s own builds use
+RPATH and do not need LD_LIBRARY_PATH set in order to run. If you
+still want the old behavior, you can run these commands to configure
+Spack to set LD_LIBRARY_PATH:
The spack:concretization:[together|separately] has been removed
+after being deprecated in v0.18. Use concretizer:unify:[true|false].
config:module_roots is no longer supported after being deprecated in
+v0.18. Use configuration in module sets instead (
+docs).
spack activate and spack deactivate are no longer supported,
+having been deprecated in v0.18. Use an environment with a view
+instead of activating/deactivating
+(docs).
The old YAML format for buildcaches is now deprecated . If you are
+using an old buildcache with YAML metadata you will need to regenerate
+it with JSON metadata.
spack bootstrap trust and spack bootstrap untrust are deprecated
+in favor of spack bootstrap enable and spack bootstrap disable and
+will be removed in v0.20.
The graviton2 architecture has been renamed to neoverse_n1, and
+graviton3 is now neoverse_v1. Buildcaches using the old architecture
+names will need to be rebuilt.
The terms blacklist and whitelist have been replaced with
+include and exclude in all configuration files . You can use
+spack config update to automatically fix your configuration files.
spack install --reuse was introduced in v0.17.0, and --reuse is
+now the default concretization mode. Spack will try hard to resolve
+dependencies using installed packages or binaries .
To avoid reuse and to use the latest package configurations, (the old
+default), you can use spack install --fresh, or add configuration like
+this to your environment or concretizer.yaml:
concretizer:
+ reuse: false
Finer-grained hashes
Spack hashes now include link, run, andbuild dependencies, as
+well as a canonical hash of package recipes. Previously, hashes only
+included link and run dependencies (though build dependencies were
+stored by environments). We coarsened the hash to reduce churn in user
+installations, but the new default concretizer behavior mitigates this
+concern and gets us reuse and provenance. You will be able to see the
+build dependencies of new installations with spack find. Old
+installations will not change and their hashes will not be affected.
Improved error messages
Error handling with the new concretizer is now done with optimization
+criteria rather than with unsatisfiable cores, and Spack reports many
+more details about conflicting constraints.
Unify environments when possible
Environments have thus far supported concretization: together or
+concretization: separately. These have been replaced by a new
+preference in concretizer.yaml:
concretizer:
+ unify: [true|false|when_possible]
concretizer:unify:when_possible will try to resolve a fully unified
+environment, but if it cannot, it will create multiple configurations of
+some packages where it has to. For large environments that previously
+had to be concretized separately, this can result in a huge speedup
+(40-50x).
Automatically find externals on Cray machines
Spack can now automatically discover installed packages in the Cray
+Programming Environment by running spack external find (or
+spack external read-cray-manifest to only query the PE). Packages
+from the PE (e.g., cray-mpich are added to the database with full
+dependency information, and compilers from the PE are added to
+compilers.yaml. Available with the June 2022 release of the Cray
+Programming Environment.
New binary format and hardened signing
Spack now has an updated binary format, with improvements for security.
+The new format has a detached signature file, and Spack verifies the
+signature before untarring or decompressing the binary package. The
+previous format embedded the signature in a tar file, which required
+the client to run tarbefore verifying . Spack can still install
+from build caches using the old format, but we encourage users to switch
+to the new format going forward.
Production GitLab pipelines have been hardened to securely sign
+binaries. There is now a separate signing stage so that signing keys are
+never exposed to build system code, and signing keys are ephemeral and
+only live as long as the signing pipeline stage.
Bootstrap mirror generation
The spack bootstrap mirror command can automatically create a mirror
+for bootstrapping the concretizer and other needed dependencies in an
+air-gapped environment.
Makefile generation
spack env depfile can be used to generate a Makefile from an
+environment, which can be used to build packages the environment in
+parallel on a single node. e.g.:
spack -e myenv env depfile > Makefile
+make
Spack propagates gmake jobserver information to builds so that their
+jobs can share cores.
New variant features
In addition to being conditional themselves, variants can now have
+conditional
+values that are only possible for certain configurations of a
+package.
Variants can be
+declared sticky, which prevents them from being enabled or disabled by the
+concretizer. Sticky variants must be set explicitly by users on the
+command line or in packages.yaml.
6.9.1 Important Notes for Upgrading Slurm Releases:#
If using the slurmdbd (Slurm DataBase Daemon) you must update this first.
+If using a backup DBD you must start the primary first to do any
+database conversion, the backup will not start until this has happened.
6.9.2.1 Important notes for upgrading to version 22.05#
Slurmdbd version 22.05 will work Slurm daemons of version 20.11.
+You will not need to update all clusters at the same time, but it is very
+important to update slurmdbd first and having it running before updating
+any other clusters making use of it.
Slurm can be upgraded from version 20.11 to version 22.05 without loss of jobs
+or other state information. Upgrading directly from an earlier version
+of Slurm will result in loss of state information.
For more information and a recommended upgrade procedure, see the section
+"Upgrading Slurm" in the chapter "Slurm — utility for HPC workload management"
+of the in the SLE HPC 15 "Administration Guide".
All SPANK plugins must be recompiled when upgrading from any Slurm version
+prior to 22.05.
If you are using the Slurm plugin for pdsh you must make sure,
+pdsh_slurm_22_05 is installed together with slurm_22_05.
The template slurmrestd.service unit file now defaults to listen on both the
+Unix socket and the slurmrestd port.
The template slurmrestd.service unit file now defaults to enable auth/jwt
+and the munge unit is no longer a dependency by default.
Add extra “EnvironmentFile=-/etc/default/$service” setting to service files.
Allow jobs to pack onto nodes already rebooting with the desired features.
Reset job start time after nodes are rebooted, previously only done for
+cloud/power save boots.
Node features (if any) are passed to RebootProgram if run from slurmctld.
Fail srun when using invalid --cpu-bind options (e.g. --cpu-bind=map_cpu:99
+when only 10 CPUs are allocated).
Storing batch scripts and env vars are now in indexed tables using
+substantially less disk space. Those storing scripts in 21.08 will all
+be moved and indexed automatically.
Run MailProg through slurmscriptd instead of directly fork+exec()'ing
+from slurmctld.
Add acct_gather_interconnect/sysfs plugin.
Future and Cloud nodes are treated as "Planned Down" in usage reports.
Add new shard plugin for sharing GPUs but not with mps.
Add support for Lenovo SD650 V2 in acct_gather_energy/xcc plugin.
Remove cgroup_allowed_devices_file.conf, since the default policy in modern
+kernels is to whitelist by default. Denying specific devices must be done
+through gres.conf.
Node state flags (DRAIN, FAILED, POWERING UP, etc.) will be cleared now if
+node state is updated to FUTURE.
srun will no longer read in SLURM_CPUS_PER_TASK. This means you will
+implicitly have to specify --cpus-per-task on your srun calls, or set the
+new SRUN_CPUS_PER_TASK environment variable to accomplish the same thing.
Remove connect_timeout and timeout options from JobCompParams as there’s no
+longer a connectivity check happening in the jobcomp/elasticsearch plugin
+when setting the location off of JobCompLoc.
Add support for hourly reoccurring reservations.
Allow nodes to be dynamically added and removed from the system. Configure
+MaxNodeCount to accomodate nodes created with dynamic node registrations
+(slurmd -Z --conf="") and scontrol.
Added support for Cgroup Version 2.
sacct - allocations made by srun will now always display the allocation and
+step(s). Previously, the allocation and step were combined when possible.
cons_tres - change definition of the "least loaded node" (LLN) to the node
+with the greatest ratio of available CPUs to total CPUs.
Add support to ship Include configuration files with configless.
Provide a detailed reason in the job log as to why it has been terminated
+when hitting a resource limit.
Pass and use alias_list through credential instead of environment variable.
Add ability to get host addresses from nss_slurm.
Enable reverse fanout for cloud+alias_list jobs.
Add support to delete/update nodes by specifying nodesets or the 'ALL'
+keyword alongside the delete/update node message nodelist expression (i.e.
+scontrol delete/update NodeName=ALL or scontrol delete/update NodeName=ns1,nodes[1-3]).
Expanded the set of environment variables accessible through Prolog/Epilog
+and PrologSlurmctld/EpilogSlurmctld to include SLURM_JOB_COMMENT,
+SLURM_JOB_STDERR, SLURM_JOB_STDIN, SLURM_JOB_STDOUT, SLURM_JOB_PARTITION,
+SLURM_JOB_ACCOUNT, SLURM_JOB_RESERVATION, SLURM_JOB_CONSTRAINTS,
+SLURM_JOB_NUM_HOSTS, SLURM_JOB_CPUS_PER_NODE, SLURM_JOB_NTASKS, and
+SLURM_JOB_RESTART_COUNT.
Attempt to requeue jobs terminated by slurm.conf changes (node vanish, node
+socket/core change, etc). Processes may still be running on excised nodes.
+Admin should take precautions when removing nodes that have jobs on running
+on them.
Add switch/hpe_slingshot plugin.
Add new SchedulerParameters option bf_licenses to track licenses as
+within the backfill scheduler.
6.9.2.3 Configureation File changes (for details, see the appropriate man page)#
AcctGatherEnergyTypersmi is now gpu.
TaskAffinity parameter was removed from cgroup.conf.
Fatal if the mutually-exclusive JobAcctGatherParams options of UsePss and
+NoShared are both defined.
KeepAliveTime has been moved into CommunicationParameters. The standalone
+option will be removed in a future version.
preempt/qos - add support for WITHIN mode to allow for preemption between
+jobs within the same QOS.
Fatal error if CgroupReleaseAgentDir is configured in cgroup.conf. The
+option has long been obsolete.
Fatal if more than one burst buffer plugin is configured.
Added keepaliveinterval and keepaliveprobes to CommunicationParameters.
Added new max_token_lifespan=<seconds> to AuthAltParameters to allow sites
+to restrict the lifespan of any requested ticket by an unprivileged user.
Disallow slurm.conf node configurations with NodeName=ALL.
6.9.2.4 Command Changes (for details, see the appropriate man page)#
Remove support for (non-functional) --cpu-bind=boards.
Added --prefer option at job submission to allow for 'soft' constraints.
Add condflags=open to sacctmgr show events to return open/currently down
+events.
sacct -f flag implies -c flag.
srun --overlap now allows the step to share all resources (CPUs, memory, and
+GRES), where previously --overlap only allowed the step to share CPUs with
+other steps.
burst_buffer plugins - err_msg added to bb_p_job_validate().
openapi - added flags to slurm_openapi_p_get_specification(). Existing
+plugins only need to update their prototype for the function as
+manipulating the flags pointer is optional.
openapi - Added OAS_FLAG_MANGLE_OPID to allow plugins to request that the
+operationId of path methods be mangled with the full path to ensure
+uniqueness.
openapi/[db]v0.0.36 - Plugins have been marked as deprecated and will be
+removed in the next major release.
Removed gres/mic plugin used to support Xeon Phi coprocessors.
Add LimitFactor to the QOS. A float that is factored into an associations
+GrpTRES limits. For example, if the LimitFactor is 2, then an association
+with a GrpTRES of 30 CPUs, would be allowed to allocate 60 CPUs when
+running under this QOS.
A job’s next_step_id counter now resets to 0 after being requeued.
+Previously, the step id’s would continue from the job’s last run.
API change: Removed slurm_kill_job_msg and modified the function signature
+for slurm_kill_job2. slurm_kill_job2 should be used instead of
+slurm_kill_job_msg.
AccountingStoreFlags=job_script allows you to store the job’s batch script.
AccountingStoreFlags=job_env allows you to store the job’s env vars.
Removed sched/hold plugin.
cli_filter/lua, jobcomp/lua, job_submit/lua now load their scripts from the
+same directory as the slurm.conf file (and thus now will respect changes
+to the SLURM_CONF environment variable).
SPANK - call slurm_spank_init if defined without slurm_spank_slurmd_exit in
+slurmd context.
Add new PLANNED state to a node to represent when the backfill scheduler
+has it planned to be used in the future instead of showing as IDLE.
+sreport also has changed it’s cluster utilization report column name from
+'Reserved' to 'Planned' to match this nomenclature.
Put node into INVAL state upon registering with an invalid node
+configuration. Node must register with a valid configuration to continue.
Remove SLURM_DIST_LLLP environment variable in favor of just
+SLURM_DISTRIBUTION.
Make --cpu-bind=threads default for --threads-per-core — can be
+overridden by the CLI or an environment variable.
slurmd - allow multiple comma-separated controllers to be specified in
+configless mode with --conf-server
Manually powering down of nodes with scontrol now ignores
+SuspendExc<Nodes|Parts>.
Distinguish queued reboot requests (REBOOT@) from issued reboots (REBOOT^).
auth/jwt - add support for RS256 tokens. Also permit the username in the
+'username' field in addition to the 'sun' (Slurm UserName) field.
service files - change dependency to network-online rather than just
+network to ensure DNS and other services are available.
Add "Extra" field to node to store extra information other than a comment.
Add ResumeTimeout, SuspendTimeout and SuspendTime to Partitions.
The memory.force_empty parameters is no longer set by jobacct_gather/cgroup
+when deleting the cgroup`. This previously caused a significant delay (~2s)
+when terminating a job, and is not believed to have provided any perceivable
+benefit. However, this may lead to slightly higher reported kernel mem page
+cache usage since the kernel cgroup memory is no longer freed immediately.
TaskPluginParam=verbose is now treated as a default. Previously it would be
+applied regardless of the job specifying a --cpu-bind.
Add node_reg_mem_percentSlurmctldParameter to define percentage of
+memory nodes are allowed to register with.
Define and separate node power state transitions. Previously a powering
+down node was in both states, POWERING_OFF and POWERED_OFF. These are now
+separated.
+e.g.
+ IDLE+POWERED_OFF (IDLE~)
+→ IDLE+POWERING_UP (IDLE#) - Manual power up or allocation
+→ IDLE
+→ IDLE+POWER_DOWN (IDLE!) - Node waiting for power down
+→ IDLE+POWERING_DOWN (IDLE%) - Node powering down
+→ IDLE+POWERED_OFF (IDLE~) - Powered off
Some node state flag names have changed. These would be noticeable for
+example if using a state flag to filter nodes with sinfo.
+e.g.
+POWER_UP → POWERING_UP
+POWER_DOWN → POWERED_DOWN
+POWER_DOWN now represents a node pending power down
Create a new process called slurmscriptd which runs PrologSlurmctld and
+EpilogSlurmctld. This avoids fork() calls from slurmctld, and can avoid
+performance issues if the slurmctld has a large memory footprint.
Pass JSON of job to node mappings to ResumeProgram.
QOS accrue limits only apply to the job QOS, not partition QOS.
Any return code from SPANK plugin or SPANK function that is not
+SLURM_SUCCESS (zero) will be considered to be an error. Previously, only
+negative return codes were considered an error.
Add support for automatically detecting and broadcasting executable shared
+object dependencies for sbcast and srun --bcast.
All SPANK error codes now start at 3000. Where previously SPANK would give
+a return code of 1, it will now return 3000. This change will break ABI
+compatibility with SPANK plugins compiled against older version of Slurm.
SPANK plugins are now required to match the current Slurm release, and
+must be recompiled for each new Slurm major release. (They do not need
+to be recompiled when upgrading between maintenance releases.)
SLURM_NODE_ALIASES now has brackets around the node’s address to be able to
+distinguish IPv6 addresses. e.g. <node_name>:[<node_addr>]:<node_hostname>
The job_container/tmpfs plugin now requires PrologFlags=contain to be set in
+slurm.conf.
Limit max_script_size to 512 MB.
6.9.3.2 Configuration File Changes (for details, see the appropriate man page)#
Errors detected in the parser handlers due to invalid configurations are now
+propagated and can lead to fatal (and thus exit) the calling process.
Enforce a valid configuration for AccountingStorageEnforce in slurm.conf.
+If the configuration is invalid, then an error message will be printed and
+the command or daemon (including slurmctld) will not run.
Removed AccountingStoreJobComment option. Please update your config to use
+AccountingStoreFlags=job_comment instead.
Added Script to DebugFlags for debugging slurmscriptd (the process that runs
+slurmctld scripts such as PrologSlurmctld and EpilogSlurmctld).
Rename SbcastParameters to BcastParameters.
systemd service files - add new “-s” option to each daemon which will
+change the working directory even with the -D option. (Ensures any core
+files are placed in an accessible location, rather than /.)
Added BcastParameters=send_libs and BcastExclude options.
Remove the (incomplete) burst_buffer/generic plugin.
Make SelectTypeParameters=CR_Core_Memory default for cons_tres and cons_res.
Remove support for TaskAffinity=yes in cgroup.conf. Adding task/affinity to
+TaskPlugins in slurm.conf is strongly recommended instead.
6.9.3.3 Command Changes (for details, see the appropriate man page)#
Changed the --format handling for negative field widths (left justified)
+to apply to the column headers as well as the printed fields.
Invalidate multiple partition requests when using partition based
+associations.
scrontab - create the temporary file under the TMPDIR environment variable
+(if set), otherwise continue to use TmpFS as configured in slurm.conf.
sbcast / srun --bcast - removed support for zlib compression. lz4 is vastly
+superior in performance, and (counter-intuitively) zlib could provide worse
+performance than no compression at all on many systems.
sacctmgr - changed column headings to ParentID and ParentName instead
+of Par ID and "Par Name` respectively.
SALLOC_THREADS_PER_CORE and SBATCH_THREADS_PER_CORE have been added as
+input environment variables for salloc and sbatch, respectively. They do
+the same thing as --threads-per-core.
Don’t display node’s comment with scontrol show nodes unless set.
Added SLURM_GPUS_ON_NODE environment variable within each job/step.
sreport - change to sorting TopUsage by the --tres option.
slurmrestd - do not run allow operation as SlurmUser/root by default.
scontrol show node now shows State as base_state+flags instead of
+shortened state with flags appended. eg. IDLE# → IDLE+POWERING_UP.
+Also POWER state flag string is POWERED_DOWN.
scrontab - add ability to update crontab from a file or standard input.
scrontab - added ability to set and expand variables.
Make srun sensitive to BcastParameters.
Added sbcast/srun --send-libs, sbcast --exclude and srun --bcast-exclude.
Changed ReqMem field in sacct to match memory from ReqTRES. It now shows
+the requested memory of the whole job with a letter appended indicating
+units (M for megabytes, G for gigabytes, etc.). ReqMem is only displayed for
+the job, since the step does not have requested TRES. Previously ReqMem
+was also displayed for the step but was just displaying ReqMem for the job.
jobcomp plugin: change plugin API to jobcomp_p_*().
sched plugin: change plugin API to sched_p_*() and remove
+slurm_sched_p_initial_priority() call.
step_ctx code has been removed from the api.
slurm_stepd_get_info()/stepd_get_info() has been removed from the api.
The v0.0.35 OpenAPI plugin has now been marked as deprecated.
+Please convert your requests to the v0.0.37 OpenAPI plugin.
6.10 Creating containers from current HPC environment#
Usually users use environment modules to adjust their environment (that is, environment variables like PATH, LD_LIBRARY_PATH, MANPATH etc.) to pick exactly the tools and libraries they need for their work.
+The same can be achieved with containers by including only those components in a container that are part of this environment.
+This functionality is now provided using the spack and singularity applications.
6.11.1 Important Notes on Upgrading Slurm from a Previous Version#
If using the slurmdbd (Slurm DataBase Daemon) you must update this first.
If using a backup DBD you must start the primary first to do any
+database conversion, the backup will not start until this has happened.
The 23.02 slurmdbd will work with Slurm daemons of version 21.08 and above.
+You will not need to update all clusters at the same time, but it is very
+important to update slurmdbd first and having it running before updating
+any other clusters making use of it.
Slurm can be upgraded from version 22.05 to version 23.02 without loss
+of jobs or other state information. Upgrading directly from an earlier version
+of Slurm will result in loss of state information.
All SPANK plugins must be recompiled when upgrading from any Slurm version
+prior to 23.02.
slurmctld - Add new RPC rate limiting feature. This is enabled through
+SlurmctldParameters=rl_enable, otherwise disabled by default.
Make scontrol reconfigure and sending a SIGHUP to the slurmctld behave the
+same. If you were using SIGHUP as a 'lighter' scontrol reconfigure to rotate
+logs please update your scripts to use SIGUSR2 instead.
Change cloud nodes to show by default. PrivateData=cloud is no longer
+needed.
sreport - Count planned (FKA reserved) time for jobs running in IGNORE_JOBS
+reservations. Previously was lumped into IDLE time.
job_container/tmpfs - Support running with an arbitrary list of private
+mount points (/tmp and /dev/shm are the default, but not required).
job_container/tmpfs - Set more environment variables in InitScript.
Make all cgroup directories created by Slurm owned by root. This was the
+behavior in cgroup/v2 but not in cgroup/v1 where by default the step
+directories ownership were set to the user and group of the job.
accounting_storage/mysql - change purge/archive to calculate record ages
+based on end time, rather than start or submission times.
job_submit/lua - add support for log_user() from slurm_job_modify().
Run the following scripts in slurmscriptd instead of slurmctld:
+ResumeProgram, ResumeFailProgram, SuspendProgram, ResvProlog, ResvEpilog,
+and RebootProgram (only with SlurmctldParameters=reboot_from_controller).
Only permit changing log levels with srun --slurmd-debug by root
+or SlurmUser.
slurmctld will fatal() when reconfiguring the job_submit plugin fails.
Add PowerDownOnIdle partition option to power down nodes after nodes become
+idle.
Add “[jobid.stepid]” prefix from slurmstepd and “slurmscriptd” prefix from
+slurmcriptd to Syslog logging. Previously was only happening when logging
+to a file.
Add purge and archive functionality for job environment and job batch script
+records.
Extend support for Include files to all "configless" client commands.
Make node weight usable for powered down and rebooting nodes.
Removed “launch” plugin.
Add “Extra” field to job to store extra information other than a comment.
Add usage gathering for AMD (requires ROCM 5.5+) and NVIDIA gpus.
Add job’s allocated nodes, features, oversubscribe, partition, and
+reservation to SLURM_RESUME_FILE output for power saving.
Automatically create directories for stdout/stderr output files. Paths may
+use %j and related substitution characters as well.
Add --tres-per-task to salloc/sbatch/srun.
Allow nodefeatures plugin features to work with cloud nodes.
+e.g. - Powered down nodes have no active changeable features.
Nodes can’t be changed to other active features until powered down.
Active changeable features are reset/cleared on power down.
Make slurmstepd cgroups constrained by total configured memory from
+slurm.conf (NodeName=<> RealMemory=#) instead of total physical memory.
node_features/helpers - add support for the OR and parentheses operators
+in a --constraint expression.
slurmctld will fatal() when [Prolog|Epilog]Slurmctld are defined but are not
+executable.
Validate node registered active features are a super set of node’s
+currently active changeable features.
On clusters without any PrologFlags options, batch jobs with failed prologs
+nolonger generate an output file.
Add SLURM_JOB_START_TIME and SLURM_JOB_END_TIME environment variables.
Add SuspendExcStates option to slurm.conf to avoid suspending/powering down
+specific node states.
Add support for DCMI power readings in IPMI plugin.
slurmrestd served /slurm/v0.0.39 and /slurmdb/v0.0.39 endpoints had major
+changes from prior versions. Almost all schemas have been renamed and
+modified. Sites using OpenAPI Generator clients are highly suggested to
+upgrade to to using atleast version 6.x due to limitations with prior
+versions.
Allow for --nodelist to contain more nodes than required by --nodes.
Rename “nodes” to “nodes_resume” in SLURM_RESUME_FILE job output.
Rename “all_nodes” to “all_nodes_resume” in SLURM_RESUME_FILE output.
Add jobcomp/kafka plugin.
Add new PreemptParameters=reclaim_licenses option which will allow higher
+priority jobs to preempt jobs to free up used licenses. (This is only
+enabled for with PreemptModes of CANCEL and REQUEUE, as Slurm cannot
+guarantee suspended jobs will release licenses correctly.)
hpe/slingshot - add support for the instant-on feature.
Add ability to update SuspendExc* parameters with scontrol.
Add ability to restore SuspendExc* parameters on restart with slurmctld -R
+option.
Add ability to clear a GRES specification by setting it to "0" via
+“scontrol update job”.
Add SLURM_JOB_OVERSUBSCRIBE environment variable for Epilog, Prolog,
+EpilogSlurmctld, PrologSlurmctld, and mail ouput.
System node down reasons are appended to existing reasons, separated by ':'.
New command scrun has been added. scrun acts as an Open Container Initiative
+(OCI) runtime proxy to run containers seamlessly via Slurm.
Fixed GpuFreqDef option. When set in slurm.conf, it will be used if
+--gpu-freq was not explicitly set by the job step.
6.11.3 Configuration File Changes (see appropriate man page for details)#
job_container.conf - Added “Dirs” option to list desired private mount
+points.
node_features plugins - invalid users specified for AllowUserBoot will now
+result in fatal() rather than just an error.
Deprecate AllowedKmemSpace, ConstrainKmemSpace, MaxKmemPercent, and
+MinKmemSpace.
Allow jobs to queue even if the user is not in AllowGroups when
+EnforcePartLimits=no is set. This ensures consistency for all the Partition
+access controls, and matches the documented behavior for EnforcePartLimits.
Add InfluxDBTimeout parameter to acct_gather.conf.
job_container/tmpfs - add support for expanding %h and %n in BasePath.
slurm.conf - Removed SlurmctldPlugstack option.
Add new SlurmctldParameters=validate_nodeaddr_threads=<number> option to
+allow concurrent hostname resolution at slurmctld startup.
Add new AccountingStoreFlags=job_extra option to store a job’s extra field
+in the database.
Add new “defer_batch” option to SchedulerParameters to only defer
+scheduling for batch jobs.
Add new DebugFlags option “JobComp” to replace “Elasticsearch”.
Add configurable job requeue limit parameter - MaxBatchRequeue - in
+slurm.conf to permit changes from the old hard-coded value of 5.
helpers.conf - Allow specification of node specific features.
helpers.conf - Allow many features to one helper script.
job_container/tmpfs - Add “Shared” option to support shared namespaces.
+This allows autofs to work with the job_container/tmpfs plugin when enabled.
acct_gather.conf - Added EnergyIPMIPowerSensors=Node=DCMI and
+Node=DCMI_ENHANCED.
Add new “getnameinfo_cache_timeout=<number>” option to
+CommunicationParameters to adjust or disable caching the results of
+getnameinfo().
Add new PrologFlags=ForceRequeueOnFail option to automatically requeue
+batch jobs on Prolog failures regardless of the job --requeue setting.
Add HealthCheckNodeState=NONDRAINED_IDLE option.
Add “explicit” to Flags in gres.conf. This makes it so the gres is not
+automatically added to a job’s allocation when --exclusive is used. Note
+that this is a per-node flag.
Moved the “preempt_” options from SchedulerParameters to PreemptParameters,
+and dropped the prefix from the option names. (The old options will still
+be parsed for backwards compatibility, but are now undocumented.)
Add LaunchParameters=ulimit_pam_adopt, which enables setting RLIMIT_RSS in
+adopted processes.
Update SwitchParameters=job_vni to enable/disable creating job VNIs for all
+jobs, or when a user requests them.
Update SwitchParameters=single_node_vni to enable/disable creating single
+node VNIs for all jobs, or when a user requests them.
Add ability to preserve SuspendExc* parameters on reconfig with
+ReconfigFlags=KeepPowerSaveSettings.
slurmdbd.conf - Add new AllResourcesAbsolute to force all new resources
+to be created with the Absolute flag.
topology/tree - Add new TopologyParam=SwitchAsNodeRank option to reorder
+nodes based on switch layout. This can be useful if the naming convention
+for the nodes does not natually map to the network topology.
Removed the default setting for GpuFreqDef. If unset, no attempt to change
+the GPU frequency will be made if --gpu-freq is not set for the step.
6.11.4 Command Changes (see man pages for details)#
sacctmgr - no longer force updates to the AdminComment, Comment, or
+SystemComment to lower-case.
sinfo - Add -F/--future option to sinfo to display future nodes.
sacct - Rename “Reserved” field to “Planned” to match sreport and the
+nomenclature of the 'Planned' node.
scontrol - advanced reservation flag MAINT will no longer replace nodes,
+similar to STATIC_ALLOC
sbatch - add parsing for #PBS -d and #PBS -w.
scontrol show assoc_mgr will show username(uid) instead of uid in
+QoS section.
Add strigger --draining and -R/--resume options.
Change --oversubscribe and --exclusive to be mutually exclusive for job
+submission. Job submission commands will now fatal if both are set.
+Previously, these options would override each other, with the last one in
+the job submission command taking effect.
scontrol - Requested TRES and allocated TRES will now always be printed when
+showing jobs, instead of one TRES output that was either the requested or
+allocated.
srun --ntasks-per-core now applies to job and step allocations. Now, use of
+--ntasks-per-core=1 implies --cpu-bind=cores and --ntasks-per-core>1 implies
+--cpu-bind=threads.
salloc/sbatch/srun - Check and abort if ntasks-per-core > threads-per-core.
scontrol - Add ResumeAfter=<secs> option to “scontrol update nodename=”.
Add a new “nodes=” argument to scontrol setdebug to allow the debug level
+on the slurmd processes to be temporarily altered.
Add a new “nodes=” argument to “scontrol setdebugflags” as well.
Make it so scrontab prints client-side the job_submit() error messsage (which can
+be set i.e. by using the log_user() function for the lua plugin).
scontrol - Reservations will not be allowed to have STATIC_ALLOC or MAINT
+flags and REPLACE[_DOWN] flags simultaneously.
scontrol - Reservations will only accept one reoccurring flag when
+being created or updated.
scontrol - A reservation cannot be updated to be reoccurring if it is
+already a floating reservation.
squeue - removed unused “%s” and “SelectJobInfo” formats.
squeue - align print format for exit and derived codes with that of other
+components (<exit_status>:<signal_number>).
sacct - Add --array option to expand job arrays and display array tasks on
+separate lines.
Partial support for “--json” and “--yaml” formated outputs have been
+implemented for sacctmgr, sdiag, sinfo, squeue, and scontrol. The resultant
+data ouput will be filtered by normal command arguments. Formatting
+arguments will continue to be ignored.
salloc/sbatch/srun - extended the --nodes syntax to allow for a list of
+valid node counts to be allocated to the job. This also supports a "step
+count" value (e.g., --nodes=20-100:20 is equivalent to
+--nodes=20,40,60,80,100) which can simplify the syntax when the job needs
+to scale by a certain "chunk" size.
srun - add user requestible vnis with “--network=job_vni” option.
srun - add user requestible single node VNIs with the
+“--network=single_node_vni” option.
cgroup plugins - task_cgroup_devices_constrain() function signature removed
+pid_t pid.
task plugins - replace task_p_pre_set_affinity(), task_p_set_affinity(), and
+task_p_post_set_affinity() with task_p_pre_launch_priv() like it was back in
+slurm 20.11.
Allow for concurrent processing of job_submit_g_submit() and
+job_submit_g_modify() calls. If your plugin is not capable of concurrent
+operation you must add additional locking within your plugin.
Removed return value from slurm_list_append().
The List and ListIterator types have been removed in favor of list_t and
+list_itr_t respectively.
burst_buffer.lua - Pass UID and GID to most hooks. Pass job_info (detailed
+job information) to many hooks. See etc/burst_buffer.lua.example for a
+complete list of changes. WARNING: Backwards compatibility is broken for
+slurm_bb_get_status: UID and GID are passed before the variadic arguments.
+If UID and GID are not explicitly listed as arguments to
+slurm_bb_get_status(), then they will be included in the variadic arguments.
+Backwards compatibility is maintained for all other hooks because the new
+arguments are passed after the existing arguments.
node_features plugins - node_features_p_reboot_weight() function removed.
+node_features_p_job_valid() - added parameter feature_list.
+node_features_p_job_xlate() - added parameters feature_list and
+job_node_bitmap.
This section lists features and packages that were removed from SUSE Linux Enterprise for High-Performance Computing or will be removed in upcoming versions.
The following features and packages have been removed in this release.
Python 2 bindings for genders has been removed.
+These are now provided for Python 3.
Ganglia is not supported anymore in 15 SP4.
+It has been replaced with Grafana (https://grafana.com/)
Due to a lack of usage by customers, some library packages have been removed from the HPC module in SLE HPC 15 SP4. On SUSE Linux Enterprise you can build your own library using spack.
+These libraries will continue to be available through SUSE Package Hub.
+The following libraries have been removed:
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-hpc/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
a",n=d.getElementsByTagName("*")||[],r=d.getElementsByTagName("a")[0],!r||!r.style||!n.length)return t;s=a.createElement("select"),u=s.appendChild(a.createElement("option")),o=d.getElementsByTagName("input")[0],r.style.cssText="top:1px;float:left;opacity:.5",t.getSetAttribute="t"!==d.className,t.leadingWhitespace=3===d.firstChild.nodeType,t.tbody=!d.getElementsByTagName("tbody").length,t.htmlSerialize=!!d.getElementsByTagName("link").length,t.style=/top/.test(r.getAttribute("style")),t.hrefNormalized="/a"===r.getAttribute("href"),t.opacity=/^0.5/.test(r.style.opacity),t.cssFloat=!!r.style.cssFloat,t.checkOn=!!o.value,t.optSelected=u.selected,t.enctype=!!a.createElement("form").enctype,t.html5Clone="<:nav>"!==a.createElement("nav").cloneNode(!0).outerHTML,t.inlineBlockNeedsLayout=!1,t.shrinkWrapBlocks=!1,t.pixelPosition=!1,t.deleteExpando=!0,t.noCloneEvent=!0,t.reliableMarginRight=!0,t.boxSizingReliable=!0,o.checked=!0,t.noCloneChecked=o.cloneNode(!0).checked,s.disabled=!0,t.optDisabled=!u.disabled;try{delete d.test}catch(h){t.deleteExpando=!1}o=a.createElement("input"),o.setAttribute("value",""),t.input=""===o.getAttribute("value"),o.value="t",o.setAttribute("type","radio"),t.radioValue="t"===o.value,o.setAttribute("checked","t"),o.setAttribute("name","t"),l=a.createDocumentFragment(),l.appendChild(o),t.appendChecked=o.checked,t.checkClone=l.cloneNode(!0).cloneNode(!0).lastChild.checked,d.attachEvent&&(d.attachEvent("onclick",function(){t.noCloneEvent=!1}),d.cloneNode(!0).click());for(f in{submit:!0,change:!0,focusin:!0})d.setAttribute(c="on"+f,"t"),t[f+"Bubbles"]=c in e||d.attributes[c].expando===!1;d.style.backgroundClip="content-box",d.cloneNode(!0).style.backgroundClip="",t.clearCloneStyle="content-box"===d.style.backgroundClip;for(f in x(t))break;return t.ownLast="0"!==f,x(function(){var n,r,o,s="padding:0;margin:0;border:0;display:block;box-sizing:content-box;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;",l=a.getElementsByTagName("body")[0];l&&(n=a.createElement("div"),n.style.cssText="border:0;width:0;height:0;position:absolute;top:0;left:-9999px;margin-top:1px",l.appendChild(n).appendChild(d),d.innerHTML="
diff --git a/sle-hpc-15_SP5/html/release-notes/index.html b/sle-hpc-15_SP5/html/release-notes/index.html
new file mode 120000
index 0000000..43e2831
--- /dev/null
+++ b/sle-hpc-15_SP5/html/release-notes/index.html
@@ -0,0 +1 @@
+release-notes.html
\ No newline at end of file
diff --git a/sle-hpc-15_SP5/html/release-notes/release-notes.html b/sle-hpc-15_SP5/html/release-notes/release-notes.html
new file mode 100644
index 0000000..3d2babf
--- /dev/null
+++ b/sle-hpc-15_SP5/html/release-notes/release-notes.html
@@ -0,0 +1,398 @@
+
+Release Notes | SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise for High-Performance Computing is a highly-scalable, high-performance open-source operating system designed to utilize the power of parallel computing. This document provides an overview of high-level general features, capabilities, and limitations of SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease) and important product updates.
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.
2 SUSE Linux Enterprise for High-Performance Computing#
SUSE Linux Enterprise for High-Performance Computing is a highly scalable, high performance open-source operating system designed to utilize the power of parallel computing for modeling, simulation and advanced analytics workloads.
SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease) provides tools and libraries related to High Performance Computing. This includes:
Workload manager
Remote and parallel shells
Performance monitoring and measuring tools
Serial console monitoring tool
Cluster power management tool
A tool for discovering the machine hardware topology
System monitoring
A tool for monitoring memory errors
A tool for determining the CPU model and its capabilities (x86-64 only)
User-extensible heap manager capable of distinguishing between different kinds of memory (x86-64 only)
Serial and parallel computational libraries providing the common standards BLAS, LAPACK, …
Various MPI implementations
Serial and parallel libraries for the HDF5 file format
SUSE Linux Enterprise for High-Performance Computing is backed by award-winning support from SUSE, an established technology leader with a proven history of delivering enterprise-quality support services.
SUSE Linux Enterprise for High-Performance Computing 15 has a 13-year life cycle, with 10 years of General Support and 3 years of Extended Support.
+The current version (SP5) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise for High-Performance Computing 15 SP6.
Any release package is fully maintained and supported until the availability of the next release.
Extended Service Pack Overlay Support (ESPOS) and Long Term Service Pack Support (LTSS) are also available for this product. If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support (LTSS) can extend the support you get by an additional 12 to 36 months in 12-month increments, providing a total of 3 to 5 years of support on any given Service Pack.
Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
L2
Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
L3
Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.
For contracted customers and partners, SUSE Linux Enterprise for High-Performance Computing is delivered with L3 support for all packages, except for the following:
Certain software delivered as part of SUSE Linux Enterprise for High-Performance Computing may require an external contract.
+Check the support status of individual packages using the RPM metadata that can be viewed with rpm, zypper, or YaST.
SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease) (and the SUSE Linux Enterprise modules) includes the following software that is shipped only under a GNU AGPL software license:
Ghostscript (including subpackages)
SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease) (and the SUSE Linux Enterprise modules) includes the following software that is shipped under multiple licenses that include a GNU AGPL software license:
Get the detailed change log information about a particular package from the RPM (where FILENAME.rpm is the name of the RPM):
rpm --changelog -qp FILENAME.rpm
Check the ChangeLog file 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 docu directory of the installation medium of SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease).
+This directory includes PDF versions of the SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease) Installation Quick Start Guide.
For the most up-to-date version of the documentation for SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease), see https://susedoc.github.io/sle-hpc/main (draft version).
This section comprises information about modules and extensions for SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease)
+Modules and extensions add functionality to the system.
3.1 Modules in the SLE 15 SP5 (prerelease) product line#
The SLE 15 SP5 (prerelease) product line is made up of modules that contain software packages. Each module has a clearly defined scope. Modules differ in their life cycles and update timelines.
The modules available within the product line based on SUSE Linux Enterprise 15 SP5 (prerelease) at the release of SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease) are listed in the Modules and Extensions Quick Start at https://documentation.suse.com/sles/15-SP3/html/SLES-all/article-modules.html.
Not all SLE modules are available with a subscription for SUSE Linux Enterprise for High-Performance Computing 15 SP5 (prerelease) itself (see the column Available for).
The following extension is not covered by SUSE support agreements, available at no additional cost and without an extra registration key: SUSE Package Hub, see https://packagehub.suse.com/.
This sections lists related products. Usually, these products have their own release notes documents that are available from https://www.suse.com/releasenotes.
Technology previews are packages, stacks, or features delivered by SUSE which are not supported.
+They may be functionally incomplete, unstable or in other ways not suitable for production use.
+They are included for your convenience and give you a chance to test new technologies within an enterprise environment.
Whether a technology preview becomes a fully supported technology later depends on customer and market feedback.
+Technology previews can be dropped at any time and SUSE does not commit to providing a supported version of such technologies in the future.
Give your SUSE representative feedback about technology previews, including your experience and use case.
SUSE Linux Enterprise for High-Performance Computing for Arm 12 SP2 and later kernels have used a page size of 4K.
+This offers the widest compatibility also for small systems with little RAM,
+allowing to use Transparent Huge Pages (THP) where large pages make sense.
As a technology preview, SUSE Linux Enterprise for High-Performance Computing for Arm 15 SP5 (prerelease) adds a kernel flavor
+64kb, offering a page size of 64 KiB and physical/virtual address size
+of 52 bits.
+Same as the default kernel flavor, it does not use preemption.
Main purpose at this time is to allow for side-by-side benchmarking for
+High Performance Computing, Machine Learning and other Big Data use cases.
+Contact your SUSE representative if you notice performance gains
+for your specific workloads.
Important: Swap needs to be re-initialized
After booting the 64K kernel, any swap partitions need to re-initialized to be usable.
+To do this, run the swapon command with the --fixpgsz parameter on the swap partition.
+Note that this process deletes data present in the swap partition (for example, suspend data).
+In this example, the swap partition is on /dev/sdc1:
swapon --fixpgsz /dev/sdc1
Important: Btrfs file system uses page size as block size
It is currently not possible to use Btrfs file systems across page sizes.
+Block sizes below page size are not yet supported and block sizes above
+page size might never be supported.
During installation, change the default partitioning proposal and choose
+another file system, such as Ext4 or XFS, to allow rebooting from the
+default 4K page size kernel of the Installer into kernel-64kb and back.
See the Storage Guide for a discussion of supported file systems.
Warning: RAID 5 uses page size as stripe size
It is currently not yet possible to configure stripe size on volume creation.
+This will lead to sub-optimal performance if page size and block size differ.
Avoid RAID 5 volumes when benchmarking 64K vs. 4K page size kernels.
See the Storage Guide for more information on software RAID.
The HPC module contains HPC specific packages. These include the workload manager Slurm, the node deployment tool clustduct, munge for user authentication, the remote shell mrsh, the parallel shell pdsh, as well as numerous HPC libraries and frameworks.
This module is available with the SUSE Linux Enterprise for High-Performance Computing only. It is selected by default during the installation. It can be added or removed using the YaST UI or the SUSEConnect CLI tool. Refer to the system administration guide for further details.
The NVIDIA Compute Module provides the NVIDIA CUDA repository for SUSE Linux Enterprise 15. Note that that any software within this repository is under a 3rd party EULA. For more information check https://docs.nvidia.com/cuda/eula/index.html.
This module is not selected for addition by default when installing SUSE Linux Enterprise for High-Performance Computing. It may be selected manually during installation from the Extension and Modules screen. You may also select it on an installed system using YaST. To do so, run from a shell as root yast registration, select: Select Extensions and search for NVIDIA Compute Module and press Next.
Important
Do not attempt to add this module with the SUSEConnect CLI tool. This tool is not yet capable of handling 3rd party repositories.
Once you have selected this module you will be asked to confirm the 3rd party license and verify the repository signing key.
As of 15 SP5 (prerelease), SUSE Linux Enterprise for High-Performance Computing is no longer a separate product. As a result:
the HPC Module can now be enabled in SUSE Linux Enterprise Server
when migrating from SUSE Linux Enterprise for High-Performance Computing 15 SP3, SP4, and SP5, only SUSE Linux Enterprise Server 15 SP6 will be available as migration target.
+The result of such a migration will be an installation of SUSE Linux Enterprise Server with all the previously enabled modules.
6.2 Enriched system visibility in the SUSE Customer Center (SCC)#
SUSE is committed to helping provide better insights into the consumption of SUSE subscriptions regardless of where they are running or how they are managed; physical or virtual, on-prem or in the cloud, connected to SCC or Repository Mirroring Tool (RMT), or managed by SUSE Manager.
+To help you identify or filter out systems in SCC that are no longer running or decommissioned, SUSEConnect now features a daily “ping”, which will update system information automatically.
Installing the following packages automatically opens the following ports:
dolly - TCP ports 9997 and 9998
slurm - TCP ports 6817, 6818, and 6819
Important
These release notes only document changes in SUSE Linux Enterprise for High-Performance Computing compared to the immediate previous service pack of SUSE Linux Enterprise for High-Performance Computing.
+The full changes and fixes can be found on the respective web site of the packages.
SLE HPC 15 SP5 (prerelease) now supports the GNU compiler suite version 12.
+To install the runtime environments (environment modules) for version 12, run: zypper install gnu12-compilers-hpc.
+To install all the packages required for development (C, C and Fortran compilers), run `zypper install gnu12-compilers-hpc-devel`.
+To load the environment, run 'module load gnu/12' in your shell.
+When the `-devel` package is installed, the compilers (`gcc-12`, `g-12`, gfortran-12) will become available in this shell under their standard names (gcc, g++, gfortran).
Add option --miniConfig to report configuration differences from default.
Move cache file location from ~/.lmod.d/.cache/* to ~/.cache/lmod/*
Transitional support for using ~/.config/lmod for collections. Currently collect are written to both ~/.lmod.d/ and ~/.config/lmod.
setenv and pushenv change local environment when running spider (and avail).
Allow bash users to export SUPPORT_KSH=no so that they can avoid bash startup setting FPATH
Add --location option to show to write to stderr the file location.
Only rebuild spider caches if there are any loaded or pending modules. module avail <name1> <name2> … now only prints matching aliases. Search names are resolved.
Print dataT table when there is an Exception.
New command added: module overview.
Add spiderPathFilter hook so that sites can control what paths are kept or ignored.
Added $LMOD_SITE_MODULEPATH support to prepend to MODULEPATH
Add support for sh_to_modulefile to support zsh, ksh, bash and tcsh with aliases and shell functions
Support for source_sh added. Now support more than one shell script per modulefile.
Added "intel_gpu" component with monitoring capabilities support for Intel GPUs, including GPU hardware events and memory performance metrics.
Added "sysdetect" component for detecting a machine’s architectural details. Additionally, PAPI offers a new API that enables users to get "sysdetect" details from within their application.
A major redesign of the "rocm" component for advanced monitoring features for the latest AMD GPUs. The PAPI "rocm" component is now thread-safe.
Support for NVIDIA compute capability 7.0 and greater. This implies support for CUPTI’s new Profiling and Perfworks APIs.
Significant redesign of the "sde" component into two separate entities:
a standalone library "libsde" with a new API for software developers to define software-based metrics from within their applications
the PAPI "sde" component that enables monitoring of these new software-based events.
New C++ interface for "libsde," which enables software developers to define software-defined events from within their C++ applications.
New Counter Analysis Toolkit (CAT) benchmarks and refinements of PAPI’s CAT data analysis.
warewulf4 is a popular SLE for HPC deployment tool whose latest version is a full rewrite in the Go programming language.
+It is applying lessons learned from its predecessors.
+It deploys minimal images which it obtains from container images stored in a registry and performs a minimal configuration for the image to be useful as a compute node image in a cluster. warewulf4 is deprecating the former deployment tool clustduct.
6.15 Creating containers from current HPC environment#
Usually users use environment modules to adjust their environment (that is, environment variables like PATH, LD_LIBRARY_PATH, MANPATH etc.) to pick exactly the tools and libraries they need for their work.
+The same can be achieved with containers by including only those components in a container that are part of this environment.
+This functionality is now provided using the spack and singularity applications.
Spack’s traditional
+package
+preferences are soft, but we’ve added hard requriements to
+packages.yaml and spack.yaml . Package requirements use the same
+syntax as specs:
spack install in an environment will no longer add to the specs:
+list; you’ll need to either use spack add <spec> or
+spack install --add <spec>.
Similarly, spack uninstall will not remove from your environment’s
+specs: list; you’ll need to use spack remove or
+spack uninstall --remove.
This will make it easier to manage an environment, as there is clear
+separation between the stack to be installed (spack.yaml/spack.lock)
+and which parts of it should be installed (spack install /
+spack uninstall).
concretizer:unify:true is now the default mode for new environments
We see more users creating unify:true environments now. Users who need
+unify:false can add it to their environment to get the old behavior.
+This will concretize every spec in the environment independently.
Include environment configuration from URLs (
+docs)
You can now include configuration in your environment directly from a
+URL:
Currently, compiler flags and variants are inconsistent: compiler flags
+set for a package are inherited by its dependencies, while variants are
+not. We should have these be consistent by allowing for inheritance to
+be enabled or disabled for both variants and compiler flags.
Example syntax:
+* package ++variant: enabled variant that will be propagated to
+dependencies
+* package +variant: enabled variant that will NOT be propagated to
+dependencies
+* package ~~variant: disabled variant that will be propagated to
+dependencies
+* package ~variant: disabled variant that will NOT be propagated to
+dependencies
+* package cflags==-g: cflags will be propagated to dependencies
+* package cflags=-g: cflags will NOT be propagated to dependencies
+
+Syntax for non-boolan variants is similar to compiler flags. More in the
+docs for
+variants
+and
+compiler
+flags.
Enhancements to git version specifiers
v0.18.0 added the ability to use git commits as versions. You can
+now use the git. prefix to specify git tags or branches as versions.
+All of these are valid git versions in v0.19 :
foo@abcdef1234abcdef1234abcdef1234abcdef1234 # raw commit
+foo@git.abcdef1234abcdef1234abcdef1234abcdef1234 # commit with git prefix
+foo@git.develop # the develop branch
+foo@git.0.19 # use the 0.19 tag
v0.19 also gives you more control over how Spack interprets git
+versions, in case Spack cannot detect the version from the git
+repository. You can suffix a git version with =<version> to force
+Spack to concretize it as a particular version :
# use mybranch, but treat it as version 3.2 for version comparison
+foo@git.mybranch=3.2
+
+# use the given commit, but treat it as develop for version comparison
+foo@git.abcdef1234abcdef1234abcdef1234abcdef1234=develop
Cray machines have historically had their own platform within Spack,
+because we needed to go through the module system to leverage compilers
+and MPI installations on these machines. The Cray EX programming
+environment now provides standalone craycc executables and proper
+mpicc wrappers, so Spack can treat EX machines like Linux with extra
+packages .
We expect this to greatly reduce bugs, as external packages and
+compilers can now be used by prefix instead of through modules. We will
+also no longer be subject to reproducibility issues when modules change
+from Cray PE release to release and from site to site. This also
+simplifies dealing with the underlying Linux OS on cray systems, as
+Spack will properly model the machine’s OS as either SuSE or RHEL.
Improvements to tests and testing in CI
spack ci generate --tests will generate a .gitlab-ci.yml file that
+not only does builds but also runs tests for built packages . Public
+GitHub pipelines now also run tests in CI.
spack test run --explicit will only run tests for packages that are
+explicitly installed, instead of all packages.
Experimental binding link model
You can add a new option to config.yaml to make Spack embed absolute
+paths to needed shared libraries in ELF executables and shared libraries
+on Linux (
+docs):
This can improve launch time at scale for parallel applications, and it
+can make installations less susceptible to environment variables like
+LD_LIBRARY_PATH, even especially when dealing with external libraries
+that use RUNPATH. You can think of this as a faster, even
+higher-precedence version of RPATH.
Support for Python 3.5 is dropped . Only Python 2.7 and 3.6+ are
+officially supported.
This is the last Spack release that will support Python 2 . Spack
+v0.19 will emit a deprecation warning if you run it with Python 2, and
+Python 2 support will soon be removed from the develop branch.
LD_LIBRARY_PATH is no longer set by default by spack load or
+module loads.
Setting LD_LIBRARY_PATH in Spack environments/modules can cause
+binaries from outside of Spack to crash, and Spack’s own builds use
+RPATH and do not need LD_LIBRARY_PATH set in order to run. If you
+still want the old behavior, you can run these commands to configure
+Spack to set LD_LIBRARY_PATH:
The spack:concretization:[together|separately] has been removed
+after being deprecated in v0.18. Use concretizer:unify:[true|false].
config:module_roots is no longer supported after being deprecated in
+v0.18. Use configuration in module sets instead (
+docs).
spack activate and spack deactivate are no longer supported,
+having been deprecated in v0.18. Use an environment with a view
+instead of activating/deactivating
+(docs).
The old YAML format for buildcaches is now deprecated . If you are
+using an old buildcache with YAML metadata you will need to regenerate
+it with JSON metadata.
spack bootstrap trust and spack bootstrap untrust are deprecated
+in favor of spack bootstrap enable and spack bootstrap disable and
+will be removed in v0.20.
The graviton2 architecture has been renamed to neoverse_n1, and
+graviton3 is now neoverse_v1. Buildcaches using the old architecture
+names will need to be rebuilt.
The terms blacklist and whitelist have been replaced with
+include and exclude in all configuration files . You can use
+spack config update to automatically fix your configuration files.
spack install --reuse was introduced in v0.17.0, and --reuse is
+now the default concretization mode. Spack will try hard to resolve
+dependencies using installed packages or binaries .
To avoid reuse and to use the latest package configurations, (the old
+default), you can use spack install --fresh, or add configuration like
+this to your environment or concretizer.yaml:
concretizer:
+ reuse: false
Finer-grained hashes
Spack hashes now include link, run, andbuild dependencies, as
+well as a canonical hash of package recipes. Previously, hashes only
+included link and run dependencies (though build dependencies were
+stored by environments). We coarsened the hash to reduce churn in user
+installations, but the new default concretizer behavior mitigates this
+concern and gets us reuse and provenance. You will be able to see the
+build dependencies of new installations with spack find. Old
+installations will not change and their hashes will not be affected.
Improved error messages
Error handling with the new concretizer is now done with optimization
+criteria rather than with unsatisfiable cores, and Spack reports many
+more details about conflicting constraints.
Unify environments when possible
Environments have thus far supported concretization: together or
+concretization: separately. These have been replaced by a new
+preference in concretizer.yaml:
concretizer:
+ unify: [true|false|when_possible]
concretizer:unify:when_possible will try to resolve a fully unified
+environment, but if it cannot, it will create multiple configurations of
+some packages where it has to. For large environments that previously
+had to be concretized separately, this can result in a huge speedup
+(40-50x).
Automatically find externals on Cray machines
Spack can now automatically discover installed packages in the Cray
+Programming Environment by running spack external find (or
+spack external read-cray-manifest to only query the PE). Packages
+from the PE (e.g., cray-mpich are added to the database with full
+dependency information, and compilers from the PE are added to
+compilers.yaml. Available with the June 2022 release of the Cray
+Programming Environment.
New binary format and hardened signing
Spack now has an updated binary format, with improvements for security.
+The new format has a detached signature file, and Spack verifies the
+signature before untarring or decompressing the binary package. The
+previous format embedded the signature in a tar file, which required
+the client to run tarbefore verifying . Spack can still install
+from build caches using the old format, but we encourage users to switch
+to the new format going forward.
Production GitLab pipelines have been hardened to securely sign
+binaries. There is now a separate signing stage so that signing keys are
+never exposed to build system code, and signing keys are ephemeral and
+only live as long as the signing pipeline stage.
Bootstrap mirror generation
The spack bootstrap mirror command can automatically create a mirror
+for bootstrapping the concretizer and other needed dependencies in an
+air-gapped environment.
Makefile generation
spack env depfile can be used to generate a Makefile from an
+environment, which can be used to build packages the environment in
+parallel on a single node. e.g.:
spack -e myenv env depfile > Makefile
+make
Spack propagates gmake jobserver information to builds so that their
+jobs can share cores.
New variant features
In addition to being conditional themselves, variants can now have
+conditional
+values that are only possible for certain configurations of a
+package.
Variants can be
+declared sticky, which prevents them from being enabled or disabled by the
+concretizer. Sticky variants must be set explicitly by users on the
+command line or in packages.yaml.
6.17.1 Important Notes on Upgrading Slurm from a Previous Version#
If using the slurmdbd (Slurm DataBase Daemon) you must update this first.
If using a backup DBD you must start the primary first to do any
+database conversion, the backup will not start until this has happened.
The 23.02 slurmdbd will work with Slurm daemons of version 21.08 and above.
+You will not need to update all clusters at the same time, but it is very
+important to update slurmdbd first and having it running before updating
+any other clusters making use of it.
Slurm can be upgraded from version 22.05 to version 23.02 without loss
+of jobs or other state information. Upgrading directly from an earlier version
+of Slurm will result in loss of state information.
All SPANK plugins must be recompiled when upgrading from any Slurm version
+prior to 23.02.
slurmctld - Add new RPC rate limiting feature. This is enabled through
+SlurmctldParameters=rl_enable, otherwise disabled by default.
Make scontrol reconfigure and sending a SIGHUP to the slurmctld behave the
+same. If you were using SIGHUP as a 'lighter' scontrol reconfigure to rotate
+logs please update your scripts to use SIGUSR2 instead.
Change cloud nodes to show by default. PrivateData=cloud is no longer
+needed.
sreport - Count planned (FKA reserved) time for jobs running in IGNORE_JOBS
+reservations. Previously was lumped into IDLE time.
job_container/tmpfs - Support running with an arbitrary list of private
+mount points (/tmp and /dev/shm are the default, but not required).
job_container/tmpfs - Set more environment variables in InitScript.
Make all cgroup directories created by Slurm owned by root. This was the
+behavior in cgroup/v2 but not in cgroup/v1 where by default the step
+directories ownership were set to the user and group of the job.
accounting_storage/mysql - change purge/archive to calculate record ages
+based on end time, rather than start or submission times.
job_submit/lua - add support for log_user() from slurm_job_modify().
Run the following scripts in slurmscriptd instead of slurmctld:
+ResumeProgram, ResumeFailProgram, SuspendProgram, ResvProlog, ResvEpilog,
+and RebootProgram (only with SlurmctldParameters=reboot_from_controller).
Only permit changing log levels with srun --slurmd-debug by root
+or SlurmUser.
slurmctld will fatal() when reconfiguring the job_submit plugin fails.
Add PowerDownOnIdle partition option to power down nodes after nodes become
+idle.
Add “[jobid.stepid]” prefix from slurmstepd and “slurmscriptd” prefix from
+slurmcriptd to Syslog logging. Previously was only happening when logging
+to a file.
Add purge and archive functionality for job environment and job batch script
+records.
Extend support for Include files to all "configless" client commands.
Make node weight usable for powered down and rebooting nodes.
Removed “launch” plugin.
Add “Extra” field to job to store extra information other than a comment.
Add usage gathering for AMD (requires ROCM 5.5+) and NVIDIA gpus.
Add job’s allocated nodes, features, oversubscribe, partition, and
+reservation to SLURM_RESUME_FILE output for power saving.
Automatically create directories for stdout/stderr output files. Paths may
+use %j and related substitution characters as well.
Add --tres-per-task to salloc/sbatch/srun.
Allow nodefeatures plugin features to work with cloud nodes.
+e.g. - Powered down nodes have no active changeable features.
Nodes can’t be changed to other active features until powered down.
Active changeable features are reset/cleared on power down.
Make slurmstepd cgroups constrained by total configured memory from
+slurm.conf (NodeName=<> RealMemory=#) instead of total physical memory.
node_features/helpers - add support for the OR and parentheses operators
+in a --constraint expression.
slurmctld will fatal() when [Prolog|Epilog]Slurmctld are defined but are not
+executable.
Validate node registered active features are a super set of node’s
+currently active changeable features.
On clusters without any PrologFlags options, batch jobs with failed prologs
+nolonger generate an output file.
Add SLURM_JOB_START_TIME and SLURM_JOB_END_TIME environment variables.
Add SuspendExcStates option to slurm.conf to avoid suspending/powering down
+specific node states.
Add support for DCMI power readings in IPMI plugin.
slurmrestd served /slurm/v0.0.39 and /slurmdb/v0.0.39 endpoints had major
+changes from prior versions. Almost all schemas have been renamed and
+modified. Sites using OpenAPI Generator clients are highly suggested to
+upgrade to to using atleast version 6.x due to limitations with prior
+versions.
Allow for --nodelist to contain more nodes than required by --nodes.
Rename “nodes” to “nodes_resume” in SLURM_RESUME_FILE job output.
Rename “all_nodes” to “all_nodes_resume” in SLURM_RESUME_FILE output.
Add jobcomp/kafka plugin.
Add new PreemptParameters=reclaim_licenses option which will allow higher
+priority jobs to preempt jobs to free up used licenses. (This is only
+enabled for with PreemptModes of CANCEL and REQUEUE, as Slurm cannot
+guarantee suspended jobs will release licenses correctly.)
hpe/slingshot - add support for the instant-on feature.
Add ability to update SuspendExc* parameters with scontrol.
Add ability to restore SuspendExc* parameters on restart with slurmctld -R
+option.
Add ability to clear a GRES specification by setting it to "0" via
+“scontrol update job”.
Add SLURM_JOB_OVERSUBSCRIBE environment variable for Epilog, Prolog,
+EpilogSlurmctld, PrologSlurmctld, and mail ouput.
System node down reasons are appended to existing reasons, separated by ':'.
New command scrun has been added. scrun acts as an Open Container Initiative
+(OCI) runtime proxy to run containers seamlessly via Slurm.
Fixed GpuFreqDef option. When set in slurm.conf, it will be used if
+--gpu-freq was not explicitly set by the job step.
6.17.3 Configuration File Changes (see appropriate man page for details)#
job_container.conf - Added “Dirs” option to list desired private mount
+points.
node_features plugins - invalid users specified for AllowUserBoot will now
+result in fatal() rather than just an error.
Deprecate AllowedKmemSpace, ConstrainKmemSpace, MaxKmemPercent, and
+MinKmemSpace.
Allow jobs to queue even if the user is not in AllowGroups when
+EnforcePartLimits=no is set. This ensures consistency for all the Partition
+access controls, and matches the documented behavior for EnforcePartLimits.
Add InfluxDBTimeout parameter to acct_gather.conf.
job_container/tmpfs - add support for expanding %h and %n in BasePath.
slurm.conf - Removed SlurmctldPlugstack option.
Add new SlurmctldParameters=validate_nodeaddr_threads=<number> option to
+allow concurrent hostname resolution at slurmctld startup.
Add new AccountingStoreFlags=job_extra option to store a job’s extra field
+in the database.
Add new “defer_batch” option to SchedulerParameters to only defer
+scheduling for batch jobs.
Add new DebugFlags option “JobComp” to replace “Elasticsearch”.
Add configurable job requeue limit parameter - MaxBatchRequeue - in
+slurm.conf to permit changes from the old hard-coded value of 5.
helpers.conf - Allow specification of node specific features.
helpers.conf - Allow many features to one helper script.
job_container/tmpfs - Add “Shared” option to support shared namespaces.
+This allows autofs to work with the job_container/tmpfs plugin when enabled.
acct_gather.conf - Added EnergyIPMIPowerSensors=Node=DCMI and
+Node=DCMI_ENHANCED.
Add new “getnameinfo_cache_timeout=<number>” option to
+CommunicationParameters to adjust or disable caching the results of
+getnameinfo().
Add new PrologFlags=ForceRequeueOnFail option to automatically requeue
+batch jobs on Prolog failures regardless of the job --requeue setting.
Add HealthCheckNodeState=NONDRAINED_IDLE option.
Add “explicit” to Flags in gres.conf. This makes it so the gres is not
+automatically added to a job’s allocation when --exclusive is used. Note
+that this is a per-node flag.
Moved the “preempt_” options from SchedulerParameters to PreemptParameters,
+and dropped the prefix from the option names. (The old options will still
+be parsed for backwards compatibility, but are now undocumented.)
Add LaunchParameters=ulimit_pam_adopt, which enables setting RLIMIT_RSS in
+adopted processes.
Update SwitchParameters=job_vni to enable/disable creating job VNIs for all
+jobs, or when a user requests them.
Update SwitchParameters=single_node_vni to enable/disable creating single
+node VNIs for all jobs, or when a user requests them.
Add ability to preserve SuspendExc* parameters on reconfig with
+ReconfigFlags=KeepPowerSaveSettings.
slurmdbd.conf - Add new AllResourcesAbsolute to force all new resources
+to be created with the Absolute flag.
topology/tree - Add new TopologyParam=SwitchAsNodeRank option to reorder
+nodes based on switch layout. This can be useful if the naming convention
+for the nodes does not natually map to the network topology.
Removed the default setting for GpuFreqDef. If unset, no attempt to change
+the GPU frequency will be made if --gpu-freq is not set for the step.
6.17.4 Command Changes (see man pages for details)#
sacctmgr - no longer force updates to the AdminComment, Comment, or
+SystemComment to lower-case.
sinfo - Add -F/--future option to sinfo to display future nodes.
sacct - Rename “Reserved” field to “Planned” to match sreport and the
+nomenclature of the 'Planned' node.
scontrol - advanced reservation flag MAINT will no longer replace nodes,
+similar to STATIC_ALLOC
sbatch - add parsing for #PBS -d and #PBS -w.
scontrol show assoc_mgr will show username(uid) instead of uid in
+QoS section.
Add strigger --draining and -R/--resume options.
Change --oversubscribe and --exclusive to be mutually exclusive for job
+submission. Job submission commands will now fatal if both are set.
+Previously, these options would override each other, with the last one in
+the job submission command taking effect.
scontrol - Requested TRES and allocated TRES will now always be printed when
+showing jobs, instead of one TRES output that was either the requested or
+allocated.
srun --ntasks-per-core now applies to job and step allocations. Now, use of
+--ntasks-per-core=1 implies --cpu-bind=cores and --ntasks-per-core>1 implies
+--cpu-bind=threads.
salloc/sbatch/srun - Check and abort if ntasks-per-core > threads-per-core.
scontrol - Add ResumeAfter=<secs> option to “scontrol update nodename=”.
Add a new “nodes=” argument to scontrol setdebug to allow the debug level
+on the slurmd processes to be temporarily altered.
Add a new “nodes=” argument to “scontrol setdebugflags” as well.
Make it so scrontab prints client-side the job_submit() error messsage (which can
+be set i.e. by using the log_user() function for the lua plugin).
scontrol - Reservations will not be allowed to have STATIC_ALLOC or MAINT
+flags and REPLACE[_DOWN] flags simultaneously.
scontrol - Reservations will only accept one reoccurring flag when
+being created or updated.
scontrol - A reservation cannot be updated to be reoccurring if it is
+already a floating reservation.
squeue - removed unused “%s” and “SelectJobInfo” formats.
squeue - align print format for exit and derived codes with that of other
+components (<exit_status>:<signal_number>).
sacct - Add --array option to expand job arrays and display array tasks on
+separate lines.
Partial support for “--json” and “--yaml” formated outputs have been
+implemented for sacctmgr, sdiag, sinfo, squeue, and scontrol. The resultant
+data ouput will be filtered by normal command arguments. Formatting
+arguments will continue to be ignored.
salloc/sbatch/srun - extended the --nodes syntax to allow for a list of
+valid node counts to be allocated to the job. This also supports a "step
+count" value (e.g., --nodes=20-100:20 is equivalent to
+--nodes=20,40,60,80,100) which can simplify the syntax when the job needs
+to scale by a certain "chunk" size.
srun - add user requestible vnis with “--network=job_vni” option.
srun - add user requestible single node VNIs with the
+“--network=single_node_vni” option.
cgroup plugins - task_cgroup_devices_constrain() function signature removed
+pid_t pid.
task plugins - replace task_p_pre_set_affinity(), task_p_set_affinity(), and
+task_p_post_set_affinity() with task_p_pre_launch_priv() like it was back in
+slurm 20.11.
Allow for concurrent processing of job_submit_g_submit() and
+job_submit_g_modify() calls. If your plugin is not capable of concurrent
+operation you must add additional locking within your plugin.
Removed return value from slurm_list_append().
The List and ListIterator types have been removed in favor of list_t and
+list_itr_t respectively.
burst_buffer.lua - Pass UID and GID to most hooks. Pass job_info (detailed
+job information) to many hooks. See etc/burst_buffer.lua.example for a
+complete list of changes. WARNING: Backwards compatibility is broken for
+slurm_bb_get_status: UID and GID are passed before the variadic arguments.
+If UID and GID are not explicitly listed as arguments to
+slurm_bb_get_status(), then they will be included in the variadic arguments.
+Backwards compatibility is maintained for all other hooks because the new
+arguments are passed after the existing arguments.
node_features plugins - node_features_p_reboot_weight() function removed.
+node_features_p_job_valid() - added parameter feature_list.
+node_features_p_job_xlate() - added parameters feature_list and
+job_node_bitmap.
The --uid option for the srun command is broken: its use may lead to the error message job <job ID> queued and waiting for resources.
+This does not, however, affect the sbatch command.
This section lists features and packages that were removed from SUSE Linux Enterprise for High-Performance Computing or will be removed in upcoming versions.
dapl, rds-tools, and imgen are being deprecated due to lack of upstream activity.
openmpi 2 and openmpi 3 are being deprecated due to being replaced by openmpi 4.
The following features and packages have been removed in this release.
Python 2 bindings for genders has been removed.
+These are now provided for Python 3.
Ganglia is not supported anymore in 15 SP5 (prerelease).
+It has been replaced with Grafana (https://grafana.com/)
Due to a lack of usage by customers, some library packages have been removed from the HPC module in SLE HPC 15 SP5 (prerelease). On SUSE Linux Enterprise you can build your own library using spack.
+These libraries will continue to be available through SUSE Package Hub.
+The following libraries have been removed:
The following features and packages are deprecated and will be removed in a future version of SUSE Linux Enterprise for High-Performance Computing.
clustduct is deprecated and will be removed in SUSE Linux Enterprise for High-Performance Computing 15 SP6.
+With SLE HPC 15 SP5 (prerelease), warewulf4 has been introduced as cluster deployment tool, and users are advised to migrate to it.
This SUSE product includes materials licensed to SUSE under the GNU
+General Public License (GPL).
+The GPL requires SUSE to provide the source code that corresponds to the
+GPL-licensed material.
+The source code is available for download at https://www.suse.com/download/sle-hpc/ on Medium 2.
+For up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code.
+Send requests by e-mail to sle_source_request@suse.com.
+SUSE may charge a reasonable fee to recover distribution costs.
SUSE makes no representations or warranties with regard to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.
Further, SUSE makes no representations or warranties with regard to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
+Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries.
+You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables.
+You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws.
+You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses.
+Refer to https://www.suse.com/company/legal/ for more information on exporting SUSE software.
+SUSE assumes no responsibility for your failure to obtain any necessary export approvals.
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.
diff --git a/sle-hpc-15_SP6/html/release-notes/index.html b/sle-hpc-15_SP6/html/release-notes/index.html
new file mode 120000
index 0000000..43e2831
--- /dev/null
+++ b/sle-hpc-15_SP6/html/release-notes/index.html
@@ -0,0 +1 @@
+release-notes.html
\ No newline at end of file
diff --git a/sle-hpc-15_SP6/html/release-notes/release-notes.html b/sle-hpc-15_SP6/html/release-notes/release-notes.html
new file mode 100644
index 0000000..b008d69
--- /dev/null
+++ b/sle-hpc-15_SP6/html/release-notes/release-notes.html
@@ -0,0 +1,398 @@
+
+Release Notes | SUSE Linux Enterprise for High-Performance Computing 15 SP6 (prerelease)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
SUSE Linux Enterprise for High-Performance Computing is a highly-scalable, high-performance open-source operating system designed to utilize the power of parallel computing. This document provides an overview of high-level general features, capabilities, and limitations of SUSE Linux Enterprise for High-Performance Computing 15 SP6 (prerelease) and important product updates.
![](\"bug-report.svg\")
"
+ + bug_svg
+ + "