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

Deploy more Zebra or zcashd instances on testnet #1222

Closed
Tracked by #745
teor2345 opened this issue Oct 28, 2020 · 4 comments · Fixed by #1844
Closed
Tracked by #745

Deploy more Zebra or zcashd instances on testnet #1222

teor2345 opened this issue Oct 28, 2020 · 4 comments · Fixed by #1844
Assignees
Labels
A-infrastructure Area: Infrastructure changes C-enhancement Category: This is an improvement
Milestone

Comments

@teor2345
Copy link
Collaborator

teor2345 commented Oct 28, 2020

Motivation

The Zebra sync tests currently run on mainnet and testnet. Sometimes the testnet nodes are slow or unreliable, so the sync tests are unreliable.

Solution

Deploy about 10 Zebra or zcashd instances on testnet, to increase the average speed and reduce the average latency of testnet.

Open Questions

Right now, we just need a few more Zebra or zcashd instances to stabilise the test network. We can deal with distribution, mining, and network speed later.

Should the zcashd instances be configured to mine blocks?

  • Maybe a few should mine on 1 core each

Where should they be located? How fast should they be?

  • Reasonably fast
  • Distributed across multiple DCs
  • In reasonably central internet locations, so Zebra developers have low latency for quick sync tests
  • Near our CI and CD runners?

Related Issues

Testnet sync fixes: Issue #1207 PR #1223
Tracking issue #745

@dconnolly
Copy link
Contributor

Maybe this work will scale out / let us deploy zebra nodes on testnet too

@mpguerra mpguerra modified the milestones: 2021 Sprint 2, 2021 Sprint 3 Jan 25, 2021
@teor2345 teor2345 modified the milestones: 2021 Sprint 3, 2021 Sprint 4 Feb 8, 2021
@teor2345
Copy link
Collaborator Author

In the most recent team sync, we decided to deploy a few nodes to mainnet and testnet for testing purposes.

We can do this as soon as the hang PR in #1707 is merged.

@teor2345 teor2345 changed the title Deploy more zcashd instances on testnet Deploy more Zebra instances on testnet Feb 16, 2021
@yaahc
Copy link
Contributor

yaahc commented Feb 26, 2021

From the discord:

quick thoughts

  • there is a zcashd Dockerfile somewhere in github.com/zcash repos (https://github.com/zcash/zcash/tree/master/contrib/docker)
  • Can copy the broad strokes of the cd.yml workflow, but we may make another google cloud project to put those in, since they are not technically Zebra(edited)
  • Our zebrad Dockerfiles have ARG's and stuff to allow mainnet/testnet and other config options, I am not familiar how configurable the existing zcashd Dockerfile is or zcashd period (exploration time! )
    I think all Zfnd engineers have a lot of powers in our gcloud but we can get there when we need to

@teor2345
Copy link
Collaborator Author

teor2345 commented Mar 1, 2021

  • Can copy the broad strokes of the cd.yml workflow, but we may make another google cloud project to put those in, since they are not technically Zebra(edited)

Yeah, we might want to keep the following deployments separate:

  • mainnet and testnet
  • per-merge-to-main and manual deploys
  • Zebra and zcashd

That way, it's easier for everyone to see what we have deployed, and to shut down things that aren't working.

@teor2345 teor2345 added C-enhancement Category: This is an improvement P-Medium labels Mar 1, 2021
@mpguerra mpguerra assigned mpguerra and yaahc and unassigned mpguerra Mar 4, 2021
@yaahc yaahc linked a pull request Mar 5, 2021 that will close this issue
1 task
🦓 automation moved this from To Do to Done Mar 6, 2021
Effort Affinity Grouping automation moved this from M - 5 to Done Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-infrastructure Area: Infrastructure changes C-enhancement Category: This is an improvement
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants