Hi,
This is the info I have from Mice from sometime last year, not sure if it
is relevant. Sadly, I am unable to attach the original HTML message, I
will forward it off the list to you
==================
1) When a VM is created, the root volume and data volume are just
single node in storage
2) After take a Disk Snapshot, leaf nodes are created as current
volume (this is vmware case), their parents nodes are not active and are a
part of snapshots.
Two usage events are generated, since there are two volumes for
this VM.
Usage event: VMSnapshot, volumeId:root; vmid: xxxx; size: sizeOf(Root)
VMSnapshot, VolumeId:data; vmid:xxxx; size: sizeOf(Data)
3) After take a DiskMemory Snapshot:
Two usage events are generated,.
Usage event: VMSnapshot, volumeId:root; vmid: xxxx; size: sizeOf(Root) +
sizeOf(ROOT-00001) + sizeOf(memoryImage)
VMSnapshot, VolumeId:data; vmid:xxxx; size: sizeOf(Data) +
sizeOf(Data-00001)
Please note the size in usage event is CURRENT chain size of a volume.
===================
On 4/25/14 1:11 PM, "Mike Tutkowski" <[email protected]> wrote:
>Hi,
>
>I logged a JIRA ticket with regards to how we calculate
>vm_snapshot_chain_size in the volumes table (with regards to VMware).
>
>https://issues.apache.org/jira/browse/CLOUDSTACK-6514
>
>If someone out there with a bunch of VMware experience could take a look
>at
>that ticket and comment on whether or not this is a problem, that would be
>great.
>
>Thanks!
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: [email protected]
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>
>*(tm)*
