NexentaEdge driver does not honor clone volume size

[Sean McGinnis]

It's possible to create a volume from a source volume with a different size. The create_cloned_volume call into the driver could have a larger volume['size'] than the source volume. So the driver will need to create the clone, then check if it needs to extend the volume to a new size.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit e150db740187e26e8bcb5234821660f20e6a960d
Author: Danny Al-Gaaf <email address hidden>
Date: Thu Mar 17 20:01:35 2016 +0100

    NexentaEdge: resize volume if cloned image is larger

    Extend volume if during create_volume_from_snapshot() the new volume
    is larger than the image it was cloned from. Extended test case to
    cover the change.

    Closes-Bug: #1554785

    Change-Id: I7cd05ace41994a631fd9cbeb84c9ffcc04a4a115
    Signed-off-by: Danny Al-Gaaf <email address hidden>

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/cinder 9.0.0.0b1 development milestone.