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

Show master address and login command after launch #195

Merged
merged 1 commit into from
Apr 5, 2017
Merged

Conversation

nchammas
Copy link
Owner

@nchammas nchammas commented Apr 4, 2017

This is a belated response to a suggestion (I believe originally by @engrean) to show the master address immediately after launch to make it easy for people to find the Spark UI without having to run a separate describe. I originally resisted but now I think it would be useful.

I also added a brief note showing how to login to the cluster after seeing several people manually look up the master address and login using plain SSH. Did anyone else do this when they first started using Flintrock?

New output:

$ flintrock launch nick --no-install-spark
Launching 2 instances...
[54.89.148.191] SSH online.
[54.89.148.191] Configuring ephemeral storage...
[54.89.148.191] Installing Java 1.8...
[52.23.251.87] SSH online.
[52.23.251.87] Configuring ephemeral storage...
[52.23.251.87] Installing Java 1.8...
launch finished in 0:02:49.
Cluster master: ec2-52-23-251-87.compute-1.amazonaws.com
Login with: flintrock login nick

It's not the cleanest output honestly, but it's practical and will do fine until we get around to #27.

@BenFradet
Copy link
Contributor

@nchammas I used plain SSH and wasn't aware of a login command 👍

@nchammas
Copy link
Owner Author

nchammas commented Apr 5, 2017

@BenFradet - Oh, interesting!

How did you look up the master address in order to SSH? Did you use describe, or the AWS web console, or something else?

@BenFradet
Copy link
Contributor

Both alternatively depending on whether I had the console open.

The worst part is I've seen much of the codebase before, I guess I just skipped right through that one :(

@nchammas
Copy link
Owner Author

nchammas commented Apr 5, 2017

😆 There are probably many other people doing the same!

Alright, hopefully with this little change we can eliminate that problem. 👍

@nchammas nchammas merged commit 33a392b into master Apr 5, 2017
@nchammas nchammas deleted the launch-info branch April 5, 2017 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants