From a Fedora perspective -We prefer separate packages, but it is acceptable to bundle libraries if required - especially if OMPI is only tested against a few (or a single) version of PRRTE. However, I would say that if Fedora ends up packaging PRRTE separately we would really rather that open-mpi build against that.
HTH, Orion On 4/27/20 6:47 PM, Ralph Castain wrote:
Just as an FYI - just learned that a major resource manager vendor will be utilizing PRRTE as their runtime for executing applications. So a significant percentage of HPC systems are going to need a PRRTE package, hopefully distributed by someone from the distro community. RalphOn Apr 27, 2020, at 12:48 PM, Jeff Squyres (jsquyres) via ompi-packagers <ompi-packagers@lists.open-mpi.org> wrote: Open MPI packagers -- Just to be clear: this is an open question to you for the upcoming Open MPI v5.0.x series. We'd really appreciate your feedback. Thanks!On Apr 14, 2020, at 12:40 PM, Ralph Castain <r...@open-mpi.org> wrote: <poke> Just pinging you all to ensure you got this. I need to know if we need to coordinate an official PRRTE release to coincide (and sync) with the release of OMPI v5.0, or if you are okay with just using the embedded PRRTE included with the OMPI v5.0 tarball. If it helps, PRRTE depends upon hwloc, libevent, and PMIx - none of which are internally embedded. Thanks RalphOn Apr 1, 2020, at 8:40 PM, Ralph Castain <r...@open-mpi.org> wrote: Hi folks I just wanted to alert you to the fact that we are replacing the ORTE runtime environment in Open MPI with an external package called PRRTE ("PMIx Reference RunTime Environment"). We will be including a copy of that package in the OMPI v5 tarball, just as we do libevent, hwloc, and PMIx. PRRTE historically has not been generating official releases - there is an old v1.0, but nothing on a regular release sequence. As part of this change in OMPI, the PRRTE folks will begin generating official releases that OMPI will use in their releases. So there will be correlation between the packages. My question to you is: is this a package you would prefer to distribute separately (as you do for PMIx and friends), or shall we just leave it as an included package? PRRTE does get used by a fairly small community of people at the national labs and a couple of universities, but it by no means has as wide-ranging a following as OMPI. Just need to know if we need to add a --with-prrte option to OMPI's configure code so one could point it at an external PRRTE installation. Ralph _______________________________________________ ompi-packagers mailing list ompi-packagers@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/ompi-packagers_______________________________________________ ompi-packagers mailing list ompi-packagers@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/ompi-packagers-- Jeff Squyres jsquy...@cisco.com _______________________________________________ ompi-packagers mailing list ompi-packagers@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/ompi-packagers_______________________________________________ ompi-packagers mailing list ompi-packagers@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/ompi-packagers
-- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ ompi-packagers mailing list ompi-packagers@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/ompi-packagers
