Difference between revisions of "Zaqar"
m (→Queuing and Notification Service for OpenStack) |
m (→A Queuing and Notification Service for OpenStack) |
||
Line 1: | Line 1: | ||
− | = | + | == OpenStack Queuing and Notification Service == |
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. | 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. |
Revision as of 22:49, 27 March 2013
Contents
OpenStack Queuing and Notification Service
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.
Design
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:
- Emergent functionality, utility
- Modular, pluggable code base
- REST architectural style
Principles to live by:
- DRY
- YAGNI
- KISS
Use Cases
- Distribute tasks among multiple workers (transactional job queues)
- Forward events to data collectors (transactional event queues)
- Publish events to any number of subscribers (pub-sub)
- Send commands to one or more agents (point-to-point or pub-sub)
- 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.
- Forwarding notifications to email, SMS, Twitter, etc.
- Forwarding notifications to web hooks
- Forwarding notifications to APNS, GCM, etc.
- Scheduling-as-a-service
- Metering usage
Resources
Meetings | Meetings/Marconi |
IRC | #openstack-marconi on Freenode |
Trello | https://trello.com/b/7NLODgbr |
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 |