iSER is broken after the transition of LVM drivers to use target objects

[Aviram Bar-Haim]

The iSER driver flow, after setting volume_driver to cinder.volume.drivers.lvm.LVMISERDriver, is broken in the new driver - target model in the master, due to a mismatch in the target prefixes and a lack of iSER target initialization with the correct parameters.

Reproduced in devstack with Cinder Master branch over an RDMA environment.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/148097
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=009a6c301bb9f366eaaa76e1026ae962deda6d3b
Submitter: Jenkins
Branch: master

commit 009a6c301bb9f366eaaa76e1026ae962deda6d3b
Author: Aviram Bar-Haim <email address hidden>
Date: Fri Jan 16 02:45:30 2015 +0200

    Fix the iSER legacy usage in the new targets flow

    The iSER driver flow, after setting volume_driver to LVMISERDriver,
    is broken in the new driver - target model in the master,
    due to a mismatch in the target prefixes and a lack of iSER target
    initialization, with the correct parameters.

    In order to fix this:
      1. The function initialize_connection, that sets the iSER required
         parameters, was added to cinder/volume/targets/iser.py (and overrides the
         new connection initialization in cinder/volume/targets/tgt.py).
      2. The iSER and iSCSI prefixes equalized, due to the removal of brick/iscsi
         with the different default prefix for ISERTgtAdm (and for stability).

    Closes-Bug:#1411470

    Change-Id: Ie4b9b85b47e9da20a1de1e10415766413cd01f04