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

[Autoscaler] Use NetworkInterfaces parameter to launch instances. #16816

Conversation

xcharleslin
Copy link
Contributor

@xcharleslin xcharleslin commented Jul 1, 2021

Why are these changes needed?

This PR allows launching in subnets where public IP assignments are enabled but off by default.

It does this by:

  • Specifying NetworkInterfaces.AssociatePublicIpAddress = True
  • Moving SubnetId, SecurityGroupIds into NetworkInterfaces (required by boto when using NetworkInterfaces)

Related issue number

Partial resolution to #16815.

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 :(

Copy link
Contributor

@DmitriGekhtman DmitriGekhtman left a comment

Choose a reason for hiding this comment

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

There's also a lint error -- In case you haven't used it before, Ray lint check/format can be done locally with ray/scripts/ci.sh
You can also install pre-push lint hooks with ray/setup_hooks.sh.

Also, it would be good to do a spot-check that you can launch a ray cluster with ray up with these changes.

Thanks for making this fix!

@DmitriGekhtman
Copy link
Contributor

should check with ray up aws/example-full.yaml before merge

@wuisawesome
Copy link
Contributor

Can one of you confirm it works, then add the tests-ok label (or ping me) and I will merge?

@DmitriGekhtman
Copy link
Contributor

Can one of you confirm it works, then add the tests-ok label (or ping me) and I will merge?

I'll go ahead and do that

@DmitriGekhtman DmitriGekhtman added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label Jul 2, 2021
@DmitriGekhtman
Copy link
Contributor

It works. @wuisawesome ready 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.

None yet

3 participants