Bug 1041750

Summary:	[RFE][glance]: VMware vCenter templates available as glance images
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images
Whiteboard:	upstream_milestone_none upstream_status_started upstream_definition_new
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:30:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 19:09:57 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images.

Description:


Title: VMware vCenter templates available as glance images

In the current OpenStack architecture, to deploy an instance from an image, the images have to be available in glance. Images are added using the glance image-create command. This command uploads the images into the glance server.
VMware vCenter already has the deployable images in the form of “Templates”. This blueprint proposes to make
1. Glance to be aware the vCenter templates.
2. Avoid upload of VMware templates into the image server.
The advantages are
1. VMware vCenter Driver can be used to deploy the images to the ESX hosts. The driver will use the VI SDK API to deploy the template. Leverage vCenter template deployment optimizations.
2. Avoids the copy of the vCenter images into the glance image server.
The same design can be extended to other hypervisors as well.

Specification URL (additional information):

None