Evaluate/PoC the possibility to implement support for both cli (“legacy”) and slurmrestd data fetching.
Originally, the logic behind going cli-way was that all slurm users have access to the slurm commands, but not all sites provide slurmrestd endpoint. So to make SC available to everyone, CLI-way was chosen.
Now, for sites providing users with slurmrestd endpoint, might be:
- more elegant to gather data from there, see client generated code
- give us the ability to do caching with a 3rd party caching proxy, instead of something like (abandoned) sccache daemon)
Rough idea about what might be needed:
- additional configuration stanza with rest_endpoint, jwt parameters
- method of refreshing jwt periodically
- create datafetcher interface that legacy cli functions and new rest functions satisfy (refactor legacy code accordingly)
- rest client code
- make it all work together…somehow :D
In terms of expected delivery, i've started with some early preparation work for this topic, but it's still far away from anything resembling a PoC.
Considering my time availability, i'd suppose this would be a medium term goal for SC.
In case anyone is willing to contribute time to working on this, i'd be more then happy to assist. If not, it's a SC 2.0.0 goal 😄
Evaluate/PoC the possibility to implement support for both cli (“legacy”) and slurmrestd data fetching.
Originally, the logic behind going cli-way was that all slurm users have access to the slurm commands, but not all sites provide slurmrestd endpoint. So to make SC available to everyone, CLI-way was chosen.
Now, for sites providing users with slurmrestd endpoint, might be:
Rough idea about what might be needed:
In terms of expected delivery, i've started with some early preparation work for this topic, but it's still far away from anything resembling a PoC.
Considering my time availability, i'd suppose this would be a medium term goal for SC.
In case anyone is willing to contribute time to working on this, i'd be more then happy to assist. If not, it's a SC 2.0.0 goal 😄