So, is this GUI field going to be in 4.3, but not functional? If so, that seems a little strange. Perhaps it should be removed.
On Mon, Jan 20, 2014 at 8:34 AM, Nux! <n...@li.nux.ro> wrote: > On 20.01.2014 13:52, Marcus Sorensen wrote: > >> If you're not against building your own code, you can apply a small >> patch that should enable it. When I developed the initial resize call, >> it actually allowed root resize, but I wasn't confident that it made >> sense to put it in the final product because root disks are managed by >> service offerings, and it allows you to violate that service offering. >> I imagine a global config option would need to be added to explicitly >> turn it on. >> > > Marcus, thanks a lot, I'd love to use this feature, but not if I'll have > to fork my own clodstack. Not being a coder I try to stay as far away from > this kind of stuff as I can. > I'll wait for this feature to be officially supported and in the meanwhile > I'll just have to maintain 4-5x times more templates. > > IMO the disk size should not depend on the template's and it should be > defined in the compute offering. This is one of the things that openstack > got right, then again openstack doesn't have much legacy to deal with so > it's understandable. I'm glad that the feature is at least planned. > > > Regards, > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
