I logged off IRC, chat, and email Friday afternoon to push Pulse forward. I made a bunch of progress.
- New, beefier VM, all set up (bug 609956 and bug 614029)
- The new VM setup supports publishing and consuming messages via websockets / Socket.io
- The ‘org.mozilla.exchange.hg‘ exchange has been renamed to ‘org.mozilla.exchange.code‘. This is because we’ll be publishing messages from non-hg sources into it as well (like GitHub using http://christian.legnitto.com/blog/2010/11/23/github-amqp-integration-service-hook-live/), bitbucket, svn, etc). Please note the previous change will likely break your existing python scripts until you update the mozillapulse helper library!
- The mozillapulse python helper library has been updated. I added transparent support for the above exchange change. If your scripts are using HgConsumer they will automatically use the proper exchange so there is no need to change them. In the future you should migrate from HgConsumer to CodeConsumer though
- The (lame) website has been put into HG. It uses Django. Currently it it just one static template, but I intend to make it more dynamic very soon
- A new scraper / shim that polls ftp and sends interesting build release/generation events. I’ll be documenting this in the coming week
- I finished up a MediaWiki extension so we can get wiki.mozilla.org events via Pulse. I’ll be releasing it next week
Coming this week
- DNS switchover from the old VM to new VM. The switch will happen on Tuesday during scheduled IT downtime
- Documentation about the new ftp scraper / shim
- General improvements to the website and documentation (likely leveraging the websocket functionality to show live Pulse messages)
- Instructions (with video!) how to set up and configure the server-side of Pulse on a stock RHEL 5 VM
- Pulse will be marked as BETA rather than an unsupported prototype
Coming in the near future but likely not next week
- Rolling out extensions on assorted systems so that I can retire the shims/scrapers that poll
- Hooking up to a 2nd VM that listens to all Pulse messages in all exchanges and stores them in Redis or CouchDB
- Interesting (web?) visualizations to encourage others to write tools against Pulse
For more information, sign up for the mailing list.