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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user remibergsma opened a pull request:

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

    CLOUDSTACK-6181: Allow RBD volumes to be resized

    We don't need an external script to investigate the format of the RBD volume,
    we only have to ask Libvirt to resize the volume and that will ask librbd to
    do so.
    
    Backport for 4.4, original commit: 173909e99d85cfcc85b017bc426950f9f16fddf0
    Requested by Andrija Panić http://markmail.org/thread/gau2xngqjpq5cza7


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

    $ git pull https://github.com/remibergsma/cloudstack 4.4_cepth_resize_backport

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

    https://github.com/apache/cloudstack/pull/281.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 #281
    
----
commit a26bbc2ce2f99e706895f9c0bbc6bdb5a522c37f
Author: Remi Bergsma <gi...@remi.nl>
Date:   2015-05-21T20:57:12Z

    CLOUDSTACK-6181: Allow RBD volumes to be resized
    
    We don't need an external script to investigate the format of the RBD volume,
    we only have to ask Libvirt to resize the volume and that will ask librbd to
    do so.
    
    Backport for 4.4, original commit: 173909e99d85cfcc85b017bc426950f9f16fddf0

----


> 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)