[mpiwg-sessions] notes from today's call

[rhc at open-mpi.org]

Hello all

I followed up on my AR from the meeting to check with the RMs on how they handle unique identifiers for procs on different clusters. As we had surmised, they provide a string name for each cluster, and they agreed that adding that to the PMIx nspace would be a reasonable path forward.

I have accordingly updated the PMIx RFC (https://github.com/pmix/RFCs/pull/3 <https://github.com/pmix/RFCs/pull/3>) to include three new attributes:

* PMIX_CONNECT_ID_MODIFIER_PREPEND: modify the nspace returned by the host by prepending the given modifier to the nspace string. This allows the application to "tag" the connected group in a recognizable fashion.

* PMIX_CONNECT_ID_MODIFIER_APPEND: modify the nspace returned by the host by appending the given modifier to the nspace string. This allows the application to "tag" the connected group in a recognizable fashion.

* PMIX_CONNECT_ID_REQUEST: request that the given identifier be used as the assigned nspace for the connected group. The "required" flag in the directive can be used to indicate that this identifier is required (i.e., the host RM must use it for the group, returning an error if it is already in use) as opposed to requested (i.e., the host RM can substitute its own unique identifier if the specified one is already in use).

I also added the PMIX_CLUSTER_ID attribute to the list of information to be provided by the RM at process start - you can see the list here:
https://github.com/pmix/pmix/wiki/2.8-Pmix-Server-Data-Requirements <https://github.com/pmix/pmix/wiki/2.8-Pmix-Server-Data-Requirements>

Ralph

> On Oct 16, 2017, at 11:48 AM, Pritchard Jr., Howard <howardp at lanl.gov> wrote:
> 
> Hi Folks,
> 
> Notes from today’s call are on the wiki:
> 
> https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-16-webex <https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-16-webex>
> 
> Howard
> 
> -- 
> Howard Pritchard
> B Schedule
> HPC-ENV
> Los Alamos National Laboratory
> 
> _______________________________________________
> mpiwg-sessions mailing list
> mpiwg-sessions at lists.mpi-forum.org
> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-sessions/attachments/20171018/ed76ce5b/attachment.html>