Energy_Management_for_Flex

Table of Contents

• Overview
• Interface
  • The change of the interface compared to blade center
• Internal Implementation
• Other Design Considerations

{{:Design Warning}}

[TOC]

Overview

1. Communicate with IMM (for x86 ITE) via IPMI interface to perform the energy management. And communicate with FSP (for power ITE) via CIM interface to perform the energy management.
2. Communicate with CMM via the snmp interface to perform the energy management for Chassis, power ITE and x86 ITE.

Interface

We have supported the energy management for the blade center via snmp interface of AMM. The CMM is the next generation management product of AMM, most of the snmp OIDs are same between them. So for flex, I just need to change the interface which could not supported by AMM or have been changed for Flex.

The change of the interface compared to blade center

• For chassis, since the concept of 'power domain' has been removed from CMM (you could think that there's only one power domain for CMM, but there are two for AMM), the attribute start with pd[1|2] will be replaced with 'power', see following.

  renergy noderange [-V] { all │ [powerstatus] [powerpolicy] [powermodule] [avaiablepower] [reservedpower] [remainpower] [inusedpower] [availableDC] [averageAC] [thermaloutput] [ambienttemp] [mmtemp] }

• For ITE, the getting and setting of capping have been added for CMM, see following:

  renergy noderange [-V] { all │ [averageDC] [capability] [cappingvalue] [cappingmaxmin] [cappingmax] [cappingmin] [CPUspeed] [maxCPUspeed] [savingstatus] [dsavingstatus] } renergy noderange [-V] { cappingwatt=watt │ cappingperc=percentage │ savingstatus={on │ off} │ dsavingstatus={on-norm │ on-maxp │ off} }

Note: All the attributes for the ITE are common for power and x86 ITE except that the 'dsavingstatus' and 'savingstatus' are only working for power ITE.

Internal Implementation

• Classify the flex nodes to get the proper plugin

For the flex node, the 'mgt' attribute is set to 'ipmi' for 'x86 ITE' and the 'mgt' is set to 'fsp' for 'power ITE', but we want to use the snmp interface in the blade.pm to handle energy management for flex. Then we have to make a filter function to classify the nodes before really running in the plugins.

For the renergy command, the program will run into all the three plugins blade.pm, ipmi.pm and fsp.pm, then each plugin will run the xCAT::Utils->filter_nodes to figure out whether there are nodes that should be run by itself, if having, go ahead, otherwise, return directly.

• Power domain

As described in the previous section that the support of flex will be an enhancement base on the existed code for the blade center, only the changes against the current code will be listed. The concept of power domain has been removed from the flex, or you can consider there's only one power domain (blade center chassis has two power domain) in the flex chassis. The name of attributes for the power domain will be changed to following for flex:

pd1status => powerstatus
pd1policy => powerpolicy
pd1powermodule1 => powermodule
pd1avaiablepower => avaiablepower
pd1reservedpower => reservedpower
pd1remainpower => remainpower
pd1inusedpower => inusedpower

• Power Capping

Power capping function is supported for flex.

Query: cappingmaxmin cappingmax cappingmin
Set: cappingwatt=watt | cappingperc=percentage

Other Design Considerations

• Required reviewers: Bruce, Brian, Er Tao, Guang Cheng
• Required approvers: Bruce Potter
• Database schema changes: N/A
• Affect on other components: N/A
• External interface changes, documentation, and usability issues: N/A
• Packaging, installation, dependencies: N/A
• Portability and platforms (HW/SW) supported: N/A
• Performance and scaling considerations: N/A
• Migration and coexistence: N/A
• Serviceability: N/A
• Security: N/A
• NLS and accessibility: N/A
• Invention protection: N/A