No way to secure volumes based on initiator name

[Vish Ishaya]

Some hardware volume drivers secure volumes based on the name of the initiator. When the connection is prepared, an ip address is sent in, but the volume driver has no way of knowing what initiator the iscsi connection will come from. There needs to be some way for the driver to get the right initiator for the instance.

This could be done with a callback, but it is easiest to add the parameter to initialize_connection.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/3586
Committed: http://github.com/openstack/nova/commit/94d8553201e50e3e9e25992bfe4735addae4ffda
Submitter: Jenkins
Branch: master

commit 94d8553201e50e3e9e25992bfe4735addae4ffda
Author: Vishvananda Ishaya <email address hidden>
Date: Sat Jan 28 01:17:00 2012 -0800

    Add initiator to initialize_connection

    Some volumes need to know the name of the initiator that will be
    connecting to the iscsi volume. This adds a call down to the hypervisor
    driver to get the ip and the initiator name for the vm before calling
    initialize connection. This connection is passed down to the volume
    driver so that it can be used to authenticate when the hypervisor
    tries to connect to the volume.

     * Adds initiator initialize_connection
     * Makes a call to driver to get initiator name and ip address
     * Gets initiator from openiscsi for libvirt
     * Gets initiator from config for xenapi
     * Add tests for the driver calls
     * Fixes bug 924461

    Change-Id: I5b6a2dd84560c7f7b447571e0abf0993e5512ca0