Skip to content

Latest commit

 

History

History
174 lines (117 loc) · 4.96 KB

vn.md

File metadata and controls

174 lines (117 loc) · 4.96 KB

Running Validator 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: "VN"
  ...

2. Specify target instance address

[deployment/ansible/inventory/hosts.yml]

all:
  ...
  children:
    ...
    validators:
      hosts:
        <validator node IP address or hostname>
    ...

3. Set persistent peers string in validator configuration

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

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

persistent_peers value:

  • If your VN doesn't use any Private Sentry nodes, then the persistent_peers field must point to other orgs' validator/sentry nodes with public IPs.
    For testnet-2.0 or main-net the persistent_peers string can be get from the CSA slack channel.
  • If Private Sentry Nodes are used, then it must point to Private Sentry nodes with private IPs.
  • Use the following command to get node-ID of a node: ./dcld tendermint show-node-id.

4. (Optional) 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/validator.yml]

config:
...
  statesync:
    enable: true
    rpc_servers: "http(s):<node1-IP>:26657, ..."
    trust_height: <trust-height>
    trust_hash: "<trust-hash>"
...

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

Make your node a Validator (target machine)

1. Switch to cosmovisor user in the Validator

sudo su -s /bin/bash cosmovisor

2. Generate NodeAdmin keys

dcld keys add "<admin-account-name>" 2>&1 | tee "<admin-account-name>.dclkey.data"

IMPORTANT keep generated data (especially the mnemonic) securely.

3. Share generated address and pubkey with the community

address and pubkey can be found using

dcld keys show --output text "<admin-account-name>"

4. Wait until your NodeAdmin key is proposed and approved by the quorum of trustees

  • Make sure the Node Admin account is proposed by a Trustee (usually CSA). The account will appear in the "Accounts" / "All Proposed Accounts" tab in DCL Web UI

  • Make sure that the proposed account is approved by at least 2/3 of Trustees. The account must disappear from the "Accounts" / "All Proposed Accounts" tab in Web UI, and appear in "Accounts" / "All Active Accounts" tab.

5. Check the account presence on the ledger

dcld query auth account --address="<address>"

6. Make the node a validator

dcld tx validator add-node --pubkey="<protobuf JSON encoded validator-pubkey>" --moniker="<node-name>" --from="<admin-account-name>"

Note: Get <protobuf JSON encoded validator-pubkey> using dcld tendermint show-validator command

(once transaction is successfully written you should see "code": 0 in the JSON output.)

7. Make sure the VN participates in consensus

dcld query tendermint-validator-set must contain the VN's address

Note: Get your VN's address using dcld tendermint show-address command.