VMware: Handle image size correctly for OVA and streamOptimized images
The image size is different from the virtual disk size when the image is
streamOptimized or OVA. In this case we need to use the size of the
virtual disk which belongs to the temporary VM created by ImportVApp.
This works for both vSAN and VMFS datastores.
(cherry picked from commit bfc5edc405138e3412ae1af01abbf098c319c77c)
Reviewed: https:/ /review. openstack. org/277990 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=2c6c67422e0 e9dac5e4bd0b610 85d3ca1b32e789
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit 2c6c67422e0e9da c5e4bd0b61085d3 ca1b32e789
Author: Radoslav Gerganov <email address hidden>
Date: Thu Mar 26 16:54:05 2015 +0200
VMware: Handle image size correctly for OVA and streamOptimized images
The image size is different from the virtual disk size when the image is
streamOptimized or OVA. In this case we need to use the size of the
virtual disk which belongs to the temporary VM created by ImportVApp.
This works for both vSAN and VMFS datastores.
(cherry picked from commit bfc5edc405138e3 412ae1af01abbf0 98c319c77c)
Related-Bug: #1240373 1453b07ee9fed3d ffdd8b4a0c7
Related-Bug: #1472955
Change-Id: Ie7df9a78632ff0