Adding a new node in Besu¶
To add a new organization in Besu, an existing besu network should be running, enode information of all existing nodes present in the network should be available, genesis file should be available in base64 encoding and the information of orion nodes should be available and new node account should be unlocked prior adding the new node to the existing besu network.
NOTE: Addition of a new organization has been tested on an existing network which is created by BAF. Networks created using other methods may be suitable but this has not been tested by BAF team.
NOTE: The guide is only for the addition of non-validator organization in existing besu network.
Create Configuration File¶
Refer this guide for details on editing the configuration file.
network.yaml file should contain the specific
network.organization details along with the enode information, genesis file in base64 encoding and orion transaction manager details
NOTE: Make sure that the genesis flie is provided in base64 encoding. Also, if you are adding node to the same cluster as of another node, make sure that you add the ambassador ports of the existing node present in the cluster to the network.yaml
For reference, sample
network.yaml file looks like below for IBFT consensus (but always check the latest network-besu-newnode.yaml at
--- # This is a sample configuration file for Hyperledger Besu network which has 4 nodes. # All text values are case-sensitive network: # Network level configuration specifies the attributes required for each organization # to join an existing network. type: besu version: 1.5.5 #this is the version of Besu docker image that will be deployed. #Environment section for Kubernetes setup env: type: "dev" # tag for the environment. Important to run multiple flux on single cluster proxy: ambassador # value has to be 'ambassador' as 'haproxy' has not been implemented for besu ## Any additional Ambassador ports can be given below, this is valid only if proxy='ambassador' # These ports are enabled per cluster, so if you have multiple clusters you do not need so many ports # This sample uses a single cluster, so we have to open 4 ports for each Node. These ports are again specified for each organization below ambassadorPorts: portRange: # For a range of ports from: 15010 to: 15043 # ports: 15020,15021 # For specific ports retry_count: 20 # Retry count for the checks on Kubernetes cluster external_dns: enabled # Should be enabled if using external-dns for automatic route configuration # Docker registry details where images are stored. This will be used to create k8s secrets # Please ensure all required images are built and stored in this registry. # Do not check-in docker_password. docker: url: "index.docker.io/hyperledgerlabs" username: "docker_username" password: "docker_password" # Following are the configurations for the common Besu network config: consensus: "ibft" # Options are "ibft". "ethash" and "clique" will be implemented in future release ## Certificate subject for the root CA of the network. # This is for development usage only where we create self-signed certificates and the truststores are generated automatically. # Production systems should generate proper certificates and configure truststores accordingly. subject: "CN=DLT Root CA,OU=DLT,O=DLT,L=London,C=GB" transaction_manager: "orion" # Transaction manager is "orion" # This is the version of "orion" docker image that will be deployed tm_version: "1.6.0" # TLS can be True or False for the orion tm tm_tls: True # Tls trust value tm_trust: "ca-or-tofu" # Options are: "whitelist", "ca-or-tofu", "ca", "tofu" ## File location for saving the genesis file should be provided. genesis: "/home/user/blockchain-automation-framework/build/besu_genesis" # Location where genesis file will be fetched ## Transaction Manager nodes public addresses should be provided. # - "https://node.test.besu.blockchain-develop.com:15013" # The above domain name is formed by the (http or https)://(peer.name).(org.external_url_suffix):(ambassador orion node port) tm_nodes: - "https://carrier.test.besu.blockchaincloudpoc-develop.com:15013" - "https://manufacturer.test.besu.blockchaincloudpoc-develop.com:15023" - "https://store.test.besu.blockchaincloudpoc-develop.com:15033" - "https://warehouse.test.besu.blockchaincloudpoc-develop.com:15043" # Besu rpc public address list for existing validator and member nodes # - "http://node.test.besu.blockchaincloudpoc-develop.com:15011" # The above domain name is formed by the (http)://(peer.name).(org.external_url_suffix):(ambassador node rpc port) besu_nodes: - "http://validator.test.besu.blockchaincloudpoc-develop.com:15051" - "http://carrier.test.besu.blockchaincloudpoc-develop.com:15011" - "http://manufacturer.test.besu.blockchaincloudpoc-develop.com:15021" - "http://store.test.besu.blockchaincloudpoc-develop.com:15031" # Allows specification of one or many organizations that will be connecting to a network. organizations: # Specification for the 1st organization. Each organization should map to a VPC and a separate k8s cluster for production deployments - organization: name: neworg type: member # Provide the url suffix that will be added in DNS recordset. Must be different for different clusters # This is not used for Besu as Besu does not support DNS hostnames currently. Here for future use external_url_suffix: test.besu.blockchaincloudpoc.com cloud_provider: aws # Options: aws, azure, gcp aws: access_key: "aws_access_key" # AWS Access key, only used when cloud_provider=aws secret_key: "aws_secret_key" # AWS Secret key, only used when cloud_provider=aws region: "aws_region" # AWS Region where cluster and EIPs are created # Kubernetes cluster deployment variables. The config file path and name has to be provided in case # the cluster has already been created. k8s: context: "cluster_context" config_file: "cluster_config" # Hashicorp Vault server address and root-token. Vault should be unsealed. # Do not check-in root_token vault: url: "vault_addr" root_token: "vault_root_token" # Git Repo details which will be used by GitOps/Flux. # Do not check-in git_access_token gitops: git_protocol: "https" # Option for git over https or ssh git_url: "https://github.com/<username>/blockchain-automation-framework.git" # Gitops https or ssh url for flux value files branch: "develop" # Git branch where release is being made release_dir: "platforms/hyperledger-besu/releases/dev" # Relative Path in the Git repo for flux sync per environment. chart_source: "platforms/hyperledger-besu/charts" # Relative Path where the Helm charts are stored in Git repo git_repo: "github.com/<username>/blockchain-automation-framework.git" # Gitops git repository URL for git push username: "git_username" # Git Service user who has rights to check-in in all branches password: "git_access_token" # Git Server user access token (Optional for ssh; Required for https) email: "git_email" # Email to use in git config private_key: "path_to_private_key" # Path to private key file which has write-access to the git repo (Optional for https; Required for ssh) # The participating nodes are named as peers services: peers: - peer: name: newOrg subject: "O=Neworg,OU=Neworg,L=51.50/-0.13/London,C=GB" # This is the node subject. L=lat/long is mandatory for supplychain sample app geth_passphrase: 12345 # Passphrase to be used to generate geth account lock: false # Sets Besu node to lock or unlock mode. Can be true or false p2p: port: 30303 ambassador: 15020 #Port exposed on ambassador service (use one port per org if using single cluster) rpc: port: 8545 ambassador: 15021 #Port exposed on ambassador service (use one port per org if using single cluster) ws: port: 8546 tm_nodeport: port: 15022 # Port exposed on ambassador service must be same ambassador: 15022 tm_clientport: port: 8888
Three new sections are added to the network.yaml
|tm_nodes||Existing network's transaction manager nodes public addresses with nodeport provided as an array.|
|besu_nodes||Existing network's besu nodes public addresses with rpc port provided as an array.|
|genesis||Path to existing network's genesis.json in base64.|