Go to main content

Installing Oracle® Solaris 11.3 Systems

Exit Print View

Updated: April 2019
 
 

Managing Install Services

Use the installadm set-service command to reconfigure an existing install service. The examples in this section show how to set install service aliases, the default AI manifest, or the image path for an install service, as well as how to update an install service.

Setting Install Service Aliases

You can use install service aliases to minimize the amount of reconfiguration that needs to be done when a new service is created. For instance, the default-arch install services are aliases. When creating a service, you can create an alias by using the –t option of the create-service subcommand. The –t option to the set-service subcommand changes the specified service to be an alias of the another service. When you use the set-service subcommand, the specified service must already be an alias.

Manifests, profiles, and client criteria that were added to either the service or the alias remain the same after resetting the alias. The only change is which net image the specified service uses.

Manifests and profiles that were added to the service prior to setting the alias are revalidated when the alias is reset because the AI DTDs and SMF DTDs associated with the new installation image could be different. This validation is the same validation that is performed by the create-manifest and create-profile commands.

Example 50  Creating an Install Service Alias

This example creates the new install-sparc service as an alias to the existing solaris11_3-sparc install service.

# installadm create-service -t solaris11_3-sparc -n install-sparc
Example 51  Modifying an Install Service Alias

In this example, both the solaris11_3-i386 install service and the install-i386 install service alias must have been created previously. The following example sets the install-i386 install service as an alias to the solaris11_3-i386 install service.

# installadm set-service -t solaris11_3-i386 -n install-i386

Setting the Default AI Manifest for an Install Service

These examples show how to designate a particular manifest or a derived manifest script as the default manifest for both a new install service and an existing install service.

Example 52  Setting a Default AI Manifest When Creating an Install Service

This example sets the mem1 manifest as the default manifest for the new install-sparc service. All AI clients associated with this service that do not match other client criteria will use this manifest by default.

# installadm create-service -M /tmp/mem1 -n install-sparc
Example 53  Setting a Default AI Manifest by Modifying an Existing Install Service

This example sets the already registered mem1 manifest as the default manifest for the existing install-i386 service. All AI clients associated with this service that do not match other client criteria will use this manifest by default.

# installadm set-service -M mem1 -n install-i386

Setting the Image Path for an Install Service

These examples show how to define or reset the path to an installation image for a given service.

Example 54  Setting the Image Path for an New Installation Image

This example defines the path to the installation image for the solaris11_3-i386 service while creating the service and the net image.

# installadm set-service -d /export/ai-images/solaris11_3.i386 -n solaris11_3-i386
Example 55  Setting the Image Path for an Existing Installation Image

This example relocates the path to the installation image for the solaris11_3-i386 service.

# installadm set-service -d /export/ai-images/solaris11_3.i386 -n solaris11_3-i386

Updating an Existing Install Service

Use the update-service subcommand to update the image associated with an alias of a service that was created using an IPS AI net image package. A new service is created with the updated image, and the alias is changed to use the new service.

To use a different repository when updating a service, add the –p option to the update-service subcommand. If the –p option is not specified, the publisher used is the publisher that was used to create the image of the service for which svc-name is an alias.

If the –s option is not specified, the newest available version of the install-image/solaris-auto-install package is used from the publisher.

Example 56  Updating an Install Service

This example creates a new service, and changes the default-i386 alias to use this new service.

# installadm update-service -n default-i386
Example 57  Using a Different Repository When Updating an Install Service

This example shows how to identify the publisher associated with the solaris11_3-i386 service. First determine the image path for the service using the installadm list subcommand. Then you can use the image path to determine the publisher that is being used.

$ installadm list -v -n solaris11_3-i386
Service Name      Status Arch  Type Alias Aliases Clients Profiles Manifests
------------      ------ ----  ---- ----- ------- ------- -------- ---------
solaris11_3-i386  on     i386  iso  no    1       0       1        1

   Image Path ........ /export/auto_install/solaris11_3-i386
    ....

$ pkg -R /export/auto_install/solaris11_3-i386 publisher
PUBLISHER        TYPE     STATUS   URI
solaris          origin   online   http://pkg.oracle.com/solaris/release/

This example specifies using the publisher at example.com/solaris/mybuild when updating an install service.

# installadm update-service -n default-i386 -p solaris=http://example.com/solaris/mybuild
Example 58  Using a Different Net Image Package When Updating an Install Service

This example specifies a specific net image package.

# installadm update-service -n default-i386 -s FMRI