Hi, > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Monday, October 31, 2011 1:09 PM > To: [email protected] > Cc: [email protected]; [email protected] > Subject: Re: [Meego-distribution-tools] ruote-amqp-pyclient crashes > when declaring exchange > > On 10/31/2011 12:39 PM, ext Ed Bartosh wrote: > > Hi, > > > > Thank you for the good news, Islam. > > > > What about second one? If I didn't convince David to apply it I can > change it. However, I need some feedback on that, not just several > weeks of silence. > > > > Thanks, > > > >> -----Original Message----- > >> From: [email protected] [mailto:[email protected]] > >> Sent: Friday, October 28, 2011 4:27 PM > >> To: [email protected] > >> Cc: [email protected]; [email protected] > >> Subject: Re: [Meego-distribution-tools] ruote-amqp-pyclient crashes > >> when declaring exchange > >> > >> Hello, > >> > >> The first part (allowing usage with rabbitamqp > 2.2) just got > merged > >> to master branch. > > > > > > Regards, > > Ed > > > > > > Hello, > > Apologies, we are in a bit of disarray. > No prob. Just wanted to make sure my merge request was not forgotten.
> The second patch to me (and David agrees AFAIR) looks like it would be > helpful in enabling a certain use case we were looking into. > > Currently there's a one to one constraint between BOSS and OBS. We > would like to have multiple BOSSes listening to one OBS. This can be > kludged by publishing the same message in boss-obs-plugin to multiple > AMQP servers. > > However the elegant way would be to publish to a fanout exchange and > then that distributes the message to anyone listening. > > Maybe your patch can be used for that ? > It can be used partly, I'd say. >From my point of view we should first think about decoupling ruote from obs >plugin. OBS plugin should just send messages with some routing key to topic >exchange. Message should not contain any ruote-specific info. It should >contain only the information about obs event itself. All routing and >multiplexing of messages should be done according to AMQP principles. For >example if you have two boss instances and one exchange and you want messages >from obs plugin going to both of them then you just create 2 queues and bind >them to the topic exchange with the same routing key. Using topic exchange is >more flexible then fanout exchange, I believe. Fanout exchange behaviour can >be easily implemented using topic exchange, but not the other way around. For >example you can't implement complex routing based on hierarchical routing keys >in fanout exchange. Decoupling ruote from obs plugin would allow us to use any workflow engine we want or no engine at all. It also makes sense to modify obs plugin multiple AMQP servers. Something similar has been done already in meego-boss project: https://gitorious.org/meego-boss/boss/commit/e2e20b95183a594ff1a1e810f58d74b83660149e PS: If this doesn't sound too bad for you I can sketch out some prototype, but first we should agree about overall direction. Regards, Ed _______________________________________________ MeeGo-distribution-tools mailing list [email protected] http://lists.meego.com/listinfo/meego-distribution-tools
