Jump to: navigation, search

Difference between revisions of "Meetings/Ceilometer"

m (Agenda)
(Agenda)
Line 19: Line 19:
  
 
'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
 
'''Please add your name with the agenda item, so we know who to call on during the meeting.'''
 
+
* icehouse-1 status
* Release python-ceilometerclient?
+
* progress on writing up blueprints for icehouse
 
* what's a resource? -- gordc
 
* what's a resource? -- gordc
 
** in Samples, user and project attributes are pretty self-explanatory and map to keystone concepts pretty well but what about resource_id
 
** in Samples, user and project attributes are pretty self-explanatory and map to keystone concepts pretty well but what about resource_id
 
** stems from this: https://review.openstack.org/#/c/56019  
 
** stems from this: https://review.openstack.org/#/c/56019  
 +
* Release python-ceilometerclient?
 
* Open discussion
 
* Open discussion
  

Revision as of 19:25, 20 November 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

  • Wed Nov 20th at 2100 UTC

Agenda

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

  • icehouse-1 status
  • progress on writing up blueprints for icehouse
  • what's a resource? -- gordc
    • in Samples, user and project attributes are pretty self-explanatory and map to keystone concepts pretty well but what about resource_id
    • stems from this: https://review.openstack.org/#/c/56019
  • Release python-ceilometerclient?
  • Open discussion

Apologies for absence

  • jd will be absent on the 20th November

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
#endmeeting
  • Update == Agenda for next meeting ==
  • Mail the automatic summary as a reply to the invitation