You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Priyank Parihar (JIRA)" <ji...@apache.org> on 2016/11/23 08:25:58 UTC

[jira] [Created] (CLOUDSTACK-9604) Root disk resize support for VMware and XenServer

Priyank Parihar created CLOUDSTACK-9604:
-------------------------------------------

             Summary: Root disk resize support for VMware and XenServer
                 Key: CLOUDSTACK-9604
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9604
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Priyank Parihar
            Assignee: Priyank Parihar


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.3.4#6332)