Open Stack

On Fri, Apr 24, 2015 at 4:35 PM, Fox, Kevin M <Kevin.Fox at pnnl.gov> wrote:

>  Notification might be a good way to integrate with nova. Individual
> tenants might want to do things as vm's come up/down, etc. Right now, you
> need a privileged pipe into rabbit. Forwarding them to Zaqar, per tenant
> queue's could solve the problem.
>
>
Right now you can poll the nova API. Or tenants can use any number of
monitoring tools.  How does zaqar better then the alternatives?


FWIW, I think there are some really neat use cases for amazon SQS, that
presumably Zaqar would fit as well. Cases such as
https://aws.amazon.com/articles/1464



> Thanks,
> Kevin
>  ------------------------------
> *From:* Joe Gordon [joe.gordon0 at gmail.com]
> *Sent:* Friday, April 24, 2015 4:02 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)
>
>
>
> On Mon, Apr 20, 2015 at 5:54 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
>>
>
>  I get integration with Horizon etc. But to use the SQS/SNS analogy how
> would say Nova integrate with Zaqar?
>
>
>> 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
>>
>>
>
> __________________________________________________________________________
> 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/20150424/f713151d/attachment.html>