Cinder-Volume on Windows Storage Server 2012

Post 9 of 16

Windows Server 2012 and Windows Storage Server 2012 offer an integrated iSCSI Target service that can be used with Cinder Volume in your stack. Being entirely a software solution, consider it in particular for mid sized networks where the costs of a SAN might be excessive.

One of the great advantages of integrating Windows solutions in the OpenStack ecosystem is the ease of management and deployment. Cinder is no exception as you will see right away.

All you need to start is a physical or virtual host running Windows Server 2012 or Windows Storage Server 2012 and a copy of our Cinder volume installer available for free here.

Here’s our welcome screen:

 

Once you get through the license and the folder selection screens, you will be asked for the cinder.conf options as in the following screenshot. The great advantage is that the installer will create all the configuration files for you, without having to look around for obscure options by yourself :-)

 

The Windows iSCSI LUNs path is the folder where the Microsoft iSCSI Target Service will create a VHD for each volume, so it is best to choose an appropriate data partition if available.

The next step consist in providing the optional logging options:

That’s it! One last confirmation screen and the setup will start. Another great advantage of this setup is that it will take care of all the dependencies, including Python, the iSCSI Target Service, the cinder-volume Windows service and so on.

 

Once the setup is finished, the cinder-volume service will start and you can check the logs (in the path configured above) to see if the service is properly connected to your controller.

You can restart the service from the Windows Service GUI tool or via command line with:

To test your new volume server, you can connect to your OpenStack controller and create a simple volume:

This command creates a 1GB volume. You can now check the status of your new volume:

The Windows Cinder Volume driver works perfectly well with Nova on any Hypervisor, including support for the boot from volume feature. Great kudos go to Pedro Navarro Pérez who contributed the Windows volume driver to the Cinder project!
 

, , , , ,

This article was written by apilotti

8 comments:

Emilien MacchiDecember 13, 2012 at 01:04Reply

Great job guys :-)

OpenStack Community Weekly Newsletter (Nov 30 – Dic 14) » The OpenStack BlogDecember 15, 2012 at 01:25Reply

[...] By Alessandro Pilotti: Cinder-Volume on Windows Storage Server 2012 [...]

Dan WykeSeptember 17, 2013 at 18:54Reply

I need something cleared up. Where do I find the RabbitMQ password. I was never prompted to create a password during setup. Is this even necessary?

Alessandro PilottiSeptember 17, 2013 at 18:58Reply

Look in the cinder configuration on your controller, for example:

grep rabbit_password /etc/cinder/cinder.conf

The default is “guest”.

Note: RDO uses AMQP instead of RabbitMQ.

DanSeptember 30, 2013 at 23:14Reply

I need some help. I keep getting the error “There is a problem with this windows installer package. A script required for this install to complete could not be run….” What’s the deal here?

Alessandro PilottiOctober 30, 2013 at 07:24Reply

Can you please write version of Windows are you using?

HabibJanuary 29, 2014 at 06:04Reply

Can I use this on RDO which use AMQP? So do I need to specify my AMQP password replacing RabbitMQ?

Alessandro PilottiFebruary 6, 2014 at 15:34Reply

Sure, AMQP is the protocol (used also by Rabbit-MQ), while Apache Qpid is the service available by default on CentOS using RDO. Just replace in cinder.conf the rabbit-mq configuration options with the corresponding qpid ones:

qpid_hostname=, qpid_port=5672, qpid_username=, qpid_password=

Menu