Do the following on a machine that is different from the machine you are going to upgrade and has your ssh key on it (your normal dev PC works)
apt-get install ansible
orbrew install ansible
- Set your machine details in
machine-description.yml
- run
bash deploy.sh
oransible-playbook -v -i machine-description.yml deploy.yml
- If you did an initial deployment, the user you use to SSH into the box may have changed during the above step depending on what you have set for
ansible_user
andssh_user
, so you may need to adjust theansible_user
var. - ensure all is looking fine, and then finally run
bash reboot.sh
, wait up to 20 minutes for the machine to be accessible via ssh again
NOTE for OVH ADVANCE
class devices:
When doing an initial deployment with OLA (OVH Cloud Link Aggregation, see https://www.notion.so/litprotocol/Datil-test-Testnet-Node-Provisioning-Guide-6c78bd5e7ebd4b0f8cec1ad78e130be2?pvs=4#22de9bba0e7e49108509a5d60b8f6aaa), what you entered for host_ip
becomes the IP you need to use to access your machine via SSH after you reboot.
After executing reboot.sh
your machine may not be reachable (and the reboot.sh
will time out waiting) until you change ansible_host
to be equal to the host_ip
(you can also just SSH into host_ip
manually after reboot as that is the final step anyway)
If you encounter errors during this process:
- save a copy of the
deploy.log
file and send it to someone from Lit Protocol for debugging - You may attempt to rerun the
deploy.sh
script, it will simply skip the already completed steps