 I'm Tom Nato from Brocade. I'm going to show you a demo of the Brocade viata controller running as a VPN gateway solution with OpenStack. This is a proof of concept that we've done jointly with Comcast in the US. Also, if you have questions, feel free to raise your hand during the presentation or whatnot. This demo is going to be pretty interactive. So if you want to see something, let me know. But I'll go through the basic scenario here. We're also doing this demo at our booth. So if you want something more in-depth or in detail, you can stop by the Brocade booth. So what what we tried to do here was we we have a use case where Comcast has multi-site video distribution and they wanted a dynamic and flexible way to position video servers. And so the solution here is to provision VPN tunnels that are not only inside of the Comcast network, but also to show that this can work for extra net capability. For example, if they wanted to use a cloud provider or whatnot to go off-net. We also used a demo high-speed broadband access trial that Comcast has going on right now as well to connect one leg of the demo. The demo is fully v6 capable as well. And then we're controlling the entire setup using the Brocade Viata SDN controller, which is an open daylight based controller. So this is a this figure describes what's going on in the demo. There are three sites. One site is Comcast in Philadelphia. One site is actually my house which has broadband residential high-speed access through Comcast's special high-speed v6 service. And then the other is our lab in San Jose. You can see there are VPN tunnels connecting each of the sites. There's actually a third one here that's not drawn. These are tunnels that carry VPN traffic between the sites. And not only between the sites, they're used to also handle what is the San Jose site, which is in effect an extra net site, so it's off-net. Whereas these two sites are actually on the Comcast network. What we've done in the demo is we've set up the three sites. We've provisioned the three sites using OpenStack and we provisioned the Viata V routers, which are the gateways, VPN gateways between the sites. We provision that, lay those down, configure the tunnels and then the traffic runs across the tunnels. The other cool thing we can do in this configuration is that if we need additional capacity, it's very easy to deploy additional V routers. These are all deployed using heat templates. So it's as easy as literally pushing a button and plugging it in. We're also running, again, the Brocade Viata SDN controller. And we're running three instances of a single logical cluster of the controller. The controller is Helium Open Daylight based. And you can see, I'll show you that running as well. That's used to control and manage and configure the V routers once they're laid down. And I think that's all we wanted to show on here. I mean, there's a couple of interesting things on here. I'm actually showing the actual addressing that we're using. The V routers are also fully configured using NetConf and the controllers are talking to the routers, the virtual routers using NetConf and obviously Yang. The UI also is using the ResConf interface that the controller is exposing. This is showing a little more detail. We actually are running tunnels within tunnels within tunnels so that this will work. It looks a little bit messy, but this is what you need to do to get this to work with the off-net case, the extra net case. We're showing full V6 connectivity between the sites. We're also demonstrating the Viata 5600 router in the example, which is going to be available in a couple of weeks. Using the images that we're showing here, so full NetConf capability. So how does this work? So I'm actually not going to step through all of the VM creation and whatnot, because this actually takes some time. If you're interested, we can do this at the booth, but we only had about 20 minutes here for the demo. So I'm going to go through some of the highlights. Basically, the way that we configure this, the VMs are running the Rokate image with public IP addresses, static IP addresses from Comcast. Those things are provisioned using OpenStack and laid down in the network. The controller then discovers those instances and then we use the controller to actually configure the tunnels on those routers. We have, again, those three sites, San Jose, Philadelphia and New Hampshire. And then I'll show you the Rokate UI that's used to actually talk to a couple of the sites. Let's see. I think we went through this already. Again, we're going to use RESTConf between the UI and the controller, NetConf between the controller and the routers. And again, we're going to provision the hosts using OpenStack. And I think, there we go. Yeah, this is just further going through the example, building the example up. And then, let me get to the last slide in here. Yeah, and the last slide here is actually showing, again, sort of the logical picture of what's going on. But further pointing out that we have three view routers running. We can easily add another site. These are just three Nova instances that are running. We could add a fourth one if we wanted to. And that's all you would need to provision additional instances somewhere else. And then the use case, of course, is again to transmit video or other traffic antenna. Excuse me. So let me bring up the demo here. Actually, let me show you a couple of slides. These are screenshots from the demo real quick. So again, the network topology is reflected. This is basically cloned at each of the sites. You'll see in the example, we have two VMs, which are just a bunch of VMs that are traffic generators. And inside of the network, we have our gateway router up here. We have the Brocade Viota controller instance. Actually, in this instance, we had two running here. We could basically have as many instances of the controller as we'd like running at the site. And then the VPN tunnels are running between these V routers and the other site. And that's how traffic is getting from where it needs to go to. That's just another figure of that. Let me grab the UI. So this is one of the first applications that we're coming out with when we release the controller in a couple of weeks. We'll be actually shipping this as a product in two weeks. And so we have two applications in here. One is called the Path Explorer, which I'll show you in a second. The other is the Viota EMS functionality. So we can see the controller will have discovered the three instances. Because this is a logical controller, it's feeding in the instances from each of the sites. And you can configure those from here. And we actually configured the tunnels using this interface. You can configure all of the parameters on the V router using this app. This is a tunnel visualization application. So this is the Path Explorer app. This is the second app that we have in here. So this is showing your Viota V routers with our tunnel that's running between these two sites. And here's another tunnel, the other tunnel that's running between these two sites with the NVMs and their stub networks hanging off of there. This is the Path Explorer app. Again, this is showing how we're actually configuring these paths and highlighting the paths that you just configured. Cool. So let's jump into the live demo. So this is, this VNC, excuse me, is of the live running network. So I'm SSH'd into, this is the Philadelphia site that I'm connected to. And you can see these are the live routers. These are the Ubuntu's that are running. If I want, I can open the console. So these guys are actually running. Let me jump in here. I've actually got some scripts that are running that are actively pinging. So these are running at each of the sites. So over here, excuse me, we're pinging from one site to the other. Over here. So this is 10, 0, 1, 7. This is net, this is pinging net 2. And this should be pinging net 107. Yep. So if we go over here, whoops, sorry about that. Here we go. So this is the site in New Hampshire that's connected over the high speed broadband access. So this is one of the guys. This is 10, 0, 2. This is the 10, 0, 2 site that I'm pinging in that ping. And what else? We can actually go to the router config over here, which I believe is running here. Yep. So this is the console for this V router over here that I'm talking to. So you can see the configuration over here. And I think that's all I wanted to show. You know, the point is that it's possible to integrate the two of these guys together. And it actually works, and it works pretty well. There's a couple of areas that we're going to be working on right now when the V routers are configured and are provisioned. Right now, the controller has to discover those using LLDP or a variety of other protocols. What we want to do is actually hack Neutron so that it works correctly. And I think there's some work going on about this right now in the L3 space. But right now, when things are provisioned through Neutron, they don't actually flow into the controller. And I think that was, oh, I wanted to show you also the live topology that's running in the controller. So this is the Path Explorer app that's running. And you can see the routers that we have here that were discovered in the previous one with their hosts on the ends. And then also the EMS that we have, let's see, in here. So this is one of the V routers. This is the V router that's at the New Hampshire site. And you can see the interfaces that are attached. This is the guy with the V6 address. And then we can also explore that guy with the Yang Explorer. This takes a little bit. Here we go. So let's go through that. Come on. Here we go. I'm going to get that from the, there we go. So we've retrieved that table from the VR using NetConf. And we're showing, we can display the info here as it came out. So this is pulled out using the RESTConf interface, which then talked to the device using NetConf at the bottom. If we want, we can actually modify these things, you know, the fields that are configurable. We can modify those. I think that's all I wanted to show. That was, you know, sort of demonstrating the Path Explorer and the EMS, as well as showing how you can do provisioning with OpenStack, and then configuration with Open Daylight. Thank you. Any questions? All right. Thanks a lot.