Difference between revisions of "Ceilometer"
(→Subpages) |
|||
| Line 53: | Line 53: | ||
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]] | ||
| + | |||
| + | === 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. | ||
| + | |||
| + | ==== 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 == | ||
| Line 61: | Line 79: | ||
== Subpages == | == Subpages == | ||
| − | < | + | <<Navigation(children,1)>> |
| + | |||
---- | ---- | ||
[[Category:Ceilometer]] | [[Category:Ceilometer]] | ||
Revision as of 15:34, 20 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
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 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.
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 how to do bug triaging for OpenStack.
Other resources
- Original blueprint
- Projects that use Ceilometer
- In order to estimate the amounts that your cloud may generate, a Google spreadsheet has been proposed.
Subpages
<<Navigation(children,1)>>
