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

[aws][autoscaler] fix regional default AMI's #22506

Merged
merged 9 commits into from
Feb 28, 2022

Conversation

ckw017
Copy link
Member

@ckw017 ckw017 commented Feb 18, 2022

Why are these changes needed?

The AMI's for ray.head.default and ray.worker.default in defaults.yaml supersede the default AMI for the region (defaults get merged in before _check_ami is called, causes problems if region isn't us-west-2). Removes the default AMI from defaults.yaml, and aborts if user doesn't specify an AMI in a region without a default.

Related issue number

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@ckw017 ckw017 changed the title [aws] fix regional default AMI's [aws][autoscaler] fix regional default AMI's Feb 19, 2022
ami_src_info[key] = "dlami"
if not default_ami:
cli_logger.abort(
f"Node type `{key}` does not have an ImageId and no default "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To slightly reduce cognitive load, let's express in this message that ImageId is a subfield of nodeConfig.

@DmitriGekhtman
Copy link
Contributor

Thanks, @ckw017!
Besides error message nit, lgtm.

@DmitriGekhtman DmitriGekhtman added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Feb 25, 2022
@DmitriGekhtman
Copy link
Contributor

lmk when it's ready to merge

@ckw017 ckw017 added tests-ok The tagger certifies test failures are unrelated and assumes personal liability. and removed @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. labels Feb 28, 2022
@ckw017
Copy link
Member Author

ckw017 commented Feb 28, 2022

@DmitriGekhtman good to merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants