archive_location

backup_media

boot_device device
boot_device c1t0d0

<target>
  <disk whole_disk="true">
    <disk_name name="c1t0d0" name_type="ctd"/>
  </disk>
  <logical nodump="true" noswap="false"/>
</target>

boot_device device eeprom
boot_device c0t0d0s0 update

bootenv

client_arch

client_root

client_swap

cluster cluster-name

The Oracle Solaris 11 OS 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 installation. You can customize this list of packages.

cluster cluster-name delete

dontuse

fdisk disk_name type size
fdisk c0t3d0 solaris all

<target>
  <disk>
    <disk_name name="c0t3d0" name_type="ctd"/>
    <partition action="create" name="1" part_type="191"/>
  </disk>
  <logical nodump="true" noswap="false"/>
</target>

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

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.

filesys c1t0d0s0 10000 /

<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 tool only supports translations of the root file system (/) and swap.

filesys mirror:rpool
c6t0d0s0 c6t1d0s0 60048 /

<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

forced_deployment

geo

install_type

layout_constraint

local_customization

locale

metadb

no_content_check

no_master_check

num_clients

package SUNWpampkcs11
package SUNWpampkcs11 add

<software type="IPS">
  <software_data action="install">
    <name>pkg:/SUNWpampkcs11</name>
  </software_data>
</software>

package SUNWpampkcs11 add nfs
golden:/packages/Solaris_10

Translation by js2ai:

The js2ai tool ignores the retrieval_type location argument.

package SUNWpampkcs11 delete

<software type="IPS">
  <software_data action="uninstall">
    <name>pkg:/SUNWpampkcs11</name>
  </software_data>
</software>

partitioning default
partitioning explicit

Translation by js2ai:

For js2ai, partitioning must be default or explicit. For explicit, only swap and / are supported

partitioning existing

patch

To update your system or specific packages, use the pkg update command on the installed system.

pool newpool auto auto auto c1t0d0s0

<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>

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 tool 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

root_device c1t0d0s0

<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>

When root_device is specified, js2ai sets the rootdisk to the specified device.

system_type

Translation by js2ai:

Only the value standalone is supported.

usedisk

The js2ai tool 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.