[three]Bean

Today, I was working on busmon and trying to minimize some of the spam it was publishing back to the fedmsg bus. This amounted to cutting out some server-side code that used pygments to produce styled html markup and replacing it with client-side code that did approximately the same thing.

@lmacken found this Stack Overflow piece that did just about what I needed. Like any reasonable person, I copied and pasted and was satisfied.

Licensing! Hold the phone! Turns out that content on Stack Overflow is licensed CC-BY-SA-3.0. By my reading, code posted there is therefore incompatible with GPL code.

Wild, right?

Denouement -> I ended up rewriting it my way just to get on with it.

herlo was asking in #fedora-devel about consuming fedmsg messages from FAS. He pointed out that while there is documentation about consuming messages, there's also a lot of stuff going on. Most importantly, an introduction to the workflow is missing.

So, here's a tutorial I made in response that should walk you through it. Its a little verbose and a little rough around the edges (the line-wrapping gets wonky in places) but I think it will still serve the purpose. If it raises new questions or comments, please bring them up in the comment thread here, on the messaging-sig mailing list, or in #fedora-apps on freenode.

Static files created in that tutorial can be found in and downloaded from this gist.

Just got out of the Fedora Infrastructure weekly meeting. Some highlights from the development side of things:

Status app -- http://status.fedoraproject.org/ is live. Keep it open in a tab in your browser; the favicon should dynamically change when sysadmin-noc declares an outage.

pkgdb migration -- There's a plan in the works to migrate some pieces of pkgdb out to other apps where those pieces make more sense. Some of those pieces (in /packages and /tagger have hit staging).

fedora-packages has a /bugs path that we intend to replace bugz.fedoraproject.org some day. How does it look? Need more work?

fedora-tagger can now export a sqlite-db for yum like pkgdb's sqlitebuildtags did. We still need to test that it works with bodhi's masher before moving forwards with it.

Raw stream -- You can now access a raw stream of zmq messages from our staging infrastructure.

I'll have a handy works-out-of-the-box fedmsg config coming to your Fedora repo soon but in the meantime, you could try connecting to it yourself by running this script like $ python topics_sub.py tcp://stg.fedoraproject.org:9940.

You won't see much; its only broadcasting the quiet solace of our staging environment. But to make it and busmon dance, you could go hit the staging wiki, login, and make an edit.

rossdylan is working on a desktop notification app that will hook into this. Awesome.

Websockets -- (moksha, ftw) This was the one of the first things I wrote when I started work on fedmsg, and it finally made it to staging.

Check it out at https://apps.stg.fedoraproject.org/busmon/. Think of it as a web based version of #fedora-fedmsg with live regex filtering. You won't see much data. It's just displaying messages from the staging bus.

New hooks -- I have an untested fedmsg koji plugin ready to try out once staging has a builder.

There's also a new supybot plugin (supybot-fedmsg) that is ready to try out, but there's no stg instance of zodbot to do this easily. I'll wait until post-freeze. I like the code a bunch.. it is kind of magical.

You can always track the status of all the hooks at the fedmsg status page.

So I'm spinning up the Fedora Messaging SIG. It's been sitting idle for years; this time we're really going to do it. We're going to put 0mq messaging hooks into bodhi, koji, pkgdb, fas, you name it.

I'm building a python module called fedmsg to wrap it all and it comes with a proposal-in-development. And if you're not excited yet, we've already 0mq enabled the Moksha Hub and achieved a ~100 times speedup over AMQP/qpid.

The point of this post is to ask about times for an IRC meeting of the Messaging SIG. Right now I'm thinking Tuesdays at 16:00-17:00 UTC in #fedora-meeting. If you're interested in helping with the effort but that's a bad time for you, let me know and we'll work it out.

I'll be out at PyCon until next Wednesday; so the first meeting won't be until March 20th at the earliest.