HPE LeftHand SAN ISCSI REST Proxy.
Volume driver for HPE LeftHand Storage array. This driver requires 11.5 or greater firmware on the LeftHand array, using the 2.0 or greater version of the hpelefthandclient.
You will need to install the python hpelefthandclient module. sudo pip install python-lefthandclient
Set the following in the cinder.conf file to enable the LeftHand iSCSI REST Driver along with the required flags:
It also requires the setting of hpelefthand_api_url, hpelefthand_username, hpelefthand_password for credentials to talk to the REST service on the LeftHand array.
Bases: cinder.volume.driver.ISCSIDriver
Executes REST commands relating to HPE/LeftHand SAN ISCSI volumes.
Version history:
1.0.0 - Initial REST iSCSI proxy
1.0.1 - Added support for retype
1.0.2 - Added support for volume migrate
1.0.3 - Fixed bug #1285829, HP LeftHand backend assisted migration
should check for snapshots
1.0.4 - Fixed bug #1285925, LeftHand AO volume create performance
improvement
1.0.5 - Fixed bug #1311350, Live-migration of an instance when
attached to a volume was causing an error.
1.0.6 - Removing locks bug #1395953
1.0.7 - Fixed bug #1353137, Server was not removed from the HP
Lefthand backend after the last volume was detached.
1.0.8 - Fixed bug #1418201, A cloned volume fails to attach.
1.0.9 - Adding support for manage/unmanage.
1.0.10 - Add stats for goodness_function and filter_function
1.0.11 - Add over subscription support
1.0.12 - Adds consistency group support
1.0.13 - Added update_migrated_volume #1493546
1.0.14 - Removed the old CLIQ based driver
2.0.0 - Rebranded HP to HPE
2.0.1 - Remove db access for consistency groups
2.0.2 - Adds v2 managed replication support
2.0.3 - Adds v2 unmanaged replication support
2.0.4 - Add manage/unmanage snapshot support
2.0.5 - Changed minimum client version to be 2.1.0
2.0.6 - Update replication to version 2.1
2.0.7 - Fixed bug #1554746, Create clone volume with new size.
2.0.8 - Add defaults for creating a replication client, bug #1556331
2.0.9 - Fix terminate connection on failover
2.0.10 - Add entry point tracing
Checks for incorrect LeftHand API being used on backend.
Creates a consistency group snapshot.
Creates a consistencygroup.
Creates a consistency group from a source
Creates a snapshot.
Creates a volume.
Creates a volume from a snapshot.
Deletes a consistency group snapshot.
Deletes a consistency group.
Deletes a snapshot.
Deletes a volume.
Set up LeftHand client.
Extend the size of an existing volume.
Force failover to a secondary replication target.
Gets volume stats.
Assigns the volume to a server.
Assign any created volume to a compute node/host so that it can be used from that host. HPE VSA requires a volume to be assigned to a server.
Manage an existing LeftHand volume.
existing_ref is a dictionary of the form: {‘source-name’: <name of the virtual volume>}
Return size of volume to be managed by manage_existing.
existing_ref is a dictionary of the form: {‘source-name’: <name of the virtual volume>}
Manage an existing LeftHand snapshot.
existing_ref is a dictionary of the form: {‘source-name’: <name of the snapshot>}
Return size of volume to be managed by manage_existing.
existing_ref is a dictionary of the form: {‘source-name’: <name of the virtual volume>}
Migrate the volume to the specified host.
Backend assisted volume migration will occur if and only if;
Volume re-type is not supported.
Returns a boolean indicating whether the migration occurred, as well as model_update.
Parameters: |
|
---|
Convert the volume to be of the new type.
Returns a boolean indicating whether the retype occurred.
Parameters: |
|
---|
Unassign the volume from the host.
Removes the specified volume from Cinder management.
Removes the specified snapshot from Cinder management.
Updates a consistency group.
Because the backend has no concept of volume grouping, cinder will maintain all volume/consistency group relationships. Because of this functionality, there is no need to make any client calls; instead simply returning out of this function allows cinder to properly add/remove volumes from the consistency group.
Rename the new (temp) volume to it’s original name.
This method tries to rename the new volume to it’s original name after the migration has completed.