Open Stack

From: Angus Salkeld <asalkeld at mirantis.com<mailto:asalkeld at mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, April 9, 2015 6:43 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [all] how to send messages (and events) to our users



On Fri, Apr 10, 2015 at 2:24 AM, Sandy Walsh <sandy.walsh at rackspace.com<mailto:sandy.walsh at rackspace.com>> wrote:
>From: Angus Salkeld <asalkeld at mirantis.com<mailto:asalkeld at mirantis.com>>
>Sent: Wednesday, April 8, 2015 8:24 PM
>To: OpenStack Development Mailing List (not for usage questions)
>Subject: Re: [openstack-dev] [all] how to send messages (and events) to our users
>
>
>I also want to point out that what I'd actually rather see is that all
>of the services provide functionality like this. Users would be served
>by having an event stream from Nova telling them when their instances
>are active, deleted, stopped, started, error, etc.
>
>Also, I really liked Sandy's suggestion to use the notifications on the
>backend, and then funnel them into something that the user can consume.
>The project they have, yagi, for putting them into atom feeds is pretty
>interesting. If we could give people a simple API that says "subscribe
>to Nova/Cinder/Heat/etc. notifications for instance X, and put them
>in an atom feed", that seems like something that would make sense as
>an under-the-cloud service that would be relatively low cost and would
>ultimately reduce load on API servers.
>
>"an under-the-clould service" ? - That is not what I am after here.
>

Yeah, we're using this as an "under cloud" service. Our notifications are only
consumed internally, so it's not a multi-tenant/SaaS solution.

>
>What I am really after is a general OpenStack solution for how end users can
>consume service notifications (and replace "heat event-list").
>
>
>Right now there is "ceilometer event-list", but as some Ceilometer devs have said,
>they don't want to store every notification that comes.
>
>So is the yagi + atom hopper solution something we can point end-users to?
>Is it per-tenant etc...

However, there is a team within Rax working on this SaaS offering:
Peter Kazmir and Joe Savak. I'll let them respond with their lessons on
AtomHopper, etc.

Great, thanks Sandy. It would be good to see what this is (is it just Zaqar? or something totally different).

AtomHopper is an atom-pub server (it's open source: http://atomhopper.org/ ), we use it with Repose (http://openrepose.org/)
to support Keystone auth, etc. We use Yagi to read notifications from the rabbit queues and publish notifications in Atom format to a feed.

We've been using this setup internally for a couple of years now. As Sandy mentioned, Peter and Joe are working on the project to provide these Atom feeds to end users.


>Sandy, do you have a write up somewhere on how to set this up so I can experiment a bit?

Yagi: https://github.com/rackerlabs/yagi
AtomHopper: http://atomhopper.org/  (java warning)

The StackTach.v3 sandbox is DevStack-for-Notifications. It simulates
notifications (no openstack deploy needed) and it has Yagi set up to
consume them. There's also Vagrant scripts to get you going.

http://www.stacktach.com/install.html
https://github.com/stackforge/stacktach-sandbox

and some, slightly older, screencasts on the Sandbox here:
http://www.stacktach.com/screencasts.html​

We're in the #stacktach channel, by all means ping us if you run into problems.
Or if a Hangout works better for you, just scream :)

Thanks for the help!

-Angus





__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@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/20150410/4202ce65/attachment.html>