Hi, Hari
1) Get your point. in current implementation, users have to delete all
the VM snapshots manually if they want to upgrade service offering,
And i agree with you that it would be better to make this deletion
automated if users confirm the service upgrading and their memory
snapshots will be
Hi, Fang
1. Yes, There is a global config limit for the max snapshots each vm can
take, default is 10
2. Yes, parent and current snapshot is updated when any vm snapshot
operation is taken.
3. It is not allowed to attach or detach any volumes if the VM already has
some vm snapshots, you can refer
Hi Mice
Thanks for the comments - please see some more feedback inline below
Hari
-Original Message-
From: Mice Xia [mailto:weiran.x...@gmail.com]
Sent: Monday, November 19, 2012 5:52 PM
To: cloudstack-dev@incubator.apache.org
Subject: VM Snapshot progress update
Hi, Hari,
changing se
Hi Mice,
Thanks for the doc. I have couple of questions:
1. Do you set a upper limit on how many VM snapshots can be created on a VM /
cluster?
2. If we have 3 vm snapshots,
A
|
B
\
C where A is the parent of B and B is parent of C.
If
Hello Mice,
Thanks for this feature! After reading your document, I have a couple of
questions:
Under the limitations section, can you please elaborate, in general, why those
limitations arise - is it because they are not implemented (in phase 1, for
example due to lack of time etc.) or they d
stack-dev@incubator.apache.org
Subject: Re: VM Snapshot progress update
On 11/19/2012 11:22 AM, Mice Xia wrote:
> Hi, Folks,
>
> Sorry for the late update. I have been busy recently and haven’t updated this
> for awhile.
> Yesterday I re-created vm-snapshot branch based on
On 11/19/2012 11:22 AM, Mice Xia wrote:
Hi, Folks,
Sorry for the late update. I have been busy recently and haven’t updated this
for awhile.
Yesterday I re-created vm-snapshot branch based on 4.0 branch and submitted
refactorred codes with KVM support.
Now the major parts have been done, and
