openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #00828
Re: Queue Service, next steps
On Fri, Feb 18, 2011 at 6:23 PM, Eric Day <eday@xxxxxxxxxxxx> wrote:
> Perhaps I've been assuming some things, but I thought everyone
> understood that is what we are looking to build (fault-tolerant,
> horizontally scalable, ...). We're certainly not looking to build
> a clustered queue (like RabbitMQ) with a REST API. I know the wiki
> page is still brief, but I hope that's one of the key take-aways:
Sorry, I guess I was confused by some of the discussion, and then I
didn't really see the sort of distributed architecture I expected on
the wiki. Like, how or whether a single queue will scale or how the
system is highly available, how ordered delivery is reconciled with
those two, etc.
Maybe this is all worked out offline, or it's TBD and the current spec
is more of an ideal. But it seems like people want to start banging
out code before any of that's on paper.
-- Mike
Follow ups
References
-
Re: Queue Service, next steps
From: ksankar, 2011-02-18
-
Re: Queue Service, next steps
From: Eric Day, 2011-02-18
-
Re: Queue Service, next steps
From: Schwartz, Philip Marc (LNG-BCT), 2011-02-18
-
Re: Queue Service, next steps
From: Curtis Carter, 2011-02-18
-
Re: Queue Service, next steps
From: Eric Day, 2011-02-18
-
Re: Queue Service, next steps
From: Michael Barton, 2011-02-19
-
Re: Queue Service, next steps
From: Eric Day, 2011-02-19