[openstack-dev] [Zaqar] Call for adoption (or exclusion?)

Michael Krotscheck krotscheck at gmail.com
Mon Apr 20 18:22:09 UTC 2015

What's the difference between openstack/zaqar and stackforge/cue? Looking
at the projects, it seems like zaqar is a ground-up implementation of a
queueing system, while cue is a provisioning api for queuing systems that
could include zaqar, but could also include rabbit, zmq, etc...

If my understanding of the projects is correct, the latter is far more
versatile, and more in line with similar openstack approaches like trove.
Is there a use case nuance I'm not aware of that warrants duplicating
efforts? Because if not, one of the two should be retired and development
focused on the other.

Note: I do not have a horse in this race. I just feel it's strange that
we're building a thing that can be provisioned by the other thing.


On Mon, Apr 20, 2015 at 6:00 AM Flavio Percoco <flavio at redhat.com> wrote:

> Greetings,
> I'd like my first action as Zaqar's PTL to be based on reflections and
> transparency with regards to what our past has been, to what our
> present is and to what our future could be as a project and community.
> Therefore, I'm sending this call for adoption and support before
> taking other actions (also mentioned below).
> The summit is very close and the Zaqar team is looking forward to it.
> The upcoming summit represents an important opportunity for Zaqar to
> integrate with other projects. In the previous summits - since
> Icehouse's - we've been collecting feedback from the community. We've
> worked on addressing the many use-cases, we've worked on addressing
> the concerns raised by the community and we've also kept moving
> towards reaching the project's goals.
> As you all know, the project has gone through many ups and downs.
> We've had some "failures" in the past and we've also had successes, as
> a project and as a team. Nevertheless, we've got to the point where it
> doesn't make much sense to keep pushing new features to the project
> until it gains adoption. Therefore, I'd like to take advantage of the
> workshop slots and invite people from other projects to help us/guide
> us through a hacking session on their projects so we can help with the
> adoption. The current adoption of Zaqar consist in:
> - 1 company reachingunning it in production
> - 1 planning to do it soon
> - RDO support
> Unfortunately, the above is certainly not enough for a project to
> succeed and it makes the time and effort spent on the project not
> worth it. It's been more than 2 years since we kicked the project off
> and it's time for it to show some results. The current problem seems
> to be that many people want the project but no one wants to be the
> first in adopting Zaqar (which kind of invalidates the premises of the
> "Big tent").
> In summary, this is a call for adoption before we call it a nice
> adventure and ask for the project to be excluded from the OpenStack
> organization based on the lack of adoption and contributions.
> If you think it's worth it, speak up. Either way, thanks for the
> support and for reading thus far.
> On behalf of the Zaqar team,
> Flavio
> --
> @flaper87
> Flavio Percoco
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150420/e898e533/attachment.html>

More information about the OpenStack-dev mailing list