my .02USD worth:

 I don't think this belongs in iscsiadm, I think it probably the kind of
thing which should be "out of site, out of mind." I think it should be
there if someone needs it, but considering the fairly obscure nature of
these parameters cluttering up iscsiadm with it is a bit of overkill.

Andrew Hettinger
http://Prominic.NET  ||  [EMAIL PROTECTED]
Tel:  866.339.3169 (toll free) -or- +1.217.356.2888 x.110 (int'l)
Fax: 866.372.3356 (toll free) -or- +1.217.356.3356            (int'l)
Mobile direct: 1.217.621.2540
CompTIA A+, CompTIA Network+, MCP


                                                                       
             David Weibel                                              
             <[EMAIL PROTECTED]                                         
             .com>                                                      To
             Sent by:                  [email protected]:
             storage-discuss-b                                          cc
             [EMAIL PROTECTED]                                         
             s.org                                                Subject.
                                       Re: [storage-discuss] iscsi /   
                                       CR6497777 : What should become a
             08/25/2008 03:44          tunable?                        
             PM                                                        
                                                                       
                                                                       
                                                                       
                                                                       
                                                                       




iSCSI already has lots of parameters that effect transfer sizes, io flow,
timeouts, etc.  Instead of hiding these new parameters in iscsi.conf
how about making these "vendor specific" parameters and have them
managed though the same management interfaces (ie. iscsiadm).  The
iscsi.conf parameters tend to be misused if anything.  The only intended
iscsi.conf parameter was mpxio-disable=yes since that matched what was
done with scsi_vhci.conf, fcp.conf, and srp.conf.  (The other iscsi.conf
parameters are ones that were slipped in by a developer and didn't really
match the management goals of the rest of the software at the time.
One might consider prompting or removing those if they are really used.
These are related to TCP socket options.)

The other advantage of using iscsiadm.  Is if you follow the same
management style with those parameters they could be updated
without requiring a reboot.  This is more work but would lead to a
more consistent / usable product.


This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

<<inline: graycol.gif>>

<<inline: pic28562.gif>>

<<inline: ecblank.gif>>

_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to