cinder.volume.drivers.datera.datera_iscsi
Modulecinder.volume.drivers.datera.datera_iscsi
Module¶DateraDriver
(*args, **kwargs)¶Bases: cinder.volume.drivers.san.san.SanISCSIDriver
, cinder.volume.drivers.datera.datera_api2.DateraApi
, cinder.volume.drivers.datera.datera_api21.DateraApi
The OpenStack Datera Driver
1.0 - Initial driver
1.1 - Look for lun-0 instead of lun-1.
2.0 - Update For Datera API v2
2.1 - Multipath, ACL and reorg
Naming convention change, Volume Manage/Unmanage support
2.1 Api Version Support, Restructure
2.3.1 - Scalability bugfixes
2.3.2 - Volume Placement, ACL multi-attach bugfix
2.4.0 - Fast Retype Support
CI_WIKI_NAME
= ‘datera-ci’¶HEADER_DATA
= {‘Datera-Driver’: ‘OpenStack-Cinder-2.4.0’}¶VERSION
= ‘2.4.0’¶create_cloned_volume
(*args, **kwargs)¶create_export
(*args, **kwargs)¶create_snapshot
(*args, **kwargs)¶create_volume
(*args, **kwargs)¶Create a logical volume.
create_volume_from_snapshot
(*args, **kwargs)¶delete_snapshot
(*args, **kwargs)¶delete_volume
(*args, **kwargs)¶detach_volume
(*args, **kwargs)¶do_setup
(*args, **kwargs)¶ensure_export
(*args, **kwargs)¶Gets the associated account, retrieves CHAP info and updates.
extend_volume
(*args, **kwargs)¶get_manageable_volumes
(*args, **kwargs)¶List volumes on the backend available for management by Cinder.
Returns a list of dictionaries, each specifying a volume in the host, with the following keys:
Parameters: |
|
---|
get_volume_stats
(*args, **kwargs)¶Get volume stats.
If ‘refresh’ is True, run update first. The name is a bit misleading as the majority of the data here is cluster data.
initialize_connection
(*args, **kwargs)¶login
(*args, **kwargs)¶manage_existing
(*args, **kwargs)¶Manage an existing volume on the Datera backend
The existing_ref must be either the current name or Datera UUID of an app_instance on the Datera backend in a colon separated list with the storage instance name and volume name. This means only single storage instances and single volumes are supported for managing by cinder.
Eg.
if using Datera 2.1 API
or
if using 2.0 API
Parameters: |
|
---|
manage_existing_get_size
(*args, **kwargs)¶Get the size of an unmanaged volume on the Datera backend
The existing_ref must be either the current name or Datera UUID of an app_instance on the Datera backend in a colon separated list with the storage instance name and volume name. This means only single storage instances and single volumes are supported for managing by cinder.
Eg.
existing_ref == app_inst_name:storage_inst_name:vol_name
Parameters: |
|
---|
retype
(*args, **kwargs)¶Convert the volume to be of the new type.
Returns a boolean indicating whether the retype occurred.
Parameters: |
|
---|
unmanage
(*args, **kwargs)¶Unmanage a currently managed volume in Cinder
Parameters: | volume – Cinder volume to unmanage |
---|
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.