[autoscaler] Should use internal IP for ssh

[ericl]

What do these changes do?

As reported on the dev list, the external ip is not always accessible from the head node.

@richardliaw

[ericl]

Tested and this seems to work

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/5925/
Test PASSed.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/5928/
Test PASSed.

[richardliaw]

Test failures look unrelated.

[npyoung]

Just tried the latest build and it seems to work, thanks! I did notice that my EC2 instances no longer get named and the ray:etc tags don't get assigned. Not sure if that's specific to this build, something that changed since ray 0.3.1, or another issue entirely.

…

On Fri, Jun 8, 2018 at 1:09 AM Richard Liaw ***@***.***> wrote: Merged #2209 <#2209>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABSUn3m0WBnMx7LPNsiKEEK47F2n8qNtks5t6jEigaJpZM4UfUhM> .

[ericl]

Oh, the tag name change is due to a recent PR to support the GCP labeling scheme as well. I guess on unintentional side effect is it breaks AWS names. I'll see if that can be fixed.

…

On Fri, Jun 8, 2018, 10:31 AM NP Young ***@***.***> wrote: Just tried the latest build and it seems to work, thanks! I did notice that my EC2 instances no longer get named and the ray:etc tags don't get assigned. Not sure if that's specific to this build, something that changed since ray 0.3.1, or another issue entirely. On Fri, Jun 8, 2018 at 1:09 AM Richard Liaw ***@***.***> wrote: > Merged #2209 <#2209>. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#2209 (comment)>, or mute > the thread > < https://github.com/notifications/unsubscribe-auth/ABSUn3m0WBnMx7LPNsiKEEK47F2n8qNtks5t6jEigaJpZM4UfUhM > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA6SlnPJgLxf6QpOzUisiRneIAeSsNCks5t6rT9gaJpZM4UfUhM> .