<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 19/11/15 10:26 PM, Srikanth
Vavilapalli wrote:<br>
</div>
<blockquote
cite="mid:0738F7545DD8EA459B4A21F4B608D0FF2CBD2913@ESESSMB107.ericsson.se"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi
Gord<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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On
your second point, Yes, Ceilometer does provide a framework
to capture a notification and republish to multiple “publish
targets” in addition to the collector service using
udp/kafka/notification as the transport mechanisms… We
believe this is how “Event Alarm Evaluator” module in Aodh
project get notified directly from Notification Agents. <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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">However
seems like the configuration of these additional “publish
targets” is supported only through updating the
pipeline_cfg_file and restarting the corresponding
ceilometer services. i.e. the users need to manually update
the pipeline config files to insert their “publish targets”
in the sink-publisher configuration for a set of event
filters of their interest. This type of provisioning is very
static.
<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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As
per our understanding, ceilometer currently does not provide
means for users to dynamically register/unregister their
“publish targets” with ceilometer framework for a subset
events of their interest? i.e User invokes a ceilometer API
with a set of event filters and associated publish targets,
that can be stored in a data store, which will eventually be
used by the ceilometer Publisher to dispatch the
notification to those configured destinations in addition to
the statically configured “publish targets”. Plz let us know
if our understanding is wrong or if there are any other
means to achieve the above functionality. We believe this as
a very key functionality needed to build latency sensitive
(sub-second) analytics application on-top of ceilometer
framework. We are seeking the feedback from community on
having this kind of functionality inside ceilometer before
proceeding with blueprint submission.
</span></p>
</div>
</blockquote>
actually, in Liberty you can configure a reload[1][2] to refresh
pipeline when a change happens. based on survey results, most
operators don't need this functionality so it's off by default but
it seems you do. :)<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://specs.openstack.org/openstack/ceilometer-specs/specs/liberty/reload-file-based-pipeline-configuration.html">https://specs.openstack.org/openstack/ceilometer-specs/specs/liberty/reload-file-based-pipeline-configuration.html</a><br>
[2]
<a class="moz-txt-link-freetext" href="https://github.com/openstack/ceilometer/blob/master/ceilometer/pipeline.py#L50-L58">https://github.com/openstack/ceilometer/blob/master/ceilometer/pipeline.py#L50-L58</a><br>
<br>
cheers,<br>
<br>
<pre class="moz-signature" cols="72">--
gord</pre>
</body>
</html>