Skip to content

Infrastructure for Nimbus cluster

Notifications You must be signed in to change notification settings

status-im/infra-nimbus

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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/ geth-01.ih-eu-mda1.nimbus.mainnet
http://testing.mainnet.beacon-api.nimbus.team/ geth-02.ih-eu-mda1.nimbus.mainnet
http://unstable.sepolia.beacon-api.nimbus.team/ linux-01.ih-eu-mda1.nimbus.sepolia
http://unstable.holesky.beacon-api.nimbus.team/ geth-01.ih-eu-mda1.nimbus.holesky
http://testing.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/ erigon-01.ih-eu-mda1.nimbus.mainnet
https://mainnet.era1.nimbus.team/ nec-01.ih-eu-mda1.nimbus.mainnet
https://sepolia.era.nimbus.team/ linux-01.ih-eu-mda1.nimbus.sepolia
https://sepolia.era1.nimbus.team/ linux-01.ih-eu-mda1.nimbus.sepolia
https://holesky.era.nimbus.team/ geth-01.ih-eu-mda1.nimbus.holesky

Dashboards

The fleet catalog can be seen at: https://fleets.nimbus.team/

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.

Bootstrap Nodes

Some nodes in this repo are used as bootstrap nodes for testnets and mainnet.

Currently this includes:

Host IP
bootstrap-01.aws-eu-central-1a.nimbus.mainnet 3.120.104.18
bootstrap-02.aws-eu-central-1a.nimbus.mainnet 3.64.117.223

They are recorded in the eth2-networks repository.

Repo Usage

Simplest way to run commands on fleets if you have SSH access:

 > ./foreach.sh nimbus-mainnet-small "sudo systemctl --no-block restart 'build-beacon-node-*'"
stable-small-01.aws-eu-central-1a.nimbus.mainnet
stable-small-02.aws-eu-central-1a.nimbus.mainnet

For more details read the Infra Repo Usage doc.