Configuring the Ignite-UX Server to Recognize the Golden Image

To create an Ignite-UX configuration file for the golden image, use the example file: /opt/ignite/data/examples/core11.cfg

Create a copy of the example configuration file:
cp /opt/ignite/data/examples/core11.cfg \ /var/opt/ignite/data/Rel_B.11.11/core_archive.cfg
The destination file name is arbitrary. You can store configuration files anywhere on the system you chose. Ignite-UX manages the names and locations using the /var/opt/ignite/INDEX file (see Step 3). This file must be accessible using tftp.

Modify the core_archive.cfg file to set up the golden image for NFS transfer. (See the sw_sel example following these instructions. Use values appropriate for your systems.) Key changes are:

In the sw_sel clause, change the following:
nfs_source = "10.2.72.150:/var/opt/ignite/archives/Rel_B.11.11"
This points nfs_source to the directory where the archive resides, which must be NFS exported.
In the init sw_sel clause, change the following:
description = "Archive HP-UX 11.11 CDE"
This configuration will appear as an operating system environment choice on the Basic tab (see “Basic Tab”) in the Ignite-UX GUI.
Ensure that the following variable:
archive_path = "hostname.gz"
where:
hostname points to the actual file in combination with the nfs_source line in step a.
Add impacts lines in the init sw_sel clause by executing the archive_impact command. The example command below indicates a tar archive compressed with gzip. See archive_impact(1M) for more information.
/opt/ignite/lbin/archive_impact -t -g archive_file
Include the results in the file, replacing the example impacts lines.
Review the init sw_sel "English"clause and modify it for the locales you want available in the golden image.
The format of an entry in the locale list is
"<locale>:<description>"
where <locale>is the name of a locale shown in the output of the locale -acommand run on the golden image system (for example: ja_JP.SJIS). The <description> is a text string labeling that particular locale. The <description> text string cannot contain white space; if you need more than one word in the description, use the underscore character. Locale list entries must be enclosed in double quotes.
For example, the following line would make available any of the Japanese or English locales on the system:
locale = { "ja_JP.SJIS:Japanese", "ja_JP.eucJP:Japanese", "ja_JP.utf8:Japanese", "SET_NULL_LOCALE:English", "C:English" }
The locale line in the configuration file should not be wrapped; it should be one continuous line. Never add locales that do not exist in the golden image.
Be aware that by listing a locale, it means that it can be selected via itool. Any locale present when the golden image is created will still be available on any system installed using this golden image, whether it is listed or not.

Here is the complete sw_sel clause example:

init sw_sel "golden image" {
  description = "Archive HP-UX 11.11 CDE"
  sw_source = "core archive"
  sw_category = "HPUXEnvironments" 
  archive_type = gzip tar
  # For NFS, the path to the archive is relative to the mount
  # point specified in the sw_source: 
  archive_path = "hostname.gz"
  # ftp/remsh sources can use a full path:
  # archive_path = "/pub/IUXarchives/B.11.11_CDE.gz"
  impacts = "/" 23Kb
  impacts = "/.dt" 35Kb
  impacts = "/TT_DB" 18Kb
  impacts = "/etc" 1375Kb
  impacts = "/export" 1Kb
  impacts = "/opt" 74079Kb 
  impacts = "/sbin" 13449Kb
  impacts = "/stand" 1Kb 
  impacts = "/tmp" 1Kb
  impacts = "/usr" 225459Kb
  impacts = "/var" 5736Kb
} = TRUE

Add the new configuration file (core_archive_cfg) to Ignite-UX:

Edit the /var/opt/ignite/INDEX file to install a new configuration to Ignite-UX. For this example, add a new cfg clause as follows:

cfg "HP-UX B.11.11 archive" { 
  description "some description of this archive..." 
  "/opt/ignite/data/Rel_B.11.11/config" 
  "/var/opt/ignite/data/Rel_B.11.11/core_archive_cfg" 
  "/var/opt/ignite/config.local"
}

The line of most interest is the one containing core_archive_cfg. The config and config.local files contain default configurations.

The /var/opt/ignite/config.local file should be the last file in the cfg clause. The last configuration file has the highest priority and can override values in the configuration files listed before it.

The file /opt/ignite/data/Rel_B.11.11/configsupplies the disk and file system layout defaults, plus other control information required by Ignite-UX. It must be first in every cfg clause.

Each cfg clause appears as an available configuration to Ignite-UX. Therefore, the string HP-UX B.11.11 archive now appears as a valid configuration.

Ensure the target client has NFS access to the archive. In the sw_source clause in the previous step, we specified the location of the golden archive to be a file on an NFS server. You need to ensure clients have access to this directory.
For HP-UX 11i v3 systems:
- Edit the /etc/dfs/dfstab file on the source client.
- Append ,ro=target_client to the -o argument of the source client's line, where target_client is a fully qualified client name.
- Run # shareall -F nfs
For HP-UX 11i v1 and 11i v2 systems:
- Edit the /etc/exports file on the source client.
- Append :target_client to the end of the source client's line, where target_client is the hostname of the target system.
- Run # exportfs -av
See dfstab(4) or exportfs(4) for more information.

Configuring the Ignite-UX Server to Recognize the Golden Image

Technical documentation

» Table of Contents

» Glossary

» Index