![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| ||
Chapter 6Configuration Stage 2: Adding User-Defined Data to the Flash ArchiveThis chapter describes how to add user-defined data and user-specific installation scripts to an existing flash archive. The flash archive can be:
Stage 2 is optional. If you do not plan to add user applications and user-defined configuration data, you do not need to read this chapter. The slconfig command prepares the software load configuration data, and the flconfig command incorporates the user-defined configuration data into the flash archives. When stage 2 is complete, you have one or more flash archives that include user applications and user-defined configuration data. These archives are called configured flash archives. This chapter contains the following sections:
Configuration Stage 2 ChecklistBefore you perform configuration stage 2, ensure you have:
Configuration Stage 2 ProcedureThe following figure shows the configuration procedure for stage 2, resulting in a configured flash archive. Figure 6-1 Configuration Stage 2 ![]() Creating a User Application Configuration File for a Node GroupThe user application configuration file contains a structured list of user-defined configuration data to be run at specific stages of cluster startup. User-defined configuration data can be:
A user application configuration file is required for each node group that is to be installed with user applications. If no applications are to be deployed, it is not necessary to have any user application configuration files. The application installation scripts can be executed at any one of three stages during the boot phase of the target cluster:
Figure 6-2 Boot Sequence for User Application Configuration Files ![]() Note - When creating the application configuration file, note that the PRE_SCRIPT scripts do not run under the root directory (/) during the Solaris Jumpstart finish script. For more information, see the Solaris Custom JumpStart Guide. The following example is a user application configuration file config.soft_switch, for a node group soft_switch. Example 6-1 Example of a User Application Configuration File
| ||
| ||
![]() |