Symphony conductor and network OS: What do they have in common?
Feb 9, 2017
The symphony season is at full swing. The San Francisco Symphony kicks off 2017 with series of performances. The top-billing event features the exhilaration of Beethoven’s Piano Concerto No. 4, accompanied by Brahams’ Symphony No. 3 and performance by international piano phenomenon Lang Lang.
The symphony orchestra is one of the oldest forms of musical ensemble, consisting of over 80 musicians on its roster. The ensemble contains sections of string instruments (violin, viola, cello and double bass), brass (horns, trumpets, trombones, and tuba), woodwind (flute, clarinets, and oboes), piano, concert harp, and percussion instruments.
The orchestra conductor is the heart and soul of any symphony. The conductor interprets the music being performed and provides instructions to the musicians. The conductor also unifies the orchestra, sets the tempo, directs the performance, and shapes the sound of the ensemble.
Similar to an orchestra conductor, network OS performs a critical function that aligns devices, applications, and data for network services based on a set of pre-defined policies and service level agreements (SLAs). Network OS has also to adapt to revolving market environments with open programmability, ensuring communication service providers and enterprises alike to rapidly adopt an agile, scalable, and secured IT infrastructure that is critical to business success.
Junos OS was a major disruption to the networking industry when it was introduced 20 years ago. From day one, Junos OS has been leveraging Juniper’s Data Definition Language (DDL), effectively the precursor of YANG, to model the configuration state. What Junos OS started has now become mainstream and is standardized across the networking industry, where Network Configuration Protocol (NETCONF) is used as a transport mechanism, and YANG is used as a data-modeling language.
In addition to supporting YANG to model configuration objects, Junos OS supports the standardized YANG models as defined by IETF and OpenConfig. Junos OS can easily incorporate any new model without requiring a software upgrade. It can also incorporate any custom YANG model including model intent-based interfaces toward the network infrastructure.
I would like to invite you to explore different use cases that Junos automation has to offer. Watch our webinar Model-Driven Network operation with OpenConfig and YANG and download our Junos OS whitepaper to learn more about the Juniper automation solution.
There are endless possibilities with Juniper’s automation. Visit the Automation Use Cases @ Juniper Networks for more information.