Scribd
Upload
416 views13 pages

Automating Network With Ansible and Cisco NSO: Enable Continuous Integration and Deployment With Devops Approach

(1) Ansible and Cisco NSO enable continuous integration and deployment with a DevOps approach for automating networks. (2) Red Hat Ansible Tower scales and operationalizes Ansible automation while Cisco NSO provides model-driven service orchestration across hybrid networks. (3) Together, Ansible and Cisco NSO allow application-centric services to leverage the full value of the network through playbook-driven automation and model-based configuration.

Uploaded by

Balan Wv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
416 views13 pages

Automating Network With Ansible and Cisco NSO: Enable Continuous Integration and Deployment With Devops Approach

(1) Ansible and Cisco NSO enable continuous integration and deployment with a DevOps approach for automating networks. (2) Red Hat Ansible Tower scales and operationalizes Ansible automation while Cisco NSO provides model-driven service orchestration across hybrid networks. (3) Together, Ansible and Cisco NSO allow application-centric services to leverage the full value of the network through playbook-driven automation and model-based configuration.

Uploaded by

Balan Wv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Automating Network with Ansible and

Cisco NSO
Enable Continuous Integration and Deployment with Devops Approach
RED HAT ANSIBLE TOWER
Scale + operationalize your automation

CONTROL KNOWLEDGE DELEGATION

RED HAT ANSIBLE ENGINE


Support for your Ansible automation

SIMPLE POWERFUL AGENTLESS

FUELED BY AN INNOVATIVE OPEN SOURCE COMMUNITY


Cisco NSO – The Network API
Automation Network
Frameworks Engineers • No hard-coded assumptions
about:
Northbound: REST, NETCONF, JSON-RPC, Java, Python, Erlang, CLI, Web UI • Network services
• Network architecture
• Network devices
Cisco NSO • YANG-based data store driving
the north- and southbound
interfaces
Southbound: 70+ vendors across physical and virtual networks
• Southbound multi-protocol
CPE
CPE Metro and Access WAN Data Center support including NETCONF,
REST, CLI, SNMP
• Massively scalable architecture
deployed in networks with 100k+
devices
From Devices (ConfD)…
CLI SNMP NETCONF REST Challenges:
• Many different APIs and interfaces to
ConfD the north
• Heterogenous environment to
Data
Data the south
Models
Models CDB • One operation may lead to
many activities

Subscription-based APIs Solution includes:


A Mess (OS, Apps) • APIs and interfaces driven
by models
• Transaction-engine with
flexible rollback
Cisco NSO
Network Engineering Ops and Provisioning Service Developers • Model-driven end-to-end service
lifecycle and customer experience
in focus
NSO
• Seamless integration
Service Manager with existing and future OSS/BSS
Package environment
CDB Manager
Device Manager • Loosely-coupled and modular
architecture leveraging open APIs
Device Abstraction ESC (VNFM) and standard protocols
• Orchestration across
VNF Lifecycle VNF Service
NED NED NED multi-domain and multi-layer for
Manager Monitoring
centralized policy
and services across
entire network
Multi-domain Networks
Automation
Better Together with Ansible +
NSO
Reference Architectures
Spanning Applications and Networks
Application Centric Connectivity Centric

Playbooks
Ansible NSO

NSO Ansible Playbooks

App App App App


Ansible Plus Cisco NSO – Better Together

• Ansible uses Playbooks to define named


tasks that are executed by the ansible-
Red Hat Ansible Tower provides playbook tool. The tasks use modules to
playbook-driven IT and network perform activities. The NSO modules uses the
automation version JSON-RPC API

• NSO uses YANG modules to describe the


schema of the data that can be manipulated
using JSON-RPC. Clients (in this case an
Cisco NSO provides model-driven Ansible module) perform operations on the
service orchestration in hybrid data stored in CDB.
networks
• Easily consumed by native Ansible allows
application-centric services to unlock the full
value of the network
Ansible + Cisco NSO - Roles and Responsibilities
Ansible Devops teams
Playbook
• Owns lifecycle of playbook
Playbook
Playbook
YANG becomes contract language
NSO module between teams across infrastructure
cycles:
JSON-RPC
• Requirements from apps device
NSO provided in YAML-format
• New services published by infra team
CDB YANG
as REST-interface update

Infrastructure teams:
• Owns lifecycle of network services
Hybrid Network
Applicable Cisco NSO Features
Ansible • NSO provides a full CRUD
Playbook
Playbook
Playbook
interface
• Create – easy
NSO module
• Update – hard

• Delete – very hard


JSON-RPC

NSO
• Transactions – either stuff entirely
YANG
happens or no stuff happens
CDB YANG
• Model-based (YANG) so clients can
fetch and validate payloads

Hybrid Network
Three Ansible Modules for Cisco NSO
• The nso_verify module fetches data from NSO, compares with data in
the task and reports any violations
• The nso_action module performs RPCs on NSO (e.g. check-sync) and
validates the output
• The nso_config module is used to create and delete instance data in NSO
Module Commonality
• YAML data encoding for all Ansible features
• YAML encoding is straight translation from the JSON data structures natively
provided by NSO, e.g:
• curl -H "Accept: application/yang-data+json" \
http://localhost:8080/restconf/data/devices/ | json2yaml
• Input data is runtime validated against applicable subset of NSO YANG
modules
Value of Ansible Tower + Cisco NSO
• Single Ansible module leveraging • Gain immediate control over the
NSO to support 70+ vendors entire network from data center to
across domains CPE
• Integrated YANG-support for • Significantly reduce the amount of
model-driven configuration time spent testing configuration
validation changes
• Full rollback capabilities across • Reduce fallouts requiring manual
vendors and device types intervention to a minimum

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy