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

Example to run on Google compute engine #26

Open
chrislusf opened this issue Feb 1, 2016 · 2 comments
Open

Example to run on Google compute engine #26

chrislusf opened this issue Feb 1, 2016 · 2 comments

Comments

@chrislusf
Copy link
Owner

Glow should be very suitable to run on the cloud. It'll be nice to see that we can run a simple driver program and invoke the google compute engine.

Some benefits I can see:

  1. the ingress data transportation is free.
  2. GCE's cost is per second. Glow is very fast to start and stop.

Suggestions:

  1. Starting a globally accessible glow master may make it easier.
  2. Glow just need local SSD.
@justicezyx
Copy link
Collaborator

Found this blog post about running glow on Kubernetes (not integrating):
https://medium.com/@cedriclam/how-to-use-glow-with-kubernetes-22820d8f6270#.gstrirbcf

It might be straightforward to replicate the steps on GKE, which is a managed Kubernetes service.

@chrislusf
Copy link
Owner Author

I am not really familiar with Kurbernetes. But I want to have some script or even Go code to do this:

  1. start a glow master and multiple glow agents on kurbernetes. (May need to provide some Kurbernetes credentials here. May need to return a cluster id.)
  2. start a glow flow on the master and agents. (Maybe this would also need to credential file and the cluster id)
  3. wait for the glow flow to finish
  4. shutdown the master and agents.

The details should be encapsulated inside the script or go code. I prefer that a common user do not even need to know the details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants