<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 2, 2013 at 10:12 PM, Jarret Raim <span dir="ltr"><<a href="mailto:jarret.raim@rackspace.com" target="_blank">jarret.raim@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">> There are two big parts to this, I think. One is techincal - a significant<br>
> portion<br>
> of OpenStack deployments will not work with this because Celery does not<br>
> work with their deployed messaging architecture.<br>
> See another reply in this thread for an example of someone that sees the<br>
> inability to use Qpid as a roadblock for an example. This is solvable, but<br>
> not<br>
> quickly.<br>
><br>
> The other is somewhat technical, but also a community issue. Monty<br>
> articulated this well in another reply. Barbican has made a conflicting<br>
> library<br>
> choice with what every other project using messaging is using.<br>
> With the number of projects we have, it is in our best interest to strive<br>
> for<br>
> consistency where we can. Differences should not be arbitrary. The<br>
> differences should only be where an exception is well justified. I don't<br>
> see<br>
> that as being the case here. Should everyone using oslo.messaging (or its<br>
> predecessor rpc in oslo-incubator) be using Celery? Maybe. I don't know,<br>
> but that's the question at hand. Ideally this would have come up with a<br>
> more<br>
> broad audience sooner. If it did, I'm sorry I missed it.<br>
<br>
</div>I understand the concern here and I'm happy to have Barbican look at using<br>
oslo.messaging during the Icehouse cycle.<br>
<br>
I am a bit surprised at the somewhat strong reactions to our choice. When we<br>
created Barbican, we looked at the messaging frameworks out there for use. At<br>
the time, oslo.messaging was not packaged, not documented, not tested, had no<br>
track record and an unknown level of community support.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">The API and developer documentation is at <a href="http://docs.openstack.org/developer/oslo.messaging/">http://docs.openstack.org/developer/oslo.messaging/</a></div>
<br></div><div><div class="gmail_default" style="font-size:small">Doug</div><div class="gmail_default" style="font-size:small"></div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Celery is a battle-tested library that is widely deployed with a good track<br>
record, strong community and decent documentation. We made our choice based on<br>
those factors, just as the same as we would for any library inclusion.<br>
<br>
As celery has met our needs up to this point, we saw no reason to revisit the<br>
decision until now. In that time oslo.messaging has moved to a separate repo.<br>
It still has little to no documentation, but the packaging and maintenance<br>
issues seem to be on the way to being sorted.<br>
<br>
So in short, in celery we get a reliable library with good docs that is battle<br>
tested, but is limited to the transports supported by Kombu. Both celery and<br>
Kombu are extendable and have many backends including AMQP, Redis, Beanstalk,<br>
Amazon SQS, CouchDB, MongoDB, ZeroMQ, ZooKeeper, SoftLayer MQ and Pyro.<br>
<br>
Oslo.messaging seems to have good support in OpenStack, but still lacks<br>
documentation and packaging (though some of that is being sorted out now). It<br>
offers support for qpid which celery seems to lack. It also offers a common<br>
place for message signing and some other nice to have features for OpenStack.<br>
<br>
Based on the commonality in OpenStack (and the lack of anyone else using<br>
Celery), I think looking to move to oslo.messaging is a good goal. This will<br>
take some time, but I think doing it by Icehouse seems reasonable. I think<br>
that is what you and Monty are asking for?<br>
<br>
I have added the task to our list on<br>
<a href="https://wiki.openstack.org/wiki/Barbican/Incubation" target="_blank">https://wiki.openstack.org/wiki/Barbican/Incubation</a>.<br>
<br>
<br>
Thanks again for all the eyeballs our on application.<br>
<span class=""><font color="#888888"><br>
<br>
Jarret<br>
<br>
</font></span><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>