The Cisco Open SDN Controller is based on the OpenDaylight SDN Controller and meets the need of Service Providers for a flexible, powerful, and commercially-supported multi-protocol controller. In this 60 minute session we will give an overview of the Cisco Open SDN Controller, explaining how the controller is packaged and the features it supports, and showing examples of applications that are supported by the controller. We will also outline the new features and applications that will be introduced in the next release of the controller. Taught by Giles Heron. You can see this presentation on youtube: https://www.youtube.com/watch?v=fzgvt--7Wxw&feature=youtu.be
14. Thank you.
DevNet @
Join us on DevNet at developer.cisco.com
Follow DevNet on Twitter: @ciscodevnet
Notes de l'éditeur
Background info on ODL
So now we add auto-population of the NCS devices inventory.
To do that we run BGP-LS on ODL to learn all the IGP nodes and then write an app inside ODL (“NCS Inventory Creator”) which reads the linkstate topology and creates each node in NCS using the binding-aware API generated from tailf-ncs-devices.yang. As noted above we wrote something similar in I2SS (but using the ODL node inventory and using the NCS Java APIs)
Potentially we could even interface Niklas’s “Pathman” to this as his LSP setup code is quite isolated inside the Pathman app.
We will also create the “LSP Config app”. This exposes a tunnel programming API (most likely we’d create topology-tunnel-config and topology-tunnel-config-programming – similar to their PCEP equivalents). The app will create tunnels using the binding aware Java API to the NCS device-layer YANG models for IOS-XR (from the IOS XR NED – tailf-ned-cisco-ios-xr.yang).
PathMan uses the topology API (http://localhost:8181/restconf/operational/network-topology:network-topology/topology/example-linkstate-topology) to learn the topology and then the tunnel programming API to create tunnels. It’d mean slight modifications to PathMan so it can use the slightly different API.
As noted above we’d also still be able to show Postman accessing the RESTCONF to NETCONF stuff.
The NCS IOS-XR NED uses CLI over ssh to configure the XR node at the head end of the LSP.
IOS-XR uses RSVP-TE to signal the LSP (or SR to impose a label stack)