Page Comparison

...

AWS Management Console (amazon.com)

Devnet - FIO Operations - Confluence (atlassian.net)

Devnet Testing (fioprotocol.io)

...

The DevNet build, and deploy process follows the LocalNet Release process (steps 1, 3 and 4)

...

Review the Master Release Plan at Master Release Plan and identify the current MainNet release branches. For example, the 3.3.0 Release has the following repos/branches:

1. fio - release/3.3.x-dev

2. fio.contracts - release/2.7.x

3. fio.test - release/2.7.x_3.3.x

4. fio.devtools - release/2.7.x_3.3.x

5. fiosdk_typescript - release/1.6.x

...

On the master (boot) node, check out the repos cloned above to the current MainNet release versions

1. To build, deploy and test the release, check out the appropriate branch in the following repos:

   1. fio.contracts

   2. fio.devtools

   3. For instance, to test the FIP-41, FIP-17a, FIP-17b release (future), checkout out the repos as follows:

      1. fio.contracts - release/2.7.x

      2. fio.devtools - release/2.7.x_3.3.x

2. Build the contracts

   1. cd fio.devtools

   2. Execute ./start.sh <FIO Version> and specify the following responses to the runtime options

      1. Local Startup (1)

      2. Update/Build Contracts (2)

3. Start the Local Chain

   1. Execute ./start.sh <FIO Version> and specify the following responses to the runtime options

      1. Local Startup (1)

      2. Local Blockchain (1)

      3. Increased Transaction Time (2)

...

-4). See FIO LocalNet Release Notes. In addition, perform the following steps on the devnet master node to spin up the nodes, devnet-a, devnet-b and devnet-c. Note that this requires access to the AWS Management Console for the DevNet cluster.

The DevNet boot node, devnet.fioprotocol.io, has the following directory layout;

Under /home/ubuntu, the following directories exist;

• 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 reltest.

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