Slope

• continue polling agent prototyping

Slop

• over 0
• total 4.5

Notes

On the polling agent thing I've started a branch which creates a PollingManager as a simplified version of the PipelineManager. It keeps tracks of what is to polled and just produces samples. It has not interest in sinks, just sources. The AgentManger is using it.

The data structure from setup_polling_tasks needs to be adjusted. It is currently keyed on time interval, which means that different pollsters are in the same task. This doesn't really make any sense to me. We should have lots of tasks, keyed on the name of the source. I currently have a datastructure that is a list of tuples but this is too hard to use, needs to be dict.

I've moved some tests in ceilometer/tests/newagent and in there I should make tests of the PollingManager.

Need to make sure I haven't clobbered some NotificationAgent stuff (looks like not, it has its own super class and own setup_pipeline).