Set root disk size from a combination of image and flavor metadata
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)
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
variable root disk
Gerrit topic: https:/
Addressed by: https:/
variable root disk
If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
