This repo is to set up the Cosmos-based node. It currently support:

• BitCanna
• Chihuahua
• Comdex
• Juno
• Kava
• KiChain
• Osmosis
• Sifchain
• Terra

You run one playbook and set up a node. For example:

ansible-playbook -i inventory juno.yml -e "target=juno_mainnet_main"

But before you rush with this easy setup, you probably want to read on so you understand the structure of this Ansible program and all the features it offers.

First, make sure that you have a production inventory file with your confidential server info. You will start by copying the sample inventory file (included in the repo). The sample file gives you a good idea on how to define the inventory.

cp inventory.sample inventory

Needless to say, you need to update the dummy values in the inventory file. For each node, you need to update the server IP, validator_name and log_name (log_name is optional if you do not install Promtail). While you are free to keep the default, you might also want to update:

1. ansible_user: The sample file assumes ubuntu, but feel free to use other user name. This user need sudo privilege.
2. 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.
3. ansible_ssh_private_key_file: The sample file assumes ~/.ssh/id_rsa, but you might have a different key location.
4. path: This is to make sure that the ansible_user can access the go executable. If your ansible_user is not ubuntu, you need to update it.
5. node_exporter: Default is true. Change it to false if you do not want to install node_exporter
6. promtail: Default is true. Change it to false if you do not want to install promtail
7. log_monitor: Enter your monitor server IP. It is most likely a private IP address if you use a firewall around your private virtual cloud (VPC). You do not need this if you do not install promtail

It is beyond the scope of this guide to help you create a sudo user, alternate ssh port, create a private key, install Ansible on your machine, etc. You can do a quick online search and find the answers. In my experience, Digital Ocean have some quality guides on these topics. Stack Overflow can help you trouble-shoot if you are stuck.

The basic cluster structure is:

1. Name each juno node as juno_mainnet_main, juno_mainnet_backup, etc. Group all Juno nodes into juno_mainnet group.
2. Name each juno node as comdex_mainnet_main, Comdex_mainnet_test, etc. Group all comdex nodes into comdex_mainnet group.
3. ...

The structure allows you to target vars to each node, or a group cluster, or the whole cluster. Make sure that you are familiar with the files in the group_vars folder. They follow this clustered structure closely.

The key Ansible playbook is <chain>.yml files. It will set up a fresh node from scratch. For example:

ansible-playbook -i inventory bitcanna.yml -e "target=bitcanna_mainnet_main"
ansible-playbook -i inventory chihuahua.yml -e "target=chihuahua_mainnet_main"
ansible-playbook -i inventory comdex.yml -e "target=comdex_mainnet_main"
ansible-playbook -i inventory juno.yml -e "target=juno_mainnet_main"
ansible-playbook -i inventory kava.yml -e "target=kava_mainnet_main"
ansible-playbook -i inventory kichain.yml -e "target=kichain_mainnet_main"
ansible-playbook -i inventory osmosis.yml -e "target=osmosis_mainnet_main"
ansible-playbook -i inventory sifchain.yml -e "target=sifchain_betanet_main"
ansible-playbook -i inventory terra.yml -e "target=terra_mainnet_main"

If you prefer to install the node manually, you can run a 'prepare' playbook to set up a server for a cosmos-based chain without installing the node itself.

Playbooks are:

When you install a node that has upgrades in the past, you can either sync from Block 1, or use a snapshot to time-travel to the present quickly. We strongly recommend using snapshots. It will save you time of syncing and debugging. Here are a list of trusted snapshot providers. Do your own research and make sure that you can trust the snapshot providers:

Kava: Snapshot is here

KiChain: Follow instruction here. In fact, we cannot make it work with the peers listed when we tried to sync from Block 1. The only way we made it work is by syncing with the snapshot from the included link.

Osmosis: Snapshot is here

Sifchain: Follow instruction here

General

Terra, Injective, Celestia

Validator Server Migration Best Practice