<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 22/11/2015 10:04 PM, Srikanth
Vavilapalli wrote:<br>
</div>
<blockquote
cite="mid:0738F7545DD8EA459B4A21F4B608D0FF2CBD37CC@ESESSMB107.ericsson.se"
type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We
have found a related blueprint
<b>[1],</b> which is exactly addressing this dynamic
provisioning of pipelines via an API and making use of a new
data store to store this configuration. But seems like that
blueprint was abandoned due its limited usage. We agree that
it may not be that frequent operation to change the pipeline
configuration in all deployments, but in certain deployments,
where applications desire to turn ON/OFF receiving these
notifications based on some other trigger (like anomaly
detection, where application might have sensed an anomaly
based on some set of meters and wanted to turn ON few
additional set of event/meters to confirm that and turn OFF
once the anomaly is confirmed). <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
</blockquote>
you're right, we abandoned that because of lack of usage and the
idea was that generally you'd probably be some type of admin if you
were editing pipeline file(s).<br>
<br>
also, the scope was a big reason for dropping. i think modification
of configuration via API is not just a Ceilometer requirement but a
global OpenStack requirement. that said, it's suggested to support
this level of functionality, it should probably be done in a way
that is useful to all OpenStack<br>
<br>
this cross-project item might be of interest:
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2015-November/078400.html">http://lists.openstack.org/pipermail/openstack-dev/2015-November/078400.html</a><br>
<br>
cheers,<br>
<pre class="moz-signature" cols="72">--
gord</pre>
</body>
</html>