NordicHPC / NordicHPC/slurm2sql

Who uses slurm2sql? What are your use cases?

Open
#16 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
19
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I started this to fill a need, but there are clearly some other users here so I'm wondering: what do you use this for? How important is it? What do you need?

Here are some of my principles:

  • All values are the most basic (metric) units: bytes, seconds, seconds-since-epoch, etc.
  • Try to use existing column names as much as possible.
  • Try to support as many Slurm versions as possible, but if something becomes hard to support, don't worry too much about breaking compatibly. SchedMD support slurm for 18 months after release. Try to support at least those versions.
  • Don't try to maintain database compatibility. It's expected that for all schema changes, you have to delete and re-import. But try to avoid this if not needed.

Most things are added based on our site's own needs, but I wonder if more flexibility is needed for use by others?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by reviewing the three existing comments and the project's current Slurm accounting and SQLite behavior; the issue does not define a concrete change or a testable completion condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, sqlite
Domain
data, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.