Making the operating system archive:
Once the golden system is configured the way you want it, either install the Ignite-UX software or copy the file
/opt/ignite/data/scripts/make_sys_image to /tmp on the golden system. If you’ve copied the above file,
change the permissions of /tmp/make_sys_image to be executable.
On the Ignite-UX server make sure there is sufficient space in the target file system to hold the golden-image archive that will
be created. By default, the directory is /var/tmp, but you may want to store the golden image on another file system
because /var is typically more difficult to extend than other file systems.
1. On the golden system, run:
# /tmp/make_sys_image -s \
–d / -n
For example, executing:
# /tmp/make_sys_image -s 75.99.87.15 \
–d /var/opt/ignite/data/Rel_B.11.23 -n B.11.23_VM_archive.gz
will create the golden image in the directory /var/opt/ignite/data/Rel_B.11.23 on the host with the IP address
75.99.87.15. Note that the golden system must be listed in the /.rhosts file on the Ignite-UX server. If not, you will see
the following error:
ERROR: Cannot remsh server system_name (check server .rhosts file).
Typically make_sys_image will run for several minutes.
Once finished, it will have created the B.11.23_VM_archive.gz gzip (suffix .gz) file (for example,
/var/opt/ignite/data/Rel_B.11.23/B.11.23_VM_archive.gz ) on the Ignite-UX server.
2. In the directory where the archive has been created, change the ownership of the archive to bin:
# chown bin:bin *.gz
3. You will need to make sure that the directory where the golden image resides is available for an NFS mount. In our
example, the path /var/opt/ignite/data/Rel_B.11.23 is added to the Ignite-UX server’s /etc/exports file as
follows:
/var/opt/ignite/data/Rel_B.11.23 -anon=2
and is subsequently exported by running exportfs –a.
Configuring the Ignite-UX server to recognize the golden image
Once the golden image has been created, you’ll need to finish setting up the configuration for use on the Ignite-UX server.
The steps to do this are as follows:
1. Capture the necessary impacts statements to be used in the configuration file by executing:
# /opt/ignite/lbin/archive_impact -t -g B.11.23_VM_archive.gz
in the directory where the archive was created and capturing the output.
For our example, in the directory where the archive resides (/var/opt/ignite/data/Rel_B.11.23), you would run:
# /opt/ignite/lbin/archive_impact -t -g \
./B.11.23_VM_archive.gz > impacts.txt
This may take a minute or two to complete.
2. Create a configuration file by copying the example configuration file to the directory with the system archive. For
example:
# cp /opt/ignite/data/examples/B.11.23.golden_image.cfg \
/var/opt/ignite/data/Rel_B.11.23/vm.cfg
You’ll need to customize the configuration file for your archive as follows.
3. In the configuration file, modify the nfs_source definition in the sw_source section so that it references the Ignite UX
server and the correct path. That is, using the example systems here, change:
nfs_source = "10.2.72.150: /var/opt/ignite/archives/Rel_B.11.23"
to:
nfs_source = "75.99.87.15: /var/opt/ignite/data/Rel_B.11.23"
4. Continuing in the configuration file, modify the init sw_sel section(s) so that it corresponds to your golden image.
Note that the example configuration specifies two different images – one for Itanium-based systems (ia64) and another for
PA-RISC systems (hppa). Assuming you didn’t create an image for a PA-RISC systems version of HP-UX, you may simply
delete the init sw_sel section for the PA-RISC system image ("is_hppa"). Follow these steps:
a) Change the description parameter to better describe your golden image. For example, change:
description = "B.11.23 IA golden image archive"
to:
description = "HP-UX 11.23 image for VMs"
b) Change the archive_path to contain the name of the actual archive file. Using our example, you would change:
archive_path = "B.11.23_archive_IA.gz"
to:
archive_path = "B.11.23_VM_archive.gz"
c) Replace the ‘impacts’ lines with those captured in step 1 above. For example, replace the lines:
impacts = "/" 7659Kb
impacts = "/dev" 11Kb
impacts = "/etc" 76229Kb
impacts = "/home" 1Kb
impacts = "/opt" 2223298Kb
impacts = "/sbin" 109002Kb
impacts = "/stand" 51127Kb
impacts = "/usr" 2379518Kb
impacts = "/var" 848454Kb
with:
impacts = "/" 833Kb
impacts = "/dev" 13Kb
impacts = "/etc" 82077Kb
impacts = "/home" 133696Kb
impacts = "/opt" 2536512Kb
impacts = "/sbin" 111333Kb
impacts = "/scratch" 135843Kb
impacts = "/stand" 52187Kb
impacts = "/usr" 2396952Kb
impacts = "/var" 1603044Kb
where the latter are those from the impacts.txt file created in step 1.
d) If your golden image has the HPVM-Guest bundle installed (recommended), then you’ll want to make sure the dynamic
memory device driver is configured correctly. To achieve this, add the following line after the init sw_sel stanza:
set_kernel += "module hpvmdynmem loaded"
The resulting section will then read as follows:
(is_ia64) {
init sw_sel "B.11.23 IA golden image archive" {
description = "HPUX 11.23 image for VMs"
sw_source = "golden image archive"
sw_category = "HPUXEnvironments"
archive_type = gzip tar
archive_path = "B.11.23_VM_archive.gz"
impacts = “/” 833Kb
impacts = “/dev” 13Kb
impacts = “/etc” 82077Kb
impacts = “/home” 133696Kb
impacts = “/opt” 2536512Kb
impacts = “/sbin” 111333Kb
impacts = “/scratch” 135843Kb
impacts = “/stand” 52187Kb
impacts = “/usr” 2396952Kb
impacts = “/var” 1603044Kb
} = TRUE}
set_kernel += "module hpvmdynmem loaded"
…
5. Edit the file /var/opt/ignite/INDEX to install the new configuration for Ignite-UX. This is done by adding a new
cfg section to that file. For our example, the new cfg section would read as follows:
cfg "HP-UX B.11.23 VM Config" {
description "This selection supplies the VM configuration."
"/opt/ignite/data/Rel_B.11.23/config"
"/var/opt/ignite/data/Rel_B.11.23/vm.cfg"
"/var/opt/ignite/config.local"
}
6. Verify the syntax of your newly-entered configuration information with the following command:
# /opt/ignite/bin/instl_adm –T
If this command is successful, your configuration is now ready to use.