ignite.5 (2012 03)

i
ignite(5) ignite(5)
For non-SD (archive) operating system software:
Ignite-UX has the capability of loading a client from an archive image taken from a client
that represents a standard configuration. This method gives significantly faster install
times, but may not be as flexible as using an SD source.
You will first need to generate the archive image of a client in the desired state. It is
recommended that the
/opt/ignite/data/scripts/make_sys_image
script be
used to accomplish this task.
Once an archive image is created, a configuration file that represents the location and
attributes of that image must be created before Ignite-UX may use it.
A sample of a config file that may be used with a core archive may be found at:
/opt/ignite/data/examples/B.11.23.archives.cfg
The comments in this example file describe where to copy the file and what to change in
the file to make it reference your archive and work in your environment. There are also
example config file files for B.11.11 and B.11.31.
4. Add additional applications (optional).
If you have other software you would like to have loaded during the client installation, you may
create configuration files similar to what was done for the core operating system software by
using
make_config and manage_index, or by using an example configuration file and
modifying it.
For SD application software:
Run the following commands for each depot you plan to load SD software from during the
installation. The
make_config command only handles SD software that is packaged in
bundle form. If the SD depot you want to use has software not contained in a bundle (for
example, a collection of patches), the make_bundles command may be used to create
bundles in the depot prior to running make_config. See make_bundles (1M) for more
information on various usages and options of that command.
make_bundles /depots/11.23_patches
make_config -s server:/depots/11.23_patches \
-c /var/opt/ignite/data/Rel_B.11.23/patches_cfg
manage_index -a -f /var/opt/ignite/data/Rel_B.11.23/patches_cfg
To make a depot containing compilers available which are already in bundles (no need to
use make_bundles):
make_config -s server:/depots/compiler \
-c /opt/ignite/data/Rel_B.11.23/compilers_cfg
manage_index -a -f /opt/ignite/data/Rel_B.11.23/compilers_cfg
The depot server (in this example <server> ) should be replaced with the server on which
you have the SD software. The make_bundles command must be run on the same
client the depot exists. If the depot is not on the Ignite-UX server, you may need to copy
the make_bundles command to the depot server and run it there.
Note: The
make_config command will need to be rerun each time new software is
added or modified in the depots.
make_config constructs Ignite-UX config files which correspond to SD depots. When an
SD depot is used as part of the Ignite-UX process, it must have a config file which
describes the contents of the depot to Ignite-UX. This command may automatically con-
struct such a config file given the name of an SD depot on which to operate. This com-
mand should be run when adding or changing a depot which will be used by Ignite-UX.
manage_index is used to manipulate the /var/opt/ignite/data/INDEX file.
This utility is primarily called by other Ignite-UX tools but may also be called directly.
For non-SD application software:
If the source is not an SD depot, the
make_config command is not applicable. You will
need to create a unique config file that includes the non-SD software. A sample of a config
file that performs a non-core archive may be found at:
HP-UX 11i Version 3: March 2012 − 3 − Hewlett-Packard Company 3