Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 71393101DF for ; Tue, 24 Feb 2015 00:22:15 +0000 (UTC) Received: (qmail 98286 invoked by uid 500); 24 Feb 2015 00:22:15 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 98259 invoked by uid 500); 24 Feb 2015 00:22:15 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 98250 invoked by uid 500); 24 Feb 2015 00:22:15 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 98247 invoked by uid 99); 24 Feb 2015 00:22:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Feb 2015 00:22:15 +0000 Date: Tue, 24 Feb 2015 00:22:15 +0000 (UTC) From: "Marcus Sorensen (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-6181) Root resize MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334152#comment-14334152 ] Marcus Sorensen commented on CLOUDSTACK-6181: --------------------------------------------- To be clear, that method should probably throw a CloudRuntimeException if it encounters an unknown pool type, there's nothing that can be done to handle such a case other than to return an error. > 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)