 So, Patrick talked about GE's usage of that new model that we were talking about, remotely managed private cloud. Something else that I mentioned earlier as an emerging use case was edge computing. And you know, when people think about edge computing, and I know that this is how I looked at it a lot of times, I often thought about the telecom opportunity. Tens of billions of connected devices all over the world that need to be networked and how that's going to put a lot of load on telecom networks along with VR, AR, all of these different use cases. But what's been interesting for me to hear over the last few months, I've seen a big spike in interest in other organizations and other industries as well who are looking to do more edge computing in industries like the retail industry for use cases like oil rigs, manufacturing, self-driving cars, hospitals, you know, on and on and on. And I think that the reality is that we are collecting so much data at the edge that we can't send it to central data centers, whether that's public clouds or private clouds. And so, you know, this is, I think, a huge opportunity and a big use case that we're going to see a lot more of. To talk about one particular application of that, we've got our next user, Verizon. So help me welcome Beth Cohen. Thank you. Thank you. So I'm here to talk about OpenStack as we are using it out in massively distributed. So let me start with what's, so OpenStack traditionally has been limited to the data center, which is all well and good. Everybody, you know, there's, as you can, as you've heard, it's been really successful. But that's not good enough for Verizon. Because Verizon, of course, is a networking company, among other things. And so we need to have OpenStack be, we need to reach out to the edge. We need to be in the data center. We need to be all over the place. So how can we do that? So let's see how that is done. So a couple years ago, Verizon announced its software-defined networking strategy, and my team was asked to deliver actual products to meet that strategy. So what we needed to do was we needed to create products, and we needed to deliver them faster, and we needed to deliver them to simply, reliably, and securely. So what did we do? We talked to our customers, and our customers said, what do they want? Security, of course. And they wanted routing. They wanted software-defined WAN, which, of course, is the latest emerging networking technology. They wanted WAN optimization, and they wanted a whole portfolio of other network services. So in addition, of course, we had a number of challenges. We had a whole portfolio of vendors we wanted to work with. We wanted to automate our service delivery and tight hardware limitations, cost constraints, and, of course, the usual resource limitations. So what did we do? OpenStack to the rescue. So OpenStack offered standardized management tools. So OpenStack, so we needed standardized management tools. OpenStack gave that to us with open source and a set of tools ready-made. So we were also working with a portfolio of vendors, and, again, OpenStack gave us a common platform that the vendors could work with, which made it easier to integrate. We also had common, robust APIs that we needed, and, again, OpenStack had those familiar tools that we could use. And, of course, we had the aggressive dates, you know, delivery dates, and OpenStack platform gave us a leg up to get there. So the choice was obvious, right? OpenStack. So what did we do first? We built our hosted network services platform. This is a global data center-based platform. It's delivered all around the world. And it's used for both internal and external customers. So we have internal applications sitting on it, external customers. So it has to be good. And we built it for high-performance networking workloads, which is very important to us, of course. So then what we did is we built the new thing, which is the universal CPE. And here I'm going to work all over here. And this is it. This is OpenStack in a box. So very compact platform. And you'll notice we used the same components in both. So how did we manage to cram it into this box? We containerized it. And, of course, we needed to minimize the size of the OpenStack footprint because, of course, what's important in here is the services that we're going to sell to our customers. And so that's where we're going to generate revenue. And it has to be robust because the coffee shops of the world just want something to work. We have LTE capability built right into this box. So with that, the other thing that OpenStack gave us is a massively distributed OpenStack. And we could use the same cloud management tools across the entire network. And so we could scale this up to thousands or hundreds of thousands or millions of nodes, all powered by OpenStack. So we put it all together. And we created a product called Virtual Network Services. And it has the flexibility to deliver on the premises with this box. And it also has the capability of delivering in a hosted environment for customers that want to be near the core with their cloud applications. And it can be done with both, too. And it all matches in with our customers that have legacy environments as well. So it delivers that great deal of flexibility that customers are really looking for, rapid scaling and seamless delivery of their applications across a portal experience. And how do we do it? Automation is the key. And orchestration is the tools and the technology that delivers on that promise of automation. So that allows us to do fast changes from the centralized portal. We've automated ordering, provisioning, and operations, which allows customers to change service levels, sizes, and features all from a single portal. And with that, let's see it all work. So the portal pulls all network management, analytics, network optimization, and, of course, that security altogether. And it all comes together with Virtual Network Services. So here's the portal. So the first thing I'm going to do here is I'm going to add a new site. So this site needs software defined networking and security. And it gives you some options, some pre-built options. You can change them if you want. But in this case, we're going to go with a pre-built option. So we want to go with SD-WAN and security. And it gives you size options, which are based on the network size, service options based on the feature set. You can also have automated policies preset. And you can apply the policies. And then you can review what you did to make sure that everything is all done. And then we are going to confirm that we're deploying this out to the site. And as you can see, it's going ahead and deploying this. So the next thing I'm going to show you is that there's a couple sites that need some attention. You'll notice there's two sites there. So we're going to go to the first one and see what's going on. So it looks like both sites need upgrades. The first site looks like the SD-WAN is oversubscribed. So we need to take a look at what's going on. And we have a whole bunch of tools to make sure to check what's going on. So reporting. So let's go and check to see what's doing. And it says, oh, looks like the capacity's oversubscribed. So we're going to go ahead and change that. So it says, oh, and if you want to do that change, you need to change the circuit size to match. So again, we're going ahead and we're changing the circuit size on the fly. So it says it's been updated. And now we can go ahead and make the change to the SD-WAN service to match. So we're going to go ahead and deploy the service. And now it's been upgraded. So let's go back to the second one. And as you can see, it's been deployed successfully. And you can check the site details to see where it's going. So let's focus on the second one now. Again, SD-WAN is the issue, needs some additional services. But in this case, it's caused by traffic congestion, as you can see from this report. So what that means is we need to change the bandwidth. So we're going to go ahead and upgrade the bandwidth again to reduce the congestion. So bandwidth has been updated successfully. And it says, go ahead and restart the service. So we're going to restart the service. So that's what's going on now. And as you can see, it's instantly applied the upgrade and reduced the congestion. In addition, there's also reporting capabilities. So you can see how many licenses you have. You can see the security threats blocked additional information about your virtual inventory and your service requests. So this portal gives you a huge number of tools to really manage your network in a whole different way. And so now I invite you to we're going to be talking about more about the details of how we actually did it this afternoon at our use case study. And I invite everybody to join us, where we talk about how virtual network services all fit together as a product, and how we used OpenStack to really make that all work. And then I just want to do a shout out to the folks here from my team, Glenn and Jason and Mark, who all contributed to making this a success. Yes.