Jump to content
SUSE Linux Enterprise Desktop 15

Modules & Extensions Quick Start

SUSE Linux Enterprise Desktop 15

This Quick Start gives you an overview of modules and extensions available for the SUSE Linux Enterprise family. Learn about purpose and features and how to manage them.

Publication Date: December 20, 2018

1 Modules & Extensions Explained

Starting with SUSE Linux Enterprise Desktop 15, the installation medium only consists of the Installer, a minimal system for deploying, updating and registering SUSE Linux Enterprise Desktop. During deployment you can add functionality by selecting modules and extensions to be installed on top of the Installer.

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 just 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, allowing you to easily adjust the system to changing requirements.

Modules are part of your SUSE Linux Enterprise Desktop subscription and therefore free of charge. They differ from the base of SUSE Linux Enterprise Desktop only by their lifecycle. With the exception of the SUSE Package Hub module, SUSE provides L3 support for almost all packages provided by modules. For more information about the SUSE Linux Enterprise Desktop support statement refer to the Release Notes.

Extensions

Extensions provide advanced capabilities for tasks such as live patching and high availability clustering to SUSE Linux Enterprise Desktop. 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 https://www.suse.com/releasenotes.

1.1 Modules Available for the SUSE Linux Enterprise Product Family

The following modules are available within the SUSE Linux Enterprise Product Family. Note that the availability of modules depends on the product (refer to the column Availability). Refer to https://www.suse.com/lifecycle for more information about lifecycle, release frequency, and the overlay support period.

Name

Module depends on

Available for

Support

Content

Basesystem

None

default on all products

lifecycle: 10 yrs
extended: 3 yrs LTSS1
level: L3

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 installation pattern minimal system of previous SUSE Linux Enterprise Desktop versions. This module is selected for installation by default and should not be deselected.

Containers

Basesystem

SLES, SLES for SAP, SLE HPC

lifecycle: 10 yrs
extended: no
level: L3

Contains support, tools and images for containers.

Desktop Applications

Basesystem

SLED (default), SLE-WE (default), SLES, SLES for SAP, SLE RT, SLE HPC

lifecycle: 10 yrs
extended: no
level: L3

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.

Development Tools

Basesystem, Desktop Applications

SLES, SLES for SAP, SLED, SLE RT, SLE HPC

lifecycle: 10 years
extended: 3 yrs LTSS1
level: L3

Contains compilers (including gcc) and libraries required for compiling and debugging applications. Replaces the former Software Development Kit (SDK).

High Availability

Basesystem

SLES for SAP, SLE HPC

lifecycle: 10 yrs
extended: 3 yrs LTSS1
level: L3

Adds clustering support for mission critical setups. Tools included are Hawk, crm, Pacemaker, and Corosync. High Availability support is included in subscriptions for SLES for SAP and SLE HPC and therefore available as a module on these products. It is also available as an extension for SLES (see below).

High Performance Computing

Basesystem

SLE HPC

lifecycle: 10 yrs
extended: 3 yrs LTSS1, 1 yr ESPOS2
level: L3

SLE HPC basic system.

Legacy

Basesystem, Server Applications

SLES, SLES for SAP, SLE HPC

Contains packages that were available in previous versions of SUSE Linux Enterprise Desktop, but have been discontinued in SLES 15. This module is recommended when migrating from a previous product version.

Public Cloud

Basesystem, Server Applications

SLES, SLES for SAP, SLE HPC

Contains all tools required to create images for deploying SUSE Linux Enterprise Desktop in cloud environments such as the Amazon Web Services (AWS), Microsoft Azure, Google Compute Platform, or the SUSE OpenStack Cloud.

SAP Applications

Packages specific to SLES for SAP

Basesystem

SLES for SAP (default)

lifecycle: 10 yrs
extended: 3 yrs LTSS1, 1 yr ESPOS2
level: L3

SLES for SAP basic system.

Server Applications

Basesystem

SLES (default), SLES for SAP, SLE RT, SLE HPC

lifecycle: 10 yrs
extended: 3 yrs LTSS1
level: L3

Adds server functionality by providing network services such as DHCP server, name server, or Web server.

SUSE Cloud Application Platform Tools

Basesystem

SLED, SLES, SLES for SAP

Adds tools allowing you to interact with a SUSE Cloud Application Platform product.

SUSE Package Hub

Basesystem

all products

lifecycle: none
extended: none
level: none

Provides access to packages for SUSE Linux Enterprise Desktop maintained by the openSUSE community. These packages are delivered without L3 support and do not interfere with the supportability of SUSE Linux Enterprise Desktop. For more information refer to https://packagehub.suse.com/.

Web and Scripting

Basesystem, Server Applications

SLES, SLES for SAP, SLE HPC

Contains packages intended for a running Web server.

1 LTSS: Long-Term Service Pack Support
2 ESPOS: Extended Service Pack Overlay Support

1.2 Extensions Available for the SUSE Linux Enterprise Product Family

The following extensions are available within the SUSE Linux Enterprise Product Family. Note that the availability of extensions depends on the product (refer to the column Availability).

Name and Content

Module Dependency

Availability

SUSE Linux Enterprise High Availability Extension

Basesystem, Server Applications

SLES

SUSE Linux Enterprise Live Patching

Basesystem

SLES

SUSE Enterprise Storage

Basesystem, Server Applications

SLES

SUSE Linux Enterprise Workstation Extension

Basesystem, Desktop Applications

SLES, SLED (default)

2 Installing and Managing

Modules & Extensions can be installed when initially setting up the system and also on an existing SUSE Linux Enterprise Desktop installation.

2.1 Installing Modules & Extensions During the Initial System Setup

Modules & 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 SUSE Customer Center or a local registration server (SUSE Manager or Repository Mirroring Tool), which provide the respective repositories. An offline installation is supported, too. In that case an additional installation media is required. For detailed information refer to Book “Deployment Guide”, Chapter 4 “Installation Steps”, Section 4.7 “Extension and Module Selection”.

2.2 Installing and Managing Modules & Extensions from the Running System

To install modules & extensions from the running system, you need to make sure your system is registered with the SUSE Customer Center or a local registration server. If you have not done so during the installation, refer to Book “Deployment Guide”, Chapter 5 “Registering SUSE Linux Enterprise and Managing Modules/Extensions”, Section 5.2 “Registering from the Installed System” for instructions.

After the system has been registered, modules can be added or removed. Refer to Book “Deployment Guide”, Chapter 5 “Registering SUSE Linux Enterprise and Managing Modules/Extensions”, Section 5.3 “Managing Modules and Extensions in a Running System” for details.

3 Module Membership of Packages

The default tools for searching software packages (YaST Software Management or zypper search) are restricted to searching within active repositories. As a consequence, packages that are members of modules currently not installed on SUSE Linux Enterprise Desktop are not found.

SUSE Linux Enterprise Desktop 15 introduces a new Zypper subcommand, search-packages, which lets you search for packages in all modules and extensions available for SUSE Linux Enterprise Desktop. This command becomes available after installing the package zypper-search-packages-plugin, which is not installed by default. To find out which module a package belongs to, run

zypper search-packages PACKAGE_1 PACKAGE_2
Tip
Tip: Search for Packages in the SUSE Customer Center

In case Zypper's package search command is not available on your system, you can also use the SUSE Customer Center package search Web interface to check the availability of packages and their respective modules. Visit https://scc.suse.com/packages for this purpose. A SUSE login is not required for this service.

To refine the search results, zypper search-packages offers the following options:

-x, --match-exact

Search for exact matches.

-g, --group-by-module

Group the search results by modules rather than by package name.

-d, --details

Additionally lists version numbers and repositories containing the package.

--xmlout

Generate XML output.

The following shows a few examples on how to use zypper search-packages.

Example 1: 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 the SUSE Linux Enterprise High Availability Extension Extension. Both packages are not yet installed:

tux > zypper search-packages hawk2 nodejs
Following packages were found in following modules:

Package        Module or Repository
-------------  --------------------------------------------------------------------
hawk2          SUSE Linux Enterprise High Availability Extension (sle-ha/15/x86_64)
nodejs8        Web and Scripting Module (sle-module-web-scripting/15/x86_64)
nodejs8-devel  Web and Scripting Module (sle-module-web-scripting/15/x86_64)
nodejs8-docs   Web and Scripting Module (sle-module-web-scripting/15/x86_64)
nodejs-common  Web and Scripting Module (sle-module-web-scripting/15/x86_64)

To activate the respective module or product, use SUSEConnect --product.
Use SUSEConnect --help for more details.
Example 2: Searching for Exact Matches

If you know the exact package names, you can narrow the results down to exact matches by using the option -x:

tux > zypper search-packages -x hawk2 nodejs8
Following packages were found in following modules:

Package  Module or Repository
-------  --------------------------------------------------------------------
hawk2    SUSE Linux Enterprise High Availability Extension (sle-ha/15/x86_64)
nodejs8  Web and Scripting Module (sle-module-web-scripting/15/x86_64)

To activate the respective module or product, use SUSEConnect --product.
Use SUSEConnect --help for more details.
Example 3: 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.

tux > zypper search-packages -x vim
Following packages were found in following modules:

Package  Module or Repository
-------  ---------------------------------------------------
vim      Basesystem Module (sle-module-basesystem/15/x86_64)
vim      Installed
vim      Available

tux > zypper search-packages -x emacs
Following packages were found in following modules:

Package  Module or Repository
-------  ---------------------------------------------------
emacs    Basesystem Module (sle-module-basesystem/15/x86_64)
emacs    Available

4 Legal Notice

Copyright© 2006– 2018 SUSE LLC and contributors. All rights reserved.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled GNU Free Documentation License.

For SUSE trademarks, see http://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.

All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.

Print this page