 testing. Okay, yeah that sounds good. I went back right after the party and I gather that there were others that did not see what happens when I do this. No, it's not resolution fun. I just want to be able to see from here without. He's here. He was. He was wandering around. I saw him. All right, good morning everybody and welcome to Ansible OpenShift in Roe. Better together at the edge. My name is Martin Jackson with me is Chad Furman. This whole concept is an outgrowth of experiences that we've had at previous companies and now we know each other from previous experience and are now working together at Red Hat. We are going to be talking about some big concepts about declarative and imperative automation and how you can explore some of these ideas with us using using a new concept that we're developing at Red Hat called validated patterns. So basically, you know, we are going to talk through some of these things. You know, why should you be listening to me and Chad about this in the first place? What are some of the inherent complexities that exist at the edge and talk about some of the issues around declarative and imperative automation? We'll introduce the concept of validated patterns. We'll talk about the Ansible GitOps validated pattern in particular and we'll have some time for questions and answers. All right, first off, Chad. Hey everybody, Chad Furman. So one thing I think that will be different from this discussion than a lot of folks is we've got a lot of Red Haters, which Marty and I both are now, but combined, we have about 50 years of customer experience. So we've actually done this. So the things that we're talking about, the things that you'll see and please ask questions and jump in if you have anything to say. But this is stuff that we've done. I've done it at Wella Gas. I've done it in retail. I've done it in DOD and then Marty. Yeah, I spent 22 years at Walmart stores before coming to Red Hat and Walmart stores has a far-flung infrastructure all over the world. You know, stores in a lot of different countries, about 12,000 stores in various countries at the point at which I left. Each of those stores has its own computing environment which operates semi-autonomously from the proverbial mothership. And so we are now calling this and similar kinds of things edge computing. So Chad and I have done a lot of edge computing over the course of our careers and we think we have something to say about it. So when you say autonomous, that's something that I think a lot of people don't realize about edge. So everybody's like, oh, edge, you know, we just put rel out there. We throw open shift out there. So what autonomous actually means is every one of those sites needs to be able to operate as if it were the data center. So if a Walmart store loses connectivity, if an oil and gas site loses connectivity, two things that will always ruin you. And it's always a network problem. Always. But really what it is is probably a DNS problem. So you have an open shift cluster. Open shift cluster needs to know how to talk to each other. DNS goes down unless you put stuff in the Etsy host file, which please God, don't do that anymore. You lose connectivity. Everything goes down. So with this diagram, this guy, it's super messy. And I did this intentionally is all of the stuff on the left-hand side, that's your typical data center. A lot of those services or the majority of those services also need to be at all of those other sites in order to have actual operations happen. And I think one thing when we talk about edge, we kind of miss that sometimes and just go, oh, you'll have rel or oh, you're going to have cloud native applications. There's a lot more things than rel and open shift. There's VMware, there is windows, there are PKI, there are all the other different pieces and parts that we need to think about to make sure that edge is successful. Yeah, I mean, you've got your network infrastructure, your switches, your routers, your wireless access points that, you know, need control plane information to know sort of developers or have used git. But one thing that I've done in many, many hackathons over the past four years, the first thing I actually had to teach people was, are you actually using source control and when you're making changes? Is it actually the one that you want it to be in git?