Skip to content

Meeting 2020 05 08

Jump to bottom
Stephen Herbein edited this page May 13, 2020 · 2 revisions

Agenda

Attendees:

Kathryn Mohror (LLNL)
	Josh Hursey (IBM)
	Ken Raffenetti (ANL)
	Ralph Castain (Intel)
	Shane Snyder (ANL)
	John DelSignore (Perforce)
	Stephen Herbein (LLNL)
	Mahdieh Ghazimirsaeed (OSU)
	Thomas Naughton (ORNL)
	Michael Karo (Altair)
	Aurelien Bouteiller (UTK)
	David Solt (IBM)

Notes:

  • Update from Slicing working group on introducing use cases into standard document Notes:
  • WG Updates
    • Functionality Slices
      • Integrated feedback from quarterly and adding to latex/standard, interested to get some feedback on the formatting for use-cases
      • Swaroop looking into MPI Sessions - open call for interests in MPI Sessions use case and getting that written up
      • Josh moving MPIR tests into PRRTE tests, which might plug into debug use-case. Josh working with IBM developer and looking to streamline those tests with CI, etc.
    • Storage
      • Ralph prototyped some of the query functions for storage pieces in openpmix to do the prototyping needed, e.g., query space available, num inodes, etc.
      • Next is to work on summarize currently available and starting to work up what could go into standard/spec and get ideas on any gaps in storage related queries
      • Later look into more mechanism/action pieces for data movement (future)
    • Dynamic Workflows
      • Speaking with Swift and ADIOS teams to better understand their workflow managers and their requirements.
      • Working with both teams to hook into PMIx to do Comm_Spawn, use event library, and resource allocation interfaces
      • Thomas got PRRTE up and running on Summit.
      • Working towards getting Swift up and running on Summit
      • Robert Clay to present at SNL abou tasking runtimes and Balsam workflow manager
    • Implementation Agnostic
      • Took feedback from first reading of Ch2 and made a PR/updates
        • Will be posting a strawpoll
      • Need to determine if changes were sufficient to require a re-reading
        • Opinion is that they are mainly wordsmith, no major semantics changes
      • Been moving forward onto Ch 3, the macros and the data structures
        • Would making certain data structures opaque make sense? Only the init/finalizers
        • Re-visiting strategy for this chapter due to its size
        • Is re-organizing the chapter the right effort for this WG?
      • Always open to people stopping in
        • In particular, this week want input into organization
      • Ralph: organizing and ordering things, especially all of the constants, structures, etc will take a long time. Suggestion: focus on the primary objective of the WG and we can always loop back and focus on ordering
  • Stephen show example of Ch3 Use-Cases in standard for feedback
    • Q: Like the format? Want in spec or separate?
    • Kathryn: Like this format, only concern is whether it should be in standard doc, or if these grow it could get large.
    • Ralph: Yes, good point. Possibly at this stage, having it in one place is useful and then as things mature, possibly pull out into separate doc. Possibly useful to having them all together - example of jumping to standard/API is useful when in single doc.
    • Concern about having the API spec creep into use-case descriptions, just trying to think about pro/con.
    • Good to have API / use-case references. Possibly do that linkage via a pointer to use-case (named) and can later jump if live separate, just as a for instance.
    • Regardless, all agreed this is useful and good.
    • Note that this includes example code/working program, which is nice to provide context for the use-cases.
    • LaTeX goodies are using macros to keep the internals consistent and avoid having lots of duplications and possibly have skew.
    • Q: Can you have LaTeX hyperrefs to other docs from PDF?
    • Not sure, possibly.
    • Ralph: Checked and you can reference page in PDF file. Possible to link to section in a separate doc.
    • Comment - The example programs when getting into PMIx (as new user) were very helpful. Encourage we package a “Virtual Ralph” with the docs too! :-)
    • Note about MPI Forum, they have working programs that you can link for checks. Possibly could do similar thing here and back examples for checking things to ensure they are correct. But these are very valuable, but size may be a factor for inclusion into text. Maybe a repo for those examples could be good alternative.
    • Good idea to pulling snippets from working programs would be useful, also to avoid having errors in the examples.
  • Next monthly June 12, 2020
  • Any update on git forks into individual WGs?
    • Stephen - our working group interested
    • Josh - we can sync to see if you are ready to be guinea pigs :-)
    • Josh/Stephen/Kathryn can sync on this
  • Ralph - spec version 4
    • Updates recently indicate can proceed and release v4 and consolidate things to avoid having many forks
    • Good to have Python to check header/attributes

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally