Volume driver for Tintri storage.
Bases: object
REST client for Tintri storage.
Clones a volume from snapshot.
Creates a volume snapshot.
Deletes a snapshot.
Gets a volume snapshot.
Bases: cinder.volume.driver.ManageableVD, cinder.volume.driver.CloneableImageVD, cinder.volume.driver.SnapshotVD, cinder.volume.drivers.nfs.NfsDriver
Base class for Tintri driver.
Version History
2.1.0.1 - Liberty driver 2.2.0.1 - Mitaka driver
– Retype – Image cache clean up – Direct image clone fix
Creates a volume efficiently from an existing image.
image_location is a string whose format depends on the image service backend in use. The driver should use it to determine whether cloning is possible.
Returns a dict of volume properties eg. provider_location, boolean indicating whether cloning occurred.
Fetches the image from image_service and write it to the volume.
Creates a clone of the specified volume.
Creates a snapshot.
Creates a volume from snapshot.
Deletes a snapshot.
Returns pool name where volume resides.
Parameters: | volume – The volume hosted by the driver. |
---|---|
Returns: | Name of the pool where given volume is hosted. |
Brings an existing backend storage object under Cinder management.
existing_ref is passed straight through from the API request’s manage_existing_ref value, and it is up to the driver how this should be interpreted. It should be sufficient to identify a storage object that the driver should somehow associate with the newly-created cinder volume structure.
Parameters: |
|
---|
Returns size of volume to be managed by manage_existing.
When calculating the size, round up to the next GB.
Parameters: |
|
---|
Retype from one volume type to another.
At this point Tintri VMstore does not differentiate between volume types on the same array. This is a no-op for us.
Removes the specified volume from Cinder management.
Does not delete the underlying backend storage object.
Parameters: | volume – Cinder volume to unmanage |
---|