Comment 4 for bug 715831

We need to first answer the question: are we dependent on RabbitMQ and
are just using carrot as the API? Or are we dependent on carrot and
just using RabbitMQ as the backend? If the latter, I agree our queue
options should mirror the options defined in the 'carrot.connection'
documentation.

We shouldn't use 'amqp_*' prefix though since not all carrot backends
are AMQP based.

-Eric

On Wed, Feb 09, 2011 at 03:21:05PM -0000, Christian Berendt wrote:
> Public bug reported:
>
> Because OpenStack uses the python library carrot to support the AMQP
> messaging it should also be possible to use an other queuing system than
> RabbitMQ.
>
> ---snip---
> Several AMQP message broker implementations exists, including RabbitMQ, ZeroMQ and Apache ActiveMQ. You’ll need to have one of these installed, personally we’ve been using RabbitMQ.
> ---snap---
>
> I find it a little bit confusing to use a flag "--rabbit_host" for
> defining the used queuing server and I would prefer something like "--
> amqp_host" or "--amqp_server". Feel free...
>
> ** Affects: nova
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Nova Bug
> Team, which is subscribed to OpenStack Compute (nova).
> https://bugs.launchpad.net/bugs/715831
>
> Title:
> rename gflag --rabbit_host
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> Because OpenStack uses the python library carrot to support the AMQP
> messaging it should also be possible to use an other queuing system
> than RabbitMQ.
>
> ---snip---
> Several AMQP message broker implementations exists, including RabbitMQ, ZeroMQ and Apache ActiveMQ. You’ll need to have one of these installed, personally we’ve been using RabbitMQ.
> ---snap---
>
> I find it a little bit confusing to use a flag "--rabbit_host" for
> defining the used queuing server and I would prefer something like "--
> amqp_host" or "--amqp_server". Feel free...
>