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

Add GCE as a supported provider #10

Closed
nchammas opened this issue Oct 5, 2015 · 2 comments
Closed

Add GCE as a supported provider #10

nchammas opened this issue Oct 5, 2015 · 2 comments

Comments

@nchammas
Copy link
Owner

nchammas commented Oct 5, 2015

Flintrock was designed from the start to make it possible to support multiple cloud providers within one tool.

Google's Compute Engine (GCE) is most likely the next cloud provider that Flintrock will support.

It will take quite a bit of work to do this, and in the process Flintrock will be forced to refine its internals which will make it more maintainable in the long run. This is a good thing.

Work on this should probably start only after #6 and #8 have been resolved, so that there is a slightly better definition of the APIs and structure that the GCE provider can follow. #11 is another blocker for this issue.

@nchammas
Copy link
Owner Author

For those who may be watching this issue and waiting for GCE support, I recommend checking out @broxtronix's project, spark-gce.

@nchammas
Copy link
Owner Author

I'm going to close this for now since, realistically speaking, this is not going to happen without a motivated contributor 1) stepping up to add this and 2) committing to maintain it over the long run (which would entail becoming a Flintrock committer). That contributor is likely not going to be me. We can reopen this issue if such a contributor steps up.

I am still committed to maintaining an appropriate separation of concerns within Flintrock such that, if support for another provider like GCE is to be added, it can be done without too much surgery. Modules like core.py and services.py will continue to be completely provider-agnostic to make that possible.

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

No branches or pull requests

1 participant