Skip to content
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 seqr non-preemptible pools #243

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add seqr non-preemptible pools #243

wants to merge 2 commits into from

Conversation

vladsavelyev
Copy link

@vladsavelyev vladsavelyev commented Nov 11, 2022

Not sure if that would work, but just a guess.

Seems like it's a bit verbose to add a pool, but I guess we aren't going to add many new pools. Hail upstream seem to be satisfied with this solution as well

By the way, how the large-cohort pools were added? Do you have sql commands for that locally? Did you mean to add add-seqr-pools.sql just as an example, and we shouldn't add more sql files into batch/sql? We probably still should store sqls somewhere for repdocubility

@vladsavelyev vladsavelyev requested a review from lgruen November 11, 2022 05:25
batch/sql/add-seqr-nonpreemptible-pools.sql Outdated Show resolved Hide resolved
@@ -0,0 +1,44 @@
-- Adds dedicated pools for the seqr loading pipeline, with the 'seqr' pool label, but non-preemptible versions
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could potentially add these changes simply to add-seqr-pools.sql, as we haven't integrated that with CI anyhow.

I.e. regarding your question of reproducibility: ideally we'd add all our "CPG"-custom pools in here (including the large-cohorts one, so we should probably rename this to add-cpg-pools.sql or similar) and add another build step in build.yaml, so these pools also get created for dev deployments, for example. I was hoping to do that once the upstream merge had been done, but that ended up taking way longer (in fact has just been recently merged!).

@violetbrina violetbrina requested a review from lgruen January 19, 2023 01:26
Copy link

@lgruen lgruen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@violetbrina Would you like to take a stab at the integration outlined in #243 (comment)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants