OpenSolaris

You are not signed in. Sign in or register.

OpenSolaris Project: Solaris iSCSI Target

View the leaders for this project
Project Observers

Endorsing communities

Device Drivers
HPC Developer
NFS
Networking
OS/Net (ON)
Storage
Testing

Welcome

The iSCSI Target has been integrated into Solaris and is available through the Solaris Express releases and nightly builds of OpenSolaris. If you download the OpenSolaris source tree you'll find the target code in usr/src/iscsi.

Weekly Status Updates

27-Jan-2007
The project is moving forward towards integration into Solaris 10 Update 4 which has been taking a good portion of my time to complete the various backend process work.
Later today I will post the packages which have the fix which prevented the Microsoft initiator from connecting to the Solaris iSCSI Target. The fix was putback into Solaris Nevada last weekend which will be available in build 57. One thing to note about the packages that I'll make available today, they will contain some other changes which have not been putback yet. The door interface, which the CLI uses to communicate with the daemon, has been opened up allow a normal user to run 'iscsitadm list <object>'. The door credentials are examined to determine if a requested operation should proceed. These changes also allow a user to create/modify/delete targets if 'usermod -K defaultpriv=base,sys_config <user>' is run first.

Futures.

You might be wondering what's on the horizon for the iSCSI Target. Here's a current roadmap of things planned.
  1. iSNS client support — This will enable the iSCSI target to communicate with an iSNS server and register which targets are being exported and receive a list of initiators that are aloud to connect to the target.
  2. SMF configuration — Instead of storing the configuration data in regular UNIX files, in the future the data will be stored in SMF.
  3. Persistent Reservation — The iSCSI Target currently supports the old SCSI-2 RESERVE/RELASE (it was easy). We need to really support the PGR commands and it'll take a little more work. This is a must have for Sun Cluster support. Other OS's may use PGR, but I know that SC needs this support to enable more than 2 nodes per cluster.
  4. MC/S and ERL=2 — The higher error recover and multiple connections per session are nice to have, but not really required for disk operations. For Tape operations though this is a must have.
  5. Sun Cluster Support

#1 and #2 are the top priorities right now. #4 and #5 might move ahead of #3 depending on resources available.

Some of the other features that I'm looking to add, but need to prioritize are:

  • FC Target mode
  • T10 Data Integrity
  • iSER
  • LOFI support for partitions
  • OSD Emulation
  • Media Changer
  • LUN Expansion
  • Performace enhancements over slow links
  • Performace enhancements to reduce latency
  • per port IPsec