Jira | ||||||
---|---|---|---|---|---|---|
|
master
The objective of this API is to enable storage vendor side snapshots of virtual disk when using managed hardware as Primary Storage. When using the Primary storage plugins such as SolidFire vendor, each virtual disks are LUNs on the storage array. Using the storage array snapshot capability benefits for performance and feature set supported by the storage vendor.
StorageSnapshot does not fit in the VolumeSnapshot API because it would not perform the same tasks, a Volume Snapshot uses the hypervisor capability to create a volume snapshot then extract it and archive it into the secondary storage. The intent of a StorageSnapshot is to perform a snapshot at the hardware vendor level, and keep it there for rollback purposes and disk cloning. StorageSnapshot is more aligned with the VMsnapshot API capability but is intent to be per virtual disk basis.
When using VDI-per-LUN with XenServer 6.5 + SolidFire storage array, all VirtualDisks are unique LUNs on the storage array so it leverages snapshot capabilities of the storage vendor for volumes.
...
New API | params | Description |
---|---|---|
createStorageSnapshot | id: volume ID | Create storage-snapshot of a volume |
createVolumeFromStorageSnapshot | id: StorageSnapshot ID | Create a volume from a storage snapshot by cloning it on the device |
deleteStorageSnapshot | id: StorageSnapshot ID | Delete a single storage-snapshot |
listStorageSnapshot | volumeID: volume ID storageID: storage array ID (admin)? | List storage-snapshot of a volume |
Are there any entities being created that require usage reporting for billing purposes?
Does this change any existing entities for which usage is being tracked already?
Appendix A:
Appendix B: