forked from open-mpi/ompi
-
Notifications
You must be signed in to change notification settings - Fork 1
Meeting 2015 06
rhc54 edited this page Jun 23, 2015
·
72 revisions
This is a standalone meeting; it is not being held in conjunction with an MPI Forum meeting.
Doodle for choosing the date: http://doodle.com/4arc4ciiby2ve222
- Date: 9am Tuesday, June 23 through 3pm Thursday, June 25
- Location:
- Cisco Building 1, 3850 Zanker Road, San Jose, California 95134
- Tuesday: Mt. Everest conference room
- Wednesday: Mt. Everest conference room
- Thursday: Mt. Aetna conference room
Link to January meeting wiki notes.
Local attendees:
- Jeff Squyres - Cisco
- Ralph Castain - Intel
- Nathan Hjelm - LANL
- Dave Solt - IBM
- Dave Goodell - Cisco (may not be there for the whole meeting)
- Howard Pritchard - LANL
- Shinji Sumimoto - Fujitsu
- George Bosilca - UTK
- Devendar Bureddy - Mellanox
- Jithin Jose - Intel
- Yohann Burette - Intel
- Rolf vandeVaart - NVIDIA
- Andrew Friedley - Intel
- ... YOU MUST ADD YOUR NAME IF YOU PLAN TO COME! (Jeff has to register you as a Cisco guest) ...
- Review action items from Jan meeting
- PMIx integration and API extension for PMIx v2.0
- "Instant On" status and planning
- Async add procs
- Direct modex support
- Distributed mapping
- Thread multiple support status
- ORTE process name change - replace jobid with namespace
- Can we add new environment variable CUDA_AWARE_SUPPORT and also create info key on MPI_COMM_WORLD for runtime detection?
- Coverity update
- Plan for v2.x
- revisit mtl one-sided support
- Fujitsu Development Status and Some Topics towards Next MPI development
- Version number scheme / roadmap announcement to users
- Jeff's slides as pptx
- Jeff's slides as PDF
- Endless discussion - slides cleaned up. Major decisions were to revise definition of backward compatibility to be "binary compatible + CLI + MCA params"
- v1.10.0 will not meet this definition relative to v1.8 series
- NEWS will contain list of CLI and MCA param changes
- Plan for v1.10.x
- Feature-complete once PSM2 PR is committed
- Mellanox may have some PowerPC contributions, more as bug-fixes/optimizations
- MPI 3.1 - are we ready?
- Jeff is blocker - Fortran changes
- Edgar - need to know plans for non-blocking IO
- Nathan - looking at MPICH Generalized request code to see if we can bring it into OMPI to enable ROMIO 3.1 support
- Howard has wiki page tracking MPI-3 compliance - reviewed all the 3.0 errata and 3.1 outstanding tickets and assigned them to people
- Open MPI legacy code: can we chop off support for some older systems?
- E.g., can we force users to use compilers with
<stdbool.h>
? (has implications in opal_config/opal_config_bottom.h) - C99 requires stdbool.h exist, so this is stale and can be removed
- Nathan points out that other headers and types are in this category, so we need to scrub the entire configure system to remove extraneous header and type checks (full list TBD)
- E.g., can we force users to use compilers with
- Git / github usage. How's it going? What's going well / not well? What can we improve on?
- One idea: should everything on master be a pull request (just to get smoke testing on a variety of systems)? NOTE: NOT advocating a code czar -- anyone can still push the merge button.
- Jenkins usage on PRs.
- LANL work on a Jenkins aggregator for Github.
- Other Github webhooks that might be useful?
- Anything else we want to tweak?
- Cisco et al will work on completing the Jenkins aggregator project and improving both throughput and reliability of the service
- We strongly encourage developers to use PR's to bring changes into the master. Once the testing support has been improved, we may change this policy to a requirement
- We will look at the possibility of pulling all outstanding master PR's into an integrated tarball and running it thru MTT on a nightly basis
- coll ml discussion - get rid of this completely?
- Ralph has contacted ORNL - they are in the process of fixing it and would like it to stay
- See http://www.open-mpi.org/community/lists/users/2015/06/27170.php
- Should be no way the user can get into that code without specifically requesting it, need to understand what the user is doing to enable ml
- Re-introducing Microsoft Windows support (http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and-c99/)
- IBM to look at what would be required
- Requested that IBM provide a Jenkins-like tester so we can know when we break it
- Probably want a handcoded .project file, no-build (either no Cmake file or other way) components that cannot work under Windows
- Windows support removed at open-mpi/ompi@a4b6fb241fe0bdf082431e8a380c1a1ab8b25799
- ...fill in content here