# module keystone\_user deprecation

**URL:** <https://forum.ansible.com/t/module-keystone-user-deprecation/20454>\
**Category:** Ansible Project\
**Created:** [February 4, 2016, 3:56pm UTC](https://forum.ansible.com/t/module-keystone-user-deprecation/20454 "2016-02-04T15:56:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeff\_Dexter](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@Jeff\_Dexter](https://forum.ansible.com/u/Jeff_Dexter)\
**Post date:** [February 4, 2016, 3:56pm UTC](https://forum.ansible.com/t/module-keystone-user-deprecation/20454/1 "2016-02-04T15:56:26Z")

</div>

We have recently worked to move our playbooks to using Ansible v2.

Currently we are using keystone\_user for doing a lot of the administrative tasks associated with configuring keystone.  
creating tenants,  
creating user  
creating roles

This has worked well in the past, however with the move to Ansible v2, we not get:

[DEPRECATION WARNING]: keystone\_user is kept for backwards compatibility but usage is discouraged. The module documentation details page may explain more about this rationale…  
This feature will be removed in a future release. Deprecation warnings can be disabled by setting deprecation\_warnings=False in ansible.cfg.

The issue with going to os\_user and os\_project, is there (AFAIK) no way to assign a role within the projects.

If someone knows a way to get around this I would be greatly appreciated.

- Jeff