Upgrade macos

macx64/mpi/openmpi/etc/pmix-mca-params.conf

@@ -11,6 +11,7 @@
 #                         All rights reserved.
 # Copyright (c) 2006-2017 Cisco Systems, Inc.  All rights reserved
 # Copyright (c) 2017-2018 Intel, Inc. All rights reserved.
+# Copyright (c) 2022      Nanook Consulting.  All rights reserved.
 # $COPYRIGHT$
 #
 # Additional copyrights may follow
@@ -19,28 +20,28 @@
 #
 
 # This is the default system-wide MCA parameters defaults file.
-# Specifically, the MCA parameter "mca_param_files" defaults to a
+# The MCA parameter "mca_param_files" defaults to a
 # value of
 # "$HOME/.pmix/mca-params.conf:$sysconf/pmix-mca-params.conf"
-# (this file is the latter of the two).  So if the default value of
-# mca_param_files is not changed, this file is used to set system-wide
-# MCA parameters.  This file can therefore be used to set system-wide
-# default MCA parameters for all users.  Of course, users can override
-# these values if they want, but this file is an excellent location
-# for setting system-specific MCA parameters for those users who don't
-# know / care enough to investigate the proper values for them.
+# (this file is the latter of the two).  The list of files are parsed
+# in a right-to-left manner so that the user-level default file values
+# naturally overwrite those from the default system file.  This file
+# can therefore be used to set system-wide default MCA parameters for
+# all users.
 
 # Note that this file is only applicable where it is visible (in a
-# filesystem sense).  Specifically, processes each read this file
-# during their call to PMIx_Init to determine what default values for MCA
-# parameters should be used.  Launchers generally do not bundle up the values in
-# this file from the node where they are run and send them to all nodes;
-# the default value decisions are effectively distributed.  Hence,
-# these values are typically only applicable on nodes that "see" this file.  If
-# $sysconf is a directory on a local disk, it is likely that changes
-# to this file will need to be propagated to other nodes.  If $sysconf
-# is a directory that is shared via a networked filesystem, changes to
-# this file will be visible to all nodes that share this $sysconf.
+# filesystem sense).  Launchers in some PMIx-enabled environments
+# (e.g., PRRTE) will read and forward the values to the backend
+# compute nodes, thus providing for a more scalable startup procedure.
+#
+# For launchers do not provide this service, processes each read this
+# file during their call to PMIx_Init to determine what default values
+# for MCA parameters should be used. This necessitates that the file be
+# visible on all nodes, and can result in significant startup procedure
+# delays as large numbers of processes attempt to simultaneously read/parse
+# the files. Also note that if $sysconf is a directory on a local disk
+# in this case, it is likely that changes to this file will need to be
+# propagated to other nodes prior to launching your job
 
 # The format is straightforward: one per line, mca_param_name =
 # rvalue.  Quoting is ignored (so if you use quotes or escape
@@ -55,5 +56,5 @@
 # Change component loading path
 #   mca_base_component_path = /usr/local/lib/pmix:~/my_pmix_components
 
-# See "pinfo --param all all --level 9" for a full listing of PMIx
+# See "pmix_info --param all all" for a full listing of PMIx
 # MCA parameters available and their default values.

macx64/mpi/openmpi/etc/prte-default-hostfile

@@ -9,13 +9,15 @@
 #                         University of Stuttgart.  All rights reserved.
 # Copyright (c) 2004-2005 The Regents of the University of California.
 #                         All rights reserved.
+# Copyright (c) 2019-2020 Intel, Inc.  All rights reserved.
+# Copyright (c) 2020      Cisco Systems, Inc.  All rights reserved
 # $COPYRIGHT$
 #
 # Additional copyrights may follow
 #
 # $HEADER$
 #
-# This is the default hostfile for Open MPI.  Notice that it does not
+# This is the default hostfile for PRTE.  Notice that it does not
 # contain any hosts (not even localhost).  This file should only
 # contain hosts if a system administrator wants users to always have
 # the same set of default hosts, and is not using a batch scheduler
@@ -25,12 +27,10 @@
 # environments (e.g., running in a job under a job scheduler, such as
 # SLURM or PBS / Torque).
 #
-# If you are primarily interested in running Open MPI on one node, you
-# should *not* simply list "localhost" in here (contrary to prior MPI
-# implementations, such as LAM/MPI).  A localhost-only node list is
+# If you are primarily interested in running PRTE on one node, you
+# should *not* simply list "localhost" in here.  A localhost-only node list is
 # created by the RAS component named "localhost" if no other RAS
 # components were able to find any hosts to run on (this behavior can
 # be disabled by excluding the localhost RAS component by specifying
 # the value "^localhost" [without the quotes] to the "ras" MCA
 # parameter).
-

macx64/mpi/openmpi/etc/prte-mca-params.conf

@@ -0,0 +1,55 @@
+#
+# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
+#                         University Research and Technology
+#                         Corporation.  All rights reserved.
+# Copyright (c) 2004-2005 The University of Tennessee and The University
+#                         of Tennessee Research Foundation.  All rights
+#                         reserved.
+# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
+#                         University of Stuttgart.  All rights reserved.
+# Copyright (c) 2004-2005 The Regents of the University of California.
+#                         All rights reserved.
+# Copyright (c) 2006-2020 Cisco Systems, Inc.  All rights reserved
+# Copyright (c) 2018-2020 Intel, Inc.  All rights reserved.
+# $COPYRIGHT$
+#
+# Additional copyrights may follow
+#
+# $HEADER$
+#
+
+# This is the default system-wide MCA parameters defaults file.
+# Specifically, the MCA parameter "mca_param_files" defaults to a
+# value of
+# "$HOME/.prte/mca-params.conf:$sysconf/prte-mca-params.conf"
+# (this file is the latter of the two).  So if the default value of
+# mca_param_files is not changed, this file is used to set system-wide
+# MCA parameters.  This file can therefore be used to set system-wide
+# default MCA parameters for all users.  Of course, users can override
+# these values if they want, but this file is an excellent location
+# for setting system-specific MCA parameters for those users who don't
+# know / care enough to investigate the proper values for them.
+
+# Note that this file is only applicable where it is visible (in a
+# filesystem sense) by PRTE daemons.  Hence,
+# these values are only applicable on nodes that "see" this file.  If
+# $sysconf is a directory on a local disk, it is likely that changes
+# to this file will need to be propagated to other nodes.  If $sysconf
+# is a directory that is shared via a networked filesystem, changes to
+# this file will be visible to all nodes that share this $sysconf.
+
+# The format is straightforward: one per line, mca_param_name =
+# rvalue.  Quoting is ignored (so if you use quotes or escape
+# characters, they'll be included as part of the value).  For example:
+
+# Select a particular routing component
+#   routed = binomial
+
+# Note that the value "~/" will be expanded to the current user's home
+# directory.  For example:
+
+# Change component loading path
+#   mca_base_component_path = /usr/local/lib/prte:~/my_prte_components
+
+# See "prte_info --param all all --level 9" for a full listing of
+# PRTE MCA parameters available and their default values.

macx64/mpi/openmpi/etc/prte.conf

@@ -0,0 +1,76 @@
+#
+# Copyright (c) 2023      Nanook Consulting.  All rights reserved.
+# $COPYRIGHT$
+#
+# Additional copyrights may follow
+#
+# $HEADER$
+#
+# The PMIx Reference RunTime Environment (PRRTE) can be instantiated
+# as a Distributed Virtual Machine (DVM) in two ways. First, the
+# `prte` command can be executed at a shell prompt. This will discover
+# the available resources (either from hostfile or as allocated by a
+# resource manager) and start a PRRTE shepherd daemon (`prted`) on each
+# of the indicated nodes.
+#
+# The other method, however, is to bootstrap the DVM at time of cluster
+# startup. Bootstrapping PRRTE allows the DVM to serve as the system-level
+# runtime, providing a full-service PMIx environment to sessions under
+# its purview. Integration to an appropriately enabled scheduler can
+# provide a full workload managed environment for users.
+#
+# Establishing the DVM using the bootstrap method requires that a PRRTE
+# configuration file be created and made available on every node of the
+# cluster at node startup. The configuration file provides necessary
+# information for establishing the communication infrastructure between
+# the DVM controller and the compute node daemons. It also provides a
+# means for easily defining DVM behavior for options such as logging,
+# system-level prolog and epilog scripts for each session, and other
+# PRRTE features.
+#
+# The configuration file can be manually created or can be created using
+# the PRRTE configuration tool ``<install-location>/etc/prte-configurator.html``
+# running in the browser of your choice. Manual creation can best be done
+# by editing the example configuration file (``<source-location>/src/etc/prte.conf``).
+# This file contains all the supported configuration options, with all
+# entries commented out. Simply uncomment the options of interest and
+# set them to appropriate values. The file will be installed into the
+# final ``<install-location>/etc`` when ``make install`` is performed.
+#
+# The configuration tool also contains all the supported options in an
+# easy-to-use form. Once you have filled out the desired entries, the
+# "submit" button will show the resulting configuration file on the
+# browser window - a simple "copy/paste" operation into your target
+# configuration file will yield the final result.
+#
+# Configuration Options
+# ---------------------
+#
+# The following options are supported by this version of PRRTE.
+# While we make every effort to maintain compatibility with prior versions,
+# we recommend that you check options when installing new versions to
+# see what may have changed and/or been added. We also recommend that
+# you use the prte-configurator.html for the version you are using to
+# ensure that it is fully compatible.
+#
+# Bootstrap Options
+# -----------------
+#ClusterName=cluster
+#DVMControllerHost=host0
+#DVMControllerPort=7817
+#PRTEDPort=7818
+#DVMNodes=
+#
+# Operational Options
+# -------------------
+#DVMTempDir=/tmp
+#SessionTmpDir=/tmp
+#
+# Logging Options
+# ---------------
+#ControllerLogJobState=undefined
+#ControllerLogProcState=undefined
+#ControllerLogPath=
+#PRTEDLogJobState=undefined
+#PRTEDLogProcState=undefined
+#PRTEDLogPath=