This makes sense, so really it comes down to where (at what level and
access) you want to do the work.
-Kelcey
>-Original Message-
>From: Marcus Sorensen [mailto:shadow...@gmail.com]
>Sent: Thursday, February 28, 2013 11:23 AM
>To: cloudstack-dev@incubator.apache.org
>
Kelcey is talking about growing the volume that the VM has, which can
be done via resizeVolume API call, or adding a new Data disk to the VM
as he mentions.
CloudStack is supposed to track the size available and size used of
storage pools, but I'm not sure how robust this is or which storage
types
In our experience with both XenServer and KVM by increasing the size of the
underlying system CS automatically noticed and updated itself. I know this is
a bit different with regard to what you're doing since you're talking about
individual volumes and I'm referring to primary storage repositor
I favor adding a new volume and using LVM in the guest to make it appear as a
single data source for the end user.
Same with windows and merged drives, or multi-backed folders.
Sent from my iPhone
On Feb 28, 2013, at 10:36 AM, Mike Tutkowski
wrote:
> Hi,
>
> Can someone give me an idea wha
