linc: setup staging/prod hubs (and fixes for bican/dandi) #3901
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment was marked as resolved.
This comment was marked as resolved.
GeorgianaElena
approved these changes
Apr 3, 2024
There was a problem hiding this comment.
Thanks for fixing the allocation issue on the other mit hubs as well @consideRatio ❤️
LGTM 🚀
consideRatio
force-pushed
the
pr/bican-dandi-linc
branch
from
71b8b76 to
6875eea
Compare
|
Thanks for reviewing @GeorgianaElena! I force pushed to filter out the deployer stuff into a dedicated PR (#3903). |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/8540627494 |
|
The funding_url should be declared, and maybe there are more things, but i'll open a new PR for that and go for a merge. Thanks for reviewing @GeorgianaElena! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tested ability to startup the biggest resource allocation request, as we don't have any headroom its very sensitive to changes. I observed that EKS k8s 1.29 has eaten up a bit of headroom, so we were unable to start those instances. I've updated node info stuff so that future generation attempts won't fail in EKS and fixed the resource allocation stuff for bican/dandi/linc.
As soon as other hubs upgrade to k8s 1.29 (maybe 1.28), they will run into these kinds of issues again as memory/cpu headroom is reduced.
Remaining
funded_bynot filled in