 All right, let's see if this is going to work. OK, so this is the last talk of the day, so I really appreciate you staying around. I'm going to keep this quite light and fun, hopefully, nothing too serious. I have called this talk Crossing the Chasm with MultiArt, but as I said, I want to keep it light. And I also want to talk a little bit about some of my time inside CNCS and some of the stories and some of the things that I remember from that, because I think it's a different viewpoint from the community side. And so my background is, if you go to LinkedIn, this is what it will say. So I started out at Google as a C++ engineer. I moved into infrastructure, develop advocacy. I started a meetup called Cloud Native London, which has about 7,000 members. And then in 2018, I moved into CNCF. That's the kind of very glossy story. The truth of the matter is, I think I decided to join Google when I was a teenager, because I heard Google has free food and massages. I genuinely did not really know what software engineering was at that point or why anyone would do it. But I thought, hey, this sounds like a cool company. Sounds like they're doing lots of fun stuff. So I really joined Google because I studied computer science. Also, I could get the free food and massages at Google. I spent five years working on Google Maps, various backend features. And I left 2015 just as containers was coming up. So when I was looking around for what to do, I was like, oh, I've done Borg inside Google. I know how this works. This is the same thing. So I kind of just moved into infrastructure because I happened to know what it was from five years at Google. I moved into developer advocacy at the same time. Again, fairly early, 2016 was quite early for developer advocacy. I moved into that because I was like, hey, I want to be the sort of person who travels and gets up on stage and does keynotes. That's kind of what I did. I started Cloud Native London, The Meetup, because I was looking for events to speak at. And there was a Cloud Native Paris and a Cloud Native Berlin. And there wasn't a Cloud Native London. So I was like, ah, whatever. I'll just start it, put it on Meetup, see if anyone shows up. I picked a date that was about two months away. I had nothing, no speakers, no venue, no sponsors. And then more than 100 people showed up on the first one. They were like, OK, cool. There must be some interest here. And that's how I kind of moved into open source and community. And then CNCF 2018, I had a job offer from AWS at the time. Does anyone here work for AWS? OK, I didn't want to work for AWS. So I slacked someone I knew at CNCF, Chris Anjik. And I asked him, hey, I've got this offer from AWS. But is there anything interesting happening at CNCF that you think I could do? And he was like, yeah, we're two weeks away from hiring a director of ecosystem. If you would be great, you should join. So the whole point of me telling you that is that I kind of fell a lot into the open source infrastructure container world a little bit just by coincidence and good timing, a lot of it. And I want to tell you three particular times I really remember from CNCF. The first one is called After CNCF, You Could Be. This was when I was interviewing with CNCF. I was waiting for a phone call from Dan Cohn. He was the executive director. So getting a bit nervous, butterflies in the stomach. And phone rang. I picked it up. I said, hi, I'm Cheryl. He said, hi, Cheryl, I'm Dan Cohn. And after CNCF, You Could Be executive director of your own foundation, or you could be a VC, or you could go work at one of our member companies. And I was like, I hadn't said anything. I was like, what do you mean after CNCF I Could Be? This is a job interview. I'm supposed to be telling you why I'm supposed to be here. Did I mess up? Did I already get the job, and I didn't notice? But I really realized over time, that's how Dan thought about people. He was always like, hey, how can I set you up? So the next thing that you do, you can have even bigger opportunities and do even greater things that you want to do. And I've kind of tried to keep that in mind as I worked with community and with open source. And try not to sort of say, can you do things today? But what things could people do in the future that's even bigger and what they wanna do? The second thing that I remember is when I was a little few months into CNCF and I was getting my bearings, trying to figure out what was the most important thing that I should be spending my time on. So I wrote this long list of things that I could do and I took them to Dan and I said, hey, which of these do you think is the most important for me? And he listened to me talk and he said to me very, very calmly, you know, Cheryl, failure is an option. And what he meant by that was it doesn't really matter in a sense. Like you can't predict in advance which of these are gonna work out or not. But failure is an option. So don't get too in your head about what is the perfect thing to do and trying to set everything up perfectly. Just try a few different things and see which ones work and which ones don't. And I was so grateful to him, especially in a new job where you're so anxious to try and do the right thing that he said to me, failure's an option. Just don't stress too much. And a lot of the things that actually failed that I did at CNCF, no one remembers them now, thankfully, but quite a few things that I did just didn't work out and that was okay. Of the things that I did that did work out well, people and timing mattered the most. And I think Dawn, some of the stuff Dawn said also reflects upon this. So my favorite story of this is not something that's particularly well known, but it's called the Cloud Native Maturity Model. I had a consultant friend who said, hi, Cheryl, we've got this maturity model that we use at our consultancy. We help evaluate how far along the Cloud Native journey these different organizations are. We think CNCF community might be interested in it. Why don't you publish it? I was like, okay, cool. But one company's opinion on this is not really a community thing. So I filed it away and said, okay, we'll come back to it. A year later, a different friend at a different consultancy said, we've been working on a maturity model to help evaluate why organizations, how far organizations are along, to adopting Cloud Native. So I thought, okay, this sounds familiar. Let me do a little bit of searching. Turns out a third friend of mine had also published a different maturity model. So I was like, okay, this must be something interesting. Let's form a group around it. Let's go and publish it. And this group ended up being called the Cartagraphus Group, and they're looking at different ways of mapping out the journey to Cloud Native. I wanted to point this out because there was a year, as I said, between the first time someone said, hey, this is something interesting we've got, and oh, there's enough other people around it that we can do something together and make it happen. So I think the value of being at these kind of events is really about talking to people and finding out what stuff is happening now. And then maybe it'll pan out in a few years, maybe not. But that's how the things that I've done, that I've worked out, have always come about. So, right, what am I looking at now? So I work at ARM now, the chip design company, let's say. And I wanna sort of, like ARM is founded in 1985. So here's some other things that happened in 1985. They found the Titanic, the wreck of the Titanic. George Michael's Careless Whisper was the number one song in that year. Nintendo published Super Mario Brothers, Windows 1.0 came out, and Back to the Future was the top-grossing movie in that year. Now, in 2023, we live in a slightly different world. So connectivity and data-wise, we've got tons more data that we need to store and manage. We have 5G coming, well, no, it's already here, but 5G continues to increase, IoT continues to increase. And then in terms of the trends, everyone knows the markets are a little bit tricky time right now, companies are looking for cost savings, Moore's Law is coming to an end, so we can no longer double our performance easily, as easily in the past. And then lots of companies also have corporate mandates, and we should do the right thing to save money and be more sustained, sorry, not save money, save CO2, be more efficient with our use of energy and save the planet. So in the context of that, ARM has been really interesting because ARM has focused on a couple of things. One is that it's a risk architecture, so ARM stands for Advanced Risk Machines, and that means that it's focused on power efficiency, which is particularly good for mobile devices, and right now for data centers. Secondly, it's multi-purpose, so you can create different cores specialized for different tasks, which means you generally get comparable or sometimes better performance compared to x86. And then the third reason why ARM became really popular is because you can license, anyone can license ARM IP, which means you can get really customizable with different things that you can do. So on the left, that's the BBC Micro, the very first ARM v1 ARM machine. We have the iPhone, Apple created the iPhone of ARM v6, that's the Raspberry Pi. A couple of years ago, AWS launched Graviton to provide ARM in the cloud, and then Apple also now provide developer laptops that are based on M1 and M2 that are based on ARM. And then the other thing that makes ARM quite different is ARM is really focused on the ecosystem. ARM doesn't manufacture any kind of chips or do any manufacturing itself. So from ARM's point of view, the world looks like this. You have the silicon ecosystem, which is what ARM does, has lots of engineers who focus on designing architectures and what's coming next. It's really small, so you can't see this, but remember this EDA at the bottom right hand corner, it will come up again later, that's electronic design automation, it will come up again. Above that, you have the compute subsystem, so that's where you turn it into a CPU, that's where ARM partners with lots of companies that manufacture the actual CPUs. And then above that, that's where I play, the software ecosystem, that's all the other things around it, all the tools, all the libraries, all the middleware that you need to actually run ARM. So ARM is now in all the major clouds, apart from AWS, Google Cloud, Microsoft Azure, the Chinese, the big ones, Baidu, Tencent, Alibaba, and so on. And actually ARM really is everywhere. This is a very incomplete list, but it gives you a little bit of an idea of some of the open and closed source stuff that supports ARM. ARM is also in CNCF, in LF networking, and a bunch of other open standards bodies. Okay, so multi-arch. So the goal of multi-arch infrastructure is that workloads can run on the best hardware for their price performance needs without developers being concerned about the underlying architecture. That's what it boils down to, usually means moving from X86 to ARM, but the ultimate goal of multi-arch is, just use whatever gives me the best price performance. I pulled these headlines today, this morning, just to give you an idea of what this actually looks like in practice. So most of the companies that are trying to reduce costs effectively. So there's, and these are some of the different companies that have confirmed they do use Graviton, quoting anywhere from what, 25% up to 63% lower costs from moving to Graviton. And of course, you have to build through your own stuff. So remember I mentioned EDA, that is part of the chip design process for ARM, very compute-intensive workloads used to run on Femm X86, and ARM decided to move that to Graviton. And the results that they found a 60% better performance, half the cost, and then saved a bunch of power as well. Okay, this is my one slide where I'm gonna mention Kubernetes because I said this is the end of the day so your brain's all very tired already, but I'll give you some hints and tips if you think this is something that you wanna try. One is Kubernetes is not just Kubernetes. You have Prometheus and Falco and Silium and Flux or Argo or whatever. You have many, many, many applications that you run within Kubernetes if you wanna run a production-grade cluster. So when we talk about moving ARM to Kubernetes on ARM, you actually have to look at many, many different applications. So your strategy for this could be you move the control plane nodes and leave the worker nodes where they are. You could move the worker nodes, leave the control plane as it is. You could try and do a mix of X86 and ARM worker nodes. Each of these has its own complications, saves a certain amount, adds a little bit of complexity in other ways. When you're creating your clusters, that probably means you have to change how your clusters are created. That also causes problems if you're running things in demon sets or thought causes problems, but you have to have multi-arch images that run because a demon set will run on every node. So you have to make sure you're selecting the correct image for that architecture. In order to select those, that means that you might have different limits and the requests per architecture. You need to control it using node affinity and taints and tolerations. And you need to think about whether your build... If you're now getting to the point where you're like, now I have to move my actual applications, then are your builds reproducible? What do your pipelines look like? So, none of this is simple. I'll be like, having just told you, you're like, hey, you can save a bunch of money and save the planet. This is like a year plus process to actually move it. That's why it's hard. But at the same time, that's kind of where the pressures are going now. And it's perhaps not... I think it's still pretty... It's still kind of early now, but we're getting to this point where we're crossing the chasm with ARM. Lots of companies are starting to do this migration because, effectively, all of this is a one-off cost. And then hopefully you continue to save 24% on your ongoing cloud builds forevermore. So, takeaways. Takeaways. The main reason to move to ARM is just cost savings. You can get, in theory, get between 20 and 40% cheaper than running on X86. ARM is costing the chasm. 48 out of the top 50 EC2 customers use Graviton for some of their workloads. So it is real, whether you're at an end-user company that's trying to save money or whether you're a product company where your customers are starting to ask for ARM, it is coming. It's coming and you should be aware about it. And then, thirdly, just, again, people in timing. A lot of the stuff that... A lot of the reason that we're here in these conferences is to talk to the people and to find out what's coming up next. So I really encourage you to just get together, chat, have fun, find out what's happening in the community. And that is it for me. Thank you so much. I'll leave slides on my blog at osharl.com. Thank you. Thank you very much, Cheryl. That was fantastically on time. I'm like, everyone wants to get up and go off on dinner, I think, so it's good. I think they're well-frozen, so they can't actually stand up. Does anyone have questions for Cheryl? Yes, we do have questions over there. Do we go to... I see two there. We're really interested in adopting our architecture and stuff, but I see community space as a kind of major blocker is that many people use those actually charts made by Bitnami, and they repack all the images into, like, it's an architecture. So I think vendors, like, I really should work with those sort of blocks to have a wider adoption. Because in the end, someone looks at the chart, tries to deploy it, it doesn't work in them, all right. So I see huge vendors, they have kind of capacity, workforce, many connections, so they can kind of convince. So you said they have ugly charts? You mean helm charts, right? Helm charts, yeah. It's like a huge repository of different charts, and they always repack, like, binary things to their own images based on they've been, and it's never compatible with ARM. Yeah, yeah, yeah, yeah. Well, luckily, my job title is the Senior Director of Ecosystem, so it's actually my job to go out there and make it more beautiful, make these companies... I mean, my goal really is to make the experience as smooth and easy as possible. So I really want to work with these companies, and if anyone's here, actually, their company wants to work with ARM and wants to chat to me about it, like, I really encourage that, because, yeah, I agree. A lot of it's really, really ugly right now, and it could be a lot better. Hi. Hi. What I like the most was choosing the best cost performance for your application. Do you see WebAssembly as part of the multi-accord story? Say, the last bit again, do you see... Sorry. Do you see WebAssembly as part of the multi-architecture story? WebAssembly. I don't know WebAssembly in a lot of detail, but I think, from what I've seen, it's taking off slowly. So I'm sort of mildly positive towards WebAssembly, but I'm not super familiar with it myself. Anyone else? Thank you very much. Thank you. Thank you. Thank you.