2026.03.09

LDMS User Group Meeting – March 9, 2026

• LDMSCON2026 announcement (registration open, call for contributions open)
• Multi-tenant Monitoring Series: Open Floor for Community Discussion

LDMSCON2026 – June 9–11, 2026 | David Rubenstein Forum, UChicago

• Registration: (https://ldmscon2026.eventbrite.com/)
• Call for Contributions : (https://easychair.org/conferences/?conf=ldmscon2026)
• Info & website: (https://sites.google.com/view/ldmscon2026)

Summary of Open Floor Discussion

The discussion covered two related topics around security in multi-tenant LDMS deployments.

ldms_msg and per-job metrics

A community member (LLNL) asked whether ldms_msg is required for per-job metrics collection. The answer is no — metrics can be read directly from the cgroup filesystem. The concern raised is that ldms_msg currently lacks authorization controls. Existing ldmsd authentication relies on Munge. A related discussion thread from ~2 years ago will be shared with the group.

Sidecar ldmsd architecture — security challenges

Running ldmsd as a sidecar inside a job container and connecting it to an ldmsd on the host or a remote node raises security concerns. Two issues were identified:

1. Munge cross-boundary authentication — Munge may not work across the container-to-host boundary.
2. User identity mismatch — UIDs inside a container may not exist on the host.

GUID was raised as a potential approach to address the identity mismatch.

Next Steps: A smaller working group will be formed to assess the practicality of the framework and infrastructure before committing to a design direction.

Slides from the meeting: (https://github.com/ovis-hpc/ovis-wiki/blob/main/LDMS-UG-03-09-2026.pdf)