wustl-oncology cloud-workflows issues

wustl-oncology / cloud-workflows

Infrastructure and tooling required to get genomic workflows running in the cloud

1 stars 7 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Added estimate billing script for GCP batch runs

#41 ldhtnp opened 3 weeks ago
0
Investigate use of Google Batch instead of Life Sciences API as a Cromwell backend

#40 malachig opened 1 month ago
17
added ability to specify what version of cloud-workflows to pull

#39 evelyn-schmidt closed 9 months ago
1
Test latest version of Cromwell

#38 malachig opened 9 months ago
0
Use a release of analysis WDLs instead of pulling main

#37 malachig closed 9 months ago
4
adding gcp getting started

#36 chrisamiller closed 1 year ago
0
updating readme

#35 chrisamiller closed 1 year ago
0
Log info for missing values instead of showing errors.

#34 tmooney closed 1 month ago
2
Customizing memory and cpu specifications for VMs

#33 Layth17 opened 1 year ago
2
Customizing VM's CPU/RAM instead of setting --machine-type

#32 Layth17 opened 1 year ago
0
Handle backendStatus "Success" with executionStatus "RetryableFailure"

#31 tmooney closed 1 year ago
1
Analysis of Monitoring Scripts

#30 Layth17 opened 1 year ago
0
PAP Flag

#29 Layth17 closed 1 year ago
0
Adding Monitoring Script Option

#28 Layth17 opened 2 years ago
0
During project initialization apply public access prevention flag to bucket

#27 malachig closed 1 year ago
1
Adding cost script to create a costs summary

#26 ksinghal28 opened 2 years ago
0
Set up resource monitoring for tasks of cromwell runs

#25 malachig opened 2 years ago
5
Fixing Issues #23, #20, and #21

#24 Layth17 closed 2 years ago
2
Cromwell config file is not within a writable dir

#23 Layth17 closed 2 years ago
1
Solution for Issue #16 -- customizing CIDR and GC_REGION

#22 Layth17 closed 2 years ago
0
cloudize-workflow.py should fail if it encounters an invalid file path or access issue

#21 malachig closed 2 years ago
0
Add retention policy to resource creation step for manual workflows

#20 malachig closed 2 years ago
1
Add costs of cromwell head node to cost reporting scripts

#19 chrisamiller opened 2 years ago
0
fix issue with infite loop when parsing workflows

#18 malachig closed 2 years ago
0
use max of time or 1m for billing, not minimum

#17 chrisamiller closed 2 years ago
1
Add option so user can configure IP addresses during project initiation stage

#16 malachig closed 2 years ago
1
Prototype GCP Identity Aware Proxy to secure central-server endpoints

#15 johnmaruska opened 2 years ago
0
Prototype reference disks for reference directories like VEP cache

#14 johnmaruska opened 2 years ago
0
Add billing estimation scripts

#13 johnmaruska closed 2 years ago
0
Add workflow prefix to WDL inputs before processing

#12 johnmaruska closed 2 years ago
0
Grab bag

#11 johnmaruska closed 2 years ago
0
Revert "Grab-bag improvements"

#10 johnmaruska closed 2 years ago
0
Grab-bag improvements

#9 johnmaruska closed 2 years ago
0
Rewrite README.md for new usage patterns

#8 johnmaruska closed 3 years ago
0
Set firewall to behind WashU VPN

#7 johnmaruska closed 3 years ago
0
Add infra.sh commands for deploys for jinja and docker

#6 johnmaruska closed 3 years ago
0
Extend cloudize-workflow to work with WDL workflows

#5 johnmaruska closed 3 years ago
0
Checking

#4 johnmaruska closed 3 years ago
0
cloudize-workflow.py - Script should start from last-upload if it fails and re-runs

#3 johnmaruska opened 3 years ago
0
cloudize-workflow.py - Handle Directory input types

#2 johnmaruska closed 2 years ago
1
Add python script to automate the local to GCS process, upload and file modification

#1 johnmaruska closed 3 years ago
0