Jessica, Thanks for your work, the content looks fine to me; Whether this feature is enabled for Xenserver(and KVM) depends on other tasks' progress, and the content to be modified/added is not much if we finally decide to support them.
Chandan, Could you update test progress of Xenserver? We might need to propose a VOTE later to decide if Xenserver(and KVM) support are included in 4.2. Regards Mice -----Original Message----- From: Jessica Tomechak [mailto:jessica.tomec...@gmail.com] Sent: Tuesday, April 16, 2013 8:28 AM To: dev@cloudstack.apache.org Subject: [DOCS] Please review: VM Snapshots section (CLOUDSTACK-1561) I have posted a review draft at the URL below [1]. Please take a look. A few more replies to Mice's input inline: > > > *From:* Mice Xia [mailto:mice_...@tcloudcomputing.com] > *Sent:* Tuesday, April 09, 2013 10:25 PM > *To:* Jessica Tomechak; Vijayendra Bhamidipati > *Cc:* Animesh Chaturvedi > *Subject:* RE: Doc questions on VM Snapshots (CLOUDSTACK-684)**** > > ** ** > > Hi Jessica**** > > ** ** > > Quiesce option is not implemented, it is always ‘not quiesce’ > I added this under "Limitations". > **** > > vmsnapshot.expunge.interval and vmsnapshot.expunge.workers are not > used anymore and I have removed them from global config. > Also not in the docs! Thanks for letting me know. > **** > > ** ** > > And per Animesh’s suggestion, i.e, enable/disable this feature on a > per hypervisor basis, this has been implemented in > hypervisor_capabilities, and by default Xenserver and VMware are > enabled. But the UI part needs further work, I will contact UI gurus for > details. > I had thought this was VMware only for 4.2. Please advise if XenServer will work in this release. For now, the docs just say "VMware only." > **** > > ** ** > > *For the doc:* > > VM snapshots can't be kept if you change the VM's service offering. > Any existing VM snapshots will be discarded.**** > > VM snapshots can't be kept if you change the VM's service offering. > Any existing VM snapshots *of type ‘DiskAndMemory’* will be discarded. > I made a change for this; please check it out. > **** > > ** ** > > And if possible, it is preferred to add some explanations about ‘current’ > and ‘parent’ attribute of a snapshot. > I added a paragraph as follows: VM snapshots can have a parent/child relationship. Each successive snapshot of the same VM is the child of the snapshot that came before it. Each time you take an additional snapshot of the same VM, it saves only the differences between the current state of the VM and the state stored in the most recent previous snapshot. The previous snapshot becomes a parent, and the new snapshot is its child. It is possible to create a long chain of these parent/child snapshots, which amount to a "redo" record leading from the current state of the VM back to the original. > **** > > ** ** > > Thanks and Regards**** > > Mice > > ** ** > [1] http://people.apache.org/~jtomechak/CLOUDSTACK-1561/VM_Snapshots_Review_Draft.html Thanks, Jessica T.
