iSCSI login depends on fix length sleep to wait for connections to become active

[Chris Krelle]

The iSCSI login depends on a hard coded sleep value. This may not be the best approach. We should actively check for the connection to become active. The amount of time should also be adjustable to account for environments where the connection may take a little longer then allotted for with the hard coded sleep value.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/150187
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=46067160e6787631fb5a55193a02794449f22ebf
Submitter: Jenkins
Branch: master

commit 46067160e6787631fb5a55193a02794449f22ebf
Author: Chris Krelle <email address hidden>
Date: Mon Jan 26 15:58:05 2015 -0800

    Actively check iSCSI connection after login

    This replaces the sleep command at the end of the login_iscsi fuction
    with an active check and a forced lun update. These two things help ensure
    the connection sees all luns on the iSCSI device before attempting to write
    to it. It also adds a configurable option to allow users to be able to
    customize the number of attempts for their environment.

    Also add some very basic logging to aid in deploy debuging

    Change-Id: I68c9f9f86f5f113bb111c0f4fd83216ae0659d36
    Closes-bug: #1415117
    Partial-Bug: #1286374

[aeva black (tenbrae)]

Fix was partially reverted, so I am re-opening the bug