blockworks-foundation
/
solana
mirror of https://github.com/blockworks-foundation/solana.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update testnet deploy docs

This commit is contained in:
Michael Vines 2018-11-05 19:12:43 -08:00
parent 7789fda016
commit 52491b467a
No known key found for this signature in database
GPG Key ID: 33F4FDEC4E0E88BD
2 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ci/testnet-manager.sh
View File

@ -43,7 +43,7 @@ steps:
options: options:
- label: "Sanity check. Restart network on failure" - label: "Sanity check. Restart network on failure"
value: "sanity-or-restart" value: "sanity-or-restart"
- label: "Start the network" - label: "Start (or restart) the network"
value: "start" value: "start"
- label: "Stop the network" - label: "Stop the network"
value: "stop" value: "stop"

17
doc/testnet.md
View File

@ -4,14 +4,18 @@ Currently we have three testnets:
* `testnet` - public beta channel testnet accessible via testnet.solana.com. Runs 24/7 * `testnet` - public beta channel testnet accessible via testnet.solana.com. Runs 24/7
* `testnet-perf` - private beta channel testnet with clients trying to flood the network * `testnet-perf` - private beta channel testnet with clients trying to flood the network
with transactions until failure. Runs 24/7 with transactions until failure. Runs 24/7
* `testnet-master` - private edge channel testnet with clients trying to flood the network * `testnet-msater` - public edge channel testnet accessible via master.testnet.solana.com. Runs 24/7
* `testnet-master-perf` - private edge channel testnet with clients trying to flood the network
with transactions until failure. Runs on weekday mornings for a couple hours with transactions until failure. Runs on weekday mornings for a couple hours
## Deploy process ## Deploy process
They are deployed with the `ci/testnet-deploy.sh` script. There is a scheduled buildkite job which runs to do the deploy, They are deployed with the `ci/testnet-manager.sh` script through a list of [scheduled
look at `testnet-deploy` to see the agent which ran it and the logs. There is also a manual job to do the deploy manually.. buildkite jobs](https://buildkite.com/solana-labs/testnet-management/settings/schedules).
Validators are selected based on their machine name and everyone gets the binaries installed from snap. Each testnet can be manually manipulated from buildkite as well. The `-perf`
testnets use a release tarball while the non`-perf` builds use the snap build
(we've observed that the snap build runs slower than a tarball but this has yet
to be root caused).
## Where are the testnet logs? ## Where are the testnet logs?
@ -29,7 +33,8 @@ $ net/ssh.sh
for log location details for log location details
## How do I reset the testnet? ## How do I reset the testnet?
Manually trigger the [testnet-deploy](https://buildkite.com/solana-labs/testnet-deploy/) pipeline Manually trigger the [testnet-management](https://buildkite.com/solana-labs/testnet-management) pipeline
and when prompted select the desired testnet
## How can I scale the tx generation rate? ## How can I scale the tx generation rate?
@ -43,5 +48,5 @@ Currently, a merged PR is the only way to test a change on the testnet. But you
can run your own testnet using the scripts in the `net/` directory. can run your own testnet using the scripts in the `net/` directory.
## Adjusting the number of clients or validators on the testnet ## Adjusting the number of clients or validators on the testnet
Through the [testnet-deploy](https://buildkite.com/solana-labs/testnet-deploy/) settings. Edit `ci/testnet-manager.sh`