Difference between revisions of "Meetings/Zaqar"
< Meetings
m (→Next meeting) |
(→Agenda) |
||
Line 14: | Line 14: | ||
The blueprints that are used as a basis for the [https://launchpad.net/marconi Marconi project] can be found at https://blueprints.launchpad.net/marconi | The blueprints that are used as a basis for the [https://launchpad.net/marconi Marconi project] can be found at https://blueprints.launchpad.net/marconi | ||
+ | * Incubation Plans | ||
+ | ** What other reference drivers do we need? | ||
+ | ** Timing | ||
+ | * H1 Closure | ||
* Bugs | * Bugs | ||
** AutoReconnect | ** AutoReconnect |
Revision as of 18:18, 29 May 2013
Contents
Weekly Marconi (queuing) meeting
The Marconi project team holds a weekly team meeting in #openstack-meeting-alt
:
- Thursdays at 1900 UTC
Next meeting
- 30 May 2013
Agenda
The blueprints that are used as a basis for the Marconi project can be found at https://blueprints.launchpad.net/marconi
- Incubation Plans
- What other reference drivers do we need?
- Timing
- H1 Closure
- Bugs
- AutoReconnect
- ?
- BPs
- QA cluster news
- Proposal: Rename "exceptions" modules to "errors".
- Simple Project ID-based Authorization
- RPC, also scaling long-lived connections (see also: http://nodeup.com/fortytwo)
- Polling modes in the client
- Message size use cases, and a crazy idea
- Open discussion (time permitting)
Previous meetings
- Meeting #12 | Bug triage, QA/ref cluster progress and hardening | 23 May 2013 | log | summary
- Meeting #11 | Blueprint target, test update, apiclient, zmq | 16 May 2013 | log | summary
- Meeting #10 | System and perf testing, blueprint triage | 9 May 2013 | log | summary
- Meeting #9 | Alignment with Havana milestones, FIFO, saved by grace | 2 May 2013 | log | summary
- Meeting #8 | Portland Demo, Auth, Claims, Routing | 4 April 2013 | log | summary
- Meeting #7 | State of the project, claiming messages | 21 Mar 2013 | log | summary
- Meeting #6 | Posting messages, queue metadata | 7 Mar 2013 | log | summary
- Meeting #5 | Claiming messages, dev kickoff | 21 Feb 2013 | log | summary
- 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