ONE controller and Open Daylight!!
Now it’s getting really exciting. Madhu Venugopal is presenting information about Cisco’s participation in Open Daylight and its relation to the ONE controller.
3 layers to the controller architecture:
- Northbound API – for apps to be written towards
- Network Service & Orchestration
- Southbound – protocol plugin to communicate with network infrastructure
ONE controller use cases:
- Network Segmentation – aka Campus Slicing
- Topology Independent Forwarding – Traffic Steering
- Network Tapping – aka Matrix use case
- Overlay & Underlay – Openflow & OnePK (we will be doing hands on lab with this use case) – ability to guarantee underlay SLA for overlay tunnels
TIF – Topology Independent Forwarding
Madhu is demonstrating modifying values and links in ONE controller management.
** LAB TIME **
Labs were entertaining but I really wanted to understand what was going on so I had to spend 10 minutes or so just mapping & drawing out the topology … CCIE lab style :p.
They moved on to discussing overlays and 1000v … old news. Zoning out and surfing Twitter at the moment.
I woke up when he started going over VTEP (VXLAN Tunnel End Point) details. VTEP is per hyper-visor (he said per host but we got it)… blah blah. It’s picking back up at least.
At least I thought it was, talking about VXLAN … nothing new here, just re-hashing. Zoning back out.
Talking about VXLAN gateway, I think I knew this but I forgot, VXLAN gateway will appear as a module in the VSM.
Discussing OpenStack Quantum integration with VXLAN. Cisco is coming out with Nexus 1000v tab for OpenStack dashboard.
I find it very interesting that they are using Openstack and KVM for the VXLAN overlay-underlay stitching demo rather than VMWare. That is rather telling I think.
Looks like we are wrapping up here. I am going to head to the Tweetup then finish some of the Cisco ONE controller labs later.