I’ve been trying to build a ubuntu deb of this in a juno environment. It’s a bit of a nightmare as they have changed all the module names from oslo.XXX to oslo_XXX
Have fixed those up with a few sed replaces and had to remove support for aioeventlet as the dependencies aren’t in the ubuntu cloud archive juno. Still have a couple of tests failing but I think it *should* work in on our juno hosts. I have a branch of the 1.8.0 release that I’m trying to build against Juno here [1] and I’m hoping that it will be easy to integrate the heartbeat code. I’m sure there is lots of people that would be keen to get a latest version of oslo.messaging working against a juno environment. What is the best way to make that happen though? Cheers, Sam [1] https://github.com/NeCTAR-RC/oslo.messaging/commits/nectar/1.8.0 > On 20 Mar 2015, at 8:59 am, Davanum Srinivas <[email protected]> wrote: > > So, talking about experiments, here's one: > https://review.openstack.org/#/c/165981/ > > Trying to run oslo.messaging trunk against stable/juno of the rest of > the components. > > -- dims > > On Thu, Mar 19, 2015 at 5:10 PM, Matt Fischer <[email protected]> wrote: >> I think everyone is highly interested in running this change or a newer OSLO >> messaging in general + this change in Juno rather than waiting for Kilo. >> Hopefully everyone could provide updates as they do experiments. >> >> >> On Thu, Mar 19, 2015 at 1:22 PM, Kevin Bringard (kevinbri) >> <[email protected]> wrote: >>> >>> 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 <[email protected]> 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 >>>> [email protected] >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >>> _______________________________________________ >>> OpenStack-operators mailing list >>> [email protected] >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > > > > -- > Davanum Srinivas :: https://twitter.com/dims > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
