IBM Storage driver is a unified Volume driver for IBM XIV, Spectrum Accelerate, FlashSystem A9000, FlashSystem A9000R and DS8000 storage systems.
Bases: cinder.volume.drivers.san.san.SanDriver, cinder.volume.driver.ManageableVD, cinder.volume.driver.ExtendVD, cinder.volume.driver.SnapshotVD, cinder.volume.driver.MigrateVD, cinder.volume.driver.ConsistencyGroupVD, cinder.volume.driver.CloneableImageVD, cinder.volume.driver.TransferVD
IBM Storage driver
IBM Storage driver is a unified Volume driver for IBM XIV, Spectrum Accelerate, FlashSystem A9000, FlashSystem A9000R and DS8000 storage systems.
Creates a consistency group snapshot.
Create Cloned Volume.
Creates a consistency group.
Creates a consistencygroup from source.
Create an export.
Create a snapshot.
Create a volume on the IBM Storage system.
Create a volume from a snapshot.
Deletes a consistency group snapshot.
Deletes a consistency group.
Delete a snapshot.
Delete a volume on the IBM Storage system.
Setup and verify connection to IBM Storage.
Ensure an export.
Extend Created Volume.
Failover a backend to a secondary replication target.
Notify the backend that it’s frozen.
Return replication status.
Get volume stats.
Map the created volume.
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. In the case of XIV family and FlashSystem A9000 family, the existing_ref consists of a single field named ‘existing_ref’ representing the name of the volume on the storage.
There are two ways to do this:
If the existing_ref doesn’t make sense, or doesn’t refer to an existing backend storage object, raise a ManageExistingInvalidReference exception.
The volume may have a volume_type, and the driver can inspect that and compare against the properties of the referenced backend storage object. If they are incompatible, raise a ManageExistingVolumeTypeMismatch, specifying a reason for the failure.
Return size of volume to be managed by manage_existing.
Migrate the volume to the specified host.
Disconnect a volume from an attached instance.
Convert the volume to be of the new type.
Terminate a connection to a volume.
Notify the backend that it’s unfrozen/thawed.
Removes the specified volume from Cinder management.
Adds or removes volume(s) to/from an existing consistency group.