Scaling Ceilometer configuration via data store
By updating Ceilometer to monitor values recorded in a persistent data store such as MySQL, the application could be made to dynamically activate/deactivate collection targets or similar functions, have distinctly different configurations for multiple nodes in different environments (i.e. dev/test/prod or HA scenarios) and could ultimately be updated with new collection targets “on-the-fly”.
Blueprint information
- Status:
- Complete
- Approver:
- Eoghan Glynn
- Priority:
- Undefined
- Drafter:
- Phil Neal
- Direction:
- Needs approval
- Assignee:
- Fabio Giannetti
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Blocked
- Milestone target:
- None
- Started by
- Phil Neal
- Completed by
- gordon chung
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Proposed in: https:/
configuration via data store
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
Addressed by: https:/
[WIP] Storage Layer Implementation for Pipeline Configuration
Addressed by: https:/
[WIP] Agent Layer Implementation for Pipeline Configuration
Addressed by: https:/
[WIP] API design for configuration via data store
changing to blocked as we have a discussion regarding implementation going -- gordc [10.03.15]
Punting to Liberty as agreed -- eglynn [12.03.15]
Addressed by: https:/
configuration via data store
marking this obselete. there is functionality being added to oslo to handle this (http://
Work Items
Dependency tree
* Blueprints in grey have been implemented.
