need_longer_timeout_setting_for_solidfire_clone

[John Griffith]

Current timeout value for clone volume in the SolidFire driver is 20 seconds, this is fine in many cases however there seems to be a number of customers doing clones of volumes >= 400G. A populated 400G volume is taking upwards of 35 seconds in some cases resulting in failure.

There's no reason not to bump this timeout value up significantly to a worst case scenario (ie multi-terrabyte volume).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/grizzly
Review: https://review.openstack.org/37362

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/37358
Committed: http://github.com/openstack/cinder/commit/9ce7cdbaeb73031d841cb0943ca1812b149d1c19
Submitter: Jenkins
Branch: master

commit 9ce7cdbaeb73031d841cb0943ca1812b149d1c19
Author: John Griffith <email address hidden>
Date: Tue Jul 16 18:27:19 2013 -0600

    Increase timeout period for clone volume.

    Current timeout value for clone volume in the
    SolidFire driver is 20 seconds, this is fine
    in many cases however there seems to be a
    number of customers doing clones of
    volumes >= 400G.

    A populated 400G volume is taking upwards of
    35 seconds to clone in some cases resulting in failure.

    There's no reason not to bump this timeout value up
    significantly to a worst case scenario (ie multi-terrabyte volume).

    Fixes bug: 1202007

    Change-Id: I98c399f5d647e14f031018f7fc1cc43bb0d94c84

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/37362
Committed: http://github.com/openstack/cinder/commit/110133e2a5a90a01b983dea5fd892010082965a8
Submitter: Jenkins
Branch: stable/grizzly

commit 110133e2a5a90a01b983dea5fd892010082965a8
Author: John Griffith <email address hidden>
Date: Tue Jul 16 18:27:19 2013 -0600

    Increase timeout period for clone volume.

    Current timeout value for clone volume in the
    SolidFire driver is 20 seconds, this is fine
    in many cases however there seems to be a
    number of customers doing clones of
    volumes >= 400G.

    A populated 400G volume is taking upwards of
    35 seconds to clone in some cases resulting in failure.

    There's no reason not to bump this timeout value up
    significantly to a worst case scenario (ie multi-terrabyte volume).

    Fixes bug: 1202007

    Change-Id: I98c399f5d647e14f031018f7fc1cc43bb0d94c84
    (cherry picked from commit 9ce7cdbaeb73031d841cb0943ca1812b149d1c19)