Split the collector
The collector has 2 purposes:
- convert Notifications into Samples (and optionally store the notification)
- store Samples received over RPC
I propose we split this in 2 differents services for better redundancy and scalability.
Blueprint information
- Status:
- Complete
- Approver:
- Julien Danjou
- Priority:
- Medium
- Drafter:
- Julien Danjou
- Direction:
- Needs approval
- Assignee:
- Julien Danjou
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
- Implemented
- Milestone target:
- 2014.1
- Started by
- Julien Danjou
- Completed by
- Julien Danjou
Related branches
Related bugs
Sprints
Whiteboard
Have we determined that this is actually a scalability issue yet ... shouldn't we be able to run multiple collectors to horizontally scale? -Sandy
Gerrit topic: https:/
Addressed by: https:/
Remove useless defined Exception in tests
Addressed by: https:/
Split collector
Gerrit topic: https:/
Addressed by: https:/
Merge ceilometer-
Addressed by: https:/
Move dispatcher a level up
Addressed by: https:/
Remove the collector submodule
Addressed by: https:/
Simplify the dispatcher method prototype
Addressed by: https:/
Use map_method from stevedore 0.12