From bd69d0b0e5cc2d6f4983307a5b2c3befa0cb0946 Mon Sep 17 00:00:00 2001 From: Christoph Wickert Date: Mon, 9 Sep 2024 09:24:42 +0200 Subject: [PATCH] Modules: reformat with daps-xmlformat --- xml/art_modules.xml | 3109 +++++++++++++++++++++---------------------- 1 file changed, 1538 insertions(+), 1571 deletions(-) diff --git a/xml/art_modules.xml b/xml/art_modules.xml index 3cd53f7866..2d1fbca948 100644 --- a/xml/art_modules.xml +++ b/xml/art_modules.xml @@ -7,7 +7,6 @@ %entities; ]> -
&modulesquick; - &productnumber; - &productname; - + &productnumber;&productname; + &abstract_modulesquick; @@ -30,13 +28,10 @@ Products & Solutions How to use the modules and extensions available for the &sle; family Use modules and extensions for &slea; - - Administration - Installation + AdministrationInstallation - - 2024-06-26 + 2024-06-26 Updated for the initial release of &productname; &productnumber;. @@ -46,1431 +41,1417 @@ - Introduction to modules and extensions - - Starting with &productname; 15, the installation medium consists of only the - &leanos;: a minimal system for deploying, updating and registering - &productname;. During deployment, you can add functionality by selecting - modules and extensions to be installed on top of the &leanos;. - - - Technically, modules and extensions are very similar. Both can be managed - with &yast; or the command-line tool SUSEConnect. Both - modules and extensions add a set of online repositories - (main, update, - source, debug) containing all - necessary packages. Additionally, both may add partitioning proposals and - system roles that can be chosen during deployment. - - - However, there are significant differences between modules and extensions: - - - - Modules - - - Modules allow you to shape the product according to your needs. Each - module has a clearly defined scope ranging from tools for Web Development - and Scripting, through a Public Cloud, all the way to the &suse; Package - Hub, offering community-managed packages. - - Modules enable you to provide only the set of packages required for - the machine's purpose, making the system lean, fast, and more secure. - This modular approach also makes it easy to provide tailor-made images - for container and cloud environments. - - - Modules can be added or removed at any time during the lifecycle of the - system. This allows you to easily adjust the system to changing requirements. - - - Modules are part of your &productname; subscription and therefore free of - charge. They differ from the base of &productname; only by their lifecycle. - - - - - Extensions - - - Extensions provide advanced capabilities for tasks such as live patching - and high availability clustering to &productname;. They are offered as - subscriptions and require a registration key that is liable for costs. - Usually, extensions have their own release notes that are available from - . - - - - - - Support - - L3 support is generally provided for packages except for &suse; - Package Hub and third-party modules. To check the support level - for a package, run - zypper info PACKAGE. - - - Long-Term Service Pack Support (LTSS) is available for - most modules and extensions. For more information, refer to . - - - Some modules and extensions also include Extended Service Pack - Overlay Support (ESPOS), which gives you significantly more time to upgrade and/or - skip a service pack completely. - - - For more information on support and lifecycles, refer to the - SUSE Technical - Support Policy and the - Product - Lifecycle Support Policies. For a complete list of lifecycle dates - by product, refer to the - Product Support - Lifecycle page. - - - - - - Modules and extensions for the &sle; product family - - The following modules and extensions are available within the &sle; product - family: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + Introduction to modules and extensions + - + Starting with &productname; 15, the installation medium consists of only the &leanos;: a + minimal system for deploying, updating and registering &productname;. During deployment, you + can add functionality by selecting modules and extensions to be installed on top of the + &leanos;. - - + - + Technically, modules and extensions are very similar. Both can be managed with &yast; or the + command-line tool SUSEConnect. Both modules and extensions add a set of + online repositories (main, update, + source, debug) containing all necessary packages. + Additionally, both may add partitioning proposals and system roles that can be chosen during + deployment. - - + - + However, there are significant differences between modules and extensions: - - - - Please note that the availability depends on the product. Not all modules and - extensions are available for all products. Some modules are included in one - product but also available as extension for another. - - - Basesystem - - This module adds a basic system on top of the Installer. It is required by - all other modules and extensions. The scope of an installation that only - contains the base system is comparable to the minimal - system installation pattern of previous &productname; versions. This module - is selected for installation by default and should not be deselected. - - - - - Dependencies: None - - - - - Availability: Default on all products - - - - - Lifecycle: 10 years - - - - - Extended Support: 3 years LTSS - - - - - Support level: L3 - - - - - - Certifications - - This module contains the FIPS certification packages. - - - - - Depends on: Basesystem - - - - - Available for: &slsa;, &sleda;, &sles4sapa;, - &slert; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Support level: L3 - - - - - - - Confidential Computing Technology Preview - - This module contains a Secure Virtual Machine Service Module (SVSM), which aims to provide secure - services and device emulations to guest operating systems on confidential virtual machines - (CVMs). - - - Technology preview + + + + Modules + + + Modules allow you to shape the product according to your needs. Each module has a + clearly defined scope ranging from tools for Web Development and Scripting, through a + Public Cloud, all the way to the &suse; Package Hub, offering community-managed + packages. + + + Modules enable you to provide only the set of packages required for the machine's + purpose, making the system lean, fast, and more secure. This modular approach also + makes it easy to provide tailor-made images for container and cloud environments. + + + Modules can be added or removed at any time during the lifecycle of the system. This + allows you to easily adjust the system to changing requirements. + + + Modules are part of your &productname; subscription and therefore free of charge. They + differ from the base of &productname; only by their lifecycle. + + + + + Extensions + + + Extensions provide advanced capabilities for tasks such as live patching and high + availability clustering to &productname;. They are offered as subscriptions and require + a registration key that is liable for costs. Usually, extensions have their own release + notes that are available from . + + + + + + + Support + + L3 support is generally provided for packages except for &suse; Package + Hub and third-party modules. To check the support level for a package, run + zypper info PACKAGE. + + + Long-Term Service Pack Support (LTSS) is available for most modules and + extensions. For more information, refer to + . + + + Some modules and extensions also include Extended Service Pack Overlay + Support (ESPOS), which gives you significantly more time to upgrade and/or skip a + service pack completely. + + + For more information on support and lifecycles, refer to the + SUSE Technical Support + Policy and the + Product Lifecycle Support + Policies. For a complete list of lifecycle dates by product, refer to the + Product Support Lifecycle page. + + + + + Modules and extensions for the &sle; product family + - The module is a technology preview and is not supported. Its lifecycle and support options - will be defined at a later stage. + The following modules and extensions are available within the &sle; product family: - - - &amdsev; required + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - The SVSM requires AMD Secure Encrypted Virtualization (&amdsev;) with Secure Nested Paging. It - will only work on AMD systems. + Please note that the availability depends on the product. Not all modules and extensions are + available for all products. Some modules are included in one product but also available as + extension for another. - - - - - Depends on: Server Applications - - - - - Available for: &slsa; on &x86-64; - - - - - Lifecycle: Until the release of &slea; 15 SP7 - - - - - Extended support: None - - - - - Support level: This module is a technology preview and is - not supported. - - - - - - Containers - - This module contains packages relating to containers, including the - container engine and core container-related tools such as on-premise - registry. - - - - - Dependencies: Basesystem - - - - - Availability: &slsa;, &sles4sapa; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Support level: L3 - - - - - - Desktop Applications - - This module adds a graphical user interface (Wayland) and essential desktop applications to the - system. This module is selected for installation by - default; deselecting it is not recommended. - - - - - Dependencies: Basesystem - - - - - Availability: &slsa;, &sleda; - (default), &slewea; (default), &sles4sapa;, &slerta; (default) - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - Development Tools - - This module contains compilers (including gcc) and - libraries required for compiling and debugging applications. Replaces the - former Software Development Kit (SDK). - - - Dependencies: Basesystem, Desktop - Applications - - - - - Availability: &slsa;, &sles4sapa;, - &sleda;, &slerta; (default) - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - High Availability - - This extension provides high-availability clustering technologies that can - be deployed in physical and/or virtual environments. - - - High Availability is included in the subscription for &sles4sapa; as a - module. It is also available as an extension for &slsa;. - For more information about &sle; &hasi;, refer to + Basesystem + + This module adds a basic system on top of the Installer. It is required by all other + modules and extensions. The scope of an installation that only contains the base system is + comparable to the minimal system installation pattern of previous + &productname; versions. This module is selected for installation by default and should not + be deselected. + + + + + Dependencies: None + + + + + Availability: Default on all products + + + + + Lifecycle: 10 years + + + + + Extended Support: 3 years LTSS + + + + + Support level: L3 + + + + + + + Certifications + + This module contains the FIPS certification packages. + + + + + Depends on: Basesystem + + + + + Available for: &slsa;, &sleda;, &sles4sapa;, &slert; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Support level: L3 + + + + + + + + Confidential Computing Technology Preview + + This module contains a Secure Virtual Machine Service Module (SVSM), which aims to provide + secure services and device emulations to guest operating systems on confidential virtual + machines (CVMs). + + + Technology preview + + The module is a technology preview and is not supported. Its lifecycle and support + options will be defined at a later stage. + + + + &amdsev; required + + The SVSM requires AMD Secure Encrypted Virtualization (&amdsev;) with Secure Nested + Paging. It will only work on AMD systems. + + + + + + Depends on: Server Applications + + + + + Available for: &slsa; on &x86-64; + + + + + Lifecycle: Until the release of &slea; 15 SP7 + + + + + Extended support: None + + + + + Support level: This module is a technology preview and + is not supported. + + + + + + + Containers + + This module contains packages relating to containers, including the container engine and + core container-related tools such as on-premise registry. + + + + + Dependencies: Basesystem + + + + + Availability: &slsa;, &sles4sapa; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Support level: L3 + + + + + + + Desktop Applications + + This module adds a graphical user interface (Wayland) and + essential desktop applications to the system. This module is selected for + installation by default; deselecting it is not recommended. + + + + + Dependencies: Basesystem + + + + + Availability: &slsa;, &sleda; (default), &slewea; + (default), &sles4sapa;, &slerta; (default) + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + Development Tools + + This module contains compilers (including gcc) and libraries required + for compiling and debugging applications. Replaces the former Software Development Kit + (SDK). + + + Dependencies: Basesystem, Desktop Applications + + + + + Availability: &slsa;, &sles4sapa;, &sleda;, &slerta; + (default) + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + High Availability + + This extension provides high-availability clustering technologies that can be deployed in + physical and/or virtual environments. + + + High Availability is included in the subscription for &sles4sapa; as a module. It is also + available as an extension for &slsa;. For more information about &sle; &hasi;, refer to + . - - - - - Dependencies: Basesystem, Server Applications - - - - - Availability: &slsa;, &sles4sapa; - (included), &slert; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - High Performance Computing (HPC) - - This module provides specific tools commonly used for high performance, numerically intensive - workloads. - - - &suse; packages these tools in the HPC module to provide greater flexibility to deliver new - versions or new tools more rapidly than the standard &sle; lifecycle would permit. - Packages in this module are generally supported until a newer version of the package is - released or a package is dropped from the module. - - - - - Dependencies: Basesystem - - - - - Availability: &slsa; on &x86-64; and &aarch64; - - - - - Lifecycle: 10 years - - - - - Extended support: 1 year ESPOS, 3 years - LTSS - - - - - Level: L3 - - - - - - Legacy - - This module helps you with migrating applications from earlier versions of - &productname; and other systems to &slsa; &productnumber;, by - providing packages which are discontinued on &sle;. Packages in this - module are selected based on the requirement for migration and the - level of complexity of configuration. - - - This module is recommended when migrating from a previous product - version. - - - Please note that this module has a different lifecycle than some of its - packages. Not all packages are supported for the complete lifecycle of - the module, but depend on migration requirements and upstream - lifecycles. - - - - - Dependencies: Basesystem, Server - Applications - - - - - Availability: &slsa;, &sles4sapa; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - Live Patching - - This extension provides packages to update critical components in &sle; - without shutting down your system, which reduces planned downtime and - increases service availability. - - - - - Dependencies: Basesystem - - - - - Availability: &slsa;, &sles4sapa; on &x86-64;, s390x, and - &ppc64le; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - NVIDIA Compute - - This module contains the NVIDIA CUDA (Compute Unified Device Architecture) - drivers. The software in this module is provided by NVIDIA under the + + + + Dependencies: Basesystem, Server Applications + + + + + Availability: &slsa;, &sles4sapa; (included), &slert; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + High Performance Computing (HPC) + + This module provides specific tools commonly used for high performance, numerically + intensive workloads. + + + &suse; packages these tools in the HPC module to provide greater flexibility to deliver new + versions or new tools more rapidly than the standard &sle; lifecycle would permit. Packages + in this module are generally supported until a newer version of the package is released or + a package is dropped from the module. + + + + + Dependencies: Basesystem + + + + + Availability: &slsa; on &x86-64; and &aarch64; + + + + + Lifecycle: 10 years + + + + + Extended support: 1 year ESPOS, 3 years LTSS + + + + + Level: L3 + + + + + + + Legacy + + This module helps you with migrating applications from earlier versions of &productname; + and other systems to &slsa; &productnumber;, by providing packages which are discontinued + on &sle;. Packages in this module are selected based on the requirement for migration and + the level of complexity of configuration. + + + This module is recommended when migrating from a previous product version. + + + Please note that this module has a different lifecycle than some of its packages. Not all + packages are supported for the complete lifecycle of the module, but depend on migration + requirements and upstream lifecycles. + + + + + Dependencies: Basesystem, Server Applications + + + + + Availability: &slsa;, &sles4sapa; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + Live Patching + + This extension provides packages to update critical components in &sle; without shutting + down your system, which reduces planned downtime and increases service availability. + + + + + Dependencies: Basesystem + + + + + Availability: &slsa;, &sles4sapa; on &x86-64;, s390x, + and &ppc64le; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + NVIDIA Compute + + This module contains the NVIDIA CUDA (Compute Unified Device Architecture) drivers. The + software in this module is provided by NVIDIA under the + CUDA End User License - Agreement and is not supported by &suse;. - - - Importing third-party GPG keys - + Agreement and is not supported by &suse;. + + + Importing third-party GPG keys + cwickert 2022-12-09: --gpg-auto-import-keys only works with suseconnect-ng, which is available in SLE 15 SP4+. For earlier versions, use 'yast registration'. - - As this module is provided by a third party, the repository's GPG key is - unknown to the system. To activate the module and import the key with - &suseconnect;, use the option: - - suseconnect -p sle-module-NVIDIA-compute/&product-ga;/x86_64 --gpg-auto-import-keys - - Alternatively, you can activate the module with - yast registration or during installation. - - - - Combining <literal>Workstation Extension</literal> and - <literal>NVIDIA Compute module</literal> is unsupported - - The Workstation Extension provides drivers for - NVIDIA graphics cards. These drivers share some packages with CUDA, - however, versions may differ. It is therefore neither recommended - nor supported to enable both the NVIDIA Compute - Module and the Workstation Extension at - the same time. - - - - - - Dependencies: Basesystem - - - - - Availability: &slsa; on &x86-64; and &aarch64; - - - - - Support: Software in this module is - provided by NVIDIA and is not supported by &suse; - - - - - - Public Cloud - - This module contains all tools required to create images for deploying - &productname; in cloud environments. For example: Amazon Web Services - (AWS), Microsoft Azure, Google Compute Platform, or &ostack;. - - - - - Dependencies: Basesystem, Server Applications - - - - - Availability: &slsa;, &sles4sapa; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - Python 3 - - This module provides two additional Python interpreters: - - - - - - Python 3.11 and many additional maintained Python 3.11 modules. The Python 3.11 interpreter - and modules are supported until the end of December 2027 and might be updated with the next - service pack (if compatible and when needed). - - - - - - Python 3.12 with all necessary modules for getting Python modules from PyPI. The Python 3.12 - interpreter and modules are supported for 1.5 years until general support for &slea; - &productnumber; ends. - - - - - Packages from the Python 3 module can be installed alongside existing - Python packages, and they can coexist in the same system without - impacting Python 3.6 workloads. - - - - - Dependencies: Basesystem - - - - - Availability: &slsa; (default), &sles4sapa;, &sleda; (default) - - - - - Lifecycle: Python 3.11: 31 Dec 2027, Python 3.12: 1.5 years - (end of &slea; &productnumber; general support) - - - - - - Extended support: None - - - - - Level: L3 - - - - - - Real Time - - This extension aims to reduce the latency and increase the predictability - and reliability of time-sensitive mission-critical applications. - - - Packages in this module are generally supported until a newer version - of the package is released or the package is dropped from the module. - - - - - Dependencies: Basesystem, Desktop - Applications, Development Tools, Server Applications - - - - - Availability: &slerta; (included) - - - - - Lifecycle: 10 years - - - - - Extended support: None - - - - - Level: L3 - - - - - - &sap; Applications - - - This module contains packages specific to &sles4sapa;. It has a different - lifecycle than &sle; itself. Subscriptions for &sles4sap; include 1.5 years - of General Support plus 3 years of Extended Service Pack Overlap Support - (ESPOS) for each service pack. This eliminates the need for customers to - purchase Long Term Service Pack Support (LTSS) until the final service pack - of a release. - - - - - Dependencies: Basesystem - - - - - Availability: &sles4sapa; (included) - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years ESPOS, 3 years - LTSS for last SP - - - - - Level: L3 - - - - - - &sap; Business One Server - - - This module contains packages and system configuration specific to &sap; Business One Server. - It is maintained and supported by the &sles; product subscription. - - - - - Dependencies: Basesystem, Server Applications, - Desktop Applications, Development Tools - - - - - Availability: &slsa; (&x86-64;) - - - - - Lifecycle: 10 years - - - - - Extended support: 3 LTSS - - - - - Level: L3 - - - - - - Server Applications - - This module adds server functionality by providing network services such as - DHCP server, name server or Web server. This module is - selected for installation by default; deselecting it is not - recommended. - - - - - Dependencies: Basesystem - - - - - Availability: &slsa; (default), - &sles4sapa;, &slerta; (default) - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - &suse; Package Hub - - This module provides access to packages for &productname; maintained by the - &opensuse; community. These packages are delivered without L3 support but do - not interfere with the supportability of &productname;. For more - information, refer to . - - - - - Dependencies: Basesystem - - - - - Availability: &slsa;, &sles4sapa;, &slerta; &sleda; - - - - - Lifecycle: None - - - - - Extended support: None - - - - - Level: None - - - - - - Transactional Server - - This module provides &sle; systems with a method of updating the operating - system and its packages in an entirely atomic way. Updates are either - applied to the system all together in a single transaction, or not at all. - This happens without influencing the running system. If an update fails, or - if a successful update is deemed to be incompatible or incorrect, you can - discard it immediately and return to its previous functioning state. - - - - - Dependencies: Basesystem - - - - - Availability: &slsa; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - Web and Scripting - - This module contains packages intended for a running Web server. - - - - - Dependencies: Basesystem, Server - Applications - - - - - Availability: &slsa;, &sles4sapa; - - - - - Lifecycle: 10 years - - - - - Extended support: 3 years LTSS - - - - - Level: L3 - - - - - - Workstation Extension - - This extension offers additional desktop applications and libraries. It is - installed by default on &sled;. Adding the Workstation Extension to a &sls; - installation allows you to seamlessly combine both products to create a - fully featured server workstation. For more information, refer to + As this module is provided by a third party, the repository's GPG key is unknown to the + system. To activate the module and import the key with &suseconnect;, use the + option: + +suseconnect -p sle-module-NVIDIA-compute/&product-ga;/x86_64 --gpg-auto-import-keys + + Alternatively, you can activate the module with yast registration or + during installation. + + + + Combining <literal>Workstation Extension</literal> and <literal>NVIDIA Compute module</literal> is unsupported + + The Workstation Extension provides drivers for NVIDIA graphics cards. + These drivers share some packages with CUDA, however, versions may differ. It is + therefore neither recommended nor supported to enable both the NVIDIA Compute + Module and the Workstation Extension at the same time. + + + + + + Dependencies: Basesystem + + + + + Availability: &slsa; on &x86-64; and &aarch64; + + + + + Support: Software in this module is provided by NVIDIA + and is not supported by &suse; + + + + + + + Public Cloud + + This module contains all tools required to create images for deploying &productname; in + cloud environments. For example: Amazon Web Services (AWS), Microsoft Azure, Google Compute + Platform, or &ostack;. + + + + + Dependencies: Basesystem, Server Applications + + + + + Availability: &slsa;, &sles4sapa; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + Python 3 + + This module provides two additional Python interpreters: + + + + + + Python 3.11 and many additional maintained Python 3.11 modules. The Python 3.11 + interpreter and modules are supported until the end of December 2027 and might be + updated with the next service pack (if compatible and when needed). + + + + + + Python 3.12 with all necessary modules for getting Python modules from PyPI. The Python + 3.12 interpreter and modules are supported for 1.5 years until general support for + &slea; &productnumber; ends. + + + + + Packages from the Python 3 module can be installed alongside existing Python packages, and + they can coexist in the same system without impacting Python 3.6 workloads. + + + + + Dependencies: Basesystem + + + + + Availability: &slsa; (default), &sles4sapa;, &sleda; + (default) + + + + + Lifecycle: Python 3.11: 31 Dec 2027, Python 3.12: 1.5 + years (end of &slea; &productnumber; general support) + + + + + + Extended support: None + + + + + Level: L3 + + + + + + + Real Time + + This extension aims to reduce the latency and increase the predictability and reliability + of time-sensitive mission-critical applications. + + + Packages in this module are generally supported until a newer version of the package is + released or the package is dropped from the module. + + + + + Dependencies: Basesystem, Desktop Applications, + Development Tools, Server Applications + + + + + Availability: &slerta; (included) + + + + + Lifecycle: 10 years + + + + + Extended support: None + + + + + Level: L3 + + + + + + + &sap; Applications + + + This module contains packages specific to &sles4sapa;. It has a different lifecycle than + &sle; itself. Subscriptions for &sles4sap; include 1.5 years of General Support plus 3 + years of Extended Service Pack Overlap Support (ESPOS) for each service pack. This + eliminates the need for customers to purchase Long Term Service Pack Support (LTSS) until + the final service pack of a release. + + + + + Dependencies: Basesystem + + + + + Availability: &sles4sapa; (included) + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years ESPOS, 3 years LTSS for last + SP + + + + + Level: L3 + + + + + + + &sap; Business One Server + + + This module contains packages and system configuration specific to &sap; Business One + Server. It is maintained and supported by the &sles; product subscription. + + + + + Dependencies: Basesystem, Server Applications, Desktop + Applications, Development Tools + + + + + Availability: &slsa; (&x86-64;) + + + + + Lifecycle: 10 years + + + + + Extended support: 3 LTSS + + + + + Level: L3 + + + + + + + Server Applications + + This module adds server functionality by providing network services such as DHCP server, + name server or Web server. This module is selected for installation by + default; deselecting it is not recommended. + + + + + Dependencies: Basesystem + + + + + Availability: &slsa; (default), &sles4sapa;, &slerta; + (default) + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + &suse; Package Hub + + This module provides access to packages for &productname; maintained by the &opensuse; + community. These packages are delivered without L3 support but do not interfere with the + supportability of &productname;. For more information, refer to + . + + + + + Dependencies: Basesystem + + + + + Availability: &slsa;, &sles4sapa;, &slerta; &sleda; + + + + + Lifecycle: None + + + + + Extended support: None + + + + + Level: None + + + + + + + Transactional Server + + This module provides &sle; systems with a method of updating the operating system and its + packages in an entirely atomic way. Updates are either applied to the system + all together in a single transaction, or not at all. This happens without influencing the + running system. If an update fails, or if a successful update is deemed to be incompatible + or incorrect, you can discard it immediately and return to its previous functioning state. + + + + + Dependencies: Basesystem + + + + + Availability: &slsa; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + Web and Scripting + + This module contains packages intended for a running Web server. + + + + + Dependencies: Basesystem, Server Applications + + + + + Availability: &slsa;, &sles4sapa; + + + + + Lifecycle: 10 years + + + + + Extended support: 3 years LTSS + + + + + Level: L3 + + + + + + + Workstation Extension + + This extension offers additional desktop applications and libraries. It is installed by + default on &sled;. Adding the Workstation Extension to a &sls; installation allows you to + seamlessly combine both products to create a fully featured server workstation. For more + information, refer to + . - - - Unsupported kernel modules - - The Workstation Extension installs the - kernel-default-extra package, which includes additional - kernel modules for desktop usage and enables loading of unsupported - modules. If actually loaded, these modules may compromise your &slea; - support status. - - - Please evaluate if your hardware really requires additional kernel modules, - and if so, test this expanded driver set in addition to the default set - from the kernel-default package for possible - configuration conflicts. - + + + Unsupported kernel modules + + The Workstation Extension installs the kernel-default-extra package, + which includes additional kernel modules for desktop usage and enables loading of + unsupported modules. If actually loaded, these modules may compromise your &slea; support + status. + + + Please evaluate if your hardware really requires additional kernel modules, and if so, + test this expanded driver set in addition to the default set from the + kernel-default package for possible configuration conflicts. + + + To prevent installation of the kernel-default-extra package, run + zypper addlock kernel-default-extra. + + + + + + Dependencies: Basesystem, Desktop + + + + + Availability: &slsa;, &sleda; (default), &sles4sapa; + + + + + Lifecycle: 10 years + + + + + Extended support: None + + + + + Level: mixed L2/L3 (depending on package) + + + + + + + Installing and managing modules and extensions + - To prevent installation of the kernel-default-extra - package, run zypper addlock kernel-default-extra. + Modules and extensions can be installed when initially setting up the system and on an + existing &productname; installation. - - - - - Dependencies: Basesystem, Desktop - - - - - Availability: &slsa;, &sleda; (default), - &sles4sapa; - - - - - Lifecycle: 10 years - - - - - Extended support: None - - - - - Level: mixed L2/L3 (depending on package) - - - - - - - - Installing and managing modules and extensions - - Modules and extensions can be installed when initially setting up - the system and on an existing &productname; installation. - - - - Installing modules and extensions during system installation - - Modules and extensions can easily be installed when setting up the system. - The respective steps are part of the installation routine. Following the - default installation path, this requires network access to contact the &scc; - or a local registration server (&susemgr; - or &rmtool;), which provide the respective repositories. Offline - installation is supported, too. In that case, an additional installation - media is required. For detailed information, refer to + Installing modules and extensions during system installation + + Modules and extensions can easily be installed when setting up the system. The respective + steps are part of the installation routine. Following the default installation path, this + requires network access to contact the &scc; or a local registration server + (&susemgr; or + &rmtool;), which provide the respective repositories. Offline installation is supported, + too. In that case, an additional installation media is required. For detailed information, + refer to . - - - - Installing modules and extensions with &yast; - - To install modules & extensions from the running system, you need to - make sure your system is registered with the &scc; or a local registration - server. If you have not done so during the installation, refer to for instructions. - - - &sled; - - As of &sle; 12, &sled; is not only available as a separate product, but - also as a Workstation Extension for &sls;. If you register at the &scc;, - the Workstation Extension can be selected for installation. Note that - installing it requires a valid registration key. - - - - Viewing already installed add-ons - - To view already installed add-ons, start &yast; and select - - Software - Add-Ons - . - - - - Installing add-ons and extensions from online channels with &yast; - - - Start &yast; and select Software - System Extensions. &yast; connects to the - registration server and displays a list of Available Extensions - and Modules. - - - - - Extension and Module Selection + + + + + Installing modules and extensions with &yast; + + To install modules & extensions from the running system, you need to make sure your + system is registered with the &scc; or a local registration server. If you have not done so + during the installation, refer to for + instructions. + + + &sled; + + As of &sle; 12, &sled; is not only available as a separate product, but also as a + Workstation Extension for &sls;. If you register at the &scc;, the Workstation Extension + can be selected for installation. Note that installing it requires a valid registration + key. + + + + Viewing already installed add-ons + + To view already installed add-ons, start &yast; and select + Software Add-Ons . + + + + Installing add-ons and extensions from online channels with &yast; + + + Start &yast; and select Software System + Extensions. &yast; connects to the registration server and + displays a list of Available Extensions and Modules. + + + + Extension and Module Selection dialog - - - - - - - - - - - - - Available extensions and modules + + + + + + + + + + + + + Available extensions and modules + + The number of available extensions and modules depends on the registration server. A + local registration server may only offer update repositories and no additional + extensions. + + + + + + Click an entry to see its description. + + + + + To add modules or extensions, select all components you want to install. Note that all + extensions require additional registration codes which are liable for cost. + + + + + Click Next to proceed. + + + + + Depending on the repositories to be added for the extension or module, you may be + prompted to import the repository's &gpg; key or asked to agree to a license. + + + + + The &yast; package manager opens to install release-packages for + each module and, depending on your choice of modules and extensions, additional + packages. It is strongly recommended not to deselect any of the + preselected packages; you may, however, add additional packages. + + + Choose Accept and Finish to conclude the process. + + + + + If needed, adjust the repository Properties as described in + . + + + + + Module dependencies + + Similar to software packages, which may depend on other packages to function, a module + may have dependencies on other modules. If this is the case, the modules on which it + depends are automatically selected for installation. + + + + + + Installing extensions and third-party add-on products from media - The number of available extensions and modules depends on the - registration server. A local registration server may only offer update - repositories and no additional extensions. + When installing an extension or add-on product from media, you can select various types of + product media, like DVD/CD, removable mass storage devices (such as flash disks), or a + local directory or ISO image. The media can also be provided by a network server, for + example, via HTTP, FTP, NFS, or Samba. - - - - - Click an entry to see its description. - - - - - To add modules or extensions, select all components you want to - install. Note that all extensions require additional registration codes - which are liable for cost. - - - - - Click Next to proceed. - - - - - Depending on the repositories to be added for the extension or module, you - may be prompted to import the repository's &gpg; key or asked to agree to - a license. - - - - - The &yast; package manager opens to install - release-packages for each module and, depending on your - choice of modules and extensions, additional packages. It is strongly - recommended not to deselect any of the preselected - packages; you may, however, add additional packages. - - - Choose Accept and Finish to - conclude the process. - - - - - If needed, adjust the repository Properties as - described in . - - - - - Module dependencies - - Similar to software packages, which may depend on other packages to - function, a module may have dependencies on other modules. If this is the - case, the modules on which it depends are automatically selected for installation. - - - - - - Installing extensions and third-party add-on products from media - - When installing an extension or add-on product from media, you can select - various types of product media, like DVD/CD, removable mass storage devices - (such as flash disks), or a local directory or ISO image. The media can also - be provided by a network server, for example, via HTTP, FTP, NFS, or Samba. - - - - - Start &yast; and select Software - Add-On Products . Alternatively, start the - &yast; Add-On Products module from the command line - with sudo yast2 add-on. - - - The dialog will show an overview of already installed add-on products, - modules and extensions. - - - - - Installed Add-On Products dialog - - - - - - - - - - - - - - - Click Add to install a new add-on product. - - - - - In the Add-On Product dialog, select the option that - matches the type of medium from which you want to install: - - - - - Add-On Product dialog - - - - - - - - - - - - - To scan your network for installation servers announcing their services - via SLP, select Scan Using SLP and click - Next. - - - - - To add a repository from a removable medium, choose the relevant option - and insert the medium or connect the USB device to the machine, - respectively. Click Next to start the installation. - - - - - For most media types, you will be prompted to specify the path - (or URL) to the media after selecting the respective option and clicking - Next. Specifying a Repository Name - is optional. If none is specified, &yast; will use the product name or - the URL as the repository name. - - - - - The option Download Repository Description Files is - activated by default. If you deactivate the option, &yast; will - automatically download the files later, if needed. - - - - - Depending on the repository you have added, you may be prompted - to import the repository's &gpg; key or asked to agree to a - license. - - - After confirming these messages, &yast; will download and parse the - metadata. It will add the repository to the list of Configured - Repositories. - - - - - If needed, adjust the repository Properties as - described in . - - - - - Confirm your changes with OK to close the configuration - dialog. - - - - - After having successfully added the repository for the add-on media, the - software manager starts, and you can install packages. For details, refer - to . - - - - - - Deleting modules and extensions with &yast; - - - - Start YaST - Software Add-On - Products. - - - - - Installed Add-on Products dialog - - - + + + Start &yast; and select Software Add-On + Products . Alternatively, start the &yast; Add-On + Products module from the command line with sudo yast2 + add-on. + + + The dialog will show an overview of already installed add-on products, modules and + extensions. + + + + Installed Add-On Products dialog + + + + + + + + + + + + + + + Click Add to install a new add-on product. + + + + + In the Add-On Product dialog, select the option that matches the + type of medium from which you want to install: + + + + Add-On Product dialog + + + + + + + + + + + + + To scan your network for installation servers announcing their services via SLP, + select Scan Using SLP and click Next. + + + + + To add a repository from a removable medium, choose the relevant option and insert + the medium or connect the USB device to the machine, respectively. Click + Next to start the installation. + + + + + For most media types, you will be prompted to specify the path (or URL) to the + media after selecting the respective option and clicking Next. + Specifying a Repository Name is optional. If none is specified, + &yast; will use the product name or the URL as the repository name. + + + + + The option Download Repository Description Files is activated by + default. If you deactivate the option, &yast; will automatically download the files + later, if needed. + + + + + Depending on the repository you have added, you may be prompted to import the + repository's &gpg; key or asked to agree to a license. + + + After confirming these messages, &yast; will download and parse the metadata. It will + add the repository to the list of Configured Repositories. + + + + + If needed, adjust the repository Properties as described in + . + + + + + Confirm your changes with OK to close the configuration dialog. + + + + + After having successfully added the repository for the add-on media, the software + manager starts, and you can install packages. For details, refer to + . + + + + + + + Deleting modules and extensions with &yast; + + + + Start YaST Software Add-On + Products. + + + + Installed Add-on Products dialog + + + - - - - + + - - - - - - - - Choose the module or extension that should be removed and click - Delete. Confirm the warning saying that all packages - from the selected component will be removed. - - - - - The &yast; Software Manager opens and lists all installed - packages from the deleted module or extension. Click - Accept to remove all of them. It is strongly - recommended to do so, because you will no longer get updates for packages - from deleted modules or extensions. If you keep packages, make sure - to at least remove the *-release package for each - module or extension that gets deleted. - - - Proceed with Accept and then OK. - - - - - Deleting modules - - Note that you should never delete the Basesystem - Module. It is also not recommended to delete the Server Applications Module&slewe; and Desktop Applications - Module. - - + + + + + + + Choose the module or extension that should be removed and click + Delete. Confirm the warning saying that all packages from the + selected component will be removed. + + + + + The &yast; Software Manager opens and lists all installed packages from the deleted + module or extension. Click Accept to remove all of them. It is + strongly recommended to do so, because you will no longer get updates for packages from + deleted modules or extensions. If you keep packages, make sure to at least remove the + *-release package for each module or extension that gets deleted. + + + Proceed with Accept and then OK. + + + + + Deleting modules + + Note that you should never delete the Basesystem Module. It is also + not recommended to delete the Server Applications + Module&slewe; and + Desktop Applications Module. + + + + No updates for packages from deleted modules and extensions + + If you choose to keep packages from deleted modules or extensions, you will no longer + receive updates for these packages. Because this includes security fixes, keeping such + packages may introduce a security risk to your system. + + + - - No updates for packages from deleted modules and extensions - - If you choose to keep packages from deleted modules or extensions, you - will no longer receive updates for these packages. Because this includes - security fixes, keeping such packages may introduce a security risk to - your system. - - - - - - - Adding or deleting modules and extensions with SUSEConnect - - - - Run SUSEConnect --list-extensions to get an overview of - available extensions: - - &prompt.user;sudo SUSEConnect --list-extensions + + Adding or deleting modules and extensions with SUSEConnect + + + + Run SUSEConnect --list-extensions to get an overview of available + extensions: + +&prompt.user;sudo SUSEConnect --list-extensions AVAILABLE EXTENSIONS AND MODULES Basesystem Module &product-ga; SP&product-sp; x86_64 (Activated) @@ -1565,148 +1546,134 @@ MORE INFORMATION You can find more information about available modules here: https://www.suse.com/documentation/sles-15/singlehtml/art_modules/art_modules.html + + + + Run the commands in the listing for activating/deactivating a module or extension to + add or delete a component. Note that adding an extension requires additional + registration codes which are liable for cost. + + + + + Deleting modules + + Note that you should never delete the Basesystem Module. It is also + not recommended to delete the Server Applications + Module&slewe;and + Desktop Applications Module. + + + + No automatic installation or removal of packages + + SUSEConnect only adds or removes modules and extensions. It registers + or deregisters the components and enables or disables their repositories, but it does not + install or remove any packages. If you want this to be done automatically, use &yast; to + manage modules and extensions. + + + When adding a module or extension, SUSEConnect does not install + default packages or patterns. To do this manually, use Zypper or + &yast; Software + Management. + + + When deleting a module or extension, SUSEConnect does not perform a + cleanup. Packages from the module or extension remain installed on the system, but are no + longer updated from a repository. To list these orphaned packages, run + zypper packages --orphaned. To remove one or more packages, run + zypper remove PACKAGE [ANOTHER_PACKAGE]. Alternatively, use + &yast; Software Management + and then View Package Classification + Orphaned Packages to list and delete orphaned packages. + + + + No updates for packages from deleted modules and extensions + + If you choose to keep packages from deleted modules or extensions, you will no longer + receive updates for these packages. Because this includes security fixes, keeping such + packages may introduce a security risk to your system. + + + + + + Module membership of packages - - - - Run the commands in the listing for activating/deactivating a module or - extension to add or delete a component. Note that adding an extension - requires additional registration codes which are liable for cost. - - - - - - Deleting modules - Note that you should never delete the Basesystem - Module. It is also not recommended to delete the Server Applications Module&slewe;and Desktop Applications - Module. + By default, tools for searching software packages (&yast; Software Management or + zypper search) are restricted to searching within active repositories. For + an extended search including not yet activated remote repositories, you can run - - - No automatic installation or removal of packages - - SUSEConnect only adds or removes modules and extensions. - It registers or deregisters the components and enables or disables their - repositories, but it does not install or remove any packages. If you want - this to be done automatically, use &yast; to manage modules and extensions. - - - When adding a module or extension, SUSEConnect does - not install default packages or patterns. To do this manually, use Zypper - or &yast; - Software Management. - +zypper search-packages PACKAGE + + + Searching for packages in the &scc; + + You can also search for packages and their respective modules in the &scc; Web interface at + . A &suse; login is + not required for this service. + + + - When deleting a module or extension, SUSEConnect does - not perform a cleanup. Packages from the module or extension remain - installed on the system, but are no longer updated from a repository. To list - these orphaned packages, run zypper packages - --orphaned. To remove one or more packages, run - zypper remove PACKAGE [ANOTHER_PACKAGE]. - Alternatively, use &yast; Software - Management and then - View - Package Classification - Orphaned Packages - to list and delete orphaned packages. + To refine the search results, zypper search-packages offers the following + options: - - - No updates for packages from deleted modules and extensions + + + , + + + Searches for exact matches. + + + + + , + + + Groups the search results by modules rather than by package name. + + + + + , + + + Additionally lists version numbers and repositories containing the package. + + + + + + + + Generates XML output. + + + + + - If you choose to keep packages from deleted modules or extensions, you - will no longer receive updates for these packages. Because this includes - security fixes, keeping such packages may introduce a security risk to - your system. + Below are a few examples of how to use zypper search-packages. - - - - - - - Module membership of packages - - By default, tools for searching software packages (&yast; Software Management - or zypper search) are restricted to searching within - active repositories. For an extended search including not yet activated - remote repositories, you can run - - zypper search-packages PACKAGE - - - Searching for packages in the &scc; - - You can also search for packages and their respective modules in the &scc; - Web interface at . A - &suse; login is not required for this service. - - - - - To refine the search results, zypper search-packages - offers the following options: - - - - - , - - - - Searches for exact matches. - - - - - - , - - - - Groups the search results by modules rather than by package name. - - - - - - , - - - - Additionally lists version numbers and repositories containing the - package. - - - - - - - - Generates XML output. - - - - - - Below are a few examples of how to use zypper - search-packages. - - - Simple search - - The following command searches for the packages nodejs - and hawk. The first one is available in the Web - and Scripting module, while the second one is part of &sle; - &hasi;. Both packages are not yet installed: - - &prompt.user;zypper search-packages openjdk nodejs + + + Simple search + + The following command searches for the packages nodejs and + hawk. The first one is available in the Web and + Scripting module, while the second one is part of &sle; &hasi;. Both packages are + not yet installed: + +&prompt.user;zypper search-packages openjdk nodejs Following packages were found in following modules: Package Module or Repository @@ -1722,14 +1689,15 @@ nodejs14 Web and Scripting Module (sle-module-web-scripting/15.4/x86_64) nodejs16 Web and Scripting Module (sle-module-web-scripting/15.4/x86_64) SUSEConnect --product sle-module-web-scripting/15.4/x86_64 [...] - - - Searching for exact matches - - If you know the exact package names, you can narrow the results down to - exact matches by using the option : - - &prompt.user;zypper search-packages -x java-11-openjdk nodejs14 + + + + Searching for exact matches + + If you know the exact package names, you can narrow the results down to exact matches by + using the option : + +&prompt.user;zypper search-packages -x java-11-openjdk nodejs14 Following packages were found in following modules: Package Module or Repository @@ -1741,17 +1709,18 @@ java-11-openjdk Basesystem Module (sle-module-basesystem/15.4/x86_64) nodejs14 Web and Scripting Module (sle-module-web-scripting/15.4/x86_64) SUSEConnect --product sle-module-web-scripting/15.4/x86_64 [...] - - - Searching for packages that are already installed or available - - If you search for packages that are already installed or are available in - one of the modules that are available on your system, the search results - differ. In the following example, the package vim is - already installed. The package emacs is not installed, - but is available for installation without having to add a module. - - &prompt.user;zypper search-packages -x vim + + + + Searching for packages that are already installed or available + + If you search for packages that are already installed or are available in one of the + modules that are available on your system, the search results differ. In the following + example, the package vim is already installed. The package + emacs is not installed, but is available for installation without having + to add a module. + +&prompt.user;zypper search-packages -x vim Following packages were found in following modules: Package Module or Repository @@ -1774,17 +1743,15 @@ Package Module or Repository emacs Basesystem Module (sle-module-basesystem/15.4/x86_64) SUSEConnect --product sle-module-basesystem/15.4/x86_64 emacs Available in repo Basesystem_Module_15_SP4_x86_64:SLE-Module-Basesystem15-SP4-Pool - - - - Instead of searching for packages, you can also view the list - of packages that belong to a module or extension. Start the &yast; - Software Management module and click - ViewServices. Select an - entry to display the list of packages that belong to this module or extension. - - - - - + + + + Instead of searching for packages, you can also view the list of packages that belong to a + module or extension. Start the &yast; Software Management module and click + ViewServices. Select an entry + to display the list of packages that belong to this module or extension. + + + +