What is the problem that this PR is trying to fix?
Worker will pass one more query param named "gpu_vm_type" to job-board which is needed for selection of image for GPU.
What approach did you choose and why?
I added the gpu_vm_type param in api_selector.go class where the rest of the params (like tags, is_default, repo etc) are passed to the POST /images/search request. Its only meant for GCE so the GpuVmType info is only passed from ace.go to api_selector.gce.
What is the problem that this PR is trying to fix?
Worker will pass one more query param named "gpu_vm_type" to job-board which is needed for selection of image for GPU.
What approach did you choose and why?
I added the gpu_vm_type param in api_selector.go class where the rest of the params (like tags, is_default, repo etc) are passed to the POST
/images/searchrequest. Its only meant for GCE so the GpuVmType info is only passed from ace.go to api_selector.gce.How can you test this?
deployed on staging
What feedback would you like, if any?
none