Comment 6 for bug 715831

I thought that at some point we were going to switch to Celery. Wouldn't this move solve this issue altogether?

> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
> Christian Berendt
> Sent: 09 February 2011 20:59
> To: Armando Migliaccio
> Subject: [Bug 715831] Re: rename gflag --rabbit_host
>
> Even if we are dependent on RabbitMQ at the moment, I think this is not
> the case in the next months. And if we're dependent on RabbitMQ we
> should think about how to remove this dependency, or not?
>
> I thought carrot only supports AMQP. I think it's a good idea to use the
> options defined in carrot.connection.
>
> --
> You received this bug notification because you are 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...
>