Infrastructure for Status fleets
https://github.com/status-im/nim-waku
87d2fc1605
The bigger table, messages, is a partitioned one where only INSERTS happens. Furthermore, there are no dead tuples there because we directly drop old partitions We may need to manually perform vacuum on other tables |
||
---|---|---|
ansible | ||
.gitignore | ||
Makefile | ||
README.md | ||
ansible.cfg | ||
flake.lock | ||
flake.nix | ||
hosts_boot.tf | ||
hosts_store.tf | ||
hosts_store_db.tf | ||
main.tf | ||
providers.tf | ||
secrets.tf | ||
versions.tf | ||
workspaces.tf |
README.md
Description
This repo defines infrastructure for running nim-waku nodes.
There are 3 kinds of nodes:
boot
- Bootstrap nodes. Nostore
protcol enabled.store
- Messages store nodes withrelay
, andstore
protocols.store-db
- PostgreSQL used bystore
nodes for envelope storage.
Discovery
DNS TXT
ENRTree records exist to discover available fleets:
enrtree://AMOJVZX4V6EXP7NTJPMAYJYST2QP6AJXYW76IU6VGJS7UVSNDYZG4@boot.prod.status.nodes.status.im
enrtree://AMOJVZX4V6EXP7NTJPMAYJYST2QP6AJXYW76IU6VGJS7UVSNDYZG4@store.prod.status.nodes.status.im
enrtree://AI4W5N5IFEUIHF5LESUAOSMV6TKWF2MB6GU2YK7PU4TYUGUNOCEPW@boot.staging.status.nodes.status.im
enrtree://AI4W5N5IFEUIHF5LESUAOSMV6TKWF2MB6GU2YK7PU4TYUGUNOCEPW@store.staging.status.nodes.status.im
Continious Integration
Jenkins CI builds can be used to build and deploy new Docker images:
status.staging
- https://ci.infra.status.im/job/nim-waku/job/deploy-status-staging/status.prod
- https://ci.infra.status.im/job/nim-waku/job/deploy-status-test/
Repo Usage
For how to use this repo read the Infra Repo Usage doc.