This article applies to OpenStack versions prior to Ocata.

For OpenStack Ocata or later, see OpenStack InfiniBox Volume Driver.

Mixing OpenStack APIs and non-OpenStack methods are not supported when used to attach the same hosts via the same protocol.

For example, it is not possible to create boot-from-SAN volumes and OpenStack volumes for the same host with Fibre Channel. Instead, use a different protocol for one of the volumes. 

The cinder-volume API does not support attaching a volume via iSCSI and FC in the same call.

So when cinder asks our volume driver to map a volume to the host, and supplies both iSCSi IQN and FC WWPNs, the volume driver needs to choose which connectivity type to process.

Since OpenStack is more common in iSCSI setups, we chose to accept iSCSI by default; meaning, if a OpenStack host uses both iSCSI and FC, we will favour iSCSI by default. This can be changed in via the configuration file.

You can change the behaviour of the driver by added infinidat_prefer_fc = true to the configuration; this will tell the driver to use the FC WWPNs in initialize_connection and terminate_connection for the specific volume backend in base both iSCSI IQN and FC WWPNs are supplied in the connector details.

There's no option to set this parameter with infini-openstack (our command-line tool); this needs to be done manually by modifying the cinder configuration file (the default location is /etc/cinder/cinder.conf). Here's a sample diff when applying this change: 

 volume_driver = infinidat_openstack.cinder.InfiniboxVolumeDriver
 san_ip = box-demo
 infinidat_pool_id = 1
 san_login = admin
 san_password = 123456
 infinidat_provision_type = thin
-infinidat_prefer_fc = False
+infinidat_prefer_fc = True
 infinidat_allow_pool_not_found = False
 infinidat_purge_volume_on_deletion = False

It doesn't matter if the value is True or true

Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Last edited: 2022-08-06 08:22:32 UTC