~/talk

CAPA: An Architecture For Operating Cluster Networks With High Availability

links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
name:Joon Ong
links:none on file
links:none on file
name:Amr Sabaa
links:none on file
links:none on file
links:none on file
links:none on file
links:none on file
linkedin:vahdat
slides:none on file

Google describes CAPA as a three‑layer architecture that funnels all management changes through a thin regulation funnel that enforces best practices such as two rate‑control policies, continuous data‑plane health monitoring, and a rollback path. It adds concrete fixes like BGP fail-static to avoid control‑plane withdrawals. Case studies and postmortem reanalysis claim CAPA could have prevented ~84% of past management‑induced incidents and coincide with an 82% reduction in cumulative incident duration normalized to fleet size over five years.

AI-written summary · about

  1. 0:00CAPA introduction
  2. 1:41Network management outages
  3. 3:28Network best practices challenges
  4. 5:15CAPA enforces safety
  5. 7:45Failure domains isolation
  6. 9:09Rate control for workflows
  7. 11:16Safety versus velocity
  8. 12:21CAPA’s impact on outages
  9. 14:26Success stories
  10. 15:50Summary & Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.