[three]Bean

I just finished setting up a fedmsg bot to post updates to identi.ca. You can check it out at @fedmsgbot. There's also this little realtime interface.

Why would this be of any interest?

• You can check @fedmsgbot for a public timeline of the development of Fedora.
• If you do something, and you're proud of it, you can go and "favorite" or "re-tweet" a message.

The code works just as well with Twitter (the bot can tweet to multiple platforms and accounts) but I ran into the daily maximum tweet limit; Twitter's 1000-new-updates-per-day is not enough for fedmsg. I asked Twitter if they'd allow an exception, but was denied. Ah, well.. if you have any workaround ideas, let me know.

The source for this, of course, is in the fedmsg repo.

Bill Peck wanted to know if he could consume messages from the Fedora Infrastructure message bus without using the fedmsg libs and stack. The answer is yes.

I wrote up an example for him and turns out it was pretty simple, simple enough to warrant being added as its own new section in the docs.

The downshot here is that you don't get the configuration helpers of fedmsg.config, the message manipulation helpers of fedmsg.text and most importantly, the message validation of fedmsg.crypto. The upshot is that you get a quick connection without all those dependencies:

#!/usr/bin/env python
""" You'll need to install python-zmq (pyzmq) for this one.. """

import json
import pprint
import zmq


def listen_and_print():
    # You can listen to stg at "tcp://stg.fedoraproject.org:9940"
    endpoint = "tcp://hub.fedoraproject.org:9940"
    # Set this to something like org.fedoraproject.prod.compose
    topic = 'org.fedoraproject.prod.'

    ctx = zmq.Context()
    s = ctx.socket(zmq.SUB)
    s.connect(endpoint)

    s.setsockopt(zmq.SUBSCRIBE, topic)

    poller = zmq.Poller()
    poller.register(s, zmq.POLLIN)

    while True:
        evts = poller.poll()  # This blocks until a message arrives
        topic, msg = s.recv_multipart()
        print topic, pprint.pformat(json.loads(msg))

if __name__ == "__main__":
    listen_and_print()

p.s., in other news Amit Saha has a post up on collecting stats from the fedmsg bus. This is exciting to me.

Last week we finally got datanommer working in our production environment. Originally ianweller's idea, it is a consumer that sits listening to the fedmsg bus and logs every event to a postgresql database.

It's nice to have in place now. With the data we can make more confident statements about what's happening on the bus... we can record a series of events from our production environment... play those back in staging for testing scenarios... and most importantly, we can make pretty graphs.

I made the following with the output of the datanommer-dump command and these scripts:

You can see the ups and downs of the day/night cycle and you can see activity dip on the weekend, too. Neat!