[openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

Gao, Fengqian fengqian.gao at intel.com
Mon Dec 23 02:17:25 UTC 2013

Hi, Pradipta,
>From personal experience,  I think lm-sensors is not good as IPMI. I have to configure it manually and the sensor data it could get also less than IPMI.
So, I prefer to use IPMI. Did you use it before? Maybe you can share your experience.

Best wishes


From: Pradipta Banerjee [mailto:bpradipt at yahoo.com]
Sent: Friday, December 20, 2013 10:52 PM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI

On 12/19/2013 12:30 AM, Devananda van der Veen wrote:
On Tue, Dec 17, 2013 at 10:00 PM, Gao, Fengqian <fengqian.gao at intel.com<mailto:fengqian.gao at intel.com>> wrote:
Hi, all,
I am planning to extend bp https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling with power and temperature. In other words, power and temperature can be collected and used for nova-scheduler just as CPU utilization.
This is a good idea and have definite use cases where one might want to optimize provisioning based on power consumption

I have a question here. As you know, IPMI is used to get power and temperature and baremetal implements IPMI functions in Nova. But baremetal driver is being split out of nova, so if I want to change something to the IPMI, which part should I choose now? Nova or Ironic?


A few thoughts... Firstly, new features should be geared towards Ironic, not the nova baremetal driver as it will be deprecated soon (https://blueprints.launchpad.net/nova/+spec/deprecate-baremetal-driver). That being said, I actually don't think you want to use IPMI for what you're describing at all, but maybe I'm wrong.

When scheduling VMs with Nova, in many cases there is already an agent running locally, eg. nova-compute, and this agent is already supplying information to the scheduler. I think this is where the facilities for gathering power/temperature/etc (eg, via lm-sensors) should be placed, and it can reported back to the scheduler along with other usage statistics.

Using lm-sensors or equivalent seems better.
Have a look at the following blueprint

If you think there's a compelling reason to use Ironic for this instead of lm-sensors, please clarify.



OpenStack-dev mailing list

OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131223/fc33d93c/attachment.html>

More information about the OpenStack-dev mailing list