cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6181) Root resize
Date Sat, 23 May 2015 17:06:18 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557433#comment-14557433
] 

ASF GitHub Bot commented on CLOUDSTACK-6181:
--------------------------------------------

GitHub user milamberspace opened a pull request:

    https://github.com/apache/cloudstack/pull/294

    CLOUDSTACK-6181 Specify GB for the value of rootdisksize parameter. Add some Bytes/GB
for log or exception messages. Fix Gb->GB.

    The new behavior (since 4.4) rootdisksize for KVM hyperviser when you deploy a new VM
use GB value. Update Docs Api to indicate the value type.
    
    Cherry-pick to 4.5 and 4.4 should be done

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/milamberspace/cloudstack RootDiskSizeMaster

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/294.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #294
    
----
commit 87d4086a64a6ebf387bda03509e0c03dac685cae
Author: Milamber <milamber@apache.org>
Date:   2015-05-23T15:58:05Z

    CLOUDSTACK-6181 Specify GB for the value of rootdisksize parameter. Add some Bytes/GB
for log or exception messages. Fix Gb->GB.

----


> 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
>              Labels: disk, resize, template
>             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.3.4#6332)

Mime
View raw message