-
Notifications
You must be signed in to change notification settings - Fork 51
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
[Console 2.0] Cloud-VM style deployments via Console #227
Comments
I will develope this. |
Hey @ygrishajev - when you are ready to work on this please reach out to @andy108369 to coordinate docker images and embedding the user SSH pub key (with sshd install) |
Added suggested design changes for now. We will do a full refresh of this page at a later point (with inputs from @aktdenis ) but this is for us to get the functionality in place, for now. |
hey @hiroyukikumazawa - thanks for the interest here. Sorry for missing your comment earlier. This one is on the core team's plate but happy to discuss other potential things you could contribute to (cc @baktun14 ) |
So I don't have access for this issue, right? |
@hiroyukikumazawa - correct, this is assigned to @ygrishajev for now. Are you set up to be able to build and run console locally? We should discuss this further - are you on our discord server? If so, what's your handle? |
Not fully, just run the frontend |
@hiroyukikumazawa - are you interested in working on the first sub task under this issue? |
I will do this |
Please check the pr #244 |
Specifically: - centos - debian - suse closes akash-network/console#227
as a part of this move ssh related state to the context refs #227
as a part of this: - control deeply nested state via context - configure e2e tests for console ui - cover sdl builder ssh flows with e2e refs #227
as a part of this: - control deeply nested state via context - configure e2e tests for console ui - cover sdl builder ssh flows with e2e refs #227
Overview and Problem Statement
One of the most commonly requested things from customers/ partners/ users is a similar experience to public clouds where a user is able to request a VM running on a specific (pre-set) hardware configuration, along with a plain OS image (typically linux) that they can just SSH into and work with (install any packages like git, python, pytorch, huggingface models etc). When they come to akash, they expect a similar experience.
Suggested Design
Clicking into it lets the user specify the following:
Add documentation to tell the user how to SSH into the container once it is running. Ideally we should show this in the lease details page
The text was updated successfully, but these errors were encountered: