Remove the psched pseudo-scheduler

The community has decided to move this to an external project
by reviving the "DynaSched" project - see https://github.com/dynasched/dynasched
for details

Signed-off-by: Ralph Castain <rhc@pmix.org>

.gitignore

@@ -161,7 +161,6 @@ src/tools/prte/prte
 src/tools/pcc/pcc
 src/tools/pcc/pcc-wrapper-data.txt
 src/tools/pterm/pterm
-src/tools/psched/psched
 
 src/util/hostfile/hostfile_lex.c
 src/util/keyval/keyval_lex.c

config/prte_config_files.m4

@@ -4,7 +4,7 @@
 # Copyright (c) 2016-2020 Intel, Inc.  All rights reserved.
 # Copyright (c) 2019      Research Organization for Information Science
 #                         and Technology (RIST).  All rights reserved.
-# Copyright (c) 2022-2023 Nanook Consulting.  All rights reserved.
+# Copyright (c) 2022-2024 Nanook Consulting  All rights reserved.
 # $COPYRIGHT$
 #
 # Additional copyrights may follow
@@ -26,6 +26,5 @@ AC_DEFUN([PRTE_CONFIG_FILES],[
         src/tools/prte_info/Makefile
         src/tools/prte/Makefile
         src/tools/pterm/Makefile
-        src/tools/psched/Makefile
     ])
 ])

config/prte_setup_pmix.m4

@@ -79,10 +79,6 @@ AC_DEFUN([PRTE_CHECK_PMIX],[
                   [AS_HELP_STRING([--disable-pmix-lib-checks],
                                   [If --disable-pmix-lib-checks is specified, configure will assume that -lpmix is available])])
 
-    AC_ARG_WITH(prte-scheduler,
-        AS_HELP_STRING([--with-prte-scheduler],
-                       [Normal PRTE users/applications do not need this.  Users/applications wishing to explore dynamic allocation support probably do (default: enabled).]))
-
     prte_pmix_support=1
 
     if test "$with_pmix" = "no"; then
@@ -181,35 +177,5 @@ AC_DEFUN([PRTE_CHECK_PMIX],[
 
     PRTE_SUMMARY_ADD([Required Packages], [PMIx], [], [$prte_pmix_SUMMARY])
 
-    #
-    # Do we want to install the PRRTE scheduler?
-    #
-    AC_MSG_CHECKING([if want to install PRRTE pseudo-scheduler])
-    if test "$prte_pmix_low_version" = "0"; then
-        if test "$with_prte_scheduler" = "no"; then
-            AC_MSG_RESULT([no])
-            prte_want_scheduler="no"
-            WANT_PRTE_SCHED=0
-        else
-            AC_MSG_RESULT([yes])
-            prte_want_scheduler="yes"
-            WANT_PRTE_SCHED=1
-        fi
-    else
-        if test "$with_prte_scheduler" = "yes"; then
-            AC_MSG_RESULT([yes])
-            AC_MSG_WARN([Pseudo-scheduler requested, but PMIx version])
-            AC_MSG_WARN([is too low. Please reconfigure with a version])
-            AC_MSG_WARN([of at least v6.0])
-            AC_MSG_ERROR([Cannot continue.])
-        else
-            prte_want_scheduler="no"
-            WANT_PRTE_SCHED=0
-        fi
-    fi
-    AM_CONDITIONAL(WANT_PRTE_SCHED, test "$WANT_PRTE_SCHED" = 1)
-    PRTE_SUMMARY_ADD([Miscellaneous], [PRTE Pseudo-Scheduler], [], [$prte_want_scheduler])
-
-
     PRTE_VAR_SCOPE_POP
 ])

docs/Makefile.am

@@ -68,7 +68,6 @@ PRTE_MAN1 = \
         prted.1 \
         prterun.1 \
         prun.1 \
-        psched.1 \
         pterm.1
 
 PRTE_MAN5 = \

docs/how-things-work/schedulers/index.rst

@@ -3,8 +3,7 @@ Scheduler Integration
 =====================
 
 This section describes PRRTE support for interactions
-with schedulers, including PRRTE's own ``psched``
-pseudo-scheduler.
+with schedulers.
 
 .. toctree::
    :maxdepth: 2

docs/how-things-work/schedulers/overview.rst

@@ -6,18 +6,3 @@ operations as a means of providing users and researchers with an environment wit
 which they can investigate/explore dynamic operations. It will , of course, interact
 with any PMIx-based scheduler to support allocation requests and directives for
 executing jobs within an allocation.
-
-In addition, however, PRRTE provides a pseudo-scheduler for research purposes. The
-``psched`` daemon is not a full scheduler - i.e., it does not provide even remotely
-optimal resource assignments, nor is it in any way production qualified. For example,
-the ``psched`` algorithms are not particularly fast and are focused more on providing
-functionality than supporting large volumes of requests.
-
-Within that context, ``psched`` will:
-
-* assemble a resource pool based on the usual PRRTE resource discovery methods. This
-  includes reading the allocation made by a host environment, or provided by hostfile
-  and/or dash-host command line options.
-
-* upon receipt of allocation requests (either directly from tools or relayed by PRRTE),
-  check to see if the specified resources are available.

docs/man/man1/index.rst

@@ -9,5 +9,4 @@ Commands (section 1)
    prted.1.rst
    prterun.1.rst
    prun.1.rst
-   psched.1.rst
    pterm.1.rst

docs/session-directory.rst

@@ -46,7 +46,7 @@ By default, the session directory name is set to
 
 where `tool` is the argv[0] of the process setting up the
 session directory. In most cases, this will be either `prte`,
-`prterun`, or `prted` - though special tools such as `psched`
+`prterun`, or `prted` - though special tools
 may also create a session directory tree.
 
 The session directory name includes the PID

src/docs/Makefile.am

@@ -38,7 +38,6 @@ dist_prtedata_DATA = \
         show-help-files/help-prted.txt \
         show-help-files/help-prterun.txt \
         show-help-files/help-prun.txt \
-        show-help-files/help-psched.txt \
         show-help-files/help-pterm.txt \
         show-help-files/help-ras-base.txt \
         show-help-files/help-ras-pbs.txt \