Bug 1100962

Summary:	Make the image virtual size as small as possible.
Product:	Red Hat Enterprise Linux 7	Reporter:	Jaroslav Henner <jhenner>
Component:	rhel-guest-image	Assignee:	Joey Boggs <jboggs>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dgregor, jgreguske, jhenner, leiwang, rbryant, wshi
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1100959	Environment:
Last Closed:	2014-06-18 13:37:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 3 RHEL Program Management 2014-06-06 05:47:08 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 Jaroslav Henner 2014-06-10 15:16:29 UTC

I would just like to note that being able to use smaller flavours (which is not possible when the disk image is larger than the flavour defines) means the cloud-customer will have to pay more money for the cloud services because he is using larger flavours.

Comment 5 Joey Boggs 2014-06-11 01:29:13 UTC

What's the lowest size that makes sense to you? RHEVM appears to be capable of extending the disk as of 3.3 in the vm's disk properties. I'd like to keep it around 2-4GB to save the hassle for folks just downloading the qcow and using it in a virt-manager/vanilla kvm environment.

Comment 6 Joey Boggs 2014-06-11 01:30:10 UTC

pmyers, can you weigh in here as well? just want a well rounded image in multiple environments

Comment 7 Perry Myers 2014-06-11 11:48:00 UTC

I thought that we decided a rootfs size of 15GB was what we were going for and what we did in RHEL 6.

Expanding the rootfs size from 4GB to 15GB does increase the size of the resulting qcow2, but only by a relatively nominal amount.

Comment 8 Joey Boggs 2014-06-11 13:17:20 UTC

I think he's concerned about customers being billed for larger instances(small/large) where tiny would work if the disk was small enough. If the disk is imported into openstack with a lower minimum requirement would that still work correctly?

Comment 9 Perry Myers 2014-06-11 13:21:13 UTC

I don't think we have a strong requirement to support Tiny instances for RHEL.  If 15GB will fit into Small, then I think we are good.  As long as we aren't forcing people to move to Medium or Large.

For reference, how big is the filesystem on the EC2 AMIs?

AFAIR, Tiny in OpenStack is only 1GB.  I seriously doubt we can realistically squeeze our images into a 1GB rootfs and have them be useful at all.

Small by default (next step up from Tiny) is 20GB.  Right now we have 15GB.  I think that's a good size to stick with.

Comment 11 Joey Boggs 2014-06-19 13:56:03 UTC

*** Bug 1100959 has been marked as a duplicate of this bug. ***