Difference between revisions of "Meetings/Zaqar"
< Meetings
(Added storage drivers to backlog) |
|||
| Line 25: | Line 25: | ||
Stuff we want to talk about in a future meeting: | Stuff we want to talk about in a future meeting: | ||
| + | * 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? | * 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) | * Supporting mobile devices, doing so securely (allowing mobile posts to a queue) | ||
| Line 30: | Line 32: | ||
* Authentication in general | * Authentication in general | ||
* Max payload size - give people what they need but also want to encourage appropriate usage of the service | * Max payload size - give people what they need but also want to encourage appropriate usage of the service | ||
| − | |||
== Previous meetings == | == Previous meetings == | ||
Revision as of 19:59, 14 February 2013
Weekly Marconi (queuing) meeting
The Marconi project team holds a meeting in #openstack-meeting-alt:
- 1st and 3rd Thursdays at 1900 UTC
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
We'll have an extra meeting this month to power through the API spec. Same bat time, same bat channel, on:
- 14 Feb 2013
Agenda
- Review actions from the last meeting
- Continue reviewing each operations listed in the latest API draft.
- Open discussion
Backlog
Stuff we want to talk about in a future meeting:
- 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 #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
- Publish the agenda 24h in advance
- Mail the agenda to the list and invite participants
- Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
- Use http://meetbot.debian.net/Manual.html to get an automatic summary
- Prepare an outline for the meeting to speed things up (see http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html for an actual example)
- Record decisions and commitments; review in the next meeting
