You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nux (JIRA)" <ji...@apache.org> on 2014/03/08 19:22:43 UTC
[jira] [Commented] (CLOUDSTACK-5305) Allow resize of ROOT disk
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924955#comment-13924955 ]
Nux commented on CLOUDSTACK-5305:
---------------------------------
This has started to get some traction in https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> Allow resize of ROOT disk
> -------------------------
>
> Key: CLOUDSTACK-5305
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5305
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Nux
> Labels: disk, resize, root
> Fix For: Future
>
>
> Hello,
> The current size lock-in of the ROOT disk based on the template is not consistent and creates problem.
> I've always toyed with the idea of a market place, sadly the random size lock-in is the major turn-off.
> Additionally it may be one of the causes (along with lack of popularity) for distributions not to provide OS image templates as they do for Openstack; which gets me to the next issue:
> - official images for Openstack could be used with minimal modifications now that cloud-init started to support Cloudstack as a data source, but most of these images are very minimal (< 1GB) since they rely on dracut-modules-growroot and similar to expand to the target disk.
> This hinders adoption.
> I don't know how it's done on other hypervisors, on KVM I believe the template could be used as a backing file; interesting read:
> http://www.pixelbeat.org/docs/openstack_libvirt_images/
--
This message was sent by Atlassian JIRA
(v6.2#6252)