Draft
Conversation
ciyer
force-pushed
the
ciyer/runai-support
branch
2 times, most recently
from
cabf947 to
7f4a622
Compare
Contributor
|
You can access the deployment of this PR at https://renku-ci-ui-4053.dev.renku.ch |
ciyer
force-pushed
the
ciyer/runai-support
branch
4 times, most recently
from
f5c4430 to
9907451
Compare
leafty
reviewed
Mar 4, 2026
Member
leafty
left a comment
leafty
left a comment
There was a problem hiding this comment.
Notes:
- please add a description
- I would like to review and merge the backend pieces first
leafty
reviewed
Mar 5, 2026
| public/config.json | ||
| # Do not format generated files | ||
| *generated-api.ts | ||
| .react-router/types |
Member
There was a problem hiding this comment.
We need to keep formatting the generated files: they are checked into git and the formatting makes them easier to read.
Suggested change
| .react-router/types | |
| public/config.json | |
| .react-router/types |
Contributor
Author
Sorry, this should still be a draft PR. |
ciyer
force-pushed
the
ciyer/runai-support
branch
from
9907451 to
7685736
Compare
leafty
reviewed
Mar 6, 2026
Member
leafty
left a comment
leafty
left a comment
There was a problem hiding this comment.
The updated admin UI is buggy: I could not create a local resource pool, the button "+ add resource pool" would not do anything.
Will check the code later.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Changes to the admin console to allow setting up Run:AI as a remote backend.
Limitations
The Run:AI remote backend is currently just a proof-of-concept. It works, but with limitations. Launching a session from the Renkulab UI will start a Run:AI workspace, but it will not be displayed in the Renkulab UI, because the tunneling/port-forwarding does not work. Also, the git repositories are not cloned into the Run:AI workspace.
Testing
Set up a resource pool for Run:AI, targeting the SDSC Run:AI cluster, for example (though this should work with any Run:AI cluster).
Create an "Access Key" for your user in the user settings. The information to configure the remote session needs to be passed in Environment Variables. Create a session launcher, set one of the Runai resources classes as the default. Then set the following environment variables:
/deploy amalthea-sessions=ciyer/runai-support renku-data-services=ciyer/amalthea-runai