[CLOUDSTACK-6181] Root resize

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 4.4.0
• Fix Version/s: 4.9.0
• Component/s: Hypervisor Controller, Storage Controller, UI
• Security Level: Public (Anyone can view this level - this is the default.)
• Labels: disk resize template
• Environment: KVM/libvirt/CentOS, Xenserver
• Assignee: Unassigned
• Reporter: Nux
• Created: 27/Feb/14 09:27
• Updated: 04/Aug/16 18:26
• Resolved: 15/Mar/14 06:50

Description

Rationale:

Currently the root size of an instance is locked to that of the template. This creates unnecessary template duplicates, prevents the creation of a market place, wastes time and disk space and generally makes work more complicated.

Real life example - a small VPS provider might want to offer the following sizes (in GB):
10,20,40,80,160,240,320,480,620
That's 9 offerings.

The template selection could look like this, including real disk space used:
Windows 2008 ~10GB
Windows 2008+Plesk ~15GB
Windows 2008+MSSQL ~15GB
Windows 2012 ~10GB
Windows 2012+Plesk ~15GB
Windows 2012+MSSQL ~15GB
CentOS ~1GB
CentOS+CPanel ~3GB
CentOS+Virtualmin ~3GB
CentOS+Zimbra ~3GB
CentOS+Docker ~2GB
Debian ~1GB
Ubuntu LTS ~1GB

In this case the total disk space used by templates will be 828 GB, that's almost 1 TB. If your storage is expensive and limited SSD this can get painful!

If the root resize feature is enabled we can reduce this to under 100 GB.

Issue Links

• is related to: CLOUDSTACK-9101 some issues in resize volume