Iscsi connector always uses CONF.my_ip

[Cory Stone]

When attaching to a cinder volume, the virt drivers supply details about where the iscsi connection is going to come from. However, if your compute nodes have multiple network interfaces, there is no way to specify which one is going to be used for the iscsi traffic.

It would be helpful if at least a config option allowed specifying the storage ip.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/109131

[Sean Dague (sdague)]

patch still active upstream

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/109131
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f5943ad3af08f3eb5493ea928a061a5634b59087
Submitter: Jenkins
Branch: master

commit f5943ad3af08f3eb5493ea928a061a5634b59087
Author: Cory Stone <email address hidden>
Date: Wed Jul 23 16:18:09 2014 -0500

    Specify storage IP for iscsi connector

    The virt drivers supply a connector hash to cinder volumes when
    attaching. This used to basically default to CONF.my_ip. This patch
    allows the host to have a separate config option in the case the block
    traffic is on a separate network.

    DocImpact: Adds my_block_storage_ip config option for block traffic going
    over a separate network.
    Closes-Bug: #1347025

    Change-Id: I2bab7226376acd7da78e038a230bf65613547ba6