Infrastructure for Nimbus cluster
https://nimbus.team
Jakub Sokołowski
24020d0962
We have received a complaint from InnovaHosting about them being hit by about 150 ICMP `ttl1` packets/s on their routers, causing excess CPU usage. https://client.innovahosting.net/viewticket.php?tid=532874&c=8gALx9vm By using `tcpdump` I have identified that `mtr` by default pings the target 10 times, which means that the default value of `-c`/`--report-cycles` is 10, although this is not documented in the manual. We can see this when calling `mtr github.com` and watching with `tcpdump`: ``` > sudo tcpdump -v -i eno1 icmp and src 185.181.230.78 and dst github.com | grep 'ttl 1,' tcpdump: listening on eno1, link-type EN10MB (Ethernet), snapshot length 262144 bytes 19:54:53.981243 IP (tos 0x0, ttl 1, id 37119, offset 0, flags [none], proto ICMP (1), length 64) ...(8 packets omitted)... 19:55:03.025460 IP (tos 0x0, ttl 1, id 38226, offset 0, flags [none], proto ICMP (1), length 64) ``` We don't need to run the test 10 times to get a result for our metric. Related to: https://github.com/status-im/infra-role-bootstrap-linux/commit/ea22bdfe Signed-off-by: Jakub Sokołowski <jakub@status.im> |
||
|---|---|---|
| ansible | ||
| files | ||
| scripts | ||
| .gitignore | ||
| Makefile | ||
| README.md | ||
| ansible.cfg | ||
| common.tf | ||
| dash.tf | ||
| eth1.tf | ||
| fluffy.tf | ||
| geth.tf | ||
| holesky.tf | ||
| logs.tf | ||
| main.tf | ||
| mainnet.tf | ||
| outputs.tf | ||
| prater.tf | ||
| providers.tf | ||
| secrets.tf | ||
| sepolia.tf | ||
| users.tf | ||
| variables.tf | ||
| versions.tf | ||
README.md
Description
This repo defines Nimbus cluster infrastructure.
Endpoints
These are Beacon API endpoints intended for community testing.
| Endpoint | Host |
|---|---|
| http://unstable.mainnet.beacon-api.nimbus.team/ | linux-01.ih-eu-mda1.nimbus.mainnet |
| http://testing.mainnet.beacon-api.nimbus.team/ | linux-02.ih-eu-mda1.nimbus.mainnet |
| http://unstable.prater.beacon-api.nimbus.team/ | linux-01.he-eu-hel1.nimbus.prater |
| http://testing.prater.beacon-api.nimbus.team/ | linux-02.he-eu-hel1.nimbus.prater |
| http://unstable.sepolia.beacon-api.nimbus.team/ | linux-01.he-eu-hel1.nimbus.sepolia |
These nodes have no validators attached.
There are also archives of ERA files:
| Endpoint | Host |
|---|---|
| https://mainnet.era.nimbus.team/ | linux-03.ih-eu-mda1.nimbus.mainnet |
| https://prater.era.nimbus.team/ | linux-01.ih-eu-mda1.nimbus.prater |
| https://sepolia.era.nimbus.team/ | linux-01.ih-eu-mda1.sepolia.prater |
Dashboards
There's a dedicated Kibana dashboard for Nimbus fleet logs: https://nimbus-logs.infra.status.im/
There are explorers available for various testnets:
Fleet Layouts
The fleet layout configuration used by Ansible can be found in ansible/vars/layout.
But for finding which host holds which validator use TSV files in ansible/files/layout.
Repo Usage
For how to use this repo read the Infra Repo Usage doc.