Skip to content

Latest commit

 

History

History
202 lines (140 loc) · 4.76 KB

on.md

File metadata and controls

202 lines (140 loc) · 4.76 KB
Raw

Running Observer Node using Ansible

Prerequisites

Follow all steps from common.md.

Configure node type specific parameters (local machine)

1. Set node type

[deployment/ansible/inventory/group_vars/all.yml]

  type_name: "ON"
  ...

2. Specify target instance address

[deployment/ansible/inventory/hosts.yml]

all:
    ...
    children:
      ...
      observers:
        hosts:
        <observer node IP address or hostname>
      ...

3. Specify the nodes for connection

Option 1: an Observer node is connected to another organization's Public Sentries via Seed nodes

This is the main option if you want to connect an ON to CSA public nodes.

[deployment/ansible/roles/configure/vars/observer.yml]

...
config:
  p2p:
    seeds: "<seed-node-ID>@<seed-node-public-IP>:26656"
...
CSA `seeds` Example for Testnet 2.0 (clickable) 
seeds: "[email protected]:26656"
CSA `seeds` Example for MainNet (clickable) 
seeds: "[email protected]:26656"

Option 2: an Observer node is connected to another organization's public nodes

This option can be used if you have a trusted relationship with some organization and that organization provided you with access to its nodes.

[deployment/ansible/roles/configure/vars/observer.yml]

...
config:
  p2p:
    persistent_peers: "<node1-ID>@<node1-IP>:26656,..."
...

persistent_peers value:

  • another organization nodes with public IPs that this organization shared with you.

Option 3: an Observer node is connected to my organization nodes

This is the option when you have a VN and want to create an ON connected to it.

[deployment/ansible/roles/configure/vars/observer.yml]

...
config:
  p2p:
    persistent_peers: "<node1-ID>@<node1-IP>:26656,..."
...

persistent_peers value:

  • If your VN doesn't use any Private Sentry nodes, then it must point to the Validator node with private IP.
  • Otherwise, it must point to the Private Sentry nodes with private IPs.
  • Use the following command to get node-ID of a node: ./dcld tendermint show-node-id.

4. If you are joining a long-running network, enable statesync or use one of the options in running-node-in-existing-network.md

[deployment/ansible/roles/configure/vars/observer.yml]

config:
...
  statesync:
    enable: true
    rpc_servers: "http(s):<node1-IP>:26657, ..."
    trust_height: <trust-height>
    trust_hash: "<trust-hash>"
...
Example for Testnet 2.0 (clickable) 
config:
  statesync:
    enable: true
    rpc_servers: "https://on.test-net.dcl.csa-iot.org:26657,https://on.test-net.dcl.csa-iot.org:26657"
Example for Mainnet (clickable) 
config:
  statesync:
    enable: true
    rpc_servers: "https://on.dcl.csa-iot.org:26657,https://on.dcl.csa-iot.org:26657"

NOTE: You should provide at least 2 addresses for rpc_servers. It can be 2 identical addresses

You can use the following command to obtain <trust-height> and <trust-hash> of your network

curl -s http(s)://<host>:<port>/commit | jq "{height: .result.signed_header.header.height, hash: .result.signed_header.commit.block_id.hash}"
Example for Testnet 2.0 (clickable) 
curl -s https://on.test-net.dcl.csa-iot.org:26657/commit | jq "{height: .result.signed_header.header.height, hash: .result.signed_header.commit.block_id.hash}"
Example for Mainnet (clickable) 
curl -s https://on.dcl.csa-iot.org:26657/commit | jq "{height: .result.signed_header.header.height, hash: .result.signed_header.commit.block_id.hash}"
  • <host> - RPC endpoint host of the network being joined
  • <port> - RPC endpoint port of the network being joined

NOTE: State sync is not attempted if the node has any local state (LastBlockHeight > 0)

Run ansible (local machine)

1. Verify that all the configuration parameters from the previous section are correct

2. Run ansible

ansible-playbook -i ./deployment/ansible/inventory  -u <target-host-ssh-user> ./deployment/ansible/deploy.yml
  • <target-host-ssh-username> - target host ssh user
  • Ansible provisioning can take several minutes depending on number of nodes being provisioned

Deployment Verification (target machine)

1. Switch to cosmovisor user

sudo su -s /bin/bash cosmovisor

2. Query status

dcld status