On 24/04/15 20:00, Joe Gordon wrote:
On Fri, Apr 24, 2015 at 4:35 PM, Fox, Kevin M <kevin....@pnnl.gov
<mailto:kevin....@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?
So, a couple of points about that:
1) Polling sucks.
2) If a bunch of things are going to get polled, at least collect them
together so there is *one* thing to optimise for massive polling load.
(Zaqar is this thing - you have to poll it too atm.)
3) Long-polling and WebSockets suck a lot less than polling. If you
already collected all the polling in one place, it's really easy to make
the switch as soon as you implement them in that one place.
4) If you don't have a common place to poll, then you can't use the
events as triggers for other services in OpenStack (without writing
custom polling code for every endpoint in every API - which is pretty
much what Heat does now, but that work doesn't extend automatically to
Mistral, Congress, &c. in the way that Zaqar notifications could.)
Also, APIs tend to only return the current status. You could miss events
if you just poll the API, whereas if the events are dispatched to a
durable queue and you just poll the queue for events, that problem goes
away.
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
Bingo, this is where it starts to get really interesting.
cheers,
Zane.
Thanks,
Kevin
------------------------------------------------------------------------
*From:* Joe Gordon [joe.gord...@gmail.com
<mailto:joe.gord...@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 <fla...@redhat.com
<mailto:fla...@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-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
