Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

cinder-volume storwize driver "host" creation on SAN

Recently (Ocata) I am seeing cinder-volume only creating a single "host" on the SAN (IBM Storwize). All the compute nodes seem to be sharing this single host/iqn definition.

In previous experience using the Storwize driver, cinder-volume would create a separate host/iqn definition for each compute node. Anyone know if this is a (default)setting causing this, or some other explanation or insight into how the host creation decides this?