Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules

2015-07-07 Thread Sam Yaple
Steve, We will need some of the modules from the merge-it-all branch of emoty's fork[1]. If it is more convient, you can just grab them all. The ones we require to proceed without triggering Option #4 would be the keystone related modules. That list is as follows: os_auth.py

[openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules

2015-07-03 Thread Steven Dake (stdake)
Kolla Devs as well as the Technical Committee, I wanted to get the TC’s thoughts on this plan of action as we intend to apply for big tent once our Ansible code has completed implementation. If the approach outlined in this email seems like a blocker and we should just start with #4 instead,

Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules

2015-07-03 Thread Fox, Kevin M
. That might be ok, but something to carefully consider. Thanks, Kevin From: Steven Dake (stdake) Sent: Friday, July 03, 2015 11:53:00 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Greg DeKoenigsberg Subject: [openstack-dev] [kolla][tc] Plans

Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules

2015-07-03 Thread Steven Dake (stdake)
(not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Cc: Greg DeKoenigsberg g...@ansible.commailto:g...@ansible.com Subject: Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules Please consider forwarding this to the legal list. The gpl