[openstack-dev] [nova] schedule instance based on CPU frequency ?
glongwave at gmail.com
Mon Jul 6 09:17:18 UTC 2015
I propose a review to add it in cpu_info :
2015-07-03 21:37 GMT+08:00 Sylvain Bauza <sbauza at redhat.com>:
> Le 03/07/2015 15:25, Jay Pipes a écrit :
>> On 07/03/2015 06:32 AM, Sylvain Bauza wrote:
>>> Le 02/07/2015 21:40, Jay Pipes a écrit :
>>>> On 07/01/2015 12:23 AM, ChangBo Guo wrote:
>>>>> thanks Dan and Jay, we don't need add new scheduler for that :-),
>>>>> what about provide cpu frequency to api /os-hypervisors, that means
>>>>> we can
>>>>> report this value automatically, the value can be used in high level
>>>>> mange tools.
>>>> Meh, I'm not too big of a fan of the os-hypervisors extension.
>>>> Actually, one might say I despise that extension :)
>>>> That said, I suppose it should be possible to include the output of
>>>> the CPU frequency in the cpu_info field there...
>>> Well, IMHO I don't like to have the Hypervisors API to be a Nagios-like
>>> view of the hypervisors world and I don't really much benefits of pusing
>>> the metrics up to the API.
>>> On the other hand, those monitor metrics are already sent as
>>> notifications on the bus  so a 3rd party tool can easily fetch them
>>> without necessarly needing to extend the API.
>> 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.
> 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
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev