Converting a JumpStart Profile to an AI Manifest

The following table compares JumpStart profile keywords with AI manifest directives. AI uses XML manifest files to define the client installation. See Chapter 4, Specifying Installation Instructions. JumpStart profile keywords that are not listed do not have a comparable AI directive, or their functionality does not apply to AI.

Table C-3 Comparing JumpStart Profile File Keywords and AI Manifest Directives

JumpStart Rules File Keyword	AI Manifest Directives
boot_device c0t0d0s0 update	<target> <target_device> <disk> <disk_name name="c0t0d0" name_type="ctd"/> <slice name="0" is_root="true" force="true"/> </disk> </target_device> </target> The second token value (`update` for SPARC systems and `preserve` for x86 systems) for this keyword is not supported in AI. In AI, the EEPROM on SPARC systems is always updated to the specified target device, so that the installed system automatically boots from that device. On x86 systems, the firmware is never updated.
bootenv	A boot environment is automatically created on installation of the Oracle Solaris OS.
cluster SUNWCXall	The Oracle Solaris 11 ExpressOS uses `pkg`(5) group packages. Group packages are specified just as any other package is specified in the manifest. The default AI manifest includes the packages needed for a standard Oracle Solaris 11 Express installation. You can customize this list of packages. <software_data action="install" type="IPS"> <name>pkg:/entire</name> <name>pkg:/babel_install</name> </software_data>
fdisk c0t3d0 solaris maxfree	<target> <target_device> <disk> <disk_name name="c0t3d0" name_type="ctd"/> <partition name="1" part_type="SOLARIS"> </disk> </target_device> </target> See Configuring Partitioning on an x86 Client.
filesys	In JumpStart, this `filesys` keyword creates the VTOC slice and the UFS file system on that slice. AI creates ZFS file systems, not UFS file systems. To create VTOC slices in AI, use the `<slice>` element. See Configuring Slices on a Disk.
geo	Geographic regions for language support are specified through `pkg`(5) group packages. Group packages are specified just like any other package is specified in the manifest. See the JumpStart `cluster` keyword above for more information.
locale	Locale support is specified through `pkg`(5) group packages. Group packages are specified just like any other package in the manifest. See the JumpStart `cluster` keyword above for more information.
package SUNWmysql51 add nfs golden:/packages/Solaris_10	<software name="IPS"> <software_data action="install" type="IPS"> <name>pkg:/entire</name> <name>pkg:/babel_install</name> <name>pkg:/database/mysql-51</name> </software_data> </software>
package SUNWmysql delete	<software_data action="uninstall" type="IPS"> <name>pkg:/database/mysql-4</name> </software_data>
partitioning default partitioning existing partitioning explicit	If the `target_device` directives are omitted from the AI manifest, a default partitioning is used. See Configuring Partitioning on an x86 Client.
usedisk	<target> <target_device> <disk> <disk_keyword key="boot_disk"/> </disk> </target_device> </target>

Converting Profile Files to AI Manifests

This section shows some sample JumpStart profile specifications converted to AI manifest directives. See Chapter 4, Specifying Installation Instructions for more information about AI manifest directives.

Sample JumpStart Profile File

In a JumpStart profile, the first column contains profile keywords, and the second column contains profile values.

The following sample JumpStart profile specifies:

Systems will receive an initial installation.
Systems will be set up as standalone systems.
On each system, a Solaris fdisk partition is created on the largest contiguous free space on the c0t0d0 disk.
The Entire Distribution software group, SUNWCall, is installed on the system.
The StarOffice suite of tools is installed on the system.
The Evolution email and calendar utilities are installed on the system.

install_type initial_install
system_type standalone
fdisk c0t0d0 solaris maxfree
cluster SUNWCall
cluster SUNWCstaroffice
cluster SUNWCevo

Equivalent AI Manifest Directives

The following excerpts from AI manifests show how you could convert the previous JumpStart profile into directives in AI manifests.

The following example directs the installer to install the Oracle Solaris 11 Express release on the c0t0d0 disk and create a SOLARIS partition on the biggest chunk of contiguous free space. See Configuring Partitioning on an x86 Client. Next the example specifies a source of packages to install and installs the two mandatory group packages. See Specifying Packages to Install for an explanation for why these same group packages must be uninstalled. Finally, this example installs OpenOffice and Evolution.

<?xml version="1.0"?>
<!DOCTYPE auto_install SYSTEM "file:///usr/share/auto_install/ai.dtd">
<auto_install>
  <ai_instance name="sample_ai_manifest" auto_reboot="true">
    <target>
      <target_device>
        <disk>
          <disk_name name="c0t0d0" name_type="ctd"/>
          <partition name="1" part_type="SOLARIS">
        </disk>
      </target_device>
    </target>
    <software name="ips">
      <source>
        <publisher name="solaris">
          <origin name="http://pkg.oracle.com/solaris/release"/>
        </publisher>
      </source>
      <software_data type="IPS">
        <name>pkg:/entire</name>
        <name>pkg:/babel_install</name>
      </software_data>
      <software_data action="uninstall" type="IPS">
        <name>pkg:/babel_install</name>
        <name>pkg:/slim_install</name>
      </software_data>
      <software_data type="IPS">
        <name>pkg:/office/openoffice</name>
        <name>pkg:/mail/evolution</name>
      </software_data>
    </software>
  </ai_instance>
</auto_install>

Skip Navigation Links
Exit Print View
	Oracle Solaris 11 Express Automated Installer Guide Oracle Solaris 11 Express 11/10