From Fedora Project Wiki
Project Sponsor
Name: Brennan Ashton Fedora Account Name: bashton Group: Infrastructure Infrastructure Sponsor:
Secondary Contact info
Name: Jesse Keating Fedora Account Name: jkeating Group: Infrastructure
Project Info
Project Name: Fedora Messaging Bus Target Audience: Infrastructure Expiration/Delivery Date (required): Description/Summary: Create a messaging bus for the various Fedora services to be able to communicate with each other. Project plan (Detailed): The current target is somewhat outlined here: *https://fedoraproject.org/wiki/Messaging_SIG We need to implement a test AMQP broker running qpid. Depending on how security domains are structured, this could be three or more diffent brokers (Fedora Infrastructure, Fedora Community, FAS). The different fedora services either need to have a shim implemented to take there current interface and connect it to a broker, or be patched to allow for dirrect message support. There will likely be a mix as some services such as bugzilla, it will be very difficult to add dirrect support. The shims could be operating via email notifications (buzilla), or xmlRPC, or a mix. The email based shims would use procmail or simmilar to pass the information to an interperting python script. Once core services such as Koji, Pkgdb, SCM, FAS, and Buzilla have functioning AMQP connections, and the broker is stable. This system would then be pushed to production hardware. Other services could then be added in later. Goals:
Specific resources needed
A test server is need to host:
- Broker(s)
- FAS
- Koji
- SCM
- procmail (recive bugzilla email from production server)
- various shims