-
Notifications
You must be signed in to change notification settings - Fork 860
WeeklyTelcon_20190409
Geoffrey Paulsen edited this page Apr 9, 2019
·
1 revision
- Dialup Info: (Do not post to public mailing list or public wiki)
- Geoff Paulsen
- Jeff Squyres
- Akshay Venkatesh (nVidia)
- Michael Heinz (Intel)
- Brian Barrett
- Edgar Gabriel
- Ralph Castain
- Josh Hursey
- Howard Pritchard
- Dan Topa (LANL)
- Thomas Naughton
- Todd Kordenbrock
- Joshua Ladd
- George Bosilca
- Noah Evans (Sandia)
- David Bernholdt
- Mike Heinz (Intel)
- Jake Hemstad
- Matthew Dosanjh
- Xin Zhao
- Nathan Hjelm
- Geoffroy Vallee
- Matias Cabral
- Aravind Gopalakrishnan (Intel)
- Arm (UTK)
- Peter Gottesman (Cisco)
- mohan
-
Vector Datatype https://github.com/open-mpi/ompi/issues/5540
- If you're using complicated data types for real things, it's important.
- Should it be back ported to release branches? Perhaps not, since only one customer has hit.
- Not a blocker for v4.0.1
-
Jeff opened a PR about StaleBot - https://github.com/apps/stale
- https://github.com/open-mpi/ompi/pull/6495
- Brian created a wiki page under open mpi for 'CI development tasks'
- Wishlist wiki: https://github.com/open-mpi/ompi/wiki/GitHub-Robot-Tasks
- Auto adding labels to PRs.
- Would all run on AWS Jenkins server
- Nice framework is written in NODE.js
-
Should have someone begin working on
-
Issue: Some cases cause Co-Author instead of signed-off: https://github.com/pmix/pmix-standard/pull/180/commits We may want to update our policy to also allow for Co-Authored-By When someone proposes a change via a github review, and the Author approves it, the new commit has a "Co-Authored-By". ACTION: Jeff will email Github to ask how other teams deal with this.
-
Host Ordering fix to v3.0.x, v3.1.x, v4.0.x https://github.com/open-mpi/ompi/issues/6501
- --host (and hostfile) on command line, the ordering of the hosts were not ordered.
- This Fix went into master. Do we want to bring it back to release branches?
- Everyone on call liked PRing this to release branches, but want to see what Brian and Howard think.
- Not a backwards compatibility issues, since a specified ordering is a subset of a random ordering.
- There is a PR for v4.0.x that Ralph and Jeff are iterating on. Unexpectedly large. Would be good to do this first.
-
OLD Giles openib issue: https://github.com/open-mpi/ompi/pull/6152
- No one had any thoughts on.
- Would like Mellanox to chime in and let us know if it's needed in v4.0.x
- No update.
-
OLD George did you get any follow up with Season of Documentation?
- Some. Making man pages better and finding a way to link man pages with examples would be really awesome.
- In libfabric they make man pages in Markdown, and then in make dist, they convert it to nroff.
- For user facing APIs, they use Sphynx - convert Markdown in comments to user facing HTML man pages.
- No New Updates.
- We need to apply and ask for volunteers.
-
Noah described a new thread framework
- two bits of cleverness. Static initializes, and need certain functions to be static inline.
- Get an implementation defined header that gets installed in configure. (similar to libevents)
- Two components: Argobots and pthreads.
- Currently exclusive (only one component, since it installs a header at configure time).
- Probably permanently.
- Need to look at thread local storage.
- Had to implement TLS on top of pthreads, Argobots has this already.
- Request completion would be the most sensitive to having oversubscription.
- Posted a Work-in-progress PR:
https://github.com/open-mpi/ompi/pull/6578
- certain types of applications want to schedule a finer grained task
- Ex: OpenMP groups, some apps have shown some improvements.
- If you have a really unbalanced problem, where you can't rebalance with a mesh rebalance. Then if you do a traditional MPI task per core, the imbalance becomes a big problem. Like the CharmPlusPlus approach, don't think about task / thread mapping yourself, let the system map that. To do this well, you need to implement them correctly. Really want some threads (like libevent) to really be an OS thread, rather than user thread.
- Do you have to use the same thread framework at all levels of the process?
- You kinda want the MPI process to know how the user is using threads, but also want the libevent thread to be pre-emtively schedule, not co-operatively scheduled (borrowing from solaris terminology)
Review All Open Blockers
Review v3.0.x Milestones v3.0.4
- Release did not go out last week
- Will release RC today: 3.0.4
Review v3.1.x Milestones v3.1.4
- Release did not go out last week
- Will release RC today: 3.1.4
Review v4.0.x Milestones v4.0.2
- Release went out two weeks ago
- Reminder: Need to ensure ALL Ci has run. Non-Open-MPI users won't run
-
CI until someone comments "Ok To Test" as a comment on the PR. - Josh Ladd please review PR6152 - delay UCX warning to add_procs
- Josh Hursey Please review PR6508 - ensure nodes are always used in order.
- This was being held for post v4.0.1 due to size
- Ralph, was there any reason to add anything to PR6508?
- Yes, it's not quite right.
- Still waiting on some reviews.
- Vader - cleanup, fixes the problem. Intel folks have verified that.
- PR6508 - Fixes host ordering, but is quite large.
- Fixing this brings in quite a bit of other things.
- Problem with this is that it's a significant patch
- Action: Ralph will look at it.
- This might force
- Schedule: Delaying post Summer ***
- Discussion of schedule depends on scope discussion
- if we want to separate Orte out for that? Would be a bit past summer.
- Giles has a prototype of PRTE replacing ORTE
- Want to open up release-manager elections.
- Now that we're delaying, will decide at face2face.
- Now the possibility of v4.1 from master is a possibility
- If we instead do a v4.1, some things we'd need fixed on master.
- will discuss more at face to face.
- Brian and Ralph are meeting on the 18th
- Ralph is putting out a doodle to discuss
- Fortran Array
-
Schedule sometime this summer will be v4.0.x
-
A few bugfix releases for v2 and v3 series. RC this week, and release sometime in April.
-
New standardization issue is destined for v5
-
There will be a new PMIx 3.1.3 which can be included into a future v4.0.x OMPI.
-
Take a look at Gile's PRTE work. He may have done SOME of that. He should have done that all in PRTE layer, maybe just some MPI layer work remains.
- PR6339 - he's closed, and re-opened a new branch to look at.
- Howard reviewed PR6339, and likes everything that Giles did, so abandoned his branch
- This is a good approach, and gets something running, but it's not complete
- IBM still has 10% failure rate and build issue. Please fix!!!
- MPI Forum - nothing too substantial. MPI_Sessions getting a lot of traction. Goal to get it done by next meeting. Need reading, and then vote, and another vote and another. So MPI Next would be in 2020 year. Language bindings, and some crazy proposals
- Read MPI Forum link here: https://www.mpi-forum.org/
- how do we get more participation, and make MTT more meaningful?
Review Master Master Pull Requests
- didn't discuss today.
Review Master MTT testing
- Mellanox, Sandia, Intel
- LANL, Houston, IBM, Fujitsu
- Amazon,
- Cisco, ORNL, UTK, NVIDIA