You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Nux (JIRA)" <ji...@apache.org> on 2014/02/27 10:28:19 UTC

[jira] [Created] (CLOUDSTACK-6181) Root resize

Nux created CLOUDSTACK-6181:
-------------------------------

             Summary: Root resize
                 Key: CLOUDSTACK-6181
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181
             Project: CloudStack
          Issue Type: New Feature
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Hypervisor Controller, Storage Controller, UI
    Affects Versions: 4.4.0
         Environment: KVM/libvirt/CentOS, Xenserver
            Reporter: Nux
             Fix For: 4.4.0


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.





--
This message was sent by Atlassian JIRA
(v6.1.5#6160)