HN753: Getting to Know Cisco’s Network Service Orchestrator (NSO)
Oct 14, 2024
auto_awesome
James Henderson, an automation solutions architect from Ductis, sheds light on Cisco's Network Service Orchestrator (NSO). He discusses how NSO revolutionizes network automation with its declarative management approach, enabling seamless configuration across devices. The conversation covers the tool's dry run capability, operational intricacies, and integration challenges, particularly in high-demand settings. Henderson also highlights the importance of secure access protocols and innovative solutions involving Kubernetes, inviting further exploration of these cutting-edge technologies.
Cisco's Network Service Orchestrator (NSO) simplifies network management through declarative modeling, allowing users to define desired outcomes without manual CLI commands.
NSO's atomic transactions enhance operational reliability by ensuring that changes are fully applied or completely rolled back, preventing inconsistent configurations.
Despite its advantages, using NSO entails a steep learning curve and the necessity for strong technical knowledge to avoid performance issues.
Deep dives
Overview of Network Service Orchestration
Network Service Orchestrator (NSO) is a robust automation tool designed to streamline network management through declarative modeling of configurations. It allows users to define what they want the network to do, rather than specifying how to achieve those changes. This retracts complexity, as each network service can be directly mapped to the necessary device configurations, devoid of manual CLI commands. An example highlighted is VLAN management, where NSO automates the addition of VLANs across devices by utilizing YANG models, capturing the current states, and calculating necessary changes.
Atomic Transactions and Operational Integrity
One of the key features of NSO is its capability to execute atomic transactions across a network, ensuring that changes are either fully applied or completely rolled back in case of an error. This atomicity is crucial in preventing issues where only part of a network change is implemented, leading to inconsistencies. The system communicates changes in a network-wide manner, and if any one device fails during the update process, changes are reverted across all affected devices. This functionality enhances operational reliability and minimizes potential downtime caused by incomplete configurations.
Unified API and Device Modeling
NSO offers a uniform application programming interface (API) that simplifies interactions across various devices, regardless of the vendor. It achieves this by employing Network Element Drivers (NEDs) for different device types—assuring that varied commands are handled seamlessly through its centralized management system. With this approach, network engineers can manipulate configurations without needing detailed knowledge of each device's CLI commands. The uniform API structure allows for a cohesive user experience, making it easier to manage configurations on multi-vendor environments.
The Dry Run Feature for Change Validation
To enhance confidence during configuration changes, NSO provides a 'dry run' function that allows users to preview the commands that will be executed on devices before actual implementation. This feature enables operators to conduct safety checks—ensuring that proposed changes align with expectations and identify potential errors in advance. By showcasing the specific command outputs that would be sent based on the current device states and configurations, NSO helps reduce the risks involved in network updates. This is particularly useful for network teams transitioning to automation, as it fosters trust in the tool's capabilities.
Challenges and Considerations for NSO Deployment
Despite its advantages, deploying NSO presents challenges, particularly regarding the steep learning curve and the need for careful service design to ensure effective operations. Users must be well-versed in the intricacies of NSO's capabilities, as improper configuration management can lead to performance bottlenecks or miscommunications. Additionally, NSO does not inherently track historical changes or facilitate versioning of services, which necessitates users to implement external solutions for version control of their configurations. Overall, success with NSO often requires both strong technical knowledge and an understanding of systems architecture.
On today’s episode, guest James Henderson joins the Packet Pushers to discuss Cisco’s Network Service Orchestrator (NSO). NSO’s role in network automation, its declarative management approach, and the challenges it presents are some of the things James shares with the hosts. They also cover operational requirements, deployment challenges, and performance considerations, in addition to discussing... Read more »
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode