Difference between revisions of "Meetings/Zaqar"
< Meetings
(Updated based on meeting 1) |
(Updated agenda) |
||
| Line 19: | Line 19: | ||
* Review the [https://launchpad.net/marconi/+milestone/grizzly-1 g1 milestone]. | * Review the [https://launchpad.net/marconi/+milestone/grizzly-1 g1 milestone]. | ||
* Decide whether to support tags or some other fanout mechanism, or just stick with N-queue approach (for v1.0 at least) | * Decide whether to support tags or some other fanout mechanism, or just stick with N-queue approach (for v1.0 at least) | ||
| − | * | + | * Consider splitting the API into two namespaces, one for work queuing and one for eventing |
| + | * Decide whether client state should be based on timestamps or markers (or make one optional) | ||
| + | * Talk about the state of XML support in [[OpenStack]] and decide where we stand on the issue. | ||
* Open discussion | * Open discussion | ||
| Line 26: | Line 28: | ||
Stuff we want to talk about in a future meeting: | Stuff we want to talk about in a future meeting: | ||
| + | * Discuss items from the [http://wiki.openstack.org/marconi/specs/api/v1 API blueprint] decisions list | ||
* Supporting mobile devices, doing so securely (allowing mobile posts to a queue) | * 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 | * Authorization based on an API key generated for a specific app and a specific queue | ||
Revision as of 20:38, 23 January 2013
Weekly Marconi (message bus) meeting
The Marconi project team holds a meeting in #openstack-meeting-alt:
- 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
- 24 Jan 2013
Agenda
- Review last week's actions
- kgriffs to kick the tires on Pecan
- Review the g1 milestone.
- Decide whether to support tags or some other fanout mechanism, or just stick with N-queue approach (for v1.0 at least)
- Consider splitting the API into two namespaces, one for work queuing and one for eventing
- Decide whether client state should be based on timestamps or markers (or make one optional)
- Talk about the state of XML support in OpenStack and decide where we stand on the issue.
- Open discussion
Backlog
Stuff we want to talk about in a future meeting:
- Discuss items from the API blueprint decisions list
- 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
- Audit river - should we do it, and if so, should it be an optional or mandatory part of the spec?
Previous meetings
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
