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
Add support for selecting minimum CPU platform on GCP #1633
Conversation
Thanks for submitting this PR. I was thinking this would make more sense at process (job) level instead of pipeline wide. What do you think? |
I thought about that. There is currently no additional cost for specifying Skylake, Cascade lake is only available in the N2 instances so they would need to specify a different machineType all together. The setting specifies the minimum CPU Platform, and when not specified you are still likely to end up on Skylake. It was mainly easier for me to do it on the profile level rather than on process level, and the benefit of adding it to process level was not worth it. I'll check with Andrew to get his opinion |
I had a quick sanity check with our team, and I think pipeline level config should be sufficient. |
Ok, that's reasonable. If so it's needed to add the reading of that value from the nextflow config file. See for example here: Lines 109 to 117 in bc9db8d
Also, uni tests should be added to corresponding changes. It would be nice also to add an entry in the docs for google LS Lines 109 to 117 in bc9db8d
Tx! |
Thanks, I've added it to the documentation as an example as it will be the most common option for most users. I'll look at how to add unit test as well, but can sure use some help on that. |
Thanks for this changes. For the tests,it could be enough t o verify the Lines 231 to 242 in bc9db8d
and then it's included in the request, look for example here Lines 162 to 182 in a481b42
and Lines 133 to 206 in a481b42
Also, please, make sure so sign-off the commit to fulfill the DCO bot requirement. Thanks! |
Adding cpuPlatform parameter to the request Signed-off-by: hnawar <hnawar@google.com>
Add support for CPU Platform selection Signed-off-by: hnawar <hnawar@google.com>
Add support for CPU platform Signed-off-by: hnawar <hnawar@google.com>
Adding support for CPU Platform selection Signed-off-by: hnawar <hnawar@google.com>
Signed-off-by: hnawar <hnawar@google.com>
Add the google.lifeSciences.cpuPlatform to the documentation Signed-off-by: hnawar <hnawar@google.com>
Add quotes to the example of google.lifeSciences.cpuPlatform Signed-off-by: hnawar <hnawar@google.com>
Add link to min CPU platform documentation Signed-off-by: hnawar <hnawar@google.com>
Add unit test for cpuPlatform in config Signed-off-by: hnawar <hnawar@google.com>
Signed-off-by: hnawar <hnawar@google.com>
Signed-off-by: hnawar <hnawar@google.com>
Fix Accidental deletion Signed-off-by: hnawar <hnawar@google.com>
Signed-off-by: hnawar <hnawar@google.com>
I have added the unit tests, signed the commits with DCO and Travis build passed. |
I have also staged changes to add support for specifying disk type per process. I can push these changes as well and put all in one PR if this is more convenient or submit a separate pull request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for this contribution. Merging it.
As for specifying disk type per process, free free to draft a separate PR for it. However, I would like to keep a portable model for this, i.e. able to support also other computing services. |
Any suggestion to retrieve the list of avail cpu platforms for a given zone using the Java API? Can't find an immediate way using the |
This PR adds support to specify the minimum CPU platform used by a run when using the Google Cloud Life Sciences executor