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

Fix 29GB RAM profile option not starting in openscapes #3791

Merged
merged 1 commit into from
Mar 12, 2024
Merged

Fix 29GB RAM profile option not starting in openscapes #3791

merged 1 commit into from
Mar 12, 2024
+10 −10

Commits on Mar 12, 2024

  1. Fix 29GB RAM profile option not starting in openscapes 

    Looks like the overhead of resources in AWS nodes has changed
since we last set these, causing the largest pod on r5.xlarge
to not fit anymore. We should eventually dynamically generate these
- but in the meantime, I've just regenerated these numbers using
our existing deployer command so mem_29_7 starts again.
    @yuvipanda
    yuvipanda committed Mar 12, 2024
    Configuration menu
    Copy the full SHA
    3b2216b View commit details
    Browse the repository at this point in the history