Novell LINUX ENTERPRISE SERVER 11 - DEPLOYMENT Quick reference guide

SUSE Linux Enterprise
Server
www.novell.com11
March23,2009 Deployment Guide

Deployment Guide
All content is copyright © 2006- 2009 Novell, Inc.
Legal Notice
This manual is protected under Novell intellectual property rights. By reproducing, duplicating or
distributing this manual you explicitly agree to conform to the terms and conditions of this license
agreement.
This manual may be freely reproduced, duplicated and distributed either as such or as part of a bundled
package in electronic and/or printed format, provided however that the following conditions are ful-
lled:
That this copyright notice and the names of authors and contributors appear clearly and distinctively
on all reproduced, duplicated and distributed copies. That this manual, specically for the printed
format, is reproduced and/or distributed for noncommercial use only. The express authorization of
Novell, Inc must be obtained prior to any other use of any manual or part thereof.
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.

Contents
About This Guide ix
1Planning for SUSE Linux Enterprise Server 1
1.1 Considerations for Deployment of a SUSE Linux Enterprise Server . . . . . 2
1.2 Deployment of SUSE Linux Enterprise Server . . . . . . . . . . . . . . 3
1.3 Running SUSE Linux Enterprise Server . . . . . . . . . . . . . . . . . 4
Part I Architecture Specic Installation Considerations 5
2Installation on x86, AMD64, Intel 64, and Itanium 7
2.1 Required Background . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 System Requirements for Operating Linux . . . . . . . . . . . . . . . 8
2.3 Installation Considerations . . . . . . . . . . . . . . . . . . . . . 11
2.4 Boot and Installation Media . . . . . . . . . . . . . . . . . . . . 14
2.5 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . 15
2.6 Controlling the Installation . . . . . . . . . . . . . . . . . . . . . 16
2.7 Dealing with Boot and Installation Problems . . . . . . . . . . . . . . 18
3Installation on IBM POWER 21
3.1 Requirements .......................... 21
3.2 Preparation ........................... 23
4Installation on IBM System z 39
4.1 General Information and Requirements . . . . . . . . . . . . . . . . 39
4.2 Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . 46
4.3 Network Connection Types . . . . . . . . . . . . . . . . . . . . . 63

4.4 The parmle—Automating the System Conguration . . . . . . . . . . 67
4.5 Using the vt220 Terminal Emulator . . . . . . . . . . . . . . . . . 73
4.6 Further In-Depth Information about IBM System z . . . . . . . . . . . 74
Part II Manual Deployment 77
5Deployment Strategies 79
5.1 Deploying up to 10 Workstations . . . . . . . . . . . . . . . . . . 79
5.2 Deploying up to 100 Workstations . . . . . . . . . . . . . . . . . . 81
5.3 Deploying More than 100 Workstations . . . . . . . . . . . . . . . 88
6Installation with YaST 89
6.1 Choosing the Installation Method . . . . . . . . . . . . . . . . . . 89
6.2 The Installation Workow . . . . . . . . . . . . . . . . . . . . . 91
6.3 IBM POWER: System Start-Up for Network Installation . . . . . . . . . 92
6.4 IBM System z: System Start-Up for Installation . . . . . . . . . . . . . 92
6.5 System Start-Up for Installation . . . . . . . . . . . . . . . . . . . 93
6.6 TheBootScreen......................... 93
6.7 Welcome ............................ 98
6.8 IBM System z: Hard Disk Conguration . . . . . . . . . . . . . . . . 99
6.9 Installation Mode . . . . . . . . . . . . . . . . . . . . . . . . 101
6.10 Clock and Time Zone . . . . . . . . . . . . . . . . . . . . . . . 103
6.11 Server Base Scenario . . . . . . . . . . . . . . . . . . . . . . . 105
6.12 Installation Settings . . . . . . . . . . . . . . . . . . . . . . . 105
6.13 Performing the Installation . . . . . . . . . . . . . . . . . . . . 110
6.14 Conguration of the Installed System . . . . . . . . . . . . . . . . 113
6.15 GraphicalLogin......................... 124
7Updating SUSE Linux Enterprise 125
7.1 Updating SUSE Linux Enterprise . . . . . . . . . . . . . . . . . . 125
7.2 Installing Service Packs . . . . . . . . . . . . . . . . . . . . . . 128
7.3 Software Changes from Version 10 to Version 11 . . . . . . . . . . . 128
8Setting Up Hardware Components with YaST 129
8.1 Probing Your Hardware . . . . . . . . . . . . . . . . . . . . . . 129
8.2 Setting Up Graphics Card and Monitor . . . . . . . . . . . . . . . 130
8.3 Setting Up Keyboard and Mouse . . . . . . . . . . . . . . . . . . 131
8.4 Setting Up Sound Cards . . . . . . . . . . . . . . . . . . . . . . 134
8.5 Setting Up a Printer . . . . . . . . . . . . . . . . . . . . . . . 136

9Installing or Removing Software 141
9.1 Denition of Terms . . . . . . . . . . . . . . . . . . . . . . . . 141
9.2 Using the Qt Interface . . . . . . . . . . . . . . . . . . . . . . 142
9.3 Managing Software Repositories and Services . . . . . . . . . . . . 147
9.4 Keeping the System Up-to-date . . . . . . . . . . . . . . . . . . 149
10 Installing Add-On Products 157
10.1 Add-Ons............................ 157
10.2 BinaryDrivers.......................... 158
10.3 SUSE Software Development Kit (SDK) 10 . . . . . . . . . . . . . . 158
11 Accessing the Internet 159
11.1 Direct Internet Connection . . . . . . . . . . . . . . . . . . . . 159
11.2 Internet Connection Via Network . . . . . . . . . . . . . . . . . . 162
12 Managing Users with YaST 163
12.1 User and Group Administration Dialog . . . . . . . . . . . . . . . 163
12.2 Managing User Accounts . . . . . . . . . . . . . . . . . . . . . 165
12.3 Additional Options for User Accounts . . . . . . . . . . . . . . . . 167
12.4 Changing Default Settings for Local Users . . . . . . . . . . . . . . 175
12.5 Assigning Users to Groups . . . . . . . . . . . . . . . . . . . . . 176
12.6 ManagingGroups........................ 176
12.7 Changing the User Authentication Method . . . . . . . . . . . . . . 178
13 Changing Language and Country Settings with YaST 181
13.1 Changing the System Language . . . . . . . . . . . . . . . . . . . 181
13.2 Changing the Country and Time Settings . . . . . . . . . . . . . . 185
14 Remote Installation 189
14.1 Installation Scenarios for Remote Installation . . . . . . . . . . . . . 189
14.2 Setting Up the Server Holding the Installation Sources . . . . . . . . . 198
14.3 Preparing the Boot of the Target System . . . . . . . . . . . . . . . 208
14.4 Booting the Target System for Installation . . . . . . . . . . . . . . 218
14.5 Monitoring the Installation Process . . . . . . . . . . . . . . . . . 222
15 Advanced Disk Setup 227
15.1 Using the YaST Partitioner . . . . . . . . . . . . . . . . . . . . . 227
15.2 LVM Conguration . . . . . . . . . . . . . . . . . . . . . . . . 235

15.3 Soft RAID Conguration . . . . . . . . . . . . . . . . . . . . . 241
16 Subscription Management 247
16.1 Using Kernel Parameters to Access an SMT Server . . . . . . . . . . . 248
16.2 Conguring Clients Using AutoYaST Prole . . . . . . . . . . . . . . 249
16.3 Conguring Clients Using the clientSetup4SMT.sh Script . . . . . . . . 251
16.4 Registering Clients Against SMT Test Environment . . . . . . . . . . . 251
Part III Imaging and Creating Products 253
17 KIWI 255
17.1 Prerequisites for KIWI . . . . . . . . . . . . . . . . . . . . . . 255
17.2 Knowing KIWI’s Build Process . . . . . . . . . . . . . . . . . . . 256
17.3 Image Description . . . . . . . . . . . . . . . . . . . . . . . . 256
17.4 Creating Appliances with KIWI . . . . . . . . . . . . . . . . . . . 260
17.5 For More Information . . . . . . . . . . . . . . . . . . . . . . 262
18 Creating Add-On Products With Add-on Creator 263
18.1 CreatingImages......................... 263
18.2 Add-On Structure . . . . . . . . . . . . . . . . . . . . . . . . 264
18.3 For More Information . . . . . . . . . . . . . . . . . . . . . . 265
19 Creating Images with YaST Product Creator 267
19.1 Prerequisites for Product Creator . . . . . . . . . . . . . . . . . . 267
19.2 CreatingImages......................... 267
19.3 For More Information . . . . . . . . . . . . . . . . . . . . . . 269
20 Deploying Customized Preinstallations 271
20.1 Preparing the Master Machine . . . . . . . . . . . . . . . . . . . 272
20.2 Customizing the Firstboot Installation . . . . . . . . . . . . . . . . 272
20.3 Cloning the Master Installation . . . . . . . . . . . . . . . . . . . 281
20.4 Personalizing the Installation . . . . . . . . . . . . . . . . . . . . 281
Part IV Automated Installations 283
21 Automated Installation 285
21.1 Simple Mass Installation . . . . . . . . . . . . . . . . . . . . . . 285
21.2 Rule-Based Autoinstallation . . . . . . . . . . . . . . . . . . . . 297

21.3 For More Information . . . . . . . . . . . . . . . . . . . . . . 302
22 Automated Deployment of Preload Images 303
22.1 Deploying system manually from rescue image . . . . . . . . . . . . 304
22.2 Automated Deployment with PXE Boot . . . . . . . . . . . . . . . 305

About This Guide
Installations of SUSE Linux Enterprise Server are possible in many different ways. It
is impossible to cover all combinations of boot, or installation server, automated instal-
lations or deploying images. This manual should help with selecting the appropriate
method of deployment for your installation.
Part I, “Architecture Specic Installation Considerations” (page 5)
The standard deployment instructions differ depending on the architecture used.
For differences and requirements regarding the architecture, see this part.
Part II, “Manual Deployment” (page 77)
Most tasks that are needed during installations are described here. This includes
the manual setup of your computer as well as additional software and remote instal-
lations.
Part III, “Imaging and Creating Products” (page 253)
Mass installations often require to prepare images or products furnished with the
features that are needed in this special case. Several options are described that allow
the administrator to prepare this deployment methods.
Part IV, “Automated Installations” (page 283)
To do unattended installations, either use the installation with AutoYaST or prepare
an image with kiwi or rstboot. This part describes methods to deploy these instal-
lations with a minimum of user interaction.
Many chapters in this manual contain links to additional documentation resources. This
includes additional documentation that is available on the system as well as documen-
tation available on the Internet.
For an overview of the documentation available for your product and the latest docu-
mentation updates, refer to http://www.novell.com/documentation or to
the following section.
1 Available Documentation
We provide HTML and PDF versions of our books in different languages. The following
manuals for users and administrators are available on this product:

Deployment Guide (page 1)
Shows how to install single or multiple systems and how to exploit the product
inherent capabilities for a deployment infrastructure. Choose from various approach-
es, ranging from a local installation or a network installation server to a mass de-
ployment using a remote-controlled, highly-customized, and automated installation
technique.
Administration Guide (↑Administration Guide)
Covers system administration tasks like maintaining, monitoring and customizing
an initially installed system.
Security Guide (↑Security Guide)
Introduces basic concepts of system security, covering both local and network se-
curity aspects. Shows how to make use of the product inherent security software
like Novell AppArmor (which lets you specify per program which les the program
may read, write, and execute) or the auditing system that reliably collects informa-
tion about any security-relevant events.
Virtualization with Xen (↑Virtualization with Xen)
Offers an introduction to virtualization technology of your product. It features an
overview of the various elds of application and installation types of each of the
platforms supported by SUSE Linux Enterprise Server as well as a short description
of the installation procedure.
Storage Administration Guide
Provides information about how to manage storage devices on a SUSE Linux En-
terprise Server.
In addition to the comprehensive manuals, several quick start guides are available:
Installation Quick Start (↑Installation Quick Start)
Lists the system requirements and guides you step-by-step through the installation
of SUSE Linux Enterprise Server from DVD, or from an ISO image.
xDeployment Guide

Linux Audit Quick Start
Gives a short overview how to enable and congure the auditing system and how
to execute key tasks such as setting up audit rules, generating reports, and analyzing
the log les.
Novell AppArmor Quick Start
Helps you understand the main concepts behind Novell® AppArmor.
Find HTML versions of most SUSE Linux Enterprise Server manuals in your installed
system under /usr/share/doc/manual or in the help centers of your desktop.
Find the latest documentation updates at http://www.novell.com/
documentation where you can download PDF or HTML versions of the manuals
for your product.
2 Feedback
Several feedback channels are available:
• To report bugs for a product component or to submit enhancements requests, please
use https://bugzilla.novell.com/. If you are new to Bugzilla, you
might nd the Bug Writing FAQs helpful, available from the Novell Bugzilla home
page.
• We want to hear your comments and suggestions about this manual and the other
documentation included with this product. Please use the User Comments feature
at the bottom of each page of the online documentation and enter your comments
there.
3 Documentation Conventions
The following typographical conventions are used in this manual:
•/etc/passwd: directory names and lenames
•placeholder: replace placeholder with the actual value
•PATH: the environment variable PATH
About This Guide xi

•ls,--help: commands, options, and parameters
•user: users or groups
•Alt,Alt +F1: a key to press or a key combination; keys are shown in uppercase as
on a keyboard
•File,File >Save As: menu items, buttons
•►amd64 em64t ipf: This paragraph is only relevant for the specied architectures.
The arrows mark the beginning and the end of the text block. ◄
►ipseries zseries: This paragraph is only relevant for the specied architectures.
The arrows mark the beginning and the end of the text block. ◄
•Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a
chapter in another manual.
xii Deployment Guide

1
Planning for SUSE Linux
Enterprise Server
The implementation of an operating system either in an existing IT environment or as
a completely new rollout must be carefully prepared. SUSE Linux Enterprise Server
11 provides a variety of new features. It is impossible to describe all the new features
here. The following is just a list of major enhancements that might be of interest.
Xen 3.3 Virtualization
Runs many virtual machines on a single server, each with its own instance of an
operating system. For more information, see Virtualization with Xen (↑Virtualization
with Xen).
YaST
Several new conguration options have been developed for YaST. These are nor-
mally described in the chapters about the technology involved.
SPident
The management utility SPident gives an overview of the installed software base
and claries the current service pack level of the system.
Directory Services
Several LDAP-compliant directory services are available:
• Microsoft Active Directory
• OpenLDAP
Planning for 1

Novell AppArmor
Harden your System with the Novell AppArmor technology. This service is de-
scribed in depth in Part “Conning Privileges with Novell AppArmor” (↑Security
Guide).
AIDE
This is an intrusion detection system that can be setup to detect unauthorized changes
to the system.
iSCSI
iSCSI provides an easy and reasonably inexpensive solution for connecting Linux
computers to central storage systems. Find more information about iSCSI in the
Storage Administration Guide
Network File System v4
Starting with version 10, SUSE Linux Enterprise Server supports NFS also in ver-
sion 4. This gives you performance improvements, strong security, and a “stateful”
protocol.
Oracle Cluster File System 2
OCFS2 is a general-purpose journaling le system that is fully integrated in the
Linux 2.6 kernel and later. Find an overview of OCFS2 in the High Availability
Guide .
Linux Kernel Crash Dump
Debugging kernel-related problems is now much more comfortable when using
Kexec and Kdump. This technology is available on x86, AMD64, Intel 64, and
POWER platforms.
1.1 Considerations for Deployment of
a SUSE Linux Enterprise Server
At the beginning of the planning process, you should try to dene the project goals and
needed features. This must always be done individually for each project, but the questions
to answer should include the following:
• How many installations should be done? Depending on this, the best deployment
method differs. See also Chapter 5, Deployment Strategies (page 79).
2Deployment Guide

• Will the system run as physical host, a virtual machine or as a virtual machine?
•Will the system be in a hostile environment? Have a look at Chapter 1, Security
and Condentiality (↑Security Guide) to get an overview of consequences.
• How will you get regular updates? All patches are provided online for registered
users. Find the registration and patch support database at http://www.novell
.com/linux/suse/portal/index.html.
• Do you need help for your local installation? Novell provides training, support,
and consulting for all topics around SUSE Linux Enterprise Server. Find more in-
formation about this at http://www.novell.com/products/server/.
• Do you need third-party products? Make sure that the required product is also
supported on the desired platform. Novell can also provide help to port software
to different platforms when needed.
1.2 Deployment of SUSE Linux
Enterprise Server
To make sure that your system will run awlessly, always try to use certied hardware.
The hardware certication process is an ongoing process and the database of certied
hardware is updated regularly. Find the search form for certied hardware at http://
developer.novell.com/yessearch/Search.jsp.
Depending on the number of desired installations, it is benecial to use installation
servers or even completely automatic installations. Have a look at Chapter 5, Deployment
Strategies (page 79) for more information. When using the Xen virtualization technolo-
gies, network root le systems or network storage solutions like iSCSI should be con-
sidered.
SUSE Linux Enterprise Server provides you with a broad variety of services. Find an
overview of the documentation in this book in About This Guide (↑Administration
Guide). Most of the needed congurations can be made with YaST, the SUSE congu-
ration utility. In addition to that, many manual congurations are described in the cor-
responding chapters.
Planning for 3

In addition to the plain software installation, you should consider training the end users
of the systems as well as help desk staff.
1.3 Running SUSE Linux Enterprise
Server
The SUSE Linux Enterprise Server operating system is a well-tested and stable system.
Unfortunately, this does not prevent hardware failures or other causes for downtime or
data loss. For any serious computing task where data loss could occur, a regular backup
should be done.
For optimal security and safe work, you should make regular updates of all the operated
machines. If you have a mission critical server, you should probably run a second
identical machine where you can apply all changes for testing purposes before doing
so on the real system. This also gives you the possibility to switch machines in case of
hardware failure.
4Deployment Guide

Part I. Architecture Specic
Installation Considerations

2
Installation on x86, AMD64,
Intel 64, and Itanium
This chapter describes the steps necessary to prepare for the installation of SUSE Linux
Enterprise Server on x86, AMD64, Intel 64, and Itanium computers. It introduces the
steps required to prepare for various installation methods and provides useful informa-
tion. The list of hardware requirements provides an overview of supported systems
supported by SUSE Linux Enterprise Server. Find information about available installa-
tion methods and several common known problems. Also learn how to control the in-
stallation, provide installation media, and boot with regular methods.
2.1 Required Background
To keep the scope of these guidelines manageable, certain technical assumptions have
been made. It is assumed that:
•You have some computer experience and are familiar with common technical terms.
• You are familiar with the documentation for your system and the network on which
it runs.
• You have a basic understanding of Linux systems.
For an overview of the documentation available for your product and the latest docu-
mentation updates, refer to http://www.novell.com/documentation.
Installation on x86, AMD64, Intel 64, and Itanium 7

2.2 System Requirements for
Operating Linux
The SUSE® Linux Enterprise Server operating system can be operated on a wide range
of hardware. It is impossible to list all the different combinations of hardware SUSE
Linux Enterprise Server supports. However, to provide you with a guide to help you
during the planning phase, the minimum requirements are presented here.
If you want to be sure that a given computer conguration will work, nd out which
computers have been certied by SUSE. Find a list of these computers at http://
developer.novell.com/yessearch/Search.jsp.
2.2.1 Hardware for x86
Computers based on x86 constitute a cost-effective way of building high-performance
systems. The preconditions to operating SUSE Linux Enterprise Server on this platform
are as follows:
CPU
The number of CPUs supported depends on the kernel used. Specically, these are
as follows:
Table 2.1 CPUs Supported by the Kernel
Maximum Number of
CPUs
Oldest CPU TypeKernel
32PentiumPro, Athlonkernel-default
128Pentium II, Athlon XPkernel-pae
Memory Requirements
A minimum of 512 MB is required. The minimum recommended memory is 1 GB.
For a multiprocessor system, 256 MB per processor is required. Systems with less
than 1 GB main memory need additional swap space that extends the virtual
memory to 1 GB.
8Deployment Guide