Jump to: navigation, search

Difference between revisions of "Meetings/Ceilometer"

Line 4: Line 4:
 
The [https://launchpad.net/ceilometer ceilometer] metering project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
 
The [https://launchpad.net/ceilometer ceilometer] metering project team holds a meeting in <code><nowiki>#openstack-meeting</nowiki></code>:
 
* Even weeks on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].  
 
* Even weeks on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].  
* Odd weeks on Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=21&min=0&sec=0 2100 UTC]
+
* Odd weeks on Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=21&min=0&sec=0 2100 UTC] /!\ on hold until after Grizzly summit, all weeks are even until then!
 
Everyone is welcome.
 
Everyone is welcome.
  
Line 10: Line 10:
  
 
== Next meeting ==
 
== Next meeting ==
   Wednesday Sept 12 at 2100 UTC
+
   Thursday Sept 20 at 1500 UTC
  
 
=== Agenda ===
 
=== Agenda ===
 
* Review last week's actions
 
* Review last week's actions
** nijaba to see with ttx how our sessions can be shown on official program
+
** dhellmann write up details of blueprint
** nijaba to update meeting page to note new alternating meeting time
+
      https://blueprints.launchpad.net/ceilometer/+spec/config-driven-notification-monitoring
** gmb to a plan on the ml with fixed dates
 
** dhellmann make sure flask is listed as a dependency of ceilometer
 
 
* Open discussion
 
* Open discussion
  
Line 25: Line 23:
  
 
== Previous meetings ==
 
== Previous meetings ==
 +
* meeting 20 | 12 sep 12 | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-12-21.00.log.html log] | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-12-21.00.html summary]
 
* meeting 19 | 06 sep 12 | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-06-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-06-15.00.html summary]
 
* meeting 19 | 06 sep 12 | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-06-15.00.log.html log] | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-06-15.00.html summary]
 
* meeting 18 | 30 aug 12 | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-08-30-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-08-30-16.01.html summary]
 
* meeting 18 | 30 aug 12 | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-08-30-16.01.log.html log] | [http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-08-30-16.01.html summary]

Revision as of 21:53, 12 September 2012

Weekly Metering meeting

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

  • Even weeks on Thursdays at 1500 UTC.
  • Odd weeks on Wednesdays at 2100 UTC /!\ on hold until after Grizzly summit, all weeks are even until then!

Everyone is welcome.

The blueprint that is used as a basis for the ceilometer project can be found at EfficientMetering

Next meeting

 Thursday Sept 20 at 1500 UTC

Agenda

  • Review last week's actions
    • dhellmann write up details of blueprint
      https://blueprints.launchpad.net/ceilometer/+spec/config-driven-notification-monitoring
  • Open discussion

Apologies for absence

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
#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