Client and Server Control
Ignite-UX installation sessions for multiple clients
can be controlled from a single server in a true client/server model.
The Ignite-UX Graphical User Interface (GUI) helps you manage multiple simultaneous
installations. Alternatively, you can run a single installation session
from the client console if that is more convenient. A single Ignite-UX
server can install multiple HP-UX releases.
Easy-to-Use GUI
The Ignite-UX GUI uses tabs and dialog boxes for
task navigation. The Ignite-UX GUI only runs on an Ignite-UX server.
Terminal User Interface
Ignite-UX uses a terminal user interface (TUI) with keyboard
navigation when run remotely from a client or other system. The TUI
has the same functionality as the GUI that runs on the Ignite-UX server.
Command Line Interface
Commands that power Ignite-UX can be executed
directly from the operating system's command shell on an Ignite-UX
server or client. For the list of commands, see “Ignite-UX Commands”.
Multi-Sourced Installations
You can install the base operating system from
one Software Distributor (SD) depot, a set of patches from another
depot, and the applications you want from a third depot all in one
session.
Multiple Archive Formats
In addition to supporting SD depot sources, Ignite-UX
supports tar, cpio, and with
11i v3, pax archives. Tools are provided to help
you create a golden image, or known client configuration, that you
can use to install on other clients.
Custom Installations
It is easy to create a system that is ready to
go as soon as the installation session completes. Many of the tasks
typically done as separate steps after an installation are now incorporated
into the Ignite-UX installation process. Ignite-UX lets you specify
what kernel parameters you want set and what user-supplied scripts
you want to run as part of the session. Many different script hooks
are provided so you can add your own customizations during and after
the installation. Also, the host and networking information that must
normally be supplied at first boot can be specified at installation
time. You can:
Create a configuration
for your particular needs, save it, and then quickly apply that configuration
to multiple installation clients.
Set up a configuration
and then install it on a client with no further user interaction.
This is possible for both the initial installation and the reinstallation
cases.
Scan a system and produce
a report detailing what hardware is present, how the disks are used,
what kernel modifications have been made, and what software has been
installed. This report can be customized to meet your needs.
Construct your own customized
bootable installation/recovery media. An example script, make_media_install, is provided that can help you create
bootable media (PA-RISC tapes, CDs, and DVDs) with or without golden
archives and/or SD depots included. The example script can be found
at
/opt/ignite/data/scripts/examples/make_media_install
System Recovery
You have consistent, reliable recovery in the
event of a catastrophic failure of the system disk or root volume
group using either the make_tape_recovery or make_net_recovery command.
Support for Multiple Architectures
Ignite-UX supports both the Precision Architecture Reduced Instruction Set Computing (PA-RISC) and the Intel®Itanium® (Itanium®-based) hardware architectures.
Support for HP Servicecontrol Manager
Ignite-UX supports installing HP-UX clients in
the HP Servicecontrol Manager environment. For details, see the HP Servicecontrol Manager 3.0 User's Guide.
Printable version
