Migrating From JumpStart to AI

The Automated Installer (AI) performs automated installations of networked systems. This installation method replaces the JumpStart installation method that is used in Oracle Solaris 10. For a detailed comparison of the two installation methods, see Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.1 Automated Installer.

JumpStart to AI Migration Tasks

The js2ai utility can be used to assist you in migrating from JumpStart to AI. The utility is used to convert Oracle Solaris 10 JumpStart rules, profiles, and sysidcfg files to an AI manifest and system configuration files. See the js2ai(1M) man page for more details.

To use the js2ai utility, install the software package:

# pkg install install/js2ai

You can use the js2ai utility to perform most of the following tasks:

• Replace JumpStart rules and profile files with AI criteria files and AI manifests

  AI uses client criteria to specify which AI manifest files each client system should use to complete an installation. When adding an AI manifest to an AI install service, the criteria can be specified on the command line or in a file. AI uses client criteria to specify which client systems should use which AI manifest files to complete their installation. Use the js2ai utility with the -r option to convert both JumpStart rules and their associated profiles to AI criteria and manifests. Initially, you can use the -S option to skip validation:

  # /user/sbin/js2ai -rS [-d sysidcfg-dir] [-D destination-dir]

  See Using js2ai To Convert JumpStart Rules and Profiles to AI Criteria and Manifests in Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.1 Automated Installer.

• Convert JumpStart files to an AI configuration files

  AI system configuration profiles are SMF XML profile files that specify system configuration. Use the js2ai utility with the -s option to convert any sysidcfg files that are associated with this JumpStart configuration to system configuration profile files. Initially, use the -S option to skip validation:

  # /user/sbin/js2ai -sS [-d sysidcfg-dir] [-D destination-dir]

  See Using js2ai to Convert sysidcfg Files to System Configuration Profiles in Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.1 Automated Installer.

• Set up an install server

  You can use the same Oracle Solaris 11 server as both a JumpStart install server and an AI install server. However, JumpStart can only be used to install Oracle Solaris 10, not Oracle Solaris 11. See Chapter 4, Installing Oracle Solaris 10 Using JumpStart on an Oracle Solaris 11 Server, in Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.1 Automated Installer.

  ---

  Note - Customers who have a valid My Oracle Support contract can now set up an Oracle Solaris 10 1/13 system as an AI install server by installing extra software packages. This offering enables an installation of the Oracle Solaris 11 11/11 release only. For more information, go to https://support.oracle.com/.

  ---

• Dynamically derive an AI provisioning manifest

  As an alternative to creating custom AI manifests, you can write a script that dynamically creates an AI manifest for each client at client installation time. This manifest is called a derived manifest because it is based on attributes of each client that is discovered at installation time. JumpStart begin scripts provide the ability to dynamically manipulate installation parameters that are passed to the installer. See Creating an AI Manifest at Client Installation Time in Installing Oracle Solaris 11.1 Systems

• Access a software package repository for AI installations

  After accessing the package repository (http://pkg.oracle.com/solaris/release) for AI installations, make a local copy of the package repository. See Chapter 2, Copying IPS Package Repositories, in Copying and Creating Oracle Solaris 11.1 Package Repositories.

• Provide system configuration instructions

  You can use system configuration profiles to specify the configuration for the client system as a set of configuration parameters, in the form of a Service Management Facility (SMF ) profile. This profile is applied during the first boot of the system after an AI installation. If you do not provide a system configuration profile for a particular client, the interactive configuration tool opens on that client during the installation. You can create a system configuration profile manually or by running the interactive configuration tool and saving the output to a file. For example, the following command creates a valid profile in sc.xml from responses that you provide interactively:

  # sysconfig create-profile -o sc.xml

  See Chapter 11, Configuring the Client System, in Installing Oracle Solaris 11.1 Systems.

• Create an SMF service that runs on first boot and executes a user-defined script

  For any additional installation or configuration that cannot be accomplished by using an AI manifest or a system configuration profile, you can create a script that is executed at first boot by a run-once SMF service. See Chapter 13, Running a Custom Script During First Boot, in Installing Oracle Solaris 11.1 Systems.