Cyril Plisko wrote:
On 11/1/06, Adam Leventhal <[EMAIL PROTECTED]> wrote:
> >What properties are you specifically interested in modifying?
>
> LUN for example. How would I configure LUN via zfs command ?
You can't. Forgive my ignorance about how iSCSI is deployed, but why
would
you want/need to change the LUN?
Well, with iSCSI specifically it is of less importance, since one can
easily
created multiple units identified by other means, than LUN.
I, however, trying to look forward for FC SCSI target functionality
mirroring
that of the iSCSI (AFAIK it is on the Rick' roadmap [and I really do not
mind helping]). In FC world it is essentially the only way to have multiple
units on a particular FC port.
The administration of FC devices for the target mode needs some serious
thinking so that we don't end up with a real nightmare on our hands.
As you point out the FC world doesn't separate the port address from the
target name. Therefore each FC target must support thousands of LUs. We
also need to support LU masking. I have no plans to support LU mapping
since that was created to support a certain OS which could only boot off
of LUN 0.
Also need to support linking iSCSI targets with FC LUs. The emulation
code doesn't care about the transport layer so there's no reason why a
logical unit can't be exposed via iSCSI and FC.
Lot's of things to worry about.
Can we do something similar to NFS case, where sharenfs can be
"on", "off", or something else, in which case it is a list of options ?
Would this technique be applicable to shareiscsi too ?
That's how the shareiscsi property works today.
--
----
Rick McNeal
A good friend will come and bail you out of jail...but, a true
friend will be sitting next to you saying, "Damn...that was fun!"
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
