On Feb 27, 2015, at 9:42 AM, Sasso, John (GE Power & Water, Non-GE) <john1.sa...@ge.com<mailto:john1.sa...@ge.com>> wrote:
Unfortunately, we have a few apps which use LAM/MPI instead of OpenMPI (and this is something I have NO control over). Bummer! I have been making an effortlonger supported and end-of-life. In fact, the website www.lam-mpi-org is no longer accessible as the domain name expired on 2/20/2015. Wow, I didn't realize that my prior employer had let the domain lapse. Well, perhaps it was time. We haven't changed anything about LAM/MPI in ...a decade? Now that the domain is gone, since I don't even have an SVN checkout any more, I can't check when the last meaningful commit was. I see Rob found a ROMIO commit in 2007. Aside from a change of library paths in the Makefiles, I am assuming that hardly any code changes would be needed for them to rebuild and run the code with OpenMPI. Comments on this? That should be correct. MPI should be source code compatible. mpirun options will be different, of course. And there's no lamboot and lamhalt. Yeah, any other recommendations I can give to convince the powers-that-be that immediate sun-setting of LAM/MPI would be great. Sometimes I feel like I am trying to fit a square peg in a round hole L How's this: - Brian Barrett and myself were the primary maintainers of LAM/MPI. - Brian and I moved on to Open MPI about a decade ago. - There have been no releases of LAM/MPI in many years. - There won't be any future releases of LAM/MPI, ever. - There is zero support for LAM/MPI. - Open MPI has MUCH better support for run-time systems and modern networks. - Open MPI has an active developer and user community. - Open MPI is supported by multiple different vendors. - Jeff Immelt wants you to move away from LAM/MPI. [cid:1E778E8F-E5CC-4AB5-9EFE-A45D8441298E@cisco.com] -- Jeff Squyres jsquy...@cisco.com<mailto:jsquy...@cisco.com> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
