Red Hat SATELLITE 5.1.0 RELEASE NOTES Manual de instalación descargar pdf (Pagina 21)

Chapter 1. Introduction to z/VM and Linux 3

1.2 This book’s approach

Today there are numerous technical publications that discuss virtualization, but few of them

demonstrate how to achieve it. This book gives you the “hands on” instructions needed to

achieve a virtualized environment on your enterprise.

The approach adopted is to keep all solutions simple, as expressed in the well-known quote

from Albert Einstein “Everything should be made as simple as possible, but not simpler”. This

book attempts to use a clear and insightful presentation to explain the somewhat complex

topics covered here.

1.3 Choices and decisions made in this book

When deciding on installing, maintaining and provisioning (cloning) Linux virtual servers

under z/VM, there are many basic choices to make. Here are some of the choices and

assumptions made in this book:

򐂰 Use of “roll your own” cloning versus cloning products

A discussion of cloning products such as Aduva Onstage, the Mainstar Provisioning

Expert, IBM Tivoli® Provisioning Manager and IBM Director is beyond the scope of this

book. Although these are all viable solutions, the cloning described in this book allows you

to roll your own Linux images without requiring such products. However, these products

are more sophisticated than the simple clone script and z/VM configuration described in

this book.

򐂰 Use of the USER DIRECT file versus a directory maintenance product

The use of the USER DIRECT file was chosen over a directory maintenance product such as

IBM DirMaint™ or CA’s VM:Direct.

If using DirMaint as a directory maintenance product would be better for your enterprise,

you can refer to Getting Started With Linux, SC24-6096, to configure z/VM. To configure

Linux, however, use this book.

򐂰 Use of predefined user IDs versus provisioning

z/VM user IDs must be predefined to clone. There is no attempt to

provision them (define

and bring Linux user IDs online automatically) as part of the cloning process. The target

Linux user ID must exist with the appropriate minidisks defined.

򐂰 Use of read-write versus shared read-only Linux /usr/ file system

Some cloning solutions use an environment that shares the /usr/ file system. This choice

often makes the solution more complex, especially when adding software to the virtual

servers. For this book, a read-write /usr/ file system on the virtual servers was chosen to

keep things as simple as possible.

򐂰 Use of conventional 3390 ECKD™ DASD versus FBA disks accessed using SCSI over

FCP

The System z server has traditionally only supported 3390 DASD. Support has been

extended to include SCSI/FBA disks in storage area networks (SANs). The support of

FBA disks is slightly more complicated than conventional DASD. In keeping things as

simple as possible, only conventional DASD is described in this book.

1 2 ... 16 17 18 19 20 21 22 23 24 25 26 ... 267 268

Sin comentarios

Red Hat SATELLITE 5.1.0 RELEASE NOTES Manual de instalación Pagina 21