OpenStack Telemetry (Ceilometer)

Multi publisher

Registered by Julien Danjou on 2012-10-30

Allow to use multiple publisher and not only the one targeting ceilometer-collector.

Blueprint information

Status:
Complete
Approver:
Nick Barcet
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
jiang, yunhong
Definition:
Approved
Series goal:
Accepted for grizzly
Implementation:
Implemented
Milestone target:
milestone icon 2013.1
Started by
Nick Barcet on 2012-12-27
Completed by
jiang, yunhong on 2013-02-18

Whiteboard

Each publisher should have its own value for the frequency of events it is interested int.
Each publisher would receive Counter and will manipulate them as it likes: publishing, converting in other things, etc.

Gerrit topic: https://review.openstack.org/#q,topic:bug/1073988,n,z

Addressed by: https://review.openstack.org/16522
    Initial draft for multiple publisher support

Gerrit topic: https://review.openstack.org/#q,topic:bp/multi-publisher,n,z

Addressed by: https://review.openstack.org/17440
    The framework for multiple publisher

Addressed by: https://review.openstack.org/18020
    Muitiple publisher pipeline framework

Addressed by: https://review.openstack.org/18021
    Update meter publish with pipeline framework

Addressed by: https://review.openstack.org/18022
    Add instance id and instance_type information

Addressed by: https://review.openstack.org/18023
    Add basic CW publisher support

Addressed by: https://review.openstack.org/18371
    Some generic tranform function and transformer

Gerrit topic: https://review.openstack.org/#q,topic:bp/publisher-counters-frequency,n,z

(?)

Work Items

Work items:
Make meter to meter directory, to act as a normal publisher: INPROGRESS
Create documentation to describe the multiple publisher: DONE
Create multiple publisher framework with meter as the only publisher : INPROGRESS
Add CW publisher with one metrics support: INPROGRESS
Clear Counter to support instance_type, source, unit: INPROGRESS
Add interval transformer: TODO
Add cw_put_data API support: TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.