WeeklyTelcon_20160405

Open MPI Weekly Telcon

Milestones: https://github.com/open-mpi/ompi-release/milestones/v1.10.3
1.10.3 in April - collecting some smaller fixes accumulating in the branch.
waiting for discussion on one PR out there.

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
- Issue 1505 - for v2.x merge - need PR on 2.0!
  - TCP BTL THREAD_MULTIPLE deadlock
    - Resolution: Bugfixing goodness.
  - New non-default feature: TCP async progress only in active if requested via requested via MCA param.
  - Ralph pointed out some compiler errors, that George just fixed yesterday, don't lose those.
  - Howard will merge to Master, and open a PR againt 2.0.0
- Memory Hooks: PR 1495
  - move registration of memory manager to as late as possible.
  - MxM has it's own way of hooking calls, but doesn't play well with patcher methods put in.
    - Nathan should have a good understanding today.
    - Could turn off leave pinned for BTLs when using MxM (don't like this, but possible)
    - Should talk to Yoci. Setup a call, no reason to speculate.
  - Howard found another issue where need to set LEAVE_PINNED
  - If we can't fix this in a week, we may need to fall back to not pinning by default
  - Joshua will setup phone call with Yoci, Howard, Nathan, and Mark to discuss MxM.
- -host merged to master - PR 1353
  - try to get into v2.0.0?
Milestones: https://github.com/open-mpi/ompi-release/milestones/v2.0.0 *
OMPI Release Open Pull Requests: https://github.com/open-mpi/ompi-release/pulls

Lots of failures on Master. Items failing out. MPI_Irecv_Pack (unpack is generating an error).
- Just got a lot of packing changes, may be related.
Josh question on PR1482.
- legitimate concerns on mechanism.
- Users confused why self
Ralph has committed -host change so people can begin looking at.
- At one point talked about moving to 2.x. If we don't move to 2.0.0, won't move to 2.x at all.

Over the weekend, figured out that HTTP access has been ignored for some amount of time, so over the weekend turned it back on. But if anyone submitted with wrong password, might get bad message.
- If you have an issue, please Contact Jeff Squyres or Josh Hursey.