Can't speak to that concept, but I did try cherry picking the commit into the stable/juno branch of oslo.messaging and there'd definitely be some work to be done there. I fear that could mean havoc for trying to just use master oslo as well, but a good idea to try for sure.
-- Kevin > On Mar 19, 2015, at 1:13 PM, Jesse Keating <j...@bluebox.net> wrote: > > On 3/19/15 10:15 AM, Davanum Srinivas wrote: >> Apologies. i was waiting for one more changeset to merge. >> >> Please try oslo.messaging master branch >> https://github.com/openstack/oslo.messaging/commits/master/ >> >> (you need at least till Change-Id: >> I4b729ed1a6ddad2a0e48102852b2ce7d66423eaa - change id is in the commit >> message) >> >> Please note that these changes are NOT in the kilo branch that has been >> cut already >> https://github.com/openstack/oslo.messaging/commits/stable/kilo >> >> So we need your help with testing to promote it to kilo for you all to >> use it in Kilo :) >> >> Please file reviews or bugs or hop onto #openstack-oslo if you see >> issues etc. >> >> Many thanks to Kris Lindgren to help shake out some issues in his >> environment. > > How bad of an idea would it be to run master of oslo.messaging with juno code > base? Explosions all over the place? > > -- > -jlk > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators