 Y cwpanffordd ar wahanol. Rydych chi. Y tattoos am yr ystyn ni. A mor hynny i gwybod dli'r ddeddiol. Efallai allwch hwn taro'r ddechrau gwaith hwn o'r ddeddiol. Ychydig iddo dnos. Dyna lle mae'n ystafell hon. Felly efallai hwnnw gweld drod o IBM, mae'r cyfnod iawn iawn i ein ddill gweld I.T consultation company. Y cwpanffordd argyrch am ddillwyd. Wrw i gweithi'r llein gweithledd. Mae'n ddillwydd gyda'r lleig. Ond byddwn i'n gweithio i'r ffawr i eich cyhoeddi. Mae'r fawr i eich cyhoeddi i'r fawr i eich cyhoeddi, mae'r fawr i eich cyhoeddi yn gwneud. Rydyn ni'n gofio'r 5 minu. Yn ystod, rwy'n cymdeithas i'r fawr i eich cyhoeddi, a oeddwn i'n gweithio'r stori'r fawr, ond mae'r fawr yn ymddo. Rydyn ni'n gweithio i'r stori, rydyn ni'n gweithio'r hero. The hero will go on a journey, and the spoiler is the hero will learn something about open source, so it will be relevant in the end, and if it's okay with you, I'd like the hero to be Cloud Foundry, because I work on it. Does anyone here not heard of Cloud Foundry? Anyone? A decent amount, that's quite nice. Cloud Foundry is a Paz. Does anyone know what a Paz is? No one, amazing. So, you're not wrong. This Paz word I think has caused a lot of problems, and we should have probably come up with something better. I joked that we should have just called it serverless three years ago. This is a slide by Simon Wardley who is amazing and gets some of the difference, and I know a lot of people don't like this serverless word, but I think it's exactly the correct way to explain what we're doing. For a long time, it's like, why is Paz, how is it different from containers as a service, or infrastructure as a service, or any of these things? The answer is it's about what it removes. It's about what you're not responsible for, what you don't have to care about, whether that's servers, or orchestration, or containers, or any of those other things. The serverless is the idea. Why is that important? Say it with me, because with great power? I've always wanted to say that on a stage. That is the goal, right? Only by taking away some of the power can we build things at a high level. You can't add features to C to create Ruby. You'll get C++, but you won't get Ruby unless you take away the pointers. The reason that's important is because I hope in the future, in five years or ten years, the programmers will be physicists and students and geographers and chemists, and to do that we need to make it easier to push code to a platform. That's the Cloud Foundry idea. Here's my code. Don't make me care how. So far, so good. A good story needs a villain. This is one of those stories where the villain is actually very much a hero. It's kind of a second, double hero in this story. That's going to be Kubernetes. Has anyone heard of Kubernetes? No one? I came to the right place. Kubernetes is amazing. It's fantastic software with different goals, which is fine. It's at a lower level of the stack. Kubernetes gives you amazing tools that you can use to build distributed systems. To put it another way, Cloud Foundry, Paz is serverless, want to stop you needing to fight crime. Kubernetes wants to bite you with a radioactive spider and set you loose on the streets. It can make it so easy to do distributed systems that everyone can do it. That's a different goal. Of course, there's nothing wrong with that. That's not why it's the villain of this story. It's the villain of this story for really selfish reasons. This is the Cloud Foundry architecture. That big red bit is the container scheduling bit inside it that I've spent years working on. That's the bit that there's now this really great fantastic community and piece of software that's also doing that. What do we do? In an age of proprietary software, I think we know what we do. Just get worried. We're not in that age. We're in the world of open source. These are both open source projects. We're in Britain, so I think this is a good time to refer to some ancient ... If you're not from Britain, you'll know these people. If you're not, I'll catch you up. These are some of our ancient British sages. These are Delboy, Rodney and Grandad from a British show called Only Fools and Horses, which I like to think of as a sun-zoo's art of war for British people. In that show, there's a parable called Trigger's Broom. Trigger is the guy on the right. In the middle is the broom in question. Trigger is very proud because he's had this one broom for 20 years and it's still going strong. Of course, he's replaced the brush five times and the stick 10 times, and maybe you see where I'm going with this. The goal of this thing that we've built that I'm really passionate about, as you can probably tell, is to build this high-level system. It doesn't matter what we use to schedule the containers under the covers, and there's this fantastic software that's open source that we can use. Or in other words, it can be the same brush and a different stick, but as long as it cleans the same way, maybe it really is the same thing. That's the Irini project, which I've been working on with an awesome team of people to bring these two together and give people the option of using Kubernetes as the container schedule in Cloud Foundry. Of course, it's a story about how Cloud Foundry learned to love Kubernetes, but it's also really the story of how I learned to stop worrying and love open source because when these things come together, we can build something that's better than either of us could have built alone, and open source lets that happen, and that's really awesome. Five-minute talk, I have five bullet points. One, open source is fantastic because it lets us share and consume. Sharing and consuming, bringing these things together is amazing because we can build things that we couldn't build alone, but I really believe that it's not just about adding features. We have to think about what we remove to make these systems easier for people to use. You can't add features to see to make Ruby. You have to remove pointers, and that's okay. There doesn't have to be just one abstraction. Sometimes you need Ruby, sometimes you need C. If you're interested and you'd like to try out Irini and you have a Kubernetes cluster, there's two Helm installs to try out the CF push thing, the URLs at the bottom, and with that, thank you very much.