Re: [OMPI devel] Open MPI 3rd party packaging changes

2020-10-08 Thread Orion Poplawski via devel 

On 10/1/20 1:43 PM, Barrett, Brian via devel wrote:

All -

Only 6 months after I promised the code would be done, the changes we discussed in February around 3rd party 
packages (Libevent, HWLOC, PMIx, and PRRTE) are merged to master.  With these changes, Open MPI will prefer 
an external version of any of those packages if a "new enough" version is found already installed 
on the system.  New enough is no longer defined as "newer than the built-in package", but is 
defined as "as new as the oldest version we know works".  This may cause unexpected changes from 
using the built-in versions to the system versions for some packages, particularly libevent.

If you have Libevent and hwloc pre-installed, your total build times will go 
down a couple percent, so there's that :).

Brian



Thank you.

Orion

--
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 devel] Support timelines

2021-09-16 Thread Orion Poplawski via devel 
Is there any documentation that would indicate how long the 4.0 (or any 
particular release series) will be supported?  This would be helpful for 
establishing downstream timelines.


Thanks!

--
Orion Poplawski
he/him/his - surely the least important thing about me
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 devel] openmpi/pmix compatibility

2021-10-09 Thread Orion Poplawski via devel 
It looks like openmpi 4.1.1 is not compatible with pmix 4.1.0 - is that 
expected?


In file included from ../../../../opal/mca/pmix/base/base.h:22,
 from common_ofi.c:29:
common_ofi.c: In function 'get_package_rank':
common_ofi.c:321:40: error: 'PMIX_PACKAGE_RANK' undeclared (first use in 
this function)

  321 | OPAL_MODEX_RECV_VALUE_OPTIONAL(rc, PMIX_PACKAGE_RANK,
  |^
../../../../opal/mca/pmix/pmix.h:153:56: note: in definition of macro 
'OPAL_MODEX_RECV_VALUE_OPTIONAL'
  153 | if (OPAL_SUCCESS == ((r) = opal_pmix.get((p), (s), 
&(_ilist), &(_kv {\

  |^
common_ofi.c:321:40: note: each undeclared identifier is reported only 
once for each function it appears in

  321 | OPAL_MODEX_RECV_VALUE_OPTIONAL(rc, PMIX_PACKAGE_RANK,
  |^
../../../../opal/mca/pmix/pmix.h:153:56: note: in definition of macro 
'OPAL_MODEX_RECV_VALUE_OPTIONAL'
  153 | if (OPAL_SUCCESS == ((r) = opal_pmix.get((p), (s), 
&(_ilist), &(_kv {\

  |^
make[2]: *** [Makefile:1937: common_ofi.lo] Error 1


--
Orion Poplawski
he/him/his - surely the least important thing about me
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

Re: [OMPI devel] openmpi/pmix compatibility

2021-10-10 Thread Orion Poplawski via devel 

Indeed, 4.1.2rc1 appears to build fine.  Thanks.

On 10/10/21 7:37 AM, Ralph Castain via devel wrote:

It was a bug (typo in the attribute name when backported from OMPI master) in 
OMPI 4.1.1 - it has been fixed.



On Oct 9, 2021, at 9:18 PM, Orion Poplawski via devel 
 wrote:

It looks like openmpi 4.1.1 is not compatible with pmix 4.1.0 - is that 
expected?

In file included from ../../../../opal/mca/pmix/base/base.h:22,
 from common_ofi.c:29:
common_ofi.c: In function 'get_package_rank':
common_ofi.c:321:40: error: 'PMIX_PACKAGE_RANK' undeclared (first use in this 
function)
  321 | OPAL_MODEX_RECV_VALUE_OPTIONAL(rc, PMIX_PACKAGE_RANK,
  |^
../../../../opal/mca/pmix/pmix.h:153:56: note: in definition of macro 
'OPAL_MODEX_RECV_VALUE_OPTIONAL'
  153 | if (OPAL_SUCCESS == ((r) = opal_pmix.get((p), (s), &(_ilist), 
&(_kv {\
  |^
common_ofi.c:321:40: note: each undeclared identifier is reported only once for 
each function it appears in
  321 | OPAL_MODEX_RECV_VALUE_OPTIONAL(rc, PMIX_PACKAGE_RANK,
  |^
../../../../opal/mca/pmix/pmix.h:153:56: note: in definition of macro 
'OPAL_MODEX_RECV_VALUE_OPTIONAL'
  153 | if (OPAL_SUCCESS == ((r) = opal_pmix.get((p), (s), &(_ilist), 
&(_kv {\
  |^
make[2]: *** [Makefile:1937: common_ofi.lo] Error 1


--
Orion Poplawski
he/him/his - surely the least important thing about me
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/







--
Orion Poplawski
he/him/his - surely the least important thing about me
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 devel] Restore OMPI_MCA_rmaps_base_oversubscribe or equivalent

2022-04-22 Thread Orion Poplawski via devel 
When building packages for Fedora, tests must often be run in an 
oversubscribed manner.  It is also often quite difficult to modify the 
command line of those tests.  As such, Fedora has long defined the 
OMPI_MCA_rmaps_base_oversubscribe=1 variable in the build environment to 
allow this to automatically propagate.


This option appears to no longer exist.  Can an equivalent be restored? 
If so, should this RFE be filed against OpenMPI or PRRTE?


Thanks.

--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 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

Re: [OMPI devel] Open MPI 4.1.6rc1 release candidate posted

2023-09-06 Thread Orion Poplawski via devel 

On 8/8/23 07:34, Jeff Squyres (jsquyres) via devel wrote:
There have been enough minor fixes to warrant a 4.1.6 release.  We've 
posted 4.1.6rc1 tarballs in the usual location: 
https://www.open-mpi.org/software/ompi/v4.1/  

..


We would welcome and testing and feedback.



Fedora packages and deps are looking good.

--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 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 devel] Question about the future of C++ API support

2023-10-26 Thread Orion Poplawski via devel 
I see that openmpi 5.0.0 drops the C++ API.  I'm trying to find some 
background on this.


In particular, is this likely to be a permanent change?

Also, have there been discussions of users of the C++ API?  In Fedora we 
seem to have:


MUSIC-1.1.16-13.20201002git8c6b77a.fc39.src.rpm
boost-1.81.0-9.fc40.src.rpm
bout++-5.0.0-11.fc40.src.rpm
coin-or-Ipopt-3.14.12-2.fc39.src.rpm
combblas-2.0.0-4.fc40.src.rpm
freefem++-4.13-6.fc40.src.rpm
ga-5.8.2-2.fc39.src.rpm
gloo-0.5.0^git20230824.01a0c81-6.fc40.src.rpm
gmsh-4.11.1-6.fc39.src.rpm
hpx-1.9.1-1.fc40.src.rpm
intel-mpi-benchmarks-2021.3-4.fc39.src.rpm
libneurosim-1.2.0-8.20210110.gitafc003f.fc39.src.rpm
mathgl-8.0.1-6.fc39.src.rpm
mfem-4.6-1.fc40.src.rpm
nest-3.4-1.fc39.src.rpm
netcdf-cxx4-4.3.1-9.fc39.src.rpm
netgen-mesher-6.2.2202-7.fc39.src.rpm
orsa-0.7.0-61.fc39.src.rpm
python-steps-3.6.0-30.fc39.src.rpm
scalasca-2.6.1-2.fc38.src.rpm

Thanks.

--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 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

Re: [OMPI devel] Question about the future of C++ API support

2023-10-26 Thread Orion Poplawski via devel 

On 10/26/23 21:15, Orion Poplawski via devel wrote:
I see that openmpi 5.0.0 drops the C++ API.  I'm trying to find some 
background on this.




Never mind - I see now that it has been deprecated since 2.0.0, although 
I'm sure it will catch some projects off guard still :)


MUSIC has had a bug open about it for years, but never has changed. 
Perhaps this will kick it.


Some of those listed below seem to build fine without the C++ api 
present as well (boost, coin-or-Ipopt)


So perhaps it won't be that big of a deal.  Sorry for the noise.



In particular, is this likely to be a permanent change?

Also, have there been discussions of users of the C++ API?  In Fedora we 
seem to have:


MUSIC-1.1.16-13.20201002git8c6b77a.fc39.src.rpm
boost-1.81.0-9.fc40.src.rpm
bout++-5.0.0-11.fc40.src.rpm
coin-or-Ipopt-3.14.12-2.fc39.src.rpm
combblas-2.0.0-4.fc40.src.rpm
freefem++-4.13-6.fc40.src.rpm
ga-5.8.2-2.fc39.src.rpm
gloo-0.5.0^git20230824.01a0c81-6.fc40.src.rpm
gmsh-4.11.1-6.fc39.src.rpm
hpx-1.9.1-1.fc40.src.rpm
intel-mpi-benchmarks-2021.3-4.fc39.src.rpm
libneurosim-1.2.0-8.20210110.gitafc003f.fc39.src.rpm
mathgl-8.0.1-6.fc39.src.rpm
mfem-4.6-1.fc40.src.rpm
nest-3.4-1.fc39.src.rpm
netcdf-cxx4-4.3.1-9.fc39.src.rpm
netgen-mesher-6.2.2202-7.fc39.src.rpm
orsa-0.7.0-61.fc39.src.rpm
python-steps-3.6.0-30.fc39.src.rpm
scalasca-2.6.1-2.fc38.src.rpm

Thanks.



--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 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

Re: [OMPI devel] Question about the future of C++ API support

2023-10-30 Thread Orion Poplawski via devel 
Yeah, I discovered most of that after sending my initial email (as usual :( ).

Turns out that only MUSIC still actually depends on the C++ bindings.  While
the others linked to them (perhaps without even using them), a simple rebuild
resolved that.

MUSIC has been aware of the issue for a long time - this was filed in 2016:

https://github.com/INCF/MUSIC/issues/27


On 10/30/23 08:54, Jeff Squyres (jsquyres) wrote:
> The C++ bindings were removed from the MPI-3.0 standard in 2012 -- they've
> been officially deleted for 12 years.  The MPI Forum talked extensively with
> users about this before removing them.  We held on to the C++ bindings here in
> Open MPI for a long time, but finally deleted them in 5.0.0.
> 
> Do you know if the packages you cited actually use the MPI C++ bindings, or
> are they C++ packages that happen to use MPI C bindings?
> 
> One of the reasons that the Forum decided to delete the C++ bindings was
> because C++ app developer community overwhelmingly stated that they used the C
> bindings (because the C++ bindings were almost exactly a 1:1 mapping to the C
> bindings, and didn't offer much more/different functionality than the C
> bindings).  There were a small number of users who actually used the MPI C++
> bindings, but to my knowledge, they all migrated to the C bindings over time.
> 
> --------------
> *From:* devel on behalf of Orion Poplawski via devel
> *Sent:* Thursday, October 26, 2023 11:15 PM
> *To:* Open MPI Development
> *Cc:* Orion Poplawski
> *Subject:* [OMPI devel] Question about the future of C++ API support
> 
> I see that openmpi 5.0.0 drops the C++ API.  I'm trying to find some
> background on this.
> 
> In particular, is this likely to be a permanent change?
> 
> Also, have there been discussions of users of the C++ API?  In Fedora we
> seem to have:
> 
> MUSIC-1.1.16-13.20201002git8c6b77a.fc39.src.rpm
> boost-1.81.0-9.fc40.src.rpm
> bout++-5.0.0-11.fc40.src.rpm
> coin-or-Ipopt-3.14.12-2.fc39.src.rpm
> combblas-2.0.0-4.fc40.src.rpm
> freefem++-4.13-6.fc40.src.rpm
> ga-5.8.2-2.fc39.src.rpm
> gloo-0.5.0^git20230824.01a0c81-6.fc40.src.rpm
> gmsh-4.11.1-6.fc39.src.rpm
> hpx-1.9.1-1.fc40.src.rpm
> intel-mpi-benchmarks-2021.3-4.fc39.src.rpm
> libneurosim-1.2.0-8.20210110.gitafc003f.fc39.src.rpm
> mathgl-8.0.1-6.fc39.src.rpm
> mfem-4.6-1.fc40.src.rpm
> nest-3.4-1.fc39.src.rpm
> netcdf-cxx4-4.3.1-9.fc39.src.rpm
> netgen-mesher-6.2.2202-7.fc39.src.rpm
> orsa-0.7.0-61.fc39.src.rpm
> python-steps-3.6.0-30.fc39.src.rpm
> scalasca-2.6.1-2.fc38.src.rpm
> 
> Thanks.
> 
> --
> Orion Poplawski
> he/him/his  - surely the least important thing about me
> IT Systems Manager 720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane   or...@nwra.com
> Boulder, CO 80301 https://www.nwra.com/ 
> <https://www.nwra.com/>

-- 
Orion Poplawski
IT Systems Manager 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