Inside The AI Stack

Operations

Runbooks

A runbook is not a tutorial. It is written for someone who has been woken up, is under time pressure, and needs to know what is safe to do next. Every runbook here follows the same structure so you always know where to look.

Every runbook has the same thirteen sections

Consistent structure matters more than prose quality here. Under pressure you should be able to jump straight to Rollback without reading anything above it.

We do not mass-generate runbooks. Each one is written against a failure we have actually reasoned through, and each states plainly whether the procedure was executed in a test environment or reviewed without being run.

  1. 01Purpose and when to use it
  2. 02Impact and blast radius
  3. 03Preconditions
  4. 04Symptoms that lead here
  5. 05Safety considerations
  6. 06Initial checks
  7. 07Decision tree
  8. 08Diagnosis
  9. 09Remediation
  10. 10Validation
  11. 11Rollback
  12. 12Escalation
  13. 13References and last verified date

Runbooks

OpenStack

Cinder — No Valid Backend

Diagnose and remediate OpenStack volume creation failures caused by the scheduler having no candidate backends, including the case where the API reports healthy.

expert· 20 minOpenStackCinder

Runbooks

Kubernetes

CrashLoopBackOff Triage

A structured procedure for a pod that will not stay running, covering exit-code classification, probe-induced restarts, OOM kills, and validation that the fix held.

intermediate· 15 minKubernetes

Runbooks

Linux

Linux Disk Pressure Response

Find what is consuming a full filesystem, reclaim space safely including the deleted-but-open-file case, and validate before the host causes wider failures.

intermediate· 15 minLinuxKubernetes

Newsletter

Inside The AI Stack Brief

A practical weekly briefing on AI engineering, infrastructure, production operations, and the technologies powering the AI stack.

One email a week. No sponsorship placements inside the technical sections. Unsubscribe in one click.