Difference between revisions of "Meetings/Zaqar"
< Meetings
m (Text replace - "__NOTOC__" to "") |
m (→Weekly Marconi (queuing) meeting) |
||
| Line 3: | Line 3: | ||
The [https://launchpad.net/marconi Marconi] project team holds a meeting in <code><nowiki>#openstack-meeting-alt</nowiki></code>: | The [https://launchpad.net/marconi Marconi] project team holds a meeting in <code><nowiki>#openstack-meeting-alt</nowiki></code>: | ||
| + | |||
* 1st and 3rd Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 1900 UTC] | * 1st and 3rd Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=19&min=0&sec=0 1900 UTC] | ||
| + | |||
Everyone is welcome. | Everyone is welcome. | ||
| Line 23: | Line 25: | ||
Stuff we want to talk about in a future meeting: | Stuff we want to talk about in a future meeting: | ||
| + | * Using [https://pypi.python.org/pypi/WSME/0.3 WSME] for JSON + XML support ([https://github.com/openstack/ceilometer/blob/master/ceilometer/api/controllers/v2.py example]) | ||
* Audit river - should we do it, and if so, should it be an optional or mandatory part of the spec? | * 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 | * Storage drivers - the good, the bad, and the ugly | ||
| Line 33: | Line 36: | ||
== Previous meetings == | == Previous meetings == | ||
| − | * Meeting #4 | GET and POST messages | 14 Feb 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.log.html log] | | + | * Meeting #4 | GET and POST messages | 14 Feb 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.html summary] |
| − | * Meeting #3 | PUT vs. PATCH, JSON vs. XML, and other discussions re the API draft. | 7 Feb 2013 | | + | * Meeting #3 | PUT vs. PATCH, JSON vs. XML, and other discussions re the API draft. | 7 Feb 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-07-19.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-07-19.01.html summary] |
| − | * Meeting #2 | Concrete queues, no tags, locking semantics, unified queue types or ? | 24 Jan 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-01-24-19.05.log.html log] | | + | * Meeting #2 | Concrete queues, no tags, locking semantics, unified queue types or ? | 24 Jan 2013 | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-01-24-19.05.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-01-24-19.05.html summary] |
* Meeting #1 | Kickoff |17 Jan 2013 | [http://eavesdrop.openstack.org/meetings/marconi_project_team/2013/marconi_project_team.2013-01-17-19.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi_project_team/2013/marconi_project_team.2013-01-17-19.01.html summary] | * Meeting #1 | Kickoff |17 Jan 2013 | [http://eavesdrop.openstack.org/meetings/marconi_project_team/2013/marconi_project_team.2013-01-17-19.01.log.html log] | [http://eavesdrop.openstack.org/meetings/marconi_project_team/2013/marconi_project_team.2013-01-17-19.01.html summary] | ||
Revision as of 16:34, 19 February 2013
Contents
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
- 21 Feb 2013
Agenda
- Review actions from the last meeting
- Continue reviewing each operation listed in the latest API draft. Etherpad is here: https://etherpad.openstack.org/queuing-api
- Open discussion
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
- 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
