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

job-archive-interface: clean up which data is fetched for job-usage calculation #354

Closed
Tracked by #356
cmoussa1 opened this issue May 19, 2023 · 1 comment
Closed
Tracked by #356
Assignees
Labels
improvement Upgrades to an already existing feature

Comments

@cmoussa1
Copy link
Member

Broken off from a comment in #353, the data fetched by job-archive-interface.py could probably use some cleanup. There are some attributes it's currently fetching from flux-core's job-archive DB that it probably doesn't need anymore (e.g job-list returns nnodes now). I should look to improve what data is gathered both from job-list and job-info so that the table that stores the job records in the flux-accounting DB is

  1. as organized as possible, and
  2. specific to the needs of flux-accounting
@cmoussa1 cmoussa1 added the improvement Upgrades to an already existing feature label May 19, 2023
@cmoussa1 cmoussa1 self-assigned this May 19, 2023
@cmoussa1
Copy link
Member Author

#357 now adds a specific jobs table to the flux-accounting database with the data it requires for job usage calculations, so I think I can safely close this. Will re-open more specific issues if we find that we need other kinds of data not already captured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Upgrades to an already existing feature
Projects
None yet
Development

No branches or pull requests

1 participant