Skip to content
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

[Feature Request]: Set RemoteRuntime size in frontend #5797

Open
xingyaoww opened this issue Dec 25, 2024 · 2 comments · May be fixed by #5805
Open

[Feature Request]: Set RemoteRuntime size in frontend #5797

xingyaoww opened this issue Dec 25, 2024 · 2 comments · May be fixed by #5805
Assignees
Labels
enhancement New feature or request fix-me Attempt to fix this issue with OpenHands

Comments

@xingyaoww
Copy link
Collaborator

What problem or use case are you trying to solve?

We support setting the size of RemoteRuntime instance in RemoteRuntime, but we didn't support configuring them in the frontend.

remote_runtime_resource_factor: int = 1

Describe the UX of the solution you'd like

When app_mode is AppMode.SASS, we should add entry in the frontend setting modal: "Runtime Settings".

And under it, we should have a drop-down menu that allows people to select 1x (2 core, 8G) or 2x (4 core, 16G).

Do you have thoughts on the technical implementation?

Once the instance size is selected, we should update the sandbox_config.remote_runtime_resource_factor to corresponding value (1 for 1x, 2 for 2x).

Relavant files to read (Setting implementation in the backend side).

  • openhands/server/config/openhands_config.py
  • openhands/server/routes/settings.py

You should first understand how the config is passing from frontend to backend before start implementing this.

Describe alternatives you've considered

Additional context

@xingyaoww xingyaoww added enhancement New feature or request fix-me Attempt to fix this issue with OpenHands labels Dec 25, 2024
@openhands-agent
Copy link
Contributor

OpenHands started fixing the issue! You can monitor the progress here.

@openhands-agent
Copy link
Contributor

An attempt was made to automatically fix this issue, but it was unsuccessful. A branch named 'openhands-fix-issue-5797' has been created with the attempted changes. You can view the branch here. Manual intervention may be required.

@neubig neubig linked a pull request Dec 26, 2024 that will close this issue
@neubig neubig self-assigned this Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fix-me Attempt to fix this issue with OpenHands
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants