Release of Slurm-web v3.2.0 #347
rezib
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Added
slurmrestd
REST API and return value in response ofstats
endpoint.ldap
>user_primary_group_attribute
parameter for the gateway.ldap
>group_object_classes
parameter for the gateway.cache
>version
parameter for the agent.slurmrestd
TCP/IP socket limitation in architecture page.[slurmrestd]
>version
agent setting is more intended for developers and should not be changed.Changed
slurmrestd
against hard-coded minimal version and log error if not greater or equal.Fixed
rfl.settings.errors.SettingsSiteLoaderError
when loading gateway and agent site configuration (rfl.settings.errors.SettingsSiteLoaderError when loading site configuration #317).slurmrestd
into JSON error agent that can be interpreted by frontend and emit clear error message in logs (JSONDecodeError on slurmrestd 404 #321).slurmrestd
not formatted in JSON, translated into JSON error for frontend and emit clear error message in logs (JSONDecodeError with slurmrestd due to accounting error #333).slurmrestd
responses and emit warning log instead of crashing (KeyError with unsupported Slurm version #316).user_name_attribute
configuration parameter (RFL's ldap.py not pulling user_name_attribute from gateway.ini #340).SLURMRESTD_SECURITY=disable_user_check
environment variable inslurmrestd
service drop-in configuration override (Analyze SLURMRESTD_SECURITY=disable_user_check requirement #320).sackd
) and clarify thatmunge
is not involved between Slurm-web agent andslurmrestd
.🙏 Special thanks @rseaman2016 @Talavig @attssystem @digdilem @parapar @c-vinet @satishdotpatel for their feedback and contributions!
This discussion was created from the release v3.2.0.
Beta Was this translation helpful? Give feedback.
All reactions