[
https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101326#comment-15101326
]
ASF GitHub Bot commented on CLOUDSTACK-6181:
--------------------------------------------
GitHub user ustcweizhou opened a pull request:
https://github.com/apache/cloudstack/pull/1342
CLOUDSTACK-6181: Add 'root disk size' field in instance wizard for KVM
templates
This 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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ustcweizhou/cloudstack root-disk-size-ui
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1342.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 #1342
----
commit cb98a113ca6e2183f6feb6c62fb04a2c514af361
Author: Wei Zhou <[email protected]>
Date: 2016-01-15T06:47:47Z
CLOUDSTACK-6181: Add 'root disk size' field in instance wizard for KVM
templates
This 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.
----
> 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)
