Bug 1041440

Summary: [RFE][nova]: Set root disk size from a combination of image and flavor metadata
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/variable-size-root-disk
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:38:57 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 16:08:09 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/variable-size-root-disk.

Description:

Currently all image size checks are made against the root disk size in the flavor, which is then treated as the absolute size of the root disk to create, overriding the min_disk value of the image and the image size itself.    However when working with a range of images (for example a mix of Windows and Linux) it would be better to be able to use a single set of flavors whilst still honoring the min_disk value of the image.  This would allow, for example, more efficient snapshots for images that do not need the full size of root_gb.     

This blueprint allows the root disc size to vary within the constraints specified by the image Creator (via image metadata ) and the Cloud Provider (via flavors)  


Specification URL (additional information):

https://wiki.openstack.org/wiki/VariableSizeRootDisk