On 4/8/13 7:11 PM, "Marcus Sorensen" wrote:
>Perhaps. I think there are separate issues here. There is volume snapshot
>and vm snapshot. If the hypervisor is capable of making volumes consistent
>, but VM snapshot is more about saving running state, then the two may not
>serve the same purpose
Perhaps. I think there are separate issues here. There is volume snapshot
and vm snapshot. If the hypervisor is capable of making volumes consistent
, but VM snapshot is more about saving running state, then the two may not
serve the same purpose when leveraging san-based snapshots. Its absolutely
On 4/8/13 4:19 PM, "Marcus Sorensen" wrote:
>Oh yes, I know these things, but here's my point. You said:
>
>"When CloudStack takes a snapshot of volume, it already utilizes snapshot
>feature provided by hypervisor to allow taking point of time storage image
>in a safe manner from operating syst
Oh yes, I know these things, but here's my point. You said:
"When CloudStack takes a snapshot of volume, it already utilizes snapshot
feature provided by hypervisor to allow taking point of time storage image
in a safe manner from operating system point of view."
What about five volumes? Can we e
On 4/8/13 1:39 PM, "Marcus Sorensen" wrote:
>Has anyone put together a suggestion for adding a 'paused' state to
>virtual
>machines? Or is anyone working on it? This seems fairly straightforward,
>and I think we may need the functionality going forward. Even if people
>rarely use it themselves,
