Difference between revisions of "XenServerSnapshotBlueprint"
(Started work) |
|||
| Line 16: | Line 16: | ||
Nova virt/xenapi.py The XenAPI adapter will need to be modified to know whether it's using new-style glance or the old-style S3-like object store. For the time being, glance implies raw-disk-images, though in the future that may not necessarily be the case. | Nova virt/xenapi.py The XenAPI adapter will need to be modified to know whether it's using new-style glance or the old-style S3-like object store. For the time being, glance implies raw-disk-images, though in the future that may not necessarily be the case. | ||
| + | |||
| + | Nova api: We need expose On-demand snapshots through the API. In addition, we need to expose a way to schedule snapshots (aka backups). | ||
| + | |||
| + | snapshot-scheduler: this component will be responsible initiating scheduled snapshots at the appropriate time | ||
| + | |||
| + | snapshot-pump: snapshots are long running events. We need a watcher (to kill jobs that timeout) and way of rate-limiting the number of snapshots that take place (to limit I/O on a particular host). | ||
Revision as of 22:18, 7 December 2010
Introduction
In order for OpenStack to provide comparable functionality to the current CloudServers implementation, we will need to implement live-snapshotting of the VM's disks. In particular, we will need to support two types of snapshotting:
- On demand snapshots (these are snapshots initiated by the user)
- Scheduled snapshots (these are snapshots automatically created by the system at a particular time determined by the user)
Components
These are the components that will need to be involved to implement this functionality.
XenServer Plugin glance: This is a XenServer Plugin (similar to the current objectstore plugin that knows how to talk take an image stored in glance and restore it, and knows how to create a snapshot from a running VM and store it in glance.
Nova virt/xenapi.py The XenAPI adapter will need to be modified to know whether it's using new-style glance or the old-style S3-like object store. For the time being, glance implies raw-disk-images, though in the future that may not necessarily be the case.
Nova api: We need expose On-demand snapshots through the API. In addition, we need to expose a way to schedule snapshots (aka backups).
snapshot-scheduler: this component will be responsible initiating scheduled snapshots at the appropriate time
snapshot-pump: snapshots are long running events. We need a watcher (to kill jobs that timeout) and way of rate-limiting the number of snapshots that take place (to limit I/O on a particular host).
