Moderator: Jeff Doyle, Juniper Networks Speakers: Chris Cummings, ESnet Dan Kelcher, IP Fabric Jeff Kala, Network to Code

1. Mini-Track:
Challenges to Network
Automation Adoption
Jeff Doyle, Chris Cummings,
Dan Kelcher, Jeff Kala

2. Your logo
here
Challenges to Network
Automation Adoption
Jeff Kala - Sr. Architect

3. Automation Adoption Challenges
Tool sprawl
Lack of ROI
concentration
Lack of automation
architecture
Documentation
challenges
Orchestration is
not automation
“Legacy” Network
Devices
Building automation
for the wrong
audience.
It’s a whole new
career
Culture Change
is Hard
Lack of organization
commitment
The Data Problem
Network configs vs
service
definitions
Network Automation
Testing
The Outage
Paradox
And the list continues...

4. Is the value there?
Network Automation Testing
Beyond the
testing, features
to consider
Features missed
by testing
Testing
Challenges
• Standardized
configurations
• Operational state
alignment with
configuration
• Hardware testing
• Load testing
• End to End testing
• You can’t manage the whole
network
• Device mapping is not 1 to 1
• Emulated external connections
is challenging

5. The Data Problem
“Data is the new gold” is true in network
automation too.
Configuration
Data
Provide “lite”
features & inflexible
Vendor or device
type specific
Require additional HW
State Data
Created and maintained
in silo by individual
Lack scalability
and variable
inputs
Break with network
and device
modifications
Governance
Limited to vendor or
network domain
Fixed GUI and
Configurations
Feature Dependent on
SW release cycles

6. The Outage Paradox
● Automation will break my network “faster”
● Automation will cause larger outages
● Lack of trust in an automated workflow
● The fear of the unknown
Learn from your mistakes: https://engineering.fb.com/2021/10/05/networking-
traffic/outage-details/

7. Your logo
here
Challenges to Network
Automation Adoption
Knowing is half the battle
Dan Kelcher - Solution Architect @ IP Fabric

8. What is Automation?

9. Websters Defines Automation As…
Just kidding.

10. Let’s try some automation!
Directions:
Go Forward
Turn Right
Continue Straight
Take a Slight Left
Continue Straight
Turn Right
Turn Right Again
Stop
Verification:
Did you
Go Forward?
Turn Right?
Continue Straight?
Take a Slight Left?
Continue Straight?
Turn Right?
Turn Right Again?
Stop?

11. Where Are You?
Did You Reach the
Destination?

12. Networking Example
Run this command:
switchport trunk allow vlan 25
Verify it was implemented:
show run interface gi0/1
Did it have the intended result?

13. Closed-loop
Automation
State: What is
currently True
-Collected from
devices
Intent: What should
be True
-Collected from
design documents
Assurance: Does
State = Intent?

14. Your logo
here
Challenges to Network
Automation Adoption
Chris Cummings
Full Stack Network Automation Software Engineer
Energy Sciences Network (ESnet)
Lawrence Berkeley National Laboratory
U.S. Department of Energy

15. Overview
● Automation != Orchestration
● Organizational Vision Matters
● Defining Services is hard.
● How to Do An Orchestration

16. Automation
The automatic operation or
control of equipment, a
process, or a system. This
often encompasses a linear
process.
Orchestration
The execution of
(multiple) automations
to achieve the desired
state of a process or
system.

17. Organizational Vision Matters
● Is Automation/Orchestration viewed as a cost center?
● What is the benefit?
● Who can drive this initiative?
● We’re gonna need a bigger team…

18. Defining Services is Hard
● What are our services we offer?
● What is required to deliver those services?
● Who is responsible for delivering those services?
● What is the lifecycle of this service?

19. How to Do An Orchestration
● Have strong organizational alignment
● Define your services
● Understand your service owners
● Have an army of good people

20. Your logo
here
Challenges to
Automation Adoption
Jeff Doyle
Director, Solutions Architecture
Juniper Apstra
™

21. Definitions!
What are we automating?
How are we automating it?
What are the expected results?
What is my SSoT?

22. Indecision…
COTS vs DIY
○ DIY: Low CapEx vs High OpEx
○ COTS: High CapEx vs Low OpEx
○ DIY: Custom built for my environment
○ COTS: Built for a wide range of users
○ DIY: Long development, necessary maintenance
○ COTS: Quick rollout, regular updates

23. Indecision…
Where to start? At what scale?
○ Automate Everything vs a few simple
scripts
What is the business case?

24. Indecision…
What skillsets do I need?
AI/ML is rapidly evolving
○ What if I jump in too early? Too late?

25. FEAR!!!
Losing visibility into my network
Losing control of my network
Automating a broken process

26. Panel Discussion

27. Thank You!