Skip to content

feat(data-pipelines): Allow for starting Dataproc clusters using custom OS images #1577

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.

Sign up for GitHub

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

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

feat(data-pipelines): Allow for starting Dataproc clusters using custom OS images #1577

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b245b4b
Add helpers for starting custom Dataproc cluster
nadeaujoshua Jun 18, 2024
8b2b2eb
Add note on starting Dataproc with custom img
nadeaujoshua Jun 18, 2024
7757194
Remove poetry from data-pipeline src
nadeaujoshua Jun 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions data-pipeline/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,11 @@ The ClinVar pipelines must be run on clusters with an appropriate version of VEP
./deployctl dataproc-cluster start <cluster-name>
```

NOTE: Starting with `gnomad version 4.1`, it is highly recommended to specify a
custom OS image that was built for that gnomAD version. To see these images, run
`gcloud compute images list --filter="family=dataproc-custom-image"`. You can then
Copy link
Contributor

Choose a reason for hiding this comment

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

Running this tells me 0 images were found:

❯ gcloud compute images list --filter="family=dataproc-custom-image"
Listed 0 items.

My gcloud config's project is set to exac-gnomad, maybe that's the reason?

pass the desired image name to the above `start` command using the `--image` flag.

- Run a pipeline.

A list of all pipelines can be seen with `./deployctl data-pipeline run --help`.
Expand Down
Loading