Automated Installer Use Cases

The examples in this section illustrate the major steps to configure services on an AI server. The cases start from the simplest service configuration and develop to a more advanced configurations. Most of the configuration steps for establishing an install service are optional and whether you use the depends on your environment.

Figure 7-2  AI Server Supporting One Architecture and One OS

Example 7-1  AI Server Supporting One Architecture and One OS

In this example, an AI server is configured to support only one client architecture using one OS. To create this environment:

1. Configure the AI server. See How to Set Up An AI Server.

2. Create an install service. See Creating an Install Service.

In this example, the AI server includes an install service that includes the default AI manifest. When the client is booted after the installation completes, an interactive tool prompts for system configuration information because no system configuration profile was configured. Any additional configuration steps will need to be done manually. System configuration profiles can be added to automate the system configuration steps.

Figure 7-3  AI Server Supporting Two Architectures

Example 7-2  AI Server Supporting Two Architectures

In this example, an AI server is configured to support two client architectures. To create this environment:

1. Configure the AI server. See How to Set Up An AI Server.

2. Create an install service for the x86 clients. See Creating an Install Service.

3. Create an install service for the SPARC clients.

In this example, the AI server includes two install services, one for each client architecture. Each service includes a default manifest. When the client is booted after the installation completes, an interactive tool prompts for system configuration information because no system configuration profile was configured. Any additional configuration steps will need to be done manually. Profiles can be added to automate the system configuration steps.

Figure 7-4  AI Server Supporting One Architecture and Two Disk Layouts

Example 7-3  AI Server Supporting One Architecture and Two Disk Configurations

In this example, an AI server is configured to support only one client architecture with two configurations for the client disk layout. To create this environment:

1. Configure the AI server. See How to Set Up An AI Server.

2. Create an install service for the clients. See Creating an Install Service.

3. Create an AI manifest for the second disk layout. See Chapter 10, Provisioning the Client System.

4. Associate the second manifest with the install service. See Associating Client-Specific Installation Instructions With an Install Service.

In this example, the AI server includes one install service with two AI manifests. The default manifest includes one disk layout. The second manifest includes a second disk layout. The second manifest is associated with criteria to identify the clients that should use it. All other clients will use the default manifest. When the client is booted after the installation completes, an interactive tool prompts for system configuration information because no system configuration profile was configured. Any additional configuration steps will need to be done manually. Profiles can be added to automate the system configuration steps.

Figure 7-5  AI Server Supporting One Architecture and Two Disk Configurations

Example 7-4  AI Server Supporting One Architecture and Two Time Zones

In this example, an AI server is configured to support only one client architecture with two system configurations that set the time zone. To create this environment:

1. Configure the AI server. See How to Set Up An AI Server.

2. Create an install service for the clients. See Creating an Install Service.

3. Create a system configuration profile for one time zone. See Chapter 11, Configuring the Client System.

4. Create a system configuration profile for the second time zone.

5. Associate both system configuration profiles with the install service. See Associating Client-Specific Configuration Instructions With Install Services.

In this example, the AI server includes one install service, which includes the default manifest, and two profiles that set different values for the time zone. Each profile is associated with criteria to identify which clients should use which profile. When the client is booted after the installation completes, all additional configuration information not included in the system configuration profile will need to be configured manually.

Figure 7-6  AI Server Supporting One Architecture and Two Releases

Example 7-5  AI Server Supporting One Architecture and Two Releases

In this example, an AI server is configured to support only one client architecture with two versions of the Oracle Solaris OS. To create this environment:

1. Configure the AI server. See How to Set Up An AI Server.

2. Create an install service for the first OS. See Creating an Install Service.

3. Create an second install service for the second OS. See Creating an Install Service.

4. Define AI clients to associate the clients with the appropriate service. See Associating a Client With a Service.

In this example, the AI server includes two install services. The client definitions determine which client uses which service. When the client is booted after the installation completes, an interactive tool prompts for system configuration information because no system configuration profile was configured. Any additional configuration steps will need to be done manually. Profiles can be added to automate the system configuration steps.

Figure 7-7  AI Server Supporting One Architecture With Additional Configuration for Some Clients

Example 7-6  AI Server Supporting One Architecture with Additional Configuration for Some Clients

In this example, an AI server is configured to support only one client architecture but one set of clients needs additional configuration which can not be done in a manifest or profile. To create this environment, use the following steps:

1. Configure the AI server. See How to Set Up An AI Server.

2. Create an install service for the clients. See Creating an Install Service.

3. Create a first-boot script. See Chapter 13, Running a Custom Script During First Boot.

4. Create a package that includes the first-boot script and add the package to a package repository. See Creating an IPS Package for the Script and Service.

5. Create a second manifest which includes the first-boot package. SeeAssociating Client-Specific Installation Instructions With an Install Service.

6. Associate the second manifest with the install service. See Associating Client-Specific Installation Instructions With an Install Service.

In this example, the AI server includes one install service with two manifests. The second manifest includes instructions to install the first-boot service package, which runs the first-boot script once the client has rebooted. The second manifest is associated with criteria to identify which clients should use it. All other clients use the default manifest. When the client is booted after the installation completes, the first-boot script is run. Next, an interactive tool prompts for system configuration information because no system configuration profile was configured. Any additional configuration steps will need to be done manually. Profiles can be added to automate the system configuration steps.

Figure 7-8  AI Server Supporting Many Configuration Changes

Example 7-7  AI Server Supporting Many Configuration Changes

In this example, an AI server is configured to support one architecture with two configurations. The first configuration is very basic. The second configuration could be used to choose a different disk layout and to do additional configuration. Both configurations use the same system configuration profile to configure the time zone.To create this environment,:

1. Configure the AI server. See How to Set Up An AI Server.

2. Create an install service for the clients. See Creating an Install Service

3. Create a first-boot script. See Chapter 13, Running a Custom Script During First Boot.

4. Create a package that includes the first-boot script and add the package to a package repository. See Creating an IPS Package for the Script and Service.

5. Create a second manifest which includes the first-boot package and define the second disk layout. See Chapter 10, Provisioning the Client System.

6. Associate the second manifest with the install service. See Associating Client-Specific Installation Instructions With an Install Service.

7. Create a system configuration profile to set the time zone. See Chapter 11, Configuring the Client System.

8. Associate the system configuration profile with the install service. See Associating Client-Specific Configuration Instructions With Install Services.

In this example, the AI Server includes one install service with two manifests. The second manifest includes information about the second disk layout and instructions to install the first-boot service package which includes the first-boot script. The first-boot script is run once the client has rebooted. The second manifest is associated with criteria to identify the clients that should use it. All other clients use the default manifest. Clients using either manifest may be configured to also use the profile depending on the criteria associated with the profile. When the client is booted after the installation completes, the first-boot script is run. All additional configuration information not included in the system configuration profile will need to be configured manually.