## Quick Start¶

### SUSE Manager 1.2™

Publication Date 21 Feb 2011

Abstract

SUSE® Manager is a server solution for providing updates, patches, and security fixes for single SUSE® Linux Enterprise or Red Hat Enterprise Linux clients. It comes with a set of tools and a Web-based user interface for management tasks. This Quick Start explains how to install and set up SUSE Manager and how to get started with the most important tasks.

## 1. Conceptual Overview¶

SUSE Manager is an open source (GPLv2) Linux system management solution that allows you to execute the following tasks:

- Inventorying your systems (hardware and software information)

- Installing and updating software on your systems

- Building groups to apply (custom) software packages to individual systems

- Provisioning your systems (AutoYaST/Kickstart)

- Managing and deploying configuration files to your systems

- Monitoring your systems

- Provisioning and starting/stopping/configuring virtual guests

- Distributing content across multiple geographical sites in an efficient manner

SUSE Manager's main purpose is to efficiently manage a set of Linux systems and keep them up-to-date. This is done by connecting SUSE Manager to package and update sources, organized as repositories.

Repositories are grouped into channels which are assigned to client systems. SUSE Manager then compares packages installed on the clients with packages available in assigned channels and reports any uninstalled updates.

## 2. System Requirements¶

The following section informs you about the system requirements and some prerequisites for SUSE Manager, including hardware, database, supported clients, and other requirements.

### 2.1. Server Requirements¶

Hardware | Required/Recommended
--- | ---
CPU | Required: Intel™ Pentium 4 or later AMD Opteron or later, 2 GHz or more, 512 K cache or equivalent. Recommended: Intel or AMD multi-core processor, 2.4 GHz dual processor, 512 K cache+ or equivalent.
RAM | Required: 2 GB (minimum for base installation), for a few client systems: 4 GB Recommended (for production operation): 8 GB
Free Disk Space | Required: 20 GB for base installation Additionally: At least 50 GB for repository data

### 2.2. Supported Client Systems¶

Clients with the following operating systems and architectures are supported for registration at SUSE Manager:

System | Supported Architectures
--- | ---
SUSE Linux Enterprise 10 | None
SUSE Linux Enterprise 11 SP1 | x86, x86_64, Itanium, IBM POWER, IBM System z
Red Hat Enterprise Linux 2.1 | None
Red Hat Enterprise Linux 3 | None
Red Hat Enterprise Linux 4 | x86, x86_64
Red Hat Enterprise Linux 5 | x86, x86_64

### 2.3. Supported Databases¶

Embedded Database

  `Oracle 10g Express Edition` is shipped with SUSE Manager. It can store up to 4 GB of data and is thus limited to small deployments up to 20 clients. Using an external database is recommended.

External Database

  In conjunction with SUSE Manager, the following external databases are supported:

  - Oracle Database 10g Release 2 (Standard and Enterprise Edition)

  - Oracle 11g

### 2.4. Other Requirements¶

| Network Setup

For correct installation and setup of SUSE Manager, make sure the following requirements are fulfilled:

Fully Qualified Domain Name (FQDN)

  The system on which to install SUSE Manager must resolve its own FQDN properly. If this is not the case, cookies will not work properly on the Web interface.

Hostname and IP Address

  To guarantee that SUSE Manager's domain name can be resolved by its clients, the server and the client machines must be linked to a working Domain Name Server (DNS) server in the customer environment.

  The hostname of the SUSE Manager server must not contain uppercase letters as this might cause `jabberd` to fail.

Novell Customer Center

  For using SUSE Manager, you need an account at the Novell Customer Center (NCC) where your purchased products and product subscriptions are defined. Make sure to have the following subscriptions:

  - One or more subscriptions for SUSE Manager

  - Subscriptions for the products on the client systems you want to register with SUSE Manager

  - Subscriptions to client entitlements for the client system you want to register with SUSE Manager

Network Time Protocol (NTP)

  The connection to the Web server via Secure Sockets Layer (SSL) requires correct timing of both server and clients. For this reason, SUSE Manager server and all client systems must use NTP. If SUSE Manager is used in conjunction with a stand-alone database, the machine of the separate database must be set to the same time zone as SUSE Manager.

Supported Browsers

  SUSE Manager can be used with Mozilla Firefox and Microsoft Internet Explorer 6 or greater. Other browsers might work, but are not tested.

Virtual Environments

  For running SUSE Manager server in virtual environments, use the following settings for the virtual machine (VM):

  - At least 2 GB of RAM

  - Bridged network

  The following virtual environments are supported:

  - KVM

  - VMware

  - Xen

  - Hyper-V

  For running SUSE Manager in KVM, VMware, or Hyper-V, use the SUSE Manager ISO image. For Xen, use the Xen VM image.

## 3. Prerequisites¶

For the basic SUSE Manager setup, you need to have your mirror credentials from the NCC at hand. To look up your credentials and the e-mail address with which you are registered in NCC, proceed as follows.

Procedure 1. Looking Up Mirror Credentials in NCC ¶

1. Start a Web browser and go to http://www.novell.com/center.

2. Log in to the NCC.

3. From the left navigation bar, select My Products+Mirror Credentials. A Web page opens showing your credentials (username and password).

4. Memorize the username and the password listed there.

5. Select My Profile+Login Profile and memorize the e-mail address with which you are registered.

6. Log out from the NCC.

## 4. Installation and Setup¶

SUSE Manager is a management server application combined with an operating system (appliance). It can be deployed on industry hardware or in a virtual environment and used in conjunction with an embedded or a stand-alone database.

If your future SUSE Manager server is connected to the Internet, it will receive any updates directly from the NCC. For a disconnected setup scenario, configure SUSE Manager to receive any updates from an internal update server (like SMT) instead.

The YaST graphical user interface will guide you through the installation and the setup process. It is started in text mode. Use the →| key to navigate among individual elements. To select a value from a list, use the ↑ and ↓ arrow keys and press Enter. To activate an option, press the Space key.

### 4.1. Overview and Summary of Steps¶

The Quick Start covers the following installation and setup scenarios:

Setup From Scratch—With Internet Connection

  For installation and initial setup, you need to execute the following basic steps:

  1. If using a stand-alone database: Preparing your database instance according to the formula provided in Chapter Requirements (↑Installation Guide).

  2. Installing the Appliance

  3. Setting Up SUSE Manager

Setup From Scratch—Without Internet Connection

  For installation and initial setup, execute the same basic steps as listed above, but skip the registration of the product at NCC. For details, see Step 10 in Procedure 2, “Installing the Appliance”.

  During basic configuration, the setup of Novell channels differs from the standard procedure: Instead of importing channels from NCC, you need to create custom channels, and add repositories to be synchronized with the custom channels. For details, refer to Section “Channels” (↑Reference Guide) and Section “Manage Software Channels+Manage Repositories” (↑Reference Guide), respectively.

Migration from a Satellite Server

  Instead of setting up a SUSE Manager server from scratch, you can also migrate from an existing Satellite server. For details, refer to Section 6, “Server Migration”.

### 4.2. Installation¶

The following procedure describes the installation on a physical machine. Make sure the machine you intend to use fulfills the “Server Requirements”. If you want to install the appliance in a virtual machine, additionally check the settings listed in Virtual Environments.

Procedure 2. Installing the Appliance ¶

| Loss of Data
Installing SUSE Manager on a physical machine will completely erase any data on the hard disk that will be used for installation. Before you start the installation process, create a backup of your hard disks.

1. Boot your future SUSE Manager server from the installation medium. Select Install/Restore SUSE Manager.

2. If your machine contains more than one hard disk, you are asked which one to use for the installation of SUSE Manager. Navigate with the arrow keys, and use the space key to mark the desired hard disk. You are asked if you want to continue and you are warned that the installation will destroy all data on the disk.

3. To proceed, answer with Yes. The deployment process takes over. This step may take some time as large amounts of data need to be unpacked and verified. After the verification, YaST firstboot is started.

4. In the first screen, set the system Language and Keyboard Layout for your future SUSE Manager server. Proceed with Next.

5. In the next screen, set the `root` password for your SUSE Manager server and confirm it.

   Figure 1. YaST Firstboot—Password for the System Administrator

   Proceed with Next.

6. In the next screen, read the licenses and agree to them. Proceed with Next. The installation routine checks some basic system requirements and depending on the results, lets you decide whether to proceed with the installation or cancel.

7. In the next screen, configure the network settings. Note the network requirements listed in Section 2.4, “Other Requirements”. Either choose to Use Following Configuration or Change the network setup according to your wishes.

   Figure 2. YaST Firstboot— Network Configuration

   Proceed with Next.

8. In the next screen, configure the Clock and Time Zone to use for your SUSE Manager server. Proceed with Next.

9. In the next screen, configure the NTP settings according to your wishes. For more information about the options, refer to Help. Note the NTP requirements listed in Section 2.4, “Other Requirements”. Proceed with Next.

10. In the next screen, your are asked to register and activate your product at NCC. During registration, the respective online update repositories are automatically configured.

    | NCC Registration And Updates
    Proper registration is mandatory for the system to receive updates and to ensure that any known installation problems are fixed. In case of a disconnected SUSE Manager setup, skip this step by selecting Configure Later.

    Figure 3. YaST Firstboot—NCC Configuration

    If you decide to Configure Later, you can any time call the respective YaST module on the SUSE Manager server with the yast inst_suse_register command.

    To register directly:

    1. Select Configure Now (Recommended).

    2. Confirm that you want to continue. A text-based browser (w3m) appears. Use the →| key or the arrow keys to navigate among individual elements. To enter data into an input field, activate text input mode by pressing the Enter key once, then enter the value and press Enter again to confirm.

    3. After all values are entered according to your wishes, Submit your input and press Shift+Q to close the text-based browser.

11. On the Installation Completed screen, select Finish to close YaST firstboot. The boot process continues.

12. Wait for the boot process to finish.

    | SUSE Manager Update Required
    After installation, update your SUSE Manager server to apply the latest patches before starting the setup process. To receive updates, registration at NCC (or a connection to an internal update server like SMT) is required. For details on how to execute the update, refer to Section “Updating Packages on SLE” (↑Reference Guide).

### 4.3. Setup¶

After running YaST firstboot and updating SUSE Manager server, run a setup script via YaST. It will display several consecutive screens that let you configure the basic data for setup and the connection to the database. Enter a value in each input field, otherwise the setup may fail.

In the setup screens, you will also be prompted for two passwords.

| Password Criteria

Both passwords must match the following criteria (otherwise the connection to the database or the creation of the certificate might fail):

- Length: At least 7 characters.

- Special characters: Must not contain any of the following characters:

  - Spaces

  - Quotation marks (neither `"` nor `'`)

  - Exclamation marks (`!`)

  - Dollar symbols (`$`)

Procedure 3. Setting Up SUSE Manager ¶

1. Log in to the machine as `root` with the password you set during the installation in Step 5.

2. Execute yast2 susemanager_setup to start the setup process.

3. The first setup screen lets you choose between setting up SUSE Manager from scratch and migrating to SUSE Manager from a Satellite/Spacewalk compatible server. Choose Set up SUSE Manager from scratch. Proceed with Next.

4. In the next setup screen, enter an e-mail address for the SUSE Manager administrator. It is used for notifications by SUSE Manager and is associated with the SSL certificate to be created in the next step. Proceed with Next.

5. In the next setup screen, enter the details needed for the creation of an SSL certificate. The certificate is used for a number of purposes like connections to a proxy, HTTPS protocol in browsers, and more.

   1. Enter the name of your organization, the organization unit, and the city, state and country that your SUSE Manager server is located in. The Organization name defines the name of the default administrative organization that is automatically created during setup.

   2. Set an SSL (Secure Sockets Layer) password and repeat it in the next field.

      Figure 4. Setup—Certificate

      Proceed with Next.

6. In the next setup screen, set the details for the setup of the server and the database:

   1. Decide whether to use the embedded (local) or a remote database for SUSE Manager.

      If you select Local Database, YaST automatically sets the Port and Protocol.

      To use an existing, remote database instead, select Remote Database and enter the following details for the connection to the database: the database system (SID) used to identify a particular database instance, the FQDN of the remote database, the external Port to use (usually `1521`), and the Protocol to use (usually `TCP`).

   2. If you use the embedded database, set a user name and a password for the SUSE Manager database user (that is used to connect to the database).

      For a remote database, enter a user name that already exists in the database configuration, and enter the correct password for this user. Otherwise the connection to the database will fail.

   3. Repeat the password in the next field.

      Figure 5. Setup—Local Database

      Proceed with Next.

7. The last setup screen asks for your mirror credentials from the NCC. Enter your NCC Mirror Credentials Username, the NCC Mirror Credentials Password), and your NCC E-mail Address.

   Figure 6. Setup—NCC Settings

8. Proceed with Next and confirm with Yes to start the setup.

   | Long Operation
   This step may take some time. Wait until the Setup is completed message appears in the upper part of the YaST screen.

9. Click Next and read the instructions about the next steps. Close YaST by pressing Finish.

The basic SUSE Manager settings are written to `/etc/rhn/rhn.conf`. If you have chosen to use a local database, the initial database is created and populated. If you have chosen to use a remote database, the setup script connects to the database.

The setup script also runs the `/usr/sbin/mgr-ncc-sync` command which downloads the subscriptions listed in your NCC Mirror Credentials. The respective Software Channel Entitlements will be listed in the SUSE Manager Web interface (select Admin+Subscriptions).

## 5. Basic Configuration¶

To complete the basic SUSE Manager configuration, you need to execute the following steps:

1. Creating the SUSE Manager Administrator Account

2. Importing Novell Channels from NCC

   In case of disconnected setup with an internal update server like SMT, you need to create custom channels, and add repositories to be synchronized with the custom channels.

3. Creating Activation Keys

4. Generating the Bootstrap Script

5. Editing the Bootstrap Script and Registering Clients

### 5.1. Login to the Web Interface¶

After installation of the appliance, you need to log in and create the first administrator account for SUSE Manager. This administrator has access to all resources on SUSE Manager and has the right to create and manage user accounts. Additionally, he is given the role of an `organization administrator` for the default organization created during SUSE Manager installation and setup.

To access the SUSE Manager Web interface, ask your system administrator for the URL of your SUSE Manager server. It is shown on the console after completion of the installation— see Step 8 from Procedure 2, “Installing the Appliance”.

Procedure 4. Creating the SUSE Manager Administrator Account ¶

1. Start a Web browser. Enter the URL of your SUSE Manager server, using the Fully Qualified Domain name as in the following example: `susemanager.example.com`. The SUSE Manager Web interface appears. Upon first login, you are prompted to create the SUSE Manager administrator account.

2. Enter the data for the administrator account and click Create Login.

   You will be logged in as administrator.

3. On the Overview tab, a message notifies you to finalize your basic system configuration. To make use of the monitoring features provided by SUSE Manager, click the link in the message, activate Enable Monitoring and click Update.

   Monitoring allows an organization to install probes that can immediately detect failures and identify performance degradation on client systems.

### 5.2. Setup of Novell Channels¶

Channels are collections of repositories which are assigned to client systems. Without a channel, clients cannot be grouped nor can they receive updates.

Procedure 5. Importing Novell Channels from NCC ¶

| SUSE Manager Server Without Internet Connection

This procedure only applies to scenarios where your SUSE Manager server is connected to the Internet.

For disconnected scenarios (if you want to use SUSE Manager in conjunction with an internal update server like Subscription Management Tool), create custom channels and add repositories to be synchronized with the custom channels. For details, refer to Section “Channels” (↑Reference Guide) and Section “Manage Software Channels+Manage Repositories” (↑Reference Guide), respectively.

During installation, a first synchronization between Novell Customer Center and SUSE Manager is automatically done by mgr-ncc-sync. At this point in time, it only downloads the subscriptions to the products you have registered for, but it does not synchronize any channel data yet. After installation, you need to import the channels you need.

1. On a shell, log in to the SUSE Manager server as `root`.

2. Execute mgr-ncc-sync `-l` to view all channels that you are allowed to synchronize with SUSE Manager. The output lists both parent and child channels. The following notation is used to mark each channel:

   - `[.]`: A channel not imported or synchronized yet.

   - `[p]`: A previously imported or synchronized channel.

3. Select the channels you want to import. You can only import child channels if their respective parent channels is already imported.

   | Novell Channels Cannot Be Deleted
   Once imported, Novell channels cannot be deleted. Only custom software channels can be deleted.

4. For each channel that you want to import, run mgr-ncc-sync with the `-c` option and add and the respective channel label. For example:

       mgr-ncc-sync -c suse_sles_11.i586-base

   The respective channel data is imported into the SUSE Manager database and a full synchronization is triggered for that channel.

| Client Tools Channel
Make sure to also import the `client tools` channel. It provides the packages that need to be installed on a system to make it a SUSE Manager client system.

Any channel that has been imported is also displayed in the SUSE Manager Web interface. To see a list of all channels, go to the Channels tab and select Novell Channels from the left navigation bar.

### 5.3. Client Setup¶

For a list of client systems supported by SUSE Manager, refer to Section 2.2, “Supported Client Systems”. Registering clients to SUSE Manager is done with a bootstrap script that deploys all necessary information to the clients. The bootstrap script refers some parameters (like activation keys or GPG keys) that depend on your particular setup.

Procedure 6. Creating Activation Keys ¶

Activation keys define entitlements, and which channels and groups the client system is allowed to subscribe to. This information is passed on to all systems registered with a key. Each activation key is bound to the organization for which it has been created.

| Activation Keys for New Organizations
If you created a new organization for which to create activation keys, you need to assign system entitlements first. For details, refer to Procedure 10, “Assigning Entitlements to an Organization” and Section 5.4, “Organization Management”. The default organization has all necessary prerequisites by default.

1. Log in to the SUSE Manager Web interface as administrator.

2. Switch to the Systems tab and select Activation Keys.

3. Click the Create New Key link at the upper right corner.

4. Enter a Description to identify the generated activation key.

5. If you want the key to be generated automatically, leave the Key input field empty. If you want to use a certain string for the key, define the desired string in the Key input field.

   | Allowed Characters
   Do not use commas within the key string. All other characters are allowed. (Commas are used as separators when registering client systems with multiple activation keys with rhnreg_ks).

6. To restrict the number of client systems that can be registered with the activation key, set a Usage Limit by entering a maximum number of systems.

   For unlimited use, leave this field empty.

7. With Base Channels, set the primary channel for the key. This can be either the `SUSE Manager Default` channel or a custom base channel.

   Choosing `SUSE Manager Default` allows client systems to register with the default Novell-provided channel that corresponds to their installed version of SUSE Linux Enterprise.

8. Activate the Add-On Entitlements that you want to give to the client systems that are registered with that key.

9. If any newly registered client systems of your organization should inherit the properties of this key, activate the Universal Default checkbox. Only one universal default activation key can be defined per organization.

10. Generate the key by clicking Create Activation Key.

11. To create more activation keys, repeat the steps above.

Figure 7. Example Activation Key

| Activation Key Update
After modifying or adding any components that are bound to an existing activation key (for example, channels to which to subscribe to), make sure to update the key under Systems+Activation Keys+KEY_TO_MODIFY+Update Activation Key.

The next steps are to generate the `bootstrap.sh` script on the SUSE Manager server, to edit a copy of the script and to run the resulting script on each client machine that you want to register with SUSE Manager.

Procedure 7. Generating the Bootstrap Script ¶

Several options in the bootstrap script can be set via the SUSE Manager Web interface, for example, if remote command execution or remote configuration of clients should be allowed.

1. On the SUSE Manager Web interface, switch to the Admin tab and select SUSE Manager Configuration+Bootstrap Script.

2. Check the options listed on the page and activate or deactivate them according to your needs.

   | Remote Command Execution and Configuration

   If you choose to Enable Remote Configuration and/or Enable Remote Commands, make sure that the `rhncfg-actions` package is installed on the client systems:

   1. Switch to the Systems tab and select Activation Keys.

   2. From the list of activation keys, click the activation key you want to modify.

   3. Click the Packages subtab, enter `rhncfg-actions` into the input field and click Update Key.

   The required package for remote command execution and configuration will automatically be installed on all client systems registered with the respective activation key.

3. Click the Update button. The necessary bootstrap script is generated and stored on the server's filesystem in the `/srv/www/htdocs/pub/bootstrap` directory. It is also available from `susemanager.example.com/pub/bootstrap/`.

4. Proceed with Procedure 8, “Editing the Bootstrap Script and Registering Clients”.

Procedure 8. Editing the Bootstrap Script and Registering Clients ¶

Adjust the generated bootstrap script according to your needs. The minimal requirement is to include the activation key. We strongly recommend to also include one or more GPG keys (for example, your organization key, and package signing keys). Then execute the resulting script on each client machine that you want to register with SUSE Manager (either centrally, from the SUSE Manager server, or decentralized, on each client.)

| Access to Installation Media During Registration
The bootstrap process triggers installation of packages on the client machines. Before executing the bootstrap script on a client, make sure the client can access its default installation medium: network access (in case of network repositories) or inserted DVD (in case of physical media).

1. Log in as `root` to the SUSE Manager server.

2. Create a copy of the automatically generated script:

       cp /srv/www/htdocs/pub/bootstrap/bootstrap.sh \
             /srv/www/htdocs/pub/bootstrap/bootstrap-edited.sh

3. Edit the copy as follows:

   1. Search for the `ACTIVATION_KEYS` entry and enter the activation key from Procedure 6, “Creating Activation Keys”. Make sure to also include the organization prefix in the key, for example:

          ACTIVATION_KEYS=1-fef154ddcf0d515fc

   2. Search for the `ORG_GPG_KEY` entry and enter one or more GPG keys. Multiple keys must be entered as comma-separated list.

      | Package Signing Key for Red Hat Support
      If you receive maintenance and support for your Red Hat client systems through Novell, make sure to include the package signing key you received from Novell. Otherwise the RPM packages cannot be installed on the Red Hat client systems.

   3. Adjust further parameters, if needed. For details, refer to the comments in `bootstrap.sh`.

   4. To enable the script for execution, remove the `exit 1` entry from the message block. The last lines of the message block should now read:

          echo "the exit below)"
                  echo

4. Save the edited version of the script.

5. Use one of the following possibilities to execute the edited script on all client machines that you want to register with SUSE Manager:

   - Log in as `root` on the SUSE Manager server and execute the following commands:

         cd /srv/www/htdocs/pub/bootstrap/
         cat bootstrap-edited.sh | ssh \
         root@client_hostname /bin/bash

   - Log in to each client and execute the following command:

         curl -Sks https://server_hostname/pub
         /bootstrap/bootstrap-edited.sh | /bin/bash

   The clients are registered with the SUSE Manager server specified in the bootstrap script. The SUSE Manager Web interface shows the registered client systems on the Systems tab.

For more information about bootstrapping, refer to Chapter Using Bootstrap (↑Client Configuration Guide).

### 5.4. Organization Management¶

During installation and setup, SUSE Manager automatically creates a default administrative organization. It gets the organization ID `1` and the organization name that you entered in Step 5.a in Procedure 3, “Setting Up SUSE Manager”. For management of larger environments, create multiple organizations: for example, for different departments within your company—or for administering several distinct third-party companies.

| Use of Default Administrative Organization

For managing multiple organization, create new, dedicated organizations within SUSE Manager. The default administrative organization receives special treatment with regards to subscriptions and entitlements. Therefore do not use the default administrative organization for registering client systems and creating users in a multi-organization setup. For details, refer to Section “General Tips for Multi-Org Usage” (↑Reference Guide).

Procedure 9. Creating and Deleting Organizations ¶

Administrators can create new organizations and assign entitlements, groups, systems, and users to it. This enables organizations to perform administrative tasks on their own without affecting other organizations.

1. Log in to the Web interface as SUSE Manager administrator or organization administrator.

2. To create an organization:

   1. Switch to the Admin tab to see a list of all Organizations within SUSE Manager.

   2. Click the Create New Organization link at the top right corner.

   3. Enter an Organization Name.

   4. To create the initial organization administrator for the new organization, enter the Desired Login and the Desired Password for the new user and confirm the password.

   5. Enter the first and last name and the e-mail address of the new user.

   6. To finish, click Create Organization.

3. To delete an organization:

   1. On the Admin tab, select Organizations from the left navigation bar.

   2. Click the desired organization to see the organization details.

   3. Click the Delete Organization link at the upper right corner and confirm by clicking the Delete Organization button.

### 5.5. Management of System and Software Entitlements¶

One important task after creating a new organization is to assign entitlements to the new organization. There are two types of entitlements that are important:

System Entitlements

  Various categories of system entitlements are available: management, provisioning, monitoring, and virtualization entitlements. Having management entitlements is a base requirement for an organization to function in SUSE Manager. The maximum number of systems that may register with an organization in SUSE Manager depends on the number of management entitlements allocated to that organization—regardless of the number of software entitlements available.

Software Channel Entitlements

  Apart from system entitlements, software channel entitlements are needed for each organization. For example, you must grant `client tools` channel entitlements to each organization (as this channels contains client software required for extended SUSE Manager functionality, such as AutoYaST or Kickstart or virtualization support).

The default organization automatically gets the needed system and software entitlements during the synchronization with mgr-ncc-sync. To transfer the respective entitlements from the default organization to any newly created organization, proceed as follows.

Procedure 10. Assigning Entitlements to an Organization ¶

1. Log in to the SUSE Manager Web interface as SUSE Manager administrator.

2. Switch to the Admin tab and from the left navigation bar, select Organizations.

3. Select the organization for which to assign or change entitlements and select the Subscriptions sub-tab.

4. To set any system entitlements for the selected organization:

   1. Click the System Entitlements sub-tab to view the System Entitlements Counts.

   2. Set the total number of Management (Base) entitlements for the current organization by entering a value in the Proposed Total field.

   3. Similarly, set total numbers for any other entitlements you may need (like monitoring, provisioning, virtualization).

   4. Click Update Organization to confirm your changes.

5. To set software channel entitlements for the selected organization:

   1. Click the Software Channel Entitlements subtab to view the Software Channel Entitlements Counts.

   2. For any channel that should be available to the client systems of the current organization, enter the desired number of entitlements for this channel in the Regular Proposed Total field.

   3. Click Update Organization to confirm your changes.

Any number of system or software entitlements assigned to an organization are deducted from the total number of system or software entitlements.

To view the total number of software entitlements across all organizations in SUSE Manager, switch to the Admin tab and select Subscriptions+Software Channel Entitlements.

### 5.6. User Management¶

Upon first login to the SUSE Manager Web interface, the account for the first SUSE Manager administrator needs to be created, as described in Procedure 4, “Creating the SUSE Manager Administrator Account”. The SUSE Manager administrator can then add more SUSE Manager users and grant and edit permissions for each user.

| Users and Organizations
Each user belongs to the organization within which the user account has been created. A user cannot belong to more than one organization. For creating or editing a user account, log in with an `organization administrator` account for the organization to which the user belongs or should belong.

Procedure 11. Creating User Accounts ¶

Only organization administrators or SUSE Manager administrators can create and edit user accounts.

1. Log in to the SUSE Manager Web interface as administrator. The top level row of the Web interface shows the organization you are currently logged in to.

2. Switch to the Users tab and click the create new user link at the upper right corner.

3. Enter the Desired Login and the Desired Password for the new user and confirm the password. Both login and password must consist of at least 5 characters.

4. Enter the first and last name and the e-mail address of the new user and click Create Login. The Web interface switches to the User List, showing either Active, Deactivated, or All users.

With the creation of a new user account, the user can log in to the SUSE Manager Web interface, but he does not have any administrative permissions yet. Administrative permissions are granted via roles. Each user can have multiple roles. To assign roles to a user and to set other permissions and options proceed as described in Procedure 12, “Editing User Accounts”:

Procedure 12. Editing User Accounts ¶

1. Log in to the SUSE Manager Web interface as administrator. The top level row of the Web interface shows the organization you are currently logged in to.

2. Switch to the Users tab.

3. From the left navigation bar, select if you want to see Active, Deactivated, or All users.

4. From the list of users, click the user entry you want to modify. The Web interface shows the User Details for the selected entry. Apart from the user's name and password, the Details sub-tab also lets you assign roles to the user.

5. Select the roles that you want to assign to the user. For detailed information about the roles, refer to Section “User List+Active+User Details+Details — [Mgmt]” (↑Reference Guide). If you activate the Organization Administrator check box, the user will automatically inherit the roles listed below. To assign or remove individual roles, activate or deactivate the respective check boxes.

6. Click Submit to confirm your changes on the Details sub-tab.

7. To set or modify the user's permissions for system groups, systems or channels that exist within the current organization, switch to the respective sub-tabs and follow the instructions on the Web interface.

8. To modify preferences, addresses or notification methods for the currently selected user, switch to the respective sub-tabs and confirm your changes.

Procedure 13. Adding or Removing the SUSE Manager Administrator Role ¶

As SUSE Manager administrator, you can assign the permission to become SUSE Manager administrator to other users.

1. Log in to the Web interface as SUSE Manager administrator.

2. For an overview of all users that exist within SUSE Manager (across all organizations), switch to the Admin tab and select Users from the left navigation bar.

   A green checkmark in the SUSE Manager Administrator column marks users that have the respective permission.

3. To assign or remove the `SUSE Manager administrator` role, activate or deactivate the SUSE Manager Administrator checkbox for the respective user.

For more details about user management, refer to Section “Users — [Mgmt]” (↑Reference Guide).

## 6. Server Migration¶

If you have a SUSE Manager server installed in parallel to an existing Satellite server, you can migrate your Satellite server to SUSE Manager. The YaST SUSE Manager setup module first collects the necessary information. Then you execute the migration in several steps with the `migration.sh` script as described in Procedure 14, “Migrating a Red Hat Satellite to SUSE Manager”. Use `-h` to see the available options:

    /usr/lib/susemanager/bin/migration.sh -h

| Supported Migration
SUSE Manager only supports migration from Satellite 5.3 and 5.4 servers.

Procedure 14. Migrating a Red Hat Satellite to SUSE Manager ¶

1. Log in to your existing SUSE Manager server as `root`.

2. Execute yast2 susemanager_setup to start the YaST module.

3. Select Migrate a Satellite/Spacewalk compatible server. Proceed with Next.

4. In the next screen, enter the Hostname of the Satellite Server, its Domain Name, the Satellite Database Username, the Satellite Database Password, and the Satellite Database SID.

   Figure 8. Migration—Satellite Information

   Proceed with Next.

5. In the next screen, enter the IP Address of the SUSE Manager Server, the Database Administrator Password (belonging to the database's `root`), and the e-mail address of the SUSE Manager administrator.

   Figure 9. Migration—SUSE Manager Information

   Proceed with Next.

6. The next screen asks for details about the database to be migrated.

   1. If you want to migrate data from an embedded database, select Local Database. YaST automatically sets the Port and Protocol.

      To migrate data from an existing remote database instead, select Remote Database and enter the following details for the connection to the database: the database system (SID) used to identify a particular database instance, the FQDN of the remote database, the external Port to use (usually `1521`), and the Protocol to use (usually `TCP`).

   2. Enter or set the name and password of the SUSE Manager database user (that is used to connect to the local or remote database).

   3. Repeat the password in the next field.

      Figure 10. Migration—Local Database

      Proceed with Next.

7. The next screen asks for your mirror credentials from the NCC. Enter your NCC Mirror Credentials Username, the NCC Mirror Credentials Password), and your NCC E-mail Address.

   Figure 11. Migration—NCC Information

   Proceed with Next.

8. Click Next to close YaST and to write the collected information to a file that will be parsed by the migration.sh script during the next steps.

9. Using the `-r` option, first copy the RPM packages and configuration files from the Satellite server:

       /usr/lib/susemanager/bin/migration.sh -r

   | Long Operation
   This step may take hours to finish.

10. Before you start the final migration process, make sure that nothing is changed on your Satellite server from this point on. Log in to your Satellite server and shut down the Web interface:

        rcapache2 stop

11. On the SUSE Manager server, start the final migration process:

        /usr/lib/susemanager/bin/migration.sh -m

    It synchronizes any remaining changes (that may have occurred during the first run with the `-r` option) and migrates the database.

12. After the process has been finished successfully, shut down the Satellite server.

13. In the DNS server, change the name of the Satellite server to the SUSE Manager server's IP address, so that the new SUSE Manager server gets the hostname of the former Satellite server.

From now on, use your SUSE Manager as a replacement for your Satellite server. Since the hostname is the same, all certificates will still work. Any registered clients are automatically directed to the SUSE Manager server.

## 7. Troubleshooting¶

If you have difficulties deploying the appliance, proceed according to the following list.

### 7.1. Installation and Basic Setup¶

CPU: 64-Bit and Virtualization Support

  For running SUSE Manager in a virtual environment you need a machine with a recent Linux Kernel on either an Intel processor with VT (Virtualization technology) extensions, or an AMD processor with SVM extensions (also called AMD-V).

  Test if your CPU supports hardware virtualization (and which set of extensions is used) by executing the following command:

      egrep '(vmx|svm)' /proc/cpuinfo

  If this command returns no output, your processor either does not support hardware virtualization, or this feature has been disabled in the BIOS. Enable virtualization support in the BIOS and try again. If in doubt, consult your mainboard manual.

  If the output contains a `svm` string, your machine uses the AMD- V extensions, if the output contains an `vmx` string, the Intel VT extensions are used.

Database Connection Error

  If the setup script reports a database connection error, check if bridged networking is configured correctly on your virtual machine. As repairing the current installation will fail after a database connection error, fix the network settings in your virtual machine and start from scratch with a new SUSE Manager image.

Hostname and DNS

  Make sure to fulfill the hostnames and DNS requirements listed in Section 2.4, “Other Requirements”.

### 7.2. Basic Configuration¶

Client Is Not Registered

  This is often caused by a missing channel assignment. For example, if you want to register a client running a 64-bit version of SUSE Linux Enterprise Server 11 SP1, you need to add one or more channel for that version of SUSE Linux Enterprise Server 11 SP1. Check if the required steps mentioned at the beginning of Section 5, “Basic Configuration” have been executed correctly.

Web Interface: Unavailable Functions

  If any functions or entries in the Web interface are not available, check if you have the permission to access these functions. SUSE Manager uses a role-based model for granting permissions. For more information, refer to Section 5.6, “User Management” and Section 5.4, “Organization Management”.

## 8. Glossary¶

Repository

  A collection of software packages for a specific architecture.

Channel

  A channel contains one or more repositories. Channels help you segregate packages by sensible rules: for instance, a channel may contain packages from a specific distribution. A channel may contain packages for an application or family of applications. Users may also define channels for their own particular needs; for example, a company may create a channel that contains packages for all of the organization's laptops.

Base and Child Channels

  A base channel consists of packages based on a specific architecture and release. A child channel is a channel associated with a base channel but contains extra packages.

## 9. For More Information¶

SUSE Manager

  This guide gave you a short introduction to SUSE Manager. To discover more, refer to the other manuals available for SUSE Manager. Find them at http://www.novell.com/documentation/suse_manager. Alternatively, access them from the SUSE Manager Web interface by selecting Help from the top navigation bar.

Novell Customer Center

  For detailed information about the NCC, refer to the NCC guide available at http://www.novell.com/documentation/ncc.

KVM

  For detailed information about KVM refer to the guide Virtualization with KVM, available at http://www.novell.com/documentation/sles11.

## 10. Legal Notice¶

Copyright© 2006– 2011 Novell, Inc. 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”.

Alternatively this document is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Novell, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

For Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell.com/company/legal/trademarks/tmlist.html. Linux* is a registered trademark of Linus Torvalds. All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a Novell trademark; an asterisk (*) denotes a third party trademark.

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

## 11. GNU Free Documentation License¶

Version 1.2, November 2002

Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

### 11.1. PREAMBLE¶

The purpose of this License is to make a manual, textbook, or other functional and useful document “free” in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

### 11.2. APPLICABILITY AND DEFINITIONS¶

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The “Document”, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”.

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.

A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

### 11.3. VERBATIM COPYING¶

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

### 11.4. COPYING IN QUANTITY¶

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

### 11.5. MODIFICATIONS¶

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.

C. State on the Title page the name of the publisher of the Modified Version, as the publisher.

D. Preserve all the copyright notices of the Document.

E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice.

H. Include an unaltered copy of this License.

I. Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

K. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

M. Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version.

N. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section.

O. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles.

You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

### 11.6. COMBINING DOCUMENTS¶

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements”.

### 11.7. COLLECTIONS OF DOCUMENTS¶

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

### 11.8. AGGREGATION WITH INDEPENDENT WORKS¶

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

### 11.9. TRANSLATION¶

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

### 11.10. TERMINATION¶

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

### 11.11. FUTURE REVISIONS OF THIS LICENSE¶

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

### 11.12. ADDENDUM: How to use this License for your documents¶

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

       Copyright (c) YEAR YOUR NAME.
       Permission is granted to copy, distribute and/or modify this document
       under the terms of the GNU Free Documentation License, Version 1.2
       or any later version published by the Free Software Foundation;
       with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
       A copy of the license is included in the section entitled “GNU
       Free Documentation License”.

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this:

       with the Invariant Sections being LIST THEIR TITLES, with the
       Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.