Home

Using Git and Github

• GitHub migration notes

• Initial Git setup

• Open MPI's Git repositories on Github

• Open MPI Git best practices

• Awesome flow chart on how to get out of Git messes

• "How to undo almost anything in Git"

• How to make Git (Github) commit messages affect Github issues

• How to submit a bug or enhancement

• How to submit a pull request (i.e., move code to a release branch)

• How to submit an RFC

• How bugs will be managed by the Release Managers

• How pull requests get processed by the Gatekeeper(s)

• How to test pull request with Jenkins

• How to use "bot:" commands in issues and pull requests

• Cheat sheet of Github emoji 👍

Development Documents

• Are you a new developer to the Open MPI project?
• Open MPI project infrastructure
• Mailing lists used by the Open MPI development team
• Development Process
• Coding Style
• Developer Configure Options
• Using Compiler Attributes
• Development Docs
• Technical Guidelines (draft)
• MPI Conformance
• Coverity Prevent web tool guidelines
• Everything you wanted to know about linkers but were too afraid to ask
• How to write / add FAQ entries to the Open MPI web site
• The role of autogen.pl in components and frameworks
• How to add a new component to Open MPI
• How to add a new framework to Open MPI
• How to add an experimental MPI interface in Open MPI
• Guidelines for MCA / MPI_T parameter levels
• Owners of each component (i.e., owner.txt file table)

Weekly Telecon Agendas / Meetings

• Weekly Telecons - 2016
• Weekly Telecons - 2015

Engineering / developer meetings

• Feb 22-25, 2016, Dallas, TX USA
  • Meeting Minutes - Geoff
• June 22-25, 2015, San Jose, CA USA
• January 27-29, 2015, Dallas, TX USA
• June 24-26, 2014, Chicago, IL USA
• December 12-13, 2013, Chicago, IL USA
• June 3-4, 2013, San Jose CA USA
• December 2012, San Jose CA USA
• June 6-8 2012, San Jose, CA USA
• May 3-5 2011, Oak Ridge, TN, USA
• Sep 8-10 2010, Stuttgart, Germany
• Feb 25-27 2009, Louisville, KY, USA
• Feb 11, 2009, San Jose, CA USA
• Dec 2008, Menlo Park, CA, USA
  • Meeting notes
• September 1-2 2008, Dublin, Ireland
• mid-July 2008, Louisville, KY, USA
• June-July 2008, Menlo Park, CA, USA

Periodic maintenance / logistics

• 2014 SVN write access summer cleaning
• 2012 SVN write access summer cleaning

Open MPI Portability

• General notes on writing portable code
• Escape sequences for printf()-like functions
• Specific Ports:
  • Microsoft Windows
  • Cray XT-3/XT-4

Features

• Generic symbol visibility support
• Heterogeneous support
• multi-lib support
  • Creating wrapper compilers with 32 & 64 bit support
• Fault Tolerance
  • Checkpoint/Restart Process Fault Tolerance
  • Multi Automatic Protocols Fault Tolerant Framework
  • On-the-fly Recovery with the Recovery Supervisor/Service (RecoS) Framework
• IPv6 Support
• Thread Safety Support
• Implementing Progress Threads
• OpenMPI and Process Affinity: A primer for the hopelessly confused
• Modex-less Launches: How to get faster and more scalable launches
• Process placement

Design Documents

• CPU / Network Topology Description
• BTL Semantics Description (or Discovery, as the case may be)
• Error Messages How to handle error messages in the Open MPI stack. Also known as OPAL_SOS
• Network Failover Support for IB Networks
• Hierarchical Topology Framework
• Cray XE Port
• Runtime Interposition Project (Code named: Pineapple)
• ORTE Out-of-Band v2.0

Release documents

• General information
  • Release methodology
  • Release procedures
    • Manual tests to conduct before releasing
  • Release Manager management of bugs (in general, may be superseded by individual release managers/series requirements)
  • How to submit Pull Requests
• v1.7 series
• v2.0 series

Administrative documents

• Administrative rules

ORTE documents

• Hostfile Usage Plan
• Design for IOF 2.0

Runtime environment

• Requirements for a RTE used with Open MPI
• Current state of the runtime
  • List of current frameworks and what they do, and diagram of how they interact
  • Sample use cases showing how frameworks are used
• ORTE Scalability Plan and Measurements