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.

Sign up for GitHub

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

Jump to bottom

Custom resource constraints: RAM is passed as int in MB #5056

Open
1 task done
mrnicegyu11 opened this issue Nov 21, 2023 · 0 comments
Open
1 task done

Custom resource constraints: RAM is passed as int in MB #5056

mrnicegyu11 opened this issue Nov 21, 2023 · 0 comments
Assignees
@GitHK @pcrespov
Labels
t:maintenance Some planned maintenance work

Comments

@mrnicegyu11
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Planned changes

Requesting an integer amount of memory (RAM) in the oSparc frontend for dynamic services leads to some floating point number of RAM requested in the docker resource limits by the dynamic sidecar. Since I am not sure how much the swarm likes fractional floating point numbers, we should always request integer amounts of RAM here.

Discovered with @matusdrobuliak66

image

The portainer screenshots corresponds to asking for 110Gb of RAM in the frontend for a dynamic service

This is a sub issue from ITISFoundation/osparc-issues#675
@mrnicegyu11 mrnicegyu11 added the t:maintenance Some planned maintenance work label Nov 21, 2023
@pcrespov pcrespov added this to the Kobayashi Maru milestone Nov 24, 2023
@sanderegg sanderegg removed this from the Kobayashi Maru milestone Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GitHK GitHK

@pcrespov pcrespov

Labels
t:maintenance Some planned maintenance work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@GitHK @mrnicegyu11 @pcrespov @sanderegg