Bases: cinder.volume.drivers.san.san.SanISCSIDriver
OpenStack driver to enable SolidFire cluster.
Create a clone of an existing volume.
Create volume on SolidFire device.
The account is where CHAP settings are derived from, volume is created and exported. Note that the new volume is immediately ready for use.
One caveat here is that an existing user account must be specified in the API call to create a new volume. We use a set algorithm to determine account info based on passed in cinder volume object. First we check to see if the account already exists (and use it), or if it does not already exist, we’ll go ahead and create it.
Create a volume from the specified snapshot.
Delete the specified snapshot from the SolidFire cluster.
Delete SolidFire Volume from device.
SolidFire allows multiple volumes with same name, volumeID is what’s guaranteed unique.
Extend an existing volume.
Get volume status.
If ‘refresh’ is True, run update first. The name is a bit misleading as the majority of the data here is cluster data
Initialize the connection and return connection info.
Optionally checks and utilizes volume access groups.
Manages an existing SolidFire Volume (import to Cinder).
Renames the Volume to match the expected name for the volume. Also need to consider things like QoS, Emulation, account/tenant.
Return size of an existing LV for manage_existing.
existing_ref is a dictionary of the form: {‘name’: <name of existing volume on SF Cluster>}
Convert the volume to be of the new type.
Returns a boolean indicating whether the retype occurred.
Parameters: |
|
---|
Mark SolidFire Volume as unmanaged (export from Cinder).
Bases: cinder.volume.targets.iscsi.SanISCSITarget