Difference between revisions of "Ceilometer/Graduation"
| Line 8: | Line 8: | ||
** etc... | ** etc... | ||
* Robust multi purpose architecture recently extended to support multiple publishing channels, thus allowing ceilometer to become a metrics source for other tools appart from metering | * Robust multi purpose architecture recently extended to support multiple publishing channels, thus allowing ceilometer to become a metrics source for other tools appart from metering | ||
| − | * Successfully passed the adoption challenge of | + | * Successfully passed the adoption challenge of 3 related projects |
** Synaps | ** Synaps | ||
** Healthnmon | ** Healthnmon | ||
| + | ** [[StackTach]] | ||
* Delivered Folsom within 2 weeks of release, prior to incubation | * Delivered Folsom within 2 weeks of release, prior to incubation | ||
* Successfully delivered the G2 milestone with the project | * Successfully delivered the G2 milestone with the project | ||
* Good integration with all core projects now, including swift | * Good integration with all core projects now, including swift | ||
== Is our architecture stable? == | == Is our architecture stable? == | ||
| − | + | Discussion with healthnmon and sandywalsh have been deep and involved. We believe their suggestions are still obtainable with only slight modifications to ceilometer architecture. The main challenge was to explain the reasoning behind our choices which, while different in their approach of the problem of collecting metrics from other projects, proved sound enough that we now have, without changing the fundamentals of our architecture a solution which: | |
* allows lean collection of metric from supporting project that send events on the Oslo bus | * allows lean collection of metric from supporting project that send events on the Oslo bus | ||
* permits regular fetching of data via a pull mechanism for non event generating projects (ie SWIFT) | * permits regular fetching of data via a pull mechanism for non event generating projects (ie SWIFT) | ||
* allows more intrusive data collection for non support project via an optional agent mechanism | * allows more intrusive data collection for non support project via an optional agent mechanism | ||
| − | The same metrics can then be | + | The same metrics can then be retrieved at different intervals and republished to multiple destinations though a JSON-based configuration mechanism, thus allowing seamless integration of multiple projects around ceilometer without forcing the use of a single database and API. |
| + | |||
| + | There are still some aspects of the architecture that are still emerging (such as database schemas for metadata/rich data and aggregation) and all groups have committed to working on a mutually acceptable solution. | ||
== Testimonials == | == Testimonials == | ||
* Rackspace | * Rackspace | ||
| + | ** Rackspace has committed considerable resources to taking the lessons learned from developing and deploying [[StackTach]] into Ceilometer ([[StackTach]] will be twilighted once comparable functionality is available). Rax has documented some of their discussion points (here: http://wiki.openstack.org/RaxCeilometerRequirements) and we will working through those in the public channels. | ||
* Healthnmon | * Healthnmon | ||
* Redhat | * Redhat | ||
Revision as of 03:12, 12 February 2013
Why we think we're ready
- Deployed and in use at many sites
- Robust multi purpose architecture recently extended to support multiple publishing channels, thus allowing ceilometer to become a metrics source for other tools appart from metering
- Successfully passed the adoption challenge of 3 related projects
- Synaps
- Healthnmon
- StackTach
- Delivered Folsom within 2 weeks of release, prior to incubation
- Successfully delivered the G2 milestone with the project
- Good integration with all core projects now, including swift
Is our architecture stable?
Discussion with healthnmon and sandywalsh have been deep and involved. We believe their suggestions are still obtainable with only slight modifications to ceilometer architecture. The main challenge was to explain the reasoning behind our choices which, while different in their approach of the problem of collecting metrics from other projects, proved sound enough that we now have, without changing the fundamentals of our architecture a solution which:
- allows lean collection of metric from supporting project that send events on the Oslo bus
- permits regular fetching of data via a pull mechanism for non event generating projects (ie SWIFT)
- allows more intrusive data collection for non support project via an optional agent mechanism
The same metrics can then be retrieved at different intervals and republished to multiple destinations though a JSON-based configuration mechanism, thus allowing seamless integration of multiple projects around ceilometer without forcing the use of a single database and API.
There are still some aspects of the architecture that are still emerging (such as database schemas for metadata/rich data and aggregation) and all groups have committed to working on a mutually acceptable solution.
Testimonials
- Rackspace
- Rackspace has committed considerable resources to taking the lessons learned from developing and deploying StackTach into Ceilometer (StackTach will be twilighted once comparable functionality is available). Rax has documented some of their discussion points (here: http://wiki.openstack.org/RaxCeilometerRequirements) and we will working through those in the public channels.
- Healthnmon
- Redhat
