BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.balticnog.org//P9DYEB
BEGIN:VTIMEZONE
TZID:EET
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1;UNTIL=19991231T220000Z
TZNAME:EET
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:STANDARD
BEGIN:STANDARD
DTSTART:20011028T050000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:EET
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20010325T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:EEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-bnog-2026-P9DYEB@pretalx.balticnog.org
DTSTART;TZID=EET:20260923T140000
DTEND;TZID=EET:20260923T142500
DESCRIPTION:Design-driven automation treats the design of a network — its
  topology\, roles\, relationships\, and constraints — as an explicit mod
 el that exists independently of any device's running configuration. That m
 odel becomes the thing you reason about: the source of intent that configu
 ration\, validation\, and change all refer back to.\n\nThis talk looks at 
 what that means once you're operating a real network\, not sketching one. 
 We'll walk through the lifecycle: expressing intent as a design\, turning 
 it into configuration\, and (the hard part) keeping the two in agreement a
 s the network drifts\, as tickets land\, and as people make changes out-of
 -band. We'll dig into how drift is detected and interpreted\, why reconcil
 iation is harder than pushing config\, and how a design model changes the 
 way operators handle refactoring and unplanned change.\n\nThe same propert
 y that makes this work for humans\, an explicit statement of intent to che
 ck reality against\, is also what keeps the next wave of automation honest
 \, whether that's a script or something smarter. We'll touch on that\, but
  the focus stays on the mechanics operators live with today.\n\nThroughout
 \, we'll ground the concepts in real declarative provisioning systems\, in
 cluding open-source NetBox\, using them as concrete examples of the patter
 ns and trade-offs: where design-driven approaches pay off\, and where they
  still struggle in production.\n\nYou'll leave with a clear mental model o
 f design-driven automation\, a realistic view of the reconciliation proble
 m\, and a sharper sense of where these approaches earn their place in day-
 to-day operations.
DTSTAMP:20260920T210917Z
LOCATION:ROOM ALFA
SUMMARY:Keeping the Network Honest: Design Models\, Drift\, and Reconciliat
 ion - Mark Robert Coleman
URL:https://pretalx.balticnog.org/bnog-2026/talk/P9DYEB/
END:VEVENT
END:VCALENDAR
