Closing Remarks

on YouTube ↗06m

" summary

Emphasizes that teams document manual workflows before automating, because common processes hide 20–30 decision points that break naive scripts; recommends treating security policies as explicit, testable steps. Advocates DevOps practices: code, version control, and combining off‑the‑shelf tools with customization to actually deploy solutions. Stresses testing like full‑mesh validation to catch forgotten commands and using git‑backed sources of truth or per‑domain authoritative stores rather than ad hoc device edits.

AI-written summary · about

" related talks

• 32mKeys to Success for Enterprise Network AutomationJason Edelman · Network Automation Summit at Interop 2020
• 31mEnterprise Transformation With Network Automation PanelJay Moran, Troy Whitney, Aryo Kresnadi, Matt Elphick · Network Automation Summit at Interop 2020
• 31mWelcome & State of Network AutomationJason Edelman · Network Automation Summit at Interop 2020
• 10mKeynote: Make Infrastructure Relevant to A Better FutureBill Ren · Open Networking Summit North America 2018
• 31mNetwork Automation Architecture: Platform vs Power ToolsDamien Garros · Network Automation Summit at Interop 2020
• 15mKeynote: Scaling DevOps – Moving from Mechanization to AutomationAmy Wheelus · Open Networking Summit Europe 2019
• 25mNetwork Automation Tools & TechnologyCristian Sirbu · Network Automation Summit at Interop 2020
• 52mThe role of the Network Engineer in the DevOps eraChristian Adell Querol · DevOps Barcelona Conference 2022