Go to main content

Automatically Installing Oracle® Solaris 11.4 Systems

Exit Print View

Updated: July 2019
 
 

Examples of Automated Install Setups

The following figures illustrate different AI server configurations. The configuration you adopt depends on your environment.

Figure 2  One AI Service Supporting One Architecture and One OS

image:Shows one install service which includes a default manifest.

This configuration is the simplest to create and assumes an environment where clients share the same architecture and OS version. Clients are booted from the network which starts the installation. After each each system is rebooted, an interactive tool prompts you for system configuration information.

Figure 3  Two Install Services Supporting Two Architectures

image:Shows two install services with their respective default manifests.

AI requires that each architecture must have its own install service. As you create the install services, their corresponding default manifests are also created. System configuration is performed manually.

This setup also applies in a situation where you have two OS versions to install on two groups of clients, even though they share the same architecture.

Figure 4  AI Service Supporting Two Types of Installation With Different Installation Parameters

image:Shows one install service with two manifests.

In this scenario, some clients require an installation that is different from the rest in the group. Thus, a separate manifest with special instructions exists to cater to these clients. The rest would use the default manifest. System configuration is performed manually.

Figure 5  AI Service Supporting Specific Clients That Use a Script

image:Shows one install service with two manifests. One manifest points to a first-boot script.

This example is a slight variation of Figure 4 in the previous example. The clients that use Manifest 2 also use a script that configures the system after it reboots at the end of the installation. For the other clients that use the default manifest, system configuration is performed manually.

Figure 6  One AI Service Supporting Clients With Different Post-Install Configurations

image:Shows one install service with a default manifest and two profiles.

In this scenario, the OS installation is the same for all clients. However, one group requires a different system configuration from the rest, such as the time zone, types of network configuration, and so on. Thus, separate system configuration profiles are created for each group that automatically runs after the clients are rebooted at the end of the installation.

Figure 7  AI Server Supporting Many Configuration Settings

image:Shows one install service with two manifests, each sharing one profile, but one manifest also using a first-boot script.

This example shows how you can set up AI depending on the complexities of the needs of the clients. You can combine services, manifests, profiles, and boot scripts that will address the specific requirements of different clients in the data center. In scenarios such as this, client criteria must be well defined so that the correct manifest and profile definitions or boot scripts are applied to the appropriate clients.