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 2.2 - Capabilites List, Extended Volume-Type Support
Naming convention change, Volume Manage/Unmanage support
Create a logical volume.
Gets the associated account, retrieves CHAP info and updates.
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: - reference (dictionary): The reference for a volume, which can be
passed to “manage_existing”.
Parameters: |
|
---|
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.
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: |
|
---|
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: |
|
---|
Unmanage a currently managed volume in Cinder
Parameters: | volume – Cinder volume to unmanage |
---|