Hi William, > I would also propose that the iSCSI target be taken from the NIC card > which would be manually preconfigured with the target information. A > DHCP server can be configured to deliver the iSCSI target information to > the NIC, as well.
That's the best option from my point of view. The information will be already in the NIC card so it should be used by the installer. Otherwise we'll have to maintain both the parameters of the NIC's BIOS, and the ones in the manifest that could even differ, creating confusion. +1 to this proposal. > The AI client, running in the microroot environment, would need to be > modified to automatically detect the iSCSI target (disk) configured in > the NIC, mount it, and include it among potential disk targets for the > automated installation. Then the AI client selects a disk target > according to the parameters defined in the AI manifest. The MPXIO > device name (/dev/dsk/cxtx<long hex string>dx) can be specified in the > manifest, providing a reliable identifier that should not change over > OpenSolaris releases. Other AI disk selection manifest parameters, such > as target disk size or controller type (here, "scsi") could be > specified, if the MPXIO device name were not known. Only a side note. In the majority of the cases the admin won't know the device name before the installation has actually started (unless he previously discovered the iscsi disk and then noted the device name to pass it as a parameter in the manifest). So most likely everyone will use the type 'scsi' (or 'iscsi' maybe so there will be no confusing in case we have an iscsi disk available *and* an internal scsi drive?) instead of the device name. The proposal looks very good to me. Cheers, David
