settingsLogin | Registersettings

[Openstack-operators] FYI: Rabbit Heartbeat Patch Landed

0 votes

At the Operator’s midcycle meetup in Philadelphia recently there was a lot of operator interest[1] in the idea behind this patch:

https://review.openstack.org/#/c/146047/

Operators may want to take note that it merged yesterday. Happy testing!

[1] See bottom of https://etherpad.openstack.org/p/PHL-ops-rabbit-queue

At Your Service,

Mark T. Voelker
OpenStack Architect


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
asked Mar 19, 2015 in openstack-operators by Mark_Voelker (4,000 points)   2 3
retagged Mar 19, 2015 by admin

26 Responses

0 votes

I have been working with dism and sileht on testing this patch in one of
our pre-prod environments. There are still issues with rabbitmq behind
haproxy that we are working through. However, in testing if you are using
a list of hosts you should see significantly better catching/fixing of
faults.

If you are using cells with the don¹t forget to also apply:
https://review.openstack.org/#/c/152667/


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.

On 3/19/15, 10:22 AM, "Mark Voelker" mvoelker@vmware.com wrote:

At the Operator¹s midcycle meetup in Philadelphia recently there was a
lot of operator interest[1] in the idea behind this patch:

https://review.openstack.org/#/c/146047/

Operators may want to take note that it merged yesterday. Happy testing!

[1] See bottom of https://etherpad.openstack.org/p/PHL-ops-rabbit-queue

At Your Service,

Mark T. Voelker
OpenStack Architect


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
responded Mar 19, 2015 by Kris_G._Lindgren (7,740 points)   1 5 10
0 votes

schweet. Thanks Mark/Kris/Mehdi.


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 19, 2015 by David_Medberry (8,000 points)   1 4 5
0 votes

Apologies. i was waiting for one more changeset to merge.

Please try oslo.messaging master branch
https://github.com/openstack/oslo.messaging/commits/master/ 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 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.

thanks,
dims

On Mar 19, 2015, at 12:22 PM, Mark Voelker mvoelker@vmware.com wrote:

At the Operator’s midcycle meetup in Philadelphia recently there was a lot of operator interest[1] in the idea behind this patch:

https://review.openstack.org/#/c/146047/

Operators may want to take note that it merged yesterday. Happy testing!

[1] See bottom of https://etherpad.openstack.org/p/PHL-ops-rabbit-queue

At Your Service,

Mark T. Voelker
OpenStack Architect


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
responded Mar 19, 2015 by Davanum_Srinivas (35,920 points)   2 4 8
0 votes

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
responded Mar 19, 2015 by jlk_at_bluebox.net (2,760 points)   2 3
0 votes

I am doing this in test without any issues (aside from the cells patch
that was needed below). Assuming that you can satisfy the new
requirements.


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
(480) 505-8800 X7111
Email: klindgren@godaddy.com

This email message and any attachment(s) hereto are intended for use only
by its intended recipient(s) and may contain confidential information. If
you have received this email in error, please immediately notify the
sender and permanently delete the original and any copy of this message
and its attachments.

On 3/19/15, 1:13 PM, "Jesse Keating" jlk@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
responded Mar 19, 2015 by Kris_G._Lindgren (7,740 points)   1 5 10
0 votes

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@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
responded Mar 19, 2015 by Kevin_Bringard_(kevi (1,500 points)   1 3
0 votes

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@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@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


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 19, 2015 by Matt_Fischer (9,340 points)   1 3 7
0 votes

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@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@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@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


OpenStack-operators mailing list
OpenStack-operators@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@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 19, 2015 by Davanum_Srinivas (35,920 points)   2 4 8
0 votes

Why would anyone want to run rabbit behind haproxy? I get people did it post the ‘rabbit_servers' flag. Allowing the client to detect, handle, and retry is a far better alternative than load balancer health check intervals.

On Thursday, March 19, 2015 at 9:42 AM, Kris G. Lindgren wrote:

I have been working with dism and sileht on testing this patch in one of
our pre-prod environments. There are still issues with rabbitmq behind
haproxy that we are working through. However, in testing if you are using
a list of hosts you should see significantly better catching/fixing of
faults.

If you are using cells with the don¹t forget to also apply:
https://review.openstack.org/#/c/152667/



Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.



On 3/19/15, 10:22 AM, "Mark Voelker" <mvoelker@vmware.com (mailto:mvoelker@vmware.com)> wrote:

At the Operator¹s midcycle meetup in Philadelphia recently there was a
lot of operator interest[1] in the idea behind this patch:

https://review.openstack.org/#/c/146047/

Operators may want to take note that it merged yesterday. Happy testing!


[1] See bottom of https://etherpad.openstack.org/p/PHL-ops-rabbit-queue

At Your Service,

Mark T. Voelker
OpenStack Architect



OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org (mailto:OpenStack-operators@lists.openstack.org)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org (mailto: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
responded Mar 20, 2015 by John_Dewey (1,320 points)   2
0 votes

I tried that once as a test, it was pretty much a major fail. This was
behind an F5 too. Just leaving the hosts in a list works better.

On Thursday, March 19, 2015, John Dewey john@dewey.ws wrote:

Why would anyone want to run rabbit behind haproxy? I get people did it
post the ‘rabbit_servers' flag. Allowing the client to detect, handle, and
retry is a far better alternative than load balancer health check
intervals.

On Thursday, March 19, 2015 at 9:42 AM, Kris G. Lindgren wrote:

I have been working with dism and sileht on testing this patch in one of
our pre-prod environments. There are still issues with rabbitmq behind
haproxy that we are working through. However, in testing if you are using
a list of hosts you should see significantly better catching/fixing of
faults.

If you are using cells with the don¹t forget to also apply:
https://review.openstack.org/#/c/152667/


Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.

On 3/19/15, 10:22 AM, "Mark Voelker" <mvoelker@vmware.com
<javascript:_e(%7B%7D,'cvml','mvoelker@vmware.com');>> wrote:

At the Operator¹s midcycle meetup in Philadelphia recently there was a
lot of operator interest[1] in the idea behind this patch:

https://review.openstack.org/#/c/146047/

Operators may want to take note that it merged yesterday. Happy testing!

[1] See bottom of https://etherpad.openstack.org/p/PHL-ops-rabbit-queue

At Your Service,

Mark T. Voelker
OpenStack Architect


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
<javascript:_e(%7B%7D,'cvml','OpenStack-operators@lists.openstack.org');>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
<javascript:_e(%7B%7D,'cvml','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
responded Mar 20, 2015 by Abel_Lopez (4,820 points)   1 3 5
...