February 2020 - mpi-forum - mailman3.cels.anl.gov

Re: [Mpi-forum] Time To Open Source MPI
by Wesley Bland 03 Feb '20

03 Feb '20

I really want to emphasize how little work this should be for each person. For people with lots of PRs (like you), I estimate it’ll be less than 15 minutes before the meeting and less than 15 minutes afterward. For people with no open pull requests, it’s 0 minutes. If people are having trouble, I can do “almost” everything for you (other than clicking the delete and fork buttons). I’m asking for help here because I’d rather make a small amount for a handful of people instead of a lot of work for just me. This is also one of the reasons I want to do this in person, so I can help those having trouble. The reason we want to do it now is because this only became a problem at the last meeting when we broke the testing infrastructure. We could keep pushing this back, but in the meantime, we won’t be getting the benefit of that testing that we’ve relied on for a while to help make sure that Bill has an easier time of merging our pull requests (which will be even more important as we start to finish up these votes). We didn’t make this decision just to give people more work and I spent a fair amount of time making this as painless for everyone as possible. However, unlike some of the other transitions that we’ve made in the past (e.g. SVN -> Git), we also didn’t have the benefit of a long run-up to make this change. Thanks, Wesley > On Feb 3, 2020, at 1:36 PM, HOLMES Daniel <d.holmes(a)epcc.ed.ac.uk> wrote: > > Hi Wesley, > >> This change really won’t be as painful as it sounds > > Then why do I have to do a bunch of unexpected/unscheduled backup and book-keeping work before an arbitrarily chosen deadline? I’m not sure that springing this surprise on folks is the wisest course of action. > > Cheers, > Dan. > — > Dr Daniel Holmes PhD > Architect (HPC Research) > d.holmes(a)epcc.ed.ac.uk <mailto:[email protected]> > Phone: +44 (0) 131 651 3465 > Mobile: +44 (0) 7940 524 088 > Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT > — > The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. > — > >> On 3 Feb 2020, at 16:02, Wesley Bland via mpi-forum <mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]>> wrote: >> >> Because in the meantime, our testing remains broken and we don’t have another solution to fix it at the moment. We really want to have that testing fix. >> >> This change really won’t be as painful as it sounds. There’s almost no Git commands required. No rebasing/merging/etc. >> >>> On Feb 3, 2020, at 9:57 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de <mailto:[email protected]>> wrote: >>> >>> Why aren't we doing this when we finished 4.0, i.e. merged all the voted in >>> pull requests into the standard? >>> >>> ----- Original Message ----- >>>> From: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]>> >>>> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]>> >>>> Cc: "Wesley Bland" <work(a)wesbland.com <mailto:[email protected]>> >>>> Sent: Monday, February 3, 2020 4:38:48 PM >>>> Subject: [Mpi-forum] Time To Open Source MPI >>> >>>> Hi folks, >>>> >>>> ** Look at the numbered list for your action items before 2020-02-18! ** >>>> >>>> Since we moved from Subversion to GitHub, there’s been a back and forth on >>>> whether the MPI Standard Source code should be open source or closed source. As >>>> you know (since most of you have access to it, we decided to keep the standard >>>> closed for a few reasons (avoiding rogue copies of the Standard was a big one), >>>> but recently, the scales have tipped back toward open sourcing and after >>>> talking to Bill and Martin some more, we think it’s finally time to open up the >>>> MPI Standard repository. Specifically, these are the issues that get addressed >>>> by moving to a public repository: >>>> >>>> * Participation to the forum has a barrier to entry (i.e. me) >>>> * Our current automated testing system is broken and will not be fixed >>>> * We rely on special dispensation from GitHub for free, private repositories >>>> >>>> I’ll be discussing this in more detail in Portland, but I want to make folks >>>> aware that this is coming now because it will have some impact on people who >>>> are actively working on text proposals. The mitigations here should be pretty >>>> straightforward and I have both slides (for a high level) and a wiki page (for >>>> details) on what’s happening and what you need to do about it. >>>> >>>> The short version for the purpose of this email and your action item leading up >>>> the forum next week is to do two thing s: >>>> >>>> 1. Back up your branches. >>>> 2. Make a note for each of your open pull requests on where the are and what >>>> issues they’re attached to. >>>> >>>> Detailed notes and the slides I’ll present in Portland on how to do this are >>>> here: [ >>>> https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository <https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository> | >>>> https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository <https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository> ] >>>> >>>> The plan is for me to flip this switch DURING THE FEBRUARY MEETING! This should >>>> not disrupt any readings for the meeting itself as none of the pull requests >>>> will actually be deleted, but they will all become stale and we’ll need to >>>> re-open new ones. The main benefit of doing this during the meeting is that >>>> if/when anyone has trouble, I’ll be there in person to provide live help to >>>> anyone else that’s there (sorry, Marc-Andre, you’ll need to follow my slides >>>> remotely \uD83D\uDE00). >>>> >>>> Please email me if you have questions or concerns. If there’s enough demand, I’d >>>> even be willing to do a short Virtual Meeting on this on Wednesday. >>>> >>>> Thanks, >>>> Wesley >>>> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> >>>> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >>> >>> -- >>> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de <mailto:[email protected]> . >>> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 . >>> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 . >>> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner <http://www.hlrs.de/people/rabenseifner> . >>> Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) . >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> >> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >

1 0

Re: [Mpi-forum] #153 Re: REMINDER: Planing for the MPI Forum Meeting in February (DEADLINE February 4th)
by Rolf Rabenseifner 03 Feb '20

03 Feb '20

Hi all, I had to do a small bugfix in #153 Bug in MPI_NEIGHBOR_ALLTOALL--1 or 2 processes in the cyclic Cartesian case Therefore latest pdf for errata issue #153 is: https://github.com/mpi-forum/mpi-issues/files/4149883/mpi-report-issue153-n… Issue #153: https://github.com/mpi-forum/mpi-issues/issues/153 PR153: https://github.com/mpi-forum/mpi-standard/pull/153 It is now really ready for reading and voting. Best regards Rolf ----- Original Message ----- > From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Cc: "Martin Schulz" <schulzm(a)in.tum.de> > Sent: Friday, January 31, 2020 12:08:29 AM > Subject: #153 Re: [Mpi-forum] REMINDER: Planing for the MPI Forum Meeting in February (DEADLINE February 4th) > Dear Martin and all together, > > Errata issue https://github.com/mpi-forum/mpi-issues/issues/153 > is ready for reading and voting. > > Except for a few typo corrections, it is the same text as I already presented > in Albuquerque, Dec. 2019. > > PDF: > https://github.com/mpi-forum/mpi-issues/files/4136647/mpi32-report-neighbor… > > Best regards > Rolf > > ----- Original Message ----- >> From: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> >> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> >> Cc: "Martin Schulz" <schulzm(a)in.tum.de> >> Sent: Monday, January 27, 2020 11:03:18 PM >> Subject: [Mpi-forum] REMINDER: Planing for the MPI Forum Meeting in February >> (DEADLINE February 4th) > >> Hi all, >> >> Just a reminder - the deadline for ballot and reading announcements is February >> 4th, i.e., in one week. Please send all announcements, as usual, to the whole >> list. Also, please let me know if any WG would like dedicated discussion time. >> >> Thanks! >> >> Martin >> >> >> — >> Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems >> Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching >> Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) >> [ mailto:[email protected] | Email: schulzm(a)in.tum.de ] >> >> >> >> >> >> Hi all, >> >> The February MPI Forum meeting is getting closer. Logistics and registration is >> online at the usual place: >> >> [ https://www.mpi-forum.org/meetings/2020/02/logistics | >> https://www.mpi-forum.org/meetings/2020/02/logistics ] >> >> Please register as soon as you can. >> >> Note, due to the holiday on Monday, the meeting is this time from Tuesday 2pm to >> Friday 12:30. >> >> As a consequence, the cutoff for ballots, readings, etc. is Tuesday February >> 4th. Please send all announcements to the list. If there are any additional >> requests for plenary sessions, please let me know as well, with the connected >> WG chair in CC. >> >> Also, as we are wrapping up MPI 4.0 and I will (hopefully) not get many requests >> directly connected with MPI 4.0, I will try to make time for WGs again. Hence, >> WG-chairs, please send me any time requests for the forum meeting for WG >> discussions. >> >> Thanks! >> >> Martin >> >> >> — >> Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems >> Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching >> Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) >> [ mailto:[email protected] | Email: schulzm(a)in.tum.de ] >> >> >> >> >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de . > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 . > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 . > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner . > Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) . -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 . University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 . Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) .

1 0

Re: [Mpi-forum] Time To Open Source MPI
by HOLMES Daniel 03 Feb '20

03 Feb '20

Hi Wesley, This change really won’t be as painful as it sounds Then why do I have to do a bunch of unexpected/unscheduled backup and book-keeping work before an arbitrarily chosen deadline? I’m not sure that springing this surprise on folks is the wisest course of action. Cheers, Dan. — Dr Daniel Holmes PhD Architect (HPC Research) d.holmes(a)epcc.ed.ac.uk<mailto:[email protected]> Phone: +44 (0) 131 651 3465 Mobile: +44 (0) 7940 524 088 Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT — The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. — On 3 Feb 2020, at 16:02, Wesley Bland via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]>> wrote: Because in the meantime, our testing remains broken and we don’t have another solution to fix it at the moment. We really want to have that testing fix. This change really won’t be as painful as it sounds. There’s almost no Git commands required. No rebasing/merging/etc. On Feb 3, 2020, at 9:57 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de<mailto:[email protected]>> wrote: Why aren't we doing this when we finished 4.0, i.e. merged all the voted in pull requests into the standard? ----- Original Message ----- From: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]>> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]>> Cc: "Wesley Bland" <work(a)wesbland.com<mailto:[email protected]>> Sent: Monday, February 3, 2020 4:38:48 PM Subject: [Mpi-forum] Time To Open Source MPI Hi folks, ** Look at the numbered list for your action items before 2020-02-18! ** Since we moved from Subversion to GitHub, there’s been a back and forth on whether the MPI Standard Source code should be open source or closed source. As you know (since most of you have access to it, we decided to keep the standard closed for a few reasons (avoiding rogue copies of the Standard was a big one), but recently, the scales have tipped back toward open sourcing and after talking to Bill and Martin some more, we think it’s finally time to open up the MPI Standard repository. Specifically, these are the issues that get addressed by moving to a public repository: * Participation to the forum has a barrier to entry (i.e. me) * Our current automated testing system is broken and will not be fixed * We rely on special dispensation from GitHub for free, private repositories I’ll be discussing this in more detail in Portland, but I want to make folks aware that this is coming now because it will have some impact on people who are actively working on text proposals. The mitigations here should be pretty straightforward and I have both slides (for a high level) and a wiki page (for details) on what’s happening and what you need to do about it. The short version for the purpose of this email and your action item leading up the forum next week is to do two thing s: 1. Back up your branches. 2. Make a note for each of your open pull requests on where the are and what issues they’re attached to. Detailed notes and the slides I’ll present in Portland on how to do this are here: [ https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository | https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository ] The plan is for me to flip this switch DURING THE FEBRUARY MEETING! This should not disrupt any readings for the meeting itself as none of the pull requests will actually be deleted, but they will all become stale and we’ll need to re-open new ones. The main benefit of doing this during the meeting is that if/when anyone has trouble, I’ll be there in person to provide live help to anyone else that’s there (sorry, Marc-Andre, you’ll need to follow my slides remotely \uD83D\uDE00). Please email me if you have questions or concerns. If there’s enough demand, I’d even be willing to do a short Virtual Meeting on this on Wednesday. Thanks, Wesley _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de<mailto:[email protected]> . High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 . University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 . Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner<http://www.hlrs.de/people/rabenseifner> . Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) . _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

1 0

MPI sessions - no-no vote and 1st vote announcement
by HOLMES Daniel 03 Feb '20

03 Feb '20

Hi all, The Sessions WG would like to announce a no-no vote for changes since the last face-to-face meeting and the 1st vote for the whole sessions proposal. If the no-no vote fails, then I will read the whole ticket again and reset the procedural clock. The ticket/issue is #103: https://github.com/mpi-forum/mpi-issues/issues/103 The most recent PDFs are available from the web links below. The change since the last face-to-face are: * some minor spelling/grammar/formatting corrections * fixes/improvements to the new examples to permit the build tool to check correctness * inclusion of recent FTWG changes voted in by the Forum The clean PDF (no change-bars) is here: https://github.com/mpi-forum/mpi-issues/files/4149596/mpi-report-ticket103-… The marked-up PDF (with change-bars) is here: https://github.com/mpi-forum/mpi-issues/files/4149600/mpi-report-ticket103-… The differences since the 2-week deadline for the reading at the last face-to-face meeting can be retrieved from Github like so: https://github.com/mpi-forum/mpi-standard/pull/55/files/83ccf354fc6fa146d84…<https://github.com/mpi-forum/mpi-standard/pull/55/files/83ccf354fc6fa146d84…> Note that I created a new PR #160 with simplified history and the change-bars: https://github.com/mpi-forum/mpi-standard/pull/160 The original PR #55 with full development history and reviews is still available: https://github.com/mpi-forum/mpi-standard/pull/55 I would like to take this opportunity to put on record my thanks to Howard Pritchard; this proposal would not have gotten anywhere near this far without his tireless effort. Cheers, Dan. — Dr Daniel Holmes PhD Architect (HPC Research) d.holmes(a)epcc.ed.ac.uk<mailto:[email protected]> Phone: +44 (0) 131 651 3465 Mobile: +44 (0) 7940 524 088 Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT — The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. — On 3 Feb 2020, at 19:04, Grant, Ryan Eric (-EXP) via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]>> wrote: Hello Everyone, I’d like to announce the following tickets for a second vote at the MPI Forum in Portland. They are unchanged from the tickets that passed first vote in Albuquerque. Ticket #146: https://github.com/mpi-forum/mpi-issues/issues/146 This solution uses a single function MPI_Info_get_string to both provide required buffer lengths and the value string itself. Ticket #147: https://github.com/mpi-forum/mpi-issues/issues/147 Deprecates the existing functions of MPI_Info_get and MPI_Info_get_valuelen that were unsafe in C Best Regards, Ryan ================================ Ryan E. Grant Principal Member of Technical Staff Center for Computing Research Scalable Systems Software Department Sandia National Laboratories Albuquerque NM, USA 505-844-1252 regrant(a)sandia.gov<mailto:[email protected]> _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

1 0

Second Vote on Safe String Handling tickets for MPI_Info
by Grant, Ryan Eric (-EXP) 03 Feb '20

03 Feb '20

Hello Everyone, I'd like to announce the following tickets for a second vote at the MPI Forum in Portland. They are unchanged from the tickets that passed first vote in Albuquerque. ?Ticket #146: https://github.com/mpi-forum/mpi-issues/issues/146 This solution uses a single function MPI_Info_get_string to both provide required buffer lengths and the value string itself. Ticket #147: https://github.com/mpi-forum/mpi-issues/issues/147 Deprecates the existing functions of MPI_Info_get and MPI_Info_get_valuelen that were unsafe in C Best Regards, Ryan ================================ Ryan E. Grant Principal Member of Technical Staff Center for Computing Research Scalable Systems Software Department Sandia National Laboratories Albuquerque NM, USA 505-844-1252 regrant(a)sandia.gov

1 0

Re: [Mpi-forum] Planing for the MPI Forum Meeting in February
by Rolf Rabenseifner 03 Feb '20

03 Feb '20

Hi all, The Semantic Terms Working Group would like to request - a re-reading of issue #96 "Semantic Terms" - a no-no-vote for the changes since Albuquerque added for -- removing changes to MPI-3.1 that were never intended: - correct definition of local and non-local - not defining service/inquiry procedures as blocking/nonblocking -- handling special cases correctly (MPROBE/MRECV, IPROBE/PROBE) - a full reading if the no-no-vote fails - a first vote if the no-no-vote passes. The terms chapter is missing many terms we would like to see added for MPI-4 * Issue: https://github.com/mpi-forum/mpi-issues/issues/96 * PR: https://github.com/mpi-forum/mpi-standard/pull/116 * PDF: https://github.com/mpi-forum/mpi-issues/files/4145580/mpi-report-issue96-20… Current status of #96: - Had a complete reading at Albuquerque - Is strongly needed to achieve consistency for - nonblocking collectives (in since MPI-3.0 and inconsistent to semantic terms) - nonblocking collectives (voted in for MPI-4.0 but inconsistent to semantic terms) - Major problems from Albuquerque are resolved, see above. - "Perfect is the enemy of good enough" We hope that we are now really good enough for MPI-4.0 ;-) And we know that we are not perfect, e.g., we opened doors for one-sided or partitinoed communications, but not more. Thanks and kind regards Rolf On 1/22/20 1:35 PM, Martin Schulz via mpi-forum wrote: > (Sorry, some may get this a second time due address autocompletion problems) > > Hi all, > > The February MPI Forum meeting is getting closer. Logistics and > registration is online at the usual place: > > https://www.mpi-forum.org/meetings/2020/02/logistics > > Please register as soon as you can. > > Note, due to the holiday on Monday, the meeting is this time from > Tuesday 2pm to Friday 12:30. > > As a consequence, the cutoff for ballots, readings, etc. is Tuesday > February 4th. Please send all announcements to the list. If there are > any additional requests for plenary sessions, please let me know as > well, with the connected WG chair in CC. > > Also, as we are wrapping up MPI 4.0 and I will (hopefully) not get many > requests directly connected with MPI 4.0, I will try to make time for > WGs again. Hence, WG-chairs, please send me any time requests for the > forum meeting for WG discussions. > > Thanks! > > Martin > > > — > Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems > Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching > Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) > Email: schulzm(a)in.tum.de <mailto:[email protected]> > > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum > _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

1 0

Re: [Mpi-forum] Planing for the MPI Forum Meeting in February
by Rolf Rabenseifner 03 Feb '20

03 Feb '20

Hi all, The Hardware Topologies Working Group would like to additional request - a re-reading of issue #120 MPI_Cart/Dims_create_weighted - a no-no-vote for the changes since Albuquerque added for - better readable text - having a significantly shorter halo example - a full reading if the no-no-vote Fails - a first vote if the no-no-vote passes. MPI_Cart_create_weighted / Topology aware Cartesian Communicators * Issue: https://github.com/mpi-forum/mpi-issues/issues/120 * PR: https://github.com/mpi-forum/mpi-standard/pull/98 * PDF: https://github.com/mpi-forum/mpi-issues/files/4149191/mpi-report-issue120-t… Current Status of #120: - Had reading at Albuquerque (version Nov.07/updated Nov.21, 2019) - Was significantly shortened in Albuquerque and halo example was also removed - This changed version (Dec. 11, 2019) failed the non-no-vote - Updated version now for (re-)reading is from Feb.03, 2020 Thanks and kind regards Rolf On 1/22/20 1:35 PM, Martin Schulz via mpi-forum wrote: > (Sorry, some may get this a second time due address autocompletion problems) > > Hi all, > > The February MPI Forum meeting is getting closer. Logistics and > registration is online at the usual place: > > https://www.mpi-forum.org/meetings/2020/02/logistics > > Please register as soon as you can. > > Note, due to the holiday on Monday, the meeting is this time from > Tuesday 2pm to Friday 12:30. > > As a consequence, the cutoff for ballots, readings, etc. is Tuesday > February 4th. Please send all announcements to the list. If there are > any additional requests for plenary sessions, please let me know as > well, with the connected WG chair in CC. > > Also, as we are wrapping up MPI 4.0 and I will (hopefully) not get many > requests directly connected with MPI 4.0, I will try to make time for > WGs again. Hence, WG-chairs, please send me any time requests for the > forum meeting for WG discussions. > > Thanks! > > Martin > > > — > Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems > Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching > Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) > Email: schulzm(a)in.tum.de <mailto:[email protected]> > > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum > _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

1 0

Re: [Mpi-forum] Planing for the MPI Forum Meeting in February
by Guillaume Mercier 03 Feb '20

03 Feb '20

Hi all, The Hardware Topologies Working Group would like to request the first vote for the following items: - Hardware split, guided mode * Issue: https://github.com/mpi-forum/mpi-issues/issues/132 * PR: https://github.com/mpi-forum/mpi-standard/pull/142 * PDF: https://github.com/mpi-forum/mpi-issues/files/3952944/mpi40-report-hw-topo-… - Hardware split, unguided mode * Issue: https://github.com/mpi-forum/mpi-issues/issues/156 * PR: https://github.com/mpi-forum/mpi-standard/pull/148 * PDF: https://github.com/mpi-forum/mpi-issues/files/3952929/mpi40-report-hw-topo-… There were no changes since the Albuquerque meeting. Thanks, Guillaume On 1/22/20 1:35 PM, Martin Schulz via mpi-forum wrote: > (Sorry, some may get this a second time due address autocompletion problems) > > Hi all, > > The February MPI Forum meeting is getting closer. Logistics and > registration is online at the usual place: > > https://www.mpi-forum.org/meetings/2020/02/logistics > > Please register as soon as you can. > > Note, due to the holiday on Monday, the meeting is this time from > Tuesday 2pm to Friday 12:30. > > As a consequence, the cutoff for ballots, readings, etc. is Tuesday > February 4th. Please send all announcements to the list. If there are > any additional requests for plenary sessions, please let me know as > well, with the connected WG chair in CC. > > Also, as we are wrapping up MPI 4.0 and I will (hopefully) not get many > requests directly connected with MPI 4.0, I will try to make time for > WGs again. Hence, WG-chairs, please send me any time requests for the > forum meeting for WG discussions. > > Thanks! > > Martin > > > — > Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems > Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching > Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) > Email: schulzm(a)in.tum.de <mailto:[email protected]> > > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >

1 0

Re: [Mpi-forum] Time To Open Source MPI
by Wesley Bland 03 Feb '20

03 Feb '20

Because in the meantime, our testing remains broken and we don’t have another solution to fix it at the moment. We really want to have that testing fix. This change really won’t be as painful as it sounds. There’s almost no Git commands required. No rebasing/merging/etc. > On Feb 3, 2020, at 9:57 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: > > Why aren't we doing this when we finished 4.0, i.e. merged all the voted in > pull requests into the standard? > > ----- Original Message ----- >> From: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> >> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> >> Cc: "Wesley Bland" <work(a)wesbland.com> >> Sent: Monday, February 3, 2020 4:38:48 PM >> Subject: [Mpi-forum] Time To Open Source MPI > >> Hi folks, >> >> ** Look at the numbered list for your action items before 2020-02-18! ** >> >> Since we moved from Subversion to GitHub, there’s been a back and forth on >> whether the MPI Standard Source code should be open source or closed source. As >> you know (since most of you have access to it, we decided to keep the standard >> closed for a few reasons (avoiding rogue copies of the Standard was a big one), >> but recently, the scales have tipped back toward open sourcing and after >> talking to Bill and Martin some more, we think it’s finally time to open up the >> MPI Standard repository. Specifically, these are the issues that get addressed >> by moving to a public repository: >> >> * Participation to the forum has a barrier to entry (i.e. me) >> * Our current automated testing system is broken and will not be fixed >> * We rely on special dispensation from GitHub for free, private repositories >> >> I’ll be discussing this in more detail in Portland, but I want to make folks >> aware that this is coming now because it will have some impact on people who >> are actively working on text proposals. The mitigations here should be pretty >> straightforward and I have both slides (for a high level) and a wiki page (for >> details) on what’s happening and what you need to do about it. >> >> The short version for the purpose of this email and your action item leading up >> the forum next week is to do two thing s: >> >> 1. Back up your branches. >> 2. Make a note for each of your open pull requests on where the are and what >> issues they’re attached to. >> >> Detailed notes and the slides I’ll present in Portland on how to do this are >> here: [ >> https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository | >> https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository ] >> >> The plan is for me to flip this switch DURING THE FEBRUARY MEETING! This should >> not disrupt any readings for the meeting itself as none of the pull requests >> will actually be deleted, but they will all become stale and we’ll need to >> re-open new ones. The main benefit of doing this during the meeting is that >> if/when anyone has trouble, I’ll be there in person to provide live help to >> anyone else that’s there (sorry, Marc-Andre, you’ll need to follow my slides >> remotely \uD83D\uDE00). >> >> Please email me if you have questions or concerns. If there’s enough demand, I’d >> even be willing to do a short Virtual Meeting on this on Wednesday. >> >> Thanks, >> Wesley >> >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de . > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 . > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 . > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner . > Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) .

1 0

Re: [Mpi-forum] Time To Open Source MPI
by Rolf Rabenseifner 03 Feb '20

03 Feb '20

Why aren't we doing this when we finished 4.0, i.e. merged all the voted in pull requests into the standard? ----- Original Message ----- > From: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Cc: "Wesley Bland" <work(a)wesbland.com> > Sent: Monday, February 3, 2020 4:38:48 PM > Subject: [Mpi-forum] Time To Open Source MPI > Hi folks, > > ** Look at the numbered list for your action items before 2020-02-18! ** > > Since we moved from Subversion to GitHub, there’s been a back and forth on > whether the MPI Standard Source code should be open source or closed source. As > you know (since most of you have access to it, we decided to keep the standard > closed for a few reasons (avoiding rogue copies of the Standard was a big one), > but recently, the scales have tipped back toward open sourcing and after > talking to Bill and Martin some more, we think it’s finally time to open up the > MPI Standard repository. Specifically, these are the issues that get addressed > by moving to a public repository: > > * Participation to the forum has a barrier to entry (i.e. me) > * Our current automated testing system is broken and will not be fixed > * We rely on special dispensation from GitHub for free, private repositories > > I’ll be discussing this in more detail in Portland, but I want to make folks > aware that this is coming now because it will have some impact on people who > are actively working on text proposals. The mitigations here should be pretty > straightforward and I have both slides (for a high level) and a wiki page (for > details) on what’s happening and what you need to do about it. > > The short version for the purpose of this email and your action item leading up > the forum next week is to do two thing s: > > 1. Back up your branches. > 2. Make a note for each of your open pull requests on where the are and what > issues they’re attached to. > > Detailed notes and the slides I’ll present in Portland on how to do this are > here: [ > https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository | > https://github.com/mpi-forum/mpi-issues/wiki/Migrate-to-Public-Repository ] > > The plan is for me to flip this switch DURING THE FEBRUARY MEETING! This should > not disrupt any readings for the meeting itself as none of the pull requests > will actually be deleted, but they will all become stale and we’ll need to > re-open new ones. The main benefit of doing this during the meeting is that > if/when anyone has trouble, I’ll be there in person to provide live help to > anyone else that’s there (sorry, Marc-Andre, you’ll need to follow my slides > remotely \uD83D\uDE00). > > Please email me if you have questions or concerns. If there’s enough demand, I’d > even be willing to do a short Virtual Meeting on this on Wednesday. > > Thanks, > Wesley > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 . University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 . Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) .

1 0