Difference between revisions of "Meetings/Ceilometer"
< Meetings
(switching order of question) |
|||
Line 12: | Line 12: | ||
* Agree on update to schema to include JSON formated metadata as described at [[EfficientMetering#Storage]] | * Agree on update to schema to include JSON formated metadata as described at [[EfficientMetering#Storage]] | ||
+ | * Agree on API proposal described at: [[EfficientMetering/APIProposalv1]] | ||
* Agree on format for date_time. Suggestion is to use ISO but seeking validation for best practice for REST | * Agree on format for date_time. Suggestion is to use ISO but seeking validation for best practice for REST | ||
− | |||
* Agree on the use of a transparent cache for aggregation | * Agree on the use of a transparent cache for aggregation | ||
* Open discussion (if we have any time left) | * Open discussion (if we have any time left) |
Revision as of 18:37, 16 May 2012
Weekly Metering meeting
The ceilometer metering project team holds a meeting in #openstack-meeting
, Thursdays at 1600 UTC. Everyone is welcome.
The blueprint that is used as a basis for the ceilometer project can be found at EfficientMetering
Agenda for next meeting
Main Topic: external API definition (part 2)
- Agree on update to schema to include JSON formated metadata as described at EfficientMetering#Storage
- Agree on API proposal described at: EfficientMetering/APIProposalv1
- Agree on format for date_time. Suggestion is to use ISO but seeking validation for best practice for REST
- Agree on the use of a transparent cache for aggregation
- Open discussion (if we have any time left)
Meeting topics
Based on the 26 APR '12 meeting decision, here are the discussion to take place in the upcoming meetings:
- 03 May: schema and counter definitions
- 10 May: external API definition (part 1)
- 17 May: external API definition (part 2)
- 24 May: message queue choice
- 31 May: API message format
- 7 June: storage backend (high availability, SPOF etc.)
Apologies for absence
- dachary
Previous meetings
- meeting 2 | 10 may 12 | summary | log
- meeting 1 | 3 may 12 | summary | log
- meeting 0 | 26 APR 12 | summary | log
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:
#action 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)
#startmeeting #chair <white space separated list of chairs> #link <thread announcing the meeting> #topic actions from previous meetings <all #actions from people responsible for actions from the previous meetings>
- Update Previous meetings
- Update == Agenda for next meeting ==
- Mail the automatic summary as a reply to the invitation