Sync meeting 2025 07 01 - multixscale/meetings GitHub Wiki

MultiXscale WP1+WP5 sync meetings

Next meetings

  • Tue 1 July 2025 09:30 CEST
    • rescheduled from 8 July
  • Tue 12 August 2025 09:30 CEST
  • Tue 9 September 2025 09:30 CEST
    • 3 days before review

Agenda/notes 2025-07-01

attending:

  • Thomas
  • Julian
  • Alan
  • Giulia
  • Lara
  • Pedro
  • Richard
  • Susana
  • Caspar
  • Satish

General

  • Alan: EOSC call happened

    • You can access cloud resources already as a researcher
    • Alan tried it out
    • They have some 'tools'. One of them just starts a VM. Another creates a SLURM cluster.
    • They're a bit 'rough', e.g. default shell is sh, they give you disk but permissions are wrong so you don't have access, etc
    • Alan presented EESSI. Went well, demo was smooth, was on their resources
    • Got an email for follow up
      • One option is to offer it through the 'tools' service.
      • Second step would be to maintain it, that would require resources. Not sure where that would go.
      • That would require a candidate node. That could be SURF, as SURF essentially already put up their hand for this in a call that's being prepared.
      • Last step would be a stratum 1 within their own network / each node site. Would likely fall in the SURF effort.
    • Will look good for us for the review, that we've had this negotiation
    • Very little scaling in their resources.
      • Only spinning up/down resources through web interface.
      • You pay for the maximum capacity you're allowed to use, whether the VM is running or not
    • CPU and GPU resources, not sure which

  • Caspar: Periodic Report => see notes taken in

    • WP1 periodic report for 2nd period
    • WP5: Caspar will ask Petra if she can add the responses for the objectives (or copy it myself)
    • WP6/7: Also discussed, divided responsibilities

  • Agreed: We'll do the quarterly reports for WP1 & 5, but only bullets + amount of effort. It can serve as input for the periodic report

  • Kenneth: will plan a follow-up meeting, propose 4th of August

Deliverables due M30

  • All deliverables were submitted on time

WP status updates

  • Skipped, focussed on the periodic report