Jump to: navigation, search


< Zaqar
Revision as of 20:03, 5 April 2013 by Kgriffs (talk | contribs) (QueueController)

Marconi Endpoints

Endpoints define the protocol between a given transport and the storage driver. In this way, multiple transports like HTTP and ZMQ can be supported; they are not exclusive and can be enabled directly from the config file.

Related endpoints are grouped into one of several controllers, who's interface is defined by an abstract base class. The storage driver provides a concrete implementation for each controller type.

For specific implementations read: HTTP, ZMQ

Common Endpoints, exposed by Storage Drivers

Storage drivers export 3 controllers which group endpoints by resource.

TODO(kgriffs): Define params and valid ranges for each.


  • List Queues
    • Return list of queue names in alphabetical order
    • Optional marker, limit params to support paging
    • Optionally include queue metadata in listing
  • Get queue metadata
  • Upsert Queue
    • Queue names may not exceed 512 bytes in length
    • Can specify arbitrary metadata (optional).
    • Top-level field names in the metadata document MUST NOT start with the underscore character as it is reserved for future use.
    • Metadata is limited to 4 KiB in size
    • (For Updates) The document that the client provides will completely overwrite existing metadata (partial updates are planned for a future release)
  • Delete Queue
  • Get queue stats
    • Messages: total, claimed, and expired (but not yet scrubbed)
  • Get Actions
    • Delete message
    • Claim messages
    • Update claim
    • Release claim
    • Claim expired
    • Message expired

Note about action messages

TODO: This has been postponed to a post-v1.0 release.

The interactions of various agents/workers with a cloud queuing services can be difficult to audit and debug. Marconi emits action messages to a special queue (hence action messages use the same format as regular messages), from which auditors can retrieve a list of recent actions involving a specific queue's messages. These actions can then be archived by the auditor for future analysis and diagnostics.

Action messages expire after 5 minutes, so auditors should regularly poll for actions and persist them for posterity.


  • Get Message(s)
  • Post Message(s)
  • Delete Message


  • Claim messages
    • Storage driver makes a best-effort attempt to return the requested number of messages, but may return fewer.
  • Query claim
  • Update claim
  • Release Claim
  • Claim Stats


The following endpoints only apply to specific transports.


  • Node health (test_reachable)
  • Get home document