 As you can see I'm working for red hat, you know and after this fancy behind this fancy name Which doesn't mean a lot. I'm going to talk about the integration between ansible and open daylight and more specifically specifically ansible networking So this is a little bit of the agenda. What is open daylight? What is ansible pretty raise your hands if you know what is open daylight and Ansible Not pretty good. So I can go much quicker then The third point We're going to talk about the integration between those two these two technologies and then I'm going to show a video of a demo. So they will they will not be hands-on actually What is open daylight? It's an open source project. It was created with all these SDN wave and one of the Definitions that I like the most about open daylight is that it's like the middleware for for network services, right? So it's not just an SDN controller. It's It's a kind of a platform to create network services red hat was a platinum founding member of the project and It was it's quite interesting because the presentation from last noise is that the architecture is pretty much the same and So you will understand easier The the heart of the open daylight is this blue box here, which is called md sal model driven service abstraction layer and What it allows you to do is to to model your network service via Language call young where you can define attributes RPC calls or any kind of parameter and There will be some rendering of this model into Java classes that are ready to to be implemented, right? It also provides The databases like we have two different data stores configuration operational data store and on top of that we have what it's called not bound applications. So we have You can do many things with it we have Kubernetes networking management we have service function chaining network utilization applications There's plenty of them and in the south of this blue box below We have what we call? Southbound plugins or protocols. So we have open flow of the SBB BGP and so on and what we want to do here what we want to show it is it's basically a prototype, but It it could be quite promising. It's to integrate Ansible as one of these southbound plugins and now why Ansible Mainly because you know is one of the fastest growing projects I think in in the last decade There's a huge community. It's very simple to use like Great in a playbook Which is like a recipe of tasks that you want to automate is very very easy. There's a thousands of modules to to use Unlike puppet or chef you don't need an agent on the target machine that you want to automate and and it's very powerful You can automate servers storage and what we are going to talk about here network devices, so there are like 50 more than 50 platform supported and 700 modules something like that for just Ansible networking and of course it's not only switches and Routers you can also there are load balancers and any other platform the way Ansible is a structure We have playbooks which are the recipes where you write your your tasks that you want to automate and then some roles Which is like a group of of tasks around a same topic. Let's say and In in Ansible networking we have Function roles and provided roles. I'm going to explain better with with an example The demo is going to be about creating an L3 VPN between two endpoints to routers so our Function role is basically to create a VPN or delete a VPN and That's very simple that that's something that everyone understands and you don't need to care so much about how it's going to be implemented The implementation details are embedded into the provider roles So imagine you have a lab with heterogeneous hardware, so we do you have Cisco's and juniper and And another vendor comes for example Dell and says hey I will give you a very good deal with this bunch of hardware take it because the only thing that you want to You have to provide or the vendor will have to provide is the provided role for for that same Function role for creating the VPN. So the beauty of Ansible networking is that you get an abstraction layer and the user doesn't need to care about the implementation details and The provider roles will connect to the devices and configure whatever is need to be configured So the integration is mainly these two boxes here We're using Ansible towers a GUI to interface with open daylight just not to send like Rescom calls VSEI but The important part is here Ansible is it's a stateless right and it was meant to be like that the thing is From the network Operator standpoint you need some kind of a state you need to to have to know the state of the network and Ansible can cover the management plane of Then of the network, but not the control plane. It's not done as the end and that's what the What open daylight provides? It provides state it provides network topology. So I think that the combination could be very very powerful So the demos about creating an L3 VPN, this is all running in one server is virtualized and we have a bunch of virtual machines these four boxes that you see here are acting as piggy routers and Which are there the routers that are in the service provider network and we are assuming that Some underlying connectivity is provided like MPLS and BGP and so on so these peer routers will have customer premises routers connected to them and and From Ansible tower we will instruct open daylight to create a VPN between two of these peer routers so one once the VPN is created We will be able to see two of these C routers Being able to ping each other, right? so in the end what it will do open daylight will Know in the topology we'll execute L3 VPN and civil role and And the provider roles will connect to for example the Cisco boxes. It doesn't matter is if the boxes are virtualized or or physical and We'll configure the VRF the interface the IP in the interface that is connected to the CE router and so on So this is the operational workflow, but I'm going to show you in the video because I don't have So much time. Yeah, okay. Can you see it more or less? Okay, I can explain anyway It's okay. No problem. So This screen is showing the CLI of the terminal of To see of the to see routers. These are the routers that are in the customer premises or at home, right and As if you can see here, we have this IP 10 dot 10 dot 10 dot 5 and 20 dot 20 dot 20 dot 5 different networks so what we are going to do like I'm showing that that IP and I'm going to try to ping each other Okay, ping doesn't work So this is a civil tower It's a good to manage and civil playbooks and roles and things like this what we have here are different templates the job template is like basically one Playbook let's say and a workflow template is a chain of different job templates so What we are going to do is Execute the configure site template and we will pick to the two endpoints of the L3 VPN We have a bunch of parameters like the the site name The IP of the peer router of the interface that the peer router faces to the C router So what we are doing here is pushing information to open daylight From the first site now. We are going to execute the same With the second site the other endpoint Okay, we change the VPN ID doesn't change because it will be just one We change the name of the node Okay, it's executed. You can see like a civil tower provides logs and everything is pretty cool Now we will execute the manage L3 VPN service will which will do It will push the information to Open daylight to to create the the L3 VPN this is skydive It's another open source tool that allows you to monitor the the network and as you can see this is the underlying Infrastructure so you can see the box is connected and this is the VPN And there is no links between between these these items so now once we Execute we execute the manage L3 pn It will create the VPN it will SSH into the boxes Configure the VRF the IP in the interfaces and so on Now we see the three VPN is in green Now we are pinging if it's correct and Suddenly the pin starts working right so now let's see that the L3 VPN will be established and and the people connected to this serial router will be able to connect to the other side of the network and there The overlay Drawing is it's connected now you can see the interfaces so that there's a budget of information that Sorry for going so quickly, but that's basically it any question. I will be outside