Revision history [back]

Is it possible to use the Windows Cinder storage as a backend for Glance?

I have tried it out (using Pike) and when creating a new image the basic Cinder volume create/delete/etc function works the image create ultimately fails inside glancestore.drivers.cinder with a series of similar InvalidConnectorProtocol errors e.g. "Failed to write to volume 14635b29-f3c5-4908-a6be-11bc8ab17d8c.: InvalidConnectorProtocol: Invalid InitiatorConnector protocol specified SMBFS"

This seems to track back into os_brick/initiator/connector.py. It looks like this is a consequence of Glance trying to directly mount the volume on the SMB backend, and with Glance running in a Linux container the SMBFS protocol isn't available to it so it fails.

Is there any workaround for this?

Alternatively what storage method is recommended for Glance on a hyper-converged installation similar to Hyper-C? A file backend using a mount to the SoFS share?

Is it possible to use the Windows Cinder storage as a backend for Glance?

I have tried it out (using Pike) and when creating a new image the basic Cinder volume create/delete/etc function works but the image create ultimately fails inside glancestore.drivers.cinder with a series of similar InvalidConnectorProtocol errors e.g. "Failed to write to volume 14635b29-f3c5-4908-a6be-11bc8ab17d8c.: InvalidConnectorProtocol: Invalid InitiatorConnector protocol specified SMBFS"

This seems to track back into os_brick/initiator/connector.py. It looks like this is a consequence of Glance trying to directly mount the volume on the SMB backend, and with Glance running in a Linux container the SMBFS protocol isn't available to it so it fails.

Is there any workaround for this?

Alternatively what storage method is recommended for Glance on a hyper-converged installation similar to Hyper-C? A file backend using a mount to the SoFS share?