shortcuts for OpenStack operations

27 views
Skip to first unread message

Dmitry Makovey

unread,
Jul 23, 2014, 8:40:02 PM7/23/14
to ansible...@googlegroups.com
I have finally gottent my first OpenStack "node creation" playbook which in fact turned out rather nice, once I looked at source code ;)

I have found out that names used in OpenStack component creation routines from ansible will be considered "unique" and ansible will happily provide me with needed "id" for the component (like tenant_id, image_id, etc.), see https://github.com/droopy4096/openstack-ng/blob/multinode/sample.yml 

however I found it rather unpleasant to repeat all of the authentication tokens with every OpenStack call. Looking at source code it doesn't seem like it's possible to bypass this "feature" by setting up ENV vars according to OpenStack tradition. 

Question: what could be done to optimize such a playbook? Or, conversely: what am I missing?

Michael DeHaan

unread,
Jul 24, 2014, 7:02:59 AM7/24/14
to ansible...@googlegroups.com

Common auth functions for things like ec2 live here - https://github.com/ansible/ansible/tree/devel/lib/ansible/module_utils

OpenStack really needs stubs here for common auth, and then it can take variables like EC2/RAX/GCE and others.

This would also make sure all that happens in one place.

Contributions would be welcome!  Stop by ansible-devel list if you'd like to discuss!



--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/4fafafc2-9404-4f31-9bc3-b49fe7741464%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages