Skip to content

Conversation

@nchammas
Copy link
Contributor

Both of these options are useful when spark-ec2 is being used as part of an automated pipeline and the engineers want to minimize the need to pass around AWS keys for access to things like S3 (keys are replaced by the IAM role) and to be able to launch a cluster that can terminate itself cleanly.

@SparkQA
Copy link

SparkQA commented Jun 23, 2015

Test build #35600 has finished for PR 6962 at commit efba9ee.

  • This patch fails Python style tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@nchammas
Copy link
Contributor Author

cc @JoshRosen

@SparkQA
Copy link

SparkQA commented Jun 23, 2015

Test build #35601 has finished for PR 6962 at commit fcf252e.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Merged build finished. Test FAILed.

Copy link
Contributor

Choose a reason for hiding this comment

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

Just curious -- is boto happy if we pass in None here ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

None should be fine, but I'll double check that and empty string tomorrow.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yup, both None (i.e. leaving out the option) and empty string work fine.

@shivaram
Copy link
Contributor

Thanks for checking. LGTM

@asfgit asfgit closed this in 31f48e5 Jun 24, 2015
@nchammas nchammas deleted the additional-ec2-options branch June 24, 2015 19:27
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.

4 participants