Page Comparison

...

• devnet ← contains devnet repo and devnet executable

• repos ← contains directories with names aligned with the build

  • localnet: a develop repo directory

  • mainnet: a mainnet release directory (branches are those is the last release to MainNet)

  • reltest: a release test directory (branches are a combination of those in MainNet and Develop)

For the purposes of this document the repo directory will be reltestNote that to run any commands using the devnet tool, a chain must be running. Also note that when running the chain using fio.devtools start.sh, a local cluster of three nodes is automatically started.

1. Stop and clean any running chains using fio.devtools/start.sh

2. Build, and install fio as discussed in FIO LocalNet Release Notes.

3. Start the chain and build the contracts (see above)

4. Using the devnet tool, upgrade the nodes, devnet-a, devnet-b and devnet-c.

   1. Stop all remote nodes using the command ./devnet -f config.yml stop. Note that fio-nodeos is started on startup/boot of nodes

      1. For devnet-a, the config yaml file is a.yml

      2. For devnet-b, the config yaml file is b.yml

      3. For devnet-c, the config yaml file is c.yml

   2. Upgrade and start the nodes with the newly build nodeos using the command, ./devnet -f config.yml -bin <FIO Install Dir>/bin/nodeos upgrade

      1. The FIO Install Dir is /home/ubuntu/fio/<Version Nbr>

      2. For devnet-a, the config yaml file is a.yml

      3. For devnet-b, the config yaml file is b.yml

      4. For devnet-c, the config yaml file is c.yml

5. Start fiotop

6. Run any tests from a client (also discussed in FIO LocalNet Release Notes) against the boot node IP

Fork Testing