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

[EGGO-44] Use Cloudera Director for cluster provisioning. #45

Merged
merged 1 commit into from
Apr 29, 2015

Conversation

tomwhite
Copy link
Member

This change makes it possible to start and stop a cluster using Cloudera
Director. However, it is not tied in to Eggo operations yet.

This change makes it possible to start and stop a cluster using Cloudera
Director. However, it is not tied in to Eggo operations yet.
# A prefix that Cloudera Director should use when naming the instances (this is not part of the hostname)
#

instanceNamePrefix: cloudera-director
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: change to eggo-director?

Copy link
Member Author

Choose a reason for hiding this comment

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

I was trying to leave this eggo-agnostic, so we can move it out or use it separately.

@laserson
Copy link
Contributor

This is awesome, @tomwhite! Should we merge it in so easier to iterate?

tomwhite added a commit that referenced this pull request Apr 29, 2015
[EGGO-44] Use Cloudera Director for cluster provisioning.
@tomwhite tomwhite merged commit 1055959 into bigdatagenomics:master Apr 29, 2015
@tomwhite tomwhite deleted the EGGO-44-cloudera-director branch April 29, 2015 11:10
@tomwhite
Copy link
Member Author

I merged and opened #48 as a follow on.

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