Revision history [back]

Hi,

You can deploy Cinder on one of the SOFS nodes.

Cinder itself has a notion of clusters, supporting Active-Active deployments, but this is a new work-in-progress feature, which we do not support at the moment.

We encourage configuring the Cinder service as a Windows clustered service. This means that in case of a failure, the service will be automatically moved to a different node within the cluster. We recommend configuring the Cinder service to use the cluster name as a hostname, when reporting back to the scheduler in order to remain consistent after a service failover.

We're working on updating the documentation (which at the moment is quite out of date), emphasizing this scenario.

Lucian

Hi,

You can deploy Cinder on one of the SOFS nodes.

Cinder itself has a notion of clusters, supporting Active-Active deployments, but this is a new work-in-progress feature, which we do not support at the moment.

We encourage configuring the Cinder service as a Windows clustered service. This means that in case of a failure, the service will be automatically moved to a different node within the cluster. We recommend configuring the Cinder service to use the cluster name as a hostname, when reporting back to the scheduler in order to remain consistent after a service failover.

We're working on updating the documentation (which at the moment is quite out of date), emphasizing this scenario.

Edit: Updated docs:

https://docs.openstack.org/cinder/latest/install/cinder-storage-install-windows.html https://docs.openstack.org/cinder/latest/configuration/block-storage/drivers/windows-smb-volume-driver.html#windows-smb-volume-driver http://compute-hyperv.readthedocs.io/en/latest/

Lucian