Go to main content

Automatically Installing Oracle® Solaris 11.4 Systems

Exit Print View

Updated: July 2019
 
 

Working With Install Services

An install service runs the automated installs of Oracle Solaris.

Creating and Configuring an Install Service

To create an install service, use the following command:

installadm create-service options [–y]

The –y option suppresses command prompts. Besides the –y option, the following are some other typical options:

  • –s full-path specifies the location of the IOS image to be used for the service.

  • –d full-path specifies the destination directory where the install service's files are stored.

  • –n service-name enables you to specify a preferred name for the service instead of using the default name.


Note -  You must create a separate service for each platform-OS version combination that describes your target clients.

If you create the service without using options, the command does the following:

  • Names the service with the convention solarisOS-version-architecture, based on the AI system's OS version and architecture, for example, solaris11_4-i386.

  • Installs the image in /export/auto_install/service-name directory.

  • If this is the first service created, also creates a default-architecture service.

The installadm list command displays the results:

$ installadm create-service -y
$ installadm list
Service Name     Status Arch Type Secure Alias Aliases Clients Profiles Manifests
------------     ------ ---- ---- ------ ----- ------- ------- -------- ---------
default-i386     on     i386 pkg  no     yes   0       0       0        1        
solaris11_4-i386 on     i386 pkg  no     no    1       0       0        1        

These examples show additional options for creating the install service.

Example 1  Creating a SPARC Install Service Using an ISO File

The –s option specifies a source for the image to be used for the service. The example assumes that the AI server is a SPARC system.

$ installadm create-service -s /var/tmp/images/sparc/sol-11_4-ai-sparc.iso
  0% : Service svc:/network/dns/multicast:default is not online. Installation services
       will not be advertised via multicast DNS.
...
100% : Created Service: 'solaris11_4-sparc'
...
Example 2  Creating an Install Service for a Different Architecture

This example uses the –a option to specify the architecture for the install service. Use this option if the service's clients and the AI server do not share the same architecture. You must also use the –n option to assign a name to the service. This option applies only if you are creating the service from an IPS package.

$ installadm create-service -n solaris11_4-i386 -a sparc -y
Example 3  x86: Creating a Service That Automatically Installs an X86 Client

By default, AI does not automatically start on x86 clients. The –b option enables you to override the default behavior.

$ installadm create-service -s /var/tmp/images/i386/sol-11_4-ai-x86.iso \
   -y -b install=true
Example 4  Setting the Image Path for an Install Service

The install image is normally located in /export/auto_install/service-name. The –d option sets the location of the image path elsewhere.

$ installadm create-service -d /export/ai-images -n solaris11_4-i386

About AI Manifests

When you create an install service for the first time, a default manifest file is also automatically created. All services use this manifest as a default file for installing Oracle Solaris on all valid clients. Valid clients are those whose architecture matches that for which the service was created. The setup is displayed as follows:

$ installadm list
Service Name Status Arch Type Secure Alias Aliases Clients Profiles Manifests
------------ ------ ---- ---- ------ ----- ------- ------- -------- ---------
ai-x86       on     i386 pkg  no     no    1       0       0        1        
default-i386 on     i386 pkg  no     yes   0       0       0        1

With this minimum setup, you can already start an automated install on clients by simply booting the clients from the network.

However, in more complicated scenarios with different installation requirements, you would need multiple manifests with their own instructions. For more information about creating various manifests with customized configuration instructions, see Chapter 2, Working With AI Manifests in Customizing Automated Installations With Manifests and Profiles.

About Configuration Profiles

Configuration profiles enable you to automate post-installation configurations which you would otherwise perform manually.

A typical tool for creating configuration profiles is the System Configuration Interactive (SCI) tool. For example, to create a profile in /var/tmp/, you would type:

$ sysconfig create-profile -o /var/tmp/

The command opens the SCI tool and displays screens where you set parameter values such as time zones, language, and so on. The configurations are saved in sc_profile.xml in the directory you specified.

The profile must be assigned to an install service in order to be used in an installation. For example:

$ installadm create-profile -p myprofile -f /var/tmp/sc_profile.xml -n ai-x86

The –p option creates the profile instance for the service ai-x86. When you run the installation, system configuration based on the profile becomes part of the automated operation.

If an install service does not have any associated configuration profile, then you would have to perform the post-installation configuration manually. When the client reboots after the completion of the installation, the SCI tool automatically opens. You specify values on different screens to configure the system.

For additional information about system configuration profiles, see Chapter 3, Working With System Configuration Profiles in Customizing Automated Installations With Manifests and Profiles.

Creating Client-Service Associations

Default install services are automatically associated with clients that match the platform for which the install services are created.

If clients need to use an install service other than the default service, then you must manually associate the server and those clients. The clients are identified by their MAC addresses, as shownin the following example:

$ installadm create-client -e aa:bb:cc:dd:ee -n ai-x86

A client can be associated with only one install service at one AI instance. If you run the command on the same client multiple times for different services, that client is associated only with the install service that was specified last.

To remove an association, delete the client:

$ installadm delete-client -e mac-address

Every creation of a client also modifies the DHCP configuration file of the DHCP server. Thus, the DHCP server recognizes and provides network connectivity to the client.

After you have properly created and configured the services, manifests, profiles, and server-client associations as needed, you can proceed with the installation on the clients. See Running AI on Clients by Using an AI Server.

The examples that follow show additional ways to associate clients to install services.

Example 5  Setting Up a SPARC Client With an Install Service

The following example associates the SPARC client with MAC address 00:14:4f:a7:65:70 with a service called sparc-service01.

# installadm create-client -n sparc-service01 -e 00:14:4f:a7:65:70
Example 6  x86: Associating an X86 Client With an Install Service and Redirecting Output to a Serial Line

In this example, the installation output is redirected to a serial console device.

$ installadm create-client -e c0ffeec0ffee -n solaris11_4-i386 -b console=ttya
Example 7  x86: Changing Boot Properties for an X86 Client

The –G option is specific to x86 clients to specify a custom GRUB2 menu to use when booting the client. In this example, the custom GRUB2 menu is /etc/netboot/grub.custom.cfg.

$ installadm create-client -e c0ffeec0ffee -n solaris11_4-i386 -G /etc/netboot/grub.custom.cfg

Note that the –b and –G options cannot be used at the same time.