Project

General

Profile

Solaris Unattended installation » History » Version 10

Oliver Weinmann, 12/28/2011 06:46 AM

1 1 Romain Vrignaud
h1. Solaris Unattended installation
2
3 4 Oliver Weinmann
h2. Installation Media
4 1 Romain Vrignaud
5 10 Oliver Weinmann
h3. Linux:
6
7
Copy the contents of the Solaris 10 Install DVD to a local directory.
8
9
Example:
10
11
<pre>
12
cp -r /media/dvd /Solaris
13
</pre>
14
15
h3. Solaris:
16 7 Oliver Weinmann
17 9 Oliver Weinmann
Create a directory and run the following script from the Solaris 10 Installation DVD on a Solaris 8 / 10 machine:
18 4 Oliver Weinmann
19
<pre>
20
mkdir -p /Solaris
21
cd /cdrom/cdrom0/Solaris_10/Tools
22
./setup_install_server /Solaris
23
</pre>
24
25 3 Oliver Weinmann
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
26
download the required components for the build. Currently this step has to be done manually. Simply copy the inetboot files to your tftp directory.
27
28
Example:
29 1 Romain Vrignaud
30 3 Oliver Weinmann
<pre>
31 4 Oliver Weinmann
cp /Solaris/install/Solaris_5.10_sparc_hw0811/Solaris_10/Tools/Boot/platform/sun4u/inetboot /var/lib/tftpboot/Solaris-5.10-hw0811-SUN4U-inetboot
32 3 Oliver Weinmann
</pre>
33
34
As the Solaris jumpstart process is performed via NFS rather than TFTP the distribution media must also be made available for
35 1 Romain Vrignaud
ReadOnly mounting on the clients. The fields describing this alternative access naming scheme are revealed on the Media page when a Solaris operating system is selected. The
36
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 
37
the distribution directory by default but can be located anywhere that can be accessed via NFS.
38
39 2 Oliver Weinmann
Example:
40
41
<pre>
42
Name: Solaris Install Media
43
44
Path: http://server/Solaris/install/Solaris_$major.$minor_$arch_$release
45
Media Path: server:/Solaris/install/Solaris_$major.$minor_$arch_$release
46 5 Oliver Weinmann
Config Path: server:/jumpstart
47 2 Oliver Weinmann
Image Path: server:/Solaris/images
48
</pre>
49
50 5 Oliver Weinmann
h2. Jumpstart files
51 1 Romain Vrignaud
52 5 Oliver Weinmann
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/extra/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]]
53 7 Oliver Weinmann
54
Examples:
55
56
h3. Linux:
57
58
<pre>
59
vi /etc/exports
60
"/usr/share/foreman/extra/jumpstart" *(ro,async,no_root_squash,anonuid=0)
61
</pre>
62
63 1 Romain Vrignaud
h3. Solaris:
64 8 Oliver Weinmann
<pre>
65 7 Oliver Weinmann
share -F nfs -o ro,anon=0 /jumpstart
66
</pre>
67 1 Romain Vrignaud
68 5 Oliver Weinmann
h2. Edit Model
69
70
You need to setup a model for each Solaris Sparc host that you want to deploy.
71
72
Example:
73
74
<pre>
75
Name: Sun Ultra 10
76
Hardware Model: SUN4U
77
Vendor Class: Ultra-5_10
78
</pre>
79
80 1 Romain Vrignaud
h2. Model consolidation
81
82 5 Oliver Weinmann
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]]