Marcus, you are referring to task CLOUDSTACK-887. I have added a comment to that bug and assigned it to myself. There is an old Resizing Volumes section, which documents a workaround for the fact that CS had no such feature (see docs/resizing-volumes.xml). But we need to update that.
Jessica T On Fri, Feb 15, 2013 at 4:15 PM, Marcus Sorensen <shadow...@gmail.com>wrote: > That is interesting. Has anyone written the resizing volumes section? I saw > a task for it but nobody assigned. > On Feb 15, 2013 5:12 PM, "Jessica Tomechak" <jessica.tomec...@gmail.com> > wrote: > > > This question on -users prompted me to look for our "Resizing Volumes" > > section. I discovered that it is missing, along with the entire "Working > > with Volumes" section. All the files are in the repo's docs directory > > already, so I think it's just an oversight. > > > > Before I file a bug and add this info back in, I wonder whether anyone > > remembers deciding on purpose to leave this info out? Or has someone > > perhaps rewritten this and put it in another part of the docs? > > > > The missing section covers: > > > > What is a volume > > Uploading an existing volume to a VM > > Attaching a volume to a VM > > Detaching a volume from one VM and attaching it to a different one > > Moving volumes from one storage pool to another > > Resizing volumes (using VHD) > > How deleting a volume affects snapshots (it doesn't) > > How to configure garbage collection of deleted volumes > > > > Jessica T. > > > > > > -----Original Message----- > > > From: Clayton Weise [mailto:cwe...@iswest.net] > > > Sent: Friday, February 15, 2013 1:33 PM > > > To: cloudstack-us...@incubator.apache.org > > > Subject: RE: customising the ROOT disk > > > > > > Not that I'm recommending or endorsing this method but we have done it > in > > > the past. Stop the instance, resize the root volume on your hypervisor > > > directly (this process varies based on the hypervisor and storage > method > > > used), adjust the size to match in the CloudStack database > (specifically > > in > > > the volumes table), and start the instance. > > > > > > -----Original Message----- > > > From: Mathias Mullins [mailto:mathias.mull...@citrix.com] > > > Sent: Friday, February 15, 2013 12:46 PM > > > To: cloudstack-us...@incubator.apache.org > > > Subject: Re: customising the ROOT disk > > > > > > true. you can do that if you have LVM or Volume manager in windows. But > > > you have to be careful. If that volume gets deleted out from under the > > VM, > > > your VM is pretty much dead. > > > > > > Thank you, > > > Matt > > > On Feb 15, 2013, at 3:38 PM, "Thomas Joseph" <thomas.jo...@gmail.com > > > <mailto:thomas.jo...@gmail.com>> wrote: > > > > > > From storage tab and create a data disk with the required size, assign > > it > > > to the VM and then increase the root volume group. > > > > > > > > > Regards, > > > Thomas > > > > > > > > > -----Original Message----- > > > From: Nux! [mailto:n...@li.nux.ro] > > > Sent: 15 February 2013 07:49 PM > > > To: Cloudstack users > > > Subject: customising the ROOT disk > > > > > > Hi, > > > > > > When I'm creating a new instance is there a way to specify the size of > > the > > > ROOT disk? I see it uses the template's size (which in my case is > > > tiny) and I need to have it increased. > > > > > > Pointers? > > > > > > Thanks, > > > > > > Lucian > > > > > > -- > > > Sent from the Delta quadrant using Borg technology! > > > > > > Nux! > > > www.nux.ro<http://www.nux.ro> > > > > > > > > >
