Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 28 Jan 2016 12:34:40 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12697640.1393493233000.236777.1453984480245@Atlassian.JIRA>
In-Reply-To: <JIRA.12697640.1393493233000@Atlassian.JIRA>
References: <JIRA.12697640.1393493233000@Atlassian.JIRA>
 <JIRA.12697640.1393493233852@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-6181) Root resize
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF subversion and git services commented on CLOUDSTACK-6181:
-------------------------------------------------------------

Commit a4ad71cc56d07d9314bb060f93846d75cace4e11 in cloudstack's branch refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a4ad71c ]

Merge pull request #1342 from ustcweizhou/root-disk-size-ui

CLOUDSTACK-6181: Add 'root disk size' field in instance wizard for KVM templatesThis commit includes three changes:
(1) Revert commit 13bf1ec5da9891eca98ef5dab61bf74b6db9530b to show the 'root disk size' field
(2) Set the default value from '1' to empty. This also changes the default value of customized service offerings from '1' to empty.
(3) show 'root disk size' field only when users choose a KVM template, as cloudstack supports deployvm with rootdisksize on KVM only.

* pr/1342:
  CLOUDSTACK-6181: Add 'root disk size' field in instance wizard for KVM templates

Signed-off-by: Remi Bergsma <github@remi.nl>


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