Release notes for SUSE Manager 3 Server

Version 3.0.12
Friday May 18, 2018



This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires that SUSE makes available certain source code that corresponds to the GPL-licensed material. The source code is available for download at http://www.suse.com/download-linux/source-code.html.

Also, for up to three years from SUSE's distribution of the SUSE product, upon request SUSE will mail a copy of the source code. Requests should be sent by e-mail to sle_source_request@suse.com or as otherwise instructed at http://www.suse.com/download-linux/source-code.html. SUSE may charge a fee to recover its reasonable costs of distribution.

Version Revision History

About SUSE Manager

You have more than just a few Linux servers to manage, maybe even a mixed environment of RHEL and SLES?

Then SUSE Manager is the answer.

SUSE Manager gives you best of breed Linux lifecycle management based on the most mature codebase for any Linux management tool, with both RHEL and SLES support from one unified console, maintained and improved by the guys who wrote the fastest and most advanced Linux update stack on the planet.

SUSE Manager gives you the lowest possible Total Cost of Ownership for your Linux environment, from bare metal provisioning to daily patch management. SUSE Manager is an open source (GPLv2) Linux systems management solution that allows you to:

Stay up-to-date

You can stay up-to-date regarding information about SUSE Manager and SUSE products:

Installation

Requirements and registration code

SUSE Manager 3 Server is an extension for SLES 12 SP3 x86_64 or s390x.

This means that, unlike SUSE Manager 2.1 Server, installation is done in two steps

This addresses the need of enterprise deployments to standardize on the base operating system as well as specific storage setups.

Attention Your SUSE Manager Server registration code is valid for the base operating system as well as the SUSE Manager 3 extension.

Installing the SUSE Manager 3 Server extension on SLES 12 SP3

You'll need a physical or virtual SLES 12 SP3 x86_64 or s390x system to install SUSE Manager 3.

When you install and register SLES 12 SP3, SUSE Manager 3 Server will show up in the list of available extensions.

You'll need a SUSE Manager Server registration code to access this extension.

Update from previous versions of SUSE Manager Server

In-place updates from previous versions of SUSE Manager Server are not supported.

Upgrade from SUSE Manager 2.1 Server to SUSE Manager 3 Server is done by choosing the 2.1 Server as a migration source when running ``yast2 susemanager_setup``

See this wiki page for a detailed description of the required steps.

All connected clients will continue to run and are manageable unchanged.

Note that the SUSE Manager 2.1 Server needs to have PostgreSQL as its database.

Update from SUSE Manager 2.1 with Oracle Database

Data migration from SUSE Manager 2.1 with Oracle Database is not possible.

You need to first migrate from Oracle to PostgreSQL database as outlined in the SUSE Manager 2.1 Server documentation.

Migrating from RHN Satellite 5

Is conditionally supported with SUSE Manager 3 Server.

If you have the need to migrate from RHN Satellite 5 to SUSE Manager 3, please get in contact with a SUSE sales engineer or a SUSE consultant before starting the migration.

Using an external database

It's strictly recommended to use the database embedded with the product. Deviating from this recommendation is not generally supportable.

Major changes since SUSE Manager Server 3 GA

Features and changes

Version 3.0.12

Bugfix release.

Update to Salt 'Oxygen' 2018.3.0

Salt is updated to the 'Oxygen' release, versioned as 2018.3.0.

This brings many changes and improvements all over the place, most notably in Python 3 support, Unicode, and Docker.

See the Salt Oxygen and Salt Nitrogen release notes for a full description of changes since SUSE Manager's previous Salt version.

Salt on SLE 11 and RHEL 5

Salt deprecated Python 2.6 with the release of Salt Nitrogen in 2017.

Client systems with Python 2.6, like SLE 11 or RHEL 5, will therefore NOT get Salt upgrades and stay with their current Salt version.

Python 3 subpackages

In order to support SLE 15 clients with salt-ssh, Python 3 compatibility packages are added in this update.

This enables salt-ssh to use Python 3 code when running on SLE 15 clients, which have Python 3 as their main Python version.

spacecmd updates

spacecmd now has a new command: softwarechannel_update (Update a software channel)

The spacecmd functions softwarechannel_create, softwarechannel_clone, and softwarechannel_tree now have a new parameter -g DISABLE-GPG-CHECK.

See 'spacecmd reference' in the advanced topics manual for details.

New products supported

Version 3.0.11

Bugfix release.

Version 3.0.10

Bugfix release.

Database cleanup migration

After several reports about duplicate package ids in the database, a cleanup task was introduced in spacewalk-schema-upgrade to repair such cases.

Warning In case your database is corrupted with duplicate package ids, this cleanup task can take hours to complete. Runtimes of 4-5 hours are normal.

Here is how to check for duplicate package ids

  echo "select min(id) as id \
         from rhnpackageevr \
        group by version, release, epoch \
          having count(*) > 1;" \
    | spacewalk-sql --select-mode-direct -
  echo "select min(id) as id \
          from rhnPackageCapability \
          group by name, version \
          having count(*) > 1;"\
    | spacewalk-sql --select-mode-direct -

These read-only checks can be run during normal operation of SUSE Manager. Just running the checks can take a long time (up to 1hr in some of our test scenarios. YMMV).

If any of these queries returns a non-empty result, it can be stopped immediately. Your database has duplicate package ids in this case and the next run of spacewalk-schema-upgrade will take hours.

Take this under consideration before starting the upgrade to SUSE Manager 3.0.10.

Check for duplicate minion ids

With this update we introduce a unique constraint on minion_id in the database.

When multiple systems exists already with the same minion_id, the schema migration will fail.

There will be a list of the duplicates in the schema migration log. In this case, duplicate minion_id need a manual cleanup:

New products supported

Dropped products

Version 3.0.9

PostgreSQL 9.6 support

A new version of the PostgreSQL database is available in SLES 12 SP2 and can be used for SUSE Manager 3.0 Server.

New installations of SUSE Manager 3.0 Server based on SLES 12 SP3 will automatically pick up this version.

Migrating from PostgreSQL 9.4 to PostgreSQL 9.6

Note: SUSE Manager 3.0 Server must NOT be migrated to SLES 12 SP3 before migrating PostgreSQL to version 9.6.

The migration needs PostgreSQL 9.4 and 9.6 installed in parallel and PostgreSQL 9.4 is only available in SLES 12 SP2

You should have an up-to-date database backup before attempting the migration.

Existing installations of SUSE Manager 3.0 Server will need to run

      /usr/lib/susemanager/bin/pg-migrate.sh

to migrate from PostgreSQL 9.4 to PostgreSQL 9.6

Your SUSE Manager Server installation will not be accessible during the migration.

Migration will create a copy of the database under /var/lib/pgsql and thus needs sufficient disk space to hold two copies (9.4 and 9.6) of the database.

Since it does a full copy of the database, it also needs considerable time depending on the size of the database and the IO speed of the storage.

If your system is scarce on disk space you can do an fast, in-place migration by running

      /usr/lib/susemanager/bin/pg-migrate.sh fast

The fast migration usually only takes minutes and no additional disk space. However, in case of failure you need to restore the database from a backup.

This wiki page contains additional information about the migration.

SUSE Manager Server enabled for SLES 12 SP3

SUSE Manager 3.0 is now based on SLES 12 SP3.

If you already have a SUSE Manager 3.0 Server or Proxy deployed, you can now initiate a service pack migration as outlined in the SLES documentation.

Please migrate to PostgreSQL 9.6 as outlined above before starting the service pack migration.

If you deploy a new SUSE Manager 3.0 Server or Proxy, please start with SLES 12 SP3 as the base operating system.

Release notes and documentation have been adapted to reflect this.

Version 3.0.8

Bugfix release.

Change of jabberd database

jabberd now uses sqlite in place of the berkeley db database to improve stability and performance. sqlite is the preferred database option for jabberd.

Fresh installations of SUSE Manager 3.0 Server will use sqlite by default.

Existing installation need to manually switch to this database as follows

      # systemctl stop jabberd
      # sed -i.bak "s#<driver>db</driver>#<driver>sqlite</driver>#g" /etc/jabberd/sm.xml
      # sed -i.bak "s#<module>db</module>#<module>sqlite</module>#g" /etc/jabberd/c2s.xml
      # systemctl start jabberd

Note: Running spacewalk-setup-jabberd is not recommended as it will reset the jabberd password, breaking existing installations.

jabberd removal and recreation

Notice that the sqlite variant of the jabberd database does not get re-created automatically.

The workaround for corruptions of the old database - regular removal - does not apply anymore.

In case you erroneously deleted the sqlite database, jabberd will not be able to re-create it.

You need to run /usr/share/spacewalk/setup/jabberd/create_sqlite3_database to create the database schema and restart jabberd.

New products supported

Version 3.0.7

Bugfix release.

Version 3.0.6

Bugfix release.

New products supported

Version 3.0.5

Security fix

This release contains a security fix (CVE-2017-7470) for spacewalk-backend where non admin or disabled user could make changes to a system using spacewalk-channel.

new package: locale-formula

This enables configuration of locale-related settings across many salt-management clients (minions) via a user-friendly UI.

UEFI PXE boot

PXE boot should now support UEFI systems. However, our experience shows that UEFI BIOS implementation still vary a lot. So this feature might not work for some systems.

To get this supported across more systems, we need your feedback.

New products supported

Version 3.0.4

SUSE Manager Server enabled for SLES 12 SP2

With the release of the SUSE Manager product definition 188 patch, SUSE Manager 3 is now based on SLES 12 SP2.

If you already have a SUSE Manager 3 Server or Proxy deployed, you can now initiate a service pack migration as outlined in the SLES documentation.

If you deploy a SUSE Manager 3 Server or Proxy anew, please start with SLES 12 SP2 as the base operating system. Release notes and documentation have been adapted to reflect this.

Websocket enablement

Sending remote commands to Salt minions could block the web UI. This was fixed by introducing websocket-based communication for the remote command UI.

If you are connecting from your browser to SUSE Manager Server UI via a http proxy, please enable websocket forwarding on the http proxy.

New products supported

Version 3.0.3

Update of Salt to 2015.8.12

Salt is now at version 2015.8.12 and also available for SLES 12 via the advanced systems management module.

Please take care to update Salt first, before applying any other SUSE Manager updates.

'Live patching' support

Live patching is now fully supported in SUSE Manager. You can view and apply live patches to applicable systems. Please see the best practices guide for full documentation.

SSH push for Salt

SSH push is now available for Salt minions. This allows connections initiated by the SUSE Manager Server as well as agentless clients.

See the best practices guide for full documentation.

Add Raspberry Pi channels

A Raspberry Pi running SLES 12 SP2 or later can now be managed by SUSE Manager. Please note that this combination is self-supported.

New products supported

Version 3.0.2

Support Service Pack migration for Salt minions

Service pack migration is now enabled for Salt minions.

python-pyinotify available in Tools channel

python-pyinotify, a Python module for watching filesystems changes has been added to the SUSE Manager Tools 12 Module.

This module can be used when setting up Beacons on Salt minions. For more details see (Salt beacons)

SLES 12 SP2 for ARM 64bit

The SUSE Manager Tools channel is now available for for aarch64 (bsc#1002776)

Version 3.0.1

Changed versioning scheme

SUSE Manager 3 now has a <major>.<minor>.<micro> version number and will be referenced as SUSE Manager 3.0.

Every patch release adding features will increase the <micro> version numnber. This version number will also be displayed in the footer of the web UI.

New products supported

Salt minions via SUSE Manager Proxy

SUSE Manager Proxy now supports clients managed by Salt, aka salt minions. See the SUSE Manager Proxy release notes for details.

Salt on Expanded Support Platform

Salt on clients running SUSE Linux Enterprise Server with Expanded Support or RHEL. Only versions 6 and 7 are supported. Version 5's Python version is too old to run Salt.

Note: When installing patches, the UI lags behind on the patch status. This will be fixed in the next maintenance update.

Skipping a Service Pack during SP migration

Service pack migration used to restrict migrations to the 'next' service pack only.

With SLE 12 SP2 it is possible to skip a service pack. You can migrate from SLE 12 GA to SLE 12 SP2 without the need to migrate to SLE 12 SP1 in between.

In the web UI this adds a new screen in the SP migration workflow, allowing you to select the migration target.

Note: Not all base and extension (aka add-on product) combinations are supported. The web UI restricts possible migration targets to supported scenarios.

'taskotop' web UI

You can now see the status of taskomatic jobs in the web UI. This is the same information you get from the taskotop command-line tool introduced before.

Go to 'Admin' -> 'Task Engine Status' -> 'Runtime Status'

The table shows you all currently running or finished jobs for the last 5 minutes. The view is refreshed every 5 seconds.

new API call: listMigrationTargets

The listMigrationTargets API call, given base and evtl. extensions, returns a list of available targets for a service pack migration.

The existing scheduleSPMigration API call now optionally takes one of those targets.

New documentation sections

Best practices
Advanced topics

Between GA and 3.0.1

New products supported

Bootstrap UI

The new bootstrapping UI can be used to register systems from the UI by giving only the hostname of a machine to be managed and SSH credentials to access that machine. SUSE Manager will take care of installing the needed software agent (salt-minion) from its own (bootstrap) repositories, as well as configuring and enabling it.

With this procedure it is no longer necessary to manually accept that new minion's key because pre-accepted key is deployed to the system that is going to be registered.

If a username is provided that is different from "root" sudo will be used on the client to configure it, which naturally requires that sudo has been setup correctly.

taskotop

spacewalk-utils now contains taskotop, a command line tool to visualize the taskomatic schedule.

New products supported

Patches

The SUSE Patch Finder is a simple online service to view released patches.

Version 3.0.12

SUSE Manager Server

nutch:

patterns-suse-manager:

spacecmd:

spacewalk-backend:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-search:

spacewalk-utils:

spacewalk-web:

subscription-matcher:

susemanager:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

virtual-host-gatherer:

Salt

salt:

supportutils-plugin-salt:

Client tools

cobbler:

hwdata:

osad:

python-websocket-client:

rhn-custom-info:

rhn-virtualization:

rhncfg:

rhnlib:

rhnpush:

spacecmd:

spacewalk-backend:

spacewalk-client-tools:

spacewalk-koan:

spacewalk-oscap:

spacewalk-remote-utils:

spacewalk-usix:

spacewalksd:

supportutils-plugin-susemanager-client:

suseRegisterInfo:

zypp-plugin-spacewalk:

Version 3.0.11

spacecmd:

spacewalk-backend:

spacewalk-java:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

Version 3.0.10

nutch:

osad:

pxe-default-image:

spacecmd:

spacewalk-backend:

spacewalk-branding:

spacewalk-client-tools:

spacewalk-java:

spacewalk-reports:

spacewalk-search:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

virtual-host-gatherer:

Version 3.0.9

Patch 1217: SUSE Manager Proxy 3.0

jabberd:

spacewalk-backend:

spacewalk-certs-tools:

spacewalk-client-tools:

spacewalk-web:

susemanager-sls:

Patch 984: SUSE Manager Server, Proxy and Client Tools

zypp-plugin-spacewalk:

salt:

spacecmd:

spacewalk-backend:

spacewalk-client-tools:

Version 3.0.8

salt-netapi-client:

smdba:

spacewalk-backend:

spacewalk-branding:

spacewalk-config:

spacewalk-java:

spacewalk-search:

spacewalk-setup-jabberd:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sync-data:

virtual-host-gatherer:

Version 3.0.7

spacecmd:

spacewalk:

spacewalk-backend:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-utils:

spacewalk-web:

susemanager-sls:

Version 3.0.6

locale-formula:

salt-netapi-client:

spacecmd:

spacewalk-backend:

spacewalk-certs-tools:

spacewalk-config:

spacewalk-java:

spacewalk-web:

susemanager:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

Version 3.0.5

spacewalk-backend:

cobbler:

rhnlib:

salt-netapi-client:

spacecmd:

spacewalk-backend:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-reports:

spacewalk-setup:

spacewalk-web:

subscription-matcher:

susemanager:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

virtual-host-gatherer:

Version 3.0.4

salt-netapi-client:

spacecmd:

spacewalk-backend:

spacewalk-client-tools:

spacewalk-config:

spacewalk-java:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

Client tools

salt:

spacewalk-backend:

spacewalk-client-tools:

spacewalk-koan:

spacecmd:

spacewalksd:

Version 3.0.3

salt:

osad:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-setup:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-frontend-libs:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

Version 3.0.2

salt:

spacecmd:

other bugfixes:

From GA until version 3.0.1

Patch 1542: salt

salt:

Patch 1533: cobbler

cobbler:

Patch 1539: SUSE Manager Server

pxe-default-image:

rhnlib:

smdba:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-client-tools:

spacewalk-config:

spacewalk-java:

spacewalk-setup:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

python-certifi:

Patch 1216: SUSE Manager Server

This update fixes the following issues with cobbler:

Patch 1217: SUSE Manager Server 3.0

This update for SUSE Manager Server 3.0 includes the following new features:

jabberd:

quartz:

salt:

smdba:

spacewalk:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-client-tools:

spacewalk-java:

spacewalk-search:

spacewalk-setup:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

Patch 1214: salt

This update for salt fixes the following issues:

Patch 986: SUSE Manager Server 3.0

This update fixes the following issues:

salt:

spacecmd:

spacewalk-backend:

spacewalk-branding:

spacewalk-client-tools:

spacewalk-java:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

susemanager-tftpsync:

Patch 984: SUSE Manager Server, Proxy and Client Tools

This update fixes the following issues for the SUSE Manager Server 3.0 and Client Tools:

zypp-plugin-spacewalk:

cobbler:

salt:

spacecmd:

spacewalk-backend:

spacewalk-client-tools:

Patch 822: salt

This update for salt contains the following:

New features since SUSE Manager Server 2.1

Spacewalk 2.4

SUSE Manager 3 Server is based on Spacewalk 2.4 with many new features added by SUSE.

New documentation

The SUSE Manager 3 documentation was rewritten from scratch and is not derived from the upstream Spacewalk documentation any more.

SUSE Manager 3 comes with four manuals

All manuals will see regular updates and will be available online at www.suse.com.

Subscription Matching

SUSE Manager 3 Server removed all entitlement counting code and instead ships with subscription matching abilities. This is implemented in two parts:

The subscription matcher uses the subscription information from SUSE Customer Center and automatically matches those to known hosts.

A pre-requirement to match subscriptions to systems is to have complete information about which virtual system runs on which virtual host. See topology awareness below on how to have SUSE Manager 3 Server gather this information.

The result is stored in /var/lib/spacewalk/subscription-matcher as CSV files. A web UI will be added later.

See the SUSE Manager Reference Manual for further details about subscription matching.

Topology awareness

The tool virtual-host-gatherer is used to collect data about virtual machines running on virtual hosts.

This creates a topology mesh used by the subscription matcher.

See the SUSE Manager Reference Manual for further details about virtual-host-gatherer

Configuration management

Configuration management is about to see the biggest impact when moving from SUSE Manager 2.1 Server to SUSE Manager 3 Server as it changes from an imperative to a declarative model.

Instead of "install package X at this time", it's now "ensure package X is installed from this time on".

SUSE Manager 3 Server uses Salt from SaltStack Inc. as the client-side agent.

See the SaltStack walk-through for a quick introduction to Salt.

The traditional client stack (aka rhnsd) is still fully supported but deprecated. You do not need to make any changes to existing clients when moving from SUSE Manager 2.1 Server to SUSE Manager 3 Server.

Salt integration

SUSE Manager 3 Server comes with a preconfigured salt-master based on the official 2015.8.7 release.

Any system able to run a salt-minion can be connected to SUSE Manager 3 Server as a managed client.

Initially only SLES 11 SP4, SLES 12 GA, and SLES 12 SP1 clients are supported.

Salt vs. Traditional clients

Salt API support

SUSE Manager 3 Server provides and supports the Salt API as-is. This API will follow upstream Salt and might change at any time as Salt gets updated.

Package downloads changed

Package downloads are now using a new implementation which should have far less overhead for the SUSE Manager Server.

Package downloads itself will not be faster, but should scale better. Feedback welcome !

Monitoring dropped

The monitoring component of SUSE Manager Server has been dropped. Instead a lightweight integration with Icinga is planned.

A fully supported Icinga package for SLES 12 is available via the SUSE Manager Tools channel.

No support for Oracle database

SUSE Manager 3 Server does not initally support Oracle as a database backend.

Existing SUSE Manager 2.1 Server deployments with Oracle should be migrated to PostgreSQL.

PostgreSQL has similar functionality and performance characteristics as Oracle but uses dramatically fewer resources.

Going forward, we will focus on PostgreSQL for all scalability and performance improvements.

Extension for SLES 12 SP2

SUSE Manager is no longer an appliance but now an extension on top of SLES 12 SP2 x86_64 or s390x and available via SUSE Customer Center

This means you can set up the base operating system according to your needs and requirements. SUSE Manager 3 will add all required packages automatically during installation.

All storage setup (esp. for /var/lib/pgsql and /var/spacewalk) should be done before installation of SUSE Manager 3 Server.

Other changes since 2.1

Upgrade of Inter Server Sync setups

In ISS (Inter Server Sync) setups, upgrade all slaves to 3 before upgrading the master.

Supportability of embedded software components

All software components embedded into SUSE Manager, like Cobbler for PXE booting, are only supported in the context of SUSE Manager. Stand-alone usage is not supported.

Red Hat Channels

Managing Red Hat clients requires availability of appropriate Red Hat packages. These are not available through the SUSE Customer Center (SCC) but must be provided by other means, e.g. from a retired Red Hat Satellite installation.

Support for SLES 10 based systems

The SUSE Manager client stack for SLES10 based systems is identical to the one used on SLES11 based systems. SLES 10 systems managed by SUSE Manager will have the ZENworks Managemen Daemon (ZMD) and the rug command line tool removed.

Salt is not available for SLES 10.

SUSE Manager Proxy versions

SUSE Manager 3 Server can work with version 2.1 of SUSE Manager Proxy.

spacewalk-utils

spacewalk-utils, a packaged set of command line tools, continues to be L1* supported only - with some exceptions. Any of these commands needs expertise and can break your system. However, we consider these tools valuable enough to be included, but not fully supported.

* L1 (Problem determination, which means technical support designed to provide compatibility information, usage support, on-going maintenance, information gathering and basic troubleshooting using available documentation.)

The following tools of spacewalk-utils are fully supported:

Known bugs

Upstream changes since SUSE Manager 2.1

Note: Changes from the upstream project are listed here as-is. There's no guarantee that all of them are actually available in SUSE Manager 3 Server.

Spacewalk 2.4

Spacewalk 2.3

Spacewalk 2.2

Providing feedback to our products

In case of encountering a bug please report it through your support contact.

Documentation and other information

http://www.suse.com/products/suse-manager/technical-information/contains additional or updated documentation for SUSE Manager Server 2.1.

These Release Notes are available online at http://www.suse.com/documentation/releasenotes. Further information about SUSE Manager is available at http://wiki.novell.com/index.php/SUSE_Manager

Visit http://www.suse.com for the latest Linux product news from SUSE and http://www.suse.com/download-linux/source-code.html for additional information on the source code of SUSE Linux Enterprise products.

Legal Notices

  SUSE Linux GmbH 
  Maxfeldstr. 5 
  D-90409 Nürnberg 
  Tel: +49 (0)911 740 53 - 0 
  Email: feedback@suse.com 
  Registrierung/Registration Number: HRB 21284 AG Nürnberg 
  Geschäftsführer/Managing Director: Jeff Hawn, Jennifer Guild, Felix Imendörffer 
  Steuernummer/Sales Tax ID: DE 192 167 791 
  Erfüllungsort/Legal Venue: Nürnberg

SUSE makes no representations or warranties with respect 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 respect 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. Please refer to http://www.novell.com/company/policies/trade_services/ for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2016 SUSE LLC. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

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 http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and other countries.

For SUSE trademarks, see SUSE Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/tmlist.html). All third-party trademarks are the property of their respective owners.

Colophon

Thank you for using SUSE Manager Server in your business.

Your SUSE Manager Server Team.