Solaris Unattended installation » History » Revision 9
Revision 8 (Oliver Weinmann, 12/28/2011 05:11 AM) → Revision 9/29 (Oliver Weinmann, 12/28/2011 05:13 AM)
h1. Solaris Unattended installation h2. Installation Media Installation Media can reside on a non Solaris host. Only the To setup of the installation media has to be carried out on a Solaris host. Create 10 Installation Media, create a directory and run the following script from the Solaris 10 Installation DVD on a Solaris 8 / 10 machine: <pre> mkdir -p /Solaris cd /cdrom/cdrom0/Solaris_10/Tools ./setup_install_server /Solaris </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. Example: <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. 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. Example: <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/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]] Examples: h3. Linux: <pre> vi /etc/exports "/usr/share/foreman/extra/jumpstart" *(ro,async,no_root_squash,anonuid=0) </pre> h3. Solaris: <pre> share -F nfs -o ro,anon=0 /jumpstart </pre> h2. Edit Model You need to setup a model for each Solaris Sparc host that you want to deploy. Example: <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]]