Feature #1224
Support VM snapshots
| Status: | Closed | Start date: | 04/12/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jaime Melis | % Done: | 0% | |
| Category: | Drivers - Auth | |||
| Target version: | Release 4.0 | |||
| Resolution: | fixed | Pull request: |
Description
- list snapshots for a vm
- revert to a given snapshot
Associated revisions
Feature #1224: New method one.vm.snapshotcreate
Feature #1224: Fix snapshot attribute creation
Feature #1224: New command onevm snapshot-create
Feature #1224: Add snapshot_create vmm/kvm driver action
Feature #1224: Add placeholder for vmware and xen snapshot_create actions
Feature #1224: Return proper hypervisor_id to the core
Feature #1224: Remove debugging info
Feature #1224: Add snapshot_revert driver action
Feature #1224: Fix snapshotting not supported message for VMware
Feature #1224: New xmlrpc method one.vm.snapshotrevert
Feature #1224: New command onevm snapshot-revert
Feature #1224: Fix bug in onevm snapshot-revert
Feature #1224: Accept empty names for new snapshots
Feature #1224: Make the snapshot name optional in the CLI
Feature #1224: one.vm.snapshotcreate returns the ID of the new snapshot
Feature #1224: Delete the snapshot attributes when the VMs leave the RUNNING state
Feature #1224: onevm show formats the snapshots in a table
Feature #1224: Allow snapshot commands for multiple VMs
Feature #1224: snapshot-create can be scheduled
Feature #1224: New command onevm snapshot-delete
Feature #1224: New vmm driver action snapshot-delete
Feature #1224: Fix bug in LCM method snapshot_revert_success
Feature #1224: The name of the snapshot is up to the driver
Feature #1224: Minor edits
Feature #1224: The hypervisor_id of the snapshot for Libvirt/KVM is decided by Libvirt
Feature #1224: Fix bug in no snapshot support error message reporting
Feature #1224: add vmware drivers
Feature #1224: the snapshot create method doesn't need snapshot_id
Feature #1224: snapshot-* actions should be local for the vmware driver
feature #1224: Get rid of unused method in VirtualMachine
feature #1224: split HOTPLUG state into HOTPLUG & HOTPLUG_SNAPSHOT
feature #1224: Implement snapshot interface for the dummy driver
Feature #1224: Add snapshot methods to Java OCA
History
#1
Updated by Ruben S. Montero about 9 years ago
- Target version changed from Release 3.6 to Release 3.8
#2
Updated by Ruben S. Montero almost 9 years ago
- Target version changed from Release 3.8 to Release 4.0
#3
Updated by Sebastian Porombka over 8 years ago
Hi!
Is there any design- or development-work done yet?
If not -- i would try to implement this feature and would submit a possible patch?
Greetings!
#4
Updated by Ruben S. Montero over 8 years ago
Hi,
We've not started the development yet. Summary of the design for this feature:
- Depending where the snapshot is stored, they can be internal (stored within the disk) or external (stored as a separated file/dev)
- Depending what it is saved, they can be disk, memory (RAM & CPU) or system (disk & memory)
- Our high level requirements is to be able to snapshot a VM and to "revert" to the state. The snapshots would be independent, multiple snapshots of the same VM could be instantiated once.
- The support for the different types of snapshots depends on the hypervisor and the storage technology used to support the VM disk images.
- Another requirement for us is to present and homogeneous as possible functionality across technologies.
Initially we've decided to go for disks snapshots, pretty much as the snapshots that can be found in EC2. We will use the hypervisor functionality when available to produce consistent disk snapshots...
Feedback more than welcome!
#5
Updated by Ruben S. Montero over 8 years ago
Finally, we'll go for both system and disk snapshots.
#6
Updated by Simon Boulet over 8 years ago
Ruben S. Montero wrote:
Finally, we'll go for both system and disk snapshots.
Are the one.vm.snapshotcreate and one.vm.snapshotrevert calls for the "system" snapshots ie. VM state snapshots? Are you going to have separate call / driver actions for disk snapshots?
#7
Updated by Ruben S. Montero over 8 years ago
Simon Boulet wrote:
Ruben S. Montero wrote:
Finally, we'll go for both system and disk snapshots.
Are the one.vm.snapshotcreate and one.vm.snapshotrevert calls for the "system" snapshots ie. VM state snapshots?
Yes
Are you going to have separate call / driver actions for disk snapshots?
Yes, disk snapshots will be TM based
#8
Updated by Carlos Martín over 8 years ago
Improvement to consider: The DispatchManager::snapshot_create method could call LibVirtDriverKVM (in case the VM vmm is kvm) and check if all the VM disks use DRIVER=qcow2, to return a request failure before the operation is attempted by the drivers.
#9
Updated by Ruben S. Montero over 8 years ago
- Status changed from New to Closed
- Resolution set to fixed