Open Stack

> -----Original Message-----
> From: Eoghan Glynn [mailto:eglynn at redhat.com]
> Sent: Thursday, July 04, 2013 3:36 AM
> To: OpenStack Development Mailing List; Neal, Phil
> Subject: Re: [openstack-dev] [Ceilometer] Changing pollster/pipeline
> parameters
> 
> 
> Hi Phil,
> 
> Some more thoughts inline ...
> 
> > > A couple of related questions on managing CM pollster behavior via
> "config"
> > > type files:
> > >
> > > 1. I'm trying to make some modifications to the timing of the Glance
> > > (image)
> > > polling in a default CM install. It looks like the pipeline interval fields
> > > are the way to do it, and that I should tweak it using a yaml config file,
> > > but I can't seem to verify based on a read-through of the code. Can
> anyone
> > > confirm?
> >
> > Yep, the configured interval in the /etc/ceilometer/pipeline.yaml is the way
> > to go.
> >
> > For example:
> >
> >  $ sed -i 's/interval: .*$/interval: 10/' /etc/ceilometer/pipeline.yaml
> >  $ # restart ceilometer-agent-central
> >  $ ceilometer sample-list -m image.size | tail -5
> >  | df52ee46-91c0-417a-a27c-ca0b447fb5db | image.size | gauge |
> 25165824.0 | B
> >  | | 2013-07-03T21:40:15        |
> >  | df52ee46-91c0-417a-a27c-ca0b447fb5db | image.size | gauge |
> 25165824.0 | B
> >  | | 2013-07-03T21:40:25        |
> >  | df52ee46-91c0-417a-a27c-ca0b447fb5db | image.size | gauge |
> 25165824.0 | B
> >  | | 2013-07-03T21:40:35        |
> >  | df52ee46-91c0-417a-a27c-ca0b447fb5db | image.size | gauge |
> 25165824.0 | B
> >  | | 2013-07-03T21:40:45        |
> >  +--------------------------------------+------------+-------+------------+------+------
> ----------------------+
> >
> > As you see the meter is now being collected at a 10s cadence.
> >
> > This timing is pulled in via the AgentManager base class:
> >
> >
> https://github.com/openstack/ceilometer/blob/master/ceilometer/agent.p
> y#L90
> 
> I should have been more explicit here, in the sense of pointing out that:
> 
> (a) this pipeline config can be made specific to the central agent
>     (i.e. the agent responsible for polling glance among other things)
>     by adding the line:
> 
>       pipeline_cfg_file = pipeline-central.yaml
> 
>     to the ceilometer.conf picked up by the central agent (so that the
>     central agent pipeline is independent of the pipeline used by the
>     other agents)
> 
> 
> (b) multiple pipelines can be defined in a single yaml file, with different
>     polling intervals for different groups of meters.
> 
>     For example, to make only the glance polling interval 120s while keeping
>     the other central agent polling cycles at 60s, use something like the
>     following in the appropriate pipeline.yaml file:
> 
> ---
> -
>     name: meter_pipeline
>     interval: 60
>     counters:
>         - "*"
>         - "!image"
>         - "!image.size"
>     transformers:
>     publishers:
>         - rpc://
> -
>     name: image_pipeline
>     interval: 120
>     counters:
>         - "image"
>         - "image.size"
>     transformers:
>     publishers:
>         - rpc://
> 

Makes sense on paper. :=)  Will try implementing today.

> 
> > > 2. Similarly, it looks like disabling pollsters is done via the oslo.cfg
> > > logic in the agent manager. I'd like to populate that using a config
> > > file....is there logic already to do that that I haven't come across yet?
> >
> > Well the way I'd disable a pollster is simply by configuring the counters
> > exclusion in the pipeline.yaml.
> >
> > For example to disable the pollster providing the image.size meter referred
> > to above, the following will do the trick:
> >
> >     counters:
> >         - "*"
> >         - "!image.size"
> >
> > i.e. allow everything but the image.size meter.
> >
> > Confirm as before using:
> >
> >  $ # restart ceilometer-agent-central
> >  $ ceilometer sample-list -m image.size | tail -5
> 
> 
> It also occurred to me that you may have been thinking of the now-obsolete
> disabled_{central|compute|...}_pollsters config options, which are no longer
> supported as they've been superceeded by the newer pipeline config.
> 

Yes, that's the line of logic I was headed down. Thanks for noting the obsolescence.

> Hope this helps clarify things for you.
> 
> Cheers,
> Eoghan
> 
> >


Truly helpful....thanks again!
> > > - Phil
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >