Ticket 11489

Summary: Provide build support for pmix v4
Product: Slurm Reporter: Mathis Clayer <mathis.clayer>
Component: PMIxAssignee: Felip Moll <felip.moll>
Status: RESOLVED DUPLICATE QA Contact:
Severity: 4 - Minor Issue    
Priority: ---    
Version: 20.11.3   
Hardware: Linux   
OS: Linux   
Site: Atos/Eviden Sites Alineos Sites: ---
Atos/Eviden Sites: Grenoble Confidential Site: ---
Coreweave sites: --- Cray Sites: ---
DS9 clusters: --- HPCnow Sites: ---
HPE Sites: --- IBM Sites: ---
NOAA SIte: --- OCF Sites: ---
Recursion Pharma Sites: --- SFW Sites: ---
SNIC sites: --- Linux Distro: ---
Machine Name: CLE Version:
Version Fixed: Target Release: ---
DevPrio: --- Emory-Cloud Sites: ---

Description Mathis Clayer 2021-04-29 08:45:35 MDT
Hello,
Is it possible to provide the support for pmix v4 ? There are some minor changes to be done in order to build Slurm with this version of pmix:

Inside: auxdir/x_ac_pmix.m4:

   AM_CONDITIONAL(HAVE_PMIX, [test $_x_ac_pmix_v1_found = "1"] ||
                 [test $_x_ac_pmix_v2_found = "1"] ||
-                [test $_x_ac_pmix_v3_found = "1"] )
+                [test $_x_ac_pmix_v3_found = "1"] ||
+                [test $_x_ac_pmix_v4_found = "1"] )
   AM_CONDITIONAL(HAVE_PMIX_V1, [test $_x_ac_pmix_v1_found = "1"])
   AM_CONDITIONAL(HAVE_PMIX_V2, [test $_x_ac_pmix_v2_found = "1"])
   AM_CONDITIONAL(HAVE_PMIX_V3, [test $_x_ac_pmix_v3_found = "1"])


Inside src/plugins/pmi/pmix/mpi_mpix.c:

 const char plugin_type[] = "mpi/pmix_v2";
 #elif (HAVE_PMIX_VER == 3)
 const char plugin_type[] = "mpi/pmix_v3";
+#elif (HAVE_PMIX_VER == 4)
+const char plugin_type[] = "mpi/pmix_v4";
 #endif
 
I hope I didn't forget any change to support pmix_v4.

Best regards,
Mathis.
Comment 1 Felip Moll 2021-04-29 10:26:42 MDT
Hi Matis,

Thanks for your report. We are tracking this issue in bug 7263 but pmix/v4 is not supported yet. This bug is open so you can read through it if you are interested, but briefly there are some functions that need to be added to our api to support this.

I am marking this issue as a dup of 7263.

*** This ticket has been marked as a duplicate of ticket 7263 ***