Admin Readiness Path

Three checkpoints before we hand over rack keys

This path is not a secret shortcut—it is the same checklist mentors use when a new hire joins a classroom pod. Work through it with your manager so expectations stay grounded.

Host setup

Verify BIOS time sources, serial labels, and out-of-band paths before touching OS configuration. We require a photo of the asset tag beside your written IP plan—boring, and it prevents swapped cables during week two.

  • Serial console path tested from two networks
  • DNS forwarders documented with rollback
  • Disk layout screenshot archived
Overhead view of color-coded server trays in a training rack

User controls

Map sudo fragments to teams instead of individuals. Practice revoking keys with a calendar reminder, not a sticky note. If your org still shares root passwords, we pause enrollment until a break-glass process exists—even a modest one.

Uptime checks

Build three signals: synthetic, log-derived, and human spot checks. We supply a starter Prometheus snippet, but the readiness path only passes when you can explain each alert to a non-technical coordinator without jargon.

Visual schema

Host setup feeds user controls then uptime checks Host setup User controls Uptime checks Evidence packet archived before rack week