Tivoli Provisioning Manager for OS Deployment Version 7.1.1.9
Total Page:16
File Type:pdf, Size:1020Kb
Tivoli Provisioning Manager for OS Deployment Version 7.1.1.9 Getting Started Tivoli Provisioning Manager for OS Deployment Version 7.1.1.9 Getting Started ii Tivoli Provisioning Manager for OS Deployment: Getting Started Contents Chapter 1. Getting started .......1 The deployment process ..........10 Product overview.............1 Universal images ............11 Components ..............1 Shared repository and its cleanup .......11 Product topology .............4 Setting up a system profile by unattended setup . 4 Chapter 2. Glossary .........15 Setting up a system profile by cloning ......5 Choosing the correct way to boot your target . 5 Chapter 3. Notices ..........21 Types of PXE network boot ........6 Network boot process ..........9 © Copyright IBM Corp. 2012 iii iv Tivoli Provisioning Manager for OS Deployment: Getting Started Chapter 1. Getting started Product overview The product is a database-driven, network-based deployment solution. Using an easy-to-use interface, the product provides Windows cloning and unattended setup, Linux cloning, and unattended setup, Solaris cloning and unattended setup, AIX® unattended setup, and VMWare ESX unattended setup, from Windows, Linux, Solaris, and IBM® AIX servers. In addition to BIOS targets, the product can also manage Unified Extensible Firmware Interface (UEFI) enabled targets. Support for UEFI targets is currently provided for Windows deployment only. Using industry standards such as Wake on LAN and vPro, PXE and OpenBOOT, ODBC and JDBC, DMI and PCI, Microsoft system preparation tool (Sysprep), Kickstart, Autoyast, Jumpstart and NIM, the product provides ready to use installation of operating systems and selected software on tens, or even hundreds, of computers simultaneously. The deployment source can be on the network (with either unicast or multicast downloading), on a CD or DVD, or on a disk partition. Components The product is made of server-side components, installed using a typical setup program, of web interface components, and of target-side applications, automatically installed by the target through the network. The server-side components include: v The OS deployment server, running in the background as a service. This component provides the PXE remote-boot capability and multicast file access to the remote-boot targets. v A deployment database, accessed through the standard ODBC/JDBC interface, and through the product TCP-to-ODBC/JDBC Gateway service. This database stores the Bill of Material for every target, including information about what software modules must be installed. v The web interface, a Web-based application used to prepare and supervise deployments. Through the web interface, you can configure the OS deployment server, manage objects used during a deployment, and create recovery CDs and DVDs. You can also visualize targets into their different groups. The parameters and status of each target can be controlled (for example, when a target requests a remote-boot through PXE). The web interface side application, typically installed on the server, is the web interface extension, running in background as a service. Optionally, a web interface extension can be installed on targets, so that you can take control of them remotely. The web interface extension is useful, for example, to restart the computer when a deployment starts, or to perform an operating system inventory. Several features of the web interface are not available when the web interface extension is not © Copyright IBM Corp. 2012 1 installed on the server. The web interface extension is a piece of software designed to run as an operating system application (a Windows application or a UNIX application). There are two target-side tools: Deployment engine The deployment engine is a stand-alone mini-operating system used for all management tasks to be performed outside of the real operating system, such as operating system installation. This deployment engine never has to be installed manually on target systems, because it is downloaded automatically when target systems are instructed to boot on the OS deployment server in their DHCP configuration. After the deployment engine is started, it loads a ramdisk which can perform any kind of operations on the target, such as v partition and format disks v install a complete operating system such as Windows or UNIX v wipe the disks The deployment engine is a stand-alone management platform and does not require an operating system. web interface extension The web interface extension is a small program that can run on most operating systems (Windows, AIX, Linux , Solaris) either in the background as a service or as a command-line tool. It provides cross-operating system connectivity to the management platform for targets with an installed operating system. It can be used to collect information from targets, to remotely initiate tasks on a target from the OS deployment server, or to trigger commands on the OS deployment server from a target. The web interface extension can access all files on the hard disk and other drives through the operating system. When running under Microsoft Windows, it can also access the system registry, and all system information published by drivers using the Windows Management Interface (WMI). In addition, for all Intel-based operating systems, the Web interface extension can install a hook on the boot process to force a PXE boot or to start the deployment engine in offline mode, to trigger pre-operating system management tasks such as migration or recovery. When you install the product you are installing the OS deployment server. The target side is embedded into the server, and sent to computers through a network connection such as a network boot or PXE boot, or through media such as a CD,a diskette,orahard disk partition. Note: It is also possible to boot targets over the network without using PXE. The installation process is exemplified in Figure 1 on page 3. 2 Tivoli Provisioning Manager for OS Deployment: Getting Started IBM Tivoli Provisioning Manager for OS Deployment 1 Setup wizard Installation files contain server-side and target-side components Install 2 Tivoli Provisioning Manager for OS Deployment server CD-ROM Runs Contains - the server-side component - the deployment engine - optionally, the Web interface extension - the Web interface extension Stores - the deployment engine - the Web interface extension Network 3 Target Target Target Boots on the network Boots on the network Boots on the CD-ROM and loads the and loads the and loads the deployment engine deployment engine deployment engine 4 Target Target Target Runs the deployment Runs the deployment Runs the deployment engine which loads a engine which loads a engine which loads a ramdisk ramdisk ramdisk (MCP for Linux) (WinPE2 for Windows) (WinPE2 for Windows) 5 Target Target Target The ramdisk performs The ramdisk performs The ramdisk performs tasks such as tasks such as tasks such as operating system operating system operating system installation installation installation 6 Target Target Target - Boots into the operating Boots into the operating - Boots into the operating system, for instance system, for instance system, for instance Linux. Windows Windows. - Runs the Web - Runs the Web interface extension. interface extension. Figure 1. Tivoli Provisioning Manager for OS Deployment components 1. The installer, containing server-side and target-side components, installs the server-side and potentially the Web interface extension on the server computer. Chapter 1. Getting started 3 2. A CD can then be created containing both the deployment engine and the web interface extension. 3. Computers then boot, loading the deployment engine either from the PXE server (OS deployment server), or from the CD. 4. The deployment engine loads a ramdisk, Linux deployment engine for Linux, WinPE for Windows. 5. The ramdisk can now perform all kinds of tasks, including operating system installation. 6. The targets boot into the operating system (Windows, Linux, Solaris,... ) , with the web interface extension optionally running. Product topology The product topology to automate remote deployment of operating systems and virtual images can be as simple as a single LAN implementation or a more complex implementation involving a large enterprise with multiple subnets with remote sites connecting through a low speed communication link. When planning your topology, you must make the following considerations: v What is the operating system of the computer where the OS deployment server will be installed? v Where will the database be located and what is the name of the database engine (DB2, Access,...)? v Will there be a single OS deployment server or a hierarchy of servers? v Where will the browser be located and what type of browser and version? The following diagram depicts a typical product topology with a single LAN, a single OS deployment server separate from the DHCP server, and a number of target computers. host DHCP host server host…. hosthost host LAN target hypervisor guest Web web interface browser extension database Tivoli Provisioning Manager for OS Deployment server Setting up a system profile by unattended setup Use unattended setup to set up a system profile without actively being involved when the process occurs. Setting up an automated system profile by unattended setup typically involves the following steps: 4 Tivoli Provisioning Manager for OS Deployment: Getting Started v Installing the OS deployment server on a computer v Creating a system profile by providing the installation CDs and choosing installation options v Creating software modules for most commonly used business applications and other software, using the web interface v Optionally, designing automatic binding rules and fixed configuration parameters for fully unattended deployment on unknown targets Setting up a system profile by cloning A cloning-mode system profile requires you to configure a target, prepare it for cloning, and run the cloning process directly on the computer. However, the native mode of operation of Tivoli® Provisioning Manager for OS Deployment is centered around cloning-mode system profiles, because this method of deployment is faster than unattended installation.