Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
I think it could bring more general discussion on how to collect physical equipment information, and which to be collected? right now, ceilometer only tracking the VM level, and when we use ironic, we expect the ironic can bring us some good information on the deployed physical machine images. On Mon, Dec 23, 2013 at 10:17 AM, Gao, Fengqian fengqian@intel.comwrote: 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 --fengqian *From:* Pradipta Banerjee [mailto:bprad...@yahoo.com] *Sent:* Friday, December 20, 2013 10:52 PM *To:* openstack-dev@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@intel.com wrote: Hi, all, I am planning to extend bp https://blueprints.launchpad.net/nova/+spec/utilization-aware-schedulingwith 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? Hi! 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. +1 Using lm-sensors or equivalent seems better. Have a look at the following blueprint https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking If you think there's a compelling reason to use Ironic for this instead of lm-sensors, please clarify. Cheers, Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Regards, Pradipta ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
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 --fengqian From: Pradipta Banerjee [mailto:bprad...@yahoo.com] Sent: Friday, December 20, 2013 10:52 PM To: openstack-dev@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@intel.commailto:fengqian@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? Hi! 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. +1 Using lm-sensors or equivalent seems better. Have a look at the following blueprint https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking If you think there's a compelling reason to use Ironic for this instead of lm-sensors, please clarify. Cheers, Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Regards, Pradipta ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
Cheers Gao. So my only comment here is how complex and how many attributes are we expecting the scheduler to take as input. Similarly the more variables you schedule on the more complex the beast becomes and from experience you end up having cross dependencies. I can see power be an item of concern but don't you think that we could solve that one with Nova Cells Parent being aware of the Power consumption costs at time-T and then just forward the Nova API call to the appropriate Child which has say the least power consumption cost? Also, on a priority scale, some DC providers (speaking as one of the DC Providers here) will not have power cost on their top say 5 list for scheduling. So I agree its definitely interesting but if you consider scheduling inside a large DC in the same geographical region and Dc site, Scheduling for power consumption becomes null and void. ;-( BR Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-19-13 11:10 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Yes, Alan, you got me. Providing power/temperature to scheduler, set threshold or different weight, then the scheduler can boot VM on the most suitable node. Thanks --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Friday, December 20, 2013 11:58 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Cheers Gao It definitely makes sense to collect additional metrics such as power and temperature, and make that available for selective decisions you would want to take. However, I am just wondering if you could realistically feed those metrics as variables for scheduling, this is the main part I feel is questionable. I assume then you would use temperature || power etc to gauge if you want to schedule another VM on a given node when a given temperature threshold is reached. Is this the main case you are thinking of Gao? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 10:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi, Alan, I think, for nova-scheduler it is better if we gather more information. And In today's DC, power and temperature are very important facts to considering. CPU/Memory utilization is not enough to describe nodes' status. Power/inlet temperature should be noticed. Best Wishes --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Thursday, December 19, 2013 2:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi Gao What is the reason why you see it would be important to have these two additional metrics power and temperature for Nova to base scheduling on? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 1:00 AM To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI 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. 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? Best wishes --fengqian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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@intel.com mailto:fengqian@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? Hi! 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. +1 Using lm-sensors or equivalent seems better. Have a look at the following blueprint https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking If you think there's a compelling reason to use Ironic for this instead of lm-sensors, please clarify. Cheers, Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Regards, Pradipta ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
One additional item Gao and apologies as I was thinking power on two front here. I assume then the limit here is per compute node within a given DC site, so yes I can see some small benefits on that for sure. I still however have a hard time seeing if I want to do scheduling based on power as one of my main attributes I need to schedule based on, but sure I can see some value in this. Let me know when you flesh this out in the blueprint, would be willing to support and take some items for dev for this. BR Alan From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: December-20-13 8:21 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Cheers Gao. So my only comment here is how complex and how many attributes are we expecting the scheduler to take as input. Similarly the more variables you schedule on the more complex the beast becomes and from experience you end up having cross dependencies. I can see power be an item of concern but don't you think that we could solve that one with Nova Cells Parent being aware of the Power consumption costs at time-T and then just forward the Nova API call to the appropriate Child which has say the least power consumption cost? Also, on a priority scale, some DC providers (speaking as one of the DC Providers here) will not have power cost on their top say 5 list for scheduling. So I agree its definitely interesting but if you consider scheduling inside a large DC in the same geographical region and Dc site, Scheduling for power consumption becomes null and void. ;-( BR Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-19-13 11:10 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Yes, Alan, you got me. Providing power/temperature to scheduler, set threshold or different weight, then the scheduler can boot VM on the most suitable node. Thanks --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Friday, December 20, 2013 11:58 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Cheers Gao It definitely makes sense to collect additional metrics such as power and temperature, and make that available for selective decisions you would want to take. However, I am just wondering if you could realistically feed those metrics as variables for scheduling, this is the main part I feel is questionable. I assume then you would use temperature || power etc to gauge if you want to schedule another VM on a given node when a given temperature threshold is reached. Is this the main case you are thinking of Gao? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 10:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi, Alan, I think, for nova-scheduler it is better if we gather more information. And In today's DC, power and temperature are very important facts to considering. CPU/Memory utilization is not enough to describe nodes' status. Power/inlet temperature should be noticed. Best Wishes --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Thursday, December 19, 2013 2:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi Gao What is the reason why you see it would be important to have these two additional metrics power and temperature for Nova to base scheduling on? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 1:00 AM To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI 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. 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? Best wishes --fengqian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
On Wed, Dec 18, 2013 at 7:16 PM, Gao, Fengqian fengqian@intel.comwrote: Hi, Devananda, I agree with you that new features should be towards Ironic. As you asked why use Ironic instead of lm-sensors, actually I just want to use IPMI instead of lm-sensors. I think it is reasonable to put the IPMI part into Ironic and we already didJ. To get the sensors’ information, I think IPMI is much more powerful than lm-sensors. Firstly, IPMI is flexible. Generally speaking, it provides two kinds of connections, in-bind and out-of-band. Out-of-band connection allows us to get sensors’ status even without OS and CPU. In-band connection is quite similar to lm-sensors, It needs the OS kernel to get sensor data. Secondly, IPMI can gather more sensors’ information that lm-sensors and it is easy to use. From my own experience, using IPMI can get all the sensor information that lm-sensors could get, such as temperature/voltage/fan. Besides that, IPMI can get power data and some OEM specific sensor data. Thirdly, I think IPMI is a common spec for most of OEMs. And most of servers are integrated with IPMI interface. As you sais, nova-compute is already supplying information to the scheduler and power/temperature should be gathered locally. IPMI can be used locally, the in-band connection. And there is a lot of open source library, such as OpenIPMI, FreeIPMI, which provide the interfaces to OS, just like lm-sensors. So, I prefer to use IPMI than lm-sensors. Please leave your comments if you disagreeJ. I see nothing wrong with nova-compute gathering such information locally. Whether you use lm-sensors or in-band IPMI is an implementation detail of how nova-compute would gather the information. However, I don't see how this has anything to do with Ironic or the nova-baremetal driver. These would gather information remotely (using out-of-band IPMI) for hardware controlled and deployed by these services. In most cases, nova-compute is not deployed by nova-compute (exception: if you're running TripleO). Hope that helps, -Deva ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
Hi, Devananda, Thanks for your reply. I totally agree with your thought, nova-compute could gathering such information locally. And I think IPMI, using in-band connection, might be more suitable to be used to collect these sensor data. At the beginning, I thought it would better to put all IPMI part together in Ironic while there is part of code over there. Now, it looks like that I thought too much:). In all, power and temperature could be collected by IPMI locally in nova-compute. Best wishes --fengqian From: Devananda van der Veen [mailto:devananda@gmail.com] Sent: Friday, December 20, 2013 3:42 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI On Wed, Dec 18, 2013 at 7:16 PM, Gao, Fengqian fengqian@intel.commailto:fengqian@intel.com wrote: Hi, Devananda, I agree with you that new features should be towards Ironic. As you asked why use Ironic instead of lm-sensors, actually I just want to use IPMI instead of lm-sensors. I think it is reasonable to put the IPMI part into Ironic and we already did:). To get the sensors' information, I think IPMI is much more powerful than lm-sensors. Firstly, IPMI is flexible. Generally speaking, it provides two kinds of connections, in-bind and out-of-band. Out-of-band connection allows us to get sensors' status even without OS and CPU. In-band connection is quite similar to lm-sensors, It needs the OS kernel to get sensor data. Secondly, IPMI can gather more sensors' information that lm-sensors and it is easy to use. From my own experience, using IPMI can get all the sensor information that lm-sensors could get, such as temperature/voltage/fan. Besides that, IPMI can get power data and some OEM specific sensor data. Thirdly, I think IPMI is a common spec for most of OEMs. And most of servers are integrated with IPMI interface. As you sais, nova-compute is already supplying information to the scheduler and power/temperature should be gathered locally. IPMI can be used locally, the in-band connection. And there is a lot of open source library, such as OpenIPMI, FreeIPMI, which provide the interfaces to OS, just like lm-sensors. So, I prefer to use IPMI than lm-sensors. Please leave your comments if you disagree:). I see nothing wrong with nova-compute gathering such information locally. Whether you use lm-sensors or in-band IPMI is an implementation detail of how nova-compute would gather the information. However, I don't see how this has anything to do with Ironic or the nova-baremetal driver. These would gather information remotely (using out-of-band IPMI) for hardware controlled and deployed by these services. In most cases, nova-compute is not deployed by nova-compute (exception: if you're running TripleO). Hope that helps, -Deva ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
Cheers Gao It definitely makes sense to collect additional metrics such as power and temperature, and make that available for selective decisions you would want to take. However, I am just wondering if you could realistically feed those metrics as variables for scheduling, this is the main part I feel is questionable. I assume then you would use temperature || power etc to gauge if you want to schedule another VM on a given node when a given temperature threshold is reached. Is this the main case you are thinking of Gao? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 10:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi, Alan, I think, for nova-scheduler it is better if we gather more information. And In today's DC, power and temperature are very important facts to considering. CPU/Memory utilization is not enough to describe nodes' status. Power/inlet temperature should be noticed. Best Wishes --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Thursday, December 19, 2013 2:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi Gao What is the reason why you see it would be important to have these two additional metrics power and temperature for Nova to base scheduling on? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 1:00 AM To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI 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. 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? Best wishes --fengqian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
Yes, Alan, you got me. Providing power/temperature to scheduler, set threshold or different weight, then the scheduler can boot VM on the most suitable node. Thanks --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Friday, December 20, 2013 11:58 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Cheers Gao It definitely makes sense to collect additional metrics such as power and temperature, and make that available for selective decisions you would want to take. However, I am just wondering if you could realistically feed those metrics as variables for scheduling, this is the main part I feel is questionable. I assume then you would use temperature || power etc to gauge if you want to schedule another VM on a given node when a given temperature threshold is reached. Is this the main case you are thinking of Gao? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 10:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi, Alan, I think, for nova-scheduler it is better if we gather more information. And In today's DC, power and temperature are very important facts to considering. CPU/Memory utilization is not enough to describe nodes' status. Power/inlet temperature should be noticed. Best Wishes --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Thursday, December 19, 2013 2:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi Gao What is the reason why you see it would be important to have these two additional metrics power and temperature for Nova to base scheduling on? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 1:00 AM To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI 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. 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? Best wishes --fengqian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
Hi Gao What is the reason why you see it would be important to have these two additional metrics power and temperature for Nova to base scheduling on? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 1:00 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI 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. 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? Best wishes --fengqian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
On Tue, Dec 17, 2013 at 10:00 PM, Gao, Fengqian fengqian@intel.comwrote: Hi, all, I am planning to extend bp https://blueprints.launchpad.net/nova/+spec/utilization-aware-schedulingwith power and temperature. In other words, power and temperature can be collected and used for nova-scheduler just as CPU utilization. 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? Hi! 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. If you think there's a compelling reason to use Ironic for this instead of lm-sensors, please clarify. Cheers, Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
Hi, Devananda, I agree with you that new features should be towards Ironic. As you asked why use Ironic instead of lm-sensors, actually I just want to use IPMI instead of lm-sensors. I think it is reasonable to put the IPMI part into Ironic and we already did:). To get the sensors' information, I think IPMI is much more powerful than lm-sensors. Firstly, IPMI is flexible. Generally speaking, it provides two kinds of connections, in-bind and out-of-band. Out-of-band connection allows us to get sensors' status even without OS and CPU. In-band connection is quite similar to lm-sensors, It needs the OS kernel to get sensor data. Secondly, IPMI can gather more sensors' information that lm-sensors and it is easy to use. From my own experience, using IPMI can get all the sensor information that lm-sensors could get, such as temperature/voltage/fan. Besides that, IPMI can get power data and some OEM specific sensor data. Thirdly, I think IPMI is a common spec for most of OEMs. And most of servers are integrated with IPMI interface. As you sais, nova-compute is already supplying information to the scheduler and power/temperature should be gathered locally. IPMI can be used locally, the in-band connection. And there is a lot of open source library, such as OpenIPMI, FreeIPMI, which provide the interfaces to OS, just like lm-sensors. So, I prefer to use IPMI than lm-sensors. Please leave your comments if you disagree:). Best wishes --fengqian From: Devananda van der Veen [mailto:devananda@gmail.com] Sent: Thursday, December 19, 2013 3:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI On Tue, Dec 17, 2013 at 10:00 PM, Gao, Fengqian fengqian@intel.commailto:fengqian@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. 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? Hi! 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. If you think there's a compelling reason to use Ironic for this instead of lm-sensors, please clarify. Cheers, Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
Hi, Alan, I think, for nova-scheduler it is better if we gather more information. And In today's DC, power and temperature are very important facts to considering. CPU/Memory utilization is not enough to describe nodes' status. Power/inlet temperature should be noticed. Best Wishes --fengqian From: Alan Kavanagh [mailto:alan.kavan...@ericsson.com] Sent: Thursday, December 19, 2013 2:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI Hi Gao What is the reason why you see it would be important to have these two additional metrics power and temperature for Nova to base scheduling on? Alan From: Gao, Fengqian [mailto:fengqian@intel.com] Sent: December-18-13 1:00 AM To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: [openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI 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. 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? Best wishes --fengqian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Nova] [Ironic] Get power and temperature via IPMI
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. 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? Best wishes --fengqian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
