Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 11 Express Automated Installer Guide Oracle Solaris 11 Express 11/10 |
1. Automated Installer Overview
2. Setting Up an AI Install Server
4. Specifying Installation Instructions
5. Configuring the Client System
8. Automated Installations That Boot From Media
A. Troubleshooting Automated Installations
B. Automated Installer Installation Administration Commands
C. Migrating From JumpStart to Automated Installer
Comparing JumpStart and Automated Installer
Converting JumpStart Rules to AI Criteria
Comparing Rules Keywords and Criteria Directives
Converting a JumpStart Profile to an AI Manifest
AI client criteria can be specified in the following two ways. The directives in the following table apply in both cases. See Chapter 3, Customizing Installations.
As -c options of the installadm add-manifest command or as -c or -a options of the installadm set-criteria command
In criteria files
The following table compares JumpStart rules keywords with AI criteria directives. AI uses these criteria to apply the correct AI manifest and SC (system configuration) manifest information to a particular client. JumpStart rules keywords that are not listed in this table do not have a comparable AI directive, or their functionality does not apply to AI.
Table C-2 Comparing JumpStart Rules File Keywords and AI Criteria Directives
|
This section shows some sample JumpStart rules converted to AI criteria. The add-manifest and set-criteria subcommands associate client criteria with specified AI manifests. See Associate Client-Specific Installation Instructions With Install Services.
In a JumpStart rules file, the first column contains rule keywords and rule values that identify client systems, the second column is the begin script, the third column is the profile, and the fourth column is the finish script.
The following sample JumpStart rules file identifies three groups of systems, and each group is assigned a different profile. In this example, no begin or finish scripts are specified for any of the three client groups. This sample rules file states the following rules:
Any SPARC systems with a memory size between 2048 MB and 4096 MB will be installed using specifications in the lx_prof profile.
Any x86 systems will be installed using specifications in the prog_prof profile.
Any systems not covered in the above rules will be installed using specifications in the generic_prof profile.
memsize 2048-4096 && model SUNW - lx_prof - karch i86pc - prog_prof - any - generic_prof -
This section shows AI commands that are comparable to the three rules from the previous JumpStart sample. In these examples, the lx_prof profile has been converted to the manifest_lx.xml AI manifest and the prog_prof profile has been converted to the manifest_prog.xml AI manifest. Clients that do not match any of these specified criteria use the default AI manifest.
In the following example, any SPARC systems with a memory size between 2048 MB and 4096 MB will be installed using specifications in the manifest_lx.xml AI manifest.
# installadm add-manifest -m ./manifest_lx.xml -n s11-sparc \ -c arch="sparc" -c mem="2048-4096"
You can also put the criteria in a file and reference the file. The following command is equivalent to the preceding command if the content of the criteria_lx.xml file is as shown.
# installadm add-manifest -m ./manifest_lx.xml -n s11-sparc \ -C ./criteria_lx.xml
<ai_criteria_manifest> <ai_criteria name="cpu"> <value>sparc</value> </ai_criteria> <ai_criteria name="mem"> <range> 2048 4096 </range> </ai_criteria> </ai_criteria_manifest>
In the following example, any x86 systems will be installed using specifications in the manifest_prog.xml AI manifest.
# installadm set-criteria -m ./manifest_prog.xml -n s11-x86 \ -c arch="i86pc"