[iscsi-mgmt-api-reflib] Re: feedback requested regarding IMA plugins for software iSCSI i nitiators

[Paul v. B. <Paul.Vonbehren@Sun.COM>]

David Dillard wrote:

>>>  3. Expose LU
>>>  4. Unexpose LU
>>
>>No, we are assuming this is managed from targets (LUN Masking).
> 
> 
> Huh?  IMA_ExposeLu exposes the LU to the OS, not to the initiator.

Understood.  Our plan is to have the initiator code expose all LUNs per
information reported in SCSI Report LUNs and Inquiry (as is done with
other transports) rather than changing the user experience for iSCSI.
Note that we don't provide any per-LU management in FC Persistent
Binding either - we allow you to specify which I_T pairs will be
enumerated by the drivers, but all usable LUNs within the I_T pair
are enumerated.

It seems like all arrays provide this capability (LUN Masking) now, so
the customer will have already had to use the array management interface
to decide which initiators will be granted access to LUNs.  Assuming the
customer has already done this once, we didn't see a good reason why
the customer would need to override this decision on the initiator side.

Paul