You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 23, 2020. It is now read-only.
We want a single user to be able to have multiple running pods of different config active at the same time. Multiple images, different amounts of RAM, GPUs, etc.
The issue is one of UX - how do we let users choose which profile? This is reasonably easy with an interactive session - you can just ask! However, since we want to support non-interactive use as well (for #8 and similar), we can't rely on having a working TTY. And for similar reasons, we shouldn't hijack how commands get interpreted either - most remoting tools expect that to not change either.
Possible options:
Use the 'username' part of the ssh command. We pick a character that we consider a separator, escape it otherwise, and use that to pass options. For example, you could ssh as 'yuvipanda+profile-1@host'. Need to see what the restrictions on usernames are in the SSH protocol, and if there are length limitations
Pass an environment variable. SSH lets the client pass a whitelisted set of environment variables through to the server. We could use this to pass profile info through
???
The text was updated successfully, but these errors were encountered:
We want a single user to be able to have multiple running pods of different config active at the same time. Multiple images, different amounts of RAM, GPUs, etc.
The issue is one of UX - how do we let users choose which profile? This is reasonably easy with an interactive session - you can just ask! However, since we want to support non-interactive use as well (for #8 and similar), we can't rely on having a working TTY. And for similar reasons, we shouldn't hijack how commands get interpreted either - most remoting tools expect that to not change either.
Possible options:
The text was updated successfully, but these errors were encountered: