Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment architecture, etc #248

Open
lars-t-hansen opened this issue Feb 5, 2025 · 0 comments
Open

Deployment architecture, etc #248

lars-t-hansen opened this issue Feb 5, 2025 · 0 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@lars-t-hansen
Copy link
Collaborator

Some preliminary notes, to be fleshed out.

For a typical cluster we'll have:

  • one sonar per node for sampling
  • one sonar per node for sysinfo
  • at least one sonar per cluster for slurm data, but probably more than one for redundancy - depends on where, how often
  • some kind of exfiltration method
  • a remote database for storage
  • maybe an on-cluster broker for message forwarding, TBD

There are various scripts for these things currently kept in the Jobanalyzer repo but that's not a great place for them. It's unclear if Jobanalyzer can handle all the redundancy of slurm data that would result from having the slurm agent run on multiple nodes. There isn't any documentation.

@lars-t-hansen lars-t-hansen added enhancement New feature or request question Further information is requested labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant