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

Back-end sends new information for cluster load indicator #1666

Open
MartinBelthle opened this issue Jul 25, 2023 · 0 comments
Open

Back-end sends new information for cluster load indicator #1666

MartinBelthle opened this issue Jul 25, 2023 · 0 comments

Comments

@MartinBelthle
Copy link
Contributor

MartinBelthle commented Jul 25, 2023

Problem Statement

Currently the cluster load indicator is as such :

cluster_load

This indicator is retrieved by the front-end via the end-point GET v1/launcher/load which returns a dict :
{'slurm': float, 'local': float}

With this PR : #1664, the back-end will send more accurate information with another format : LauncherLoadDTO().
This class has 4 variables which are not optional:

  • allocated_cpu_rate: float,
  • cluster_load_rate: float,
  • nb_queued_jobs: int,
  • launcher_status: str

The desired outcome

The front-end will have to do 2 things:

  • Display the first 3 indicators (all except launcher_status) at the same place it used to be. You are free to choose the mockup you want.
  • If launcher_status != "SUCCESS": it means that the cluster load could not be retrieved. The first 3 indicators will be at 0. Probably just putting 0 is not enough to show that the info could not be retrieved but I do not have a precise idea on how to display it in the front.

Developer Notes

  • You can do your development on the PR linked above because it returns the new object LauncherLoadDTO().
    NB : Probably use the branch on this commit : d549e16 because after this the UTs do not pass anymore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants