- Adds attributes to broaden logging support
- Defines a “gateway” server type
Extension of PMIx Logging Support
The PMIx_Log API supports requests for logging information to a variety of channels. Initial support was only for stdout/stderr – this RFC extends that support to additional channels such as syslog and smtp.
Copyright (c) 2018 Intel, Inc. All rights reserved.
This document is subject to all provisions relating to code contributions to the PMIx community as defined in the community’s LICENSE file. Code Components extracted from this document must include the License text as described in that file.
RFC0010 added a new PMIx_Log_nb API for requesting logging of provided data in some global data store or to standard output locations (e.g., stderr or syslog), subject to available services from the host environment. A limited number of initial keys were provided by which the logging request could direct the data to specific channels on an as-available basis, and the host RM interface was extended through the addition of a “log” interface by which client requests that are not directly supported by the PMIx library can be passed to the host RM for handling – e.g., when the logging data is directed to the stderr or stdout channels.
The illustration below highlights some of the capabilities provided by the extended logging support. Note that the illustration is not intended to be comprehensive in its coverage as the number of possible use-cases is too large to capture in a single drawing.
Supported uses include:
Writing of messages to syslog, both local (using the PMIX_LOG_LOCAL_SYSLOG attribute) or on the syslog of some central server designated for this purpose. The PMIx client will send the logging request to its local server. If the PMIX_LOG_LOCAL_SYSLOG attribute is included in the request, then the PMIx server will immediately output the message to the local syslog. If not, or if the PMIX_LOG_GLOBAL_SYSLOG attribute is specified, then the PMIx server will “upcall” the request to its host RM daemon. It is the responsibility of the host RM daemon to identify and transfer the provided data to the appropriate location – upon arrival, the RM can use the PMIx_Log function to deliver the data to the local syslog on that node, or can write the data to syslog itself. Attributes for setting the desired syslog priority are provided – the default is set to LOG_INFO indicating reporting of an informational message
Sending notifications via email (or other channels) to a designated user. Application users may wish to be notified of completion of their application, receive periodic progress reports, or be notified of a problem that merits attention. PMIx itself includes support for some of the more popular channels – requests for unsupported channels are referred to the host RM for processing, with an error returned if the requested channel is not available in the host environment
Outputting tagged log messages to stdout or stderr of the application, or a connected tool. Where supported, an alternative output stream (possibly directed to a dedicated log file) may be specified. Messages may be tagged (via the PMIX_LOG_TAG_OUTPUT} attribute) as flowing via the PMIx_Log API to differentiate them from the application’s normal output. In addition, messages may be timestamped (PMIX_LOG_TIMESTAMP_OUTPUT) or output in XML format (PMIX_LOG_XML_OUTPUT)
Storing status updates in the job record using the PMIX_LOG_JOB_RECORD attribute. Resource managers nearly always maintain a record of the jobs they schedule and execute. This includes information on the time spent waiting for allocation, priority of the request, identity of the requestor, name/path of the executable and/or job script, etc. Historically, users have had to record status information on their application (e.g., computational progress) in files which are subsequently stored in persistent storage. PMIx_Log offers the option (where supported) of injecting such status reports directly into the job record, thus providing a single, time sequential record of the job’s execution.
Note that system libraries can also use this feature to record job-affecting events (e.g., network failures) that might have impacted the application during its execution, perhaps linking them to more detailed information stored in a RAS database.
Note that data can be “logged” without specifying the output channel. In this case, the PMIx library will default to logging a copy of the data to each available channel (in the reference implementation, this is done by MCA parameter in addition to the usual build/configuration constraints). The caller can optionally control the logging behavior by providing multiple channel attributes in order of desired priority, subject to the availability of the specified channel. For example, an application could ask that data be emailed to a given user, or logged to a global syslog, or logged to local syslog by specifying first the PMIX_LOG_EMAIL attribute, followed by the PMIX_LOG_GLOBAL_SYSLOG and the PMIX_LOG_LOCAL_SYSLOG attributes, with the PMIX_LOG_ONCE attribute being included to indicate that only one log channel should be used. If PMIX_LOG_ONCE is not indicated, then the data will be logged to all three channels. In this case:
- PMIX_ERR_PARTIAL_COMPLETION is returned if any channel fails to log as requested, but others succeed;
- PMIX_ERR_OPERATION_FAILED is returned if all fail; and
- PMIX_SUCCESS is returned if all succeed.
This provides flexibility with minimal code complexity when operating in multiple environments that support differing output channels.
Logging attributes can also utilize the “required” flag in the pmix_info_t structure to indicate that the data must be logged via the specified channel. If given, failure to complete the operation on that channel will result in return of the PMIX_ERR_OPERATION_FAILED error. Otherwise, use of a given channel is considered “optional” and errors are reported according to the above rules.
Specifying a prioritized list of logging channels on each call to PMIx_Log can impact the performance of the API itself as it requires the PMIx library to scan available channels to create an ordered list, and this might in turn require multiple passes over the available options. The PMIx reference library provides an MCA parameter to help reduce this impact. A user can control the default order of channel delivery by setting the “plog_base_order” MCA parameter to a comma-delimited, prioritized list of channel names based on the corresponding attribute by extracting the characters following “PMIX_LOG_”, as follows:
- PMIX_LOG_LOCAL_SYSLOG – “local_syslog”
- PMIX_LOG_GLOBAL_SYSLOG – “global_syslog”
- PMIX_LOG_EMAIL} – “email”
and so on. Marking a given channel in the list as “required” can be done by adding “:req” to the channel name – e.g., plog_base_order = “local_syslog:req,global_syslog,email”. Parsing of this MCA parameter is case-insensitive, and the parser will accept any “required” flag that starts with “req” – e.g., “reqd” and “required”. Similarly, the PMIX_LOG_ONCE attribute can be set by default using the “plog_base_log_once” MCA parameter. Note that this is specific to the PMIx reference library and is not part of the standard – users are advised to check their local implementation for similar support.
Channels that are not recognized by the PMIx library will automatically be directed to the host RM for processing. This allows for RM-proprietary channel support without committing those channel names to the PMIx Standard.
The proposed changes covered by this RFC are organized into four categories: introduction of a new server “type”, API additions, new attributes, and clarification of behavior expected from prior attributes.
This RFC introduces the concept of a “gateway” server – i.e., a server designated at time of PMIx_server_init using the new PMIX_SERVER_GATEWAY attribute. Gateway servers act as routers for requests that cannot be serviced on backend nodes. Typical examples include logging to email or syslog on a central system management server.
#define PMIX_SERVER_GATEWAY "pmix.srv.gway" // (bool) Server is acting as a gateway for PMIx requests // that cannot be serviced on backend nodes // (e.g., logging to email)
One new API, a blocking form of the earlier PMIx_Log_nb API, is proposed:
PMIX_EXPORT pmix_status_t PMIx_Log(const pmix_info_t data, size_t ndata, const pmix_info_t directives, size_t ndirs);
In addition, a comment in pmix_server.h was modified to clarify the required behavior of the pmix_server_log_fn_t server module function:
/* Log data on behalf of a client. Calls to the host thru this * function must _NOT_ call the PMIx_Log API as this can * trigger an infinite loop. Instead, the implementation must * perform one of three operations: * * (a) transfer the data+directives to a "gateway" server * where they can be logged. Gateways are designated * servers on nodes (typically service nodes) where * centralized logging is supported. The data+directives * may be passed to the PMIx_Log API once arriving at * that destination. * * (b) transfer the data to a logging channel outside of * PMIx, but directly supported by the host * * (c) return an error to the caller indicating that the * requested action is not supported */
New attributes covered by this RFC are shown below along with their intended usage as data vs directives. Note that data attributes specify a channel and the information to be logged via that channel, while directives affect the behavior of the API itself:
PMIX_LOG_LOCAL_SYSLOG [DATA]: (char*) log msg to local syslog – defaults to INFO priority
PMIX_LOG_GLOBAL_SYSLOG [DATA]: (char*) forward data to a “gateway” server and log msg to that syslog
PMIX_LOG_JOB_RECORD [DATA]: (char*) log the provided message to the RM’s job record
PMIX_LOG_SYSLOG_PRI [DIRECTIVE]: (int) specify syslog priority level
PMIX_LOG_GENERATE_TIMESTAMP [DIRECTIVE]: (bool) request that PMIx generate and add a timestamp to the data being logged
PMIX_LOG_TAG_OUTPUT [DIRECTIVE]: (bool) label the output stream with the channel name (e.g., “stdout”)
PMIX_LOG_XML_OUTPUT [DIRECTIVE]: (bool) print the output stream in xml format
PMIX_LOG_ONCE [DIRECTIVE]: (bool) only log this once using whichever channel can first support it
PMIX_LOG_EMAIL_SENDER_ADDR [DIRECTIVE]: (char*) return email address of sender
PMIX_LOG_EMAIL_SERVER [DIRECTIVE]: (char*) hostname (or IP addr) of estmp server
PMIX_LOG_EMAIL_SRVR_PORT [DIRECTIVE]: (int32_t) port the email server is listening to
In addition, a query attribute was added by which a user can request the list of available channels:
#define PMIX_QUERY_LOG_CHANNELS "pmix.qry.lchans" // (char*) comma-delimited list of available logging channels
The definition and usage of several existing attributes have been clarified for this RFC. Updated definitions include:
PMIX_LOG_SYSLOG: changed default priority to INFO priority, and specified that it will log to global syslog if available, otherwise to local syslog
PMIX_LOG_EMAIL: data type corrected to (pmix_data_array_t*)
Also clarified are existing attributes to be used in the data array versus the directives array of the PMIx_Log APIs. A list of data attributes includes:
- PMIX_LOG_SYSLOG, PMIX_LOG_LOCAL_SYSLOG, PMIX_LOG_GLOBAL_SYSLOG – log the provided string to the specified syslog
- PMIX_LOG_STDOUT, PMIX_LOG_STDERR – log the provided string to the indicated output channel. The output will appear on a gateway server
- PMIX_LOG_EMAIL – log via email based on array of pmix_info_t containing directives and message
- PMIX_LOG_EMAIL_MSG – body of the email message to be sent. Note that in the case of the email channel, the body of the message must be passed in the pmix_pointer_array_t of the PMIX_LOG_EMAIL data attribute
The list of directives includes:
- PMIX_LOG_EMAIL_ADDR, PMIX_LOG_EMAIL_SUBJECT – the address and subject fields for the provided email
Advice to users:
The available channel support on a system can be queried via the PMIx_Query_nb API using the PMIX_QUERY_LOG_CHANNELS key should the application developer wish to tailor their code accordingly – this will always report the channels directly supported by the PMIx library. However, channels supported by the host RM will be included only if the RM itself supports such queries.
The PMIx_Log API should never be used for streaming data as it is not a “performant” transport and can perturb the application since it involves the local PMIx server and host RM daemon.
There is some ambiguity regarding what information is provided in the “data” parameter vs the “directives” parameter when calling PMIx_Log. In general, information that is to be included in the log should be provided in the “data” array. Examples would include:
PMIX_INFO_LOAD(&data, PMIX_LOG_STDOUT, "my message string", PMIX_STRING); PMIX_INFO_LOAD(&data, PMIX_LOG_STDERR, "my error message", PMIX_STRING);
Note that in the above examples, the attribute key defines the channel to be used for the provided data.
On the other hand, “directives” should be used to request behaviors of the PMIx_Log function. Examples might include:
PMIX_INFO_LOAD(&directives, PMIX_LOG_GENERATE_TIMESTAMP, NULL, PMIX_BOOL); PMIX_INFO_LOAD(&directives, PMIX_LOG_XML_OUTPUT, NULL, PMIX_BOOL); PMIX_INFO_REQUIRED(&directives);
The first example instructs PMIx_Log to generate a timestamp indicating when the log message was created, and to include that in the log. The second example requires that the log be written in XML format – an error must be returned if XML output support is not available.
Advice to implementers:
Calls relayed to the host thru the pmix_server_log_fn_t function provided in the pmix_server_module must NOT call the PMIx_Log API as this can result in an infinite loop. Instead, the implementation must perform one of three operations: * transfer the data+directives to a “gateway” server where they can be logged. Gateways are designated servers on nodes (typically service nodes) where centralized logging is supported (e.g., writing to a global syslog). The data+directives may be passed to the PMIx_Log API once arriving at that destination. If the PMIx server cannot support the provided request, it will call up to the host for final disposition – this is why the host must not call back into the server.
transfer the data to a logging channel outside of PMIx, but directly supported by the host
return an error to the caller indicating that the requested action is not supported
A complete PMIx implementation shall respond to PMIx_Query_info_nb calls requesting logging channels supported by the RM with a comma-delimited string of channel keys – e.g., “pmix.log.lsys,pmix.log.email”, indicating that PMIX_LOG_LOCAL_SYSLOG and PMIX_LOG_EMAIL are supported by including the value of those keys in the returned string.
Ralph H. Castain