[Openstack-operators] FYI: Rabbit Heartbeat Patch Landed
Sam Morrison
sorrison at gmail.com
Mon May 4 01:55:13 UTC 2015
> On 4 May 2015, at 11:49 am, Davanum Srinivas <davanum at gmail.com> wrote:
>
> Sam,
>
> 1. Weird, did you pick it up from ubuntu cloud archive? we could raise
> a bug against them
I’m basically upgrading the oslo packages from juno cloud archive to the packages in vivid. So maybe will work if upgrading to kilo cloud archive packages.
> 2. yes, not much we can do about that now i guess.
> 3. yes, Can you please log a bug for this?
Actually this has just fixed itself so I’m trying to figure out what is going on here. Looks fine now.
Sam
>
> Thanks!
>
> On Sun, May 3, 2015 at 9:45 PM, Sam Morrison <sorrison at gmail.com> wrote:
>> I’ve found a couple of issues with this:
>>
>> 1. Upgrading the packages in ubuntu doesn’t seem to work, you need to remove them all then install fresh. Some conflicts with file paths etc.
>> 2. With juno heat the requirements.txt has upper limits on the versions for oslo deps. I just removed these and it seems to work fine.
>> 3. When using amqp_durable_queues it will no longer declare the exchanges with this argument set so this will give errors when declaring the exchange. (I think this is a bug, at least an upgrade bug as this will affect people moving juno -> kilo)
>>
>>
>>
>>
>>> On 4 May 2015, at 9:08 am, Sam Morrison <sorrison at gmail.com> wrote:
>>>
>>> We’re running:
>>>
>>> kombu: 3.0.7
>>> amqp: 1.4.5
>>> rabbitmq, 3.3.5
>>> erlang: R14B04
>>>
>>>
>>>> On 2 May 2015, at 1:51 am, Kris G. Lindgren <klindgren at godaddy.com> wrote:
>>>>
>>>> We are running:
>>>> kombu 3.0.24
>>>> amqp 1.4.6
>>>> rabbitmq 3.4.0
>>>> erlang R16B-03.10
>>>> ____________________________________________
>>>>
>>>> Kris Lindgren
>>>> Senior Linux Systems Engineer
>>>> GoDaddy, LLC.
>>>>
>>>>
>>>>
>>>> On 5/1/15, 9:41 AM, "Davanum Srinivas" <davanum at gmail.com> wrote:
>>>>
>>>>> may i request folks post the versions of rabbitmq and pip versions of
>>>>> kombu and amqp libraries?
>>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On Fri, May 1, 2015 at 11:29 AM, Mike Dorman <mdorman at godaddy.com> wrote:
>>>>>> We¹ve been running the new oslo.messaging under Juno for about the last
>>>>>> month, and we¹ve seen success with it, too.
>>>>>>
>>>>>> From: Sam Morrison
>>>>>> Date: Thursday, April 30, 2015 at 11:02 PM
>>>>>> To: David Medberry
>>>>>> Cc: OpenStack Operators
>>>>>> Subject: Re: [Openstack-operators] FYI: Rabbit Heartbeat Patch Landed
>>>>>>
>>>>>> Great, let me know how you get on.
>>>>>>
>>>>>>
>>>>>> On 1 May 2015, at 12:21 pm, David Medberry <openstack at medberry.net>
>>>>>> wrote:
>>>>>>
>>>>>> Great news Sam. I'll pull those packages into my Juno devel environment
>>>>>> and
>>>>>> see if it makes any difference.
>>>>>> Much appreciated for the rebuilds/links.
>>>>>>
>>>>>> Also, good to connect with you at ... Connect AU.
>>>>>>
>>>>>> On Thu, Apr 30, 2015 at 7:30 PM, Sam Morrison <sorrison at gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> I managed to get a juno environment with oslo.messaging 1.8.1 working
>>>>>>> in
>>>>>>> ubuntu 14.04
>>>>>>>
>>>>>>> I have a debian repo with all the required dependancies at:
>>>>>>>
>>>>>>> deb http://download.rc.nectar.org.au/nectar-ubuntu
>>>>>>> trusty-juno-testing-oslo main
>>>>>>>
>>>>>>> All it includes is ubuntu official packages from vivid.
>>>>>>>
>>>>>>> Have installed in our test environment and all looking good so far
>>>>>>> although haven¹t done much testing yet.
>>>>>>>
>>>>>>> Sam
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 21 Mar 2015, at 2:35 am, David Medberry <openstack at medberry.net>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Sam,
>>>>>>>
>>>>>>> I started down the same path yesterday. If I have any success today,
>>>>>>> I'll
>>>>>>> post to this list.
>>>>>>>
>>>>>>> I'm also going to reach out to the Ubuntu Server (aka Cloud) team and
>>>>>>> so
>>>>>>> if they can throw up a PPA with this for Juno quickly (which they will
>>>>>>> likely NOT do but it doesn't hurt to ask.) We need to get the
>>>>>>> stable/juno
>>>>>>> team on board with this backport/regression.
>>>>>>>
>>>>>>> On Fri, Mar 20, 2015 at 4:14 AM, Sam Morrison <sorrison at gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> 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 <davanum at gmail.com>
>>>>>>>> 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 <matt at mattfischer.com>
>>>>>>>>> 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)
>>>>>>>>>> <kevinbri at cisco.com> 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 <jlk at 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 at lists.openstack.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> OpenStack-operators mailing list
>>>>>>>>>>> OpenStack-operators at lists.openstack.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> OpenStack-operators mailing list
>>>>>>>>>> OpenStack-operators at lists.openstack.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Davanum Srinivas :: https://twitter.com/dims
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> OpenStack-operators mailing list
>>>>>>>>> OpenStack-operators at lists.openstack.org
>>>>>>>>>
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> OpenStack-operators mailing list
>>>>>>>> OpenStack-operators at lists.openstack.org
>>>>>>>>
>>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> OpenStack-operators mailing list
>>>>>> OpenStack-operators at lists.openstack.org
>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Davanum Srinivas :: https://twitter.com/dims
>>>>>
>>>>> _______________________________________________
>>>>> OpenStack-operators mailing list
>>>>> OpenStack-operators at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>>
>>>>
>>>> _______________________________________________
>>>> OpenStack-operators mailing list
>>>> OpenStack-operators at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
More information about the OpenStack-operators
mailing list