Full Site Rebuild: Project Plan #

End-to-end rebuild of the mobile site from scratch. Validates air-gap recovery capability and exercises all automation built across the Builder, Patch Automation, and Extended Management Plane projects.

Roadmap item: Full Site Rebuild

Legend: ✅ Complete | 🔄 In Progress | ⏳ Planned

Project Vision & Scope #

Perform a complete tear-down and rebuild of the mobile (mobile) site to validate that the infrastructure-as-code automation is truly end-to-end. This is the capstone event that proves the system works.

In Scope

• Full substrate rebuild (builder, core router, switch, AP, hypervisors)
• Timing and gap collection during rebuild
• Iterative fixes until all steps are accounted for
• Coordinated release tagging across all deevnet repos

Prerequisites

• Builder & Core Services — ✅ Complete
• Patch Automation — firmware and automation improvements applied
• Extended Management Plane — management services deployable

Full Site Rebuild Event ⏳ #

• ⏳ Read and analyze the build/recovery plan
• ⏳ Rebuild the builder node (no version bump)
• ⏳ Rebuild core services (core router, access switch, AP) — collect timings, findings, and identify gaps
• ⏳ Rebuild management plane (Proxmox, extended services)
• ⏳ Bring tenants back: re-admit each tenant, each applies from its repository and pushes its application again; record what each tenant had to do
• ⏳ Apply fixes and iterate until all steps are accounted for
• ⏳ Tag all deevnet repos with a coordinated release version

Scheduled Rebuilds ⏳ #

Resiliency requires the Builder and every management-hypervisor VM to be rebuilt once per Fedora release.

• ⏳ Run the first scheduled round, each rebuild as a change record, and fold every unrecorded step back into the runbook