The LenovoFCDriver
and
LenovoISCSIDriver
Cinder drivers allow Lenovo S3200 or S2200 arrays
to be used for block storage in OpenStack deployments.
To use the Lenovo drivers, the following are required:
Lenovo S3200 or S2200 array with:
iSCSI or FC host interfaces
G22x firmware or later
Network connectivity between the OpenStack host and the array management interfaces
HTTPS or HTTP must be enabled on the array
Create, delete, attach, and detach volumes.
Create, list, and delete volume snapshots.
Create a volume from a snapshot.
Copy an image to a volume.
Copy a volume to an image.
Clone a volume.
Extend a volume.
Migrate a volume with back-end assistance.
Retype a volume.
Manage and unmanage a volume.
Verify that the array can be managed via an HTTPS connection. HTTP can also be used if
lenovo_api_protocol=http
is placed into the appropriate sections of thecinder.conf
file.Confirm that virtual pools A and B are present if you plan to use virtual pools for OpenStack storage.
Edit the
cinder.conf
file to define an storage backend entry for each storage pool on the array that will be managed by OpenStack. Each entry consists of a unique section name, surrounded by square brackets, followed by options specified inkey=value
format.The
lenovo_backend_name
value specifies the name of the storage pool on the array.The
volume_backend_name
option value can be a unique value, if you wish to be able to assign volumes to a specific storage pool on the array, or a name that's shared among multiple storage pools to let the volume scheduler choose where new volumes are allocated.The rest of the options will be repeated for each storage pool in a given array: the appropriate Cinder driver name; IP address or hostname of the array management interface; the username and password of an array user account with
manage
privileges; and the iSCSI IP addresses for the array if using the iSCSI transport protocol.
In the examples below, two backends are defined, one for pool A and one for pool B, and a common
volume_backend_name
is used so that a single volume type definition can be used to allocate volumes from both pools.Example 2.19. iSCSI example backend entries
[pool-a] lenovo_backend_name = A volume_backend_name = lenovo-array volume_driver = cinder.volume.drivers.lenovo.lenovo_iscsi.LenovoISCSIDriver san_ip = 10.1.2.3 san_login = manage san_password = !manage lenovo_iscsi_ips = 10.2.3.4,10.2.3.5 [pool-b] lenovo_backend_name = B volume_backend_name = lenovo-array volume_driver = cinder.volume.drivers.lenovo.lenovo_iscsi.LenovoISCSIDriver san_ip = 10.1.2.3 san_login = manage san_password = !manage lenovo_iscsi_ips = 10.2.3.4,10.2.3.5
Example 2.20. Fibre Channel example backend entries
[pool-a] lenovo_backend_name = A volume_backend_name = lenovo-array volume_driver = cinder.volume.drivers.lenovo.lenovo_fc.LenovoFCDriver san_ip = 10.1.2.3 san_login = manage san_password = !manage [pool-b] lenovo_backend_name = B volume_backend_name = lenovo-array volume_driver = cinder.volume.drivers.lenovo.lenovo_fc.LenovoFCDriver san_ip = 10.1.2.3 san_login = manage san_password = !manage
If HTTPS is not enabled in the array, include
lenovo_api_protocol = http
in each of the backend definitions.If HTTPS is enabled, you can enable certificate verification with the option
lenovo_verify_certificate=True
. You may also use thelenovo_verify_certificate_path
parameter to specify the path to a CA_BUNDLE file containing CAs other than those in the default list.Modify the
[DEFAULT]
section of thecinder.conf
file to add anenabled_backends
parameter specifying the backend entries you added, and adefault_volume_type
parameter specifying the name of a volume type that you will create in the next step.Example 2.21. [DEFAULT] section changes
[DEFAULT] ... enabled_backends = pool-a,pool-b default_volume_type = lenovo ...
Create a new volume type for each distinct
volume_backend_name
value that you added to cinder.conf. The example below assumes that the samevolume_backend_name=lenovo-array
option was specified in all of the entries, and specifies that the volume typelenovo
can be used to allocate volumes from any of them.Example 2.22. Creating a volume type
$
cinder type-create lenovo
$
cinder type-key lenovo set volume_backend_name=lenovo-array
After modifying
cinder.conf
, restart thecinder-volume
service.
The following table contains the configuration options that are specific to the Lenovo drivers.
Configuration option = Default value | Description |
---|---|
[DEFAULT] | |
lenovo_api_protocol = https |
(StrOpt) Lenovo api interface protocol. |
lenovo_backend_name = A |
(StrOpt) Pool or Vdisk name to use for volume creation. |
lenovo_backend_type = virtual |
(StrOpt) linear (for VDisk) or virtual (for Pool). |
lenovo_iscsi_ips =
|
(ListOpt) List of comma-separated target iSCSI IP addresses. |
lenovo_verify_certificate = False |
(BoolOpt) Whether to verify Lenovo array SSL certificate. |
lenovo_verify_certificate_path = None |
(StrOpt) Lenovo array SSL certificate path. |