Hey Jan here,
do you know that you can register for Developer Days Workshops and Labs to secure your seat? To do that, just look up your confirmation email titled "Cisco Automation Developer Days: Know Before You Go" and click the "Modify Registration" button. A few pages later you can see the program and select the sessions you want to participate in.
If you don't register, you will be welcome after all registered participants have taken their seats.
We can host up to 35 participants in the new Reaching Network Automation Level 5: Principles and Practice lab. It builds on last year's presentation about automation levels. In this lab, you will be able to take an existing service from automation level 3 to level 4 and up to level 5. This will give you an immersive feel for what the automation levels are all about.
What you get:
• Hands-on experience with Network Automation Levels 3-5
• Giddy feeling of power arising from services that adapt to their environment
• Food for thought when designing your next NSO service
To participate, you need:
• Development knowledge of NSO
• Bring your own laptop with NSO 6.1.5 (or later with a few tweaks) installed
• Basic programming skills in Python
• Familiarity with NSO services and YANG modules
Title: Reaching Network Automation Level 5: Principles and Practice
Instructors:
• Jan Lindblad, Engineering Architect, Cisco
• Per Andersson, Engineering Technical Leader, Cisco
• Jonas Johansson, Software Architect, Cisco
Abstract:
Once the Adaptive Service Activation Scripts (Network Automation Level 2) are left behind, a world of life-cycle flexibility and stylistic freedom emerges for the services running in our network. What can we use this flexibility for?
In this lab, participants will upgrade a pre-existing Network Services Orchestrator (NSO) service from Network Automation Level 3 to Level 5 by adding service health measurement and making it adapt to changes in the environment.
The vision of the Internet Engineering Task Force (IETF) Application Level Traffic Optimization (ALTO) Working Group (WG) is to optimize the application and network together, so that the delivered service is provided as efficiently as possible to the collection of users. This might mean delivering a user's service from a data center that is not the closest one but from another with less load or lower energy prices, and therefore, less expensive for the customer. Moving service instances around becomes a natural part of the life cycle.
Link to repo: https://github.com/janlindblad/nso-sustainability-automation-example
This lab can also be taken as a self paced exercise at your convenience.
