#1629 RfR: AMQP Brokers
Closed: Fixed None Opened 13 years ago by johnp.

= Project Sponsor =


Name: John (J5) Palmieri

Fedora Account Name: johnp

Group: Infrastructure

Infrastructure Sponsor: Mike McGrath

== Secondary Contact info ==


Name: Luke Macken

Fedora Account Name:lmacken

Group: Infrastructure

== Project Info ==


Project Name: Fedora AMQP Infrastructure

Target Audience: Fedora Infrastructure developers

Expiration/Delivery Date (required):

Description/Summary:

We need servers for our AMQP Brokers in order for infrastructure services to start integrating notification services. These brokers should be isolated from other services for security reasons though they can be run virtualized on the same physical hardware at first. They also have the ability to be clustered if need be. There are two servers needed:

  • The main Infrastructure AMQP Broker - This is the central broker which will be internal to Fedora and only accessible by infrastructure services and any number of replication Brokers we set up.

  • Fedora Community Broker - This broker relays events from the central broker to the Fedora Community web app via an orbited socket. We do this so the external web apps are not connecting directly to the main broker.

Project plan (Detailed):

  • Get servers running the brokers and relaying messages in a secure way.
  • Hook up infrastructure services

Goals:

  • To increase development efficiency by having computer parseable notifications available for client consumption
  • Provide instantaneous event notification to Fedora users and developers


== Specific resources needed ==

Separate instances for the main and Fedora Community brokers.

[[Category:Infrastructure]]


Just updating the ticket.

This is mostly setup in staging now. proxy1.stg via admin.stg.fedoraproject.org is exposed and has a link to app1.stg. app1.stg will be our 'internal' broker and the proxy servers will each be our external broker in a one to many type setup.

In last weeks meeting we discussed getting some use cases and things together to make sure things are working properly. I still need to add some bits to puppet after that to make sure the exchanges, links and routes are getting setup properly.

These are in place, firewall rules (in staging) are ready. We just need some messages to put through. The actual brokers are not configured (that is done by CLI) but I need to have more info about the messages to do that. Will work with J5 and lmacken when they are ready.

Login to comment on this ticket.

Metadata