[
https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925734#comment-13925734
]
Nux commented on CLOUDSTACK-6181:
---------------------------------
Ok,
So my tests have been almost ok, "details[0].rootdisksize" works great for all
storage I tried, NFS, local, Gluster and CLVM. What did not work is resizing
the root volume of a stopped VM. For example:
> resize volume id=ebc4c8ee-9524-4841-88fd-a559fddd194b size=20
.Async job 9abdfe20-8b5b-44a7-bab3-843df01d4929 failed
Error 530, Volume should be in ready or allocated state before attempting a
resize
accountid = 90a4e9a8-a783-11e3-816a-9660573836d5
cmd = org.apache.cloudstack.api.command.user.volume.ResizeVolumeCmd
created = 2014-03-10T13:11:25+0000
jobid = 9abdfe20-8b5b-44a7-bab3-843df01d4929
jobprocstatus = 0
jobresult:
errorcode = 530
errortext = Volume should be in ready or allocated state before attempting a
resize
jobresultcode = 530
jobresulttype = object
jobstatus = 2
userid = 90a4f0b0-a783-11e3-816a-9660573836d5
The volume IS in "Ready" state! http://fpaste.org/83939/45885313/raw/
The management log doesn't offer much more info
http://fpaste.org/83938/13944587/raw/
> 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.2#6252)
