Skip Navigation Links | |
Exit Print View | |
Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.1 Automated Installer Oracle Solaris 11.1 Information Library |
1. Comparing JumpStart and Automated Installer
Comparing Rules Keywords and Criteria Directives
Comparing Profile Keywords and AI Manifest Directives
Using js2ai To Convert JumpStart Rules and Profiles to AI Criteria and Manifests
How js2ai Converts JumpStart Device Specifications
How the System's Root Disk is Determined
How the any Device Is Translated
How the ZFS Root Pool is Determined
Example Rules and Profiles Conversion Using js2ai
Sample JumpStart Rules File and Profile Files
Using js2ai With the Rules File Option
Fix the mirrorfilesys.profile Errors
Fix the mirrorpool.profile Errors
Fix the rootdisk.profile Errors
Displaying More Profile Conversion Information
Validating an Output AI Manifest
3. Converting Configuration Files
4. Installing Oracle Solaris 10 Using JumpStart on an Oracle Solaris 11 Server
This chapter shows how to convert JumpStart rules and profile files to AI criteria files and AI manifests. Most of the conversion can be done with the js2ai utility. See the js2ai(1M) man page for more information about the js2ai utility.
AI manifests are XML files that specify system provisioning such as disk layout and software packages to install. See Chapter 10, Provisioning the Client System, in Installing Oracle Solaris 11.1 Systems and the ai_manifest(4) man page for more information about AI manifests.
AI uses client criteria to specify which client systems should use which AI manifest files to complete their installation. When an AI manifest is added to an AI install service, criteria can be specified on the command line or in a file. This chapter shows how to use the js2ai tool to convert JumpStart rules files to AI criteria files. See Chapter 9, Customizing Installations, in Installing Oracle Solaris 11.1 Systems for more information about specifying AI client criteria.