On 11/13/2012 04:03 PM, Mike Christie wrote:
> We also want the hosts/ifaces/hw-ports. With that object or objects:
> 
> - We need something to represent the iSCSI HBA, and its physical ports.
> We need to be able to set/get iscsi/net settings for these.
> 
> - We need something to represent the iscsi initiator ports (depends on
> the representation of the node above). With the iface feature we can
> create multiple initiator names and control which sessions use which
> one. We also need the ability to control the iSID to fix the clustering
> issue where our iSID is not persistent.
> 
> - We need to be able to be able to bind software iscsi sessions to
> specific netdevs (it could be a alias or vlan).
> 
> - We need to be able to bind be able to bind iscsi normal sesisons to
> and do discovery through specific iscsi hba ports.

Also virt entities on the hba port like vlans. The fw/hw/LLD will
normally take care of routing to the correct place, but how is this
represented to the user?


-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to