System information

54 Sharing and maintaining SLES 10 SP2 Linux under z/VM
Figure 1-16 Adding a second user ID, ROGOLD2, to store the next
Once the Linux machines are running and linked to the read-only gold disks, the gold disks
cannot be updated until those machines are either shutdown or migrated. Figure 1-16 depicts
how systems can be safely migrated. The machines shown in the lower left, LNX227 and a
new read-only Linux system, LNX242, are running under the current golden read-only disks.
When an updated Linux system is needed, a new golden image is created, tested and stored
onto S10GOLD2. A new RO2GOLD2 EXEC is now available to copy from the S10ROGLD system to
the new S10GOLD2 user ID.
After the new golden image has been tested, the read-only Linux systems can be migrated to
it, LNX242 is this example. This is done by changing the LINK statements in the directory entry
of the system being migrated. It is simply set to point to the 21Bx minidisks on S10GOLD2 rather
than S10GOLD. To make changing the link statements easier, two new directory PROFILEs are
created.
The following sections demonstrate how to set up this maintenance system:
򐂰 “Preparing for the new maintenance system”
򐂰 “Creating a new read-only Linux system” on page 56
򐂰 “Performing maintenance to the golden image” on page 57
򐂰 “Copying the updated golden image” on page 57
򐂰 “Updating the directory of one read-only Linux” on page 59
򐂰 “Testing the updated golden image” on page 59
Disk planning for maintenance system
Of the 4 3390-9s and one 3390-3 allocated, the last 3390-9 had only allocated 1669 cylinders
for the first read-only system, LNX227. The remaining space can be given to a second “gold”
virtual machine, S10GOLD2, and to a second read-only clone, LNX242. You may consider using
a fifth 3390-9 for S10GOLD2 to keep the gold disks separate from the “clones”.
S10ROGLD
1Bx disks
RO2GOLD
S10GOLD2
[new]
RO2GOLD2
LNX242
RO clone
S10DFLT2
S10GOLD
[current]
LNX227
RO clone
S10DFLT
LNX242
RO clone
S10DFLT