sync meeting 2023 01 10 - multixscale/meetings GitHub Wiki

Sync meeting 2023-01-10

Attending: Kenneth, Satish, Alan, Thomas, Ewald, Elisabeth, Bob, Xavier, Susana

Excused: Caspar, Henk-Jan

  • MXS kickoff meeting is being planned by NIC
    • end of March?
  • first deliverables due
    • diss. + comm. plan (HPCNow!) - due in M3
      • no MXS website yet (Alan grabbed multixscale.eu URL a while ago already)
      • prepare press release?
        • to be published by each institute on website/social media
      • incl. email address [email protected] that gets forwarded to somewhere else behind the scenes
      • should we put a single-page placeholder in place at multixscale.eu for now?
      • we should have something in place by EuroHPC summit week
      • also social media: LinkedIn, Twitter (+ Mastodon?)
      • also newsletter (which just links to articles on website)
    • other deliverables are responsibility by NIC (proj. mgmt stuff)
  • planning of these MXS sync meetings (service WPs)
    • monthly seems OK
      • 2nd Tuesday of the month, 10:00-11:00 CET
    • scope: high-level, progress update on WP1/5/7, are we still on track
    • other focused meetings for support effort, etc.
  • Communication plan:
    • WP 7: Website, Linkedin and Twitter. Should we start now with them or wait until kick-off? NIC leads this task.
    • Communicate the starting of multixscale project in our own networks. Now or after KO?
  • WP1 status (lead: SURF)
    • T1.1 (D1.1 - M12?) Providing a stable, optimized, shared scientific software stack with support for established system architectures
    • cfr. https://github.com/EESSI/meetings/blob/main/meetings/EESSI_meeting_20230105.pdf
    • planning to kickstart new EESSI pilot version soon
    • RUG is looking dedicated hardware for new Stratum-0, will be used for new CVMFS repos under eessi.io domain
      • we can already start using eessi.io on current Stratum-0 for next pilot version
      • dedicated hardware mostly motivated by having secure setup (whitelist signing with yubi key)
      • funding is there in MXS for the hardware ($10k)
      • we need to figure naming scheme for repositories in eessi.io (devel, unstable, ...)
  • WP5 status (lead: UGent)
    • T5.3 (D5.1 - M12) Facilitating community contributions to the central software stack
      • actively involved: Thomas (UiB), Kenneth (UGent), Bob (RUG)
      • 1st meeting Thu, 5 Jan 2023; next meetings: bi-weekly from 17 Jan 2023, 09:00 CET
      • discussed status of EESSI bot
      • agreed on next steps, assigned tasks
      • first goal is to make bot good enough so we can actually "expose" contributors to it
      • we definitely intend to use the bot to build next (pilot) version software layer
    • D5.2 support portal (due M12), for T5.1
      • TODO for UGent
      • which alternatives to compare?
        • JIRA, GitHub, ...
      • aspects
        • openess of discussion, solution
        • being able to archive in case we need to move to another platform (actually evaluate this)
      • scope of support
        • installation requests
        • problem reports (X doesn't work)
        • discriminate between supporting partners & others (auto-reply in issues that they'll be handled best effort)
      • take long-term sustainability in mind from the start?
  • revisit cross-WP milestones
    • example is software requires for WP 2-4
  • one page poster for EuroHPC summit week (March 20-23)