Bug 1041764

Summary:	[RFE][glance]: Adding multi-hypervisor Cloud support
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	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/multi-hypervisor-cloud-support
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_discussion
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:01:58 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:13:32 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/multi-hypervisor-cloud-support.

Description:

In this case client like Nova can automatically select the correct image format when it consuming an image for particular hypervisor, for example KVM images could potentially be stored on GlusterFS supported for KVM compute nodes whereas ESX images could be stored in a NFS storage. IMO Having multi-hypervisor Clouds is an important use case to us. This enhancement can help improve Cloud deployment flexibility for Cloud owner and operator, and also provide VM more faster for end user.

Overall seems we have two way can go currently:

1. We implement that base on multi-location mechanism, to move 'disk_format', 'container_format' and 'checksum', 'size' property to location from image entry.
2. Add a new function like image-group, i.e., a set of (current style) images, each of which could have different format specifications. End user could create an image-group now by putting a specific tag on all the images in the group.

Specification URL (additional information):

None