Re: [OMPI devel] Remove prun tool from OMPI?
On Tue, 5 Jun 2018, r...@open-mpi.org wrote: On Jun 5, 2018, at 11:59 AM, Thomas Naughton wrote: Hi Ralph, All it means is that PRRTE users must be careful to have PRRTE before OMPI in their path values. Otherwise, they get the wrong “prun” and it fails. I suppose I could update the “prun” in OMPI to match the one in PRRTE, if that helps - there isn’t anything incompatible between ORTE and PRRTE. Would that make sense? Yes, if updating "OMPI prun" with latest "PRRTE prun" works ok, that seems like a reasonable way to keep DVM for OMPI usage. I agree that it does seem likely that users could easily get the wrong 'prun' but this may be something that falls out in future (based on discussion on call today). I guess the main point of interest would be to have some method for launching the DVM scenario with OMPI. Another option could be to rename the binary in OMPI? Yeah, that’s what the OHPC folks did in their distro - they renamed it to “ompi-prun”. If that works for you, then perhaps the best path forward is to do the rename and update it as well. Sounds good to me -- seems like a good way to avoid confusion. And having the 'ompi-prun' be in sync with (prrte) prun will make sure things run properly, i.e., easy to drop in new snapshot of the tool when updating PRRTE snapshots in OMPI. (Or however done in future) Thanks, Ralph! --tjn _ Thomas Naughton naught...@ornl.gov Research Associate (865) 576-4184 Thanks, --tjn _ Thomas Naughton naught...@ornl.gov Research Associate (865) 576-4184 On Tue, 5 Jun 2018, r...@open-mpi.org wrote: I know we were headed that way - it might still work when run against the current ORTE. I can check that and see. If so, then I guess it might be advisable to retain it. All it means is that PRRTE users must be careful to have PRRTE before OMPI in their path values. Otherwise, they get the wrong “prun” and it fails. I suppose I could update the “prun” in OMPI to match the one in PRRTE, if that helps - there isn’t anything incompatible between ORTE and PRRTE. Would that make sense? FWIW: Got a similar complaint from the OpenHPC folks - I gather they also have a “prun”’ in their distribution that they use as an abstraction over all the RM launchers. I’m less concerned about that one, though. On Jun 5, 2018, at 9:55 AM, Thomas Naughton wrote: Hi Ralph, Is the 'prun' tool required to launch the DVM? I know that at some point things shifted to use 'prun' and didn't require the URI on command-line, but I've not tested in few months. Thanks, --tjn _ Thomas Naughton naught...@ornl.gov Research Associate (865) 576-4184 On Tue, 5 Jun 2018, r...@open-mpi.org wrote: Hey folks Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t believe anyone is using it, and it doesn’t look like it even works. I ask because the name conflicts with PRRTE and can cause problems when running OMPI against PRRTE Ralph ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Remove prun tool from OMPI?
> On Jun 5, 2018, at 11:59 AM, Thomas Naughton wrote: > > Hi Ralph, > >> All it means is that PRRTE users must be careful to have PRRTE before OMPI >> in their path values. Otherwise, they get the wrong “prun” and it fails. I >> suppose I could update the “prun” in OMPI to match the one in PRRTE, if that >> helps - there isn’t anything incompatible between ORTE and PRRTE. Would that >> make sense? > > > Yes, if updating "OMPI prun" with latest "PRRTE prun" works ok, that > seems like a reasonable way to keep DVM for OMPI usage. > > I agree that it does seem likely that users could easily get the wrong > 'prun' but this may be something that falls out in future (based on > discussion on call today). > > I guess the main point of interest would be to have some method for > launching the DVM scenario with OMPI. Another option could be to rename > the binary in OMPI? Yeah, that’s what the OHPC folks did in their distro - they renamed it to “ompi-prun”. If that works for you, then perhaps the best path forward is to do the rename and update it as well. > > Thanks, > --tjn > > _ > Thomas Naughton naught...@ornl.gov > Research Associate (865) 576-4184 > > > On Tue, 5 Jun 2018, r...@open-mpi.org wrote: > >> I know we were headed that way - it might still work when run against the >> current ORTE. I can check that and see. If so, then I guess it might be >> advisable to retain it. >> >> All it means is that PRRTE users must be careful to have PRRTE before OMPI >> in their path values. Otherwise, they get the wrong “prun” and it fails. I >> suppose I could update the “prun” in OMPI to match the one in PRRTE, if that >> helps - there isn’t anything incompatible between ORTE and PRRTE. Would that >> make sense? >> >> >> FWIW: Got a similar complaint from the OpenHPC folks - I gather they also >> have a “prun”’ in their distribution that they use as an abstraction over >> all the RM launchers. I’m less concerned about that one, though. >> >> >>> On Jun 5, 2018, at 9:55 AM, Thomas Naughton wrote: >>> Hi Ralph, >>> Is the 'prun' tool required to launch the DVM? >>> I know that at some point things shifted to use 'prun' and didn't require >>> the URI on command-line, but I've not tested in few months. >>> Thanks, >>> --tjn >>> _ >>> Thomas Naughton naught...@ornl.gov >>> Research Associate (865) 576-4184 >>> On Tue, 5 Jun 2018, r...@open-mpi.org wrote: Hey folks Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t believe anyone is using it, and it doesn’t look like it even works. I ask because the name conflicts with PRRTE and can cause problems when running OMPI against PRRTE Ralph ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel >>> ___ >>> devel mailing list >>> devel@lists.open-mpi.org >>> https://lists.open-mpi.org/mailman/listinfo/devel >> >> ___ >> devel mailing list >> devel@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/devel > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Remove prun tool from OMPI?
Hi Ralph, All it means is that PRRTE users must be careful to have PRRTE before OMPI in their path values. Otherwise, they get the wrong “prun” and it fails. I suppose I could update the “prun” in OMPI to match the one in PRRTE, if that helps - there isn’t anything incompatible between ORTE and PRRTE. Would that make sense? Yes, if updating "OMPI prun" with latest "PRRTE prun" works ok, that seems like a reasonable way to keep DVM for OMPI usage. I agree that it does seem likely that users could easily get the wrong 'prun' but this may be something that falls out in future (based on discussion on call today). I guess the main point of interest would be to have some method for launching the DVM scenario with OMPI. Another option could be to rename the binary in OMPI? Thanks, --tjn _ Thomas Naughton naught...@ornl.gov Research Associate (865) 576-4184 On Tue, 5 Jun 2018, r...@open-mpi.org wrote: I know we were headed that way - it might still work when run against the current ORTE. I can check that and see. If so, then I guess it might be advisable to retain it. All it means is that PRRTE users must be careful to have PRRTE before OMPI in their path values. Otherwise, they get the wrong “prun” and it fails. I suppose I could update the “prun” in OMPI to match the one in PRRTE, if that helps - there isn’t anything incompatible between ORTE and PRRTE. Would that make sense? FWIW: Got a similar complaint from the OpenHPC folks - I gather they also have a “prun”’ in their distribution that they use as an abstraction over all the RM launchers. I’m less concerned about that one, though. On Jun 5, 2018, at 9:55 AM, Thomas Naughton wrote: Hi Ralph, Is the 'prun' tool required to launch the DVM? I know that at some point things shifted to use 'prun' and didn't require the URI on command-line, but I've not tested in few months. Thanks, --tjn _ Thomas Naughton naught...@ornl.gov Research Associate (865) 576-4184 On Tue, 5 Jun 2018, r...@open-mpi.org wrote: Hey folks Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t believe anyone is using it, and it doesn’t look like it even works. I ask because the name conflicts with PRRTE and can cause problems when running OMPI against PRRTE Ralph ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Remove prun tool from OMPI?
I know we were headed that way - it might still work when run against the current ORTE. I can check that and see. If so, then I guess it might be advisable to retain it. All it means is that PRRTE users must be careful to have PRRTE before OMPI in their path values. Otherwise, they get the wrong “prun” and it fails. I suppose I could update the “prun” in OMPI to match the one in PRRTE, if that helps - there isn’t anything incompatible between ORTE and PRRTE. Would that make sense? FWIW: Got a similar complaint from the OpenHPC folks - I gather they also have a “prun”’ in their distribution that they use as an abstraction over all the RM launchers. I’m less concerned about that one, though. > On Jun 5, 2018, at 9:55 AM, Thomas Naughton wrote: > > Hi Ralph, > > Is the 'prun' tool required to launch the DVM? > > I know that at some point things shifted to use 'prun' and didn't require > the URI on command-line, but I've not tested in few months. > > Thanks, > --tjn > > _ > Thomas Naughton naught...@ornl.gov > Research Associate (865) 576-4184 > > > On Tue, 5 Jun 2018, r...@open-mpi.org wrote: > >> Hey folks >> >> Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t >> believe anyone is using it, and it doesn’t look like it even works. >> >> I ask because the name conflicts with PRRTE and can cause problems when >> running OMPI against PRRTE >> >> Ralph >> >> ___ >> devel mailing list >> devel@lists.open-mpi.org >> https://lists.open-mpi.org/mailman/listinfo/devel > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Remove prun tool from OMPI?
Hi Ralph, Is the 'prun' tool required to launch the DVM? I know that at some point things shifted to use 'prun' and didn't require the URI on command-line, but I've not tested in few months. Thanks, --tjn _ Thomas Naughton naught...@ornl.gov Research Associate (865) 576-4184 On Tue, 5 Jun 2018, r...@open-mpi.org wrote: Hey folks Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t believe anyone is using it, and it doesn’t look like it even works. I ask because the name conflicts with PRRTE and can cause problems when running OMPI against PRRTE Ralph ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
Re: [OMPI devel] Remove prun tool from OMPI?
No objection from me. > On Jun 5, 2018, at 12:09 PM, r...@open-mpi.org wrote: > > Hey folks > > Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t > believe anyone is using it, and it doesn’t look like it even works. > > I ask because the name conflicts with PRRTE and can cause problems when > running OMPI against PRRTE > > Ralph > > ___ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
[OMPI devel] Remove prun tool from OMPI?
Hey folks Does anyone have heartburn if I remove the “prun” tool from ORTE? I don’t believe anyone is using it, and it doesn’t look like it even works. I ask because the name conflicts with PRRTE and can cause problems when running OMPI against PRRTE Ralph ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
[OMPI devel] Today's Open-MPI discussion notes highlighting potential new runtime approach.
All, In today's Open MPI Web-Ex (Minutes here: https://github.com/open-mpi/ompi/wiki/WeeklyTelcon_20180605) we discussed the future of Open MPI ORTE runtime (mpirun / orteds, launching etc). Nothing was decided, but please take a look and discuss on the mailing lists, and or come to next week's Web-Ex for more discussion. This discussion is in the context of Open MPI v5.0 which we haven't yet decided on the schedule for (but v4.0 branches from master mid-July, and releases mid-Sept). We'd love to hear your input. Thanks, Geoff Paulsen ___ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
