-
Notifications
You must be signed in to change notification settings - Fork 859
WeeklyTelcon_20161018
- Dialup Info: (Do not post to public mailing list or public wiki)
- Geoff Paulsen
- Jeff Squyres
- Brad Benton
- Brian
- Edgar Gabriel
- Geoffroy Vallee
- Howard Pritchard
- Josh Hursey
- Joshua Ladd
- Ralph
- Ryan Grant
- Todd Kordenbrock
- Milestones
- 1.10.x
- Still no drivers for a 1.10.5.
-
Wiki
- 2.0.2 - Schedule, no drivers right now.
- Probably want to do it. 2.0.1 does have some problems. Nvidia couldn't even build.
- 2.0.2 - Schedule, no drivers right now.
-
Milestones
- 2.1.0
- PMIx 1.2.0 stuff. Artem has been working away. Thinks we have final set of commits needed, and stacked up.
- Backward compatibility Fix (not Rosetta Feature).
- Error handling, Return code cleanup, job info.
- Since this is slipping out of October, would it be less risky for a NEWER version of PMIx?
- Open MPI 2.1.0, do we want to Skip PMIx 1.2.0, and go straight to PMIx 2.0.0?
- Open MPI want's dstore functionality, and potentially some of the APIs IBM was asking for.
- Depends on timing.
- Ralph still working on cross compatibility code (ready well before January).
- If trying to get Open MPI 2.1.0 in December, then intermediate PMIX 1.2.0 or PMIX 2.0.0 may be better.
- What is limiting factor of going to HEAD?
- Without Rosetta Stone, not getting additional functionality of going to PMIx HEAD.
- PMIX 2.0 or HEAD (3.0) Open MPI would have to change OPAL framework level, and ORTE integration.
- Backend of existing APIs are stable, but new APIs to support those.
- If going to use PMIx 1.2, then these two don't have to change.
- Do we expect major perturbation after PMIx 3.0? (Only new APIs, no changes to APIs expected).
- in PMIx 1.2 there were 2 APIs that CHANGEd (not just added).
- Cherry-picking our way to PMI-x HEAD would be a HUGE amount of work, but drop-in, might not be as much work.
- It's really in IBM's camp. Ralph is working in PMIx camp, ready by thanksgiving.
- Josh is taking leadership for PMIx 1.2 and 2.0 streams. How much work is it to make this ready, along with Mellanox.
- Josh Hursey will talk internally and then with Mellanox, and then Ralph.
- PMIx 1.2.0 stuff. Artem has been working away. Thinks we have final set of commits needed, and stacked up.
- 2.1.0
PR 2181 - Lazy wait in 2.x - busy waiting experimenting with giving more timeslice to app / transport, rather than busy waiting.
schedule.
- Discussed PR2176 - Add an experimental ability to skip the RTE barriers.
- Mellanox says UCX supports this, so it would be nice on UCX.
- Need to tell people this won't work if not using UCX (or network that doesn't need it)
- Would like information how UCX supports communication to a non-existant remote process.
-
GITHUB Tags / Milestones - not well documented in wiki.
- push-back tag - means it's gone back to the author.
- Other tags have changed meanings over time.
-
SPI - http://www.spi-inc.org/
- Open MPI vote to be in SPI may be delayed a month.
- SPI's Official notice to mailling list had some issues. Some non-board members only finding out yesterday.
- General population needs to know, in case they know about possible pending lawsuits against new members.
- Open MPI vote to be in SPI may be delayed a month.
-
Discussion about Nightly snapshot versioning.
- Complicated tarball naming is confusing.
- Jeff proposed a nomenclature.
- Giles had a proposal about git describe, but concern that might add more confusion.
- people generally okay with Jeff's proposal, but need to ensure MTT does the right thing.
-
MTT - only Cisco and ____ testing v2.0.x. Others are testing v2.x (reported as v2.0.1-...)
- Others please test both v2.0.x and v2.x
-
MTT downtime 3 hours - no downtime today, try for Friday
- Might need to force a DNS update afterwards
- Josh H will send out reminder email before and after it's moved.
-
OMPI BOFF is moved to Wed Night at super-computing.
-
New Contribution agreement / Consent agreement / Bylaws.
- Patent clause protection change proposal. - Could put this language in the disclaimer signoff.
- either don't care or want to change this.
- Official notice: Members will hold a formal vote in 2 weeks (Oct 25) to vote on new bylaws.
- Comment that driver for this is no longer there, since they've become a member.
- Comment that this new bylaw is driving towards way other open source projects are managing this.
- Comment that 2 week notice for official votes is highly preferable.
- Geoff Paulsen will send out notice, and ask for comments to devel mailing list.
- Geoff Paulsen will send out voting notice to devel-core for Oct 25th vote.
- Patent clause protection change proposal. - Could put this language in the disclaimer signoff.
Review Master MTT testing (https://mtt.open-mpi.org/)
- Geoff will put up a doodle to solicit input.
- LANL, Houston, IBM
- Cisco, ORNL, UTK, NVIDIA
- Mellanox, Sandia, Intel