Rename leader/validator to bootstrap-leader/fullnode

Only rsyncing the genesis ledger snuck in here as well
This commit is contained in:
Michael Vines
2018-12-06 13:38:45 -08:00
parent b34e197424
commit 70c149c7da
15 changed files with 135 additions and 144 deletions

View File

@@ -41,7 +41,7 @@ $ git checkout $TAG
### Configuration Setup
The network is initialized with a genesis ledger and leader/validator configuration files.
The network is initialized with a genesis ledger and fullnode configuration files.
These files can be generated by running the following script.
```bash
@@ -50,12 +50,12 @@ $ ./multinode-demo/setup.sh
### Drone
In order for the leader, client and validators to work, we'll need to
In order for the fullnodes and clients to work, we'll need to
spin up a drone to give out some test tokens. The drone delivers Milton
Friedman-style "air drops" (free tokens to requesting clients) to be used in
test transactions.
Start the drone on the leader node with:
Start the drone with:
```bash
$ ./multinode-demo/drone.sh
@@ -64,13 +64,13 @@ $ ./multinode-demo/drone.sh
### Singlenode Testnet
Before you start a fullnode, make sure you know the IP address of the machine you
want to be the leader for the demo, and make sure that udp ports 8000-10000 are
want to be the bootstrap leader for the demo, and make sure that udp ports 8000-10000 are
open on all the machines you want to test with.
Now start the server in a separate shell:
Now start the bootstrap leader in a separate shell:
```bash
$ ./multinode-demo/leader.sh
$ ./multinode-demo/bootstrap-leader.sh
```
Wait a few seconds for the server to initialize. It will print "leader ready..." when it's ready to
@@ -79,21 +79,21 @@ The drone does not need to be running for subsequent leader starts.
### Multinode Testnet
To run a multinode testnet, after starting a leader node, spin up some validator nodes in
separate shells:
To run a multinode testnet, after starting a leader node, spin up some
additional full nodes in separate shells:
```bash
$ ./multinode-demo/validator.sh
$ ./multinode-demo/fullnode-x.sh
```
To run a performance-enhanced leader or validator (on Linux),
To run a performance-enhanced full node on Linux,
[CUDA 10.0](https://developer.nvidia.com/cuda-downloads) must be installed on
your system:
```bash
$ ./fetch-perf-libs.sh
$ SOLANA_CUDA=1 ./multinode-demo/leader.sh
$ SOLANA_CUDA=1 ./multinode-demo/validator.sh
$ SOLANA_CUDA=1 ./multinode-demo/bootstrap-leader.sh
$ SOLANA_CUDA=1 ./multinode-demo/fullnode-x.sh
```
@@ -153,14 +153,13 @@ $ sudo snap refresh solana --devmode
```
### Daemon Support
The snap supports running a leader, validator or leader+drone node as a system
daemon.
The snap supports running fullnodes and a drone as system daemons.
Run `sudo snap get solana` to view the current daemon configuration. To view
daemon logs:
1. Run `sudo snap logs -n=all solana` to view the daemon initialization log
2. Runtime logging can be found under `/var/snap/solana/current/leader/`,
`/var/snap/solana/current/validator/`, or `/var/snap/solana/current/drone/` depending
2. Runtime logging can be found under `/var/snap/solana/current/bootstrap-leader/`,
`/var/snap/solana/current/fullnode/`, or `/var/snap/solana/current/drone/` depending
on which `mode=` was selected. Within each log directory the file `current`
contains the latest log, and the files `*.s` (if present) contain older rotated
logs.
@@ -177,7 +176,7 @@ Runtime configuration files for the daemon can be found in
#### Leader Daemon
```bash
$ sudo snap set solana mode=bootstrap-fullnode
$ sudo snap set solana mode=bootstrap-leader
```
`rsync` must be configured and running on the leader.
@@ -200,7 +199,7 @@ to port tcp:873, tcp:9900 and the port range udp:8000-udp:10000**
To run both the Leader and Drone:
```bash
$ sudo snap set solana mode=bootstrap-fullnode+drone
$ sudo snap set solana mode=bootstrap-leader+drone
```