Jakub Sokołowski 13fa6ea608
get-geth-api-urls: allow specifying multiple fleets
More useful than specifying multiple servicer names.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-01-09 11:10:44 +01:00
2023-07-06 14:41:51 +02:00
2023-07-06 15:00:07 +02:00
2022-08-08 10:31:37 +02:00
2023-10-02 13:42:51 +02:00
2022-05-24 18:21:09 +02:00

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.ih-eu-mda1.nimbus.prater
http://testing.prater.beacon-api.nimbus.team/ linux-02.he-eu-hel1.nimbus.prater
http://unstable.sepolia.beacon-api.nimbus.team/ linux-02.ih-eu-mda1.nimbus.prater
http://testing.holesky.beacon-api.nimbus.team/ geth-01.ih-eu-mda1.nimbus.holesky
http://unstable.holesky.beacon-api.nimbus.team/ geth-02.ih-eu-mda1.nimbus.holesky

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.

Description
Infrastructure for Nimbus cluster
https://nimbus.team
Readme
Languages
Python 58.6%
HCL 26.7%
Shell 7.4%
Makefile 3.6%
Jinja 1.9%
Other 1.8%