Advent calendars normally take the form of a large rectangular card with number of windows. Each window represents a day in December leading up to Christmas. Each day one of these windows is opened to reveal a hidden treasure, be it a poem, story, image, toy, or, most common, a chocolate treat.
In a way, Juniper’s Junos OS is like an advent calendar. It provides a different window behind which is a new and wonderful surprise that give you the power to truly automate your network environment.Read more...
Automation is in our DNA and we take it to a new level by supporting the initial set of OpenConfig data-models in Junos OS 16.1R3 release. It was just little over a year when we had started talking about our leadership on this initiative; early this year (at the MPLS/SDN/NFV world congress), we did a demo showing how the modular and programmatic architecture of Junos can consume new data-models such as OpenConfig...and now, we are shipping it!!
A quick recap – OpenConfig is a collaborative effort by network operators sharing the goal of moving networks towards a more dynamic and programmable infrastructure by adopting SDN principles such as declarative configuration and model-driven management and operations. The group defines a consistent set of vendor-neutral data-models (written in YANG) based on actual operational needs. While initial set of models have already been published, others are being worked upon by the OpenConfig group.
Juniper’s approach to OpenConfig gives maximum agility to customers by decoupling the OpenConfig package release from the Junos releases. Our approach allows the flexibility to add any YANG model (OpenConfig, IETF, or Custom built) as a separate, add-on package on top of Junos, thereby enabling our customers to rapidly roll out new features and services without the need to upgrade Junos OS in their networks. Our support for OpenConfig includes BGP, Routing Policy, Telemetry, RPC, Local Routing, Interface, MPLS and LLDP data-models. Subsequent OpenConfig packages will be shipped as more data-models mature.
There are endless possibilities with Juniper’s OpenConfig implementation. I would encourage you to download our OpenConfig package and try it out on our vMX.
- OpenConfig Documentation: http://www.juniper.net/documentation/en_US/junos16
- OpenConfig Models on GitHub: https://github.com/openconfig/public
- Blog Post on NETCONF & YANG basics: http://forums.juniper.net/t5/Automation-Programmab
- Blog Post on OpenConfig: http://forums.juniper.net/t5/Automation-Programmab
Lego pieces can be assembled in multiple configurations—for example, a set of six 2x4 bricks can be interconnected 915,103,765 different ways. The ability to create and recreate new objects are limited only by our imagination. Similar to a set of colorful Lego blocks, the Juniper Networks® Automation solution comprises a suite of tools that developers can combine and interlock with various open-source frameworks.Read more...
Elections are part of the democratic process in which the general population participates in a formal vote to determine direction for a collective group. Public polling and surveys are as much a part of the modern electoral process as campaigning and voting. Surveys have been widely used to gain a general understanding of the current environment, as well as future directions.Read more...
One of the hottest topics circulating throughout the telecommunications industry today is how service providers are transforming their business model, migrating from a traditional telco operational management style to a development operations style.
But did you know that his hot topic is old news at Juniper?Read more...
Ansible is a very popular automation framework to manage and deploy all components of an IT infrastructure.
Since 2014, Juniper has been providing Ansible modules for Junos to allow our customers to manage Junos devices with Ansible. These modules for Junos are available in Ansible Galaxy.
In its latest release, Ansible is now officially supporting a group of modules for various network devices, including Junos. Juniper is very excited by this new partnership and we’ve been working closely with Ansible to make sure that these new modules will follow both Ansible and Juniper best practices.Read more...
So, you've bought into the idea of creating network device configurations using templates. You've got your head around breaking the config into repeatable chunks, the templating language to do flow control (things like conditionals and loops) and have organised the device variables into something that makes logical sense and produces working config. But rather than reaping the rewards of this effort you find yourself drowning in constantly maintaining the beast you've created!
Thankfully there are solutions to save you from constantly tweaking variable files to keep the system working and get you back to the sanity and serenity.
This article will use a practical example of how to increase maintainability using a repository of network configuration based on Ansible. In it you will be guided step by step in reducing the number of variables needed to generate the configuration.Read more...
Continuous integration (CI) is a software engineering practice in which discrete, isolated changes are immediately tested, logged and added to a larger code base, providing a detailed record of changes so that, if a defect is introduced into the code base, it can be quickly identified and corrected.Read more...
For years, network operators have been faced with developing a number of techniques to manage multi-vendor environments. Today, these network elements are often configured via vendor-specific CLIs (command-line interface) or through well structured programmatic standard (e.g. NETCONF/XML) or proprietary interfaces each colored with their own vendor-specific hue. Outside of the configuration aspects of these network elements, the extraction of telemetry and operational state information has also been fragmented and inconsistently available forcing operators to rely on a combination of techniques such as SNMP polling, syslog parsing and periodic screen-scraping of show commands to glean the operational state of their network.
Juniper extension toolkit (JET) for Junos OS provides a modern programmatic interface for developers of third-party applications interfacing with Junos based devices. It supports consistent APIs across all Junos OS releases and platforms supporting JET. JET is an evolution of the Junos SDK with expanded capabilities, allowing customers and partners to build and run applications either directly on Junos devices or off-box, using a standard set of APIs. These internal and external applications interact directly with Junos OS's native features and components via APIs. Since JET is based on Apache Thrift, it also supports multiple languages running off-box to interact with the same JET APIs. This gives developers true flexibility to adapt Junos devices to business processes, with applications on many different development platforms. In this blog we will examine the Juniper Extension Toolkit for Junos OS, and some examples on how it can be used to boost operational efficiencies and productivity.Read more...
The second in a series of blogs on YANG and how Network Management entities should progress in the path to Network Innovation.Read more...
Here is a great blog by my intern Animesh Kumar. He worked for my over the summer and created a great tool Ptolemy: The Network Cartographer. For me it was an amazing experience and I am so happy to have had Animesh working for me this summer.
By Animesh Kumar:
During my initial years of work in IT industry I used to work on Automation of test suites for the tools I had developed or the APIs I had written. My notion about Automation at that time was to make everything in a program or tool run automatically without any manual effort. One click of a button and it should run all the scenarios by itself, covering all the possible test cases and corner cases. For doing this, I used to think of all the possible test cases, negative or positive and automate the testing for it. But every time a new bug came in and my test suite failed catching it, used to frustrate me a lot that even after putting in so much effort, I was unable to automate the testing.Read more...
Karan Singh Dagar (kdagar)
Junos OS Has the Toolkit to Make You an Automation
n for OpenNTI Collector witho...
ility with OpenConfig and Junos
- Pallavi Mahajan (pallavi) on: Towards the path to Network Innovation (part 2 of ...
- shabbiralpha on: Can you automate Automation for me? - By Intern An...
- kaustu on: Netconf and YANG – explained in a layman’s term
- scottdware on: The Basic IO of Network Automation
- furiousmonkey on: Empowering the Tool Builders
Python for Non-Progra
mmers (Part 5)
Python for Non-Progra
mmers (Part 4)