Open Stack

On Tue, 7 Oct 2014, Sandy Walsh wrote:

> Haven't had any time to get anything written down (pressing deadlines
> with StackTach.v3) but open to suggestions. Perhaps we should just add
> something to the olso.messaging etherpad to find time at the summit to
> talk about it?

Have you got a link for that?

Another topic that I think is at least somewhat related to the
standardizing/contractualizing notifications topic is deprecating
polling (to get metrics/samples).

In the ceilometer side of the telemetry universe, if samples can't
be gathered via notifications then somebody writes a polling plugin
or agent and sticks it in the ceilometer tree where it is run as
either an independent agent (c.f. the new ipmi-agent) or a plugin
under the compute-agent or a plugin under the central-agent.

This is problematic in a few ways (at least to me):

* Those plugins distract from the potential leanness of a core
   ceilometer system.

* The meters created by those plugins are produced for "ceilometer"
   rather than for "telemetry". Yes, of course you can re-publish the
   samples in all sorts of ways.

* The services aren't owning the form and publication of information
   about themselves.

There are solid arguments against each of these problems individually
but as a set I find them saying "services should make more
notifications" pretty loud and clear and obviously to make that work
we need tidy notifications with good clean semantics.

-- 
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent