David, is there any standard way to create the _tmp path? ansible 2.0 and ansible 2.1 have not the same function signature. [0]
[0] https://github.com/openstack/kolla/blob/master/ansible/action_plugins/merge_configs.py#L45,L54 On Wed, Jun 1, 2016 at 9:53 PM, David Shrewsbury <shrewsbury.d...@gmail.com> wrote: > I believe 2.1 was when Toshio introduced the new ziploader, which totally > changed how > the modules were loaded: > > https://github.com/ansible/ansible/pull/15246 > > That broke a few of the 2.x OpenStack modules, too. But that was mostly > our fault as > we didn't code some of them correctly to the proper standards. > > -Dave > > > On Wed, Jun 1, 2016 at 6:10 AM, Jeffrey Zhang <zhang.lei....@gmail.com> > wrote: > >> 1. the ansible 2.1 make lots of change compare to the ansible 2.0 about >> how >> the plugin works. So in default, kolla do not work with ansible 2.1 >> >> 2. the compatible fix is merged here[0]. So the kolla works on both >> ansible 2.1 and ansible 2.0 >> >> [0] https://review.openstack.org/321754 >> >> On Wed, Jun 1, 2016 at 2:46 PM, Monty Taylor <mord...@inaugust.com> >> wrote: >> >>> On 06/01/2016 08:44 AM, Joshua Harlow wrote: >>> > Out of curiosity, what keeps on changing (breaking?) in ansible that >>> > makes it so that something working in 2.0 doesn't work in 2.1? Isn't >>> the >>> > point of minor version numbers like that so that things in the same >>> > major version number still actually work... >>> >>> I'm also curious to know the answer to this. I expect the 2.0 port to >>> have had the possibility of breaking things - I do not expect 2.0 to 2.1 >>> to be similar. Which is not to say you're wrong about it not working, >>> but rather, it would be good to understand what broke so that we can >>> better track it in upstream ansible. >>> >>> > Steven Dake (stdake) wrote: >>> >> Hey folks, >>> >> >>> >> In case you haven't been watching the review queue, Kolla has been >>> >> ported to Ansible 2.0. It does not work with Ansible 2.1, however. >>> >> >>> >> Regards, >>> >> -steve >>> >> >>> >> >>> __________________________________________________________________________ >>> >> >>> >> OpenStack Development Mailing List (not for usage questions) >>> >> Unsubscribe: >>> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> > >>> > >>> __________________________________________________________________________ >>> > OpenStack Development Mailing List (not for usage questions) >>> > Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> > >>> >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> >> -- >> Regards, >> Jeffrey Zhang >> Blog: http://xcodest.me >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > David Shrewsbury (Shrews) > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Regards, Jeffrey Zhang Blog: http://xcodest.me
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
