# OpenStack provision of a new instance, with the user’s persistent storage attached

**URL:** <https://forum.ansible.com/t/openstack-provision-of-a-new-instance-with-the-user-s-persistent-storage-attached/19636>\
**Category:** Ansible Project\
**Created:** [October 27, 2015, 6:48pm UTC](https://forum.ansible.com/t/openstack-provision-of-a-new-instance-with-the-user-s-persistent-storage-attached/19636 "2015-10-27T18:48:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Natan\_Franghieru](https://avatars.discourse-cdn.com/v4/letter/n/ecae2f/32.png) [@Natan\_Franghieru](https://forum.ansible.com/u/Natan_Franghieru)\
**Post date:** [October 27, 2015, 6:48pm UTC](https://forum.ansible.com/t/openstack-provision-of-a-new-instance-with-the-user-s-persistent-storage-attached/19636/1 "2015-10-27T18:48:30Z")

</div>

[![](https://syncomm.files.wordpress.com/2014/05/openstack-vdi.png)](https://syncomm.files.wordpress.com/2014/05/openstack-vdi.png)

Hello everyone!

I’m using OpenStack Kilo in a VDI project, my main difficult is to attach a user’s persistent storage to the instance.

It’s basically the flow that is exemplified on the image:

The user requests a VDI instance. Ansible communicates with OpenStack to provision a new win7 instance, and attach the user’s persistent storage. The user then accesses the desktop through RDP, VNC, or SPICE. When they are finished, they log off and the instance is **destroyed**. The user’s data, living in a cinder volume, will be reattached on the next session to a new _fresh_ image. The user gets a brand new instance, and known “perfect state” every time they log in.

Did someone already so that? Or something like this?

Thank you for the help!