Go to main content

Transitioning From Oracle® Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer

Exit Print View

Updated: April 2020
 
 

Comparing Profile Keywords and AI Manifest Elements

The following table compares JumpStart profile keywords with AI manifest elements. AI uses XML manifest files to define the client installation. For more information about AI manifests, see Chapter 10, Defining AI Client Installation Parameters in Installing Oracle Solaris 11.3 Systems and see the ai_manifest(4) man page.

To specify values that are not known until the client installation process has started, such as devices specified using the any keyword, consider using a derived manifests script. You can use a derived manifests script to specify swap size based on disk size or to specify mirroring based on available disks, for example. For information about derived manifests scripts, see Creating an AI Manifest at Client Installation Time in Installing Oracle Solaris 11.3 Systems.

Table 3  Comparing JumpStart Profile Keywords and AI Manifest Elements
JumpStart Profile Keyword
AI Manifest Elements
archive_location
Unsupported. AI does not install from flash archives.
backup_media
Unsupported. The backup_media keyword is used only with the upgrade option of install_type. AI does not support the upgrade install type; AI supports only initial install.
boot_device device
Example:
boot_device c1t0d0
Example:
<target>
  <disk whole_disk="true">
    <disk_name name="c1t0d0" name_type="ctd"/>
  </disk>
  <logical nodump="true" noswap="false"/>
</target>
boot_device device eeprom
Example:
boot_device c0t0d0s0 update
The value for the eeprom keyword (update for SPARC systems and preserve for x86 systems) 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
Unsupported. AI creates a boot environment and installs the Oracle Solaris 11 OS into that boot environment.
client_arch
Unsupported. The client architecture to be installed is defined by the AI install service, not in the AI manifest.
client_root
Unsupported. You can specify the type, vendor, and size of the target disk. You cannot specify the amount of root space on the target disk. See the ai_manifest(4) man page.
client_swap
Unsupported. By default, AI creates a swap volume in the root pool. You can specify a swap slice. See the ai_manifest(4) man page.
cluster cluster-name
Unsupported. See Converting Software Packages for information about how to handle cluster and package specifications.
The Oracle Solaris 11 OS uses group packages as defined in the pkg(5) man page. 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 installation. You can customize this list of packages.
cluster cluster-name delete
Unsupported. The delete switch is used only with the upgrade option of install_type. AI does not support the upgrade install type; AI supports only initial install.
dontuse
Unsupported.
fdisk disk-name type size
Example:
fdisk c0t3d0 solaris all
Example:
<target>
  <disk>
    <disk_name name="c0t3d0" name_type="ctd"/>
    <partition action="create" name="1" part_type="191"/>
  </disk>
  <logical nodump="true" noswap="false"/>
</target>
For a full list of the disk and partition attributes supported by AI, see the ai_manifest(4) man page.
Translation by js2ai:
For js2ai translation, the value of disk-name must be a device. A device of all is not supported. The fdisk type must be solaris. A size of 0 or delete is not supported. If partitioning is default and the rootdisk has not been set, js2ai sets the first fdisk solaris partition encountered as the root disk.
filesys
UFS file systems are not supported. AI installs ZFS file systems.
Translation by js2ai:

  • If there is no other way to determine the device to be used for root, the device from the filesys line with the / mount point is used for the root pool.

  • The local and mirrored file systems are supported when the mount point specified is / or swap.

  • If the mount point is not / or swap, the line is logged and then ignored. JumpStart fsoptions are not supported.

  • No validation of the size is performed. You might need to adjust the size specified in the resulting AI manifest to achieve a successful installation with this manifest.
Example:
filesys c1t0d0s0 10000 /
The following partial AI manifest is for x86 platforms.
<target>
  <disk>
    <disk_name name="c1t0d0" name_type="ctd"/>
    <partition action="create" name="1" part_type="191">
      <slice action="create" force="true"
       in_vdev="rpool_vdev" in_zpool="rpool" name="0">
        <size val="10000mb"/>
      </slice>
    </partition>
  </disk>
  <logical nodump="true" noswap="false">
    <zpool is_root="true" name="rpool">
      <vdev name="rpool_vdev" redundancy="none"/>
    </zpool>
  </logical>
</target>
Translation by js2ai:
The js2ai command supports translations only of the root file system (/) and swap.
Example:
filesys mirror:rpool c6t0d0s0 c6t1d0s0 60048 /
The following partial AI manifest is for x86 platforms. For SPARC platforms, no partition element is specified.
<target>
  <disk>
    <disk_name name="c6t1d0" name_type="ctd"/>
    <partition action="create" name="1" part_type="191">
      <slice action="create" force="true"
       in_vdev="rpool_vdev" in_zpool="rpool" name="0">
        <size val="60048mb"/>
      </slice>
    </partition>
  </disk>
  <disk>
    <disk_name name="c6t0d0" name_type="ctd"/>
    <partition action="create" name="1" part_type="191">
      <slice action="create" force="true"
       in_vdev="rpool_vdev" in_zpool="rpool" name="0">
        <size val="60048mb"/>
      </slice>
    </partition>
  </disk>
  <logical nodump="true" noswap="false">
    <zpool is_root="true" name="rpool">
      <vdev name="rpool_vdev" redundancy="mirror"/>
    </zpool>
  </logical>
</target>
filesys server:path
Unsupported. AI does not support remote file systems.
forced_deployment
Unsupported. AI does not install from flash archives.
geo
Unsupported. In AI, geographic regions for language support are specified in the system configuration profile. See Chapter 11, Defining AI Client System Configuration Parameters in Installing Oracle Solaris 11.3 Systems.
install_type
AI supports only initial_install.
layout_constraint
Unsupported. AI supports only initial_install.
local_customization
Unsupported. AI does not install from flash archives.
locale
Unsupported. In AI, locale support is specified in the system configuration profile. See Chapter 11, Defining AI Client System Configuration Parameters in Installing Oracle Solaris 11.3 Systems.
metadb
Unsupported.
no_content_check
Unsupported. AI does not install from flash archives.
no_master_check
Unsupported. AI does not install from flash archives.
num_clients
Unsupported.
package package
Example:
package SUNWpampkcs11 add
Example:
<software type="IPS">
  <software_data action="install">
    <name>pkg:/SUNWpampkcs11</name>
  </software_data>
</software>
See Converting Software Packages for information about how to verify the package name is valid.
package package add nfs server:path
In an AI manifest, all software is retrieved from IPS (Image Packaging System) package repositories. IPS repository locations can be a URL or file name. You can specify multiple IPS repositories as software sources. See the ai_manifest(4) man page for information about how to specify publishers.
Translation by js2ai:
The js2ai command ignores the retrieval-type location argument.
package package delete
Example:
<software type="IPS">
  <software_data action="uninstall">
    <name>pkg:/SUNWpampkcs11</name>
  </software_data>
</software>
Because AI only supports initial installations, you should not need to use an AI manifest to delete packages.
partitioning default
partitioning explicit
If no target installation device is specified, AI determines a default installation device and a default partitioning. To specify custom partitioning, see the ai_manifest(4) man page.
Translation by js2ai:
For js2ai, partitioning must be default or explicit. For explicit, only swap and / are supported
partitioning existing
Unsupported. For js2ai, partitioning must be default or explicit.
patch
Unsupported. AI supports only initial_install.
To update your system or specific packages, use the pkg update command on the installed system.
pool newpool auto auto auto device
Example:
<target>
  <disk>
    <disk_name name="c1t0d0" name_type="ctd"/>
    <partition action="create" name="1" part_type="191">
      <slice action="create" force="true"
       in_vdev="rpool_vdev" in_zpool="newpool" name="0"/>
    </partition>
  </disk>
  <logical nodump="false" noswap="false">
    <zpool is_root="true" name="newpool">
      <vdev name="rpool_vdev" redundancy="none"/>
    </zpool>
  </logical>
</target>
Translation by js2ai:
If a pool is specified in a profile, js2ai creates the ZFS root pool using the specified devices. The pool keyword supersedes all other keywords when js2ai determines which devices to use for the ZFS root pool.
The js2ai command does not perform any validation of the pool size, swap size, or dump size. You might need to adjust these sizes in the resulting AI manifest to achieve a successful installation with this manifest.
 
pool newpool auto auto auto any
For js2ai, if you specify any instead of a physical device name, you must provide device information prior to the specification that includes the any parameter. For example, you could provide a root_device or usedisk specification before this pool specification. See Example 6, Fixing mirrorpool.profile Errors for an example.
root_device c1t0d0s0
Example:
<target>
  <disk>
    <disk_name name="c1t0d0" name_type="ctd"/>
    <partition action="create" name="1" part_type="191">
      <slice action="create" force="true"
       in_vdev="rpool_vdev" in_zpool="rpool" name="0"/>
    </partition>
  </disk>
  <logical nodump="true" noswap="false">
    <zpool is_root="true" name="rpool">
      <vdev name="rpool_vdev" redundancy="none"/>
    </zpool>
  </logical>
</target>
Translation by js2ai:
When root_device is specified, js2ai sets the rootdisk to the specified device.
system_type
AI manifests do not differentiate system types.
Translation by js2ai:
Only the value standalone is supported.
usedisk
Translation by js2ai:
The js2ai command might use the specified device or devices to resolve subsequent any or rootdisk specifications. Devices specified that are not used for this purpose are added to the ZFS root pool by js2ai when that pool is not mirrored.
Copyright © 2011, 2020, Oracle and/or its affiliates. All rights reserved. 
Previous
Next