BM-3029: Zeroecco/testnet down#2029
Open
zeroecco wants to merge 9 commits into
Open
Conversation
- l-prover-ansible: drop dead DeployNightly stage (no nightly group after testnet teardown), remove deleted monitoring.yml/security.yml playbook calls, fix secret-name references in docstring - INVENTORY.md: correct group -> MagicDNS host mapping (prover-staging, prover-prod) to match the real inventory - cw-monitoring: point staging/prod prover alarms at the new hosts and remove the retired nightly prover node Co-authored-by: Cursor <cursoragent@cursor.com>
zeroecco
marked this pull request as ready for review
June 2, 2026 22:31
zeroecco
requested review from
a team,
Wollac,
bobbobbio,
capossele,
jonastheis,
nahoc,
unizarr and
willemolding
as code owners
June 2, 2026 22:31
willpote
approved these changes
Jun 3, 2026
willpote
left a comment
Contributor
There was a problem hiding this comment.
Looks good aside from the toml changes which I don't fully understand, lets chat offline about it
…dless into zeroecco/testnet_down
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tears down the production testnet deployments and moves the bare-metal prover Ansible CI onto Tailscale. As part of the cleanup, host-provisioning Ansible roles that are no longer run from this repo are removed, the prover deployment pipeline is simplified, and CloudWatch alarming is repointed at the remaining prover nodes.
Changes
Prod testnet teardown
Removed Pulumi stack configs for the retired prod testnet (Sepolia 11155111 / Base Sepolia 84532) deployments across distributor, indexer, order-generator, order-stream, and slasher.
Removed the matching prod-testnet broker configs (configs/broker/prod-testnet-nightly/, prod-mainnet-nightly/).
Dropped the l-indexer pipeline and LaunchDefaultPipeline testnet wiring.
Prover Ansible CI → Tailscale
l-prover-ansible pipeline now joins the tailnet (userspace tailscaled + SOCKS5 proxy) and reaches provers over MagicDNS instead of public IPs; SSH key, inventory, and Tailscale auth key are pulled from AWS Secrets Manager.
Removed the dead DeployNightly stage and the references to the deleted monitoring.yml/security.yml playbooks; pipeline is now Source → DeployStaging → DeployProduction.
inventory.yml is no longer tracked (gitignored; real values live in Secrets Manager).
Ansible slimming
Removed awscli, docker, nvidia, ufw, and vector roles plus monitoring.yml/security.yml — hosts are now expected to be pre-provisioned (incl. metrics shipping handled outside this repo). prover.yml only runs the prover role.
Alarming
cw-monitoring staging/prod node lists repointed to the current provers (prover-staging, prover-prod) and the retired nightly prover alarm node removed.
Broker config
Staging broker tuning: max_collateral 5 → 100, peak_prove_khz 80 → 11000, added Sepolia 11155111 override; release-config example paths updated.