Jump to: navigation, search

Difference between revisions of "Ceilometer"

m (Text replace - "__NOTOC__" to "")
(Ceilometer (Incubated OpenStack Project))
Line 3: Line 3:
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 
| Source code  
 
| Source code  
 +
| https://github.com/openstack/ceilometer
 
|-
 
|-
 
| Bug tracker  
 
| Bug tracker  
 +
| https://bugs.launchpad.net/ceilometer
 
|-
 
|-
 
| Blueprints  
 
| Blueprints  
 +
| https://blueprints.launchpad.net/ceilometer
 
|-
 
|-
 
| Developer doc  
 
| Developer doc  
 +
| http://docs.openstack.org/developer/ceilometer/
 
|-
 
|-
 
| Tarballs  
 
| Tarballs  
 +
| http://tarballs.openstack.org/ceilometer/
 
|-
 
|-
 
| RoadMap  
 
| RoadMap  
 +
| https://wiki.openstack.org/wiki/Ceilometer/RoadMap
 
|-
 
|-
 
| Meetings  
 
| Meetings  
 +
| https://wiki.openstack.org/wiki/Meetings/MeteringAgenda
 
|}
 
|}
  
 
== Project Goal ==
 
== 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'''.
 
* 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.
  

Revision as of 14:03, 18 February 2013

Ceilometer (Incubated OpenStack Project)

Source code https://github.com/openstack/ceilometer
Bug tracker https://bugs.launchpad.net/ceilometer
Blueprints https://blueprints.launchpad.net/ceilometer
Developer doc http://docs.openstack.org/developer/ceilometer/
Tarballs http://tarballs.openstack.org/ceilometer/
RoadMap https://wiki.openstack.org/wiki/Ceilometer/RoadMap
Meetings https://wiki.openstack.org/wiki/Meetings/MeteringAgenda

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.

Project Agenda

Date Event
15 Dec 2012 Blueprint freeze
04 Jan 2013 Bug Squash Day
10 Jan 2013 ¤ Grizzly-2
21 Feb 2013 ¤ Grizzly-3
05 Mar 2013 Bug Squash day
14 Mar 2013 RC Starts
04 Apr 2013

Contributing to Ceilometer

The developer documentation is starting to take shape within the source and is also published at http://docs.openstack.org/developer/ceilometer/ 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

More details can be found on possible contributions at Ceilometer/Contributing including:

  • Setting-up Ceilometer via devstack
  • Possible tasks
    • Update documentation
    • Close old fixed bugs
    • Fix bugs
    • Review patches
    • Triage incoming bugs
  • and more...

Other resources

Subpages

<<Navigation(children,1)>>