Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1041445 - [RFE][nova]: VMware driver should be able to spawn instances from OVA images
[RFE][nova]: VMware driver should be able to spawn instances from OVA images
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity low
: Upstream M3
: 7.0 (Kilo)
Assigned To: RHOS Maint
Jaroslav Henner
https://blueprints.launchpad.net/nova...
upstream_milestone_kilo-3 upstream_st...
: FutureFeature, OtherQA, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-12 11:08 EST by RHOS Integration
Modified: 2015-08-05 09:10 EDT (History)
13 users (show)

See Also:
Fixed In Version: openstack-nova-2015.1.0-10.el7ost
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-05 09:10:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1548 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 13:07:06 EDT

  None (edit)
Description RHOS Integration 2013-12-12 11:08:55 EST
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/vmware-driver-ova-support.

Description:

Currently, the VMware driver is using flat images (*-flat.vmdk) and metadata (disk type, adapter type,...) to spawn instances.
This approach requires the user to provide metadata and deal with flat images which are not designed to be portable.

To address to issue, the driver should be able to spawn an instance from an OVA located in the datastore. 
An OVA package is a tar archive file with the OVF directory inside: OVF is an open standard for packaging and distributing virtual appliances or more generally software to be run in virtual machines.

The VMware driver would have to untar the OVA and use the OVF embedded to spawn the VM (an ESX API is already available to boot from OVF).

This change would have the following benefits:
- OVF contains the configuration of the VM (hardware versions, networking configuration, etc.)
- The VMDK that comes with an OVF is stream-optimized (i.e. compressed)
- OVA can be handled by Glance respecting the one-to-one relationship between image and file (OVF comes with the 2 or more files constraint).






Specification URL (additional information):

None
Comment 8 errata-xmlrpc 2015-08-05 09:10:43 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548

Note You need to log in before you can comment on or make changes to this bug.