Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

fvandun1

30 Posts

712

January 19th, 2016 10:00

Fujitsu DX support in VIPR Controller over Openstack-CinderFujitsu DX support in VIPR Controller over Openstack-Cinder

Hello community,

We will deploy a VIPR Controller solution for managing storage arrays VNX, Netapp and Fujitsu Eternus (Fujitsu DX60).

The last one (Fujitsu DX60 and DX40 array) seems to be only supported via Openstack Cinder API.

Our question now is:

When VIPR Controller supports Fujitsu DX via Openstack Cinder, does this mean that the volumes created by VIPR Controller via the Openstack Cinder API on the Fujitsu array can only be used by Openstack compute  nodes?

Or can these volumes, once created, be directly assigned by VIPR Controller to physical hosts as well?

Thanks in advance,

Francis

Velik1

36 Posts

January 20th, 2016 09:00

Francis,

Answer is ViPR can zone newly created devices to any host ViPR is aware of (discovered or manually created), ViPR isn't aware of Nova compute nodes since ViPR doesn't integrate with Nova service. The pre-requisite for ViPR Export is host to be in ViPR and SAN connectivity between host initiator and Cinder-reported FA WWN to be in the same SANs.

Cinder reports back to ViPR what volumes have been created and what front end port WWNs they have been exposed through. ViPR then uses this information in 2 ways:

  1. exposed front end port WWNs are added to storage array information within ViPR (Cinder doesnt report this full information on discovery, only on provisioning; Admin can counter that gap by manually adding FA port WWNs)
  2. Admin can instruct ViPR to perform zoning and masking (ViPR Export operation).

does above help?

Stanislav

Was this post helpful?

View All

No Events found!

Top