Meeting 2015 06

June 2015 OMPI Developer's Meeting

This is a standalone meeting; it is not being held in conjunction with an MPI Forum meeting.

Logistics

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.

Attendees

Local attendees:

1. Jeff Squyres - Cisco
2. Ralph Castain - Intel
3. Nathan Hjelm - LANL
4. Dave Solt - IBM
5. Dave Goodell - Cisco (may not be there for the whole meeting)
6. Howard Pritchard - LANL
7. Shinji Sumimoto - Fujitsu
8. George Bosilca - UTK
9. Devendar Bureddy - Mellanox
10. Jithin Jose - Intel
11. Yohann Burette - Intel
12. Rolf vandeVaart - NVIDIA
13. Andrew Friedley - Intel
14. ... YOU MUST ADD YOUR NAME IF YOU PLAN TO COME! (Jeff has to register you as a Cisco guest) ...

Topics to discuss

• 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
• 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?
• ORTE process name change - replace jobid with namespace
• MPI 3.1 - are we ready?
• 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 v1.10.x
• Plan for v2.x
• 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)
• coll ml discussion - get rid of this completely?

Results

• 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

Presentation Material

• ...fill in content here