 Soundcheck good. Good morning guys all hear me. Okay, you know we got some spots up here in the front row, right? Awesome, thank you. So those of you that were expecting JR this morning. I'm the younger taller better-looking, but not quite as brilliant version of JR Rivers So the session was going to be a little bit about about monitoring and kind of looking at open stack from from that perspective We're gonna actually change this up a little bit and talk about layer three to the host and How to interact with with open stack in a little bit different way Sound good. All right. All right, so I'm gonna bore you What if you could reduce your IP address count and the hassles of building a layer three fabric? By putting IP addresses on every with every single link in the fabric What if you could get rid of spanning tree In your fabrics, doesn't that sound like a wonderful thing? Yep, what if my clicker worked a little faster? Oh get closer to the here we go What if you could do layer three ECMP from your servers to do flow-based load balancing rather than Doing, you know something with layer two where you've got one link up one link down And you're basically wasting half your bandwidth and so server mobility. There's a lot of different ways to approach this, right? and then Reducing the controller to the fabric complexity and then more visibility So how do I how do I create a way to actually be able to visualize or show with a connectivity between the compute pieces of the network? They opens that compute and network nodes and the actual fabric itself so the answer to this is Basically create layer three fabrics and address put IP addressing on the host itself So part of that's that's a partial answer So the way to really kind of take this to the next level is to use something that we call BGP unnumbered so if I have a BGP fabric I want to use unnumbered interfaces. I essentially can put a single IP address on a device And have unnumbered on interfaces and essentially do point-to-point pairing and TCB BGP peer establishment across in the number link All right, so a couple of different design just a couple design slides. I want to show real quick first one is kind of discussing ECMP within the fabric and then kind of a Not so traditional. I guess a single attached server connection And then the second option is really looking more at this BGP unnumbered Concept that I'm talking about which now you can do ECMP type links across from the host into the fabric And so we're showing here more of a connection There's the I'm looking for my mouse, and it's not on my screen, but it's almost sure screen very good So kind of look at these links. This looks almost like a layer two fabric connection, right? But if you can kind of visualize or Think about this as being just just an example If you wanted to put eight nicks in a server and connect it to the fabric can just as easily do that in layer three environment Little more difficult to do that in layer two environment alright, so The demo that I'm going to show you is is really like a five-node OVA in virtual box And what I've got is a single spine two Leafs a management bridge so I can talk to all the different virtual devices and Then a couple of servers and these servers as you can see down here on the bottom It's an open stack controller. So there the two servers on the one hand is server one It's an open stack controller a compute node Network node and a dashboard node. So basically everything I do is pretty much going to be from And the demo is going to be from that that one server and then server two is going to be simply a compute node just to Essentially build your tunnels and establish connectivity. So what we're going to show is A custom tenant creation script So basically going to open stack kind of do its thing just build VXLan tunnels for two different networks build a virtual router And then make sure that the connectivity works between the different nodes and then use some Command line just to kind of show you the output from both the fabric side as well as from the actual compute side alright, so I see Nolan's in the back row back there I still want to his slides and put the train wreck up here because it's demo time as promised I've got virtual box up and you'll see I've got Mario server one I've got an external router that's running just as an example to open stack to kind of get off to the physical network a leaf Two leaves in the spine just kind of like we showed in the diagram right and if anybody wants to actually kick the tires in This demo themselves if you go out to the the cumulus website under our support site There's a whole list of demos and down here on the open stack cumulus VX rack on a laptop layer three to the host Basically step-by-step instructions On how to build this essentially you're downloading the OVA And there is a link to that right here Essentially you import the OVA as an appliance and it explodes into this all right, so as Promised the server is the spot where I usually go connect you first, right? So I'll go ahead and do that and you can see here That I've got some cheater scripts kidding on kind of like we talked about a little bit of you on the slides And so I'm gonna hold off on a minute before I build this because I want to go back to open stack go to horizon login No compute instances go down look at the network real quick Network topology Generic you expect to see this on a fresh install, right? Networks external network and then routers Blank again, so I'm gonna go back over here and land on the instances pages and Look at a few things here first of all look at the IP route table Kind of get a quick shot here at one two one sixty eight dot one hundred dot two or dot zero network And then there's a two hundred dot two and I want to show you Server two which I'm for now. I'm gonna ignore, but I'm gonna actually go over here to this leaf leaf one and so net show is It's a command. It's in the operating system It actually kind of makes the Linux interface for networking a lot more Appealing to somebody that's got more of a network background So if I do this command is called net show if I do net show interface Just kind of gives me a status on the on the actual interface and talks about it shows me with the name of the Interfaces the speed empty you you can kind of read what it's showing me here, right? The neat thing about this is I can tie into the open stack environment Back into the network node and if you look at what I've got highlighted here It'll actually tell me the local port what it's connected to so I kind of talked about earlier in the slides I want to show you how to make that linkage between the open stack component and the fabric a little bit more visible, right? This is one of those those methods of doing so So you can see it's an unnumbered interface So what does that mean no IP address on the actual link? We're using the loop back IP as a connection point All right, so net show interface there when I look at the LLDP real quick Do I so I can figure out who I'm talking to you'd see that my my port 49 is talking to the spine layer? We go back to the spine You see you've got fairly similar connectivity except that we're talking to leafs, right? LLDP talking to leaf one leaf two So if I go back to the diagram so everybody's kind of got a visual remember server one server two So we've looked at server one connectivity with the leaf one look at spine one look at my routes real quick pretty simplistic I'm gonna do a quick dump on the actual PGP config so you can see that From a BGP perspective This is about as simple as it gets you define the router ID You define the interfaces that you're actually peering on and then just set the remote as is External or internal in this case. We've got it all set as external I'm gonna go ahead and show the same thing on the leaf side. You can see it's it's almost identical as definition the router ID and then the port and then whether it's remote AX is external or internal you see we've got these all as a external as well okay, see One other thing I'll show is I'll do an IF query Just to kind of give a quick snapshot of exactly what interfaces are configured on the switch Okay so Going back to this guy. I'll go ahead and kick off the demo script I'm gonna go ahead and create this two tenant subnets demo And so what you see here is I got a nice cheater menu, right? So I'll go ahead and start this And what it'll do is it'll kick off all the all the scripts to actually build the infrastructure that that two subnets with a router And then it'll have four different VMs so we can kind of test the connectivity between the different networks Any questions so far? So the neutron plug-in that we're using so the neutron plug-in that we're actually going to be using for the connectivity is going to be vxLan It's going to be ml2. It's going to be the you know the vxLan overlay the That's not actually talking to the fabric. That's just talking to the compute node and the network nodes, right? So what we're doing is using Quagga The routing application on the host to be the layer 3 connectivity to basically pass reachability information to all the host and compute nodes The compute nodes in the network. No, excuse me that way now open second Do what it does best and communicate with its own its devices to build the overlay directly rather than have to actually communicate for fabric So it's like one less failure touch point, right? And this is taking a little longer than what I think it should She would Yeah, all right So you know it's funny because we had a discussion this morning is like I don't do live demos on purpose because the train thing happens I Record demos. I just got done recording this demo in the back put it up on YouTube and Here I go doing a live and we're getting something here little patience So what you're going to see when we get done? Is there's really not going to be any kind of changes to the? the actual Fabric itself the reachability information the routes the IP connectivity is already in place All the change is going to happen on the open stack nodes, right? I'm now I'm going to see I'm going to see my VX land interfaces I'm going to see my router interfaces all my bridges. They're all going to be created on the end points Still waiting And you're out in tomatoes out there. We get on time, right? Is if this doesn't like Finish up soon. I'm probably just going to go back to my MP4 and just hit play But I I think it's building. We're still working here in the background Port forwarding turned on to the to the actual VM. So I'm not sure that that's going to work Five minutes I'm afraid to interrupt that script. It might not finish the build All right. I tell you what I'm going to do. I'm going to go back and do exactly what I said I was going to do it's like a cheater approach, but yep still waiting. All right, so We've already done all of this This is the abbreviated version because I've edited it to cut out all the wait time And since we're running short on time. It's probably a good idea to go this right anyway All right, look familiar Yeah, so that's a minute to go exactly All right, so once this thing's done I go ahead and do a a verify because you got to create a verify destroy and a quit right so on the verify Just kind of go through and actually look and see that all the different interfaces and the subnets and The machines are all created and you can see down here. I've got the two vehicle I'm going to quit pointing at that because that brings up a blocking window. All right, what you're seeing What you're seeing here is just a list of of the different open stack Instances, right and as you can see in horizon, we've got two different networks We've got the router and what I'm going to do is actually go in and show the IP addressing on the networks So you got the the 100 dot 1 dot 0 and the 100 dot 2 dot 0 the two different subnets And you can see my virtual router here Interface list You got an interface on each subnet obviously in a one interface to the external gateway And then what I want to do is just kind of go back through here and actually show the IP addresses of those devices Inside of the server that compute slash network node And so once I go ahead and do that I'll actually log back into horizon or go back to horizon and then launch off a connection into the console and actually Ping across the different VMs just to kind of prove out the fact that it's actually built up the network So compute instances all four, you know two in each subnet you've got the 100 dot 2 dot 0 network So two instances there there's like one on each so we got two servers, right? So we've got a different one of those endpoints is on one server and the others on the other server that way We're actually forcing these of the overlay network And so from this one instance when I log in I just I just ping everybody from that one spot That's usually enough to verify connectivity minute and a half. All right, that's uh That's about it for the demo. So let me Let me go back over here and see if our actual demo actually finished building and it did not so I'm glad I went to the video So we got about a minute left any any questions any other questions out there. No Well, thank you everybody for coming out. Thank you