Re: iSCSI: URL scheme

[csapuntz@cisco.com]

Doug,

This a really interesting example.

> 		Server (Drive D)
>                       \
> (always Private)  SCSI Space ---- SCSI Space
>                         \               \
>                          \               \
>              Routable SCSI Portal 1  Transparent Bridge Connection
>                           \               \
>                            \               \
>                         IP Space        IP Space
>                            /              /
>                           /              /
>                         NAT      Routable SCSI Portal 2
>                         /              /
> Non-Routable      Client (Bob)     Server (Drive C)
> 
> How does Bob get to talk to the Drive C?
> 
> Bob's system only knows about the Portal 1 however his drive is actually on
> Portal 2.  Bob's system knows about this through a sequence of boot up
> steps.  DHCP informs his system of an LDAP server.  Bob's system then
> queries this server for SCSI services via SCSI class objects.  Bob's system
> leans how to authenticate with Portal 1 and what target/lun/wwn his system
> will find his Drive C at within the realm of Portal 1.  Portal 1 knows that
> this target/lun/wwn is actually within the realm of Portal 2.  

How is the mapping configured into portal 1?

What if Bob uses his web browser to buy some storage from storage.com
and wants to mount that storage (say as Drive E)? How does he configure
all the portals?

> At Portal 2,
> his drive is at yet another target/lun/wwn.  Portal 1 will make the
> translation for Bob without Bob's knowledge into Portal 2.  Bob does not
> know how to Authenticate with Portal 2 nor where Portal 2 keeps his drive.
> That would be handled transparently for Bob.  As Portal 1 always responds
> back to the client Bob at the IP and port that he came in at, the NAT is not
> a problem.  As far as Portals are concerned, they must be exposed as
> Routable.

How is the mapping configured into portal 2?

Thanks,
_Costa