Bases: cinder.volume.drivers.san.san.SanISCSIDriver
OpenStack driver to enable SolidFire cluster.
Create a clone of an existing volume.
Setup the iscsi export info.
Create a snapshot of a volume on the SolidFire cluster.
Note that for SolidFire Clusters currently there is no snapshot implementation. Due to the way SF does cloning there’s no performance hit or extra space used. The only thing that’s lacking from this is the abilit to restore snaps.
After GA a true snapshot implementation will be available with restore at which time we’ll rework this appropriately.
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 multipe volumes with same name, volumeID is what’s guaranteed unique.
Verify the iscsi export info.
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