All right, so can you guys hear me? Okay? All right, so I'm just gonna go ahead and launch into it. So I'm Martin. I work at VMware. I was formerly at Nasera. And I'm gonna talk about virtual networking both in and out of open stack. And so I was being pressed interviews before this and someone was really confused about the title. They're like, what does vagabonds have to do with virtual networking? So let me just kind of clarify this really quick. So I spent a lot of time in airplanes. And I talked to a lot of partners and a lot of customers. So I'm the vagabond and I'm talking about virtual networking. Vagabond isn't like some open source project that has to do with virtual networking. I don't wanna be super clear about that. So I've kind of composed this talk into two pieces. So the first piece is a little bit of a retrospective which is kind of how we got here. And then I wanna talk more about virtual networking and that will be more of a, I've probably had 400 customer visits in the last two years. And just kind of give you an idea of who is doing what and why they're doing it and what's hard and what isn't hard, right? So let me start a little bit about a retrospective. So this is a picture from a talk that I gave in 2010 at the OpenStack Summit. And the world was a totally different place back then. I mean, there was real questions to the viability of OpenStack. So those of you who know who Ben Horowitz is, he was on my board. He's a principal at an Indonesian Horowitz. And like one of the biggest arguments I had with him had nothing to do with Nasirah, which I was founder and CTO, it had to do with whether OpenStack would be viable. I'm like, it's totally gonna do something big. It's gonna be really important and he disagreed, right? At the time, nobody knew what OpenV switch was. There was no quantum, SDN, like the term SDN had been coined about a year previously, right? So, you know, even though I gave this talk, it was to a very sparsely populated room, like less than half the seats were full. And if you look really closely, you'll see that those people weren't even paying attention. So, okay, so the networking wasn't like this super hot topic at the time. All right, we fast forward. Clearly a lot has happened, right? OpenStack is awesome. Ben conceded he was wrong, which was a big personal victory to me. We see a number of deployments. I don't have to tell you about that because you're here, you probably know about it or you've heard about it. But this has been a very big change. Not only that, OpenStack is, before when we would talk about networking, nobody knew what we were talking about. It was very different. And since then, OpenStack has become a beacon, certainly in open frameworks for networking, right? We saw the emergence of the quantum layer and we see an enormous ecosystem around it. And I actually don't think people understand how significant this is. And so I just want to try and give this a crack. So networks have had standardization for a really long time, right? We've had interop for a really long time. We've had control plane standardization. We've had data plate standardization. It's called Ethernet. So standardization isn't new to networking, but we've never had it for operations really. Meaning you can integrate at the control plane, you can integrate at the data plane. But boy, when it comes to things like managing a CLI, doing the provisioning, being the OAM, the operations and management, it's always been proprietary, it's always been a lock-in. Always. And it's not necessarily nefarious plan. I mean, people were focused on other aspects of it when these things were being developed. And the thing that quantum does, is quantum says, hey, listen, we actually have an abstracted interface for the network for management, for provisioning, for the ability to create new virtual networks and attach things to it. And if you look at the list of the people that participate, like, this is significant. I mean, this is a real community. And I think people are like, oh, you know, quantum is great, it's like a subset of OpenStack, but this is a really big change in the networking industry, like independent of OpenStack. So I'm gonna talk more about this later, but I really wanna point that out. So in the meantime, people talk a lot about SDN. So I'm at this point not really sure what SDN means, but it's clear that people are really excited about it and they talk a lot about it. And whenever I kind of give variance of this slide to the talk, I mean, like in the morning I kind of say, okay, what silly thing can I Google that happened recently and then that's gonna pop some article which shows how confused we are about SDN. And so this is what I actually pulled in New York, not too long ago, a few months ago, which is like, you know, like there's now investment networks, it's on the Motley Fool. Like, I mean, clearly people are very confused about SDN ever using it as an investment strategy. But this morning, I did the same thing, I actually looked in my inbox and I got an analyst report that came from the ONS which is an SDN conference that's happening right now, which is like, it's pretty clear that we're still trying to define what SDN is as a term. And we could talk about that later, which is there's clearly a lot of excitement, there's clearly a lot of hype. I don't think there's a lot of understanding about what an SDN is. So for the purposes of this talk, I'm not gonna be talking about SDN per se, I'm gonna be talking about virtual networking, which I'll describe and I'll define it's a very crisp destination and I'll be talking about OpenStack. And in the Q&A, we can talk about SDN and I'll most likely try and ask you to define what it means and then we'll try and have a discussion. Okay, so on a more personal note, so this here got acquired by VMware. And soon after that happened, well actually, around the time that it was happening, VMware got behind and got very involved in OpenStack and it wasn't just networking, right? For Grizzly, we're a top 10 contributor, but on the fourth, we announced support for vSphere. Let me see, we announced the partnership with Canonical yesterday, I believe. On our side, we've more than doubled the number of developers that we have working on it. We've increased the number of developers working on OpenVswitch. And so this is something that VMware has really gotten behind. And certainly we've been involved in it and the CIRA side has been involved in it for a long time, but we continue to be behind. And so just to kind of put this a little bit in context, so after the acquisition, I hopped in an airplane and I flew around and I talked to our existing customers and potential customers to see how they felt about the acquisition. And existing VMware customers and existing CIRA customers, generally the view was positive, which is ESX is a very important platform. VCD is a very important platform and getting integration with that was a big deal. But there was some concern about what would happen with our involvement and VMware involvement in OpenVswitch. There's a lot of skepticism. And in fact, our CEO, Steve Malaney, who actually now runs the BU, has this story where he was talking to a customer and the customer's like, listen, I believe that you believe that VMware's gonna do the right thing. I believe you believe that, but my experience is totally different. So I just wanna spend one slide to try and describe why it makes sense. And then I'm gonna go into the virtual networking talk. Okay. All right. So I think at a macro level, this is all about the movement to the software-defined data center, software-defined infrastructure, whatever you want to call it, which is things that existed in hardware and were provisioned with atoms, like physical atoms that you picked up and you moved around, those are moving to a software layer. So I'm a software guy. I've always been a software guy. I like to build software and I like to provide software to people. VMware is a software company. So let's say that you build something like a software networking layer, which is what I'm interested in building. So you have this and you want to be able to provide it to customers in a way that they want to consume it. Now, having been spent so much time on the road and figuring out how to sell this stuff, it's very clear to me that there's two consumption models. One consumption model, my consumption model is like, I am a customer. I want to consume software. One consumption model is like the vertically integrated stack. I sold against this stack for four years, isn't this here, right? I'll go in, I'll be like, listen, I've got this cool thing and never mind the wires singing out and like the sparks and whatever, it is cool and like you can modify it however you want, but it's a piece, it's a component. It's a component of the software-defined data center is not the entire thing. And like a lot of customers, very legitimate, will be like, listen, this is not what I want. And I would say this is probably 70% of the engagement cycles I want. This is the whole, forget VMware and forget OpenStack and think about just converged hardware infrastructure. This is a very common sale and consumption paradigm that some people like. It's not me, it's not what I would consume, but it's valid and this is something that VMware is very comfortable with and it's been selling into for a long time. However, there's another consumption paradigm. By the way, I made that slide, that's why it's kind of crummy, which is horizontally integrated. Meaning, I've got good developers, I think that I differentiate by technology, I like or don't like open source and I want to compose things on my own. This is the standard horizontal consumption mode. This is what I'm used to selling. This is what I've been spending four years. It's a much longer sales engagement cycle. It's very technical, but people like it for a certain reason, right? And this is where OpenStack has fit very well traditionally, right? And so from the standpoint of VMware, you want to sell into as many customers as possible. So certainly you do this, which VMware is very comfortable with and now there's interest in also selling into the horizontal model, which is, we think we've got good software. We think that it is pluggable, it can be competitive at an independent component level. Why not consume it of that way as well? So that is the interest behind selling pieces of, aligning with OpenStack. With OpenStack is a fantastic way to horizontalize the industry so you can have these best of breed components. I mean, even in the time of Nassirah, like we had a closed source controller, it wasn't open source, but it was about open interfaces. It was about getting behind OpenStack, which we still want to maintain. We're actually pretty successful with that model. So let me go on to networking. So I'm going to talk about a trend that has nothing to do with OpenFlow or SDN or even network virtualization. I want to talk about a trend that's been happening for the last 10 years. And I think that this is one of the most significant trends in networking that nobody's talking about. So if you look at a lot of the big data centers that are built, whether it's like a Web 2.0 data center or it's infrastructure as a service or platform as a service or whatever, you have this trend where you have these very simple data center networking fabrics and functionality that's traditionally been in the network is an x86 at the edge. So I'm going to give you an example of Web 2.0. So in a Web 2.0 data center, very often you've got an L3 ECMP fabric from whatever vendor.  This is a great way to build the fabric. It's not over, so you can build it in a way that's not over subscribed. You've got very quick convergence. You've got great load balancing. It's technically a great solution. And then the application or the web server or the ADC, the load balance or something else is implementing the functionality stuff like load balancing or security or isolation or whatever. Like this is done. Like there's no point in arguing about it because this is some large portion of the workloads today or under this model. And like the reason is the model's awesome. Like you get to put stuff in software. You've got software innovation cycles, right? It's at the edge, so you don't have to solve the aggregation problem. Like you're like, if you think about the amount of networking that's already happening on the end host, it's a lot.  And like the closer you are to the application, like the more semantics you have anyways, which is why like a totally valid way of building a data center is to like have the application do as much stuff as possible and pull it away. I mean this is like the convergence of the end-to-end argument, right? I mean this is a good place to put functionality. And if you look at a lot of these new data centers, it's exactly that, right? You've got the x86, whether it's a middle box or x86, whether it's a server and you've got an L3 fabric. So this is clearly a trend. I mean I'm personally familiar with dozens of these and they're some of the largest data centers in the world, but I'm also familiar with, this isn't just a service provider big data center thing. I mean there's a number of enterprises that are doing this on all sorts of scales. Because it's actually a great way not just to scale, but to actually build functionality in software. Software's awesome. There's kind of like a basic problem which is whenever you build something like that, it works for that specific application. But it's a little difficult to extend that to support all workloads, right? So if I have a VM and I give that VM an ethernet nick and I'm running a legacy operating system on it, it's gonna expect some semantic, some service model from the network. It's like, well, you've given me an ethernet nick, I want L2 or something like that. So this doesn't work for everything. But it certainly is setting the bar for the cost model, the software innovation model, the flexibility model, and the hardware independence model. I mean this is setting the bar. Like if you want something to like compare yourself against, go to look at one of these because it's a great way to build systems. So that's the first trend. Okay, so the second trend. This one's even more shocking to me. So the first trend, this has been happening over the last 10 years. It has nothing to do with me. It's a trend that's happening out in industry. This trend also has nothing to do with me. It's been happening in industry. It has to do with VMware. Which is, last year, the number of virtual ports that are ports that are attached to VMs globally succeeded the number of physical access ports. That means there are more virtual ports out there than there are physical ports at the edge of the access of the network.  Right? I mean, it's pretty easy to do the numbers. The majority of workloads are virtualized and best practices are three vNICs for one of these. And so the numbers actually pencil out pretty easily. But the implications are pretty phenomenal. Which is, it's on x86. You already have a couple dozen VMs often sitting on one of these servers. You already have to do an awful lot of networking there anyways to actually handle communication between them. Right? So you're already doing an awful lot of networking on the server at the edge. So I just want to put virtual networking in quick perspective here. Which is, it really, independent of who's doing it, it really is kind of alignment of these two macro level trends. Which is on the top, you've got this, okay, I've got all of this functionality that's moving from the physical network into x86. And then the second trend is, we have all of these virtual ports that we actually have to add functionality to anyways. And so I'm gonna do like a quick animation here, which is, okay. So what you want, is you want kind of the cost, flexibility, innovation model of that side. But you want that for every workload. Right? You don't want to do it like per application in a way that you may be only partially supporting it. And so that's it. So if you have a virtual networking layer, the idea is you can have, again, from the top side, you have whatever hardware platform that you want to do, again, else for UCMP, great model. But again, this is independent of what happens on the physical network. The physical network is its own battlefield. You want to have new workloads, share a common layer, and then of course you want to have existing enterprise apps. So you maintain the cost model, but then you support pretty much any workload. So that's the big idea of virtual networking. You guys probably already noticed that I'm gonna go very quickly about this. So the idea is on the server, just like in the days of compute virtualization, like we've decoupled the operating system from the server, but we haven't decoupled it from the network. So network virtualization says, listen, I'm gonna run stuff within the server. And then that way VMs instead of connecting to a physical network, which today, I mean, if you look at the ARP cache, if you look at the default gateway, often these are physical addresses that these things are attached to. So if you take a VM and you move it, like it's view of the network changes. And this is where a lot of the operational complexity comes from. So instead of saying, listen, I've virtualized a VM, I've pulled it up, a virtualized an operating system, I pulled it into a VM. Instead of having it talk to a physical network, I'm gonna have to talk it to a virtual network. So now VM spin up, instead of attaching to a physical network that are kind of a pain to manage, I'm gonna attach it to a virtual network. It looks exactly like a physical network so I can support any workload, but it's gonna have the operational model of VM. Great dynamically, you can go out, you can shrink it, you can move it around, but it has the same kind of like high level system design principles that I described previously. And you guys have all probably heard the pitch, which is okay, so you get like really complex networks and then you provision them really simply. So before it was a really complex network and the idea is instead of having to like string wires and this and that, like I can go ahead and just in the software, create arbitrary topologies, L4 through seven services, yada, yada, yada, right? That's the big pitch of virtual network. And so going forward, I wanna talk about like what this means. And like the first thing I wanna say is like, this is not like science fiction. Like there's so many deployments of this stuff today and there have been. I mean, we've been in production for years now. And so for the rest of this talk, I want to talk about experiences with organizations that are trying to consume this type of technology. Why they're doing it, what works, what doesn't work and so forth. Dela Daganets is one of the best movies ever. And I think it actually underscores the most important lesson of virtual networking, which is like, if you think about the SDN space and what people talk about, it's normally like commoditized hardware or flexibility of software or operational savings. And in my experience, it's none of that. And it's like, it's one thing to really like the technology and it's another thing to think it's cool and it's a totally different thing to actually buy it. And if I look back at every one of the deals and the experiences I have, like what makes people buy virtual networking is speed. That is the primary, like what is the pain point of my solving? It's not, it saves me a lot of money. It's not, I can innovate in software or I can program my infrastructure. It's like, something took me a long time before and now it takes me less time. Is that clear? And so, the other one is like, like lower operational overhead is definitely important. But it's a secondary value proposition. Lower CAPEX is definitely important, but it's also a secondary value proposition. Meaning at the end of the day, if I'm not taking something that used to take a long time and making it short, it's probably too early to consume a technology like this. So let me talk about the few use cases. So this is like the driver for why you buy it. But let me talk a little bit about what people are using it for. Okay, I didn't make this slide, that's why. So the primary use case, and all of them the primary use case is how do you take a data center and make it multi-tenant for some definition of multi-tenant? Whether this is infrastructure as a service, which is this is a dev cloud, which is this is focused on a data center. I've already got virtualization. There's a disparity between how long it takes for me to spin up VMs and configure VMs and how long it takes for me to configure the network. I mean, there's certainly dozens of deployments that are just focused on this one problem. Another use case, and by the way, when I talk about use case, I'm talking about like, like these people deploy independently. Like for DMZ virtualization, this is something to say, listen, my data center is fine. I use VLANs, they're fantastic. But I'm not comfortable with how long it takes for me to deploy the DMZ. And so actually, there's probably more deployments and interests in just DMZ virtualization, which is like the data center is fantastic. I'm running OpenStack with VLANs or the open V switch plugin or whatever, and it's fantastic. But actually like dealing with all the all four through seven services, and I need a different service chain for different customers. And, you know, I'm aging out these appliances or whatever, I need to somehow provision and virtualize that as much as possible. And especially in the enterprise is an enormous use case. And the last one, which is independent from the other two, is like, listen, my DMZ is fine, like my data center is under control, but like I'm having a very difficult time taking customers and bringing them on because of whatever reason, because I don't know how to have open relaping addresses or I don't know how to do all two extension or I don't want them to download something and configure it or they don't have a special type of hardware that I need them to have or whatever. So I just want to point out, like cool technology is flexible, I can do all sorts of stuff, but if I really do a cross section of the people that are deploying this stuff, 80% of the time it fits into one of these. One of these use cases. And in all of these, we've got pretty significant deployments. Okay, so I want to talk about hurdles. So I had a customer meeting in Europe. And like before the meeting, so we've been talking for a long time with this company. And like before I went in, to have the meeting, I guess they did some preparation work because when I sat down, it was very clear that like, listen, to do this, you need this type of hardware over this configuration. And to do that, I can use this type of hardware and this configuration. To do this, the thing that you can do with virtual networking, I need this type of hardware and this configuration. So it's very clear that anything you can do with virtual networking, like if you have enough resources and you have enough time and you have enough people, you can do. It's not like we're bending the laws of physics. And it's not like we're changing technology. It's very difficult to come up with use cases for early compute virtualization that you couldn't have done with an operating system. Virtualization has been around for a really long time. We've had virtual memories, right? But it's very, very different to give an operational abstraction, right? And so if I think about like, what is the number one hurdle? And this is probably generalizes for cloud, but certainly for virtual networking, which is, if there isn't an understanding that all of this technology is just about provisioning and automation, then there's probably not, the organization is probably not in a position to accept this stuff. Now, of course, if you look through each one of these slide decks, well, in order to do L2 you use VPLS and L3 you use VRF or whatever. I mean, of course, you need different configurations and you need people to do this and you need different types of components. Clearly, this is a resource-intensive, expensive way to do it, but you can do everything, right? And it's funny, I love press. Press is fantastic, but a question you always get is what is the number one competitor to X, Y, or Z? And independent of where I am in a company, the number one competitors to something like virtual networking is nothing to do about the new incumbents in the field. It's all about, here's one way of doing it. People are very comfortable in that way. And it's very difficult to differentiate against a million people with big tech books, right? Because they can figure out how to do this over a period of time. So it's important that you realize that the claim is not that we can do something new that you can't do before. The claim is that it actually follows like an operation-efficient software model. All right, so let's assume that, okay, customers, they understand there's a lot of value in this, right? So like they've gotten past the status quo inertia and they're like, okay, we wanna do this, we've got this pain, we're gonna take this. So now you're like, okay, let's figure out how to, let's figure out how to install this stuff. Like the number one hurdle, by far, even from a willing customer, is that like, and I'm sure this is the case for Cloud more broadly, it's just the organizations aren't structured generally to consume this type of stuff. I mean, the amount of turf war is over, like who owns the virtual network edge? Is it the networking guy? Is it the virtual admin guy? I mean, I've seen it all. I've seen whole teams fired, right? They're like, listen, if these guys, so why don't we fire them? I've seen the creation of new economic entities. We're like, listen, we're gonna create a new team. I've seen Skunkwork projects. We're like, okay, we're actually creating a new project and we're gonna hire people into it from the organization, but we're not gonna tell anybody what we're doing. And all of these are these kind of abysmal contortions to get out of the need to just deal with the internal organizational dynamics. And it's very interesting because technology, school value proposition is still very difficult to consume. So the third hurdle, and it's actually really shocking to me how significant this is, is we're still in the architectural war, which means before you have products, you talk architecture because you don't have products. And when you talk architecture, it's kind of who can say it the loudest and who's supporting what cause and everybody's confused. Like imagine if you went to go buy a car and you walked on the car a lot and the guy's like, okay, listen, you've got this car, you've got this car and the way we build the engines are totally different. And we use this paradigm for building the engine as far as speed and it's not like, come on, this is silly, right?  But for the last five years of network virtualization and STN, it hasn't been about driving cars because there really haven't been that many cars. It's been about having these idealistic arguments about which architecture's better or not better. Like the same thing happened in compute virtualization. Do you guys remember like the wars between dynamic translation and para virtualization? Like I'm sure like, I'm sure marriages were like ended over the state. Like people really care, like dynamic translation is like, you don't have to modify the guest and you can do anything. And then the para virtualization guy's like, but it's slow and like the IO's not gonna work. And like, you know what people don't talk about anymore? It doesn't matter. Like at the end of the day, if you have good products and people are using it, you don't argue architecture. You're like, listen, this is fantastic. This is fantastic. Let's go ahead and try them. And you look at the checks and fortunately we're getting to that point. The last five years has been so much craziness, right? Like, I don't know what STN is. I was there when the term was created. There's total confusion between mechanism and solution. So STN actually had a meeting at one point and that meeting was like a way to build systems. There was no customer value. It would make no sense to say, hi customer, I've got STN. That's like saying, hi, I've got Python, like good for you. But that's not what I want. But this is because we're still talking about it. It's not like you're bringing more product. You're trying to like argue from like some core architectural points. There's also like mass confusion on the implementation versus like product design, which is like I've got this implementation. I tried it out. It doesn't work. Therefore, like the approach sucks, like, you know, and this is immature and there isn't a lot of information. So nobody's really default, but like it's really important for everybody to realize that like this is what happened when you don't have anything is you talk about it and you argue. And like, and once you have products, it'll mean much, much less. And maybe instill in some dark corner of the internet we'll still be arguing over it. And I'm certain I'll be part of those arguments, but like it's going to be good once the industry evolves. So I've just got two more slides. So many times I went network virtualization in OpenStack. So I actually think OpenStack has been incredibly significant in general for SDN and OpenStack. And there's actually a reason that I am here in this conference talking to this audience. Because, you know, I've been involved, you know, in open flow. I wrote the first version. I've been involved in SDN. And like at the end of the day if you look at who's deploying stuff and who's using stuff, it's actually here. Like we can talk about this stuff all we want but until you have products and until you have software until you cut your teeth, until you have customers it's just like more discussion. And I think that the networking industry is starting to recognize how significant OpenStack is which is why things like Quantum are as diverse and as broadly supported as they are. And I believe it's going to continue to be that way. And so I think that when it comes to networking OpenStack really is somewhat of a beacon. And if you're interested, of course people can sell you stuff including me but that's actually not the point of this talk. So my last slide is I just want to let you know I'm not just a spokesperson. I'm a user. We've been using OpenStack for quite a while. We've got a very, very large deployment. And it's a great technology. Certainly for trying out some of these core networking functions. And with that I will go to questions. Is there are questions? Yes? Let me see if you were to do the relationship you know inside. So for those that you don't know OpenDalight is an open controller platform by back by a number of industry. Big guys in the industry like we're a gold member you know Cisco, IBM, HP, Red Hat and so forth. So there's many open source controller efforts that are out there. And I think they should all be compatible with OpenStack. So this is like, you know OpenDalight is how do you build an SDN controller for managing networks. And so for example, one of the things that we've offered to contribute to OpenDalight is actually a quantum plugin so that they could be compatible. And so I'm not sure I can comment behind that other than this is it's nice to see more open source efforts in this area. And we're actually the ones that stepped up to commit to plug it into. I think that's the right way to do it. I mean I think ultimately when you look at orchestration frameworks you want to abstract out pieces of infrastructure and OpenDalight is something you abstract out. I mean I think that this is what like the primary like one of the primary values that OpenStack provides is it you know like you know before we had atoms and atoms have very clear lines to plug things into each other right. And now we're going into software. And so you have like software infrastructure you need these clear lines to kind of mix and match pieces. And so any piece that fits within that like OpenDalight should be abstracted out by something like quantum. I mean this is exactly what happened. So we sell a virtual networking solution that you slot in to something under quantum. Yeah so. So I'll tell you what OpenFlow was created for. But so OpenFlow was created to as an interface to control physical hardware and at the time the focus was in campus. So it came out of you know my thesis which was ethane which was low level control for security purposes of the campus network. That's what it was created for. Since then it's been generalized to some general interface to program switch hardware. And so I would say that it would apply to any environment in which you want a generalized interface to control switch hardware. But I'm gonna be very clear about one thing. OpenFlow doesn't do anything new and it doesn't do anything that you couldn't have done before, right? So let's go to the days before OpenFlow. The days before OpenFlow you could go get an SDK from whoever and you could write software to things and expose it to a remote thing. All OpenFlow does is standardize that. So when you talk about use cases the use cases not around can I do some cool new stuff because you've always been able to write software to switches because there's software running on switches. OpenFlow says if I have somebody else's switches can I control it in a unified platform? I want to be very clear about this. Like again, having wrote the original version it's not, it doesn't make like it's not a new technology, it's a standard. Use a mic. Is it still applicable today? And do you see that being evolving and use cases developing around OpenFlow or I want to make a distinction SCN versus OpenFlow and OpenFlow was created, I understand but today and tomorrow where do you see that going? This to me is a question of customer need. In as much as there's an interest in customers and having an open interface to switches that third party vendors can talk to it's applicable. In my experience, this hasn't emerged but that doesn't mean it's not there. Like I have worked with large companies that have deployed OpenFlow networks and seem value. Now they're often they're just kind of doing something that's very similar to MPLS. But again, I want to just for everything else I want to make the distinction. Like the reason you use OpenFlow is not because you couldn't do something before it's because you want to do this in a way that's decoupled from the hardware. Whether this relevant or not these aren't the conversations I have with customers so I'm not in the right position to say.  Apologies for pounding on the same topic but to your very point, and you brought to a very good point about the difference between mechanism solution and like you clearly pointed out, I mean virtual certificates have been around for what? 20 years now, right? We had ATM virtual certificates and MPLS LSBs and we could have controlled them programmatically. Sure. And we understand that now we have the virtualization now suddenly we can control things in software.  You're absolutely right. Okay, so I want to go back to compute and server virtualization. So we've had virtualization for a really long time in the compute space, right? Like remember when VMware or whatever was just getting started, they're like, listen, we have virtual memory and of course we've got processes and we virtualize all this stuff and then we have virtualization, right? But you didn't have a virtual machine abstraction. You had tons of virtualization in networking. You've had tons of virtualization for decades but you don't have a virtual network abstraction. It doesn't exist and that is the operational abstraction that operators use. They operate on networks, not on independent components. Like it's very difficult to structure a data center where you can do both L2 and L3 and arbitrary ACLs and arbitrary L4 through L7 interposition. It's not that you don't have the technologies to that. You don't have the abstraction. So it's exactly right. We've had virtualization in networking for a long time and we've certainly been able to program it but we don't have a virtual machine abstraction and if you want to change the way you operate something you need an abstraction, like I need something I could hold on to and like read counters and snapshot and rewind in time and move because that is the way that I think and I manage networks. And short of that, I'm trying to recreate that abstraction by running around. A quick follow up of that. So if I interpret you correctly, what you're saying is that suddenly the new operational model that you're saying is that fundamentally networking makes business sense due to the fact that it's a communication model which follows the VM abstraction that we have and suddenly ties the whole thing together. I'm just saying that if your goal is to change an operational model, like prior to compute virtualization we had tons of compute virtualization but we didn't have VMs and as a result you've got a bunch of disparate virtualization technologies that virtualize IO and virtualize memory and virtualize CPU and that's great but it doesn't affect my operational model. It's the exact same thing with networking which is like we've got awesome virtualization you can solve awesome problems with it but I don't have a virtual network abstraction so I can't change the operational model because that's what operators do is in many cases it's funny if you look at a lot of these large cloud deployments that are using traditional networking technologies these guys are like hand creating crappy virtual network abstractions. I mean that's what they're doing and they're trying to do this but they're like they're not all that abstracted because it can only be L2 or you don't aggregate stats or you lose things when things move around. So all it's doing is taking all of the virtualization technologies that already exists like tunnels, like overlays, like whatever and they're saying here, virtual network abstraction. I'm so glad you brought up that point because it's really important in this discussion. Excuse me, so I'm wondering what your thoughts are on there's concern, I don't know if it's valid or not but there's concerns about doing a lot of the networking heavy lifting in software on X86 versus doing it on Silicon. What are your thoughts on that and do you see sort of the heavy lifting of virtual networking being moved up into hardware like having switches and routers aware of SCT and so forth? Yeah, yeah, so this is a good question. So I wanna take it back to like the previous, the first time that I talked about which is like today, I don't know if this is true but I believe if you spin up in UVM 30% of the chance it's already all of the heavy lifting is being done on software on X86. And then we've been doing this for 10 years. I mean this is how you do it in platforms of services. This is how you do it in a lot of these web clouds. And if you look at it like you've got great throughput, you've got security, you're doing all of the things you're doing on X86 today already. So certainly just from like an intuitive perspective. Like remember on X86, you don't have aggregation. I don't have to do 48 times 10 gig. I've gotta do one times 10 gig and I already have to do it for the entire software stack at the edge already, right? I mean it's like just because I went from having to an application level segmentation to a network level segmentation it's not like it's more work. So I mean if you look at a crash section of again not the data centers that I'm typically working with but other ones where you already do this you can make very, very simple arguments of this is a fantastic way to do it. The convergence properties are great. And if you do all of this phenomenal stuff at the edge already and then you don't have to have the discussion anymore. When it comes to networking we're not comfortable with that yet. And we're still early in the technology cycle, right? And so like implementations may not do the thing. I'll tell you where STT came from. So way back when when people heard overload they would puke just because they've been doing networking for a long time and like anytime people deal with tunneling it's been a very complex thing. Now the reality is if you look at a large web data center it's an overlay, right? It's an HTTP overlay but it's definitely an overlay and it's definitely an x86. And so we started looking at the performance as okay if I tunnel from a V-search to a V-switch like what's the most expensive thing? Well it turns out the most expensive thing is the interrupt between the guest and the hypervisor. That's very expensive. You trash your TLB, you've got your memory copies, this is an expensive operation, right? So when you do something like TSO, TCP segmentation offload I'm setting a 32K frame to the NIC instead of a 1500 byte packet, right? So like I've got this massive interrupt coalescing and like anytime that you throw a tunnel header on there we're like oh all of a sudden like it doesn't know how to interpret the packet I can't get hardware segmentation.   So this is like a system solution solving an end system problem that have nothing to do with the network but then it all becomes like a networking discussion. And so I think we're, I think technically clearly you can do it in X86 because we do all the time. And I think that trend is done if you look at the majority of systems that are being built. And I think it's just time that we get comfortable this happening on the networking side. I'm sorry for that long-winds and passionate answer but like it's a really important point. Any other questions? Please. The VLANs, there's a certain maximum in the standard and I thought I'd heard that OpenFlow would allow you to go beyond, I think it was 65K to allow scalability. So that was one thing that maybe you could do with network virtualization if that's true that you can't do just in a normal kind of hardware environment. Yeah, so I think the coolest thing about network virtualization at some point people are gonna stop working about protocols and they're gonna start worrying about virtual networking like abstractions which is the reason that you have things like VLAN limits is because at some point someone's like this field is this large because some hardware interprets it as this big, right? And so you've got these limits that get baked in. But let's imagine OpenStack and let's imagine Quantum. Like with that you don't know what protocols are running and yes it's important from an operations and management standpoint but it's not important from an operator standpoint. So like if all of your operations is against a virtual machine or virtual network then independent of how that's implemented on the bottom it's still going to be the same. So if you have some sort of a limit you can change that limit and not change your operations. And so yes, VNs have limitations.  New protocols will have limitations but I think the macro level point here is like if we could just stop getting mired down and mechanism in detail and focus on abstractions and value we don't have to have these discussions that end up going nowhere. And kind of a macro level point of my talk is like I think we're actually starting to get there. I think we're actually starting to move past that like my architecture is better or worse than your architecture. I actually talk about products and systems that are being built. And we went through the same pain in the compute virtualization phase. The same pain. But I think that we're coming out of it. I'm glad you brought that up. Any other questions? Cool. All right, thanks very much guys.


Let's gather around the campfire and sing our campfires on You two was good man and today we bring ourselves on Angela's Asylum Now this is like a modded version but it has like spongebob in it I'm not sure man so let's go ahead and begin with this and I don't know what the heck is wrong with spongebob but this game is definitely cursed as there's like a devil star on the ground all right let's begin make sure to smash the like button subscribe and turn the notification bell if you're new to the channel okay what the heck is going on yo my boy you good I don't think he can think straight with that axe through his head okay why okay okay we have a flashlight I'm like bro it's like really dark in here okay nice uh what the heck is this oh that would look like Carl Weezer man all right uh this is strange I'm not too sure what is going on in here but we are clearly inside of an asylum okay nice I swear I'm not crazy it's spongebob bro what is up with these pictures on the walls like they're so freaking weird wait I hear I hear the noise okay let's keep going hey Patrick hello Patrick what are you doing here it's okay Patrick chill out my boy is everybody forgotten nobody loves me anymore this is pretty sad was that Squidward I don't know if that was suicide Squidward it was just Squidward himself he came and snatched up Patrick wait I can still see him hey I see I see you right there I see you Patrick okay we can clearly still see that Patrick is right there I'm trying to get up on this window so maybe we can get a better view of him okay we can't this is impossible I'm sorry Patrick you're on your own brother sometimes you just gotta let people die you gotta sacrifice man okay uh what look there's another one of these bro what is wrong with those pictures they're freaking me out okay uh empty room all right let's keep on going it's so dark in here and why is this asylum like insanely humongous okay what does that say goose goose humps what okay whatever man let's just keep the heck is that what okay what is this bro what the heck is this it's so weird and that guy looks very creepy looks like a robot okay I'm not sure what this is it is fairly weird though I don't know why I can't stop staring at this man though like his face structure kind of looked like the handsome Squidward can someone explain this to me all right I'll see my way out dude I don't know what the heck that was that was probably like one of the strangest things I've ever seen and what that that's a giant jellyfish oh he's breaking some ankles better watch out I want to get my ankles broken what is this game bro all right uh KK was here what the heck is KK bro all right let's just keep moving oh there's a red light okay let's go check it out let's see what this is all about press either interact okay it seems like we have to turn this on or something maybe we have to go like flip a switch okay oh there's a door okay nice what is this all some snail stairs what the heck just happened there okay um can I just jump off oh that is 100 faster okay um where the heck are we at now there's a bunch of rooms but they're all they seem to be empty I guess this is where they kept all the crazy patience okay there's something like a podium up here oh that's the lever we're looking for okay press either interact uh what did we just do oh wait what why is there a bunch of mr crabs why do they all look like EXE now bro oh god this isn't gonna go oh my god they keep coming out what in the world did we just get ourselves it's a gun dude there's a whole army of them okay whatever go go go oh my god it's gonna take forever to climb up why isn't there an elevator like why oh my god we're falling okay I think we lost them did we lose them oh we definitely did not lose them bro they are legit coming up this third case all right uh let's get out of here before they catch up to us because I do not want to die by the stampede of mr crabs are they coming this way are they still coming okay I think they got lost that's the right suckers oh they're coming this way wait what what spongebob what that's a spongebob from the menu oh my god okay uh I guess we're supposed to grab the water no you were not getting you got the water okay that is clearly Peter Griffin's laugh is this really the ending to this feels like we played a troll game or something all right well that might have been one of the weirdest spongebob horror games I've ever played like what was going on in that place and who the heck was that weird guy on the tv bro like I couldn't stop staring at him it's like he was hypnotizing or something in the oddly way whether you have it ladies and gentlemen angel as asylum I'm pretty sure it's an actual game and like I said I think they just modded it and they put spongebob in it like the whole little spongebob characters I don't know pretty weird pretty strange you all thank you guys for watching thank you all for the great support if you enjoyed the video make sure to slap the like button if you're new to the channel make sure to subscribe and turn that notification bell on and hit all notifications and I will see you guys in the next one


Time here for more systems and we're gonna talk about virtual machine memory management and XCPNG and how you set the dynamic memory and how you can change it dynamically on a running VM. Now, I bring this up because there's a few caveats that I wanna make sure people understand about dynamic memory management and what happens when you over allocate as in, you've assigned a group of VMs that cumulatively have more memory needs than the host can provide, but there's ways you can set a dynamic sizing on there so that they can, well, keep running and keep working on that particular host. Now, where someone can get into trouble is if they live migrate this, this came up during a consulting call because when you do a live migration and there's dynamic memory options set, well, it will reduce the host to its lower dynamic number. That's what that dynamic number is for. Before it moves it over to another host and then re as it's called balloons, the memory backup to the dynamic maximum that's been set. So I wanna walk through that process and yes, this does work with virtual machines that are built in Linux and in Windows, provided they have the Zen agent running and loaded on them. That is a prerequisite for this to work properly, just so you know. But before we dive into details of this video, let's first, are you an individual or a company looking for support on a network engineering, storage or virtualization project? Is your company or internal IT team looking for someone to proactively monitor your system security or offer strategic guidance to keep your IT systems operating smoothly? Not only would we love to help consulting your project, we also offer fully managed or co-managed IT service plans for businesses in need of IT administration or IT teams in need of additional support. With our expert and solve team, we can also assist you with all of your structure, cabling and Wi-Fi planning projects. If any of this piques your interest, fill out our hire us form at laurancesystems.com so we can start crafting a solution that works for you. If you're not interested in hiring us but you're looking for other ways you wanna support this channel, there's affiliate links down below to get your deals and discounts on products and services we talk about on this channel. And now back to our content. Now, the first thing I wanna talk about is just how we set the dynamic and static and what those mean when it comes to setting memory limits. So we're gonna go into the VM, we're gonna go over to advanced, we're gonna scroll down over here. The template that you use to build your virtual machine will set the static minimum right here. So the static minimum is two gig. The difference between static max and static min and we'll actually go ahead and try and change this here. We'll change this to 32 and we're gonna get an error message that setting on VM Tom Wendell's memory, VM state is running and should be halted. You cannot change the static limits while the virtual machine is running. These are the limits that you have set but what you can change is the dynamic ones because if I don't wanna start a VM, restart a VM or stop and start the service and change memory settings, maybe I wanna bring it down to its minimum and then bring it up to its maximum of, well, 16 gigs. But if I tried to say 24 or even 32 gigs, it won't let me change it to a maximum above what those static limits are set. It's really that simple. You set these so the system understands the potential for this VM when it's not running and then the dynamic and lower and upper limits are set so you can change it while it is running. Now the things and considerations to take. When you migrate the VMs and we're doing that and showing that in a Linux VM to show how it's reduced, when I move this live migrated, it will actually reduce down to its minimum and that's one of the reasons that set. The reason it does that is to, at least the way I understand it, when you migrate a VM, it makes it faster by saying, well, we aren't gonna need all of this memory so we're gonna reduce it to its minimum, migrate it over to the other host and then expand it or balloon it back up to its maximum that you have set in these dynamic ranges right here. But this can obviously cause a problem. If I have it set to two and the application is running, still require more, it may have some trouble during the migration. So you may wanna set that to at least the minimum that this would need when you're doing the live migration. If you're not doing live migration, it'll still dynamically go up and down but actually let's just show you how you can dynamically in Windows, change the memory settings and what happens. So currently it has the maximum right here of 16 gigs that we can set. We can see that it's eight gigs now so we look at here in the stats and you can see I've actually played with this a couple times already, changing it just before I started the video. So let's go ahead and change to 16. So we'll just take this running Windows VM and hit 16. It turns yellow for a second since it's changing dynamic memory. Now it's changed. Let's go over to the console on this real quick and it's a little big because of the screen size I have here but we'll go ahead and open up the task manager, scroll up and you can see, hey look it has 16 gigs of memory showing in here but we're gonna do this in Linux and play around with the settings and show you what happens when you over provision things and how it balances all of that in some of the things that change with it. So we're gonna go ahead and stop the Windows one and let's go over to our Linux ones. Now first thing I wanna do is go to this first VM that we have, go to advanced and just see what it's set at. So we have it set to four gigs max. The template allows it going all the way down to 512, pretty lightweight if it needs to be but we have a dynamic set four by four and I wanna leave it at that because I wanna show you what happens when we start this virtual machine and when we move it. So it's gonna start, it's right now running on the Ryzen 2 host. It'll boot up relatively quick here. Okay, now it's booted up and it's using four gigs of memory. If we log into the console, we can see that it's using four gigs. There's the memory right here at the top and let's migrate this and we're gonna do a live migration while it's running. So we're gonna say migrate, I wanna move it over to Ryzen 1. This is gonna happen incredibly fast. So actually click on task here, two, three, one, now go three. Okay, well like four seconds, we moved it over and you can see now it's on Ryzen 1 and it's still running. We don't have to restart the machine. Now because we left the lower and upper the same, it did nothing to the memory. It says, hey, the minimum this goes to is four, the maximum it goes to is four, therefore we are going to move the four gigs of memory from this host to the other host without making any adjustments when we do it. Let's see what happens though when we go to advanced here and we're gonna set this down to one. You gotta remember this is dynamic and we just can't go below this 512 number here. So we'll set this one at one gig, four gig and we'll do the same thing again. We're gonna migrate it back over to the other host that it's next to. So go here, hit okay.  And we're gonna do a bigger move so you can actually see that in action and see the memory change. Right there, you can see it blipped back and forth and so we can do that one more time back on the other way. If we do it this way, you're actually gonna watch it do it. So we'll keep an eye right here. It's reducing down the memory and then ballooning the memory back up. Now the console flickers for a second when it does the change because it moved to the other host. Hey, and there's our memory and now it's going to reinflate it back up so we're at 827. Then it's gonna climb back up as it reallocates on the next server. This is why those dynamics are important because if I had applications that were running, it's going to actually cause it to slightly hang doing that because it's going to get stuck trying to evacuate that memory while things are running. So let's go ahead and split the screen. We'll use Tmux. We're just gonna put htop here and then we're going to get it down here at the bottom and we're gonna run this command here stress-ng-vm-1-vm-bytes four gigs to allocate four gigs of memory. So we're gonna watch the memory usage at the top go, well, all the way to four gigs a little over and it's gonna start using swap because we're over allocating everything here a little bit beyond so we can leave any room for the operating system run but that's kind of the goal. This is now a heavily loaded up machine in terms of memory and we're going to try to do a migration while these dynamics are still set down really low. So we still got the dynamics set down to one gig and four gig but obviously if we're using up all that memory what's gonna happen? And I'm not exactly sure what state the VM will be in but let's go ahead and do a migration to the other host. Hit okay. One, I don't think it's gonna happen as fast. It's gonna try to do some reduction but it's not gonna have anywhere to reduce too so it'll probably increase the swap would be my guess what's gonna happen here but obviously it's already taken substantially longer because it's thinking and trying to sort that out while it does the migration. So it's still on the rise of one it's still trying to figure out how to get this memory allocation it's running some processes on there and I'm wondering if it's actually going to crash the VM all together when it does I think we may have locked it up here folks and this is why it's important to have those dynamics now this would run and it still might continue to run cause it's just stuck thinking right now oh there we go it's still going but this is when you don't have that dynamic low set to a reasonable number well let's just push it all to swap and is pushing it back to migrate yet maybe we're doing this all in real time cause I wanna show you how these problems occur when people are setting these up and why it's important to think about the workloads you have on there because when you dynamically are allocating them this is the type of scenario you'll run into easy to set up a really basic VM with no workload and migrate them in a matter of like five seconds much harder to do it when you have a workload and well I think we've actually just got this maybe it's stuck it still seems to be going here in the task so it's slowly getting here I can also just stop the process running the stress NG process and kill it and it would probably do in it so do suspend freeze process failed yeah freezing task failed after 20 seconds one task refusing to freeze I like the phrasing it uses here so the system's under high load trying to do some memory swapping around here to get this over to the other side so I think we'll stop this process real quick here before it crashes and we have to force a reboot so we'll there we go I stopped stress NG that'll probably allow this process to carry on and continue but this is why it's important that when you're setting these minimums you're considering the workload that's on there and that your minimum doesn't go below what the workload will at least need to get things done now a lot of times different tools may use the extra memory for caching and that memory for caching may be able to be reduced and you just have to test this on an application by application basis or whether or not you can do that I mean ideally if you live in the ideal world you have enough memory for all of your applications but you know the reason these tools exist is because the real world doesn't always have the ability to do that so you have a more challenging environment where you wanna get these done and I think this is gonna spend a little bit longer so we'll go ahead and actually kill this server see what status we leave it into or if it'll actually finish or it's still estimating it'll move let's go ahead and see if we'll give it a few more minutes here we'll just fast forward all right all we ended up with was an operation failed it failed to migrate the VM because of those dynamic memory problems being hit but it's on the rise in one server I had to restart that server to stop it after it failed and restart it it's ready to go again now with nothing running on it of course we're gonna go ahead and migrate hit this and now it's gonna pop itself over to the Zen 2 server back into our couple seconds to get this task done there we go migration completed it's over on rise in two now the next step I wanna talk about is over allocating the available memory and how it dynamically is going to resize these on a given host so if we look at a rise in two system here we currently have 62 gigs of free memory so there's the different things that are running on here and now let's over extend this system so let's assign some VMs with more than 62 free but they have these dynamic options that will allow them to go lower and we'll go ahead and include our window system in this as well so take the window system and it's shut down so we can adjust all these different limits and we're gonna assign windows 64 gigs on both sides we're gonna say 64 over here now the minimum windows is down to two and I don't think windows should go below eight gigs on here so here's this system and we're gonna specifically start it on that particular host of rise in two so we'll go over here we're over allocated already because there's well we're right at the limit because our 66 gigs free and we got this one signed 64 we'll go ahead and let windows start up on here and it's thinking about it right now and the reason it's pausing and thinking is cause goes wait a minute there's just not quite enough memory so it's going to make some adjustments on here and see if anything else can give up some memory get this host started all right windows has started on there and we click on this we've pretty much now filled it all up well there's 12 megabytes free so just a little bit of free space on there now let's go and look at this system here this one's got four gigs it's also running on here let's go ahead and just stop it though go over here and we'll set this one at 32 but let's only give it 16 for now we'll set a maximum of or a minimum of eight and a maximum of 16 here so we'll go ahead and also we're gonna start on and we'll put this one on rise in two now remember rise in two that particular system is already pretty much over allocated so we go over here look at rise in two and it's got to make some decisions now who's going to lose some memory well these other ones don't have those same minimum so this one does so this one right here is going to say we're gonna shrink how much windows has here so before that VM starts this is why it still hasn't started it's reducing and evacuating memory out of this one because it can adjust that dynamic and that will leave us in a free space to then start that next VM so now this VM is starting and we'll see how much memory is once it boots up we'll see how much memory is allocated to this particular system which it looks like it was able to allocate the 16 to it once it starts it'll talk to the processes running inside there and then decide exactly how much memory it needs so let's go ahead and start one more and we'll do the same thing on this one we'll say this one's gonna get this max of 16 minimum it's gonna leave it four but we'll put it at 16 maybe this one will give 32 let's go all out here you can have up to 32 but dynamically we'll leave it at these ones here and once again go up to the top and we're gonna start it on that particular VM if you just hit start it'll start on a host that has enough resources to handle that but we're gonna force its hand and say we don't care that this one doesn't have enough resources you're gonna have to figure that out and that's what the system's doing now so now it's gonna start resizing these other ones to try and figure out where it can find free memory so it's taking it away from the Tom windows again and where's that other one on here there's my other one that's already reduced this one it says you only need 13 right now it's gonna reduce this one a little bit more and then find room to fire up this virtual machine and once this one here oh there we go it's booting up and so it's understanding what processes are in there so now we have all these VMs which are technically provisioned at a rate higher than the available memory on that particular host but it just keeps reducing them so we have the min and maximum set now what will happen again and we'll wait till all these VMs are up and running which I think they should be now this one's got just a few more seconds to go and there's that ballooning message that you'll see because it's then ballooning waiting for initial ballooning down having finished that's that process that's going on because it's adjusting this dynamically to allow for that space to be had it's pretty simple once you start understanding what these numbers are doing with the dynamic and static and what's going on in the background but there's a lot of complicated things going on in the back end to make sure these hosts are working and this is where as I said you can get yourself into trouble especially if you don't understand the workloads and the minimum requirements of your workload in order to make this happen because right now with these having pretty much no workload on them with lots of free memory it's easy to balloon them but that ballooning process will run into some limits if there's just tools like StressNG running that say nope I refuse to give up my memory I need this much memory it's locked in here and you'll start having VM migration problems but we'll show you what happens now when we migrate it because now that we've got this completely filled up again with these different VMs how do we free up some space dynamically well that's pretty easy so we'll take and log into one of these like this one here run H top so we can see the memory we've got 12 gigs we've got a maximum set right now that it's 16 gigs and how do we get that extra 16 well now we got to take this and migrate it over so let's go ahead and migrate this over to the other one that has plenty of free memory in it and that will happen relatively fast but you got to remember it's actually gonna shrink down first because we have that minimum set so as it kicks off that process it's going to reduce the amount of memory so here we go watching it go down and that's gonna be based on that dynamic minimum we set of eight so it's gonna go all the way down to eight and once that completes it'll migrate over to the other VM while they're host and then expand it back out probably to its maximum because if I had to guess and even though it's eight right now let's go ahead and look at this we look at this one here oh there's plenty of RAM we've got 72 gigs free so it shouldn't have any problem at all expanding that one out and it's already done that so we go back over to the council it's expanding back up ballooning it out again and you're back at the full memory now hopefully this demonstration gives you a better understanding of how the dynamic memory management works how it will allocate and why those dynamic minimums are so important that they do not go below whatever the workload minimum threshold is for that particular virtual machine and the things you have running on it because well I think that's where you can really find yourself in some of those problems of causing the VMs to crash be in an unknown state or just tell you the operation's gonna fail because it doesn't have the ability to do that now if there's enough interest I might do this for processors as well because yes you can overallocate processors it's much more forgiving when you do that when you have well 24 cores available and maybe you assign five or six VMs all those cores but as long as you're not all using it once there's some advantages to doing that leave your thoughts and comments down below or head to my forums for more on that discussion and thank you for making it all the way to the end of this video if you've enjoyed the content please give us a thumbs up if you would like to see more content from this channel hit the subscribe button and the bell icon if you'd like to hire a short project head over to laurancesystems.com and click the hires button right at the top to help this channel out in other ways there's a join button here for youtube and a patreon page where your support is greatly appreciated for deals discounts and offers check out our affiliate links in the description of all of our videos including a link to our shirt store where we have a wide variety of shirts that we sell and designs come out well randomly so check back frequently and finally our forums forums.laurancesystems.com is where you can have a more in-depth discussion about this video and other tech topics covered on this channel thanks again for watching and look forward to hearing from you


Now, a day after the Supreme Court judgment of hell, the re-election of Gaffner wrote Timmia Keridulu, members of the all-progressive Congress are celebrating the verdict. The members of the party and that of the National Union of Road Transport workers trooped out in their numbers to their governor's office to celebrate the epic's court verdict. Speaking of these men, the Deputy Gaffner said the judgment has proved to rest months of legal tussle. Defend the justices of the Supreme Court for the judgment. I'm so excited and I just say that justice has been delivered. We should give kudos to the judiciary that even though it was a splitted decision, but they see the stories in the majority, the stories in why that appeal should not hold, should not succeed. And now the distraction is over and not that governments have not started, that started, but you know it's not as if we're not focused, we're focused as a government, but you know there are distractions, there are the tribunal, the court of appeal, the Supreme Court, now all of that is put behind. So you get notified about fresh news updates.


Hey guys, it's Nate, aka The Foot Accountant. Welcome back to the channel. Happy Sunday. I hope your weekend leaks and your weekends are going well. It's Sunday and that means Mini Release Day is today and that means it's also Fofana Day today in FIFA 22 as a part of Headliners Team 2. Of course, Fofana was not dropped with the main team of 11 cards released in packs on Friday so it is very likely that he is coming out today as a part of the Mini Release and that is going to be a big talking point today on this market. I also want to take a look at just this market as a whole as we had the compensation packs finished up but it didn't really go as we had planned and as we had talked about yesterday, it seemed like EA kind of like released some and then stopped and then released a bunch of these compensation packs later on as a lot more of these Headliners are dropping more on the market because I think the compensation came in a little bit later and it didn't exactly, it wasn't continuously flowing so that really did not work how we thought it was going to but in our reality again, what did we expect, right? This was something that we had never seen before so there was always going to be a learning curve to it so now we kind of know if this ever happens again how it might kind of take place with the compensation packs but I want to talk about that and the Kloss SBC and how I feel like this market right now we got team of the year, right? Team of the year is coming, it's coming soon and I just feel like we're at a tipping point, right? We are at a tipping point where a lot of people are starting to sell some cards because team of the year is getting close. It's not like a market crash, nothing like that. It's just the first little bits of selling and I think there is going to be more of that and we're going to talk through some of that today. Also looking through all the content that we could see today on Sunday. So if you're enjoying the videos on the channel of course, leave a thumbs up that helps so much and of course, subscribe if you're new. Let's talk about today, Sunday, mini release, Fulfana, what cards are we expecting today as a part of the mini release for team two? Of course, Fulfana is the big one, right? But other names that were leaked, I will drop the link to this in the description. These are not necessarily confirmed stats, I don't believe but the players that were of the leaked team that we have not received yet of course, Fulfana is the headliner of those, Trap, Rafael Leao and Mr. Harry Wilson. I think these are the four cards that we will see on the game today. In FIFA 22, because I believe they should be dropping the mini release Sundays, usually are for those. So along with that, everybody's going to be really excited for Fulfana today. Now, with how expensive some of the headliners started out on day one and how expensive some of them still are like Vinny Jr. I believe is 1.7 or like 1.8 high or something like that, 1.7 high, almost 1.8 mil I believe if I could find the right card. Yeah, okay, 1.7 mil for Vinny Jr. I mean, I know he's one of the most overpowered and overhyped and very just insane and meta cards on this game. But a lot of these headliners have been starting out very, very expensive impacts. So I think that Fulfana today as a headliner item is going to start off really expensive. But depending on what that price range is and just, I mean, usually on Sundays you don't see the cards that come out in the mini release, they're just not cheap, right? They're almost never cheap unless EA drops a preview pack today, which again, there's a slight possibility for that. But that's the only way that I think Fulfana is going to be cheap today. I think he's going to start off very expensive. Everybody is doing the Klaus SBC right now. Everybody is having, you know, a lot of people are using Genduzi, a lot of people have done Awar. It's just a lot of French links in people's clubs right now. So I think that Fulfana is going to start off very expensive and of course there will run lightning rounds today. The real question is will they do a preview pack? So besides the mini release today on Sunday, what other content could we have? I think there's a couple of things that we have on the radar, right? And these are technically leaks, but they've dropped icon SBCs, icon player SBCs before on Sundays. And we have two icon player SBCs that are leaked at this time. That is Baby Seedorf and Prime Furnando Torres. Prime Furnando Torres is really cool, right? That's a cool and that's like relevant to the stage of the game right now. Primes have been in the game for like what? Three weeks now and they're dropping another Prime icon SBC. I like that. I don't understand Baby Seedorf unless Seedorf's SBC is gonna come in at like 150 or 200,000 coins and be very, very cheap. I don't really understand that one. I don't know if that is today either, but I think Sundays have been days they dropped player icon SBCs before. So sometime either today or later on this week, I would expect those guys. There's also a bit of a leak for a ZH SBC. It's confirmed to be right wing. It is definitely not confirmed to be coming out today, but soon evidently we're getting a ZH SBC on this game as well. So I would say there's a higher percentage chance of Prime Furnando Torres coming today and Baby Seedorf is icons. Not a very high percentage chance, but that's out there. It seems more likely to be in ZH, but we will see, right? We will see, of course, those are just leaks with no date in mind and we'll probably get some more information on that today or be watching the Twitter machine as a lot of those leaks get updated almost daily. So we'll be keeping on for that, but really for Sunday content, the mini release is probably gonna be the most hyped thing. Maybe an SBC and other than that, I wouldn't expect too much on this game. I think we have like a pack supply SBC as well. Yeah, performance is key. They dropped that, I believe that was either yesterday or two days ago. So they've been dropping a few of those. I think they dropped a kit or something like that as well. But anyways, Sunday content today will be basically dominated by the entrance of Fofana onto this game. That's what's gonna be the most hyped thing about today. But let's talk about the market, right? Because we have compensation packs that EA have said have been all paid out. And as I'm looking at the market right now, I mean, I can see that, right? I can see some prices, especially on the headliner that was just looking at headliner Kimmich down like 20K from where he was just a couple hours ago when EA tweeted that the packs have been fully compensated. Yeah, down here at 130, 140,000 coins. There's been a bit of a drop off because I think people have received those packs. Now a lot of you guys in yesterday's video, when we were talking about the compensation packs, you were like, yo, Nate, I don't have these back yet. It seemed like EA said, update, we have started reaching out to players, this process will take some time and we will keep you updated. So it seems like they started the process because some of you guys messaged me like, yo, I got my packs back.  They tweeted this just a couple hours ago and they said, hey, the correct content has now been provided. And I had a lot of you guys tweet me, say, yo, I did end up getting my packs. So I think all of the compensation packs are out now, but that really didn't go is how we thought it was gonna be planned, right? I was really expecting, let's take a look at Kimmich's graph, right? You see this last night, it seemed like they did compensation because from Friday night Kimmich went from 200K, high 100s, they compensated with some packs. He went down to 170 and then it seems like they stopped for the night, right? They didn't give any more out. So there really wasn't a drop yesterday morning, like I thought there might've been. Then what you really saw was a drop into the content time, then a rebound because the content yesterday was not that insane. And now Kimmich is back down again as people are packing this card from EA giving out the rest of the compensation pack. So it's just a crazy situation. And again, this is something that we have never seen before. So we didn't exactly know how it was going to look, but EA was just all over the place with when they were giving out these packs. So it's nice that it's done. We don't have that looming now for this market at the moment, but I do think that it has caused for a lot of these headliner team two cards to be supplied a lot extra than headliners team one. And of course the team of the week that is currently out. So just being mindful and being careful of that, Teate was like 90,000 coins yesterday. He's dropped off a lot. Again, he was 97K down all the way to 60K. He was even at like 57. Now he's back up a little bit. So, we'll have to keep an eye on these headliners because again, there's gonna be more lightning rounds today. There's gonna be more people focused on the brand new mini release today and stuff like that. So that's the whole compensation situation that is done. It really didn't cause like a market crash. I think it really affected the headliners and the current team of the week price is the most on the game because of that situation. So that's just kind of something that is kind of wrapped up now. Who knows if we'll see something like that ever again. That was just kind of a crazy thing that happened, right? With EA giving back so many packs. Who knows? We might see it again. It's just kind of something to put in the archive to say, all right, if this happens, it's gonna take EA a long time. So it just feels like that that has also kind of put a level of uncertainty on this market right now. And that's kind of what I wanna talk about is with the Klaus SBC yesterday and a lot of prices that I saw yesterday just around the market as a whole, it really feels like we've kind of reached the tipping point going into team of the year. And I think this SBC and a lot of the other good value SBCs that we have seen recently like Odson and Ward has been decent. Ben Rahman was pretty good.  I mean, this is an item that fits exactly straight into my team. 93 pace, 80 defense, 82 physicality. Again, the live upgrading aspect to this item that it is, it's only 70,000 coins. And take a look at the thumbs up that this guy hasn't flip in. There are two agendas right now that EA is pushing in this game. They are pushing Premier League and they are pushing French. And they are pushing the French agenda so hard. I mean, think about the SBCs we've had in the past couple of weeks. Edward, Payet and Klaus, even in the last few days, three French SBCs that have been, you know, perfect for people to put in their teams. At the moment, so many people are using French squads. Fakir, Benzema, that's all that I see in a weekend league, right? And this guy, I mean, I tweeted it out yesterday. I said, this is giving me FIFA 19 Kenny Lala vibes. If you guys remember the Kenny Lala from FIFA 19, I have to show you the card because this Klaus with 7,000 upboats and only 70,000 coins is reminding me of this card, right? Everybody used Lala in FIFA 19 and it almost feels like this year's Lala is Klaus, right? So a ton of people are doing this SBC. I'm probably gonna get it done myself. Again, since there was such an insane amount of demand for this card and since so many people are switching up their teams to include that Klaus item, you saw right backs from across the game dropping price loads yesterday, right? Take a look at some of these other right backs. Treyore is down. I wanna look at Mbabu. Where's Mbabu? Akimis, I bought Akimis at 123K, sold them at just over 130. He's now down to 109,000 coins. Atolls, signature signings, card is down a bunch. Take a look at this Mbabu, right? Mbabu was so inflated because he linked to the brand new Zacari objective, right? This guy went from 130. He was all the way up in the 155K range and then Klaus comes out and he goes all the way down to the low 120s where he's kind of been, he was 117. Now he's kind of rebounding back up again. This would be a card that you saw him here on this big price drop off. That was probably a decent investment, right? Out of packs item from a totally different league, right? If you were running a league one team, like look at Akimis. Gold Akimis has gone from like 26K to he's like half the price. Yesterday he was 27,000 coins and look at this drop off, right? So many people are doing this Klaus. But guys like Mbabu, I think you might see a bit of a rise on him. I think you might see a bit of a rise on a guy like Trent Alexander Arnold. Or I didn't even see it. Did Reese James drop it all yesterday? Cause that's a card that is a live item, brand new from team two or team one of headliners. Reese James really didn't drop that much, 133. So he's down maybe like 10K. So that's not that big of a drop. But like that Trent Alexander Arnold card right backs across the game are just down bad because of the Klaus card yesterday. So some of those other than league one, like Treyore, the Hakimi special cards, it'll take a little bit longer for them to bounce back since Klaus is like a direct substitute replacement for them. But guys like Mbabu that link to the Zakaria objective or maybe Trent Alexander Arnold with, you know, looks like we might be getting Hakimi right wing soon. Again, you think about even the Reese James that there's more panic selling on a Reese James item. That could be a potential card you maybe look to pick up. As I know, a lot of right backs are panic sold on this game because of the Klaus, right? And then you have the other side of the coin, right? Is it so many people are buying cards to link up in their teams because they're doing the Klaus SPC and take a look at this Niikate card, 145,000 coins yesterday, SPC comes out, boom. 166,000 coins, he's 160 right now. So a lot of your French links are up. Where's like baby Desai and out of packs center back icon, 790K. So this guy is up like 30, 40,000 coins as well. Cause usually he's in like the mid to low 700 range. So I would watch all of your French icons. I really would, especially if they're out of packs, especially if they're defenders. This Blanc is actually down 575, it's kind of an undercut. I just think that Blanc doesn't have the hype that he used to have, but this would have been a card that I maybe would have expected to rise a little bit yesterday. Looks like that he didn't. Your Gen Duzzi card, did Gen Duzzi rise? Cause right now it shows him as 264, but I'm really curious to see if he actually went up when the SPC came out. Yeah, he did. He was 259, then it went up to 272. So again, the French links right now are what everybody's using, right? Al Santrini 107, that is up in price. So it's crazy to see the amount of hype that is pressed on the French links at the moment. But that's also kind of with this market and what's going on right now. As we head towards team of the year, I think what I'm also starting to see is that a lot of cards from older promo teams, you know, they're starting to drop off just a little bit, right? I was just taking a look at Zlatan's price. Zlatan Ibrahimovic, he has been down a little bit in the past few days, but Zlatan was like 2.7 mil, I think he's 2.74 right now. 2.74 on the market versus Zlatan. He was just like 2.9 mil, two or three days ago. I'm taking a look through some of the other wild card items. Paul Pogba, I've been noticing him. He was like 1.1 all of the last few days. He is now closer to like the 1.04 million coin range. So he is down in price. Fabinho is down a little bit. Modric who was usually in the high 800 range, almost 900,000 coins is right now about 830, 825. So it almost looks like that some people are starting to sell off some of their cards as we get into this, you know, team of the year timeframe, which is completely natural, right? And we kind of expected, we don't really expect a market crash. I mean, think about what happened for Black Friday. You know, you kind of had about a week and a half or two weeks before Black Friday. You had EA of course, they went out and they crashed the market themselves. But on these out of pack special cards that you see starting to drop a little bit, I think really what this is is people that are just getting ready for team of the year. That's really what I think that is. Look at Val Verde, right? Val Verde was like, I saw this dude at 677, 680K multiple times during the past week. And he's been in the low to mid 600s, like all day yesterday and even into today as well. So it seems like people are starting to maybe start to rock those untradable squads. They're starting to think about team of the year. Of course, as EA is putting out more of those team of the year votes. And you know, we're gonna have the defenders announced today on their Twitter, the defenders, that are gonna be in the team of your vote, which starts tomorrow on Monday. So that's gonna be out there. Wow, a tall is down like 25,000 coins because of Klaus, that's kind of crazy. That's a big drop there. But it really just seems like this is kind of the tipping point. I don't think that you're gonna see a huge market crash this weekend. But if there's a couple cards from your team that you wanna, you know, maybe get out, right? Maybe you have some winter wild cards in your squad, like Sterling, maybe it's, you know, Lucas Mora, or maybe it's even like Sayonche. Like Sayonche has gone up like 30,000 coins. Maybe he was 47K, now he's 90,000 coins. Some of these cards throughout this next week, I think it might be a decent shout to cash out on a few of them. Of course, as we start to get in this team of your timeframe, again, I don't think it's really gonna be like, it's not gonna cause a market crash. And we're not gonna be seeing prices drop a lot on this game unless EA really want the market to drop. Sometime in the next couple of days, I don't think you're gonna see people just outright sell their teams for team of the year. But prime icons have been another place in the market where a lot of prices have dropped. And that, again, just kinda shows me that people are starting to prepare for team of the year in the sense that they're just, you know, maybe it's a supply from some of the lightning rounds as well. But this drug has been 1.1 million coins for the past like two weeks that he's been in the game, right? Now he's down under a million coins. Where's Rio, right? I've been watching Rio pretty close. He's usually like 1.3. He's down in the 1.2 range. I think he was even lower. Roberto Carlos is an icon that I often flip and he's like been 1.2 to 1.3. Okay, so he's still 1.3. But I've seen icons from all different levels. Prime Maldini, where's he at? Wow, 3-3. This guy's dropping a lot too. So it just seems like this is the tipping point as we head closer and closer into team of the year.  Upgrade packs, you know, we still have heroes in this game that people think are gonna get upgraded or have new versions of them coming out soon. So like, Ginola is 1.2 mil flat right now. He is down a bit in price. So just keep an eye on that. That's all that I would say over these next few days. And really watch the headliners from team two as well. If you guys remember last week with headliners team one, a lot of the headliners were cheapest, kind of on that Sunday, Monday timeframe. I think people are gonna, you know, remember that from last week. And I think you're gonna have a lot of people investing in headliners team two cards this weekend, whether it's today on Sunday or maybe Monday with foot jams rewards. I'd be careful with these because you might see some people selling these off today. Again, with a little bit more supply, but then you might also have a lot of demand as people look to buy these back up, heading into this next week because they're live cards. Headliners from team one have exploded, right? Here's a specific example. Mr. Nkunku had himself a little one goal to assist performance yesterday. He is up loads. This guy was 490,000 coins on Friday and he's 640,000 coins right now because of that potential upgrade that he has. Even the cards that aren't even getting upgraded, like Van Dyke is up 100,000 coins. You've got Kula Bali is up a little bit, Nabri is up, Savarnir has gone from 80K to, what's Van Dyke right now? 770K, 765, that's crazy. That's crazy. Savarnir was 85K, he's now over 100. Carrasco, Acuña, Luis Diaz is up like 30,000 coins. So I think that a lot of people are going to be looking to invest in these headliners from team two because they've seen the insane rise from team one. So just kind of keep that in mind that buying early on some of these cards might be a bit of a play, albeit still a bit risky. There's going to be a lot of people looking to invest in these and I think with good reason. But we'll just kind of have to keep that situation in mind as we head throughout this week of headliners team two. So again, just a little bit of a backdrop. Again, today, content on Sunday, the Fofana, the mini-release with Trap, Rafael Liao and Wilson would be the most, almost 100% expectation for today's content. Maybe Prime Icon SBC for Torres and that baby C-Dorff that has been leaked and maybe a ZH or something else. I wouldn't expect it to be an insane day unless they drop a preview pack. So that's kind of today's video on the channel, boys. If you did enjoy it, smash the thumbs up on it, comment down below if you have any questions and of course, subscribe if you're new. It's been Nathan Putacown. I will catch you guys later. Peace out.