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 -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/bf0a7096-3791-4f36-977b-f77020d1de43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
