Skip to main content

Lodestar

Background​

The Infrastructure team supports the Lodestar client team by provisioning and managing servers for their various use cases, this includes a development and production environment. Lodestar devs follow a metrics-based development process. They rely heavily on metrics collected in the dev environment to make the next release decision.

Repository Structure​

The Lodestar infrastructure is managed across multiple repositories:

Development Environment​

  • Repository: lodestar-ansible-development
  • Purpose: Development and testing infrastructure for Lodestar DevOps team
  • Location: Managed from the lodestar-ansible-develop directory structure

Production Environment​

  • Repository: lodestar-ansible-production
  • Purpose: Production Lodestar infrastructure including the Lido fleet
  • Location: Managed from the prod folder
  • Note: The production repository is linked as a submodule to the development repository to share common Ansible roles and prevent duplication

Lido Fleet Management​

The production repository (lodestar-ansible-production) includes our Lido validator fleet management. This includes:

  • Lido mainnet validator nodes
  • Lido validator ejector services
  • Production beacon and validator infrastructure for Lido

Note: The production repository structure uses submodules and symlinks to share common directories and Ansible roles between development and production environments.

On-call Runbook​

All alerts and resolution steps are documented here.