October 2017 - mpiwg-sessions - mailman3.cels.anl.gov

Next meeting - today - midday Eastern US time
by HOLMES Daniel 30 Oct '17

30 Oct '17

Hi all, The next meeting for the Sessions WG is today at midday Eastern US time. The connection details for the call can be found here: http://mpi-forum.epcc.ed.ac.uk/mpiwg-sessions.php The wiki for the working group, including documentation about Sessions and minutes of previous meetings is here: https://github.com/mpiwg-sessions/sessions-issues/wiki All: I’d like to have something concrete and interesting to say about the progress/state of this WG at the MPI BoF during SC17. That gives us 2 more meetings including today’s! Cheers, Dan. The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

Next meeting - today - midday Eastern US time
by HOLMES Daniel 23 Oct '17

23 Oct '17

Hi all, The next meeting for the Sessions WG is today at midday Eastern US time. The connection details for the call can be found here: http://mpi-forum.epcc.ed.ac.uk/mpiwg-sessions.php The wiki for the working group, including documentation about Sessions and minutes of previous meetings is here: https://github.com/mpiwg-sessions/sessions-issues/wiki Ralph: thanks for your presentation last week. This week I’m intending to return to our previous discussions around sessions+endpoints and global vs local operation scope. The WG will look at the PMIx changes triggered by last week’s conversation (probably after SC17) and will bear in mind what PMIx can implement for us but we should focus on what value-add MPI can bring to users of MPI. All: I’d like to have something concrete and interesting to say about the progress/state of this WG at the MPI BoF during SC17. That gives us 3 more meetings including today’s! Cheers, Dan. The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

Re: [mpiwg-sessions] notes from today's call
by rhc＠open-mpi.org 20 Oct '17

20 Oct '17

I have updated both the RFC (including adding example code on how to make multi-cluster connect work) and the prototype code per the below comments. Comments welcome! Ralph > On Oct 19, 2017, at 10:43 AM, rhc(a)open-mpi.org wrote: > > In thinking about this more, I realized that these new attributes won’t solve the problem raised by Martin. Instead, they were focused on giving the application the ability to define the nspace name - doesn’t help with the issue of specifying procs from different clusters in the PMIx_Connect call. > > After circling around again with the RM folks, a couple of things were resolved: > > 1. They really cannot support user-defined nspaces as the nspace directly correlates to their assignment of a “jobid” to the operation. Trying to build correlation tables to map a user definition to the RM’s identifier would be overly burdensome. > > 2. They are willing to standardize on prepending the cluster ID string to the nspace when referencing remote clusters. We tentatively agreed on using a colon ‘:’ as the delimiter. So when referencing a proc in nspace “bar” on cluster “foo”, you would provide an nspace of “foo:bar”. If no cluster ID is provided, then all parties will assume the nspace refers to the local cluster. > > 3. For the issue of having multiple, parallel PMIx_Connect operations spanning identical procs, we agreed to define an attribute PMIX_CONNECT_ID (string) whereby the application can provide its own unique “tag” for that operation. When provided, the RM and PMIx libraries will use this tag to separate out the operations. Note that all procs participating in the connect operation must provide the same tag. > > I will update the RFC accordingly, and provide a couple of new macros in pmix_common.h to make insertion and parsing of the cluster ID to/from the nspace easier. > > HTH > Ralph > >> On Oct 18, 2017, at 8:51 PM, rhc(a)open-mpi.org <mailto:[email protected]> wrote: >> >> 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(a)lanl.gov <mailto:[email protected]>> 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(a)lists.mpi-forum.org <mailto:[email protected]> >>> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions> >> _______________________________________________ >> mpiwg-sessions mailing list >> mpiwg-sessions(a)lists.mpi-forum.org <mailto:[email protected]> >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions >

1 0

Re: [mpiwg-sessions] notes from today's call
by rhc＠open-mpi.org 19 Oct '17

19 Oct '17

In thinking about this more, I realized that these new attributes won’t solve the problem raised by Martin. Instead, they were focused on giving the application the ability to define the nspace name - doesn’t help with the issue of specifying procs from different clusters in the PMIx_Connect call. After circling around again with the RM folks, a couple of things were resolved: 1. They really cannot support user-defined nspaces as the nspace directly correlates to their assignment of a “jobid” to the operation. Trying to build correlation tables to map a user definition to the RM’s identifier would be overly burdensome. 2. They are willing to standardize on prepending the cluster ID string to the nspace when referencing remote clusters. We tentatively agreed on using a colon ‘:’ as the delimiter. So when referencing a proc in nspace “bar” on cluster “foo”, you would provide an nspace of “foo:bar”. If no cluster ID is provided, then all parties will assume the nspace refers to the local cluster. 3. For the issue of having multiple, parallel PMIx_Connect operations spanning identical procs, we agreed to define an attribute PMIX_CONNECT_ID (string) whereby the application can provide its own unique “tag” for that operation. When provided, the RM and PMIx libraries will use this tag to separate out the operations. Note that all procs participating in the connect operation must provide the same tag. I will update the RFC accordingly, and provide a couple of new macros in pmix_common.h to make insertion and parsing of the cluster ID to/from the nspace easier. HTH Ralph > On Oct 18, 2017, at 8:51 PM, rhc(a)open-mpi.org wrote: > > 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(a)lanl.gov <mailto:[email protected]>> 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(a)lists.mpi-forum.org <mailto:[email protected]> >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions > > _______________________________________________ > mpiwg-sessions mailing list > mpiwg-sessions(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions

1 0

Re: [mpiwg-sessions] notes from today's call
by rhc＠open-mpi.org 18 Oct '17

18 Oct '17

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(a)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(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions

1 0

notes from today's call
by Pritchard Jr., Howard 16 Oct '17

16 Oct '17

Hi Folks, Notes from today’s call are on the wiki: https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-16-webex Howard -- Howard Pritchard B Schedule HPC-ENV Los Alamos National Laboratory

1 0

Next meeting - today - midday Eastern US time
by HOLMES Daniel 16 Oct '17

16 Oct '17

Hi all, The next meeting for the Sessions WG is today at midday Eastern US time. The connection details for the call can be found here: http://mpi-forum.epcc.ed.ac.uk/mpiwg-sessions.php The wiki for the working group, including documentation about Sessions and minutes of previous meetings is here: https://github.com/mpiwg-sessions/sessions-issues/wiki Cheers, Dan. The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0

Re: [mpiwg-sessions] notes from today's call
by rhc＠open-mpi.org 03 Oct '17

03 Oct '17

For those interested, there is a PMIx RFC that I restarted relevant to this work: https://github.com/pmix/RFCs/pull/3 <https://github.com/pmix/RFCs/pull/3> > On Oct 2, 2017, at 1:59 PM, rhc(a)open-mpi.org wrote: > > Yep, I’ll be there! > >> On Oct 2, 2017, at 12:48 PM, HOLMES Daniel <d.holmes(a)epcc.ed.ac.uk <mailto:[email protected]>> wrote: >> >> Hi Ralph, >> >> Thanks, that’s helpful. We can discuss this next week, if you can join. >> >> Cheers, >> Dan. >> >>> On 2 Oct 2017, at 19:05, rhc(a)open-mpi.org <mailto:[email protected]> wrote: >>> >>> Hi folks >>> >>> Sorry I missed today’s call. FWIW, I have posted the PMIx presentation from EuroMPI that was mentioned at the meeting. >>> >>> https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.… <https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.…> >>> >>> https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.… <https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.…> >>> >>> Ralph >>> >>>> On Oct 2, 2017, at 9:59 AM, Pritchard Jr., Howard <howardp(a)lanl.gov <mailto:[email protected]>> wrote: >>>> >>>> Hi Folks, >>>> >>>> I took some notes for today’s webex: >>>> >>>> https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-02-webex <https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-02-webex> >>>> >>>> Feel free to add/correct >>>> >>>> Howard >>>> >>>> -- >>>> Howard Pritchard >>>> B Schedule >>>> HPC-ENV >>>> Los Alamos National Laboratory >>>> >>>> _______________________________________________ >>>> mpiwg-sessions mailing list >>>> mpiwg-sessions(a)lists.mpi-forum.org <mailto:[email protected]> >>>> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions> >>> _______________________________________________ >>> mpiwg-sessions mailing list >>> mpiwg-sessions(a)lists.mpi-forum.org <mailto:[email protected]> >>> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions> >> The University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> _______________________________________________ >> mpiwg-sessions mailing list >> mpiwg-sessions(a)lists.mpi-forum.org <mailto:[email protected]> >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions > > _______________________________________________ > mpiwg-sessions mailing list > mpiwg-sessions(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions

1 0

Re: [mpiwg-sessions] notes from today's call
by rhc＠open-mpi.org 02 Oct '17

02 Oct '17

Yep, I’ll be there! > On Oct 2, 2017, at 12:48 PM, HOLMES Daniel <d.holmes(a)epcc.ed.ac.uk> wrote: > > Hi Ralph, > > Thanks, that’s helpful. We can discuss this next week, if you can join. > > Cheers, > Dan. > >> On 2 Oct 2017, at 19:05, rhc(a)open-mpi.org <mailto:[email protected]> wrote: >> >> Hi folks >> >> Sorry I missed today’s call. FWIW, I have posted the PMIx presentation from EuroMPI that was mentioned at the meeting. >> >> https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.… <https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.…> >> >> https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.… <https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.…> >> >> Ralph >> >>> On Oct 2, 2017, at 9:59 AM, Pritchard Jr., Howard <howardp(a)lanl.gov <mailto:[email protected]>> wrote: >>> >>> Hi Folks, >>> >>> I took some notes for today’s webex: >>> >>> https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-02-webex <https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-02-webex> >>> >>> Feel free to add/correct >>> >>> Howard >>> >>> -- >>> Howard Pritchard >>> B Schedule >>> HPC-ENV >>> Los Alamos National Laboratory >>> >>> _______________________________________________ >>> mpiwg-sessions mailing list >>> mpiwg-sessions(a)lists.mpi-forum.org <mailto:[email protected]> >>> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions <https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions> >> _______________________________________________ >> mpiwg-sessions mailing list >> mpiwg-sessions(a)lists.mpi-forum.org <mailto:[email protected]> >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions > > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. > _______________________________________________ > mpiwg-sessions mailing list > mpiwg-sessions(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions

1 0

Re: [mpiwg-sessions] notes from today's call
by HOLMES Daniel 02 Oct '17

02 Oct '17

Hi Ralph, Thanks, that’s helpful. We can discuss this next week, if you can join. Cheers, Dan. On 2 Oct 2017, at 19:05, rhc(a)open-mpi.org<mailto:[email protected]> wrote: Hi folks Sorry I missed today’s call. FWIW, I have posted the PMIx presentation from EuroMPI that was mentioned at the meeting. https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.… https://github.com/pmix/publications/blob/master/EuroMPI-2017-Presentation.… Ralph On Oct 2, 2017, at 9:59 AM, Pritchard Jr., Howard <howardp(a)lanl.gov<mailto:[email protected]>> wrote: Hi Folks, I took some notes for today’s webex: https://github.com/mpiwg-sessions/sessions-issues/wiki/2017-10-02-webex Feel free to add/correct Howard -- Howard Pritchard B Schedule HPC-ENV Los Alamos National Laboratory _______________________________________________ mpiwg-sessions mailing list mpiwg-sessions(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions _______________________________________________ mpiwg-sessions mailing list mpiwg-sessions(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

1 0