The document outlines a 5-step framework for automating network operations and achieving network reliability engineering (NRE). The 5 steps include: 1) device-led operations, 2) architecture-led workflows, 3) automated operations, 4) continuous processes through a CI/CD pipeline, and 5) engineering outcomes. The framework provides a roadmap for customers and helps qualify needs. Achieving NRE involves taking a developer approach to network operations through principles like automation, transparency, and continuous improvement.

1. AUTOMATION JOURNEY TO NRE
5-Step Framework

2. JUNIPER 5-STEP MODEL
Device led
Architecture led
Operations led
Business led
Customer led
Our general model for maturity, transformation and a journey to multicloud IT
All steps include aspects of:
• People, learning and culture
• Process, improvement and behaviors
• Technology, products and architecture
Progress is not a straight line:
• Includes changes on the side of vendor and customer
• May skip ahead in some ways, while others need catch-up
• Contextualized steps may evolve over time
Your present does not determine where you can go, merely where you start

3. 5-STEP VALUE
HOW IS THE 5-STEP USEFUL?
• Juniper thought leadership:
• Making the map of the journey
• Clarity
• Build rapport with customer
• Agree on direction
MAP
• Conversation starter
• Let’s find your place on the map
• Consulting value:
• Service from a state audit
• SE, PS, or channel partner led
ORIENTATION
• Sales qualification
• Check need to move forward
• Sales proposal:
• To get from here to there, you
would need …
NEXT STEP

4. AUTOMATED NETWORK OPS: 5-STEP OVERVIEW
NetOps at the device or
system UI
People are technicians not
technologists / engineers
Automate the design of ops:
workflows
Focus on frequent tasks like
troubleshooting more than
config management
Connect actions to triggers
and think in TDD terms
Rethink troubleshooting as
testing and provisioning +
actions as code to be tested
DevNetOps pipeline and
principles for agility, speed
Accuracy and feedback at
speed, small changes,
safe/canary deployments
Network reliability engineer
service-level outcomes
Plan error budgets and
objectives, use service-level
indicators, plan capacity
Manual ops
Automated workflows
Automation, tests and
networks as code
Continuous processes
on a continuous pipeline
(CI/CD/CR)
Engineering Outcomes
(NRE)
DESTINATION
People:
Network
Reliability
Engineers (NRE)
Process:
DevNetOps
And NRE’ing
Technology:
Self-Driving
Network

5. STEPS ON JOURNEY
Manual ops
Automated workflows
Automation, tests and
networks as code
Continuous processes
on a continuous pipeline
(CI/CD/CR)
Engineering Outcomes
(NRE)
Master architecture.
Document workflows.
Automate and aggregate
repetitive workflow actions,
especially troubleshooting
Trigger actions
automatically. Codify like a
developer. Think TDD and
proactive instead of reactive
troubleshooting
Automate build, testing,
deployment & response like
engineering teams. Move
quickly in small steps for
agility with accuracy. Use
machine insights in CR.
Engineering. Simplicity.
Network Reliability,
Business Agility,
Continuous Improvement,
Positive Outcomes

6. TECHNOLOGY LANDSCAPE*
+ STEP 2 + STEP 3 + STEP 4 + STEP 5STEP 1
Device CLI Product GUI
Workflow Docs
Workflow
pseudocode
Documents
Mistral
Products
Code
Markup/
Modeling
Chef
OpenConfig
NAPALM
Puppet
NETCONF
Heat
Ansible
Salt
Terraform
Helm
JET PyEZ
Junos
Scripting
git GitHub
Robot
Serverless
Prometheus
Graphana
Jenkins
Salt EDI
ELK / Elastic
ToDD
BitBucket
GitLab
StackStorm
Splunk
InfluxDB
AppFormix
Events JTI, OpenNTI Ixia
Bamboo
Jenkins
Pipelines
Travis
Open AI
GitLab Runner
Tensor Flow
Spinnaker
Build Kite
theano
Virtual labs Wistar
VividCortex
Statistica
tableau
Chaos Monkey
Netsil
Spark
Istio
Catchpoint
NetBrain
MapR
Avalanche
{_();} </>
RFC
6241
Optimizely
It’s not what you use, it’s how you use it.
*Sample only, not exhaustive

7. CONTEXTUALIZING AUTOMATION
Manual ops
Automated workflows
Automation, tests and
networks as code
Continuous processes
on a continuous pipeline
(CI/CD/CR)
Engineering Outcomes
(NRE)
IMAGINE A TRANSPARENCY OVERLAID ON TO ANOTHER 5-STEP
Example:
Overlay this 5-step onto the Data Center 5-step
AUTOMATION SOLUTIONS
• Automation solutions and NetOps is always dependent on the place in network (PIN) / network domain
• Ground conversations around culture (people), behaviors (process) and products (technologies) in a PIN

8. WHAT IS NRE
APPENDIX

9. SRE is published by Google
2016
DevOps Handbook
2015
DevOps is Coined
2009
INSPIRATION

10. DEFINING TERMS
For application development ops DevOps mentality around security ops DevOps mentality around network ops
DevOps DevSecOps DevNetOps
DevOps brings together development and operations:
- PEOPLE and cultural principles and behavior through the entire business-level service lifecycle
- PROCESSES from design to production to maintenance reliability, scale, performance, security
- TOOLS to scale architecture, automate, collaborate, measure and thus improve quality and speed
Software is crafted, built and run in the
same organization
Silos are internal to IT department
Security and networking solutions are mostly bought and assembled
Silos are vendor-customer so co-creation is required

11. DEFINING TERMS… and ROLES
For application development ops DevOps mentality around security ops DevOps mentality around network ops
DevOps DevSecOps DevNetOps
DevOps brings together development and operations:
- PEOPLE and cultural principles and behavior through the entire business-level service lifecycle
- PROCESSES from design to production to maintenance reliability, scale, performance, security
- TOOLS to scale architecture, automate, collaborate, measure and thus improve quality and speed
NRE: Network Reliability EngineerSRE: Site Reliability Engineer
(and CRE = Customer Reliability Engineer)

12. WHAT IS (an) NRE?
Defn An NRE
The professional that implements network reliability engineering
Defn NREing
Engineering an automated network to deliver measurable reliability
(SLO/SLA of MTBF, MTTR, etc.) under measureable conditions
(scale, rate of change, performance, etc.)
Defn DevNetOps
Like NRE, engineering automated network, but more explicitly says:
• Take a developer (software engineering) approach
• The application of the approach is to NetOps
• Focus on shorter cycles and lead time in code-to-prod pipeline
• Our work begins in pre-production and follows CI/CD/CR

13. WHY N- RELIABILITY -E
1. It’s not just about network automation or technology:
“Network automation does not an automated network make.”
2. Reliability must be ensured before acceleration
“It’s not how fast you drive, it’s how you drive fast”
3. Reliability forces us to automate and simplify
Encompassing NetOps goals: resiliency, security, metrics…
Higher-order DevOps principles…
1. Eliminate toil and technical debt with automation
2. Truth and transparency. Management by metrics.
3. Allow for failure; Iterate and evolve with Agile; then triangulate...
4. Continuous improvement: turn local lessons into global ones
5. Continuous learning (kaizen)

14. WHY NR - ENGINEER
1. NRE focus sidesteps DevOps vs. DevNetOps confusion
There are clear NetOps projects outside of software teams, but
some confusion on terms remains. NRE is more straightforward.
2. Engineers are builders and we build networks
Vendors cannot do this; pick-up where they leave off
3. More to it than in-production NOC dashboards
More creative, more satisfying, more money
4. By building, testing, stressing, staging what you build…
you prepare for better operations and better outcomes
5. By operating what you build…
you better understand what you’ve built