Hi,  I have been able to fix the pb using this config:  [viprblockdriver] volume_driver = cinder.volume.drivers.emc.vipr.emc_vipr_fc.EMCViPRFCDriver volume_backend_name=EMCViPRFCDriver vipr_hostname=vipr-client-210.domain vipr_port=4443 vipr_username=cinder[NAME] vipr_password=cloud123 vipr_cli_path=/opt/storageos/cli/bin vipr_tenant=EscalaTenant vipr_project=EscalaProject vipr_varray=VMAX40K_VA vipr_cookiedir=/tmp vipr_storage_vmax=True  Thank you anyway.
Hi,  Trying to create a cinder-volume using ViPR, I have setup my opensatck (IceHouse) with the following information: cinder.conf [viprblockdriver] volume_driver = cinder.volume.drivers.emc.vipr.emc_vipr_fc.EMCViPRFCDriver vipr_hostname=vipr-client-210.  vipr_port=4443 vipr_username=cinder@  vipr_password=xxxxxxxxx vipr_cli_path=/opt/vipr/cli/bin vipr_tenant=EscalaTenant vipr_project=EscalaProject vipr_varray=VMAX40K_VA vipr_cookiedir=/tmp vipr_storage_vmax=True  Then I started cinder, all is fine... I registered a new volume type, and configure it: # cinder type-list | ID |         Name        | | f71ce2ac-7d91-4484-9ff9-911cdc1b4822 |      VMAX40K_VP     |  # cinder extra-specs-list | ID |         Name        | extra_specs | | f71ce2ac-7d91-4484-9ff9-911cdc1b4822 |      VMAX40K_VP | {u'volume_backend_name': u'EMCViPRFCDriver', u'ViPR:VPOOL': u'VMAX40K_VP'} |  I went to the Horizon UI, and created a new volume ... but the exec fails almost instantly. Looking at the logs I found a trace in api.log, but nothing else !! So, does someone has an idea how I can debug this further? The surprise is that it fails instantly, so I guess the error is not in ViPR itself, but I am unable to find the root cause for it.  Thanks!
ViPR used as Cinder-Volume: create volume fails