Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/polkachu/cosmos-validators
Ansible Script for Cosmos-based blockchain validators
https://github.com/polkachu/cosmos-validators
Last synced: 4 days ago
JSON representation
Ansible Script for Cosmos-based blockchain validators
- Host: GitHub
- URL: https://github.com/polkachu/cosmos-validators
- Owner: polkachu
- Created: 2021-11-09T21:30:29.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-10-18T23:30:02.000Z (21 days ago)
- Last Synced: 2024-10-20T09:28:19.639Z (20 days ago)
- Language: Jinja
- Size: 925 KB
- Stars: 128
- Watchers: 8
- Forks: 99
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
- Support: support_backup_node.yml
Awesome Lists containing this project
- awesome-ccamel - polkachu/cosmos-validators - Ansible Script for Cosmos-based blockchain validators (Jinja)
README
# Cosmos-based Node Ansible Setup Plus Several Supporting Playbooks
## Design Philosophy
1. Extendable to most Tendermint-based chains
1. Support both mainnet and testnet
1. Stable playbooks and roles; Customizable variables
1. Support essential functions (snapshot, state-sync, public RPC/API endpoints) through separate playbooks
## TL/DR
You run one playbook and set up a node.
```bash
ansible-playbook main.yml -e "target=juno_main"
ansible-playbook -i inventory_testnet.ini main.yml -e "target=juno_test"
```
Because we try our best to support the latest node version, it is not recommended for you to sync from Block 1. Rather, please [state-sync](https://polkachu.com/state_sync) or start from a [snapshot](https://polkachu.com/tendermint_snapshots).
## Node deployment (Validator, Backup and Relayer)
For every network where we run a validator on mainnet, we run 3 nodes (Validator, Backup and Relayer). The details of our 3-node infrastructure are documented [here](https://polkachu.com/blogs/holy-trinity-a-system-approach-to-tendermint-based-chain-validation).
#### Opinionated Configuration
We have 2 strong opinions about the node configuration:
1. Each network will have its custom port prefix. This is to prevent port collision if you run multiple nodes on the same server. For example, Juno's custom port prefix is 126 and that of Osmosis is 125. Since it is rather arbitrary, we are going to force the same convention on you unless you fork the code. The full list of our port prefixes is [here](https://github.com/polkachu/cosmos-port-prefixes). We recommend you follow this convention.
1. Each type of node will have its setting based on Polkachu's "best practice". For example, the main node (Validator) has null indexer, and 100/0/ pruning, and Relayer node has kv indexer and 40000/2000/ pruning. We will force these setting on you unless you fork the code.
#### Host Variables
Take a look at the `inventory.sample` file. You will see an example `juno` group with 3 different hosts: `juno_main`, `juno_backup`, and `juno_relayer`. Each host will have the following variables:
1. `ansible_host`: Required. The IP address of the server.
1. `type`: Required. It can be `main`, `backup` and `relayer` (also `test` if you are adventurous). Each is opinionated in its configuration settings.
1. `prepare`: Optional. If unset, it is default to true. If `false`, it will skip setups of firewall, go, cosmovisor, node exporter, promtail, etc. The reason for the `false` option is because we run many backup/relayer nodes on the same server with setup done already.
#### Other Variables
Besides the above host variables, you will also specify the following `all` variables in the inventory file:
1. `ansible_user`: The sample file assumes `ubuntu`, but feel free to use other user name. This user need sudo privilege.
1. `ansible_port`: The sample file assumes `22`. But if you are like me, you will have a different ssh port other than `22` to avoid port sniffing.
1. `ansible_ssh_private_key_file`: The sample file assumes `~/.ssh/id_rsa`, but you might have a different key location.
1. `var_file`: It tells the program where to look for the variable file. This is useless for the mainnet, because the var file will automatically be inferred by the network name. However, it is essentially for testnets.
1. `user_dir`: The user's home directory. In the sample inventory file this is a computed variable based on the ansible_user. It assumes that it is not a root user and its home directory is `/home/{{ansible_user}}`.
1. `path`: This is to make sure that the ansible_user can access the `go` executable.
1. `node_exporter`: Default is `true`. Change it to `false` if you do not want to install node_exporter
1. `promtail`: Default is `true`. Change it to `false` if you do not want to install promtail
1. `log_monitor`: Enter your monitor server IP if you install promtail.
1. `node_name`: This is your node name for the config.toml file.
1. `log_name`: This is the server name for the promtail service.
1. `pagerduty_key`: This is the PagerDuty key if you use TenderDuty
#### Ready? Go!
One you understand the setup, please first copy it to your own inventory file so you can customize it to suit your needs:
```bash
cp inventory.sample inventory
```
When you are ready install a node, you run:
```bash
ansible-playbook main.yml -e "target=HOST_NAME"
```
## Playbooks
| Playbook | Description |
| ------------------------------ | ------------------------------------------------------------------------------------------------ |
| `main.yml` | The main playbook to set up a node |
| `prepare.yml` | Prepare the server with node exporter, promtail, go, cosmovisor, and firewall rules |
| `support_backup_node.yml` | Install snapshot, state_sync, resync, genesis and prune script on backup node |
| `support_snapshot.yml` | Install snapshot script and a cron job |
| `support_state_sync.yml` | Install state-sync script |
| `support_resync.yml` | Install weekly scheduled state-sync and recovery script |
| `support_genesis.yml` | Install a script to upload genesis |
| `support_prune.yml` | Install a script to prune using cosmprund |
| `support_public_endpoints.yml` | Set up Nginx reverse proxy for public PRC/ API |
| `support_seed.yml` | Install seed node with Tenderseed. You need a node_key.json.j2 file so the node_id is consistent |
| `support_tenderduty.yml` | Install Tenderduty |
| `support_price_feeder.yml` | Install price feeders for selected networks (such Umee, Kujira, etc) |
| `support_scripts.yml` | Install scripts to make node operations easier |
| `support_sync_snapshot.yml` | Sync node from a snapshot |
| `support_remove_node.yml` | Remove a node and clean up |
| `support_update_min_gas.yml` | Update minimum gas price |
| `support_skip_connect.yml` | Install skip connect |
### Selected playbook Usage Example
##### support_seed
```bash
ansible-playbook support_seed.yml -e "target=umee_seed [email protected]:36656"
```
##### support_tenderduty
```bash
ansible-playbook support_tenderduty.yml -e "target=juno_tenderduty key=junovalcons1qyw2x2sjp40cqasdfyuiahsdfknasdkneafs"
```
##### support_price_feeder
```bash
# When you just want to update price feed config
ansible-playbook support_price_feeder.yml -e "target=kujira_main"
# When you just want to update price feed config and service file
ansible-playbook support_price_feeder.yml -e "target=kujira_main price_feeder_password=YOUR_PASSWORD"
# When you just want to update price feed config and service file and binary
ansible-playbook support_price_feeder.yml -e "target=kujira_main price_feeder_password=YOUR_PASSWORD price_feeder_binary=true"
```
##### support_scripts
```bash
ansible-playbook support_scripts.yml -e "target=juno_main"
```
Currently, we have 4 supported scripts. Their usage is documented below using Juno as example:
```bash
./scripts/bank_balances/juno.sh
./scripts/bank_send/juno.sh ADDRESS 1000000ujuno
./scripts/distribution_withdrawal/juno.sh
./scripts/gov_vote/juno.sh 1 yes
```
## Supported Networks
See the `group_vars` folder for the list of mainnet and testnet support
## Port Prefix
All port prefixes come from this [repo](https://github.com/polkachu/cosmos-port-prefixes)
## V1 to V2 migration [OPTIONAL]
In V1, the custom port prefix is 2 digits. However, this hobby project has evolved into a more ambitious one and we have run out of the prefixes. Therefore, V2 introduces a breaking change of the 3-digit custom port prefixes.
If you have a node running based on V1 port prefix system, you do not need to do anything. However, if you are as OCD as Polkachu, you might want to migrate all the previous nodes to comply with the new system. Here is a playbook to manage the migration. You still need to close the old ports that are not longer in use, but this playbook should take care of the rest.
```bash
ansible-playbook support_config_update.yml -e "target=juno_main"
```
## Known Issue
Because this repo tries to accommodate as many Tendermint-based chains as possible, it cannot adapt to all edge cases. Here are some known issues and how to resolve them.
| Chain | Issue | Solution |
| ---------------- | -------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Axelar | Some extra lines at the end of app.toml | Delete extra lines and adjust some settings these extra lines are supposed to change |
| Canto | genesis file needs to be unwrapped from .result.genesis | Unwrap genesis with jq command |
| Injective | Some extra lines at the end of app.toml | Delete extra lines and adjust some settings these extra lines are supposed to change |
| Kichain | Some extra lines at the end of app.toml | Delete extra lines and adjust some settings these extra lines are supposed to change |
| Celestia testnet | inconsistent config.toml file variable naming convention | Manually adjust config.toml file |