SUSE Linux Enterprise Server 12

Deployment Guide

Shows how to install single or multiple systems and how to exploit the product inherent capabilities for a deployment infrastructure. Choose from various approaches, ranging from a local installation or a network installation server to a mass deployment using a remote-controlled, highly-customized, and automated installation technique.

Publication date: Feb 19 2015
About This Guide
Available Documentation
Feedback
Documentation Conventions
1 Planning for SUSE Linux Enterprise Server
1.1 Considerations for Deployment of a SUSE Linux Enterprise Server
1.2 Deployment of SUSE Linux Enterprise Server
1.3 Running SUSE Linux Enterprise Server
I Architecture-Specific Installation Considerations
2 Installation on AMD64 and Intel 64
2.1 Required Background
2.2 System Requirements for Operating Linux
2.3 Installation Considerations
2.4 Boot and Installation Media
2.5 Installation Procedure
2.6 Controlling the Installation
2.7 Dealing with Boot and Installation Problems
3 Installation on IBM POWER
3.1 Requirements
3.2 Preparation
4 Installation on IBM System z
4.1 General Information and Requirements
4.2 Preparing for Installation
4.3 The parmfile—Automating the System Configuration
4.4 Using the vt220 Terminal Emulator
4.5 Further In-Depth Information about IBM System z
II Manual Deployment
5 Deployment Strategies
5.1 Deploying up to 10 Workstations
5.2 Deploying up to 100 Workstations
5.3 Deploying More than 100 Workstations
6 Installation with YaST
6.1 Choosing the Installation Method
6.2 System Start-up for Installation
6.3 The Installation Workflow
6.4 Language, Keyboard and License Agreement
6.5 IBM System z: Disk Activation
6.6 Network Settings
6.7 SUSE Customer Center Registration
6.8 Extension Selection
6.9 Suggested Partitioning
6.10 Clock and Time Zone
6.11 Create New User
6.12 Password for the System Administrator root
6.13 Installation Settings
6.14 Performing the Installation
7 Updating SUSE Linux Enterprise
7.1 Background Info: Terminology
7.2 Supported Upgrade Paths for SLE
7.3 General Preparations for Updating
7.4 Upgrading to SUSE Linux Enterprise 12
7.5 Background info: The Product Lifecycle of SUSE Linux Enterprise
7.6 Background: Backporting Source Code
7.7 Background: Migration Hooks for YaST Wagon
8 Setting Up Hardware Components with YaST
8.1 Setting Up Your System Keyboard Layout
8.2 Setting Up Sound Cards
8.3 Setting Up a Printer
9 Installing or Removing Software
9.1 Definition of Terms
9.2 Using the YaST Software Manager
9.3 Managing Software Repositories and Services
9.4 Keeping the System Up-to-date
10 Installing Add-On Products
10.1 SUSE Software Development Kit (SDK) 12
10.2 Registering Your System
10.3 Installing Add-ons and Extensions (without Physical Media)
10.4 Installing Add-ons and Extensions (from Media)
11 Installing Multiple Kernel Versions
11.1 Enabling and Configuring Multiversion Support
11.2 Installing/Removing Multiple Kernel Versions with YaST
11.3 Installing/Removing Multiple Kernel Versions with Zypper
12 Managing Users with YaST
12.1 User and Group Administration Dialog
12.2 Managing User Accounts
12.3 Additional Options for User Accounts
12.4 Changing Default Settings for Local Users
12.5 Assigning Users to Groups
12.6 Managing Groups
12.7 Changing the User Authentication Method
13 Changing Language and Country Settings with YaST
13.1 Changing the System Language
13.2 Changing the Country and Time Settings
14 Remote Installation
14.1 Installation Scenarios for Remote Installation
14.2 Setting Up the Server Holding the Installation Sources
14.3 Preparing the Boot of the Target System
14.4 Booting the Target System for Installation
14.5 Monitoring the Installation Process
15 Advanced Disk Setup
15.1 Using the YaST Partitioner
15.2 LVM Configuration
15.3 Soft RAID Configuration
16 Subscription Management
16.1 Using Kernel Parameters to Access an SMT Server
16.2 Configuring Clients Using AutoYaST Profile
16.3 Configuring Clients Using YaST
16.4 More Information
III Imaging and Creating Products
17 Creating Add-on Products With Add-on Product Creator
17.1 Creating Images
17.2 Add-on Structure
18 Creating Images with YaST Product Creator
18.1 Creating Images
19 Creating Images with YaST Image Creator
19.1 Creating Images
20 Deploying Customized Preinstallations
20.1 Preparing the Master Machine
20.2 Customizing the Firstboot Installation
20.3 Cloning the Master Installation
20.4 Personalizing the Installation
IV Automated Installations
21 Automated Installation
21.1 Simple Mass Installation
21.2 Rule-Based Autoinstallation
21.3 For More Information
22 Automated Upgrade from SUSE Linux Enterprise 11 SP2 to 11 SP3
22.1 Preparing the AutoYaST Profile
22.2 Running the Automated Upgrade
22.3 GRUB 2 Menu Section for Booting into the Upgrade
22.4 Second Stage of the Upgrade
22.5 Limitations and Hints
23 Automated Deployment of Preload Images
23.1 Deploying system manually from rescue image
23.2 Automated Deployment with PXE Boot
A Documentation Updates
A.1 February 2015 (Documentation Maintenance Update)
A.2 October 2014 (Initial Release of SUSE Linux Enterprise Server 12)
B GNU Licenses
B.1 GNU Free Documentation License

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

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

For SUSE and Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell.com/company/legal/trademarks/tmlist.html. All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE or 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 SUSE LLC, its affiliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof.

Print this page