Jump to: navigation, search

Difference between revisions of "Ceilometer"

Line 16: Line 16:
 
* For Grizzly, the new objective is '''The project aims to become the infrastructure to collect measurements within OpenStack so that no two agents would need to be written to collect the same data. It's primary targets are monitoring and metering, but the framework should be easily expandable to collect for other needs. To that effect, Ceilometer should be able to share collected data with a variety of consumers'''.
 
* For Grizzly, the new objective is '''The project aims to become the infrastructure to collect measurements within OpenStack so that no two agents would need to be written to collect the same data. It's primary targets are monitoring and metering, but the framework should be easily expandable to collect for other needs. To that effect, Ceilometer should be able to share collected data with a variety of consumers'''.
 
* In the 0.1 (folsom) release its goal was just to deliver a unique point of contact for billing  systems to aquire all  meters they need to establish customer billing,  across all current and  future [[OpenStack]] core components.
 
* In the 0.1 (folsom) release its goal was just to deliver a unique point of contact for billing  systems to aquire all  meters they need to establish customer billing,  across all current and  future [[OpenStack]] core components.
** Previous central blueprint: [[EfficientMetering]]
+
 
 +
== Contributing to Ceilometer ==
 +
 
 +
The developer documentation is starting to take shape within the source and is also published at http://ceilometer.readthedocs.org in a more friendly format.
 +
 
 +
The project team hangs out on Freenode in the #openstack-metering channel, feel free to drop by and stay as long as you want to discuss your future implementation. We use the [[OpenStack]] General Mailing List for our email discussions tagging the the subject with [metering].
 +
 
 +
The project team officially meets once a week, see [[Meetings/MeteringAgenda|Ceilometer's Meeting Agenda]]
  
 
== Other resources ==
 
== Other resources ==
Line 22: Line 29:
 
* [[EfficientMetering|Original blueprint]]
 
* [[EfficientMetering|Original blueprint]]
 
* [[Ceilometer/Consumers|Projects that use Ceilometer]]
 
* [[Ceilometer/Consumers|Projects that use Ceilometer]]
 +
* In order to estimate the amounts that your cloud may generate, a [https://docs.google.com/spreadsheet/ccc?key=0AtziNGvs-uPudDhRbEJJOHFXV3d0ZGc1WE9NLTVPX0E Google spreadsheet has been proposed].
 
----
 
----
 
[[Category:Ceilometer]]
 
[[Category:Ceilometer]]

Revision as of 12:53, 23 November 2012

Ceilometer (Incubated OpenStack Project)

Source code
Bug tracker
Blueprints
Developer doc
Tarballs

Project Goal

  • For Grizzly, the new objective is The project aims to become the infrastructure to collect measurements within OpenStack so that no two agents would need to be written to collect the same data. It's primary targets are monitoring and metering, but the framework should be easily expandable to collect for other needs. To that effect, Ceilometer should be able to share collected data with a variety of consumers.
  • In the 0.1 (folsom) release its goal was just to deliver a unique point of contact for billing systems to aquire all meters they need to establish customer billing, across all current and future OpenStack core components.

Contributing to Ceilometer

The developer documentation is starting to take shape within the source and is also published at http://ceilometer.readthedocs.org in a more friendly format.

The project team hangs out on Freenode in the #openstack-metering channel, feel free to drop by and stay as long as you want to discuss your future implementation. We use the OpenStack General Mailing List for our email discussions tagging the the subject with [metering].

The project team officially meets once a week, see Ceilometer's Meeting Agenda

Other resources