 All right, hi everyone. Thank you for being patient. Appreciate everyone being here today. It looked like a great turnout. I did not get to come last year because my sister decided to have a university graduation at the same time, so I hope my team did a great job representing VMware last year. But my name is Marilyn Basanta. I'm a Senior Director of Product Management for VMware's Edge Compute Products. So today, I realized after we submitted the keynote talking, as you guys heard, we both had two people who decided that Sharpen Your Edge was the right title to go with, so I think we all used the same chat, GPT prompt. And so I'd like to talk to you about these three different themes that we see come up with our Edge at Enterprise Deployments, especially over the last year, as things for us have accelerated and we've made a lot of great progress at VMware with our Edge portfolio and our products, especially our Kubernetes offering. I would say that's where we've made the most leaps and bounds in how we're gonna support apps at the Edge over the last year. We had the most recent Kubernetes release that we just had end of January, we had a lot of great things that I can cover that'll help accelerate deployments and applications at the Edge. So I'll cover these three themes. First is around scaling, large scaling and efficiently. And this is definitely a very difficult problem that I don't think any of us have yet solved. We can solve different aspects of it, but it's really how we're gonna bring all of it together and scaling your edges out. So the first thing I see come up is how are you gonna manage this? Everyone wants a cloud-like management experience for their Edge. At least that's what I'm hearing from our customers. How do we make this easy and holistically give you that one view where you have all your edges, you have your policies, you have your security, you have your applications? So how do you make this super easy to manage holistically? So this is something we've been working on with our own Kubernetes management console, but then how do I up level that even further, not just for Kubernetes, but for everything else adjacent to the Edge, or all the different other applications and the tooling that you need? Another thing that is very important for us to be able to scale efficiently is working on how do we make it easy for it to be scripted? So this, we're working on more of a get-ops approach for this, and we have some interesting projects that were announced last fall that are now kind of converging together to give people a different, some people will want an easy UI, other people will wanna take control with scripting, and how do we take that approach to not just the Kubernetes offering, but everything else and how you define your Edge sites. Another piece is how you design your Edges. And so what we've seen at VMware, people wanna deploy Kubernetes in lots of different ways. We just recently introduced some single node clusters, but we've got a reference architecture, different designs of how some people will need to scale their Kubernetes offering differently. And then separately, in which of course is very important is how do you handle these costs? So a lot of things from a business value perspective of our customers who've been successful is how do we make this easy to manage and so that way they can contain the cost. So everything's around having a killer use case or having that application that then kind of leads you into having the different applications at the Edge. Okay, so now that we've covered that's how important it is to scale your Edge, is how do we then make this quick to deploy? Cause that's the other thing that we see where there are enterprise customers who have customers coming in who know they wanna roll out a new computer vision application at the Edge and do inferencing and have real-time decision-making, but they're telling us, hey, this is gonna take years for us to roll out to all these different stores or into these manufacturing plants. So how do we get our customers taking advantage of the latest and greatest technologies that we all have in the open source community or in our here in our enterprise offerings to take advantage of the new things at the Edge? And so we're working a lot in orchestration. It goes back to what I was talking about, this GitOps approach. We're trying to make it super simple to get the infrastructure up and running and in a variety of ways cause not everyone will want it from the cloud. Some people wanna send it to their system integrators and have things staged. Other people have limited bandwidth. So it's a variety of permutations of how do we accelerate these deployments and make it easy. The second part is what I've talked about and I'll talk a little bit more about the new apps. I believe that's kind of the pitch I gave before. I love talking about the new reasons and the new apps, why apps are being deployed at the Edge, excuse me, but it's very important that we take into account the tooling, like I said, and making these applications easy to use. Things like enabling real-time functionality in the operating system to taking advantage of messaging and streaming queues to help build your applications to do closed loop automation to speak to each other. But another thing that's important that I've seen come up recently that I think is nice to point out is security. It's definitely had a bigger emphasis on security as we help our customers accelerate Edge sites. So things like Coverna, sorry, I'm gonna butcher the company name, I'm sorry, different open-source tooling and things like that that we have to kind of feed into the architecture to make sure that security is taken into account. And I'm not just talking about application security. I'm also talking physical security at the Edge locations. How do we help enable the hardware that if someone's gonna walk away from it in a grocery store or at a coffee shop that you have the hardware secure? And of course, most importantly to accelerate deployments is life cycle management. So a lot of work has also gone into how we're thinking of the life cycle management experience for Kubernetes. Okay, and then now that you've scaled your platform, we figured out reasons, important things for scaling your platform. How do you accelerate the deployment? And then so what's really driving the acceleration of the deployment? So to me, this is the most fun part to talk about. So what we're really doing, and the reason why workloads are going back to the Edge and why Kubernetes is so important to the Edge is because of the new workloads that are coming up at the Edge. And so what we're seeing this is of course in retail, manufacturing, oil and gas, power utility, the fact that everyone's on a modernization journey and their applications. And so how do we enable these new applications? In many cases I already touched upon this a little bit is their real-time applications. So if you're a power substation, how do we work with the ecosystem ISV partners to enable their application to be containerized and handle the critical optimization of power utility? In the cases of manufacturing, we're working a lot in manufacturing. In fact, this week, half of my team is here and half of my team is actually at the Hannover Messe conference, which is one of the biggest manufacturing shows. We're showing real-time Kubernetes applications there. And retail, retail is all about the immersive in-store consumer experience. Everyone's wants their experience now. So how do we help enable these new Edge workloads? So this is all about Edge native applications, which I know the CNCF have released a draft on that kind of cover the criteria of how we see Edge native applications and what makes them different. Everything I kind of talked about is very use case-based, very line of business-driven. So these are the real reasons on why we're trying to meet that use case. We're trying to say that this one use case kind of pays for the platform and then you're enabled to do lots of other things on the platform. And so to run critical application we normally see is one, we start off, a customer might start off with one use case. I would say this is a retail store with video surveillance. So if you're taking that surveillance, you have to store it for 30 days, you have to store it somewhere, you have to secure the platform, and then that video feed could be inference to serve different applications. You can send it to another device, you can send it, you can inference it there or you can need to store and forward what you need. So that's now one use case has multiple difference, serving points, storing points and capturing the video. So then as you multiply different devices in different use cases in a retail store, you then have more data sources and how do you help these applications actually communicate with each other? Then that leads to what I think is the real value of the edge, the fact that you can take all of the data sources at the edge, bring them together on a common platform that we have with our Kubernetes offering, but more importantly, how do you help these applications communicate with each other? And that could be with something like RabbitMQ because you need to capture for multiple sources, we're going to store, process, bandwidth reduce, transform and then forward. We need to process and serve it across the different edge sites for different applications and then it has to be secure. So the fact that we can help bring together a complete platform from automating, scaling and then helping build these applications and have a common communication method to make it easy to create these applications, I think are the three tools that you can use to help enable your edge and help your customers. So thank you.