Messaging SIG/Bugzilla Shim

From FedoraProject

< Messaging SIG(Difference between revisions)
Jump to: navigation, search
(Created page with '=Bugzilla Shim= ==Producer Concept== *Bugzilla cc's bzshim@fedoraproject.org for every component in the Fedora product *Sendmail forwards messages addressed to bzshim@fedorproj...')
 
Line 4: Line 4:
  
 
*Bugzilla cc's bzshim@fedoraproject.org for every component in the Fedora product
 
*Bugzilla cc's bzshim@fedoraproject.org for every component in the Fedora product
*Sendmail forwards messages addressed to bzshim@fedorproject.org to the shim at a different port (i.e. 5555)
+
*procmail runs the message processing script i.e. no pulling.
*Shim running smtpd.SMTPServer from python, monitoring port 5555 recived the messages in "realtime" i.e. no pulling.
+
 
*Shim processes data and formats it into an AMQP message
 
*Shim processes data and formats it into an AMQP message
*Shim then sends message via a moksha producer under fedoraproject.org.bugzilla
+
*Shim then sends message via a moksha producer under org.fedoraproject.bugzilla
  
 
==Consumer==
 
==Consumer==
  
 
Do we need a consumer for this?  There was some thought that we could just send data out on the AMQP bus about things like changing a reviews state and then this consumer would then make the change.  Is there any reason for not just having an XMLRPC call do this instead?
 
Do we need a consumer for this?  There was some thought that we could just send data out on the AMQP bus about things like changing a reviews state and then this consumer would then make the change.  Is there any reason for not just having an XMLRPC call do this instead?

Revision as of 06:48, 7 December 2009

Bugzilla Shim

Producer Concept

  • Bugzilla cc's bzshim@fedoraproject.org for every component in the Fedora product
  • procmail runs the message processing script i.e. no pulling.
  • Shim processes data and formats it into an AMQP message
  • Shim then sends message via a moksha producer under org.fedoraproject.bugzilla

Consumer

Do we need a consumer for this? There was some thought that we could just send data out on the AMQP bus about things like changing a reviews state and then this consumer would then make the change. Is there any reason for not just having an XMLRPC call do this instead?