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

14
Client-Specific File: CINDEX
This file specifies configuration clauses that are available only for the associated client. Typically, these are
network recovery configuration clauses. Thus, the set of configuration clauses valid for a client system
include those listed in the general INDEX config file and the client-specific CINDEX config file.
Client-Specific File: client_name
This file indicates the hostname of the client system.
For example:
# cat client_name
testsys
Client-Specific File: client_status
This file indicates the status of the current or most recent installation.
This file contains lines that have a status “phase” followed by “Active” or “Complete”. Note that some
phases might not have an “Active” status line. The file may have consecutive “Complete” status lines.
The “DONE” line indicates a complete installation; no additional status will be reported.
For example:
# cat client_status
Boot_Client/Discover_System Complete
Waiting_To_Install Complete
Prepare_Config_File Complete
Configure_Disks Active
Configure_Disks Complete
Download_mini-system Active
Download_mini-system Complete
Loading_software Active
Loading_software Complete
Build_Kernel Active
Build_Kernel Complete
Boot_From_Client_Disk Active
Boot_From_Client_Disk Complete
Run_SD_Configure_Scripts Active
Run_SD_Configure_Scripts Complete
Run_Postconfigure_Scripts Active
Run_Postconfigure_Scripts Complete
DONE
The Ignite-UX client I/O inventory phase is done independently from the server, since an inventory must be
done in order to perform network configuration. The client requires network configuration to NFS mount the
client-specific directory on the server and start reporting status.
For server-controlled installation, the client will be in the “Waiting_To_Install Active” phase. For
example:
# cat client_status
Boot_Client/Discover_System Complete
Waiting_To_Install Active