<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
/* Page Definitions */
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 137.75pt 72.0pt 137.7pt;}
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]-->
</head>
<body lang="ZH-CN" link="blue" vlink="purple" style="text-justify-trim:punctuation">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> -----Original Message-----</span></p>
<p class="MsoPlainText"><span lang="EN-US">> From: Julien Danjou [mailto:julien@danjou.info]</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Sent: Thursday, January 17, 2013 5:13 PM</span></p>
<p class="MsoPlainText"><span lang="EN-US">> To: Jiang, Yunhong</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Cc: openstack-dev@lists.openstack.org</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Subject: Re: [openstack-dev] [ceilometer] Pollsters and counters</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> On Thu, Jan 17 2013, Jiang, Yunhong wrote:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> > a) as discussed before, the pipeline definition should not be changed in</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > deployment unless expert user. While in deployment, user may want to</span></p>
<p class="MsoPlainText"><span lang="EN-US">> disable</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > some counter specifically.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> I don't think we are sure about that. The pipeline definition is also</span></p>
<p class="MsoPlainText"><span lang="EN-US">> going to configure the periodicity of pollsters for example. It's really</span></p>
<p class="MsoPlainText"><span lang="EN-US">> likely that it's going to be modified.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> AFAIK the assupmtion that the pipeline is not going to be modified has</span></p>
<p class="MsoPlainText"><span lang="EN-US">> been asserted because it seems that the pipeline is going to be complex</span></p>
<p class="MsoPlainText"><span lang="EN-US">> for publisher like CloudWatch because of the amount of transformers</span></p>
<p class="MsoPlainText"><span lang="EN-US">> needed.</span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> If this is a problem, this is likely to be hidden in another way, like</span></p>
<p class="MsoPlainText"><span lang="EN-US">> the ability of defining a transformer based on several transformer (some</span></p>
<p class="MsoPlainText"><span lang="EN-US">> sort of macro).<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> > b) If we really have several publishers (3 or 4, or even more), that means</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > user have to excluded the counters in each pipeline definition and that's</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > not so convenient. After all, pipeline is mostly a per-publisher</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > configuration.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> I don't think it's really a problem to disable counters when you have 3</span></p>
<p class="MsoPlainText"><span lang="EN-US">> or 4 publishers. People configuring 3 or 4 publishers will have to know</span></p>
<p class="MsoPlainText"><span lang="EN-US">> what they're doing.</span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">The pipeline for CloudWatch will not be very simple at least in my previous patch series :) But yes that the administrator should be qualified to modify it.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> > BTW, I noticed the glance pollster is one counter per pollster while swift</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > pollster is all counters in one pollster. I think we need keep it same for</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > all resource pollster.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> Yes, don't worry, we know the current state is not ideal. But it's</span></p>
<p class="MsoPlainText"><span lang="EN-US">> working, that's already a good point. :)</span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black">Totally agree that we already have a good point ......<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black">--jyh<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> --</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Julien Danjou</span></p>
<p class="MsoPlainText"><span lang="EN-US">> -- Free Software hacker & freelance</span></p>
<p class="MsoPlainText"><span lang="EN-US">> -- <a href="http://julien.danjou.info">
<span style="color:windowtext;text-decoration:none">http://julien.danjou.info</span></a></span></p>
</div>
</body>
</html>