Red Hat Bugzilla – Bug 978143
[Docs] [Feature] - RFE: live snapshot with cpu/memory/disk status
Last modified: 2016-01-26 20:59:54 EST
The addition of this content changes the nature of the snapshots section overall. Whereas until now, snapshots fit nicely within the "Storage arch" chapter of the Technical Reference Guide, this additional information will break the neat categorization alongside storage.
To resolve this bug, we'll move the snapshots information out of "Storage Architecture" into its own chapter called "Virtual Machine Snapshots". It'll go after "Templates and pools".
The existing topics are appropriately named, but will need re-factoring to take the focus off of the storage implications of snapshots, and include the implications for CPU and memory with the same weight.
Do you agree with what I've said in comment #1?
Will you be willing to work with me to update the Technical Reference Guide Snapshots content as stated above, to help me make sure the implications of this PRD are reflected properly?
Please note that in a *future* version we will have single disk snapshots, so you will need a snapshots section in the storage part. However, snapshots today are indeed entire VM snapshots and not limited to storage.
The new feature adds persistence to the ram of the machine as well.
Michal can provide more info on this feature.
Tim, I think for 3.3 it makes sense as you suggested to move it out. Please feel free to ask Arik Hadas or myself regarding implementation/behavioral details
I've made the structural change, moving the snapshots content into it's own chapter.
Now I'll set up a meeting with Michal as soon as possible to discuss how we can update the existing content to more accurately reflect changes introduced in the 3.3 cycle.
Reassigning to Jodi Biddle (email@example.com) as I am no longer working on Red Hat Enterprise Virtualization documentation.
Nothing, since the last time I touched the bug. An image of the "Disks to include" checkboxes are present in the RHEV 3.4 Administration guide.
I am closing this bug CLOSED CURRENTRELEASE.