[
https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556316#comment-14556316
]
ASF GitHub Bot commented on CLOUDSTACK-6181:
--------------------------------------------
Github user mlsorensen commented on the pull request:
https://github.com/apache/cloudstack/pull/281#issuecomment-104692430
It was fixed for QCOW2 and LVM, back in January or February (unless
something has changed since then). It may be fine for RBD, I just wanted to
bring it up as a caution. My impression was that there might be an issue with
the java bindings, either a bug or a missing call. If I remember correctly,
there are two things, there's libvirt managing volumes, and libvirt managing
block devices attached to VMs, and they are not the same thing. Resizing a
libvirt volume didn't necessarily notify any VM process using that volume of
the change, nor resize the block device attached to the live VM. 'virsh
blockresize' does this correctly at both the libvirt volume and VM block,
though, so we just went back to the script rather than trying to figure out how
to patch the java libvirt bindings.
Just make sure the existing behavior is not changed and test that you can
stop/start and read/write the root disk fine post a resize.
> 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)
