Move validators from testnet-beta to testnet (#4011)

* Move validators from testnet-beta to testnet

* Move testnet influxdb datasource to influxcloud

book/src/testnet-participation.md

@@ -1,22 +1,25 @@
 ## Testnet Participation
-This document describes how to participate in the beta testnet as a
+This document describes how to participate in the testnet as a
 validator node.
 
 Please note some of the information and instructions described here may change
 in future releases.
 
 ### Beta Testnet Overview
-The beta testnet features a validator running at beta.testnet.solana.com, which
+The testnet features a validator running at testnet.solana.com, which
 serves as the entrypoint to the cluster for your validator.
 
 Additionally there is a blockexplorer available at
-[http://beta.testnet.solana.com/](http://beta.testnet.solana.com/).
+[http://testnet.solana.com/](http://testnet.solana.com/).
 
-The beta testnet is configured to reset the ledger daily, or sooner
+The testnet is configured to reset the ledger daily, or sooner
 should the hourly automated cluster sanity test fail.
 
+There is a **#validator-support** Discord channel available to reach other
+testnet participants, https://discord.gg/pquxPsq.
+
 ### Machine Requirements
-Since the beta testnet is not intended for stress testing of max transaction
+Since the testnet is not intended for stress testing of max transaction
 throughput, a higher-end machine with a GPU is not necessary to participate.
 
 However ensure the machine used is not behind a residential NAT to avoid NAT
@@ -34,13 +37,13 @@ itself before debugging further.
 
 Fetch the current transaction count over JSON RPC:
 ```bash
-$ curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getTransactionCount"}' http://beta.testnet.solana.com:8899
+$ curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1, "method":"getTransactionCount"}' http://testnet.solana.com:8899
 ```
 
-Inspect the blockexplorer at [http://beta.testnet.solana.com/](http://beta.testnet.solana.com/) for activity.
+Inspect the blockexplorer at [http://testnet.solana.com/](http://testnet.solana.com/) for activity.
 
 View the [metrics dashboard](
-https://metrics.solana.com:3000/d/testnet-beta/testnet-monitor-beta?var-testnet=testnet-beta)
+https://metrics.solana.com:3000/d/testnet-beta/testnet-monitor-beta?var-testnet=testnet)
 for more detail on cluster activity.
 
 ### Validator Setup
@@ -53,13 +56,13 @@ software on Linux x86_64 systems.
 Install the latest release with a single shell command:
 ```bash
 $ curl -sSf https://raw.githubusercontent.com/solana-labs/solana/v0.14.0/install/solana-install-init.sh | \
-  sh -s - --url https://api.beta.testnet.solana.com
+  sh -s - --url https://api.testnet.solana.com
 ```
 
 Alternatively build the `solana-install` program from source and run the
 following command to obtain the same result:
 ```bash
-$ solana-install init --url https://api.beta.testnet.solana.com
+$ solana-install init --url https://api.testnet.solana.com
 ```
 
 After a successful install, `solana-install update` may be used to easily update the cluster
@@ -92,13 +95,13 @@ $ export PATH=$PWD/bin:$PATH
 Sanity check that you are able to interact with the cluster by receiving a small
 airdrop of lamports from the testnet drone:
 ```bash
-$ solana-wallet -n beta.testnet.solana.com airdrop 123
-$ solana-wallet -n beta.testnet.solana.com balance
+$ solana-wallet -n testnet.solana.com airdrop 123
+$ solana-wallet -n testnet.solana.com balance
 ```
 
 Also try running following command to join the gossip network and view all the other nodes in the cluster:
 ```bash
-$ solana-gossip --network beta.testnet.solana.com:8001 spy
+$ solana-gossip --network testnet.solana.com:8001 spy
 # Press ^C to exit
 ```
 
@@ -107,20 +110,20 @@ Then the following command will start a new validator node.
 If this is a `solana-install`-installation:
 ```bash
 $ clear-fullnode-config.sh
-$ fullnode.sh --public-address --poll-for-new-genesis-block beta.testnet.solana.com
+$ fullnode.sh --public-address --poll-for-new-genesis-block testnet.solana.com
 ```
 
 Alternatively, the `solana-install run` command can be used to run the validator
 node while periodically checking for and applying software updates:
 ```bash
 $ clear-fullnode-config.sh
-$ solana-install run fullnode.sh -- --public-address --poll-for-new-genesis-block beta.testnet.solana.com
+$ solana-install run fullnode.sh -- --public-address --poll-for-new-genesis-block testnet.solana.com
 ```
 
 If you built from source:
 ```bash
 $ USE_INSTALL=1 ./multinode-demo/clear-fullnode-config.sh
-$ USE_INSTALL=1 ./multinode-demo/fullnode.sh --public-address --poll-for-new-genesis-block beta.testnet.solana.com
+$ USE_INSTALL=1 ./multinode-demo/fullnode.sh --public-address --poll-for-new-genesis-block testnet.solana.com
 ```
 
 #### Controlling local network port allocation
@@ -150,7 +153,7 @@ accounts: ...
 Provide the **vote id** pubkey to the `solana-wallet show-vote-account` command to view
 the recent voting activity from your validator:
 ```bash
-$ solana-wallet -n beta.testnet.solana.com show-vote-account 2ozWvfaXQd1X6uKh8jERoRGApDqSqcEy6fF1oN13LL2G
+$ solana-wallet -n testnet.solana.com show-vote-account 2ozWvfaXQd1X6uKh8jERoRGApDqSqcEy6fF1oN13LL2G
 ```
 
 The vote id for the validator can also be found by running:
@@ -167,6 +170,6 @@ validator node:
 ```bash
 export u="username obtained from the Solana maintainers"
 export p="password obtained from the Solana maintainers"
-export SOLANA_METRICS_CONFIG="db=testnet-beta,u=${u:?},p=${p:?}"
+export SOLANA_METRICS_CONFIG="db=testnet,u=${u:?},p=${p:?}"
 source scripts/configure-metrics.sh
 ```

ci/testnet-manager.sh

@@ -86,6 +86,7 @@ testnet-beta|testnet-beta-perf)
 testnet|testnet-perf)
   CHANNEL_OR_TAG=$STABLE_CHANNEL_LATEST_TAG
   CHANNEL_BRANCH=$STABLE_CHANNEL
+  : "${TESTNET_DB_HOST:=https://clocktower-f1d56615.influxcloud.net:8086}"
   ;;
 *)
   echo "Error: Invalid TESTNET=$TESTNET"