Need copy / paste-able scripted deployment config docs for various types of deployments
acknowledged
C
Charcoal Mandrill
When using
tw-cli
, seqerakit
, or the Seqera Terraform Provider for deploying Compute Environments, there are many settings and most all of them independently toggle-able.If you want services like Wave and Fusion to work it's critical that you use the correct combinations of settings with the correct combinations of values for those settings. This can lead to validated CEs in small-batch testing, only to find with larger scale testing (when the users start running pipelines) that something is incorrectly configured.
Seqera should host some
clear, repeatable, and re-usable examples
of full configurations for various use cases. Similar to how we have the Nextflow Patterns webpage that documents various end-to-end scripted methods for Nextflow, I feel that we really need something analogous for the Seqera Platform scripted deployments, because it's too easy to miss settings that you did not realize were required for your CE to work.I think some of the following would be good examples to start with, described in both
tw-cli
, seqerakit
, and the Seqera Terraform Provider:- deploying a Compute Environment with EBS AutoScale
- the above but with Wave included
- the above but with Wave + Fusion included
- launching a test pipeline on the CE just created above
- doing all of the above with both TowerForge created CE's and with Manually Added CE's
I think some examples like this are already in the
seqerakit
GitHub repo, not sure if there are equivalents already available for tw-cli
. Ultimately it will be needed for the Terraform Provider as well, and they will all benefit from being available in one place so that users can see everything at once.Rob Newman
Merged in a post:
Improved Documentation on Instance Types and Configurations
C
Canny AI
I need better documentation or guidance on selecting optimal CE instance types and configurations for specific pipeline runs (eg. RNAseq). The current documentation does not provide enough clarity.
Rob Newman
Charcoal Mandrill Can I take the liberty of paring this FR down to the core feature request regarding clear and repeatable use cases (including "golden paths")?
C
Charcoal Mandrill
Rob Newman yes for sure thanks
Rob Newman
Charcoal Mandrill: Done. Please let me know if I've been too aggressive in trimming.
Rob Newman
acknowledged