Creating an AI Install Service

An install server can have more than one install service. Create a
separate install service for each client hardware architecture and each different version of the
Oracle Solaris 11 OS that you want to install.

Use the installadm create-service command to create an AI install service.

When an AI install service is created, the AI SMF service, system/install/server,
is enabled if it was not already enabled. The install service image is
mounted at /etc/netboot/svcname. For SPARC install services, the wanboot.conf file is at the root
of the install service image. For x86 install services, the GRUB menu
is at the root of the install service image.

When the first install service for a particular architecture is created on an
install server, an alias of that service, default-i386 or default-sparc, is automatically
created. This default service is a complete service, with its own manifests and
profiles, but this default service shares a net image with the explicitly created
service. This default service is used for all installations on clients of that
architecture that were not explicitly associated with a different install service with the
create-client subcommand.

To change which service the default-arch service aliases, set the aliasof property using
the set-service subcommand. Manifests and profiles that were added to either service remain
the same after resetting an alias. The only change is which net
image the service uses. See Modifying Install Service Properties for more information about setting the aliasof
property. To update the net image of the service for which the default-arch
service is an alias, use the update-service subcommand as shown in Updating an Install Service.

If a default-arch alias is changed to a new install service and a
local ISC DHCP configuration is found, this default alias boot file is set
as the default DHCP server-wide boot file for that architecture if the value
of the all_services/manage_dhcp property is true. See Automatically Updating the ISC DHCP Configuration for more information about
the all_services/manage_dhcp property.

The installadm create-service command also provides a net image on a web server running
on port 5555. For example, the web server address might be http://10.80.238.5:5555/solaris11_1-i386. See Configuring the Web Server Host Port
to use a different port.

The installadm create-service command does not require any arguments or options. The two options
described below are commonly used. For information about all options, see Creating an Install Service or
the installadm(1M) man page.

installadm create-service [-s source] [-y]

-ssource

The source argument specifies the data source for the net image. The value of source can be one of the following:

The FMRI identifier of the IPS AI net image package, which is install-image/solaris-auto-install in the Oracle Solaris 11.1 release.

The full path name of an AI ISO image file.

If you do not specify source, the newest available version of the install-image/solaris-auto-install package is used. The package is retrieved from the publisher specified by the -p option or from the first publisher in the install server's publisher preference list that provides an instance of the package.

To install a different version of the package, or to install the package from a different publisher, specify the version or publisher in the FMRI. For example, specify pkg://publisher/install-image/solaris-auto-install or pkg://publisher/install-image/solaris-auto-install@version. Use the -p option to specify the particular publisher origin.

-y

If you do not specify the -d option, specify the -y option to suppress the prompt to confirm the use of the automatically generated image path.

Creating an Install Service Without Setting Up DHCP

In the examples in this section, DHCP is already set up on
a different server or will be set up later. If the create-service command does
not detect that ISC DHCP is running on this server, the output
of the command displays instructions for configuring DHCP. In these examples, the create-service
command output provides the boot file required for DHCP configuration.

Creating a SPARC Install Service Using an ISO File

This example creates an AI install service for SPARC clients using a net
image from an ISO file.

The following operations are performed as a result of executing this installadm create-service
command:

The install service is automatically named solaris11_1-sparc.

The default install service net image directory, /export/auto_install/solaris11_1-sparc, is created. Because the -y option is specified, the prompt to confirm that this default destination is acceptable is suppressed.

The ISO file, /var/tmp/images/sparc/sol-11_1-ai-sparc.iso, is unpacked into the net image location, /export/auto_install/solaris11_1-sparc.

The wanboot.conf file for this service is generated at /export/auto_install/solaris11_1-sparc/wanboot.conf.

The AI SMF service, system/install/server, is refreshed to mount /export/auto_install/solaris11_1-sparc as /etc/netboot/solaris11_1-sparc.

Because this is the first SPARC install service created on this install server, the default-sparc service alias is automatically created. The image from solaris11_1-sparc is used by the alias, so /export/auto_install/solaris11_1-sparc is also mounted as /etc/netboot/default-sparc.

The configuration file /etc/netboot/wanboot.conf is symbolically linked to /etc/netboot/default-sparc/wanboot.conf. The configuration file /etc/netboot/system.conf is symbolically linked to /etc/netboot/default-sparc/system.conf.

The boot file required for DHCP configuration, http://10.80.238.5:5555/cgi-bin/wanboot-cgi, is provided.

If a local ISC DHCP server is already configured, the boot file of the new default-sparc alias is set as the default boot file for all SPARC clients. This assignment occurs regardless of whether the -i and -c options are used.

Creating an x86 Install Service Using an IPS Package

This example creates an AI install service for x86 clients using a
net image from an IPS package. This command also illustrates default behavior when options
are not specified. If this install server is a SPARC system, you must
supply the -a i386 option to specify that you want to create an x86
install service.

In addition to the boot file required for DHCP configuration, this command output
also provides the boot server IP required for DHCP configuration.

The following operations are performed as a result of executing this installadm create-service
command:

The install service is automatically named solaris11_1-i386.

Because no net image source option is specified, the newest version of the install-image/solaris-auto-install package is retrieved from the first publisher in the install server publisher list that provides this package.

The default install service net image directory, /export/auto_install/solaris11_1-i386, is created. Because the -y option is specified, the prompt to confirm that this default destination is acceptable is suppressed.

The install-image/solaris-auto-install package is installed into the net image location, /export/auto_install/solaris11_1-i386.

By default, the variant of the install-image/solaris-auto-install package that is installed matches the architecture of the AI install server. In this example, the install server is an x86 system. If you wanted to create a SPARC install service on this server, you would need to use the -a option. See Creating an Install Service for information about the -a option.

The GRUB menu is mounted at /etc/netboot/solaris11_1-i386/grub.cfg.

The AI SMF service, system/install/server, is refreshed to mount /export/auto_install/solaris11_1-i386 as /etc/netboot/solaris11_1-i386.

Because this is the first x86 install service created on this install server, the default-i386 service alias is automatically created. The image from solaris11_1-i386 is used by the alias, so /export/auto_install/solaris11_1-i386 is also mounted as /etc/netboot/default-i386.

The boot server IP required for DHCP configuration is provided. The boot files required for DHCP configuration, default-i386/boot/grub/pxegrub2 and default-i386/boot/grub/grub2netx64.efi, are also provided.

If a local ISC DHCP server is already configured, the boot files of the new default-i386 alias are set as the default boot files for all x86 clients. This assignment occurs regardless of whether the -i and -c options are used.

Creating an Install Service Including Local DHCP Setup

You can use the installadm create-service command to set up a DHCP server on
this AI install server. Make sure the value of the all_services/manage_dhcp property is
true. See Automatically Updating the ISC DHCP Configuration for more information about the all_services/manage_dhcp property.

The following example creates an install service for x86 clients where the network
consists of a single subnet and the install server also acts as the
DHCP server for the network. This install service serves twenty IP addresses (-c),
starting from 10.80.239.150 (-i). If a DHCP server is not yet configured, an
ISC DHCP server is configured. If an ISC DHCP server is already configured,
that DHCP server is updated.

Note that when -i and -c arguments are provided and DHCP is configured,
no binding exists between the install service being created and the IP range.
When -i and -c are passed, the IP range is set up, a
new DHCP server is created if needed, and that DHCP server remains up
and running for all install services and all clients to use. The network
information provided to the DHCP server has no specific bearing on the service
being created.

If the IP range requested is not on a subnet that the
install server is directly connected to and the install server is multihomed, use
the -B option to provide the address of the boot file server
(usually an IP address on this system). This option should only be necessary
when multiple IP addresses are configured on the install server and DHCP relays
are employed. In other configurations, the software can determine this automatically.

The following operations are performed as a result of executing this installadm create-service
command:

The install service is automatically named solaris11_1-i386.

The default install service net image directory, /export/auto_install/solaris11_1-i386, is created. Because the -y option is specified, the prompt to confirm that this default destination is acceptable is suppressed.

The ISO file, /var/tmp/images/i386/sol-11_1-ai-x86.iso, is unpacked into the net image location, /export/auto_install/solaris11_1-i386.

The GRUB menu is mounted at /etc/netboot/solaris11_1-i386/grub.cfg.

The AI SMF service, system/install/server, is refreshed to mount /export/auto_install/solaris11_1-i386 as /etc/netboot/solaris11_1-i386.

Because this is the first x86 install service created on this install server, the default-i386 service alias is automatically created. The image from solaris11_1-i386 is used by the alias, so /export/auto_install/solaris11_1-i386 is also mounted as /etc/netboot/default-i386.

A DHCP service is created if necessary, and IP addresses 10.80.239.150 through 10.80.239.169 are provisioned. If DHCP service is already set up on this server, the -i and -c options update the DHCP server with new IP addresses for this service. The svc:/network/dhcp/server service is online.

The boot files default-i386/boot/grub/pxegrub2 and default-i386/boot/grub/grub2netx64.efi are added to the local DHCP configuration as the default boot files for PXE clients.

The following sections show how installadm might add information to the DHCP configuration
file for an ISC DHCP configuration. For more information about configuring ISC DHCP,
see the Related Information.

The following example shows how installadm might add the IP addresses specified using
the -i and -c options to the /etc/inet/dhcpd4.conf file for an ISC DHCP
configuration for the Oracle Solaris 11.1 i386 install service created above:

The following example shows how installadm might set the default PXE boot files
in the /etc/inet/dhcpd4.conf file for an ISC DHCP configuration for the default-i386 Oracle
Solaris 11.1 i386 install service created above: