New Question

Windows Cinder as Glance backend

asked 2018-04-05 21:05:15 +0300

jwilson23 gravatar image

updated 2018-04-05 21:06:53 +0300

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/ 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?

edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted

answered 2018-04-05 21:37:29 +0300

Claudiu Belu gravatar image


os_brick only supports the Windows SMBFS connector; there are no Linux SMBFS connectors defined, which means that you won't be able to Windows SMB Cinder storage as a backend for Glance. Alternatively, you can use Windows iSCSI Cinder storage.

Best regards,

Claudiu Belu

edit flag offensive delete link more

answered 2018-04-05 22:30:23 +0300

lpetrut gravatar image

updated 2018-04-05 22:38:11 +0300


TL;DR; one workaround would be to "manually" mount the SMB share on your Glance host and configure it using the "file" store.

The os-brick Linux RemoteFS connector does support SMB, it's just that it's advertised as CIFS [1] (mount.cifs can be used for SMB 3 shares). Even if this small mismatch gets fixed and the volume becomes accessible, there would be some other issues:

  • the Cinder SMB driver stores the volumes as VHD/x images, while the Glance "Cinder" store driver can only handle raw disk devices

  • I think there would be some concurrency issues as the Glance "Cinder" store basically mounts the Cinder volumes locally (the Glance host) whenever accessing the images. This would become especially problematic when scaling out the Glance service.

The Glance "Cinder" store isn't considered production ready, so we didn't invest too much time on it. Since you're interested in a hyper-converged setup, I'd recommend the above mentioned approach.

Side note, we're using the Windows iSCSI driver for testing purposes mostly.



Lucian Petrut

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2018-04-05 21:05:15 +0300

Seen: 8 times

Last updated: Apr 05