Jump to: navigation, search

Difference between revisions of "Ceilometer"

Line 54: Line 54:
 
The project team officially meets once a week, see [[Meetings/MeteringAgenda|Ceilometer's Meeting Agenda]]
 
The project team officially meets once a week, see [[Meetings/MeteringAgenda|Ceilometer's Meeting Agenda]]
  
=== Setting-up Ceilometer via devstack ===
+
More details can be found on possible contributions at [[Ceilometer/Contributing]] including:
The easiest way to develop on Ceilometer is to use [http://devstack.org devstack].
+
* Setting-up Ceilometer via devstack
 
+
* Possible tasks
Edit your ''localrc'' file and add these lines to enable ''ceilometer'':
+
** Update documentation  
 
+
** Close old fixed bugs
 
+
** Fix bugs
<pre><nowiki>#!highlight bash
+
** Review patches
enable_service ceilometer-api
+
** Triage incoming bugs
enable_service ceilometer-collector
+
* and more...
enable_service ceilometer-acentral
 
enable_service ceilometer-acompute</nowiki></pre>
 
 
 
 
 
=== Possible tasks ===
 
==== Update documentation ====
 
Trying following the documentation to set-up and configuring Ceilometer to see if the documention is not wrong or out-dated would be a good first step.
 
Once everything's working, the next step would be to read the rest of the documentation to see if everything that's written is still true. Anything that's not clear or might be missing should be fixed and updated.
 
 
 
To update the documentation, the best way is to send a patch. But notifying the team via the [[MailingLists#Development_List|development mailing list]] or via IRC is fine too!
 
 
 
==== Close old fixed bugs ====
 
Old bugs are nasty. Even when they are long dead, they clog bug views and render the lists unusable. Just look at old bugs and check if they still apply! If they don't, close them as ''[[FixReleased]]'' (if you can pinpoint when they were fixed) or ''Invalid'' (if you can't).
 
 
 
==== Fix bugs ====
 
The best thing you can do is to kill a living bug. Just look at the list of ''Confirmed'' or ''Triaged'' and pick your target. Submit a change that fixes it. Ask for review help on the channel.
 
 
 
==== Review patches ====
 
You can review patches on the Gerrit platform for [https://review.openstack.org/#/q/status:open+project:openstack/ceilometer,n,z ceilometer] and for [https://review.openstack.org/#/q/status:open+project:openstack/python-ceilometerclient,n,z python-ceilometerclient].
 
 
 
==== Triage incoming bugs ====
 
It's sometimes hard to distinguish fresh bugs from false alarms. You can help by using your expertise or reproduction skills on ''New'' bugs. If you can confirm the issue, set the bug to ''Confirmed''. If you can fix it, read the previous entry. If you need more info from the reporter, set it to ''Incomplete''. And if it happens to not really be valid, set it to ''Invalid''!
 
 
 
You can read more information about [[BugTriage|how to do bug triaging for OpenStack]].
 
  
 
== Other resources ==
 
== Other resources ==

Revision as of 16:45, 21 December 2012

Ceilometer (Incubated OpenStack Project)

Source code
Bug tracker
Blueprints
Developer doc
Tarballs
RoadMap
Meetings

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
 ?? Feb 2013 Bug Squash day
21 Feb 2013 ¤ Grizzly-3
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)>>