Meeting 2024 02 01 - openpmix/openpmix GitHub Wiki

February 1, 2024 OpenPMIx-devel call notes

Attendees

  • Aurelien Bouteiller (UTK)
  • Tim Wickberg (SchedMD)
  • Thomas Naughton (ORNL)
  • Amir Shehata (ORNL)

Notes

  • Next releases

    • OpenPMIx-4.2.9 and PRRTE-3.0.4 planned for release Friday afternoon
    • Any concerns, please speak up now (before noon Ralph time 2-feb-2024)!

  • CI resources

    • UTK starting on CI setup for multi-node tests
    • Currently getting started, have identified a person to help with work

  • Online docs discussion

    • Looking into this based on recent discussions at PMIx Q1-2024 related to Use Case Examples, Howto's, etc. and need to:
      • a) make existing material more accessible, and
      • b) add more examples to support Use Cases, etc.
    • Did a quick review and have ~5 spots for "docs"
      • github wiki: prrte (small amt of stuff)
      • github wiki: openpmix
      • openpmix.org webpages
      • ReadTheDocs: docs.openpmix.org
      • ReadTheDocs: docs.prrte.org
    • We have examples in github examples/ dir that cover some use-cases
    • Question about whether we want to house the examples in Webpage (jekyll website), or instead restructre website and point to ReadTheDocs sites for examples. Leverage RTD for the existing/new material.
    • Few thoughts/take-aways from discussion
      • General discussion was to relocate prrte-wiki content (small) elsewhere and have single openpmix.wiki (meeting notes, etc.)
      • Revise layout of website for better structure to find things, e.g., presentations, pointers to documentations, downloads/releases.
      • Use ReadTheDocs areas (openpmix & prrte) for new content.
      • This helps to reduce locations where info lives, also can be a vetting phase to prune older items (not nec. delete but maybe put a marker saying "OLD", etc.)
      • RTD also fits better with our current workflows of PRs to github and simple sphinx tooling for all docs
      • Website (or wiki) also better location to house PDFs, presentations, etc. as the RTD content lives in source/docs/ dir
      • Run ideas by Ralph and others to get his thoughts

  • Updates on project asset migration

    • At PMIx Q1-2024 meeting discussed the moving to HPSF
    • After second review, plan seems to be to stay put for now with SPI
    • Q: Any need/urgency to transfer assets now (e.g., to SPI)?
    • Unsure and maybe we just put in SPI. HPSF is still forming and any actions w.r.t. that option are likely ~year out.
    • Maybe start be getting list of assets needing to be changed, irrespective of where the are transferred to.
    • TODO: Thomas will start email thread with Ralph to get thoughts and we can iteration via email or maybe github issue to list relevant assets