Include the URL of your launchpad blueprint:
Currently open-iscsi in openstack does not allow the use of offload iscsi transports (cxgb4i, qla4xx, bnx2i etc) or other software iscsi transports (like iser). This blueprint aims to add support for this
open-iscsi has hardware iSCSI transport support. The interface argument specifies the hardware iSCSI interface to use for the operation. Any hardware vendors that currently provide hardware interfaces for open-iscsi cannot use them in openstack as the interfaces (iface) argument is not currently supported in the iSCSI driver.
Use of such iSCSI hardware transports requires providing a corresponding interface file (referred to as iface), which can be autogenerated via iscsiadm but need correctness checks or can also be generated on the fly, given the 3-tuple of ipaddress, hwaddress & transport name to be used. The iface format itself is generic and does not use any propreitary fields irrespective of transport being used.
These changes are already in nova, code can be seen here : https://review.openstack.org/#/c/146233/
This will also enable use of iSER directly through the iSCSI driver, though deprecating the iSER driver is not the aim of this spec, and will probably start with iSER disabled, (and also because iSER requires target support unlike hardware transports)
On the initiator side the only difference between using software iSCSI and hardware iSCSI transport is the interface flag (–interface=[iface])
e.g. “iscsiadm -m discovery -t st -p ip:port -I <iface file>”
iface files can automatically be generated for all hardware present on a system that is supported by open-iscsi by ‘iscsiadm -m iface’. The default format for iface file names is in the form <transport_name.hw_address>
The default iface name is ‘default’. Not using the -I parameter (which is how open-iscsi is currently being used in nova) is the same as specifying
‘iscsiadm -m discovery -t st -p ip:port -I default’
Required changes are :
Use manual discovery of iscsi-targets, and provide -I parameter when doing discovery. Transport names are written in the resultant records generated by open-iscsi, however this does not guarantee hardware transports will be used, as this can be overridden with depending on how cli params are constructed.
Actual iSCSI performance can generally be improved by using transports over iscsi_tcp, no other impact.
This can be used to deprecate the separate iSER connector, as use of iser simply implies providing -I iser param to iscsiadm
None as such. However, the minimum information required for using a tansport if it is not already configured is a 3 tuple of ip, transport name & hardware address.
Current iSCSI tests will work just fine, run separately using a faux transport (open-iscsi already supports this ability)
Use of transport ifaces will need relevant documentation.