Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSpecify Google Cloud Compute Engine disk type #1444
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I would definitely support this. The key logic of nextflow is a little challenged on the cloud: unless one has a shared disk which can be mounted by all tasks VMs, each task will copy back and forth files to/from the bucket instead of using sym links as on-prem. |
New feature
Ability to specify the Compute Engine disk type (pd-standard or local-SSD) found in the new Cloud Life Sciences API (https://cloud.google.com/life-sciences/docs/reference/rpc/google.cloud.lifesciences.v2beta#disk).
Usage scenario
Job's that require a high input/output operations per second and lower latency (https://cloud.google.com/compute/docs/disks/local-ssd).
Suggest implementation
The API documentation states it can be set using
setType()(https://developers.google.com/resources/api-libraries/documentation/genomics/v1alpha2/java/latest/com/google/api/services/genomics/model/Disk.html#setType-java.lang.String-)Add disk type during formation of VM in GoogleLifeSciencesHelper.groovy
Where
req.diskTypeis specified in GoogleLifeSciencesTaskHandler.groovygetDiskType()can be set within TaskConfig.groovy, where it is set topd-standardby default.Preliminary tests showed it was successful to generate a Computer Engine instance with SSD attached.