We're excited to announce our third annual Cisco NSO Developer Days NYC!

Returning to New York City, the two-day event is a tremendous opportunity to learn more about real-world applications of automation, gain a better understanding of NSO technologies, participate in labs, and engage in open discussions with peers and the engineers that built NSO. The goal of the event this year is to learn, inspire, and connect!

Register now as space is limited and will fill up quickly.

Visit the NSO Developer Hub and check out the videos and presentations from the Stockholm NSO Developer Days 2019.

AGENDA

DAY 1: Wednesday, Dec. 4
Madison Square Garden

8:00 AM   Registration and Breakfast

8:30 AM   Welcome and Introduction
Nicklas Wagerth, NSO Community Lead

8:45 AM   NSO State of the Union
Fredrik Lundberg, Dir. Strategy & Planning, NSO 

9:15 AM   Workflow vs NSO Service vs Nano Service
Viktor Leijon, Technical Leader, NSO

10:00 AM   Break

10:30 AM   A Breakneck Journey into Network Service Based Automation in DevNet Sandbox
Hank Preston, Principal Engineer, Cisco DevNet
Sandbox is a public Software as a Service offering from Cisco DevNet that provides developers access to Cisco hardware and software (as well as relevant third party and open source solutions) for building applications and automation using the APIs and platforms provided in them. Under the hood, this means we operate data center networks that aren’t that different from most enterprises, but with some unique design and scale needs. We recently decided to go all-in with network automation and chose Cisco NSO to be our tool for defining and managing the network services that power Sandbox. As stars aligned, we also were building a new data center with a very short timeline… hence our breakneck journey into network service automation. 

11:15AM   Network Automation Delivery Model
Fredrik Swahn, Product Marketing Manager
Network automation is high on the agenda, but remains a daunting challenge, with results often failing to live up to expectations. Many are struggling with both the technical and organizational changes it requires. With years of experience of implementing network automation using the Cisco Network Services Orchestrator (NSO), we have developed a Network Automation Delivery Model (NADM) that aims to guide customers in their journey towards a fully automated network. A powerful, standardized, model that covers the essential parts of a network automation transformation will be presented and discussed. The model covers all four perspectives of People, Process, Technology, and Organization and therefore targets all the stakeholders from C-level decision makers to the network engineers that execute the operations of the network as of today. During the session, both challenges and success factors for implementing network automation will be presented and put into context. 

12:00 PM  Lunch Break

1:00 PM   OpenConfig Integration with NSO
Jeff Cook, Principal Engineer III Datacenter Network Architecture, Charter
The OpenConfig standard is currently used to provision supported devices in a device agnostic manner, similar to how NSO functions with its network element drivers. OpenConfig can be moved into NSO to function as a NED abstraction layer, providing an OpenConfig equivalent to all underlying devices that NSO manages. This provides the capability to build stacked services on top of the OpenConfig layer and provide an OpenConfig compliant API northbound to all NSO managed devices.

1:45 PM  Cisco NSO in Docker
Kristian Larsson, Architect
See how placing NSO in a Docker container can help you streamline your development, testing and deployment flow. Kristian goes through why you might want to use Docker for your NSO development and shows the official NSO Dockerfile as well as how to apply it to your NSO projects.

2:30 PM   Fastmap Templates in Cisco NSO
Michael Maddern, Technical Marketing Engineer 

3:30 PM   Break 

3:45 PM  Brownfield Service Reconcile Operations
Dan Sullivan, Principal Architect, Sales
A low code approach to brownfield service discovery in NSO.

4:30 PM  NSO Roadmap and Future – Panel

5:00 PM   Reception

DAY 2: Thursday, Dec. 5
Madison Square Garden

8:00 AM     Breakfast

8:30 AM    Optimization and Trouble Shooting
Sebastian Strollo, Principle Engineer 

10:15 AM  Break

10:45 AM  Introduction Nano Services introduction
Try Ryeng, Technical Leader, Cisco, NSO 

12:00 PM   Lunch 

1:15 – 5:00 PM Labs and Leadership Tracks @ Cisco Office

Lab 1: NANO Lab
Cisco Office, 1 Pennsylvania Plaza, Floor 6, Studio 54A
In this lab we develop a basic Nano service application. Nano service applications differ from Fastmap applications by allowing a service to be both activated and deactivated in multiple stages. This is useful, for example, if the application needs to allocate and return a license for the virtual machine it spins up and down. This is an advanced lab; you need to be comfortable building a Reactive Fastmap service application.

Lab 2: NSO In and On Kubernetes
Cisco Office, 1 Pennsylvania Plaza, Floor 9, Yankee Stadium A/B
Fredrik Jansson, Principal Engineer & John Mullooly, Distinguished Architect, Sales
In the first half of this lab we build a k8s deployment of NSO from the ground up. We will start packaging NSO in a docker container, from there we will gradually build up to having Helm charts that can deploy NSO in a k8s cluster. In the second half, we will turn things upside down. We will use NSO to orchestrate deployment and "day-n" configuration of an example cloud native application running in k8s via NSO integration with Helm. This is an intermediate lab; You need to be comfortable with container concepts.You need to be comfortable with container concepts, hands on container experience will help, but is not mandatory.

Strategy and Leadership Track
Cisco Office, 1 Pennsylvania Plaza, Floor 6, Studio 54B
Fredrik Swahn, Product Marketing Manager
Cisco strongly believes that Automation Director’s importance will steadily increase over the coming years. Organizations will heavily rely on network automation and the Automation Director will be the responsible person for delivering on the objectives and make sure that the automation team executes on the plan on time and with expected quality.

*Note: All details subject to change.