From f76df6d37bec55b2cb933f8cb49cd06a998e7b17 Mon Sep 17 00:00:00 2001 From: phahulin Date: Sun, 2 Sep 2018 15:49:21 +0300 Subject: [PATCH] Update Spec-hardfork.md --- docs/Spec-hardfork.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/docs/Spec-hardfork.md b/docs/Spec-hardfork.md index 33dd0a7..c7636c9 100644 --- a/docs/Spec-hardfork.md +++ b/docs/Spec-hardfork.md @@ -1,7 +1,13 @@ ## Make a spec.json hard-fork 0. this guide assumes that you're running this playbook from the same machine you used to make initial deployment of your node. So that you already have `python` and `ansible` installed, and you have the correct ssh keypair to root-access the node. -1. clone this repository: +1. if you already have a cloned version of this repository, pull latest changes: +``` +cd poa-devops +git pull origin master +``` + +otherwise, clone this repository: ``` git clone https://github.com/poanetwork/poa-devops.git cd poa-devops @@ -13,8 +19,8 @@ cp group_vars/hf-spec-change.example group_vars/all ``` and set the following variables: * `poa_role` - node's role (one of `bootnode`, `validator`, `moc`, `explorer`, `netstat`) -* `MAIN_REPO_FETCH` - github account where spec.json is located (e.g. "poanetwork") -* `GENESIS_BRANCH` - correct branch name to fetch from (e.g. "sokol" for testnet, "core" for mainnet) +* `MAIN_REPO_FETCH` - github account where spec.json is located (e.g. `poanetwork`) +* `GENESIS_BRANCH` - correct network name (`sokol` for testnet, `core` for mainnet) 3. create/edit `hosts` file: ``` @@ -43,14 +49,14 @@ and put your node's ip address (assuming it's 192.0.2.1) there with the followin 192.0.2.3 poa_role=moc 192.0.2.4 ``` -when you omit explicit `poa_role` in a row here, the value from `group_vars/all` is used. +on lines where you omitted explicit `poa_role`, the value from `group_vars/all` is used. 4. run the playbook: ``` ansible-playbook -i hosts site.yml ``` -5. verify that your node is active in the netstat of the corresponding network +5. verify that your node is active in the netstat of the corresponding network (https://sokol-netstat.poa.network/ for `sokol` or https://core-netstat.poa.network/ for `core`) 6. connect to the node ```