WishList
From ISCSItarget
[edit]
Write down what you want
Note: Please write your wish with more sentences. The more detail you provided, the better chance we know exactly what you want, the better chance we work on it. Thank You.
- Faster, more efficient access using a user-level process - Found that using the reference implementation of intel-iscsi on sourceforge is about 3 times faster and does not need any kernel rpms etc. - it runs as a user daemon, except it does not have any of the features that iscsi-target supports
- Object-based storage. Bonus points if you can convince folks to use a better name (one you can search for without a billion hits)...
- Support for ESX3 servers! the iscsi-target works perfectly with windows and linux servers but ESX3 puts the disks in readonly mode? -- I have used with esx3 rc2 and it works fine
- Support for real (not file backed) cd/dvd-writer type devices. (/dev/sr? devices, maybe even /dev/hd? devices that corespond to IDE writers)
- Currently this causes a kernel panic when /dev/hd? CD/DVD writer devices are specified
- Alternatively, support iSCSI<->SCSI passthrough (for example via /dev/sg?). This way, all SCSI devices (disks, tapes, CDROMs, media changers, ...) supported by linux could be "passed through" via iSCSI, probably even IDE devices via ide-scsi
- Secondary gateway address for multipath access.
- emulation of media changer on file backed sr type devices (lun per media or traditional lun 1 for changer control)
- some form of gateway center to inform iscsi-initiators of multiple iscsi target hosts.(waaay off if not another project).
- A graphical tool to add/remove/modify targets... perhaps a webmin module.
- ietadm function to print current running configuration in an ietd.conf style form, so we can save changes made with ietadm accross restarts. Alternatively, changes made with ietadm should update the config file immediately, but a print current config function would still be nice! :-)
- Share devices for many users in same time. Map the writing data to a "mapfile" temporarily, each IP each device map to one "mapfile". Just like BXP ShareMode, it implement swap patition well for diskless linux(or other OSs), even the root patition instead of NFS! :O ! I think that's good that it doesn't erases data from a client disconnect, the reasons: 1.you can manually erase one "mapfile" when you wish, for some scheme or schedule. 2.prevent lost data when connection broken for a few time accidentally.
- LiveCD version, that can turn a PC into a SAN device with minimal configuration. Possbily dependant on iSCSI<->SCSI passthrough (or FC)
- ability to define what ethernet devices the iscsi-target daemon will present target volumes to this way you can restrict target presented volumes to specific ethernet devices in multi-homes machines
- Read only targets.
- Should be able to connect multiple initiators to a read-only target.
- How about adding a command line option to indicate the address to report to the initiator.
- Say you have this configuration: 192.168.1.1 (initiator) <--> 1.2.3.4 <- internet -> 5.6.7.8 <--> 192.168.1.1 (target) - the portal adress reported to the initator is 192.168.1.1/3260 but the address used to address the target is 5.6.7.8:3260. The result is correct discovery of targets but no data connection.
Wishes came true
- Support for Centos 4x. Longer lasting than FC3/FC4. Less bleeding edge. (i am using centos 4.x all the time and iet runs well on it)
