This guide walks you through the process of upgrading your Cardano node from version 8.1.2 to the latest 8.7.2 using the Ansible playbook available at https://github.com/gp2pepe/ansible-cardano-node.
Prerequisites: Before starting the upgrade process, ensure you have Ansible installed on your system. Additionally, make sure to back up your existing configuration files, including
Installing BLST: The upgrade process includes the installation of BLST signature library focused on performance and security (https://github.com/supranational/blst). Yo can run the following command to install BLST using our ansible playbook:
ansible-playbook provision.yml -i inventories/relay-node --vault-password-file ~/path/to/.vault_pass.txt -t "blst" --flush-cache
This command installs BLST on you relay node configured on the inventory.
Performing the Update: Once BLST is installed, proceed with the Cardano node update using the following command:
ansible-playbook provision.yml -i inventories/relay-node --vault-password-file ~/path/to/.vault_pass.txt -t "update" --flush-cache
This command fetches the latest version of the Cardano node and updates your system accordingly, this could take a while depending on your hardware.
Updating Configuration Files: After the update, review and update your
conway-genesis.json files to align with any changes introduced in the new version:
Conway-genesis.json : https://book.world.dev.cardano.org/environments/mainnet/conway-genesis.json
Then start the cardano service:
sudo systemctl start cardano-node.service
And verify that is running:
sudo systemctl status cardano-node.service
Conclusion: By following these steps, you’ve successfully upgraded your Cardano node from version 8.1.2 to 8.7.2 using the provided Ansible playbook. Stay informed about future updates and security enhancements to keep your Cardano node running smoothly. For any additional support or inquiries, refer to the official Cardano documentation and community forums.
Note: This guide assumes a basic understanding of Ansible and Cardano node configuration. Always consult the official documentation for detailed instructions and best practices.