forked from open-mpi/ompi
-
Notifications
You must be signed in to change notification settings - Fork 4
WeeklyTelcon_20160501
Geoff Paulsen edited this page May 3, 2016
·
20 revisions
- Dialup Info: (Do not post to public mailing list or public wiki)
- Geoff Paulsen
- Jeff Squyres
- Brad Benton
- Howard
- Josh Hursey
- Joshua Ladd
- Nathan Hjelm
- ralph
- Todd Kordenbrock
- Milestones: https://github.com/open-mpi/ompi-release/milestones/v1.10.3
- Two pull requests that have not been reviewed:
- NULL datatypes - Jeff's looking at some oddities to see if we care.
- distinct namespaces for OSC for pt2pt. - Nathan thinks it's fine.
- Blocker for "PSM stuff" - Howard reviewed this. Good with this.
- Jeff owes a library versioning review. already updated for 1.10.3.
- Two pull requests that have not been reviewed:
- Wiki: https://github.com/open-mpi/ompi/wiki/Releasev20
- Blocker Issues: https://github.com/open-mpi/ompi/issues?utf8=%E2%9C%93&q=is%3Aopen+milestone%3Av2.0.0+label%3Ablocker *
- Milestones: https://github.com/open-mpi/ompi-release/milestones/v2.0.0 *
- Discussion:
- What "gotchas" do we need to communicate to users? I.e., what will people upgrading from v1.8.x/v1.10.x be surprised by?
- The most obvious one I can think of is mpirun requiring -np when slots are not specified somehow.
- What else do we need to communicate? It would be nice to avoid the confusion users experienced regarding affinity functionality/options when upgrading from v1.6 -> v1.8 (because we didn't communicate these changes well, IMHO).
- https://github.com/open-mpi/ompi/wiki/User-Migration-Guide:-1.8.x-and-v1.10.x-to-v2.0.0
- https://github.com/open-mpi/ompi/wiki/Developer-Migration-Guide:-v1.8.x-and-v1.10.x-to-v2.x
- What "gotchas" do we need to communicate to users? I.e., what will people upgrading from v1.8.x/v1.10.x be surprised by?
Review Master MTT testing (https://mtt.open-mpi.org/)
- Mellanox, Sandia, Intel
- LANL, Houston, IBM
- Cisco, ORNL, UTK, NVIDIA