BRKNMS-2945-Succeeding With Network Automation Using Cisco NSO

#CLUS
Succeeding with
network automation
Using Cisco NSO
Fredrik Swahn, NSO Business Unit

BRKNMS-2945
#CLUS
The reason to why we are here today
“We understand that you know more than you

share, please tell us what you think we should do!”
Customers during NSO Developer days, June 2018
#CLUS BRKNMS-2945 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
10 2
years hours
The Cisco Network Automation Delivery Model
Getting started Build automation practice
Define Demonstrate Deploy Expand Operationalize Run
The chronological perspective
Time
The topic perspective
Roles Vision, mission and culture statement Objectives, strategy and plan
Key Performance Indicators Development process Build an organization
Stakeholder management Define a use case Deployment
Continuous integration & Continuous delivery Testing Demo
Goals for this session
• What you need to do in order to take the next step in your automation
journey
• What Cisco thinks is important when it comes to be successful with

network automation powered by NSO
• What The Cisco Network Automation Delivery Model is and how it can
support your automation journey
Who would care
• If you consider introducing network automation in your organization
• If you are already part of a network automation team

• Project leads
• Automation directors/managers
• Program managers
• Executives
• Technical leads
Another view on who would benefit from this
presentation and the delivery model (NADM)
Navigates
High Good reference
organization
Software
maturity
Navigates
Low Sweet spot
competence
Low High
Organizational readiness
Depending on where in your journey you are,
different steps might be more interesting
Agenda
• Two major success factors to consider when implementing NSO
• Building a network automation capability
• The Cisco Network Automation Delivery Model
• Conclusion and Q&A
Agenda
• Define automation objective and strategy
• The power of an early win
Agenda
• Build a team
• Competence
• Sponsorship
• Organizational mindset
Agenda
Agenda
And talking about Q&A
I suggest that we take quick questions along the presentation and more
sophisticated questions between topics
You can also submit questions via Webex teams chat
Cisco Webex Teams
Questions?
Use Cisco Webex Teams to chat
with the speaker after the session
How
1 Find this session in the Cisco Live Mobile App
2 Click “Join the Discussion”
3 Install Webex Teams or go directly to the team space
4 Enter messages/questions in the team space
Webex Teams will be moderated cs.co/ciscolivebot# BRKNMS-2945

by the speaker until June 16, 2019.
#CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
Agenda
Begin to look at your self - what do you want to
accomplish with your network automation?
“Direction” “Objectives” “How” “Actions”

Objective A
Vision Objective B Strategy Plan
Objective C
The long term The vision The approach The short term
vision with broken down for how to reach plan with actions
network into reachable the objectives and activities to
automation objectives reach the
objectives
The vision is pointing out a direction for the team
“Direction” Example
Vision “No manual steps in our network operations”
The long term

vision with
network
automation
The objective(s) create clarity for the team
“Objectives” Example
Objective A • Increase quality of network
Objective B • Decrease time to spin up new devices
Objective C • Decrease number of manual steps in maintenance
processes
The vision
broken down • Free-up valuable resources
into reachable
objectives • Reduce cost for maintaining the network
• Decrease to provision new services
How do you plan to deliver on your objectives?
“How” We see three main types of NSO approaches:
Cisco (or someone else) does the implementation for you

Strategy
Cisco assists with competence and some resources

The approach
for how to reach
the objectives
You do it all by your self
To make it easier to talk about, we use an
analogy from cooking
Cisco restaurant
Cookalong with Cisco
Learn how to cook by your self
The engagement levels differs depending on
what delivery approach you chose
Cisco restaurant
The “Cisco restaurant” approach
Illustrative
Engagement level
Cisco (CX)
Customer
Cisco (Technical Support)
Time
The “Cookalong with Cisco” approach
Illustrative
Engagement level
Cisco (CX) Customer
Time
The “Learn how to cook by yourself” approach
Illustrative
Engagement level
Customer
Time
And of course, one can move between delivery
approaches along the automation journey
Learn how to cook by yourself
Learn how to cook by yourself
Time
We have seen the following pros and cons with
respective delivery approach
Cisco restaurant • Limited involvement needed from

customer
• Experienced Cisco consultants set
Cookalong with Cisco up the necessary environments and
implements the agreed use cases
• Limited learning experience from a
customer perspective
Cisco restaurant • Extensive learning experience from

a customer perspective
• Cisco knowledge shares
Cookalong with Cisco experience in a structured way
• Successive and controlled shift of
ownership to customer
Cisco restaurant • Usually a tough start to do it on

your own
• Steep learning curve
• Clear customer ownership from
start
Learn how to cook by your self • No advisory support from Cisco
Make sure to understand the expectations
REFLECTION
Before taking the first step into the journey of network

automation – make sure to both understand and align
expectations and engagement levels
Agenda
An early win increases chances for future wins
THE EARLY WIN
“Getting a small, minimum and viable use case into production quickly”
Why is it so powerful with an early win?
• Shows the rest of the organization that the technology works and that
you are a capable team
• Creates a winning theme for the team – a can do attitude!
• You will learn a lot and can reuse that knowledge for future use cases
• You have created something that actually is in production – Value!
What struggling customers end up doing
• Aim for a big and complex use case which often leads to
• limited to no value realized for a long time period
• many (and unnecessary) stakeholders involved
• internal resistance and trust issues – “does the technology really
work?”
• Began network automation initiative without enough sponsorship
• Have not involved the right competence from start
What is at stake?
Time.The investment.
The entire network automation initiative.
What we believe you should focus on
1. Let a small team with a mix of software and network competence

choose a small, minimum and viable use case and get it into
production quickly
2. Secure sponsorship and clear sign off on the chosen use case
3. Involve stakeholders and proactively manage their expectations
Creating an early win has proven to be very
successful for future progress
REFLECTION
“Understanding and having the right prerequisites to create

an early win should be focus for the first set of people
involved in the automation initiative”
Let us have a look at the model again
Start to build capability and learn from first
deployment
Getting started
Form an Automation Core Team and let them define and decide the
Define
initial scope
Show how it works and what to expect – make sure stakeholders see
Demonstrate
the demo
Focusing on deploying one minimum and viable use case fast has
Deploy
proven to be successful
Summary so far
• Set clear objectives
• Align strategy and expectations
• Take a small, minimum and viable use case and get it into production
Agenda
We have identified four other areas to highlight
when building a new capability
Build a team Competence
Sponsorship Organizational
Mindsetmindset
Building a strong team from start is a great
investment for both short and long term
Automation Core Team
We suggest you focus on a small team with both network and

software competence
The Automation Core Team is the core which
your team will build upon and grow from
Automation Core Team

Responsible for the architecture of the network service automation
Service architect system. Designs and implements the network automation system.
Develops code and works on troubleshooting
Design of network services. Prepares the design documents and makes

Network architect decisions on how to utilize the network technology. Works on the
network. Creates configuration templates, does troubleshooting
Responsible for the product backlog and its prioritization. The product
Product owner owner is also accountable for the entire development process
Take what you learned and expand it in a
structured way
Automation
group
ACT
Automation group
Automation Program
Business analyst
director manager
Team A Team B Team N

Automation Core
Network Network Network

Service architect engineer engineer engineer
Service Service Service

Team
Network developer developer developer

architect
DevOps engineer DevOps engineer DevOps engineer

Product owner
Tester Tester Tester
Team lead Team lead Team lead
Get the right people from start
Opportunities What is at stake
• Get a strong team from start that

takes and feels ownership
• The first weeks, months and years
of your automation journey
• Gather the right competence in one
team with the right decision power
Competence
Sponsorship Organizational mindset
Let us begin to define “competence”
Knowledge
+
Skills = Competence
+
Behavior
The Automation Core Team and Automation
Group need knowledge within various areas
• Networking
Knowledge
• Programming
• NETCONF / YANG
• Modelling
Skills
• Deployment
• Development tools (git)
• Test tools
• Processes
• NSO
In order to be more specific, we have expressed
expected proficiency levels per skill
Networking Programming Deployment NSO
Service
Basic Expert Basic Expert
developer
Network
Expert Basic Basic Intermediate
architect
DevOps
Intermediate Expert Expert Basic
engineer
The right behavior will make a significant
difference
• Collaborative
Behavior
• Reflecting
• Stakeholder friendly
• Integrates new competence and team
members
• Taking ownership for the holistic view
• Supportive
• Willing to understand others’
perspectives
The right behavior together the right skills is
essential
• Form an Automation Core Team with both network and software

skills and experience (and will-power)
• Involve engaged and inclusive people in your teams – a lot of work

will be to collaborate and involve stakeholders
• Understand the entire chain of events
The right competence will create opportunities
• Engage people with the right skills,

knowledge and behavior • Involving people with insufficient
competence in critical decisions
• Understand what competencies you
might lack and act upon it
Sponsorship
Risk when not having clear top management
sponsorship and support
Customer case – the challenging chain of events
Cause for automation Isolated support Siloed priorities
Interest conflicts No collaboration Focus on defending
Sponsorship is a prerequisite for any project in
any organization – same applies here!
Customer case – the positive chain of events
Cause for automation Management support Clear priorities
Internal commitment Collaboration Focus on succeeding
The right sponsorship can enable far more than a
simple “project approval”
• Right sponsorship enables a flying

start with the automation initiative • Automation initiative risk to create a
siloed organization
• Make groups work towards the
same goals • Frustration within the organization
• Have more fun!
• Unclarity
• Build strong positive culture
Many groups need to be involved
Executive
management
IT operations
Network Automation
operations group Support
ACT
Business
product
owners Marketing
Commitment levels per group
Executive
management
Commitment
Network
operations
Business
product Acceptance
owners
Support IT operations
Marketing
Understanding
Awareness
Without the organizational mindset the
automation effort risk to be isolated
What to strive for What to avoid
• Network automation is on • Old routines and mindset

stakeholders’ agendas blocking the automation potential
• Automation is an integrated • Having the automation team seen

capability in the larger as a separate unit doing
organization something on their own
• Think automation from start • Automating the old manual steps
Changing the mindset can change the culture
• Even larger potential of network

automation if more people know
about it
• Risking the automation team to get
siloed and untapped potential get
• The cause to automate can bring
stuck
groups closer – tighter collaboration
• A supporting culture
Let us summarize
Automation
Build aCore
teamTeam Competence
Behavior
Integrate automation into the

Create focus
Sponsorship
on succeeding Organizational mindset
larger organization
Let us have a look at the model again
We have sort of covered the two phases by now
Build automation practice
Expand Take what you learned and expand it in a structured way
Operationalize Establish new processes and ways of working
Run Integrate network automation into the organization
Agenda
Before we get into the demo, let’s talk a bit about
what value we see NADM creates
First use case automated

Expected value curve
Value proposition in the Getting started phase
Getting started
Define General automation knowledge increased
Stakeholder Mind shift towards Increased organizational

Demonstrate
awareness created automation begun readiness for automation
First small MVP use

Deploy Positive momentum built
case in production
Value proposition in the phase of Build
automation practice
Build automation practice
Additional MVPs in production Increased capability for automating

Expand
delivering incremental value more sophisticated MVPs
Predictable, repeated Automation mindset part of

Operationalize
success at scale organizational DNA
Run Continuous return on the investment
We are finally here – Demo time!
Let us have a look at what NADM looks like on Devnet
https://testing-developer.cisco.com/pubhub/docs/1957/new/#!nadm
Agenda
Our conclusion in one sentence
Start small, and incrementally learn, deliver value and grow
Our conclusion in three more sentences
Focus on getting one small, minimum and viable use case into
production quickly
Form a team with a mix of network and software competence from

start and give them accountability
Make sure to have a clear direction, objectives and strategy that

your team is committed to
I have told you about…
• Automation objective and strategy

• Building a new capability
….and showed you our Network Automation Delivery Model
Now, do you have any questions for me?
I have some questions for you
• Are you more comfortable about what steps you need to do in your
automation journey?
• Do you have a better view of what Cisco thinks is important to consider

when it comes to network automation?
• Do you know what The Cisco Network Automation Delivery Model is and
how it can support your automation journey?
If you want to hear this presentation again and
much, much more…and technical topics
Come join us during The NSO Developer Days in Stockholm next week
Join the NSO Community – NSO Developer hub
My contacts
Fredrik Swahn
fswahn@cisco.com
Complete your
online session • Please complete your session survey
evaluation after each session. Your feedback
is very important.
• Complete a minimum of 4 session
surveys and the Overall Conference
survey (starting on Thursday) to
receive your Cisco Live water bottle.
• All surveys can be taken in the Cisco Live
Mobile App or by logging in to the Session
Catalog on ciscolive.cisco.com/us.
Cisco Live sessions will be available for viewing
on demand after the event at ciscolive.cisco.com.
Continue your education
Demos in the
Walk-in labs
Cisco campus
Meet the engineer

Related sessions
1:1 meetings
Thank you
#CLUS
#CLUS

BRKNMS-2945-Succeeding With Network Automation Using Cisco NSO

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BRKNMS-2945-Succeeding With Network Automation Using Cisco NSO

Hochgeladen von

Copyright:

Verfügbare Formate

#CLUS

Fredrik Swahn, NSO Business Unit

“We understand that you know more than you

Customers during NSO Developer days, June 2018

Getting started Build automation practice

Define Demonstrate Deploy Expand Operationalize Run

Define Demonstrate Deploy Expand Operationalize Run

Key Performance Indicators Development process Build an organization

Stakeholder management Define a use case Deployment

Continuous integration & Continuous delivery Testing Demo

• What Cisco thinks is important when it comes to be successful with

• If you consider introducing network automation in your organization

• If you are already part of a network automation team

Getting started Build automation practice

Define Demonstrate Deploy Expand Operationalize Run

You can also submit questions via Webex teams chat

Webex Teams will be moderated cs.co/ciscolivebot# BRKNMS-2945

“Direction” “Objectives” “How” “Actions”

Vision Objective B Strategy Plan

Vision “No manual steps in our network operations”

The long term

“How” We see three main types of NSO approaches:

Cisco (or someone else) does the implementation for you

Cisco assists with competence and some resources

Cookalong with Cisco

Learn how to cook by your self

Cookalong with Cisco

Learn how to cook by your self

Cisco (CX) Customer

Cisco (Technical Support)

Cisco (Technical Support)

Learn how to cook by yourself

Learn how to cook by yourself

Cookalong with Cisco

Cisco restaurant • Limited involvement needed from

Cisco restaurant • Extensive learning experience from

Cisco restaurant • Usually a tough start to do it on

Before taking the first step into the journey of network

THE EARLY WIN

• Creates a winning theme for the team – a can do attitude!

• You have created something that actually is in production – Value!

1. Let a small team with a mix of software and network competence

3. Involve stakeholders and proactively manage their expectations

“Understanding and having the right prerequisites to create

Getting started Build automation practice

Define Demonstrate Deploy Expand Operationalize Run

• Set clear objectives

• Align strategy and expectations

Build a team Competence

Automation Core Team

We suggest you focus on a small team with both network and

Automation Core Team

Design of network services. Prepares the design documents and makes

Team A Team B Team N

Network Network Network

Service Service Service

Network developer developer developer

DevOps engineer DevOps engineer DevOps engineer

Tester Tester Tester

Team lead Team lead Team lead

Opportunities What is at stake

• Get a strong team from start that

Build a team Competence