the Presentation

Download Report

Transcript the Presentation

Software and Networking
<Audience Name>
<Your Name Here>
<How to follow you on social media>
USE THE BEST HARDWARE AND SOFTWARE
USE THE BEST HARDWARE AND SOFTWARE
Consistent Hardware Architecture
Consistent Software
SDN Ready
Key Juniper Solutions
SRX
Security Router/Gateway
EX & QFX
Switching/DC Fabric
MX & ACX
Universal Routers
Integration
More than Networking
–
–
–
–
Application Delivery
Zero Downtime
Mission Critical Services
Security
Juniper Heritage
– Started in the Service Provider Space
– Junos was always meant to be automated
– Complete Cross Portfolio Solutions
“Any sufficiently
advanced technology is
indistinguishable from
magic” – Arthur C. Clark
Sometimes it’s too Easy
‘The downside of “Easy Button” is that
it usually doesn’t get considered
“Automation” because you don’t have
to do anything… go figure!’ –
Anonymous Juniper Engineer
What does SDN mean to you?
Gartner
SDN
1. a new approach to designing, building and operating networks that
focuses on delivering business agility while lowering capital and
operational costs. It is far more than just a new set of APIs
designed to replace command line interfaces for managing individual
devices.
2. a shift from (per box) element-based control to network-based
control.
Source: Gartner, Ending the Confusion About Software-Defined Networking: A Taxonomy.
.
Juniper Partner






Juniper Partner
2500 Switch Deployment
Standardized on Junos Version
$15 Per box to Upgrade
Juniper ZTP
Potential Savings > $30,000
Retail Deployment




7000 National Locations
3 Network Techs
PCI Environment
Deployed by Store Managers
Restaurant Chain




2500 Global Locations
3 Devices Per Store
Manual rollout = 3 Per night
Automated Roll out = 50 + Per Night
Juniper Automation Heritage
Consistent feature development
From early on we have developed strong
automation features in the very heart of
our platforms, e.g.
•
Network OS
Junos V
Junos
Space
Chef
App Engine
Puppet
XML-RPC / Netconf / DMI
1996
•
Junos Scripting with Op, Event and Commit
Scripts
•
Space with Network Director and Security
Director for network level abstractions
•
Integration with Configuration and Cloud
Management Platforms, to enable end-toend automation
•
Junos SDK
Control
Plane
One Junos
JunosEZ Framework for off box and on box
scripting and integration into existing
customer solutions
2005
2006
2007
2008
2010
2011
2013
2014
2015
JunosEZ
Framework
NETCONF
Junos Script
Automation
2012
Junos SDK
Service
Plane
SDN
Protocols
Support
Ansible
… our heritage in forward thinking decisions has
allowed us to innovate and automate across our
entire portfolio
Range of Automation Tools and Building Blocks
NETWORK
OPERATORS
Using Tools to build
solutions to solve Day to
Day needs
USER SOLUTIONS
TOOLS
TOOL MAKERS
Building tools on top of
libraries and APIs to
help Network
Operators achieve
their goals
LIBRARIES
API
VENDORS
Building compelling
products, and
programmable abstractions
PLATFORM
The Path to SDN – Stages
Build
ZTP
Deployment is currently the most costly and easiest
to operationalize
Ansible
OpenClos
Deploy
Orchestration
Contrail
Add/Moves
Verify/Monitor
OpenStack
Chef
Service Now
OpenFlow
Puppet
Netconf / DMI
VMWare
Ansible
J-Vision
PythonEZ
SNMP/Events
The Orchestrate Phase moves
further into integrating into the
software stack
Orchestrate
Maintain
Maintain addresses day to day
operations and ensuring compliance
and uptime
Zero Touch Provisioning
Simplify Deployments
DHCP request/offer – specify base configuration and software version
1
Manually
Technician
must only
unbox, connect
to network,
and power up
device
Base
Config
Junos
2
Retrieve base configuration file and software image
Upgrade software and apply base configuration
Server w/
DHCP & FTP
Send SNMP Trap to Network Director, push templates, the end.
3a
Determine location in network via detected variables
3b
Specific
Config
Request location and device specific configuration
Automation
Minus
4
5
Retrieve and apply location specific configuration
Self-register with Network Director/MGMT Platform
Junos Space
Network
Director
What is ZTP? (It’s Not Magic)
The Preboot eXecution Environment (PXE) is a standardized clientserver environment to boot clients from a network. Only a PXE capable
Network Interface Card and small set of protocols such as DHCP and
TFTP are required.
Consistency Matters
Analyst and Academic
research suggests That
70-80% of Networks
are
Vulnerable Due to
Configuration Errors.
Regular Audits for
Consistent Passwords
Non Blank SNMP Community strings
VLAN Consistency
Etc.
75%
The Junos Automation Stack
Tool built into Junos that enable automation
The Junos OS has had automation features consistently
added over the past 15 years.
Python
Scripts
JET API
Ansible
Salt*
Ruby
Scripts
PyEZ Framework
Puppet
Chef
RubyEZ Library
NETCONF
THRIFT
JSNAP
This heritage of feature innovation has allowed Juniper to
deliver new features by building on top of the abstraction
layer below.
CLIRA*
Python / SLAX
Junoscript
Three (3) key features form the basis for almost all
automation aspects at the platform layer
REST
CLI
jVision
Sensor
XML-RPC
Chassis

XML-RPC in the core of Junos and
Netconf to provide network based
access to the system

Junos Script for automating Operational,
Configuration and Event based tasks

Junos EZ Framework implementing
Python and Ruby based object models
for interacting with Junos using modern
programming languages
SNMP
RO
Data Plane (PFE)
Junos Platform Automation Stack
Scripting
Commit Script
Run every time a user commits the configuration, can
help with automation and consistency
Op Script
Initiated by an operator, help in
troubleshooting, configuration, monitoring
Event Script
Initiated by an event policy and allow
automation and troubleshooting
So, Why is it called “PyEz”?
So, Why is it called “PyEz”?
Raw Python – 48 lines
So, Why is it called “PyEz”?
Raw Python – 48 lines
ncclient – 19 lines
So, Why is it called “PyEz”?
PyEZ – 7 lines (and gathers more info)
Raw Python – 48 lines
ncclient – 19 lines
All 3 scripts gather ‘show version’ info from the same device
Puppet
Ansible
The Junos Automation Stack
JET API
Salt*
PyEZ Framework
Ruby
Scripts
Puppet
Chef
RubyEZ Library
JSNAP
CLIRA*
Python / SLAX
Junoscript
NETCONF
REST
CLI
jVision
Sensor
XML-RPC
Chassis
SNMP
RO
Data Plane (PFE)
Junos Platform Automation Stack
Flexibility
THRIFT
Ansible
Simplicity
Python
Scripts
Automation – The Hard Part
• Not a technical problem, it is cultural
• Automation is business driven
• Intellectually difficult
• An engineer’s value is not how much they type at the keyboard
• Networks are already highly automated, if you think about it
• Nothing good is easy, nothing easy is good
RIPPED FROM A NET.ENG BLOG
Kurt Bales, Senior Network Engineer
www.network-janitor.net
Juniper Partner






Juniper Partner
2500 Switch Deployment
Standardized on Junos Version
$15 Per box to Upgrade
Juniper ZTP
Potential Savings > $30,000
Restaurant Chain




2500 Global Locations
3 Devices Per Store
Manual rollout 3 Per night
Automated Roll out 50 + Per Night
Retail Deployment




7000 Locations
3 Network Techs
PCI Environment
Deployed by Store Managers
SDN Point of View
Accepts and converts
orchestrator requests for VM
creation, translates requests,
and assigns network
OPENCONTRAIL CONTROLLER
Configuration
Control
Real-time analytics engine
collects, stores and
analyzes network
elements
Collector
Interacts with network
elements for VM network
provisioning and ensures
uptime
VM
VM
VM
vRouter
Physical Host
with Hypervisor
vRouter: Virtualized routing
element handles localized
control plane and forwarding
plane work on the compute
node
VM
VM
Physical
Network
(no changes)
Gateway
WAN, Internet
VM
VM
VM
vRouter
Physical Host
with Hypervisor
Gateway: MX Series (or other
router) or EX9200 serve as
gateway eliminating need for
SW gateway & improving scale
& performance
Thank You!
http://forums.juniper.net/
http://www.facebook.com/JuniperNetworks
http://www.juniper.net/youtube
http://twitter.com/#!/junipernetworks
http://www.linkedin.com/company/juniper-networks
https://github.com/Juniper