This repository provides an Ansible playbook and accompanying roles used for idempotent provisioning of the Algorand node on all the major desktop and server platforms.
It allows CI/CD process for your applications based on the Algorand blockchain. In the future, this repository will contain Ansible roles for provisioning of the Indexer and the Sandbox too.
Ansible has to be installed on your local machine. If you have Python 3 and pip installed on it, it comes down to issuing the following command:
# pip install --user ansiblePython has to be installed on the host machine(s).
The developer tools should be installed on a Mac OS by issuing:
sudo xcode-select --installYou should create an inventory file in the project's root directory, for example with the name hosts. Each line in that file represents a different host. You may either add the hostname aliases or just the IPs of the machines you want to provision:
fedora ansible_host=192.168.1.80 # alias and the IP
192.168.1.81 # just an IP
my_vps # just a hostname, implies entry in your /etc/hostsTake a look at example_hosts (INI type configuration) or example_hosts.yaml (configuration in YAML syntax) - use them as a template for your hosts inventory. Btw, the initial example inventory implies some virtual machines are created in your local network.
For the MS Windows and Mac OS hosts, place the hosts lines inside the corresponding groups and set the default variables as follows:
[macos]
catalina ansible_host=192.168.1.84
[windows]
192.168.1.85
[macos:vars]
ansible_user=algonaut
[windows:vars]
ansible_user=algonaut
ansible_connection=ssh
ansible_shell_type=cmdChange the value for the ansible_user with the existing privileged user name in the host machine. The ansible_connection from the above implies that you have OpenSSH installed on your Windows host.
In order to suppress warnings about the discovered Python interpreter, set the path to Python interpreter under the all:vars (or under specific host group):
[all:vars]
ansible_python_interpreter=/usr/bin/python3To customize the installation, change any of the variables found in the group_vars/all/vars.yml file:
# default administrator user on the host machine(s)
admin_user: algonaut
admin_user_group: "{{ admin_user }}"
# identity used to connect to host machine(s)
local_path_to_public_key: ~/.ssh/id_rsa.pub
# Algorand network configuration
algorand_network: "testnet"
fast_catchup: true
# installation by system package manager
use_package_manager: true
install_algorand_devtools: true
# installation by updater script
node_directory: "{{ admin_home_directory }}node/"
node_data_directory: "{{ node_directory }}data/"
common_data_directory: false
systemd_timer_update: false
# installation in Windows
algorand_version: "" # leave empty for the latest
# setup telemetry
enable_telemetry: false
use_hostname_for_telemetry: true
fixed_name_for_telemetry: ""This playbook will create an administrator user on the host machine if it doesn't exist. In order to create that user, we need to connect to the host machine as a privileged user. The default privileged user for the Linux machines is the root and we should add our SSH identity's public key to the list of authorized keys. The following command will add your default identity's public key (~/.ssh/id_rsa.pub) to the machine with IP of 192.168.1.90:
ssh-copy-id root@192.168.1.90If you already have a privileged user set up in the host machine then you may use it instead of root by appending the superuser variable to the host line (change username to the name of your privileged user):
192.168.1.92 superuser=usernameTo avoid supplying the password every time you run the playbook, you should append the following line to the /etc/sudoers file on the host machine:
username ALL=(ALL) NOPASSWD: ALLIn order to provision all the hosts from the hosts inventory, issue the following command from the project's root directory:
ansible-playbook -i hosts node_playbook.ymlTo limit provisioning only to some hosts:
ansible-playbook -i hosts.yaml -l my_vps node_playbook.ymlIssue the following command in order to provision your local machine (change algonaut to your username on the local machine):
ansible-playbook --connection=local \
--inventory 127.0.0.1, --limit 127.0.0.1 \
-e admin_user=algonaut -e admin_user_group=algonaut \
-i hosts node_playbook.yml --ask-become-passYou may also need to add -e ansible_become_method=su to that command if your local machine's OS is Debian.
Use your package manager to remove the Algorand node installed by the package manager, for the Debian-based systems that would be the following command:
apt-get remove algorand algorand-devtoolsRemove logs and all other data with:
sudo rm -rf /var/lib/algorand/If you used the updater script to install the Algorand node, you may remove it with the following commands (it's implied your Algorand node has been installed in /home/algonaut/node directory):
$ sudo systemctl stop algorand@$(systemd-escape /home/algonaut/node/data)
$ sudo systemctl disable algorand@$(systemd-escape /home/algonaut/node/data)
$ sudo rm /lib/systemd/system/algorand@.service
rm -r /home/algonaut/node/Remove Algorand node's environment variables by deleting the following lines from your ~/.bash_profile:
export ALGORAND_DATA="/home/algonaut/node/data/"
export PATH="/home/algonaut/node/:$PATH"The playbook has been tested on the following platforms:
- Debian 10
- Debian 11
- Ubuntu 18.04
- Ubuntu 20.04
- Ubuntu 21.04
- Fedora 34
- CentOS 7.9
- CentOS 8.4
- OracleLinux 8.4
- Rocky Linux 8.4
- AlmaLinux 8.4
- openSUSE Leap 15.3
- Manjaro 21.0.7
- Mageia 8
- Alpine 3.14.0
- Solus 4.3
- Mac OS X 10.15.7 (Catalina)
- Microsoft Windows 10 20H2
If you've encountered a bug or need an implementation for some other distribution, feel free to create an issue. If you are going to provide your playbook's output, please use the -vv or -vvvv argument to increase verbosity:
ansible-playbook -vv -i hosts node_playbook.yml