Deploying a Node

Here you will find instructions for the deployment of LACChain nodes using Dockers. By following this guide, your will deploy a writer node in your local machine. During the process of node deploying, you will be asked about the network in which you would like to deploy your nodes. At this moment the only network available is the Pro-Testnet. For deploying nodes in the Mainnet we recommend you to install using Ansible or using Kubernetes.

In order for your node to get permissioned, you need to complete the permissioning process first. In order to understand better what are the types of networks available and the permissioning processes for each network, please read permissioning process.

Minimum System Requirements

Recommended hardware features for Besu node:

Recommended Hardware

On Pro-Testnet

CPU

2 vCPUs

RAM Memory

8 GB

Hard Disk

200 GB SSD

Docker Host:

It is necessary to enable the following network ports in the machine in which we are going to deploy the node:

Besu Node:

  • Port 60606: TCP/UDP – To establish communication p2p between nodes.
  • Port 4545: TCP – To establish RPC communication. (this port is used for applications that communicate with LACChain and may be leaked to the Internet).

Nginx:

  • Port 8080: TCP – To establish RPC communication to Gas Model.

Pre-requisites

Install Docker Desktop

For this installation we will use docker-compose. It is necessary to install docker and docker-compose on a local machine that will perform the installation of the node. Follow the instructions to install docker desktop in your local machine.

Clone Repository

To configure and install Besu and Tessera, you must clone this git repository in your local machine.

				
					$ git clone https://github.com/LACNetNetworks/besu-networks
$ cd besu-networks/docker/compose
				
			

Node Installation

Preparing installation of a new node

There are three types of nodes (Bootnode / Validator / Writer) that can be created in the LACChain networks orchestrated by LACNet but at this moment you can only deploy writer nodes using docker-compose. For boot and validators you need to deploy using Ansible.

Environment variable

BESU_LOGGING:LOGGING – Level logging Besu (INFO, DEBUG, TRACE) – default INFO.

BESU_P2P_HOST: P2P Public IP Egress.

BESU_P2P_PORT: P2P PORT – Default (60606).

PUBLIC_IP: TCP Public IP.

NODE_NAME: Name you want for your node in the network monitoring tool.

NODE_EMAIL: email address you want to register for your node in the network monitoring tool. It’s a good idea to provide the e-mail of the technical contact identified or to be identified in the registration form as part of the on-boarding process.

Deploying the new node

Depending on the network you want to deploy the node, you need to move into the following folder structure:

				
					docker
  ├──compose  
    └── protest

				
			

So, if you want to deploy a writer node on pro-testnet cd to protest. 

				
					$ cd besu-networks/docker/compose/protest/writer1
				
			

This node comes with all the smart contracts pre-deployed, so you have to give permissions in the data directory to your user so you can read, write, and execute in this directory. Depending on your docker version, run:

				
					$ sudo chmod -R 667 data
$ cd ..
				
			

To deploy a writer node, run:

				
					$ docker-compose -f docker-compose-writer.yml up -d
				
			

At the end of the installation, if everything worked a BESU service will be created managed by docker with Up status. Do not forget to write down your node’s “enode” :

				
					  $ curl -X POST --data '{"jsonrpc":"2.0","method":"net_enode","params":[],"id":1}' http://localhost:4545

				
			

Result:

				
					"result" : "enode://d837cb6dd3880dec8360edfecf49ea7008e50cf3d889d4f75c0eb7d1033ae1b2fb783ad2021458a369db5d68cf8f25f3fb0080e11db238f4964e273bbc77d1ee@104.197.188.33:60606"

				
			

Node Configuration

Configuring the Besu node file

The default configuration should work for everyone. However, depending on your needs and technical knowledge you can modify your node’s settings in config-writer.toml, for RPC access or authentication. Please refer to the reference documentation.

Checking your connection

Once you have been permissioned, you can check if your node is connected to the network properly. Check that the node has stablished the connections with the peers:

 
				
					
$ curl -X POST --data '{"jsonrpc":"2.0","method":"net_peerCount","params":[],"id":1}' http://localhost:4545
				
			

You should get a result like this:

Now you can check if the node is syncing blocks by getting the log:

				
					$ docker logs <container name> -f 
$ docker logs writer-besu-david19  -f
				
			

You should get something like this:

If any of these two checks does not work, try to restart the besu service: e.g. Node Writer

				
					$ docker-compose -f docker-compose-writer.yml stop
$ docker-compose -f docker-compose-writer.yml up -d
				
			

Contact

If you find any issue, you can open an issue on Github and contact us at [email protected]. If you already have a membership, you can also open a ticket.

Next Steps

Now that you have installed your writer node, you can follow our guides to deploy smart contracts, deploy private channels (using Ansibleusing Dockers, or using Kubernetes), deploy an IPFS node (using Ansible, using Dockers, or using Kubernetes), and deploy the Hyperledger Firefly stack.

 

Copyright 2022 © All rights Reserved. Designed by LACNet