Junos Automation Stack Data Plane (PFE) Chassis XML-RPC NETCONF Junoscript SNMP RO Junos Platform Automation Stack Ansible Python Scripts SaltStack Puppet Ruby Scripts Chef Python / SLAX ASAP JSNAPy THRIFT/ gRPC REST CLI JTI Sensor Ephemeral DB JTI YANG JSD MQTT JET PyEZ Framework RubyEZ Library The Junos Automation Stack is extremely powerful and is packed with features that allow for practically everything on a Junos device to be automated. While it is very important to identify the business problems that can be solved using automation, it is also important to know that what you actually are implementing the automation against is DESIGNED to be automated and is not a bolt-on. But remember, as you get further away from the direct OS interaction, there are abstractions that happen that could remove some flexibility of command choice and/or OS manipulation. For most, IT frameworks and basic scripts will be enough to push configuration and get basic status. But when more and more information is needed from the network, you must delve deeper into the stack and use things like JET apps and YANG models to truly unleash the power of an automated Junos platform and make the idea of an “SDN” become a reality (fully integrated butterfly rainbow kitty optional)

AUTOMATION TOOLING Using Tools to build solutions to solve Day to Day needs Platform API LIBRARIES TOOLS USER SOLUTIONS NETWORK OPERATIONS TOOL MAKERS VENDORS Building tools on top of libraries and APIs to help Network Operators achieve their goals Building compelling products, and programmable abstractions At level there are ways to build automation capabilities. Vendors need to build products with programmable interfaces that allow for abstractions to be built and used to programmatically address the device(s) and manipulate them the same way any engineer would. On top of that, programmable interfaces that allow the device to act differently than it normally would and allows the end user to extend that functionality. Junos has this, no other vendor (currently) does – at least across platform families. Tool Makers need consistent and well documented APIs from vendors to be able to integrate device management and device capabilities into higher layer tools for use by customers. Juniper examples of these tools are PyEZ, Space (and associated applications), JSNAP and JEAP. Network Operators need to be able to use the tools created by the Tool Makers to assemble them and build solutions that automate tasks normally done by network engineers. This allows the engineers to move forward and solve problems rather than constantly spending time doing the same things over and over again. Different tools, aimed at different groups in the solution delivery chain

Junos Automation Stack Data Plane (PFE) Chassis XML-RPC NETCONF Junoscript SNMP RO Junos Platform Automation Stack Ansible Python Scripts SaltStack Puppet Ruby Scripts Chef Python / SLAX ASAP JSNAPy THRIFT/ gRPC REST CLI JTI Sensor Ephemeral DB JTI YANG JSD MQTT JET PyEZ Framework RubyEZ Library NETWORK OPERATIONS The Junos Automation Stack is extremely powerful and is packed with features that allow for practically everything on a Junos device to be automated. While it is very important to identify the business problems that can be solved using automation, it is also important to know that what you actually are implementing the automation against is DESIGNED to be automated and is not a bolt-on. But remember, as you get further away from the direct OS interaction, there are abstractions that happen that could remove some flexibility of command choice and/or OS manipulation. For most, IT frameworks and basic scripts will be enough to push configuration and get basic status. But when more and more information is needed from the network, you must delve deeper into the stack and use things like JET apps and YANG models to truly unleash the power of an automated Junos platform and make the idea of an “SDN” become a reality (fully integrated butterfly rainbow kitty optional)

Junos Automation Stack Data Plane (PFE) Chassis XML-RPC NETCONF Junoscript SNMP RO Junos Platform Automation Stack Ansible Python Scripts SaltStack Puppet Ruby Scripts Chef Python / SLAX ASAP JSNAPy THRIFT/ gRPC REST CLI JTI Sensor Ephemeral DB JTI YANG JSD MQTT JET PyEZ Framework RubyEZ Library TOOL MAKERS The Junos Automation Stack is extremely powerful and is packed with features that allow for practically everything on a Junos device to be automated. While it is very important to identify the business problems that can be solved using automation, it is also important to know that what you actually are implementing the automation against is DESIGNED to be automated and is not a bolt-on. But remember, as you get further away from the direct OS interaction, there are abstractions that happen that could remove some flexibility of command choice and/or OS manipulation. For most, IT frameworks and basic scripts will be enough to push configuration and get basic status. But when more and more information is needed from the network, you must delve deeper into the stack and use things like JET apps and YANG models to truly unleash the power of an automated Junos platform and make the idea of an “SDN” become a reality (fully integrated butterfly rainbow kitty optional)

Junos Automation Stack Data Plane (PFE) Chassis XML-RPC NETCONF Junoscript SNMP RO Junos Platform Automation Stack Ansible Python Scripts SaltStack Puppet Ruby Scripts Chef Python / SLAX ASAP JSNAPy THRIFT/ gRPC REST CLI JTI Sensor Ephemeral DB JTI YANG JSD MQTT JET PyEZ Framework RubyEZ Library VENDORS The Junos Automation Stack is extremely powerful and is packed with features that allow for practically everything on a Junos device to be automated. While it is very important to identify the business problems that can be solved using automation, it is also important to know that what you actually are implementing the automation against is DESIGNED to be automated and is not a bolt-on. But remember, as you get further away from the direct OS interaction, there are abstractions that happen that could remove some flexibility of command choice and/or OS manipulation. For most, IT frameworks and basic scripts will be enough to push configuration and get basic status. But when more and more information is needed from the network, you must delve deeper into the stack and use things like JET apps and YANG models to truly unleash the power of an automated Junos platform and make the idea of an “SDN” become a reality (fully integrated butterfly rainbow kitty optional)

KNOW YOUR CUSTOMER Who are your customers? Network engineers & Architects Operators IT/Sys-admins & DevOps What problems are they trying to solve? What products are they using today? Are they automation products? What have they evaluated already? Do they like to develop in-house tools? What are the typical workflows for that customer? Are there any special considerations?

1996 2004 2008 2012 2014 2000 2015 2016 Juniper Extension Toolkit Automation is in our DNA. From day one, Junos has been API driven. Since then, we’ve developed strong automation features into the very heart of our platforms allowing us to automate and innovate across our entire portfolio like no one else can: Config Groups Netconf Toolkits Juniper Extension Toolkit JSON output format One JUNOS API Driven Config & Cmd Access Control Commit Batch Chef Python On-Box Service Plane APIs Puppet RESTful API IETF YANG Models 1996 2004 2008 2012 2014 2000 2015 2016 Juniper Networks has a rich history innovating in the field of Network Programmability -- In the areas Network deployment, Management and Operations juniper has made key contributions and partnered with critical groups to advance automation technologies. For example Juniper Networks proposed RFC 4741 for the Network Configuration Protocol (NetConf) in 2006, jointly developed by the IETF working group and later revised in June 2011 and published as RFC 6241. NETCONF provides mechanisms to install, manipulate and delete the configuration of network devices. To be added: Config groups Commit confirmed SLAX 1.1 Debugger & profiler for SLAX Apply-macros The JUNOS operating system also has key elements for network programmability – the Software Development Kit was introduced in 2007. Timelines: CMD Auth -1999 Config differ – 1999 Junoscript - 1999 Commit at – 2002 Config compression – 2004 Config encryption – 2005 Netconf Interface Range – 2011 Config protect – 2011 JUNOS CLI Ansible Control Plane APIs Ruby Ez Custom YANG Models Junos Operation YANG Model NETCONF/Junos XML APIs Structured Syslog PyEZ OpenConfig Models Junos Config YANG Model