Difference between revisions of "Ceilometer"
| Line 14: | Line 14: | ||
== 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'''. |
* 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]] | ** Previous central blueprint: [[EfficientMetering]] | ||
Revision as of 21:50, 24 October 2012
OpenStack Metering ("Ceilometer")
| 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.
- Previous central blueprint: EfficientMetering
