Jump to: navigation, search

Difference between revisions of "Meetings/Ceilometer"

(Next meeting)
Line 14: Line 14:
== Next meeting ==
== Next meeting ==
* Wed Jul 3rd at 2100 UTC
* Thu Jul 11rd at 1500 UTC
=== Agenda ===
=== Agenda ===
Line 23: Line 23:
** https://launchpad.net/ceilometer/+milestone/havana-2
** https://launchpad.net/ceilometer/+milestone/havana-2
* Release python-ceilometerclient?
* Release python-ceilometerclient?
* Multi dispatcher enablement blueprint https://blueprints.launchpad.net/ceilometer/+spec/multi-dispatcher-enablement
** what wanted is to have a way so that things (plugin or handlers) can be configured so that data gathered by Ceilometer can be passed to the plugin for further handling without any data loss.
** two implementations, both were considered as not good enough. so what's next?
*** one introduces record_metering_data as an interface.  https://review.openstack.org/#/c/34301/
*** The other uses pipeline. https://review.openstack.org/#/c/34783/
* Open discussion
* Open discussion

Revision as of 21:33, 3 July 2013

Weekly Metering meeting

The ceilometer metering project team holds a meeting in #openstack-meeting:

ICAL link for the meeting schedule

HTML view of schedule in UTC

Everyone is welcome.

The blueprints that are used as a basis for the ceilometer project can be found at https://blueprints.launchpad.net/ceilometer

Next meeting

  • Thu Jul 11rd at 1500 UTC


Please add your name with the agenda item, so we know who to call on during the meeting.

Apologies for absence

Previous meetings

Older meetings

These meetings weren't sorted as "ceilometer" ones, so here's the direct links:

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
#startmeeting ceilometer
#topic some action from previous meeting
#topic something interesting
#topic Open discussion
  • Update == Agenda for next meeting ==
  • Mail the automatic summary as a reply to the invitation