<div dir="ltr">I  propose a review to add it in cpu_info :  <a href="https://review.openstack.org/#/c/197829/">https://review.openstack.org/#/c/197829/</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-07-03 21:37 GMT+08:00 Sylvain Bauza <span dir="ltr"><<a href="mailto:sbauza@redhat.com" target="_blank">sbauza@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
Le 03/07/2015 15:25, Jay Pipes a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07/03/2015 06:32 AM, Sylvain Bauza wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le 02/07/2015 21:40, Jay Pipes a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07/01/2015 12:23 AM, ChangBo Guo wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
thanks Dan and Jay,  we don't need add new scheduler for that  :-),<br>
what about provide cpu frequency to  api  /os-hypervisors, that  means<br>
we can<br>
report this value automatically,  the value can be used in high level<br>
mange tools.<br>
</blockquote>
<br>
Meh, I'm not too big of a fan of the os-hypervisors extension.<br>
Actually, one might say I despise that extension :)<br>
<br>
That said, I suppose it should be possible to include the output of<br>
the CPU frequency in the cpu_info field there...<br>
<br>
</blockquote>
<br>
Well, IMHO I don't like to have the Hypervisors API to be a Nagios-like<br>
view of the hypervisors world and I don't really much benefits of pusing<br>
the metrics up to the API.<br>
<br>
On the other hand, those monitor metrics are already sent as<br>
notifications on the bus [1] so a 3rd party tool can easily fetch them<br>
without necessarly needing to extend the API.<br>
</blockquote>
<br>
Yeah, the difference here is that CPU frequency really isn't a metric... it's a static thing that doesn't change over time. Which is why I think it's OK to put it in cpu_info.<br>
<br>
</blockquote>
<br></span>
Oh, you're right, it's a very static thing. If it's not a metric, then I would like to see it removed from the CPU monitor and provided in cpu_info then.<span class="HOEnZb"><font color="#888888"><br>
<br>
-Sylvain</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Best,<br>
-jay<br>
<br>
__________________________________________________________________________ <br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div>ChangBo Guo(gcb)</div></div></div>
</div>