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

Please use us-central1 in examples instead of other us-* regions and zones #153

Open
mbookman opened this issue Oct 26, 2021 · 0 comments
Open

Comments

@mbookman
Copy link
Contributor

The terra-cli README includes examples for both us-east1 and us-central1.

It would be good for us to make an effort to standardize on us-central1.
Many projects that already exist in the life sciences in the US have either used US multi-regional buckets or us-central1 (in order to reduce storage costs.

Terra Community Workbench (app.terra.bio) has always defaulted to running VMs in us-central1 (workflows or notebook VMs).

The problem with arbitrarily using regions around the US is that if project A stores data in us-central1 and project B stores data in us-east1, then any cross-analysis of these two datasets is going to end up unnecessarily incurring GCP network egress charges as data needs to leave one region or the other.

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

No branches or pull requests

1 participant