Efficient image cloning feature does not recognize volume-type and incompatible with SSC.

[Jeff Applewhite]

When performing efficient image cloning, if volume-type is supplied with image-id in the create command, sometimes the cloning is done in the shares which do not match the volume-type criteria. While cloning it should be verified if the cache is in share which can host volume for specified volume-type, if not then usual copy-image-to-volume route should be followed.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/47365
Committed: http://github.com/openstack/cinder/commit/f47581de091cac8f32151d2faf72df2fe84fcf62
Submitter: Jenkins
Branch: master

commit f47581de091cac8f32151d2faf72df2fe84fcf62
Author: Navneet Singh <email address hidden>
Date: Thu Aug 1 06:47:48 2013 +0530

    NetApp fix clone image compatibility issue with ssc

    It makes clone image functionality compatible
    with the ssc feature. Hence it makes clone
    image sensitive to volume type and provision
    on the right share matching volume type
    extra specs.

    Change-Id: If980239fedf784a1cca7abd6ee3d00f8625b9b11
    Closes-Bug:#1226752