-
Notifications
You must be signed in to change notification settings - Fork 735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting up a private network #95
Comments
According to this guide https://tendermint.com/docs/networks/terraform-and-ansible.html#ansible I do need to edit the config.toml or apply a |
This repository allows you to run a local network of 4 nodes via |
I've gotten something working by crawling the nodes and then using the |
Following up on this, are there any open source examples of peoples infrastructure? Many things are missing in this repo which makes me think the problems we're solving wrt. infrastructure are being done by everyone. In particular would be great to get some conversation going around setting up a sentry node architecture with multiple validator nodes and some kind of cloud KMS in place. |
Documentation does exist. I recommend taking a look at various validator's blogs/posts on their infra (e.g https://iqlusion.blog/a-look-inside-our-validator-architecture). |
You can also get more information at: https://forum.cosmos.network/t/sentry-node-architecture-overview/454 Presently (I just checked again), Google, Amazon and Azure KMS still do not support Ed25519. So there is no cloud KMS yet for Cosmos. You'd have to go with the YubiHSM. |
To me it doesn't look like this repository sets up a proper network. In the
/network
folder I see all the ansible and terraform work that has been done but from what I can see the nodes will never connect to each other.So I run
make validators-start
ormake fullnodes-start
with the configured number of servers per az (availability zone) and number of az's... let's pretend two az's and one server in each.How do these servers know about each other? I can't see anything editing the
persistent_peers
entry in theconfig.toml
file.The text was updated successfully, but these errors were encountered: