Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of shadowsor@gmail.com
 designates 209.85.128.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+y6+xHeF9cRZLEaurOEOOYhk8N1qa2TjiSNqYJSVo6ixgvr5w@mail.gmail.com>
References: 
 <7A92FF96DF135843B4B608FB576BFC3E012DA44303B3@SJCPMAILBOX01.citrite.net>
	<CA+y6+xHeF9cRZLEaurOEOOYhk8N1qa2TjiSNqYJSVo6ixgvr5w@mail.gmail.com>
Date: Fri, 15 Feb 2013 17:15:51 -0700
Message-ID: 
 <CALFpzo4tQJf+A4UDedAt962E6-BndH7FVfxs1+ZkMFYiaH3WoQ@mail.gmail.com>
Subject: Re: [DOC] Is the Working with Volumes section missing from docs on
 purpose?
From: Marcus Sorensen <shadowsor@gmail.com>
To: cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b624ec404152804d5cc659d

--047d7b624ec404152804d5cc659d
Content-Type: text/plain; charset=ISO-8859-1

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.tomechak@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:cweise@iswest.net]
> > Sent: Friday, February 15, 2013 1:33 PM
> > To: cloudstack-users@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.mullins@citrix.com]
> > Sent: Friday, February 15, 2013 12:46 PM
> > To: cloudstack-users@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.job07@gmail.com
> > <mailto:thomas.job07@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:nux@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>
> >
> >
>

--047d7b624ec404152804d5cc659d--