Make periodic monitoring tasks optional
Bug #1668330 reported by
Spyros Trigazis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Wishlist
|
Kirsten G. |
Bug Description
In deployments without ceilometer, pulling all the clusters results on unnecessary load.
Additionally, docker-py and kubernetes clients have been proven buggy so far, overloading the magnum-conductor log woth tracebacks.
We need to make the pulling of COE data optional on the periodic task.
Changed in magnum: | |
importance: | Undecided → Wishlist |
Changed in magnum: | |
assignee: | nobody → Kirsten G. (oikiki) |
Changed in magnum: | |
status: | New → In Progress |
Changed in magnum: | |
assignee: | Kirsten G. (oikiki) → Spyros Trigazis (strigazi) |
Changed in magnum: | |
assignee: | Spyros Trigazis (strigazi) → Kirsten G. (oikiki) |
To post a comment you must log in.
Hi Spyros,
I've looked through the codebase to understand monitoring tasks and where the data is being pulled. monitors.py has the abstract class pull_data() and then each type has it's own pull_data for example K8sMonitor. pull_data( ).
I am thinking that I should add an optional config param (to either magnum/conf rpc.py or cluster.py) that will be checked before pull_data() in periodic.py (line155) is executed? Is that on the right track? If so, should this be one param for all of the pull_data() functions (k8s/mesos/swarm) or should there be a way for the user to set preferences for each one separately?
Thank you!