This section describes how js2ai determines some target elements for the AI manifest from the JumpStart profile specifications.
Because js2ai does not have access to the client system profile references during the profile translation process, js2ai attempts to determine the root disk during translation using a process that matches JumpStart as much as possible.
The js2ai command performs the following steps to determine what device to use for the root disk:
If the root_device keyword is specified in the profile, js2ai sets rootdisk to the device on which the slice resides.
If rootdisk is not set and the boot_device keyword is specified in the profile, js2ai sets rootdisk to the boot device.
If rootdisk is not set, partitioning default is specified, and a solaris fdisk entry is encountered, js2ai sets rootdisk to the specified disk name.
If rootdisk is not set and a filesys cwtxdysz size / entry is specified in the profile, js2ai sets rootdisk to the cwtxdysz disk specified in the entry.
If rootdisk is not set and a usedisk disk-name entry is specified in the profile, js2ai sets rootdisk to the disk-name disk specified in the entry.
If rootdisk is not set and the following specification is encountered in the profile where size is not 0 or delete and disk-name is not all, then rootdisk is set to this disk name.
fdisk disk-name solaris size
If rootdisk is not set, any occurrence where the device is specified as rootdisk generates a conversion error.
The js2ai command performs the following steps to determine what device to use when the any keyword is specified:
If the any device is specified and the keyword action specified (non-mirrored pool, or filesys with a / mount point), the any device is set to rootdisk if rootdisk is set.
If the any device has not been translated and a usedisk statement exists in the profile, the any device is set to the device specified by the usedisk statement.
If the any device has not been translated and the action where the any device is specified causes the ZFS root pool to be created, AI chooses the device, unless a mirrored pool is specified.
The js2ai command performs the following steps to determine which device to use for the ZFS root pool. Once the ZFS root pool is determined, subsequent definitions encountered are flagged as errors if they conflict with the ZFS root pool that has already been determined.
If the profile specifies the pool keyword, js2ai sets the ZFS root pool to the devices specified by the pool keyword.
If the ZFS root pool has not been determined and the profile specifies a file system with a mount point of /, the ZFS root pool is created using the devices specified.
If the ZFS root pool has not been determined, all keywords in the profile have been processed, and rootdisk is set, the ZFS root pool is created using the rootdisk device.
If the ZFS root pool has not been determined and the partition type is default, AI chooses the device to use for the ZFS root pool.
If the ZFS root pool has not been determined and no errors have occurred during processing, AI chooses the device to use for the ZFS root pool.
If the ZFS root pool is not a mirrored pool and one or more usedisk devices that were specified have not been used for a rootdisk or any device translation, those disks are added to the ZFS root pool.