Enable the HP LeftHand/StoreVirtual iSCSI driver in standard mode

Install the hplefthandclient Python package on the OpenStack Block Storage system.

# pip install 'hplefthandclient>=1.0.2,<2.0'

If you are not using an existing cluster, create a cluster on the HP LeftHand storage system to be used as the cluster for creating volumes.

Make the following changes in the /etc/cinder/cinder.conf file:

## REQUIRED SETTINGS

# LeftHand WS API Server URL
hplefthand_api_url=https://10.10.0.141:8081/lhos

# LeftHand Super user username
hplefthand_username=lhuser

# LeftHand Super user password
hplefthand_password=lhpass

# LeftHand cluster to use for volume creation
hplefthand_clustername=ClusterLefthand

# LeftHand iSCSI driver
volume_driver=cinder.volume.drivers.san.hp.hp_lefthand_iscsi.HPLeftHandISCSIDriver

## OPTIONAL SETTINGS

# Should CHAPS authentication be used (default=false)
hplefthand_iscsi_chap_enabled=false

# Enable HTTP debugging to LeftHand (default=false)
hplefthand_debug=false

# The ratio of oversubscription when thin provisioned volumes are involved.
# Default ratio is 20.0, this means that a provisioned capacity can be 20 times of the total
# physical capacity.
max_over_subscription_ratio=20.0

# This flag represents the percentage of reserved back-end capacity.
reserved_percentage=15
                    

You can enable only one driver on each cinder instance unless you enable multiple back end support. See the Cinder multiple back end support instructions to enable this feature.

If the hplefthand_iscsi_chap_enabled is set to true, the driver will associate randomly-generated CHAP secrets with all hosts on the HP LeftHand/StoreVirtual system. OpenStack Compute nodes use these secrets when creating iSCSI connections.

	Important
	CHAP secrets are passed from OpenStack Block Storage to Compute in clear text. This communication should be secured to ensure that CHAP secrets are not discovered.

	Note
	CHAP secrets are added to existing hosts as well as newly-created ones. If the CHAP option is enabled, hosts will not be able to access the storage without the generated secrets.

Save the changes to the cinder.conf file and restart the cinder-volume service.