Hi, I've done some work on testing iSCSI recently. One thing that comes up is that on a secured setup which expects a very specific initiatorName, one needs to do some back and forth to figure out what open-iscsi has picked as a random initiatorName, and add that to what's allowed by the iSCSI targets.
It would be more obvious for administrators to be able to define valid names on the storage from the start, and entering that value during install (possibly using their own naming scheme which may be different from our default). I've already contacted the iSCSI maintainers to get open-iscsi-udeb to allow the /etc/iscsi/initiatorname.iscsi file to be initialized before iscsid is started, what this needs now is simply prompting the user for an initiatorName, and writing that to the file immediately before starting iscsid. The work is ready for partman-iscsi here: http://anonscm.debian.org/cgit/d-i/partman-iscsi.git/log/?h=people/cyphermox/initiatorname. It depends on an open-iscsi change, but that has been uploaded earlier today: https://tracker.debian.org/news/752405 Thoughts? PS. Also, seems like in Ubuntu we're carrying some extra patches for dealing with preseeding iSCSI and dealing with the case where no disks are detected by hw-detect at all (in which case we may try to login to iSCSI if the user enabled it); I will prepare a code branch for hw-detect that updates the code from cjwatson already in git, if there's anything that has changed since. -- Mathieu Trudel-Lapierre <mathieu...@gmail.com> Freenode: cyphermox, Jabber: mathieu...@gmail.com 4096R/65B58DA1 818A D123 0992 275B 23C2 CF89 C67B B4D6 65B5 8DA1
signature.asc
Description: OpenPGP digital signature
