Red Hat LINUX VIRTUAL SERVER 4.6 - ADMINISTRATION Manuale di Installazione Scaricare il pdf (Pagina 24)

4 z/VM and Linux on IBM System z: The Virtualization Cookbook for Red Hat Enterprise Linux 6.0

򐂰 Provisioning versus predefined user IDs: z/VM user IDs must be predefined to clone them.

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.

򐂰 Shared read-only Linux /usr/ file system versus read-write: Some cloning solutions use

an environment which shares the /usr/ file system. This choice often makes the solution

more complex, especially when adding software to the virtual servers. A read-write /usr/

file system on the virtual servers is chosen to keep things as simple as possible.

򐂰 Conventional 3390 ECKD™ DASD versus FBA disks accessed with 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.

򐂰 Cloning script or EXEC versus manual installation: Two methods of cloning are described:

a manual process and a process that uses a Linux bash script. The manual method is

described so that we can better teach these concepts. The Linux script is provided so you

can save time.

1.4 Infrastructure design

To install and configure z/VM, install, configure, and clone Linux, or provision virtual servers,

there must be a certain infrastructure design in place. A System z server with its associated

resources and the z/VM operating system define much of this infrastructure.

1 2 ... 19 20 21 22 23 24 25 26 27 28 29 ... 295 296

Nessun commento

Red Hat LINUX VIRTUAL SERVER 4.6 - ADMINISTRATION Manuale di Installazione Pagina 24