New Question

# Ocata or any version with S2D

Are there any experience how to work the Ocata or any version of OpenStack with HyperV Storage Spaces Direct -S2D? Tried this site link but seems still doesn't work as by default, the background of HyperV is using the integrated iSCSI Target service which is not case in my configuration and not enable as we doing the HyperV fail-over cluster as using the S2D instead.

Any configurations in the controller? thats need to be alter in glance or in cinder (using volume bootable). Any inputs/insights are highly appreciated.

Got these errors: 11:49.246 6180 ERROR cinder.volume.drivers.remotefs ] ... Share \hyper-v\c$\ClusterStorage\Volume1\OpenStack\ ignored due to invalid format. Must be of form address:/export. i tried to change but still got this... 2017-08-25 14:38:32.838 7836 ERROR cinder.volume.drivers.remotefs [req-ecbced46-59f8-4c77-827e-aae731a4b871 - - - - -] Exception during mounting Could not find the local share path for c:\ClusterStorage\Volume1\OpenStack. Thanks. edit retag close merge delete ## 1 answer Sort by » oldest newest most voted Hi, Recent Cinder MSIs (ocata included) allow you to deploy Cinder Volume using the SMB driver, which will work out of the box if configured correctly, without any changes on the controller side. The Cinder SMB driver expects the passed shares to have the following form: //shareaddress/sharename. The MSI will translate the backslashes to slashes for you. Also, administrative shares, such as \hostaddr\c$\path should not be used, nor should local paths, such as c:\path\to\volumes.

Since you're using S2D, I suggest configuring a scale-out file server role (SOFS) [1]. Having such a role configured, you can then share a subfolder residing on the CSV you want to use for storing volume images. The resulted share should then be passed to cinder (either via the msi or the smb share list file). Note that you should use the SOFS name as share address instead of a certain hostname or ip.

As a further note, Nova and Cinder will "resolve" the share addresses, using the CSV path directly, if part of the failover cluster. Nodes outside the cluster may still be able to access the volumes using the SOFS share address.

Please let me know if you have further questions.

Regards, Lucian Petrut

more