Skip to content

Meeting 2020 06 12

Jump to bottom
Stephen Herbein edited this page Jun 17, 2020 · 1 revision

Agenda

Attendees:

    Kathryn Mohror (LLNL)
    Josh Hursey (IBM)
    Swaroop Pophale (ORNL)
    Thomas Naughton (ORNL)
    Michael Karo (Altair)
    Ralph Castain (Intel)
    Shane Snyder (ANL)
    Aurelien Bouteiller (UTK)
    Dave Solt (IBM)

Notes:

  • Next meetings reminders
    • July 10 is next monthly meeting
    • July 22 is next quarterly ASC meeting
  • Q4 2020 Quarterly Meeting Update
    • Plan to make this virtual meeting
    • Feedback - seems like wise decision, labs and others have travel suspended
    • Oct 1
  • State of PMIx website (Stephen Herbein, Thomas Naughton) https://pmix.github.io/
  • PMIx v4 update
    • Bringing the fabrics sections together, choosing to use "fabrics" instead of “networks” to be more uniform. Changes in “fabric” chapter and associated attributes, See PR#243 https://github.com/pmix/pmix-standard/pull/243
      • No strong opinions about fabric/network
      • Suggestion to possibly put remark that clarifies when referring to network fabric, it means xyz. Just add text to define terms to be clear.
    • Please send feedback
    • Other remaining item to complete is the Tools area
    • Commercial vendors are finished updating to the PMIx tools items and ready to release products
    • Targeting July for release of v4 of standard
    • Will need to synchronize WG updates for addition to v4 doc release to make sure things are not too difficult to maintain
    • TODO: synchronize WG updates for v4 doc
  • Working group repositories (Kathryn Mohror, Josh Hursey)
    • Slicing and Dynamics have repos
    • Want to have WG members to have freedom to make changes to standard, have wikis, issues, etc. to manage changesets and work. Then can organize that for pull-requests up to the main/top-level Standard repo.
    • This helps WG to manage those permissions, etc.
    • Following MPI-Forum’s methods for this process
      • Example
        • Main repo (mpi-standard)
        • Tools WG - fork of mpi-standard and they work on that
          • When make changes and ready for taking to main repo, can create a PR to the master (origin) repo
      • This is one model for how to manage and works for MPI forum
      • Open to suggestions for other models, with the intent being to assist the WGs making progress
      • The MPI model would be helpful and approach of having the new organizations (github magic) will help to streamline the contributions back up. Current PMIx structure can be more prone to some problems
      • Will work to get this with WGs
      • Main difference is that MPI-Forum is an "official" non-profit in the eyes of Github, which allows for creating some freedom on private repos, etc.
      • There are some changes on Github private repos now, but could be limit in the number of members in organization. The non-profit designation lifts this limitation. So may be worth investigation of getting non-profit designation for PMIx w/ Github to make things easier when following MPI-Forum model.
      • Could possibly look into the open-source legal management stuff to manage the "organization", could then collect some funds to pay for things like Github org, etc.
      • Ralph looked into this for Open MPI
      • Likely a good idea to look into this for PMIx and it could also cover things like the domain registration, etc. Currently Ralph is paying that.
      • Talked about having that transfer to UTK, but might also be useful for having these types of organization items to investigate things.
      • Note: Open MPI went with Software in the Public Interest (SPI) **http://spi-inc.org**/
      • Note: the other option they considered was http://sfconservancy.org/members/current
  • Indexing in the standard (Josh Hursey) https://github.com/pmix/pmix-standard/pull/241
    • Split index of document by topic to help when navigating to find things
      • General -- turns into definitions, etc.
      • API - Want to include both main API and the Python version
      • Support Macros
      • Data Structures
      • Constants
      • Attributes
    • Feedback: Might want to avoid using the "Definition" and the page and just make that the bold case.
    • Feedback: Like having Macros and APIs separate, etc. Generally positive
    • Please comment on pull request if have other comments/suggestions
  • Working Group Updates:
    • Stephen Herbein: Slicing/Grouping of functionality
      • Stephen out, Swaroop giving update
      • Idea to spin off another WG on Power - anyone can join
        • Initial meeting on Jun 24 12pm-1pm ET
        • Wiil gauge interest to see if should create separate WG
      • Working to integrate changes for hybrid prog models
      • Also planning to look into MPI Sessions use case (help welcome)
      • Trying to figure out way to add code examples, which could be compiled in repo but keep code snippets in the doc
      • Email WG
    • Shane Snyder: Storage
      • Looking into proper storage query bits
      • Exploring code from Ralph for looking into storage query using statfs, get things like inodes used, etc. Use this to get some data for PMIx query on storage
      • Statfs not cover things like user quotas on HPC system, etc. Working through some of the semantics to look into those types of queries.
      • Next would be related to APIs for data movement
      • Starting with the query interfaces to get things started. Starting to get some code together and will sync w/ others to figure out how to get those bits into right repos to share things.
    • Jai Dayal: Dynamic workflows
      • Not available (possibly standing conflict)
      • WG meeting later today, agenda is for status updates. Possibly attend that meeting to get status update. Several presentations in those meetings in past.
    • Dave Solt: Implementation agnostic document
      • Setting new WG meeting time, current choices:
        • Mon 1-2 CT
        • Thu 3-4 CT
      • Taking step back to see how best to move forward
      • Been reviewing Ch.5 that gets more into interfaces, in contrast to earlier more introductory chapter(s)
      • Looking at best way to separate the client/server/tools sides to make things easy for users.
      • Ch4 changes from Josh in-progress
      • Starting to get little more involved for changes in main body chapters b/c they could require more significant restructuring, early chapters more stand alone.
      • Posted PR for comment and possibly finish off in prep for next Quarterly
  • Next meetings:
    • July 10 - monthly
    • July 22 - quarterly
      • Please send quarterly content/agenda items to Josh/Katheryn by end of June

Home

Working Groups

Events

Helpful How To...

ASC Quarterly Meetings

ASC Monthly Meetings

Clone this wiki locally