Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux

12
Ignite-LUX includes two approaches for CMS integration. The ignite command improves control by using
XML for data interchange and is the preferred approach. . Legacy Ignite commands such as
manage_index and instl_adm may also be used for CMS control. Both approaches may be used.
Terminology
HP-UX uses different release identifiers for customer marketing communication and technical product
implementation. HP-UX 11i v3 is also known as HP-UX 11.31; HP-UX 11i v2 is also known as HP-UX
11.23.
Deployment software and CMS software seem to have fairly similar concepts. However, there are
considerable differences in the terms used. For example, Ignite-UX uses the term “configuration clause” to
refer to the combination of the set of software to be installed and the config file content used to control
installation.
You may choose exactly one configuration clause for installation. In the case of an automated installation,
that configuration clause controls client installation details. In the case of an interactive installation, that
configuration clause provides defaults that may be modified prior to installation via the Ignite-UX user
interface on the client system. The set of configuration clauses is stored in
/var/opt/ignite/data/INDEX.
The Ignite-UX Administration Guide includes a glossary of terms.
Ignite-UX Concepts
Universal install kernels - The same Ignite-UX install kernels and install file systems are used for all Integrity
systems: rack-mount, Blade, HPVM, nPar, and vPar.
Install kernel and installed software consistency - You must boot the install kernel that matches the HP-UX
release to be installed. For example, to install HP-UX 11.31 you must boot the HP-UX 11.31 install kernel.
Config-based control - Ignite-UX performs an installation based on config file content, which reflects user
interface settings, is able to specify considerable system configuration detail, supports formulas, and
supports conditional statements. This is Ignite-UX’s equivalent of what is often referred to as install scripts by
other OS deployment.These config file features are helpful in constructing:
• golden images that may be used for a variety of systems
• cloned systems
• recovery images for disaster recovery
OS content for hardware support - You should consider the software included for installation that supports
hardware and virtualization. The recommended approach is to include the full set of drivers needed for all
systems. This approach allows you to create universal OS images.
Configuration adaptation to hardware - Ignite-UX will significantly adapt configuration details to the system
being installed. Recovery will restore a system to a nearly original state. A recovery image may be used to
recover a very dissimilar type of system. For example, Ignite-UX will find replacement disks if needed.
Consult Ignite-UX config file content details in the instl_adm(4) manpage for information regarding how to
control Ignite-UX behavior.