2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-08-14 07:10:21 +00:00

modify renergy manpage, add powerusage and temperature

This commit is contained in:
ertaozh
2015-11-18 03:43:00 -05:00
parent 2be4d11d9b
commit 6b20360b57
2 changed files with 78 additions and 0 deletions

View File

@@ -124,6 +124,11 @@ for the server which is running in OPAL mode.
\ **renergy**\ \ *noderange*\ [-V] { cappingstatus={on | enable | off | disable}
| {cappingwatt|cappingvalue}=watt }
\ **OpenPOWER server specific :**\
\ **renergy**\ \ *noderange*\ { powerusage | temperature }
*******************
\ **DESCRIPTION**\
@@ -157,6 +162,8 @@ The attributes listed in the \ **SYNOPSIS**\ section are which ones can be hand
are not supported. If user specifies an attribute which is not supported by a specific
server, the return value of this attribute will be 'na'.
\ **Note**\ : the options \ *powerusage*\ and \ *temperature*\ are only supported for \ **OpenPOWER servers**\ .
The supported attributes for each specific system p hardware type is listed as follows:
@@ -743,6 +750,19 @@ so no additional plugins are needed for BladeCenter.)
\ **powerusage**\
Query System Power Statistics with DCMI (Data Center Manageability Interface).
\ **temperature**\
Query the temperature from DCMI (Data Center Manageability Interface) Temperature sensor.
Currently, only CPU temperature and baseboard temperature sensor available for OpenPOWER servers.
********************
\ **RETURN VALUE**\
@@ -967,6 +987,26 @@ so no additional plugins are needed for BladeCenter.)
Query powerusage and temperature for OpenPOWER servers.
\ **renergy**\ ops01 powerusage temperature
The output will be like this:
.. code-block:: perl
ops01: Current Power : 591W
ops01: Minimum Power over sampling duration : 558W
ops01: Maximum Power over sampling duration : 607W
ops01: Average Power over sampling duration : 572W
ops01: Time Stamp : 11/18/2015 - 1:4:1
ops01: Statistics reporting time period : 10000 milliseconds
ops01: Power Measurement : Active
ops01: CPU Temperature Instance 0 : +39 Centigrade
ops01: Baseboard temperature Instance 0 : +28 Centigrade
******************
\ **REFERENCES**\
******************

View File

@@ -140,6 +140,14 @@ B<renergy> I<noderange> [-V] { cappingstatus={on | enable | off | disable}
=back
B<OpenPOWER server specific :>
=over 2
B<renergy> I<noderange> { powerusage | temperature }
=back
=head1 B<DESCRIPTION>
This B<renergy> command can be used to manage the energy consumption of
@@ -169,6 +177,8 @@ B<renergy> command. But for each specific type of server, there are some attribu
are not supported. If user specifies an attribute which is not supported by a specific
server, the return value of this attribute will be 'na'.
B<Note>: the options I<powerusage> and I<temperature> are only supported for B<OpenPOWER servers>.
The supported attributes for each specific system p hardware type is listed as follows:
=over 2
@@ -638,6 +648,15 @@ Query the system power consumed prior to power on.
Query the thermal output (load) in BTUs per hour for the blade
center chassis.
=item B<powerusage>
Query System Power Statistics with DCMI (Data Center Manageability Interface).
=item B<temperature>
Query the temperature from DCMI (Data Center Manageability Interface) Temperature sensor.
Currently, only CPU temperature and baseboard temperature sensor available for OpenPOWER servers.
=back
=head1 B<RETURN VALUE>
@@ -810,6 +829,25 @@ The output of the setting operation:
=back
=item 9
Query powerusage and temperature for OpenPOWER servers.
B<renergy> ops01 powerusage temperature
The output will be like this:
ops01: Current Power : 591W
ops01: Minimum Power over sampling duration : 558W
ops01: Maximum Power over sampling duration : 607W
ops01: Average Power over sampling duration : 572W
ops01: Time Stamp : 11/18/2015 - 1:4:1
ops01: Statistics reporting time period : 10000 milliseconds
ops01: Power Measurement : Active
ops01: CPU Temperature Instance 0 : +39 Centigrade
ops01: Baseboard temperature Instance 0 : +28 Centigrade
=back
=head1 B<REFERENCES>