Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Jeremy Stanley
On 2015-04-16 18:28:44 -0400 (-0400), Emilien Macchi wrote: > I'm trying a new hook in jeepyb: https://review.openstack.org/#/c/174627/1 > > This is a PoC, just to see how people reacts about that. [...] I've commented on the change in review too, but you should consider looking at how we set up

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Emilien Macchi
On 04/16/2015 04:27 PM, Mike Dorman wrote: > I feel somewhat responsible for this whole thing, since I landed the first > review that kicked off all this. We had gone to a kilo oslo-messaging for > RMQ improvements, which was what spurred me to patch in order to get rid > of the deprecation w

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Mike Dorman
I feel somewhat responsible for this whole thing, since I landed the first review that kicked off all this. We had gone to a kilo oslo-messaging for RMQ improvements, which was what spurred me to patch in order to get rid of the deprecation warnings. I should have actually validated it against

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Mathieu Gagné
On 2015-04-16 2:10 PM, Richard Raseley wrote: > > I am certainly sympathetic to your situation - having the world change > beneath your feet is never a good place to be. =] > > It does seem, however, that there is a disconnect between your > expectations (as I understand them) of what the 'master'

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Clayton O'Neill
On Thu, Apr 16, 2015 at 2:10 PM, Richard Raseley wrote: > I am certainly sympathetic to your situation - having the world change > beneath your feet is never a good place to be. =] > > It does seem, however, that there is a disconnect between your > expectations (as I understand them) of what the

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Emilien Macchi
On 04/16/2015 02:15 PM, Clayton O'Neill wrote: > On Thu, Apr 16, 2015 at 10:50 AM, Emilien Macchi > wrote: > > We do our best now to backport what is backportable to stable/juno. > > > This certainly has gotten much better, but I don't think it's 100% there > ye

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Clayton O'Neill
On Thu, Apr 16, 2015 at 10:50 AM, Emilien Macchi wrote: > We do our best now to backport what is backportable to stable/juno. > This certainly has gotten much better, but I don't think it's 100% there yet either. It's just a ton of work and we probably need better tooling around this to expect

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Colleen Murphy
On Thu, Apr 16, 2015 at 7:50 AM, Emilien Macchi wrote: > > > On 04/16/2015 12:26 AM, Matt Fischer wrote: > > Recently a mass of changes was proposed and some merged to move the > > rabbit/kombu settings to avoid a Kilo deprecation. As far as I can tell > > this will break rabbit connectivity for

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Richard Raseley
Matt Fischer wrote: Recently a mass of changes was proposed and some merged to move the rabbit/kombu settings to avoid a Kilo deprecation. As far as I can tell this will break rabbit connectivity for all modules still using Juno. I did an experiment with Heat and it certainly can't talk to rabbit

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

2015-04-16 Thread Emilien Macchi
On 04/16/2015 12:26 AM, Matt Fischer wrote: > Recently a mass of changes was proposed and some merged to move the > rabbit/kombu settings to avoid a Kilo deprecation. As far as I can tell > this will break rabbit connectivity for all modules still using Juno. I > did an experiment with Heat and i