To run playbook you will need a user on the server with
sudo privileges and who can be logged in via SSH public key. By default it is assumed that this user is called
ubuntu. If you already have a user with different name who satisfies these requirements, at the top of
-hosts: all section change line
user: ubuntu to the
sudo user you have
---- hosts: alluser: ubuntubecome: True...
1) Clone repository with ansible playbooks and checkout branch with the network name you want to join (e.g.
core for mainnet and
sokol for testnet)
git clone https://github.com/poanetwork/deployment-playbooks.gitcd deployment-playbooks# for core mainnetgit checkout core# OR for sokol testnetgit checkout sokol# check that you ended up on a correct branch (look where the `*` is)git branch
2) two files with ssh public key need to be created for ansible playbook to configure node correctly, use the path to your desired key.
cat ~/.ssh/id_poa-core.pub > files/admins.pubcp files/admins.pub files/ssh_bootnode.pub
3) create configuration file
cat group_vars/all.network group_vars/bootnode.example > group_vars/all
4) edit the
group_vars/all file and comment out parameters corresponding to aws:
5) set values given to you by Master of Ceremony for the following parameters in
6) set the following options as follows:
allow_bootnode_ssh: trueallow_bootnode_p2p: trueallow_bootnode_rpc: falseassociate_bootnode_elastic_ip: false
7) create file
hosts with the server's ip address (e.g. 192.0.2.1):
8) run ansible playbook, replace the
--key-file path with your desired SSH key
ansible-playbook -i hosts site.yml -K --key-file "~/.ssh/id_poa-core"
NETSTATS_SERVER url in the browser and check that the node named
NODE_FULLNAME appeared in the list
10) login to the node and get enode from parity logs:
Without access to
root you can use
sudo user instead, append
sudo in front of commands after connecting to remote machine
grep enode /home/bootnode/logs/parity.log
enode uri and send it to Master of Ceremony. If this line is not found, restart parity
systemctl restart poa-parity
and try again. If
enode uri is still not found, use the commands below to restart all services.
su bootnodepm2 restart all
after that refresh
NETSTATS_SERVER url and check your node's block number. If your node is still not active or missing
enode, log in to root account and reboot.
sushutdown -r now