Skip to content

Meeting 2019 06 07

Jump to bottom
Josh Hursey edited this page Jun 7, 2019 · 2 revisions

Agenda

Notes

        Joshua Hursey (IBM)
	Kathryn Mohror (LLNL)
	Geoffroy Vallee (Sylabs, Inc.)
	Swaroop Pophale (ORNL)
	Thomas Naughton (ORNL)
	Artem Polyakov (Mellanox)
	David Solt (IBM)
	Stephen Herbein (LLNL)
	Ken Raffenetti (ANL)
  • June 14 Meeting: Discussion regarding naming of reference implementation and standard
    • Reaching out to folks:
      • Send meeting announcement (send to both pmix-forum and hpc-runtime)
      • Reply to original email thread
    • Need to enumerate options to discuss (here are some very rough options)
      • Rename Standard Interface (e.g., System Runtime Interface instead of PMIx)
      • Rename Reference Implementation (e.g., PMIx -> Open PMIx)
      • Multiple “mini-standards” (not independent, but governed by the body supporting the use case) per use case grouping
      • Starting a blank page
    • How do we reach consensus and bring this topic to a close
  • https://github.com/pmix/pmix-standard/issues/190
    • No clear consensus on ‘core functionality’
    • Mission statement (some rough options):
      • “Market Driven” approach. Evolve based upon user requests. Stability based on usage/demand. Not unbounded/uncontrolled, but more permissive.
      • “Top-to-Bottom” approach. Tighter control over the inclusion based on ‘core’
      • “Use case groupings” approach. Define use case groupings that are defined by external groups with support requirements. Organize chapters this way.
    • Need for balance in any wording of a mission statement:
      • If mission statement is loosely defined then we risk unconstrained growth.
      • If mission statement is specifically defined then we risk not being general enough.
      • Need to get something in the middle. Hopefully towards the more loosely defined version. Needs to be sufficiently broad.
    • Use case groupings / Slices
      • Example: MPI Forum could define a PMIx Chapter for their needs and govern what goes into the chapter in collaboration with the PMIx Community. Can have a more strict governance for acceptance than the base PMIx community. This chapter is part of the PMIx Standard document.
      • Allows users to easily find the subset of PMIx they want to use.
      • Allows RMs/Libraries to easily find subsets of PMIx they want to focus on for their target markets/users.
    • We have an obligation to be careful about what we include
      • Not a research driven standard - driven by specific use cases…
      • Need more documentation around why certain interfaces are present (traceable to the use case) to help folks determine importance to their target users/market
  • (Dave) Working group update: Implementation agnostic document
  • (Stephen) Working group update: Slicing/Grouping of functionality
  • Question about use case descriptions:

Action Items

  • (Josh) Advertise naming meeting to various lists.

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally