Page Comparison

...

Interface #1
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: PBS hook power control module
  1. A new class “pbs.Power” will be made available that will provide power functionality. A hook will be able to access it via python import.
4. Reference to more detail on the interface. The following define the PMI operations available:
  1. pmi_activate_profile(self, profile_name, job)
    1. Activate a given power profile on a set of hosts on behalf of a given job. The parameter “profile_name” is a string containing the name of a profile. The parameter “job” is a PBS job object. The hosts will be calculated from the job object. If the job parameter is not specified, the pbs.event().job object will be used.
    2. The return type is bool where True indicates success and False indicates the request was made without an indication from the PMI if it was successful or not.
    3. If an error occurs where it is appropriate for some or all of the job vnodes to be marked offline, this may be done before an exception is raised.
    4. If an error occurs where it is appropriate for the supported profile names for some or all of the job vnodes to be refreshed, this may be done before an exception is raised.
  2. pmi_get_usage(self, job)
    1. Retrieve power usage for a job. The parameter “job” is a PBS job object.
    2. The return will be a float which gives the cumulative energy usage for the job at the time of the call in kilowatt-hours (kWh). If no power usage information is available, None is returned.
  3. pmi_deactivate_profile(self, job)
    1. Inform the PMI that a job is no longer active. This would be used when a job is suspended or terminated. The parameter “job” is a PBS job object. If it is not specified, the pbs.event().job object will be used.
    2. The return type is bool where True indicates success and False indicates the request was made without an indication from the PMI if it was successful or not.
  4. pmi_query(self, query_type)
    1. Return information that matches a request type. The parameter “query_type” is used to specify what should be returned. The only value for query_type is PMI_QUERY_PROFILE, and the return will be a list of strings giving profile names supported by the PMI.
  5. pmi_connect(self, endpoint, port)
    1. Connect to the PMI. The parameter “endpoint” defaults to None and is a string which will be meaningful to the PMI. The parameter “port” defaults to None and is an integer. A typical usage would be “endpoint” specifying a hostname and “port” giving a network port for a network service connection.
    2. Currently the connection/disconnection will be done per hook instead of creating a long lasting session.
    3. Nothing is returned, the connection information is maintained in an instantiation of the Power class.
    4. If the endpoint or port parameters are not specified, the underlying code specific to the PMI will determine the connection details.
  6. pmi_disconnect(self)
    1. Disconnect from the PMI. There are no parameters needed since each instance of the Power class is associated to a backend power management interface.
  7. Exceptions
    1. InternalError - returned in cases where the underlying cause of a failure cannot be determined.
    2. BackendError - the backend PMI call was unsuccessful.
  8. Power module initialization
    1. A string can optionally be passed to specify the name of the PMI to be used (see A.1.11). By default, the type of PMI to be used will be determined automatically based on the type of hardware used.
5. Examples
  1. Activate a profile from a job specific event.
    Info
    icon false
    p = pbs.Power()
    p.pmi_connect(“power_master”)
    p.pmi_activate_profile(“LOW”)
    p.pmi_disconnect()
  2. Get profile name list.
    Info
    icon false
    import pbs
    p = pbs.Power()
    p.pmi_connect(port=3564)
    pnames = p.pmi_query(p.PMI_QUERY_PROFILE)
    p.pmi_disconnect()
  3. Deactivate profile on a specific job.
    Info
    icon false
    import pbs
    p = pbs.Power()
    badjob = pbs.server().job(“10”)
    p.pmi_connect()
    p.pmi_deactivate_profile(job=badjob)
    p.pmi_disconnect()
Interface #2
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Generically applicable server power_provisioning flag
4. Reference to more detail on the interface.
  1. The power_provisioning boolean server attribute will have a default of unset, be visible to all and changeable by an administrator. When it is set True, PMI operations may take place if allowed by power_enable flag (see A.1.10). If it is unset or set False, no PMI operations will take place on any vnode.
  2. Use qmgr to set the power_provisioning flag true or false. For example:
    Info
    icon false
    qmgr -c “set server power_provisioning = true”
Interface #3
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Generically applicable energy usage for a job
  1. Add a new attribute for a job: resources_used.energy
4. Reference to more detail on the interface.
  1. The type will be float.
  2. The units will be kWh. For example: resources_used.energy=64.2
  3. The resources_used.energy value will only be updated when PMI operations are allowed on the vnodes used by the job. The resources_used.energy value will not be seen in qstat -f output or server/accounting logs when PMI operations are not allowed on the node.
Interface #4
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Generically applicable resource “eoe”
  1. A new resource similar to “aoe” is added to both jobs and vnodes to specify the energy operational environment.
4. Reference to more detail on the interface.
  1. Is added to default resource list of scheduler in sched_config file.
  2. It is a non-consumable resource.
  3. It is of type resource, added to attribute resources_available. e.g. resources_available.eoe=”low,med,high”. It is a string array.
  4. Contains list of all power profile names that are available on a vnode. By default, resources_available.eoe is unset.
  5. The list is visible to all but settable only by manager.
  6. Job Resource_List.eoe per chunk in –l select as –l select=1:ncpus:eoe=low. This will request one chunk from a node with resource_available.eoe=low.
  7. Only one eoe value can be active on a vnode at a time.
  8. A job Resource_List.eoe may be requested in a select statement but no more than one distinct value for the requested eoe is currently supported. i.e. -lselect=1:ncpus=1:eoe=med+1:ncpus=2:eoe=med
  9. If a Job request is made with more than one value for eoe (I.e. –l select=1:eoe=low+1:eoe=high), it will be rejected by qsub with the error “qsub: only one value of eoe is allowed”.
  10. A value for resources_available.eoe will not be automatically set on the system(s) where the PBS server and scheduler are running.
  11. If both an aoe and eoe are set for a job, the aoe setting will be processed first by the scheduler.
  12. The scheduler will not preempt a job with eoe set using suspend or checkpoint.
Interface #5
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Generically applicable vnode attribute: current_eoe
4. Reference to more detail on the interface.
  1. Identifies the eoe active on a vnode. It is of type String. By default, it is unset. It is settable only by manager and visible to all.
  2. A job J1 running with a eoe setting X will cause the value of current_eoe to be set to X on the vnodes assigned to J1 that allow PMI operations.
  3. Manually changing current_eoe is unsupported.
  4. The scheduler can run a job requesting an eoe on vnodes with a current_eoe value that matches the job eoe.
  5. The scheduler can only run a job on a vnode where the current_eoe does not match the job eoe if no jobs are running on the vnode and PMI operations are allowed on the vnode.
  6. When a job ends the pmi_deactivate operation will take place if all the vnodes used by the job have no other jobs running and allow PMI operations. At this point, current_eoe will be unset on all the vnodes used by the job.
Interface #6
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Cray specific job attribute: pstate
4. Reference to more detail on the interface.
  1. Cray ALPS reservation setting for p-state. See Basil 1.4 documentation.
  2. It is of type String. By default, it is unset. It is settable and visible to all PBS users.
Interface #7
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Cray specific job attribute: pgov
4. Reference to more detail on the interface.
  1. Cray ALPS reservation setting for p-governor. See Basil 1.4 documentation.
  2. It is of type String. By default, it is unset. It is settable and visible to all PBS users.
Interface #8
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Cray specific job attribute: pcap_node
4. Reference to more detail on the interface.
  1. Cray capmc set_power_cap --node setting. See capmc documentation.
  2. It is of type Int. By default, it is unset. It is settable and visible to all PBS users.
  3. A negative value will result in an PBSE_BADATVAL error.
Interface #9
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Cray specific job attribute: pcap_accelerator
4. Reference to more detail on the interface.
  1. Cray capmc set_power_cap --accel setting. See capmc documentation.
  2. It is of type Int. By default, it is unset. It is settable and visible to all PBS users.
  3. A negative value will result in an PBSE_BADATVAL error.
Interface #10
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Generically applicable vnode power enable flag
4. Reference to more detail on the interface.
  1. The power_enable boolean vnode attribute will be unset by default, be visible to all and changeable by an administrator.
  2. Use qmgr to set the power_enable flag true or false. For example:
    Info
    icon false
    qmgr -c “set node bigbox power_enable = true”
  3. When it is set to True, PMI operations may take place on the vnode. If it is unset or set to False, no PMI operations are allowed to take place on the vnode.
Interface #11
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: Expose the hook PMI structure to allow additions to the supported PMI list.
4. Reference to more detail on the interface.
  1. The PBS “power” hook can be modified to specify a PMI name in the pbs.Power() instantiation in the init_power function. For example, the code below would cause the new file described in A.11.d.ii to be used by the hook:
    Info
    icon false
    power = pbs.Power(“ipmitool”)
  2. Python code patterned after the file PBS_EXEC/lib/python/altair/pbs/v1/_pmi_none.py must be placed in a file where none is replaced by the PMI name being implemented. For example:
    Info
    icon false
    # cd $PBS_EXEC/lib/python/altair/pbs/v1
    # cp _pmi_none.py _pmi_ipmitool.py
    # vi _pmi_ipmitool.py
  3. The defined functions must all be present: __init__, _pmi_connect, _pmi_disconnect, _pmi_get_usage, _pmi_query, _pmi_activate_profile, _pmi_deactivate_profile. These all have the same arguments as those in I.1.1 except the function name has an intial underbar ('_').
Interface #12
1. Visibility: Public
2. Change Control: Stable
3. Synopsis: Mom log using logjobmsg when a job ends and the value of current_eoe is unset.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 14:44:15;0008;pbs_python;Job;165.bigcray;PMI: reset current_eoe
Interface #13
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When the energy for a job on an SGI system is obtained, it will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/06/2014 18:35:26;0008;pbs_python;Job;4856.iceberg;SGI: energy 1.456kWh
Interface #14
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: The Cray capmc command invocations will be logged by MoM using LOG_DEBUG with the keyword “launch”.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 15:20:58;0006;pbs_python;Hook;pbs_python;Cray: 167.bigcray launch: /opt/cray/capmc/default/bin/capmc get_node_energy_counter --nids 0
Interface #15
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: Following a successful Cray capmc invocation, a message will be logged by MoM using LOG_WARNING if the time used by capmc is greater than 30 seconds.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python; 21.bigcray;launch: finished in 156 seconds
Interface #16
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If Cray capmc writes anything to stderr, the first line will be logged by MoM using LOG_WARNING after the “launch” message.
4. Reference to more detail on the interface.
  1. Cray has not documented the possible stderr output from capmc.
  2. Example:
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python; 21.bigcray;launch stderr: i fell and cannot get up
Interface #17
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When Cray capmc is run with the argument “get_node_energy_counter”, the node count is checked and if it is wrong, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. The same command will be run one additional time if an error is seen. No message will be logged for the first error. If an error occurs after the second attempt, a message is logged.
  2. For example:
    Info
    icon false
    11/19/2014 15:20:05;0008;pbs_python;Job;166.centos1;error: node count 2, should be 1
  3. The output from capmc should include a node count. If it does not, the messages will show “not set” instead of a number.
  4. Example:
    Info
    icon false
    11/19/2014 15:20:05;0008;pbs_python;Job;166.centos1;node count not set, should be 1

Interface #18

Visibility: Public
Change Control: Unstable
Synopsis: If Cray RUR is configured (see B.1.f), log messages will be logged by MoM using logjobmsg when a job ends.

Reference to more detail on the interface.

A message will show the energy used by each aprun run by a job and a job tally in Joules. For example:

Info

icon	false

11/19/2014 18:17:16;0008;pbs_python;Job;267.bigcray;Cray:RUR: {"apid":34876,"apid_energy":83876J,"job_energy":83876J}

11/19/2014 18:17:16;0008;pbs_python;Job;267.bigcray;Cray:RUR: {"apid":34972,"apid_energy":84272J,"job_energy":168148J}

11/19/2014 18:17:16;0008;pbs_python;Job;267.bigcray;Cray:RUR: {"apid":35234,"apid_energy":83194J,"job_energy":251342J}

Interface #19
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If Cray RUR is not configured, a log message will be logged by MoM using logjobmsg when a job ends.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 18:17:16;0008;pbs_python;Job;267.bigcray;Cray: no RUR data
Interface #20
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: At the end of a job on a Cray, the energy reported by capmc for the compute nodes used by the job will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/06/2014 18:35:26;0008;pbs_python;Job;156.bigcray;energy usage 554520J
Interface #21
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: The energy reported by capmc for the compute nodes used by a job on a Cray will be logged by MoM using logjobmsg periodically every 5 minutes as the job runs.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/06/2014 18:35:26;0008;pbs_python;Job;156.bigcray;Cray: get_usage: energy 346342J
Interface #22
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When the PMI on a Cray is initialized, MoM will log messages at LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 15:20:58;0006;pbs_python;Hook;pbs_python;Cray: init
    11/19/2014 15:20:58;0006;pbs_python;Hook;pbs_python;Cray: connect
Interface #23
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_get_usage is called for a job on a Cray, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: get_usage
Interface #24
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_query is called on a Cray, a message will be logged by MoM using LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 15:20:58;0006;pbs_python;Hook;pbs_python;Cray: query
Interface #25
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_activate_profile is called on a Cray, a message will be logged by MoM using LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python;Cray: 167.centos1 activate 'low'
Interface #26
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_activate_profile is called on a Cray but no compute nodes are allocated to the job, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: no compute nodes for power setting
Interface #27
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_activate_profile is called on a Cray and the job has pcap_node set, a message will be logged by MoM using logjobmsg showing the pcap_node value.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: pcap node 350
Interface #28
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_activate_profile is called on a Cray and the job has pcap_accelerator set, a message will be logged by MoM using logjobmsg showing the pcap_ accelerator value.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: pcap accel 250
Interface #29
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_activate_profile is called on a Cray and the job has neither pcap_node or pcap_accelerator set, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: no power cap to set
Interface #30
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_deactivate_profile is called on a Cray, a message will be logged by MoM using LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python;Cray: deactivate 167.centos1
Interface #31
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_deactivate_profile is called on a Cray but no compute nodes are allocated to the job, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: no compute nodes for power setting
Interface #32
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_deactivate_profile is called on a Cray and the job has pcap_node set, a message will be logged by MoM using logjobmsg showing the pcap_node value.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: remove pcap node 350
Interface #33
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_deactivate_profile is called on a Cray and the job has pcap_accelerator set, a message will be logged by MoM using logjobmsg showing the pcap_ accelerator value.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: remove pcap accel 250
Interface #34
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_deactivate_profile is called on a Cray and the job has neither pcap_node or pcap_accelerator set, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: no power cap to remove
Interface #35
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If Cray RUR is configured but the file created by the output plugin has a permission problem, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. The file owner must be 0 and it must not be writable by other.
  2. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: RUR file: /var/spool/PBS/spool/167.centos1.rur should only be writable by root
Interface #36
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If Cray RUR is configured but the file created by the output plugin can be read, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray: reading RUR file: /var/spool/PBS/spool/167.centos1.rur
Interface #37
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If the file created by the RUR output plugin can be read but the energy value cannot be parsed, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. A python exception error string will be output as part of the message.
  2. Example
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray:RUR: energy_used not found: unexpected EOF while parsing
Interface #38
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If the file created by the RUR output plugin can be read but the Cray energy RUR plugin has not been enabled, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray:RUR: warning: energy plugin not enabled by RUR
Interface #39
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When the energy for a job is successfully obtained from RUR, MOM will log one of three possible messages using logjobmsg.
4. Reference to more detail on the interface.
  1. If no energy value was obtained from capmc:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray:RUR: energy 4.234kWh
  2. If the energy value from capmc was smaller than what was obtained from RUR:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray:RUR: energy 4.234kWh replaces capmc energy 4.1432kWh
  3. If the energy value from capmc was greater than or equal to what was obtained from RUR:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;Cray:RUR: energy 4.234kWh last capmc usage 4.2432kWh
Interface #40
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When the PMI on an SGI is initialized, MoM will log messages at LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 15:20:58;0006;pbs_python;Hook;pbs_python;SGI: init
    11/19/2014 15:20:58;0006;pbs_python;Hook;pbs_python;SGI: connect
Interface #41
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_get_usage is called for a job on an SGI, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1;SGI: get_usage
Interface #42
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_query is called on an SGI, a message will be logged by MoM using LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 15:20:58;0006;pbs_python;Hook;pbs_python;SGI: query
Interface #43
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_activate_profile is called on an SGI, a message will be logged by MoM using LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python;SGI: 167.centos1 activate '450W'
Interface #44
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When pmi_deactivate_profile is called on an SGI, a message will be logged by MoM using LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example:
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python;SGI: deactivate
Interface #45
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If any PMI operation is attempted for a job with a vnode assigned that does not have power_enable=True, a message will be logged by MoM using logjobmsg.
4. Reference to more detail on the interface.
  1. Example
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1; power functionality is disabled on vnode v12
Interface #46
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If the PMI hook is run with an unexpected event, MoM will log a message at LOG_WARNING.
4. Reference to more detail on the interface.
  1. Example
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python; Event not serviceable for power provisioning.
Interface #47
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: When the PMI hook handles the EXECHOST_STARTUP event and the MOM is running on the same host as the pbs_server or pbs_sched, MoM will log a message at LOG_DEBUG.
4. Reference to more detail on the interface.
  1. Example
    Info
    icon false
    11/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python; Provisioning cannot be enabled on this host.
Interface #48
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If any PMI operation at job end throws a python exception, a message will be logged by MoM using logjobmsg showing the exception string.
4. Reference to more detail on the interface.
  1. Example
    Info
    icon false
    11/19/2014 17:24:21;0008;pbs_python;Job;167.centos1; socket.error: [Errno 111] Connection refused
Interface #49
1. Visibility: Public
2. Change Control: Unstable
3. Synopsis: If pmi_activate_profile throws either of the python exceptions defined in A.1.d.vii a message will be logged by MoM at LOG_WARNING.
4. Reference to more detail on the interface.
  1. If the exception is BackendError, pmi_query is called to reset the eoe value for the natural vnode for the MoM.
  2. Example
    Info
    icon false
    1/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python; PMI:activate: set eoe: low,med,high
  3. If the exception is InternalError, the natural vnode for the MoM will be set offline.
  4. Example
    Info
    icon false
    1/19/2014 17:24:18;0006;pbs_python;Hook;pbs_python; PMI:activate: set myself offline

...

Versions Compared

Old Version 21

New Version 22

Key