-
Notifications
You must be signed in to change notification settings - Fork 45
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
Support for specifying VM Image for Cloud Batch backend #300
Comments
Hi @JackAtScaleSec ! Thanks for writing in. So for the Google Cloud Batch API, dsub does support the Is that sufficient for your needs or is there more to the issue? |
Thanks for getting back to me @wnojopra - there's more to the issue. Beyond specifying a custom container image, which is a necessity for my use case, we also need to specify a custom OS image for the GCE instance the container is ran on, due to security and compliance requirements. This will allow us to ensure the underlying GCE instance is using a custom OS image that has had security hardening applied, agents installed, etc. as needed. |
Thanks for the clarity @JackAtScaleSec . I believe I understand your use case, but I'm not sure if the Cloud Batch API supports this. In your original comment, you mention
Am I missing this somewhere? I'm primarily looking at the Batch Job spec. There's an |
@wnojopra I believe it will support this. With the batch API, you can specify an instance policy (specific items like machine type and boot disk) or an instance template itself, which would also include the boot disk to use for the GCE instances. See https://cloud.google.com/python/docs/reference/batch/latest/google.cloud.batch_v1alpha.types.AllocationPolicy.InstancePolicy > boot_disk Also, here's Google's docs page covering the capability to specify a custom OS image via this mechanism: https://cloud.google.com/batch/docs/specify-vm-os-image#api. Code snippet:
Thanks, |
Certain organizations utilizing dsub may require the ability to specify a custom VM image for compliance, regulatory, or internal requirements. The underlying Cloud Batch API supports specifying an image when creating a job.
I'm requesting adding support for specifying a custom VM image when creating a dsub job using the Google Cloud Batch backend.
FYI - I requested access to the Contributor License Agreement as referenced in CONTRIBUTING.md but still haven't been granted access to the file.
The text was updated successfully, but these errors were encountered: