-
Notifications
You must be signed in to change notification settings - Fork 34
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
chore: 0.31.0 release with crc service #3067
Conversation
7e8e604
to
b223f5f
Compare
You can access the deployment of this PR at https://ci-renku-3067.dev.renku.ch |
b1e24b0
to
e00a120
Compare
e00a120
to
856633a
Compare
92e4392
to
66dd4e7
Compare
85126e1
to
270fa91
Compare
270fa91
to
8cd0c37
Compare
8c769f9
to
2c05de6
Compare
Detailed explanation of CRC services.
Improved description of this release.
Improved description of 0.31.0. Co-authored-by: Rok Roškar <roskarr@ethz.ch>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I manually tested some scenarios and this works well. Very nice job! 🚀
Renku ``0.31.0`` introduces the compute resource control (CRC) service, enabling Renku administrators to manage access to | ||
specific computing resources. The service exposes an HTTP API for the administrators to interact with. In this way, | ||
Renku administrators can create, update or delete resource pools, and can add to or remove users from resource pools. | ||
Please note that a user interface for the CRC has not been added yet but it will be added in a future release. Currently, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we keep this level of detail for administrators here? It may be too long/irrelevant for regular Renku users. As for the details for the launching of sessions (next paragraph), I think it is good to provide this information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that administrators especially the ones deploying or updating to a new version of Renku are most likely to read the changelog in the repo or the docs. At least from my experience helping admins deploy Renku I have heard complaints specifically because the release notes excluded information or were too brief. Currently we have no other place to include this information as far as I know. So I think we should definitely include this here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively we can make another changelog of section of the docs for this information specifically tailored for admins. But I am not sure it is worth the effort and it will only scatter information that I think belongs together.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good for me!
/deploy #persist #cypress
depends on: