Jump to: navigation, search

Difference between revisions of "Meetings/Zaqar"

m (Weekly Marconi (queuing) meeting)
(Agenda)
Line 17: Line 17:
 
==== Agenda ====
 
==== Agenda ====
  
* Review actions from the last meeting
+
* Continue reviewing the draft API. Note that the blueprint has not yet been updated to reflect the last couple of meetings; we are working from [https://etherpad.openstack.org/queuing-api%20 a copy of the API in Etherpad].  
* Continue reviewing each operation listed in the latest [http://wiki.openstack.org/marconi/specs/api/v1 API draft]. Etherpad is here: https://etherpad.openstack.org/queuing-api
+
:* API - Claim Messages
* Open discussion
+
:* API - Get a Claim
 +
:* API - Renew a Claim
 +
:* API - Delete a Single Message
 +
:* API - Get Action Messages
 +
:* API - Count Messages
 +
:* API - Check Health
 +
* Open discussion (time permitting)
  
 
== Backlog ==
 
== Backlog ==

Revision as of 19:59, 20 February 2013

Weekly Marconi (queuing) meeting

The Marconi project team holds a meeting in #openstack-meeting-alt:


Everyone is welcome.

The blueprints that are used as a basis for the Marconi project can be found at https://blueprints.launchpad.net/marconi

Next meeting

  • 21 Feb 2013

Agenda

  • Continue reviewing the draft API. Note that the blueprint has not yet been updated to reflect the last couple of meetings; we are working from a copy of the API in Etherpad.
  • API - Claim Messages
  • API - Get a Claim
  • API - Renew a Claim
  • API - Delete a Single Message
  • API - Get Action Messages
  • API - Count Messages
  • API - Check Health
  • Open discussion (time permitting)

Backlog

Stuff we want to talk about in a future meeting:

  • Using WSME for JSON + XML support (example)
  • Audit river - should we do it, and if so, should it be an optional or mandatory part of the spec?
  • Storage drivers - the good, the bad, and the ugly
  • Delayed message delivery - use cases, what's the need, is it something we do now or later?
  • Supporting mobile devices, doing so securely (allowing mobile posts to a queue)
  • Authorization based on an API key generated for a specific app and a specific queue
  • Authentication in general
  • Max payload size - give people what they need but also want to encourage appropriate usage of the service

Previous meetings

  • Meeting #4 | GET and POST messages | 14 Feb 2013 | log | summary
  • Meeting #3 | PUT vs. PATCH, JSON vs. XML, and other discussions re the API draft. | 7 Feb 2013 | log | summary
  • Meeting #2 | Concrete queues, no tags, locking semantics, unified queue types or ? | 24 Jan 2013 | log | summary
  • Meeting #1 | Kickoff |17 Jan 2013 | log | summary

Meeting organizers