The JumpStart Enterprise Toolkit (JET) is a set of utilities that simplifies the process of creating the profiles necessary to provision the Solaris OS. Through the N1 SPS browser interface, you can generate the profile keywords and values that are required to perform an automated JET installation of your target host.
If you prefer to not use JET, and create the profile values manually, you can create the Solaris Provisioning profile without using JET modules. See Creating Non-JET Solaris Provisioning Profiles.
Make sure the JET server exists and that the Solaris OS software is available to that server. For more information about creating the JET server, see Setting up the Solaris JET Server. For more information about creating the Solaris image, see How to Import a Solaris Image.
If you are provisioning the Solaris OS on x86 target hosts, you must create a custom JumpStart profile that deletes any existing partitions, and point to that profile in the profile_base_config variable. For instructions about how to create a JumpStart profile that deletes existing partitions with the fdisk keyword, see Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
In the Common Tasks section of the N1 SPS browser interface, select OS Provisioning.
On the OS Provisioning Common Tasks page, click Create Profile in the Solaris Images section.
On the Plans Details page, click Run.
Choose variables to use for this plan.
To use an existing variables set, select a name from the drop-down menu in the SolarisImage component row of the Plan Parameters table.
To create a new variables set, click Select from List in the SolarisImage component row of the Plan Parameters table.
Click Create Set.
Type a name for the variables set.
Type the Solaris main version number into the version variable.
Type the Solaris minor version number into the release variable.
Verify the remaining variables and change them, if needed.
The following table describes the additional variables and their default values.
Variable Name |
Description |
Default Value/Example |
---|---|---|
architecture |
Architecture of the physical system, for example, SPARC or x86 |
sparc (Default) |
installPath |
Solaris image name to attach |
Solaris:[version]_:[release]_:[architecture] For example: Solaris9_u7_sparc |
image_path |
Path to location where image file resides |
/export/osp_image/:[installPath] (Default) |
image_subnet_addr |
Subnet address of the image server |
:[target(/):sys.ipAddress] (Default) |
image_subnet_mask |
Subnet mask of the image server |
255.255.255.0 (Default) |
media_src |
Path to the image files. |
/cdrom/cdrom0/s0 (Example) |
ISO_files |
List of ISO files located in the directory specified in the media_src variable |
sol-10-GA-sparc-v1-iso sol-10-GA-sparc-v2-iso sol-10-GA-sparc-v3-iso sol-10-GA-sparc-v4-iso (Example) |
Save the variables set.
Select the variables set that you just saved from the drop-down menu in the SolarisImage component row of the Plan Parameters table.
On the Plan Details Run page, select the JET image server on which to create the profile.
The host name of the JET image server ends in -jet.
If needed, change the Profile Name.
If needed, change the Profile Description.
Update the list of the JET modules to use.
The JET product modules are located on the JET server in the directory /opt/SUNWjet/Products.
By default, the plan variable JET Modules Name(s) lists two JET modules to include in the Solaris profile component:
base_config – Installs and configures the Solaris OS. For information about base_config variables, see Basic Solaris OS Configuration Variables.
spsra – Installs and configures the N1 SPS Remote Agent (RA) on a Solaris system. For information about spsra variables, see Component Variables for Solaris Remote Agents.
base_config is the required JET module for basic Solaris installation. All other /opt/SUNWjet/Products modules are optional. Adding a module name to this list adds the module installation function and configuration variables to the newly created Solaris provisioning profile.
One of the /opt/SUNWjet/Products optional modules is the custom module. The custom module installs arbitrary lists of Solaris packages, patches, and files, and can run arbitrary collections of scripts. See Using the custom Module for further details. You can also write other JET modules. For information about creating JET modules, see Appendix F, Creating Additional JET Modules.
Click Run Plan (includes preflight).
(Optional) Change default profile values.
Navigate to the Solaris folder that contains the new Provision component.
For example, /com/sun/n1osp/autogen-biss1-jet/provision/.
Click the Solaris provisioning component name.
For example, Solaris10_0205_sparc.standard.
Edit default values.
For information about Solaris profile variables, see Appendix B, Solaris Profile Component Variables.
If you are provisioning the Solaris OS to an x86 target host, you must create a custom JumpStart profile that deletes all existing partitions on the target host. For the profile_base_config variable value, point to the location of this profile
To create a variable set for the SolarisImage component, type a command similar to the following example:
# cr_cli -cmd cdb.vs.add -comp NM:/com/sun/n1osp/untyped/SolarisImage \ -name "solaris10sparc" -u admin -p admin -vars "version=10;release=ga;architecture=sparc; \ image_path=/export/install/s10ga-sparc;image_subnet_addr=10.42.42.2; \ image_subnet_mask=255.255.255.0;media_src=" |
To run the plan, type a command similar to the following example:
# cr_cli -cmd pe.p.run -u admin -p admin -PID NM:/com/sun/n1osp/untyped/SolarisImage-create-profile -tar H:NM:biss1-jet -comp - -vs solaris10sparc -pto 30 -nto 10 -f /tmp/solaris-profile |
Note the default N1 SPS user value you specified with the -u option. This user must exist after the OS installation for the N1 SPS Remote Agent software to start on the target host.