Jump to: navigation, search

Difference between revisions of "Zaqar"

m (Resources)
m (Resources)
Line 59: Line 59:
|  Other Blueprints     
|  Other Blueprints     
| http://docs.rackspace.com/files/api/v1/cf-devguide/content/Update_Container_Metadata-d1e1900.html
| https://blueprints.launchpad.net/marconi
|  Milestones   
|  Milestones   

Revision as of 20:29, 7 March 2013

OpenStack Message Queuing ("Marconi")

Marconi is a new OpenStack project to create a multi-tenant cloud queuing service. Our aim is to create an open alternative to SQS (producer-consumer) and SNS (pub-sub), for use in applications that run on OpenStack clouds. The project will define a clean, RESTful API, use a modular architecture, and will support both eventing and job-queuing semantics. Users will be able to customize Marconi to achieve a wide range of performance, durability, availability, and efficiency goals.

Kurt Griffiths (kgriffs) is the current PTL.


Marconi aims to be pragmatic, building upon the real-world experiences of teams who have solid track records running and supporting web-scale message queueing systems. The project's overarching design philosophy is derived from Donald A. Norman:

The value of a well-designed object is when it has such a rich set of affordances that the people who use it can do things with it that the designer never imagined.

Goals related to the above:

  1. Emergent functionality, utility
  2. Modular, pluggable code base
  3. REST architectural style

Principles to live by:

  1. DRY
  2. YAGNI
  3. KISS

Use Cases

  1. Distribute tasks among multiple workers (transactional job queues)
  2. Forward events to data collectors (transactional event queues)
  3. Publish events to any number of subscribers (pub-sub)
  4. Send commands to one or more agents (point-to-point or pub-sub)
  5. Request an action or get information from an agent (RPC)

Out of Scope

Marconi may be used as the foundation for other services to support the following use cases, but will not support them directly within its code base.

  1. Forwarding notifications to email, SMS, Twitter, etc.
  2. Forwarding notifications to web hooks
  3. Forwarding notifications to APNS, GCM, etc.
  4. Scheduling-as-a-service
  5. Metering usage


Meetings Meetings/Marconi
IRC #openstack-marconi on Freenode
Grizzly Spec Marconi/specs/grizzly
API Blueprint Marconi/specs/api/v1


Other Blueprints https://blueprints.launchpad.net/marconi
Milestones https://launchpad.net/marconi/+milestones
Developer Docs TBD
Source code https://github.com/stackforge/marconi
Code Reviews https://review.openstack.org/#/q/status:open+project:stackforge/marconi,n,z
Bug tracker https://bugs.launchpad.net/marconi