-
Notifications
You must be signed in to change notification settings - Fork 12
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
Experiment with use of private VMs #70
Comments
Upon some testing,
@tmooney suggested that "maybe it’d work if we used the docker image cache feature too (or if we pointed only to http://gcr.io images)" |
It seems the GCP is transitioning from the "Container Registry" to the "Artifact Registry". I wonder if Cromwell already supports this. |
If we wanted to try using the docker image cache feature crudely this involves something like this:
Then set up cromwell to look for images in this location as described here: |
Currently all VMs seem to be using ephemeral external IPs. Google charges for these similar to what they would charge if you actually reserve an IP, even if its in use.
It also theoretically makes the instance less secure. It not clear that we actually need to be able to access worker instances externally. Perhaps, only the cromwell server needs to be accessed externally. If one did need to get onto an individual worker instance, that could still be done by using the Cromwell server itself as a jump point.
Here is some discussion of how to do this.
https://github.com/atgu/cromwell_google_setup#using-vms-with-private-ip-addresses
Essentially to do this you can add
noAddress: true
to the runtime block of a task. We could test this and see if it breaks anything.The text was updated successfully, but these errors were encountered: