h1. Solaris Unattended installation

h2. Installation Media

First you have to identify the release name of you Solaris install media. To do this check the disc label on your Solaris DVD. 

<pre>

SOL_10_811_SPARC = hw0811

</pre>

I recommend to create a structure to hold more than just one Solaris install media like the following:

<pre>

/Solaris

/Solaris/install

/Solaris/images

/Solaris/jumpstart

</pre>

h3. Linux:

Copy the contents of the Solaris 10 Install DVD to the local install directory.

h3. Sparc:

<pre>

cp -r /media/dvd /Solaris/install/Solaris_5.10_sparc_hw0811

</pre>

h3. i386:

<pre>

cp -r /media/dvd /Solaris/install/Solaris_5.10_i386_hw0811

</pre>

Create a link of Solaris_5.10_i386_hw0811 to Solaris_5.10_x86_64_hw0811.

<pre>

cd /Solaris/install

ln -s Solaris_5.10_i386_hw0811 Solaris_5.10_x86_64_hw0811

</pre>

Note that hw0811 is the release name that has to match your Solaris install media.

h3. Solaris:

Create a directory and run the following script from the Solaris 10 Installation DVD on a Solaris 8 / 10 machine:

<pre>

mkdir -p /Solaris/install/Solaris_5.10_sparc_hw0811

cd /cdrom/cdrom0/Solaris_10/Tools

./setup_install_server /Solaris/install/Solaris_5.10_sparc_hw0811

</pre>

A Solaris distribution should be declared in the same form as a Linux distribution. There should be an http based access URL, (the path variable,) so that the smart-proxy can

download the required components for the build. Currently this step has to be done manually. Simply copy the inetboot files to your tftp directory.

<pre>

cp /Solaris/install/Solaris_5.10_sparc_hw0811/Solaris_10/Tools/Boot/platform/sun4u/inetboot /var/lib/tftpboot/Solaris-5.10-hw0811-SUN4U-inetboot

</pre>

As the Solaris jumpstart process is performed via NFS rather than TFTP the distribution media must also be made available for

ReadOnly mounting on the clients.

h3. Linux:

<pre>

vi /etc/exports

"/Solaris" *(ro,async,no_root_squash,anonuid=0)

</pre>

h3. Solaris:

<pre>

share -F nfs -o ro,anon=0 /Solaris

echo "share -F nfs -o ro,anon=0 /Solaris" >> /etc/dfs/dfstab

</pre>

The fields describing this alternative access naming scheme are revealed on the Media page when a Solaris operating system is selected. The

Solaris build can proceed via a conventional package build, where the packages selected are the SUWNCreq minimal install, or a flash build. The flash archives are located under 

the distribution directory by default but can be located anywhere that can be accessed via NFS.

<pre>

Name: Solaris Install Media

Path: http://server/Solaris/install/Solaris_$major.$minor_$arch_$release

Media Path: server:/Solaris/install/Solaris_$major.$minor_$arch_$release

Config Path: server:/jumpstart

Image Path: server:/Solaris/images

</pre>

h2. Jumpstart files

The Solaris jumpstart process occurs in two phases; a diskless client is first booted and then in phase two, the host mounts its build media and configuration files from an NFS location and proceeds with the build. Foreman provides a skeleton configuration directory structure suitable for NFS mounting on the host. In this structure are files that are customised to forward configuration requests to the Foreman instance. This directory tree, located at .../foreman/extras/jumpstart, should be NFS shared to the subnet that contains any potential Solaris clients. Some customization of this directory tree may be required. See [[Solaris_jumpstart_directory]]

h3. Linux:

<pre>

cp -r /usr/share/foreman/extras/jumpstart /Solaris/jumpstart

vi /etc/exports

"/Solaris/jumpstart" *(ro,async,no_root_squash,anonuid=0)

</pre>

h3. Solaris:

<pre>

cp -r /usr/share/foreman/extras/jumpstart /Solaris/jumpstart

share -F nfs -o ro,anon=0 /jumpstart

echo "share -F nfs -o ro,anon=0 /jumpstart" >> /etc/dfs/dfstab

</pre>

h2. Edit Model

You need to setup a model for each Solaris Sparc host that you want to deploy.

<pre>

Name: Sun Ultra 10

Hardware Model: SUN4U

Vendor Class: Ultra-5_10

</pre>

h2. Model consolidation

When Foreman imports a host that has not been configured and built by Foreman it will attempt to determine the model of that machine by analyzing the facts that are associated with the host. This can often result in many badly named models all referring to what should be a single manufacturers model. A rake task has been provided that attempts to consolidate all these duplicate malformed names into a single sensible model together with the appropriate Solaris vendor class and Solaris hardware model. See [[models_consolidate|rake models::consolidate]]