Open Stack

On Thu, Oct 03 2013, Thomas Maddox wrote:

> Interesting point, Doug and Julien. I'm thinking out loud, but if we wanted
> to use pipeline.yaml, we could have an 'enabled' attribute for each
> pipeline?

That would be an option, for sure. But just removing all of them should
also work.

> I'm curious, does the pipeline dictate whether its resulting
> sample is stored, or if no pipeline is configured, will it just store the
> sample according to the plugins in */notifications.py? I will test this out.

If there's no pipeline, there's no sample, so nothing's stored.

> For additional context, the intent of the feature is to allow a deployer
> more flexibility. Like, say we wanted to only enable storing white-listed
> event traits and using trigger pipelines (to come) for notification based
> alerting/monitoring?

This is already supported by the pipeline as you can list the meters you
want or not.

-- 
Julien Danjou
-- Free Software hacker - independent consultant
-- http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131003/f11a48b0/attachment.pgp>