Switch Google Cloud SDK from DockerHub to GCR BA-4640#5200
Conversation
kshakir
force-pushed
the
ks_gcloud_gcr
branch
from
f6c596d to
08639ef
Compare
| The Docker image for the Google Cloud SDK was previously only [published on Docker | ||
| Hub](https://hub.docker.com/r/google/cloud-sdk). Now that the image is [publicly hosted in | ||
| GCR](http://gcr.io/google.com/cloudsdktool/cloud-sdk), Papi V2 jobs will localize inputs and delocalize outputs using | ||
| the GCR image. |
There was a problem hiding this comment.
What is the benefit of using the image from GCR v/s Dockerhub?
There was a problem hiding this comment.
This is a continuation of the Papi networking (VPC / NAT / private IP) work. Not using Docker Hub means Cromwell doesn't need any resources outside of Google Cloud, so now a workflow can use things like private IP address and still localize files. Using private IPs allows one to run more machines, as it won't trip over a public ip address quotas-- or even limits in availability. NOTE: NAT was a workaround for keeping public ip address numbers down too, but I don't know the status of Cromwell/Workbench implementing that feature.
I don't know if this 100% fixes networking features for Papi V2 in Cromwell/Workbench, but it's a huge step.
kshakir
force-pushed
the
ks_gcloud_gcr
branch
from
08639ef to
8b2d901
Compare
3 participants
No description provided.