FedMsg Status Table

This is a table to keep track of where we are with all the different systems. There is no information here about receiving messages, only sending.

Service Dev Stg PKI Prod
fedmsg-relay DONE DONE N/A DONE
fedmsg-irc DONE DONE N/A DONE
fedmsg-gateway DONE DONE N/A DONE
websockets DONE DONE DONE DONE
ansible DONE N/A DONE DONE
askbot DONE DONE DONE DONE
autoqa        
badges DONE DONE DONE DONE
bodhi DONE DONE DONE DONE
bugzilla        
busmon DONE DONE DONE DONE
compose DONE N/A DONE DONE
comp 2nd arch DONE N/A DONE DONE*[4]
coprs DONE N/A DONE DONE
elections DONE [1]      
fas DONE DONE DONE DONE
fedocal DONE      
fedorahosted DONE N/A DONE DONE
koji DONE? BLOCKED [3] DONE DONE
mailman DONE      
meetbot DONE N/A DONE DONE
nagios DONE      
pastebin        
pkgdb DONE DONE DONE DONE
planet DONE? N/A DONE DONE
scm DONE DONE DONE DONE
sigul        
pkgdb2branch DONE DONE DONE DONE
tagger DONE DONE DONE DONE
wiki DONE DONE DONE DONE

Other projects

There are a number of external tools being built against fedmsg:

  • Luke Macken’s fedmsg-notify is a dbus daemon that connects the fedmsg bus to users’ desktops.
  • Bill Peck’s fedmsg-download listens to the bus and begins download rawhide and branched composes once they are complete for efficient mirroring.
  • Ralph Bean’s datanommer is a storage consumer for fedmsg. It stores every message it receives in a SQL database.

fedmsg

Previous page

← Bus Topology

Edit this document

Go to FedMsg Status Table on GitHub.

Use the web interface to fork the repo, edit the file, and send a pull request.

Your changes will be queued for review under project's Pull requests tab on Github.

Fork me on GitHub