Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-22 Thread Davanum Srinivas
Thomas, This may be of interest to you as well: http://specs.openstack.org/openstack/openstack-specs/specs/supported-messaging-drivers.html On Mon, Jun 22, 2015 at 12:57 PM, Davanum Srinivas dava...@gmail.com wrote: Thomas, here's a review for qpid https://review.openstack.org/#/c/193804/

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-22 Thread Davanum Srinivas
Thomas, here's a review for qpid https://review.openstack.org/#/c/193804/ -- dims On Mon, Jun 22, 2015 at 12:42 PM, Thomas Goirand z...@debian.org wrote: On 06/16/2015 03:22 PM, Sean Dague wrote: FYI, One of the things that came out of the summit for Devstack plans going forward is to trim

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-22 Thread Thomas Goirand
On 06/16/2015 03:22 PM, Sean Dague wrote: FYI, One of the things that came out of the summit for Devstack plans going forward is to trim it back to something more opinionated and remove a bunch of low use optionality in the process. One of those branches to be trimmed is all the support

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-19 Thread Sean Dague
On 06/19/2015 03:16 PM, Ken Giusti wrote: I've already +1'd this patch - timing issues aside - I think this is a Good Thing from a developer's point of view. Particularly, my own selfish point of view :) I envision the ability to support multiple different messaging services via the amqp1

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-19 Thread Ken Giusti
I've already +1'd this patch - timing issues aside - I think this is a Good Thing from a developer's point of view. Particularly, my own selfish point of view :) I envision the ability to support multiple different messaging services via the amqp1 driver. Having to keep devstack updated with an

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread Sean Dague
On 06/18/2015 06:49 AM, Sean Dague wrote: On 06/18/2015 03:28 AM, ozamiatin wrote: Hi, please don't remove zmq support from devstack. We are now in progress of writing a new version of the driver. I use devstack each time to check the driver functionality. When the implementation become

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread ozamiatin
Hi Sean, Thanks a lot for the plugin! I was a little bit confused with a commit message and dropping of drivers support. It turns really not so hard to test zeromq driver with plugin. So I have no objections any more and removing my -1. But I also agree with Doug Hellmann and other speakers

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread Sean Dague
On 06/18/2015 09:54 AM, ozamiatin wrote: Hi Sean, Thanks a lot for the plugin! I was a little bit confused with a commit message and dropping of drivers support. It turns really not so hard to test zeromq driver with plugin. Yes, that was the design goal with the whole plugin mechanism. To

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread Davanum Srinivas
yay! thanks Sean. -- dims On Thu, Jun 18, 2015 at 9:36 AM, Sean Dague s...@dague.net wrote: On 06/18/2015 06:49 AM, Sean Dague wrote: On 06/18/2015 03:28 AM, ozamiatin wrote: Hi, please don't remove zmq support from devstack. We are now in progress of writing a new version of the driver. I

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread Clint Byrum
Excerpts from Sean Dague's message of 2015-06-18 07:09:56 -0700: On 06/18/2015 09:54 AM, ozamiatin wrote: Hi Sean, Thanks a lot for the plugin! I was a little bit confused with a commit message and dropping of drivers support. It turns really not so hard to test zeromq driver with

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread ozamiatin
Hi, please don't remove zmq support from devstack. We are now in progress of writing a new version of the driver. I use devstack each time to check the driver functionality. When the implementation become public it will be even more important to have a possibility to check it on devstack.

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread Flavio Percoco
On 17/06/15 15:08 -0400, Doug Hellmann wrote: Excerpts from Sean Dague's message of 2015-06-17 14:07:35 -0400: On 06/17/2015 01:29 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 10:16:34 -0700: On 06/16/2015 12:49 PM, Clint Byrum wrote: Excerpts from Sean Dague's

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-18 Thread Sean Dague
On 06/18/2015 03:28 AM, ozamiatin wrote: Hi, please don't remove zmq support from devstack. We are now in progress of writing a new version of the driver. I use devstack each time to check the driver functionality. When the implementation become public it will be even more important to have a

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Sean Dague
On 06/17/2015 01:29 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 10:16:34 -0700: On 06/16/2015 12:49 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: FYI, One of the things that came out of the summit for Devstack plans going

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Dan Smith
Every change like this makes it harder for newcomers to participate. Frankly, it makes it harder for everyone because it means there are more moving parts, but in this specific case many of the people involved in these messaging drivers are relatively new, so I point that out. I dunno about

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Kyle Mestery
On Wed, Jun 17, 2015 at 2:44 PM, Sean Dague s...@dague.net wrote: On 06/17/2015 03:08 PM, Doug Hellmann wrote: Excerpts from Sean Dague's message of 2015-06-17 14:07:35 -0400: On 06/17/2015 01:29 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 10:16:34 -0700: On

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Sean Dague
On 06/17/2015 03:08 PM, Doug Hellmann wrote: Excerpts from Sean Dague's message of 2015-06-17 14:07:35 -0400: On 06/17/2015 01:29 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 10:16:34 -0700: On 06/16/2015 12:49 PM, Clint Byrum wrote: Excerpts from Sean Dague's

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Clint Byrum
Excerpts from Kyle Mestery's message of 2015-06-17 13:54:06 -0700: On Wed, Jun 17, 2015 at 3:48 PM, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Dan Smith's message of 2015-06-17 13:16:46 -0700: Every change like this makes it harder for newcomers to participate. Frankly,

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Doug Hellmann
Excerpts from Sean Dague's message of 2015-06-17 14:07:35 -0400: On 06/17/2015 01:29 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 10:16:34 -0700: On 06/16/2015 12:49 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: FYI,

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Clint Byrum
Excerpts from Sean Dague's message of 2015-06-16 10:16:34 -0700: On 06/16/2015 12:49 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: FYI, One of the things that came out of the summit for Devstack plans going forward is to trim it back to

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Doug Hellmann
Excerpts from Dan Smith's message of 2015-06-17 13:16:46 -0700: Every change like this makes it harder for newcomers to participate. Frankly, it makes it harder for everyone because it means there are more moving parts, but in this specific case many of the people involved in these

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-17 Thread Kyle Mestery
On Wed, Jun 17, 2015 at 3:48 PM, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Dan Smith's message of 2015-06-17 13:16:46 -0700: Every change like this makes it harder for newcomers to participate. Frankly, it makes it harder for everyone because it means there are more

[openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Sean Dague
FYI, One of the things that came out of the summit for Devstack plans going forward is to trim it back to something more opinionated and remove a bunch of low use optionality in the process. One of those branches to be trimmed is all the support for things beyond RabbitMQ in the rpc layer.

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Davanum Srinivas
+1 Sean. -- dims On Tue, Jun 16, 2015 at 9:22 AM, Sean Dague s...@dague.net wrote: FYI, One of the things that came out of the summit for Devstack plans going forward is to trim it back to something more opinionated and remove a bunch of low use optionality in the process. One of those

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Sean Dague
On 06/16/2015 12:49 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: FYI, One of the things that came out of the summit for Devstack plans going forward is to trim it back to something more opinionated and remove a bunch of low use optionality in the

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

2015-06-16 Thread Clint Byrum
Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: FYI, One of the things that came out of the summit for Devstack plans going forward is to trim it back to something more opinionated and remove a bunch of low use optionality in the process. One of those branches to be