>>Set restaurants. And who says TEUs had got a little ass more skin in the game for us, in charge of his destiny? You guys are excited. Robert Worship is Chief Alumni. >>My name is Dave Ante, and I'm a long time industry analyst. So when you're as old as I am, you've seen a lot of transitions. Everybody talks about industry cycles and waves. I've seen many, many waves. Met a lot of industry executives and of a little bit of a, an industry historian. When you interview many thousands of people, probably five or 6,000 people as I have over the last half of a decade, you get to interact with a lot of people's knowledge and you begin to develop patterns. And so that's sort of what I bring is, is an ability to catalyze the conversation and, you know, share that knowledge with others in the community. Our philosophy is everybody's expert at something. Everybody's passionate about something and has real deep knowledge about that's something well, we wanna focus in on that area and extract that knowledge and share it with our communities. This is Dave Ante. Thanks for watching the Cube. >>Hello everyone and welcome back to the Cube where we are streaming live this week from CubeCon. I am Savannah Peterson and I am joined by an absolutely stellar lineup of cube brilliance this afternoon. To my left, a familiar face, Lisa Martin. Lisa, how you feeling? End of day two. >>Excellent. It was so much fun today. The buzz started yesterday, the momentum, the swell, and we only heard even more greatness today. >>Yeah, yeah, abs, absolutely. You know, I, I sometimes think we've hit an energy cliff, but it feels like the energy is just >>Continuous. Well, I think we're gonna, we're gonna slide right into tomorrow. >>Yeah, me too. I love it. And we've got two fantastic analysts with us today, Sarge and Keith. Thank you both for joining us. We feel so lucky today. >>Great being back on. >>Thanks for having us. Yeah, Yeah. It's nice to have you back on the show. We were, had you yesterday, but I miss hosting with you. It's been a while. >>It has been a while. We haven't done anything in since, Since pre >>Pandemic, right? Yeah, I think you're >>Right. Four times there >>Be four times back in the day. >>We, I always enjoy whole thing, Lisa, cuz she's so well prepared. I don't have to do any research when I come >>Home. >>Lisa will bring up some, Oh, sorry. Jeep, I see that in 2008 you won this award for Yeah. Being just excellent and I, I'm like, Oh >>Yeah. All right Keith. So, >>So did you do his analysis? >>Yeah, it's all done. Yeah. Great. He only part, he's not sitting next to me too. We can't see it, so it's gonna be like a magic crystal bell. Right. So a lot of people here. You got some stats in terms of the attendees compared >>To last year? Yeah, Priyanka told us we were double last year up to 8,000. We also got the scoop earlier that 2023 is gonna be in Chicago, which is very exciting. >>Oh, that is, is nice. Yeah, >>We got to break that here. >>Excellent. Keith, talk to us about what some of the things are that you've seen the last couple of days. The momentum. What's the vibe? I saw your tweet about the top three things you were being asked. Kubernetes was not one of them. >>Kubernetes were, was not one of 'em. This conference is starting to, it, it still feels very different than a vendor conference. The keynote is kind of, you know, kind of all over the place talking about projects, but the hallway track has been, you know, I've, this is maybe my fifth or sixth CU con in person. And the hallway track is different. It's less about projects and more about how, how do we adjust to the enterprise? How do we Yes. Actually do enterprise things. And it has been amazing watching this community grow. I'm gonna say grow up and mature. Yes. You know, you know, they're not wearing ties yet, but they are definitely understanding kind of the, the friction of implementing new technology in, in an enterprise. >>Yeah. So ge what's your, what's been your take, We were with you yesterday. What's been the take today to take aways? >>NOMA has changed since yesterday, but a few things I think I, I missed talking about that yesterday were that, first of all, let's just talk about Amazon. Amazon earnings came out, it spooked the market and I think it's relevant in this context as well, because they're number one cloud provider. Yeah. And all, I mean, almost all of these technologies on the back of us here, they are related to cloud, right? So it will have some impact on these. Like we have to analyze that. Like will it make the open source go faster or slower in, in lieu of the fact that the, the cloud growth is slowing. Right? So that's, that's one thing that's put that's put that aside. I've been thinking about the, the future of Kubernetes. What is the future of Kubernetes? And in that context, I was thinking like, you know, I think in, when I put a pointer there, I think in tangents, like, what else is around this thing? So I think CN CNCF has been writing the success of Kubernetes. They are, that was their number one flagship project, if you will. And it was mature enough to stand on its own. It it was Google, it's Google's Borg dub da Kubernetes. It's a genericized version of that. Right? So folks who do tech deep down, they know that, Right. So I think it's easier to stand with a solid, you know, project. But when the newer projects come in, then your medal will get tested at cncf. Right. >>And cncf, I mean they've got over 140 projects Yeah. Right now. So there's definitely much beyond >>Kubernetes. Yeah. So they, I have numbers there. 18 graduated, right, 37 in incubation and then 81 in Sandbox stage. They have three stages, right. So it's, they have a lot to chew on and the more they take on, the less, you know, quality you get goes into it. Who is, who's putting the money behind it? Which vendors are sponsoring like cncf, like how they're getting funded up. I think it >>Something I pay attention to as well. Yeah. Yeah. Lisa, I know you've got >>Some insight. Those are the things I was thinking about today. >>I gotta ask you, what's your take on what Keith said? Are you also seeing the maturation of the enterprise here at at coupon? >>Yes, I am actually, when you say enterprise versus what's the other side? Startups, right? Yeah. So startups start using open source a lot more earlier or lot more than enterprises. The enterprise is what they need. Number one thing is the, for their production workloads, they want a vendor sporting them. I said that yesterday as well, right? So it depend depending on the size of the enterprise. If you're a big shop, definitely if you have one of the 500 or Fortune five hundreds and your tech savvy shop, then you can absorb the open source directly coming from the open source sort of universe right. Coming to you. But if you are the second tier of enterprise, you want to go to a provider which is managed service provider, or it can be cloud service provider in this case. Yep. Most of the cloud service providers have multiple versions of Kubernetes, for example. >>I'm not talking about Kubernetes only, but like, but that is one example, right? So at Amazon you can get five different flavors of Kubernetes, right? Fully manage, have, manage all kind of stuff. So people don't have bandwidth to manage that stuff locally. You have to patch it, you have to roll in the new, you know, updates and all that stuff. Like, it's a lot of work for many. So CNCF actually is formed for that reason. Like the, the charter is to bring the quality to open source. Like in other companies they have the release process and they, the stringent guidelines and QA and all that stuff. So is is something ready for production? That's the question when it comes to any software, right? So they do that kind of work and, and, and they have these buckets defined at high level, but it needs more >>Work. Yeah. So one of the things that, you know, kind of stood out to me, I have good friend in the community, Alex Ellis, who does open Fast. It's a serverless platform, great platform. Two years ago or in 2019, there was a serverless day date. And in serverless day you had K Native, you had Open Pass, you had Ws, which is supported by IBM completely, not CNCF platforms. K native came into the CNCF full when Google donated the project a few months ago or a couple of years ago, now all of a sudden there's a K native day. Yes. Not a serverless day, it's a K native day. And I asked the, the CNCF event folks like, what happened to Serverless Day? I missed having open at serverless day. And you know, they, they came out and said, you know what, K native got big enough. >>They came in and I think Red Hat and Google wanted to sponsor a K native day. So serverless day went away. So I think what what I'm interested in and over the next couple of years is, is they're gonna be pushback from the C against the cncf. Is the CNCF now too big? Is it now the gatekeeper for do I have to be one of those 147 projects, right? In order enough to get my project noticed the open, fast, great project. I don't think Al Alex has any desire to have his project hosted by cncf, but it probably deserves, you know, shoulder left recognition with that. So I'm pushing to happen to say, okay, if this is open community, this is open source. If CNC is the place to have the cloud native conversation, what about the projects that's not cncf? Like how do we have that conversation when we don't have the power of a Google right. Or a, or a Lenox, et cetera, or a Lenox Foundation. So GE what, >>What are your thoughts on that? Is, is CNC too big? >>I don't think it's too big. I think it's too small to handle the, what we are doing in open source, right? So it's a bottle. It can become a bottleneck. Okay. I think too big in a way that yeah, it has, it has, it has power from that point of view. It has that cloud, if you will. The people listen to it. If it's CNCF project or this must be good, it's like in, in incubators. Like if you are y white Combinator, you know, company, it must be good. You know, I mean, may not be >>True, but, >>Oh, I think there's a bold assumption there though. I mean, I think everyone's just trying to do the best they can. And when we're evaluating projects, a very different origin and background, it's incredibly hard. Very c and staff is a staff of 30 people. They've got 180,000 people that are contributing to these projects and a thousand maintainers that they're trying to uphold. I think the challenge is actually really great. And to me, I actually look at events as an illustration of, you know, what's the culture and the health of an organization. If I were to evaluate CNCF based on that, I'd say we're very healthy right now. I would say that we're in a good spot. There's a lot of momentum. >>Yeah. I, I think CNCF is very healthy. I'm, I'm appreciative for it being here. I love coupon. It's becoming the, the facto conference to have this conversation has >>A totally >>Different vibe to other, It's a totally different vibe. Yeah. There needs to be a conduit and truth be told, enterprise buyers, to subject's point, this is something that we do absolutely agree on, on enterprise buyers. We want someone to pick winners and losers. We do, we, we don't want a box of Lego dumped on our, the middle of our table. We want somebody to have sorted that out. So while there may be five or six different service mesh solutions, at least the cncf, I can go there and say, Oh, I'll pick between the three or four that are most popular. And it, it's a place to curate. But I think with that curation comes the other side of it. Of how do we, how, you know, without the big corporate sponsor, how do I get my project pushed up? Right? Elevated. Elevated, Yep. And, and put onto the show floor. You know, another way that projects get noticed is that startups will adopt them, Push them. They may not even be, I don't, my CNCF project may not, my product may not even be based on the CNCF product. But the new stack has a booth, Ford has a booth. Nothing to do with a individual prod up, but promoting open source. What happens when you're not sponsored? >>I gotta ask you guys, what do you disagree on? >>Oh, so what, what do we disagree on? So I'm of the mindset, I can, I can say this, I I believe hybrid infrastructure is the future of it. Bar none. If I built my infrastructure, if I built my application in the cloud 10 years ago and I'm still building net new applications, I have stuff that I built 10 years ago that looks a lot like on-prem, what do I do with it? I can't modernize it cuz I don't have the developers to do it. I need to stick that somewhere. And where I'm going to stick that at is probably a hybrid infrastructure. So colo, I'm not gonna go back to the data center, but I'm, I'm gonna look, pick up something that looks very much like the data center and I'm saying embrace that it's the future. And if you're Boeing and you have, and Boeing is a member, cncf, that's a whole nother topic. If you have as 400 s, hpu X, et cetera, stick that stuff. Colo, build new stuff, but, and, and continue to support OpenStack, et cetera, et cetera. Because that's the future. Hybrid is the future. >>And sub g agree, disagree. >>I okay. Hybrid. Nobody can deny that the hybrid is the reality, not the future. It's a reality right now. It's, it's a necessity right now you can't do without it. Right. And okay, hybrid is very relative term. You can be like 10% here, 90% still hybrid, right? So the data center is shrinking and it will keep shrinking. Right? And >>So if by whole is the data center shrinking? >>This is where >>Quick one quick getting guys for it. How is growing by a clip? Yeah, but there's no data supporting. David Lym just came out for a report I think last year that showed that the data center is holding steady, holding steady, not growing, but not shrinking. >>Who sponsored that study? Wait, hold on. So the, that's a question, right? So more than 1 million data centers have been closed. I have, I can dig that through number through somebody like some organizations we published that maybe they're cloud, you know, people only. So the, when you get these kind of statements like it, it can be very skewed statements, right. But if you have seen the, the scene out there, which you have, I know, but I have also seen a lot of data centers walk the floor of, you know, a hundred thousand servers in a data center. I cannot imagine us consuming the infrastructure the way we were going into the future of co Okay. With, with one caveat actually. I am not big fan of like broad strokes. Like make a blanket statement. Oh no, data center's dead. Or if you are, >>That's how you get those esty headlines now. Yeah, I know. >>I'm all about to >>Put a stake in the ground. >>Actually. The, I think that you get more intelligence from the new end, right? A small little details if you will. If you're golden gold manak or Bank of America, you have so many data centers and you will still have data centers because performance matters to you, right? Your late latency matters for applications. But if you are even a Fortune 500 company on the lower end and or a healthcare vertical, right? That your situation is different. If you are a high, you know, growth startup, your situation is different, right? You will be a hundred percent cloud. So cloud gives you velocity, the, the, the pace of change, the pace of experimentation that actually you are buying innovation through cloud. It's proxy for innovation. And that's how I see it. But if you have, if you're stuck with older applications, I totally understand. >>Yeah. So the >>We need that OnPrem. Yeah, >>Well I think the, the bring your fuel sober, what we agree is that cloud is the place where innovation happens. Okay? At some point innovation becomes legacy debt and you have thus hybrid, you are not going to keep your old applications up to date forever. The, the, the math just doesn't add up. And where I differ in opinion is that not everyone needs innovation to keep moving. They need innovation for a period of time and then they need steady state. So Sergeant, we >>Argue about this. I have a, I >>Love this debate though. I say it's efficiency and stability also plays an important role. I see exactly what you're talking about. No, it's >>Great. I have a counter to that. Let me tell you >>Why. Let's >>Hear it. Because if you look at the storage only, right? Just storage. Just take storage computer network for, for a minute. There three cost reps in, in infrastructure, right? So storage earlier, early on there was one tier of storage. You say pay the same price, then now there are like five storage tiers, right? What I'm trying to say is the market sets the price, the market will tell you where this whole thing will go, but I know their margins are high in cloud, 20 plus percent and margin will shrink as, as we go forward. That means the, the cloud will become cheaper relative to on-prem. It, it, in some cases it's already cheaper. But even if it's a stable workload, even in that case, we will have a lower tier of service. I mean, you, you can't argue with me that the cloud versus your data center, they are on the same tier of services. Like cloud is a better, you know, product than your data center. Hands off. >>I love it. We, we are gonna relish in the debates between the two of you. Mic drops. The energy is great. I love it. Perspective. It's not like any of us can quite see through the crystal ball that we have very informed opinions, which is super exciting. Yeah. Lisa, any last thoughts today? >>Just love, I love the debate as well. That, and that's, that's part of what being in this community is all about. So sharing about, sharing opinions, expressing opinions. That's how it grows. That's how, that's how we innovate. Yeah. Obviously we need the cloud, but that's how we innovate. That's how we grow. Yeah. And we've seen that demonstrated the last couple days and I and your, your takes here on the Cuban on Twitter. Brilliant. >>Thank you. I absolutely love it. I'm gonna close this out with a really important analysis on the swag of the show. Yes. And if you know, yesterday we were looking at what is the weirdest swag or most unique swag We had that bucket hat that took the grand prize. Today we're gonna focus on something that's actually quite cool. A lot of the vendors here have really dedicated their swag to being local to Detroit. Very specific in their sourcing. Sonotype here has COOs. They're beautiful. You can't quite feel this flannel, but it's very legit hand sound here in Michigan. I can't say that I've been to too many conferences, if any, where there was this kind of commitment to localizing and sourcing swag from around the corner. We also see this with the Intel booth. They've got screen printers out here doing custom hoodies on spot. >>Oh fun. They're even like appropriately sized. They had local artists do these designs and if you're like me and you care about what's on your wrist, you're familiar with Shinola. This is one of my favorite swags that's available. There is a contest. Oh going on. Hello here. Yeah, so if you are Atan, make sure that you go and check this out. The we, I talked about this on the show. We've had the founder on the show or the CEO and yeah, I mean Shine is just full of class as since we are in Detroit as well. One of the fun themes is cars. >>Yes. >>And Storm Forge, who are also on the show, is actually giving away an Aston Martin, which is very exciting. Not exactly manufactured in Detroit. However, still very cool on the car front and >>The double oh seven version named the best I >>Know in the sixties. It's love it. It's very cool. Two quick last things. We talk about it a lot on the show. Every company now wants to be a software company. Yep. On that vein, and keeping up with my hat theme, the Home Depot is here because they want everybody to know that they in fact are a technology company, which is very cool. They have over 500,000 employees. You can imagine there's a lot of technology that has to go into keeping Napa. Absolutely. Yep. Wild to think about. And then last, but not at least very quick, rapid fire, best t-shirt contest. If you've ever ran to one of these events, there are a ton of T-shirts out there. I rate them on two things. Wittiest line and softness. If you combine the two, you'll really be our grand champion for the year. I'm just gonna hold these up and set them down for your laughs. Not afraid to commit, which is pretty great. This is another one designed by locals here. Detroit Code City. Oh, love it. This one made me chuckle the most. Kiss my cash. >>Oh, that's >>Good. These are also really nice and soft, which is fantastic. Also high on the softness category is this Op Sarah one. I also like their bird logo. These guys, there's just, you know, just real nice touch. So unfortunately, if you have the fumble, you're not here with us, live in Detroit. At least you're gonna get taste of the swag. I taste of the stories and some smiles hear from those of us on the cube. Thank you both so much for being here with us. Lisa, thanks for another fabulous day. Got it, girl. My name's Savannah Peterson. Thank you for joining us from Detroit. We're the cube and we can't wait to see you tomorrow.

>>welcome back everyone to the cube con cloud, David Kahn coverage. I'm john for a host of the cube, we're here in person, 2020 20 a real event, it's a hybrid event, we're streaming live to you with all the great coverage and guests coming on next three days. Clayton Coleman's chief Hybrid cloud architect for Red Hat is joining me here to go over viewers talk but also talk about hybrid cloud. Multi cloud where it's all going road red hats doing great to see you thanks coming on. It's a pleasure to be >>back. It's a pleasure to be back in cuba con. >>Uh it's an honor to have you on as a chief architect at Red Hat on hybrid cloud. It is the hottest area in the market right now. The biggest story we were back in person. That's the biggest story here. The second biggest story, that's the most important story is hybrid cloud. And what does it mean for multi cloud, this is a key trend. You just gave a talk here. What's your take on it? You >>know, I, I like to summarize hybrid cloud as the answer to. It's really the summarization of yes please more of everything, which is, we don't have one of anything. Nobody has got any kind of real footprint is single cloud. They're not single framework, they're not single language, they're not single application server, they're not single container platform, they're not single VM technology. And so, um, and then, you know, looking around here in this, uh, partner space where eight years into kubernetes and there is an enormous ecosystem of tools, technologies, capabilities, add ons, plug ins components that make our applications better. Um the modern application landscape is so huge that I think that's what hybrid really is is it's we've got all these places to run stuff more than ever and we've got all this stuff to run more than ever and it doesn't slow down. So how do we bring sanity to that? How do we understand it? Bring it together and companies has been a big part of that, like it unlocked some of that. What's the next step? >>Yeah, that's a great, great commentary. I want to take into the kubernetes piece but you know, as we've been reporting the digital transformation at all time, high speed is the number one request. People want to go faster, not just speeds and feeds, but like ship code fast to build apps faster. Make it all run faster and secure. Okay, check, get that. Look what we were 15, 15 years ago, 10 years ago, five years ago, 2016. The first coupe con in Seattle we were there for small events kubernetes, we gotta sell it, figure it out. Right convince people >>that it's a it's worth >>it. Yeah. So what's your take on that? Well, I mean, it's mature, it's kind of de facto standard at this point. What's missing. Where is it? >>So I think Kubernetes has succeeded at the core mission which is helping us stop worrying about all the problems that we spent endless amounts of time arguing about, how do I deploy software, How do I roll it out? But in the meantime we've added more types of software. You know, the rise of ai ml um you know, the whole the whole ecosystem around training software models like what is a what is an Ai model? Is it look like an application, does it look like a job? It's part batch, part service. Um It's spread out to the edge. We've added mobile devices. The explosion in mobile computing over the last 10 years has co evolved. And so kubernetes succeeded at that kind of set a floor for what everybody thought was an application. And in the meantime we've added all these other parts of the application. >>It's funny, you know, David Anthony, we're talking about what's to minimum and networks at red hat will be on later. Back in the first two cubicles were like, you know, this is like a TCP I P moment, the Os I model that was a killer part of the stack. Now it was all standardized below TCP I. P. Company feels like a similar kind of construct where it's unifying, is creating some enablement, It's enabling some innovation and it kind of brought everyone together at the same time everyone realized that that's real, >>the whole >>cloud native is real. And now we're in an era now where people are talking about doing things that are completely different. You mentioned as a batch job house ai new software paradigm development paradigms, not to suffer during the lifecycle, but just like software development in general is impacted. >>Absolutely. And you know, the components like, you know, we spent a lot of time talking about how to test and build application, but those are things that we all kind of internalized now we we have seen the processes is critical because it's going to be in lots of places, people are looking to standardize. But sometimes the new technology comes up alongside the side, the thing we're trying to standardize, we're like, well let's just use the new technology instead function as a service is kind of uh it came up, you know, kubernetes group K Native. And then you see, you know, the proliferation of functions as a service choices, what do people use? So there's a lot of choice and we're all building on those common layers, but everybody kind of has their own opinions, everybody's doing something subtly different. >>Let me ask you your opinion on on more under the Hood kind of complexity challenge. There's general consensus in the industry that does a lot of complexity. Okay, you don't mean debate that, but that's in a way, a good thing in the sense if you solve that, that's where innovation comes in. So the goal is to solve complexity, abstract out of the heavy lifting under heavy living in Sandy Jackson. And I would say, or abstract away complexity make things easier to use >>Well and an open source and this ecosystem is an amazing um it's one of the most effective methods we've ever found for trying every possible solution and keeping the five or six most successful and that's a little bit like developers, developers flow downhill, developers are going to do, it's easy if it's easier to put a credit card in and go to the public cloud, you're gonna do it if you can take control away from the teams at your organization that are there to protect you, but maybe aren't as responsive as you like. People will, people will go around those. And so I think a little bit of what we're trying to do is what are the commonalities that we could pick out of this ecosystem that everybody agrees on and make those the downhill path that people follow, not putting a credit card into a cloud, but offering a way for you not to think about what clouds are on until you need to write, because you want to go to the fridge is a developer, you wanna go the fridge, pull out your favorite brand of soda, that favorite band Isoda might have an AWS label also >>talk about the open shift and the Kubernetes relationship, you guys push the boundaries. Um Den is being controlled playing and nodes, these are things that you talked about in your talk, talk about because you guys made some good bets on open shift, we've been covering that, how's that playing out now? It's a relationship now >>is interesting coming into kubernetes, we came in from the platform as a service angle, right, Platform as a service was the first iteration of trying to make the lowest cost path for developers to flow to business value um and so we added things on top of kubernetes, we knew that we were going to complex, so we built in a little bit um in our structure and our way of thinking about cube that it was never going to be just that basic bare bones package that you're gonna have to make choices for people that made sense. Ah obviously as the ecosystems grown, we've tried to grow with it, we've tried to be a layer above kubernetes, we've tried to be a layer in between kubernetes, we've tried to be a layer underneath kubernetes and all of these are valid places to be. Um I think that next step is we're all kind of asking, you know, we've got all this stuff, are there any ways that we can be more efficient? So I like to think about practical benefits, what is a practical benefit That a little bit of opinion nation could bring to this ecosystem and I think it's around applications, it's being application centric, it's what is a team, 90% of the time need to be successful, they need a way to get their code out, they need to get it to the places that they wanted to be, and that place is everywhere. It's not one cloud or on premises or a data center, it's the edge, it's running as a lambda. It's running inside devices that might be being designed in this very room today. >>It's interesting. You know, you're an architect, but also the computer science industry is the people who were trained in the area are learning. It's pretty fascinating and almost intoxicating right now in this this market because you have an operating system, dynamic systems kind of programming model with distributed cloud, edge on fire, that's only gonna get more complicated with 5G and high density data applications. Um and then you've got this changing modal mode of operations were programming with bots and Ai and machine learning to new things, but it's kind of the same distributed computing paradigm. Yeah. What's your reaction to that? >>Well, and it's it's interesting. I was kind of described like layers. We've gone from Lenox replaced proprietary UNIX or mainframe to virtualization, which, and then we had a lot of Lennox, we had some windows too. And then we moved to public cloud and private cloud. We brought config management and moved to kubernetes, um we still got that. Os at the heart of what we do. We've got, uh application libraries and we've shared services and common services. I think it's interesting like to learn from Lennox's lesson, which is we want to build an open expansive ecosystem, You're kind of like kind of like what's going on. We want to pick enough opinion nation that it just works because I think just works is what, let's be honest, like we could come up with all the great theories of what the right way computers should be done, but it's gonna be what's easy, what gets people help them get their jobs done, trying to time to take that from where people are today on cube in cloud, on multiple clouds, give them just a little bit more consolidation. And I think it's a trick people or convince people by showing them how much easier it could be. >>You know, what's interesting around um, what you guys have done a red hat is that you guys have real customers are demanding, you have enterprise customers. So you have your eye on the front edge of the, of the bleeding edge, making things easier. And I think that's good enough is a good angle, but let's, let's face it, people are just lifting and shifting to the cloud now. They haven't yet re factored and re factoring is a concept of taking what you're doing in the cloud of taking advantage of new services to change the operating dynamic and value proposition of say the application. So the smart money is all going there, seeing the funding come into applications that are leveraging the new platform? Re platform and then re factoring what's your take on that because you got the edge, you have other things happening. >>There are so many more types of applications today. And it's interesting because almost all of them start with real practical problems that enterprises or growing tech companies or companies that aren't tech companies but have a very strong tech component. Right? That's the biggest transformation the last 15 years is that you can be a tech company without ever calling yourself a tech company because you have a website and you have an upset and your entire business model flows like that. So there is, I think pragmatically people are, they're okay with their footprint where it is. They're looking to consolidate their very interested in taking advantage of the scale that modern cloud offers them and they're trying to figure out how to bring all the advantages that they have in these modern technologies to these new footprints and these new form factors that they're trying to fit into, whether that's an application running on the edge next to their load bouncer in a gateway, in telco five Gs happening right now. Red hat's been really heavily involved in a telco ecosystem and it's kubernetes through and through its building on those kinds of principles. What are the concepts that help make a hybrid application, an application that spans the data flowing from a device back to the cloud, out to a Gateway processed by a big data system in a private region, someplace where computers cheap can't >>be asylum? No, absolutely not has to be distributed non siloed based >>and how do we do that and keep security? How do we help you track where your data is and who's talking to whom? Um there's a lot of, there's a lot of people here today who are helping people connect. I think that next step that contact connectivity, the knowing who's talking and how they're connecting, that'll be a fundamental part of what emerges as >>that's why I think the observe ability to me is the data is really about a data funding a new data sector of the market that's going to be addressable. I think data address ability is critical. Clayton really appreciate you coming on. And giving a perspective an expert in the field. I gotta ask you, you know, I gotta say from a personal standpoint how open source has truly been a real enabler. You look at how fast new things could come in and be adopted and vetted and things get kicked around people try stuff that fails, but it's they they build on each other. Right? So a I for example, it's just a great example of look at what machine learning and AI is going on, how fast that's been adopted. Absolutely. I don't think that would be done in open source. I have to ask you guys at red hat as you continue your mission and with IBM with that partnership, how do you see people participating with you guys? You're here, you're part of the ecosystem, big player, how you guys continue to work with the community? Take a minute to share what you're working on. >>So uh first off, it's impossible to get anything done I think in this ecosystem without being open first. Um and that's something the red at and IBM are both committed to. A lot of what I try to do is I try to map from the very complex problems that people bring to us because every problem in applications is complex at some later and you've got to have the expertise but there's so much expertise. So you got to be able to blend the experts in a particular technology, the experts in a particular problem domain like the folks who consult or contract or helped design some of these architectures or have that experience at large companies and then move on to advise others and how to proceed. And then you have to be able to take those lessons put them in technology and the technology has to go back and take that feedback. I would say my primary goal is to come to these sorts of events and to share what everyone is facing because if we as a group aren't all working at some level, there won't be the ability of those organizations to react because none of us know the whole stack, none of us know the whole set of details >>And this text changing too. I mean you got to get a reference to a side while it's more than 80s metaphor. But you know, but that changed the game on proprietary and that was like >>getting it allows us to think and to separate. You know, you want to have nice thin layers that the world on top doesn't worry about below except when you need to and below program you can make things more efficient and public cloud, open source kubernetes and the proliferation of applications on top That's happening today. I >>mean Palmer gets used to talk about the hardened top when he was the VM ware Ceo Back in 2010. Remember him saying that he says she predicted >>the whole, we >>call it the mainframe in the cloud at the time because it was a funny thing to say, but it was really a computer. I mean essentially distributed nature of the cloud. It happened. Absolutely. Clayton, thanks for coming on the Cuban sharing your insights appreciate. It was a pleasure. Thank you. Right click here on the Cuban john furry. You're here live in L A for coupon cloud native in person. It's a hybrid event was streaming Also going to the cube platform as well. Check us out there all the interviews. Three days of coverage, we'll be right back Yeah. Mm mm mm I have

>>mhm Yes. >>Hello and welcome back to the cubes coverage of dr khan 2021 virtual. I'm john Kerry hosted the Q got a great cube segment here. Simon Maple Field C T Oh it's technique. Great company security shifting left great to have you on Simon. Thanks for thanks for stopping by >>absolute pleasure. Thank you very much for having me. >>So you guys were on last year the big partnership with DR Conn remember that interview vividly because it was really the beginning at the beginning but really come to me the mainstream of shifting left as devops. It's not been it's been around for a while. But as a matter of practice as containers have been going super mainstream. Super ballistic in the developer community then you're seeing what's happening. It's containers everywhere. Security Now dev sec apps is the standard. So devops great infrastructure as code. We all know that but now it's def sec ops is standard. This is the real deal. Give us the update on what's going on with sneak. >>Absolutely, yeah. And you know, we're still tireless in our approach of trying to get make sure developers don't just have the visibility of security but are very much empowered in terms of actually fixing issues and secure development is what we're really striving for. So yeah, the update, we're still very, very deep into a partnership with DACA. We have updates on DR desktop which allows developers to scan the containers on the command line, providing developers that really fast feedback as as early as possible. We also have uh, you know, new updates and support for running Docker scan on Lennox. Um, and yeah, you know, we're still there on the Docker hub and providing that security insights um, to, to users who are going to Docker hub to grab their images. >>Well, for the folks watching maybe for the first time, the sneak Docker partnership, we went in great detail last year was the big reveal why Docker and sneak partnership, what is the evolution of that partnership over the year? They speak highly of you guys as a developer partner. Why Doctor? What's the evolution looked like? >>It's a it's a really great question. And I think, you know, when you look at the combination of DACA and sneak well actually let's take let's take each as an individual. Both companies are very, very developer focused. First of all, right, so our goals and will be strife or what we what we tirelessly spend their time doing is creating features and creating, creating an environment in which a developer you can do what they need to do as easily as possible. And that, you know, everyone says they want to be developer friendly, They want to be developer focused. But very few companies can achieve. And you look at a company like doctor, you're a company like sneak it really, really provides that developer with the developer experience that they need to actually get things done. Um, and it's not just about being in a place that a developer exists. It's not enough to do that. You need to provide a developer with that experience. So what we wanted to do was when we saw doctor and extremely developer friendly environment and a developer friendly company, when we saw the opportunity there to partner with Yoko, we wanted to provide our security developer friendliness and developer experience into an already developed a friendly tool. So what the partnership provides is the ease of, you know, deploying code in a container combined with the ease of testing your code for security issues and fixing security issues in your code and your container and pulling it together in one place. Now, one of the things which we as a as a security company um pride ourselves on is actually not necessarily saying we provide security tools. One of what our favorite way of saying is we're a developer tooling company. So we provide tools that are four developers now in doing that. It's important you go to where the developers are and developers on DACA are obviously in places like the Docker hub or the Docker Cli. And so it's important for us to embed that behavior and that ease of use inside Dhaka for us to have that uh that that flow. So the developer doesn't need to leave the Docker Cli developer that doesn't need to leave Docker hub in order to see that data. If you want to go deeper, then there are probably easier ways to find that data perhaps with sneak or on the sneak site or something like that. But the core is to get that insight to get that visibility and to get that remediation, you can see that directly in in the in the Dhaka environment. And so that's what makes the relationship so so powerful. The fact that you combine everything together and you do it at source >>and doing it at the point of code. >>Writing >>code is one of the big things I've always liked about the value proposition is simple shift left. Um So let's just step back for a second. I got to ask you this question because this I wanted to make sure we get this on the table. What are the main challenges uh and needs to, developers have with container security? What are you seeing as the main top uh A few things that they need to have right now for the challenges uh with container security? >>Yeah, it's a it's a very good question. And I think to answer that, I think we need to um we need to think of it in a couple of ways. First of all, you've just got developers security uh in general, across containers. Um And the that in itself is there are different levels at which developers engage with containers. Um In some organizations, you have security teams that are very stringent in terms of what developers can and can't do in other organizations. It's very much the developer that that chooses their environment, chooses their parent image, et cetera. And so there when a developer has many, many choices in which they need to need to decide on, some of those choices will lead to more issues, more risk. And when we look at a cloud native environment, um uh Let's take let's take a node uh image as an example, the number of different uh images tags you can choose from as a developer. It's you know, there are hundreds, probably thousands. That you can actually you can actually choose. What is the developer gonna do? Well, are they going to just copy paste from another doctor file, for example, most likely. What if there are issues in that docker file? They're just gonna copy paste that across mis configurations that exist. Not because the developer is making the wrong decision, but because the developer very often doesn't necessarily know that they need to add a specific directive in. Uh So it's not necessarily what you add in a conflict file, but it's very often what you admit. So there are a couple of things I would say from a developer point of view that are important when we think about cloud security, the first one is just that knowledge that understanding what they need to do, why they need to do it. Secure development doesn't need to be, doesn't mean they need to be deep in security. It means they need to understand how they can develop securely and what what the best decisions that could come from guard rails, from the security team that they provide the development team to offer. But that's the that's an important error of secure development. The second thing and I think one of the most important things is understanding or not understanding necessarily, but having the information to get an act on those things early. So we know the length of time that developers are uh working on a branch or working on um some some code changes that is reducing more and more and more so that we can push to production very, very quickly. Um What we need to do is make sure that as a developer is making their changes, they can make the right decision at the right time and they have the right information at that time. And a lot of this could be getting information from tools, could be getting information from your team where it could be getting information from your production environments and having that information early is extremely important to make. That decision. May be in isolation with your team in an autonomous way or with advice from the security team. But I would say those are the two things having that information that will allow you to make that action, that positive change. Um uh and and yeah, understanding and having that knowledge about how you can develop security. >>All right. So I have a security thing. So I'm a development team and by the way, this whole team's thing is a huge deal. I think we'll get to that. I want to come back to that in a second but just throw this out there. Got containers, got some security, it's out there and you got kubernetes clusters where containers are coming and going. Sometimes containers could have malware in them. Um and and this is, I've heard this out and about how do how that happens off container or off process? How do you know about it? Is that infected by someone else? I mean is it gonna be protected? How does the development team once it's released into the wild, so to speak. Not to be like that, but you get the idea, it's like, okay, I'm concerned off process this containers flying around. What is it How do you track all >>and you know, there's a there's a few things here that are kind of like potential potential areas that, you know, we can trip up when we think about malware that's running um there are certain things that we need to that we need to consider and what we're really looking at here are kind of, what do we have in place in the runtime that can kind of detect these issues are happening? How do we block that? And how do you provide that information back to the developer? The area that I think is, and that is very, very important in order to in order to be able to identify monitor that those environments and then feed that back. So that that that's the kind of thing that can be that can be fixed. Another aspect is, is the static issues and the static issues whether that's in your os in your OS packages, for example, that could be key binaries that exist in your in your in your docker container out the box as well or of course in your application, these are again, areas that are extremely important to detect and they can be detected very very early. So some things, you know, if it's malware in a package that has been identified as malware then absolutely. That can be that can be tracked very very early. Sometimes these things need to be detected a little bit later as well. But yeah, different tools for different for different environments and wear sneak is really focused. Is this static analysis as early as possible. >>Great, great insight there. Thanks for sharing that certainly. Certainly important. And you know, some companies classes are locked down and all of sudden incomes, you know, some some malware from a container, people worried about that. So I want to bring that up. Uh The other thing I want to ask you is this idea of end to end security um and this is a team formation thing we're seeing where modern teams have essentially visibility of their workload and to end. So this is a huge topic. And then by the way it might integrate their their app might integrate with other processes to that's great for containers as well and observe ability and microservices. So this is the trend. What's in it for the developer? If I work with sneak and docker, what benefits do I get if I want to go down that road of having these teams began to end, but I want the security built in. >>Mhm. Yeah, really, really important. And I think what's what's most important there is if we don't look end to end, there are component views and there are applications. If we don't look into end, we could have our development team fixing things that realistically aren't in production anyway or aren't the key risks that are potentially hurting us in our production environment. So it's important to have that end to end of you so that we have the right insights and can prioritize what we need to identify and look at early. Um, so I think, I think that visibility into end is extremely important. If we think about who, who is re fixing uh certain issues, again, this is gonna depend from dog to walk, but what we're seeing more and more is this becoming a developer lead initiative to not just find or be given that information, but ultimately fixed. They're getting more and more responsible for DR files for for I see for for their application code as well. So one of the areas which we've looked into as well is identifying and actually running in cuba Netease workloads to identify where the most important areas that a developer needs to look at and this is all about prioritization. So, you know, if the developer has just a component view and they have 100 different images, 100 different kubernetes conflicts, you know, et cetera. Where do they prioritize, where do they spend their time? They shouldn't consider everything equal. So this identification of where the workloads are running and what um is causing you the most risk as a business and as an organization, that is the data. That can be directly fed back into your, your your vulnerability data and then you can prioritize based on the kubernetes workloads that are in your production and that can be fed directly into the results in the dashboards. That's neat. Can provide you as well. So that end to end story really provides the context you need in order to not just develop securely, but act and action issues in a proper way. >>That's a great point. Context matters here because making it easy to do the right thing as early as possible, the right time is totally an efficiency productivity gain, you see in that that's clearly what people want. It's a great formula, success, reduce the time it takes to do something, reduced the steps and make it easy. Right, come on, that's a that's a formula. Okay, so I gotta bring that to the next level. When I ask you specifically around automation, this is one the hot topic and def sec ops, automation is part of it. You got scale, you got speed, you've got a I machine learning, you go out of all these new things. Microservices, how do you guys fit into the automation story? >>It's a great question. And you know, one of the recent reports that we that we did based on a survey data this year called the state of a state of cloud, native applications security. We we asked the question how automated our people in their in their deployment pipelines and we found some really strong correlations between value from a security point of view um in terms of in terms of having that automation in it, if I can take you through a couple of them and then I'll address that question about how we can be automated in that. So what we found is a really strong correlation as you would expect with security testing in ci in your source code repositories and all the way through the deployment ci and source code were the two of the most most well tested areas across the pipeline. However the most automated teams were twice as likely to test in I. D. S. And testing your CLS in local development. And now those are areas that are really hard to automate if at all because it's developers running running their cli developers running and testing in their I. D. So the having a full automation and full uh proper testing throughout the sclc actually encourages and and makes developers test more in their development environment. I'm not saying there's causation there but there's definite correlation. A couple of other things that this pushes is um Much much more likely to test daily or continuously being automated as you would expect because it's part of the bills as part of your monitoring. But crucially uh 73% of our respondents were able to fix a critical issue in less than a week as opposed to just over 30% of people that were not automated, so almost double people are More likely to fix within a week. 36% of people who are automated can fix a critical security issue in less than a day as opposed to 8% of people who aren't automated. So really strong data that correlates being automated with being able to react now. If you look at something like Sneak what if our um goals of obviously being developer friendly developer first and being able to integrate where developers are and throughout the pipeline we want to test everywhere and often. Okay, so we start as far left as we can um integrating into, you know, CLS integrating into Docker hub, integrating into into doctors can so at the command line you type in doctors can you get sneak embedded in DHAKA desktop to provide you those results so as early as possible, you get that data then all the way through to to uh get reposed providing that testing and automatically testing and importing results from there as well as as well as other repositories, container repositories, being at a poor from there and test then going into ci being able to run container tests in C I to make sure we're not regressing and to choose what we want to do their whether we break, whether we continue with with raising an issue or something like that, and then continuing beyond that into production. So we can monitor tests and automatically send pull requests, etcetera. As and when new issues or new fixes occur. So it's about integrating at every single stage, but providing some kind of action. So, for example, in our ui we provide the ability to say this is the base level you should be or could be at, it will reduce your number of vulnerabilities by X and as a result you're going to be that much more secure that action ability across the pipeline. >>That's a great, great data dump, that's a masterclass right there on automation. Thanks for sharing that sign. I appreciate it. I gotta ask you the next question that comes to my mind because I think this is kind of the dots connect for the customer is okay. I love this kind of hyper focus on containers and security. You guys are all over it, shift left as far as possible, be there all the time, test, test, test all through the life cycle of the code. Well, the one thing that is popping up as a huge growth areas, obviously hybrid cloud devops across both environments and the edge, whether it's five G industrial or intelligent edge, you're gonna have kubernetes clusters at the edge now. So you've got containers. The relationship to kubernetes and then ultimately cloud native work clothes at, say, the edge, which has data has containers. So there's a lot of stuff going on all over the place. What's your, what's your comment there for customer says, Hey, you know, I got, this is my architecture that's happening to me now. I'm building it out. We're comfortable with kubernetes put in containers everywhere, even on the edge how to sneak fit into that story. >>Yeah, really, really great question. And I think, you know, a lot of what we're doing right now is looking at a developer platform. So we care about, we care about everything that a developer can check in. Okay, so we care about get, we care about the repositories, we care about the artifact. So um, if you look at the expansion of our platform today, we've gone from code that people uh, third party libraries that people test. We added containers. We've also added infrastructure as code. So Cuban eighties conflicts, Terror form scripts and things like that. We're we're able to look at everything that the developer touches from their code with sneak code all the way through to your to your container. And I see, so I think, you know, as we see more and more of this pushing out into the edge, cuba Nitties conflict that that, you know, controls a lot of that. So much of this is now going to be or not going to be, but so much of the environment that we need to look at is in the configurations or the MIS configurations in that in those deployment scripts, um, these are some of the areas which which we care a lot about in terms of trying to identify those vulnerabilities, those miS configurations that exist within within those scripts. So I can see yeah more and more of this and there's a potential shift like that across to the edge. I think it's actually really exciting to be able to see, to be able to see those uh, those pushing across. I don't necessarily see any other, any, you know, different security threats or the threat landscape changing as a result of that. Um there could be differences in terms of configurations, in terms of miS configurations that that that could increase as a result, but, you know, a lot of this and it just needs to be dealt with in the appropriate way through tooling through, through education of of of of how that's done. >>Well, obviously threat vectors are all gonna look devops like there's no perimeter. So they're everywhere right? Looking at I think like a hacker to be being there. Great stuff. Quick question on the future relationship with DR. Obviously you're betting a lot here on that container relationship, a good place to start. A lot of benefits there. They have dependencies, they're going to have implications. People love them, they love to use them, helps old run with the new and helps the new run better. Certainly with kubernetes, everything gets better together. What's the future with the DACA relationship? Take us through how you see it. >>So yeah, I mean it's been an absolute blast the doctor and you know, even from looking at some of the internal internal chats, it's been it's been truly wonderful to see the, the way in which both the doctor and sneak from everything from an engineering point of view from a marketing, from a product team. It's been a pleasure to, it's been a pleasure to see that relationship grow and flourish. And, and I think there's two things, first of all, I think it's great that as companies, we, we both worked very, very well together. I think as as as users um seeing, you know, doctor and and and sneak work so so seamlessly and integrated a couple of things. I would love to see. Um, I think what we're gonna see more and more and this is one of the areas that I think, um you know, looking at the way sneak is going to be viewing security in general. We see a lot of components scanning a lot, a lot of people looking at a components can and seeing vulnerabilities in your components. Can I think what we need to, to to look more upon is consolidating a lot of the a lot of the data which we have in and around different scans. What I would love to see is perhaps, you know, if you're running something through doctors can how can you how can you view that data through through sneak perhaps how can we get that closer integration through the data that we that we see. So I would love to see a lot more of that occur, you know, within that relationship and these are kind of like, you know, we're getting to that at that stage where we see integration, it just various levels. So we have the integration where we have we are embedded but how can we make that better for say a sneak user who also comes to the sneak pages and wants to see that data through sneak. So I would love to see at that level uh more there where as I mentioned, we have we have some some additional support as well. So you can run doctors can from from Lenox as well. So I can see more and more of that support rolling out but but yeah, in terms of the future, that's where I would love to see us uh to grow more >>and I'll see in the landscape side on the industry side, um, security is going beyond the multiple control planes out there. Kubernetes surveillance service matches, etcetera, continues to be the horizontally scalable cloud world. I mean, and you got you mentioned the edge. So a lot more complexity to rein in and make easier. >>Yeah, I mean there's a lot more complexity, you know, from a security point of view, the technology is the ability to move quickly and react fast in production actually help security a lot because you know, being able to spin a container and make changes and and bring a container down. These things just weren't possible, you know, 10 years ago, 20 years ago. Pre that it's like it was it's insanely hard compared trying to trying to do that compared to just re spinning a container up. However, the issue I see from a security point of view, the concerns I see is more around a culture and an education point of view of we've got all this great tech and it's it's awesome but we need to do it correctly. So making sure that as you mentioned with making the right decision, what we want to make sure is that right decision is also the easy decision and the clear decision. So we just need to make sure that as we as we go down this journey and we're going down it fast and it's not gonna, I don't see it slowing down, we're going fast down that journey. How do we make, how do we prepare ourselves for that? We're already seeing, you know, miss configurations left, right and center in the news, I am roles as three buckets, etcetera. These are they're they're simpler fixes than we than we believe, right? We just need to identify them and and make those changes as needed. So we just need to make sure that that is in place as we go forward. But it's exciting times for sure. >>It's really exciting. And you got the scanning and right at the point of coding automation to help take that basic mis configuration, take that off the table. Not a lot of manual work, but ultimately get to that cloud scale cool stuff. >>Simon, thank you >>for coming on the cube dr khan coverage. Really appreciate your time. Drop some nice commentary there. Really appreciate it. Thank you. >>My pleasure. Thank you very much. >>Simon Maple Field C T. O. A sneak hot startup. Big partner with Docker Security, actually built in deVOPS, is now dead. Say cops. This is dr khan cube 2021 virtual coverage. I'm sean for your host. Thanks for watching. Mm.

>>Mhm Yes. Hello and welcome back to the cubes coverage of red hat summit 2021 virtual. I'm john for your host of the cube we're here with Hillary Hunter, the VP and CTO and IBM fellow of IBM cloud at IBM. Hillary, Great to see you welcome back, You're no stranger to us in the cube your dentist few times. Thanks for coming on. >>Thanks so much for having me back. Great to talk more today >>I believe I B M is the premier sponsor for red hat summit this year. No, I mean I think they're somewhat interested in what's happening. >>Yeah, you know, somebody is such a great event for us because it brings together clients that, you know, we work together with red head on and gives us a chance to really talk about that overall journey to cloud and everything that we offer around cloud and cloud adoption um, and around redheads capabilities as well. So we look forward to the summit every year for sure. >>You know, the new IBM red hat relationship obviously pretty tight and successful seeing the early formations and customer attraction and just kind of the momentum, I'll never forget that Red hat something was in SAN Francisco. I sat down with Arvin at that time, uh, Red hat was not part of IBM and it was interesting. He was so tied into cloud native. It was almost as if he was dry running the acquisition, which he announced just moments later after that. But you can see the balance. The Ceo at IBM really totally sees the cloud. He sees that experience. He sees the customer impact. This has been an interesting year, especially with Covid and with the combination of red hat and IBM, this cloud priority for IT leaders is more important than ever before. What's your, what's your take on this? Because clearly you guys are all in on cloud, but not what people think, what's your, what's your view on this? >>Yeah. You know, from, from the perspective of those that are kind of data oriented IBM Institute for Business Value, did lots of studies over the last year, you know, saying that over 60% of leaders feel, you know, increased urgency to get to the cloud, um they're intending to accelerate their program to the cloud, but I think, you know, just even as consumers where each very conscious that our digital behaviors have changed a lot in the last year and we see that in our enterprise client base where um everything from, you know, a bank, we work that that that had to stand up their countries equivalent of the payroll protection program in a matter of weeks, which is just kind of unheard of to do something that robust that quickly or um, you know, retail obviously dealing with major changes, manufacturing, dealing with major changes and all consumers wanting to consume things on an app basis and such, not going into brick and mortar stores and such. And so everything has changed and months, I would say have sort of timeframes of months have been the norm instead of years for um, taking applications forward and modernizing them. And so this journey to cloud has compressed, It's accelerated. And as one client I spoke with said, uh, in the midst of last year, you know, it is existential that I get to cloud with urgency and I think That's been that has been the theme of 2020 and now also 2021. And so it is, it is the core technology for moving faster and dealing with all the change that we're all experiencing. >>That's just so right on point. But I got I want to ask you because this is the key trend enterprises are now realizing that cloud native architecture is based on open source specifically is a key architectural first principle now. >>Yeah. >>What's your, what, what would you say to the folks out there who were listening to this and watching this video, Who were out in the enterprise going, hey, that's a good call. I'm glad I did it. So I don't have any cognitive dissidence or I better get there faster. >>Yeah. You know, open source is such an important part of this conversation because I always say that open source moves at the rate and pays a global innovation, which is kind of a cute phrase that I really don't mean it in anyways, cute. It really is the case that the purpose of open sources for people globally to be contributing. And there's been innovation on everything from climate change to you know, musical applications to um things that are the fundamentals of major enterprise mission critical workloads that have happened is everyone is adopting cloud and open source faster. And so I think that, you know this choice to be on open source is a choice really, you know, to move at the pace of global innovation. It's a choice too um leverage capabilities that are portable and it's a choice to have flexibility in deployment because where everyone's I. T is deployed has also changed. And the balance of sort of where people need the cloud to kind of come to life and be has also changed as everyone's going through this period of significant change. >>That's awesome. IBM like Red has been a long supporter and has a history of supporting open source projects from Lenox to kubernetes. You guys, I think put a billion dollars in Lenox way back when it first started. Really power that movement. That's going back into the history books there. So how are you guys all collaborating today to advance the open source solutions for clients? >>Yeah, we remain very heavily invested in open source communities and invested in work jointly with Red Hat. Um you know, we enabled the technology known as um uh Rackham the short name for the Red Hat advanced cluster management software, um you know, in this last year, um and so, you know, provided that capability um to to become the basis of that that product. So we continue to, you know, move major projects into open source and we continue to encourage external innovators as well to create new capabilities. And open source are called for code initiatives for developers as an example, um have had specific programs around um uh social justice and racial issues. Um we have a new call for code out encouraging open source projects around climate change and sustainable agriculture and all those kind of topics and so everything from you know, topics with developers to core product portfolio for us. Um We have a very uh very firm commitment in an ongoing sustained contribution on an open source basis. >>I think that's important. Just to call out just to kind of take a little sidebar here. Um you guys really have a strong mission driven culture at IBM want to give you props for that. Just take a minute to say, Congratulations call for code incredible initiative. You guys do a great job. So congratulations on that. Appreciate. >>Thank you. Thank you. >>Um as a sponsor of Red Hat Summit this year, I am sponsoring the zone Read at um you have you have two sessions that you're hosting, Could you talk about what's going on? >>Yeah, the the two sessions, so one that I'm hosting is around um getting what we call 2.5 x value out of your cloud journey. Um and really looking at kind of how we're working with clients from the start of the journey of considering cloud through to actually deploying and managing environments and operating model on the cloud um and where we can extract greater value and then another session um that I'm doing with Roger Primo, our senior vice President for strategy at IBM We're talking about lessons and clouded option from the Fortune 500, so we're talking there about coca cola european bottling partners, about lumen technologies um and um also about wonderman Thompson, um and what they're doing with us with clouds, so kind of two sessions, kind of one talking a sort of a chalkboard style um A little bit of an informal conversation about what is value meaning cloud or what are we trying to get out of it together? Um And then a session with roger really kind of focused on enterprise use cases and real stories of cloud adoption. >>Alright so bottom line what's going to be in the sessions, why should I attend? What's the yeah >>so you know honest honestly I think that there's kind of this um there's this great hunger I would say in the industry right now to ascertain value um and in all I. T. Decision making, that's the key question right? Um not just go to the cloud because everyone's going to the cloud or not just adopt you know open source technologies because it's you know something that someone said to do, but what value are we going to get out of it? And then how do we have an intentional conversation about cloud architecture? How do we think about managing across environments in a consistent way? Um how do we think about extracting value in that journey of application, modernization, um and how do we structure and plan that in a way? Um that results in value to the business at the end of the day, because this notion of digital transformation is really what's underlying it. You want a different business outcome at the end of the day and the decisions that you take in your cloud journey picking. Um and open hybrid, multi cloud architecture leveraging technologies like IBM cloud satellite to have a consistent control plan across your environments, um leveraging particular programs that we have around security and compliance to accelerate the journey for regulated industries etcetera. Taking intentional decisions that are relevant to your industry that enable future flexibility and then enable a broad ecosystem of content, for example, through red hat marketplace, all the capabilities and content that deploy onto open shift, et cetera. Those are core foundational decisions that then unlock that value in the cloud journey and really result in a successful cloud experience and not just I kind of tried it and I did or didn't get out of it what I was expecting. So that's really what, you know, we talk about in these in these two sessions, um and walk through um in the second session than, you know, some client use cases of, of different levels and stages in that cloud journey, some really core enterprise capabilities and then Greenfield whitespace completely new capabilities and cloud can address that full spectrum. >>That's exciting not to get all nerdy for a second here, But you know, you bring up cloud architecture, hybrid cloud architecture and correct me if I'm wrong if you're going to address it because I think this is what I'm reporting and hearing in the industry against the killer problem everyone's trying to solve is you mentioned, um, data, you mentioned control playing for data, you mentioned security. These are like horizontally scalable operating model concepts. So if you think about an operating system, this is this is the architecture that becomes the cloud model hybrid model because it's not just public cloud cloud native or being born in the cloud. Like a startup. The integration of operating at scale is a distributed computing model. So you have an operating system concept with some systems engineering. Yeah, it sounds like a computer to me, right. It sounds like a mainframe. Sounds like something like that where you're thinking about not just software but operating model is, am I getting that right? Because this is like fundamental. >>Yeah, it's so fundamental. And I think it's a great analogy, right? I think it's um you know, everyone has kind of, their different description of what cloud is, what constitutes cloud and all that kind of thing, but I think it's great to think of it as a system, it's a system for computing and what we're trying to do with cloud, what we're trying to do with kubernetes is to orchestrate a bunch of, you know, computing in a consistent way, as, you know, other functions within a single server do. Um What we're trying to do with open shift is, you know, to enable um clients to consume things in a consistent way across many different environments. Again, that's the same sort of function um conceptually as, you know, an operating system or something like that is supposed to provide is to have a platform fundamentally, I think the word platform is important, right? Have a platform that's consistent across many environments and enables people to be productive in all those environments where they need to be doing their computing. >>We were talking before we came on camera about cloud history and we were kind of riffing back and forth around, oh yeah, five years ago or six years ago was all the conversations go to the cloud now, it's like serious conscience around the maturity of cloud and how to operate that scale in the cloud, which is complex, it's complex system and you have complexity around system complexity and novelty complexity, so you have kind of all these new things happening. So I want to ask you because you're an IBM fellow and you're on the cloud side at IBM with all this red hat goodness you've got going on, Can you give us a preview of the maturity model that you see the IBM season, that red hats doing so that these architectures can be consistent across the platforms, because you've got def sec ops, you've got all these new things, you've got security and data at scale, it's not that obviously it's not easy, but it has to be easier. What's what's the preview of the maturity model? >>Yeah, you know, it really is about kind of a one plus one equals three conversation because red hats approach to provide a consistent platform across different environments in terms of Lennox and Kubernetes and the open shift platform um enables that first conversation about consistency and maturity um in many cases comes from consistency, being able to have standards and consistency and deployment across different environments leads to efficiency. Um But then IBM odds on that, you know, a set of conversations also around data governance, um consistency of data, cataloguing data management across environments, machine learning and ai right bringing in A. I. For I. T. Operations, helping you be more efficient to diagnose problems in the IT environment, other things like that. And then, you know, in addition, you know, automation ultimately right when we're talking about F. R. I. T. Ops, but also automation which begins down at the open shift level, you know with use of answerable and other things like that and extends them up into automation and monitoring of the environment and the workloads and other things like that. And so it really is a set of unlocking value through increasing amounts of insight, consistency across environments, layering that up into the data layer. Um And then overall being able to do that, you know efficiently um and and in a consistent way across the different environments, you know, where cloud needs to be deployed in order to be most effective, >>You know, David Hunt and I always talk about IBM and all the years we've been covering with the Cube, I mean we've pretty much been to every IBM events since the Cube was founded and we're on our 11th year now watching the progression, you guys have so much expertise in so many different verticals, just a history and the expertise and the knowledge and the people. They're so smart. Um I have to ask you how you evolved your portfolio with the cloud now um as it's gone through, as we are in the 2021 having these mature conversations around, you know, full integration, large scale enterprise deployments, Critical Mission Mission Critical Applications, critical infrastructure, data, cybersecurity, global scale. How are you evolve your portfolio to better support your clients in this new environment? >>Yeah, there's a lot in there and you hit a lot of the keywords already. Thank you. But but I think that you know um we have oriented our portfolio is such that all of our systems support Red hat um and open shift, um our cloud, we have redhead open shift as a managed service and kubernetes is at the core of what we're doing as a cloud provider and achieving our own operational efficiencies um from the perspective of our software portfolio, our core products are delivered in the form of what we refer to as cloud packs on open shift and therefore deploy across all these different environments where open shift is supported, um products available through Red hat marketplace, you know, which facilitates the billing and purchasing an acquisition and installation of anything within the red hat ecosystem. And I think, you know, for us this is also then become also a journey about operational efficiency. We're working with many of our clients is we're kind of chatting about before about their cloud operating model, about their transformation um and ultimately in many cases about consumption of cloud as a service. Um and so um as we, you know, extend our own cloud capabilities, you know, out into other environment through distributed cloud program, what we refer to as as IBM cloud satellite, you know, that enables consistent and secure deployment of cloud um into any environment um where someone needs, you know, cloud to be operated. Um And that operating model conversation with our clients, you know, has to do with their own open shift environments that has to do with their software from IBM, it has to do their cloud services. And we're really ultimately looking to partner with clients to find efficiency in each stage of that journey and application modernization in deployment and then in getting consistency across all their environments, leveraging everything from uh the red hat, you know, ACM capabilities for cluster management up through a i for beauty shops and automation and use of a common console across services. And so it's an exciting time because we've been able to align our portfolio, get consistency and delivery of the red half capabilities across our full portfolio and then enable clients to progress to really efficient consumption of cloud. >>That's awesome. Great stuff there. I got to ask you the question that's on probably your customers minds. They say, okay, Hillary, you got me sold me on this. I get what's going on, I just gotta go faster. How do I advance my hybrid cloud model faster? What are you gonna do for me? What do you have within the red hat world and IBM world? How are you gonna make me go faster? That's in high quality way? >>Yeah. You know, we often like to start with an assessment of the application landscape because you move faster by moving strategically, right? So assessing applications and the opportunity to move most quickly into a cloud model, um, what to containerized first, what to invest in lift and shift perspective, etcetera. So we we help people look at um what is strategic to move and where the return on investment will be the greatest. We help them also with migrations, Right? So we can help jump in with additional skills and establish a cloud center of competency and other things like that. That can help them move faster as well as move faster with us. And I think ultimately choosing the right portfolio for what is defined as cloud is so important, having uh, an open based architecture and cloud deployment choice is so important so that you don't get stuck in where you made some of your initial decisions. And so I think those are kind of the three core components to how we're helping our clients move as quickly as possible and at the rate and pace that the current climate frankly demands of everyone. >>You know, I was joking with a friend the other night about databases and how generations you have an argument about what is it database, what's it used for. And then when you kind of get to that argument, all agree. Then a new database comes along and then it's for different functions. Just the growth in the internet and computing. Same with cloud, you kind of see a parallel thing where it's like debate, what is cloud? Why does he even exist? People have different definitions. That was, you know, I mean a decade or so ago. And then now we're at almost another point where it's again another read definition of, okay, what's next for cloud? It's almost like an inflection point here again. So with that I got to ask you as a fellow and IBM VP and Cto, what is the IBM cloud because if I'm going to have a discussion with IBM at the center of it, what does it mean to me? That's what people would like to know. How do you respond to that? >>Yeah. You know, I think two things I think number one to the, to the question of accelerating people's journeys to the cloud, we are very focused within the IBM cloud business um on our industry specific programs on our work with our traditional enterprise client base and regulated industries, things like what we're doing in cloud for financial services, where we're taking cloud, um and not just doing some sort of marketing but doing technology, which contextualize is cloud to tackle the difficult problems of those industries. So financial services, telco uh et cetera. And so I think that's really about next generation cloud, right? Not cloud, just for oh, I'm consuming some sauce, and so it's going to be in the cloud. Um but SAS and I SV capabilities and an organization's own capabilities delivered in a way appropriate to their industry in in a way that enables them to consume cloud faster. And I think along those lines then kind of second thing of, you know, whereas cloud headed the conversation in the industry around confidential computing, I think is increasingly important. Um It's an area that we've invested now for several generations of technology capability, confidential computing means being able to operate even in a cloud environment where there are others around um but still have complete privacy and authority over what you're doing. And that extra degree of protection is so important right now. It's such a critical conversation um with all of our clients. Obviously those in things like, you know, digital assets, custody or healthcare records or other things like that are very concerned and focused about data privacy and protection. And these technologies are obvious to them in many cases that yes, they should take that extra step and leverage confidential computing and additional data protection. But really confidential computing we're seeing growing as a topic zero trust other models like that because everyone wants to know that not only are they moving faster because they're moving to cloud, but they're doing so in a way that is without any compromise in their total security, um and their data protection on behalf of their clients. So it's exciting times. >>So it's so exciting just to think about the possibilities because trust more than ever now, we're on a global society, whether it's cyber security or personal interactions to data signing off on code, what's the mutability of it? I mean, it's a complete interplay of all the fun things of uh of the technology kind of coming together. >>Absolutely, yeah. There is so much coming together and confidential computing and realizing it has been a decade long journey for us. Right? We brought our first products actually into cloud in 2019, but its hardware, it's software, it services. It's a lot of different things coming together. Um but we've been able to bring them together, bring them together at enterprise scale able to run entire databases and large workloads and you know um pharmaceutical record system for Germany and customer records for daimler and um you know what we're doing with banks globally etcetera and so you know it's it's wonderful to see all of that work from our research division and our developers and our cloud teams kind of come together and come to fruition and and really be real and be product sizable. So it's it's very exciting times and it's it's a conversation that I think I encourage everyone to learn a little bit more about confidential computing. >>Hillary hunter. Thank you for coming on the cube. Vice President CTO and IBM fellow which is a big distinction at IBM. Congratulations and thanks for coming on the Cuban sharing your insight. Always a pleasure to have you on an expert always. Great conversation. Thanks for coming on. >>Thanks so much for having me. It was a pleasure. >>Okay, so cubes coverage of red Hat Summit 21 of course, IBM think is right around the corner as well. So that's gonna be another great event as well. I'm john Feehery, a host of the cube bringing all the action. Thanks for watching. Yeah.

>>mhm Yes. Welcome back to the cubes coverage of red hat summit 2021 virtual john for your host of the cube paul. Comey who's here is the president and Ceo of red hat cube alumni paul always great to have you on the leader of red hat now President and Ceo for a year I think about a year now we're looking at under your belt now part of IBM Great to see you. >>You too nice to see you again john. >>So we've talked many times on the Cuban now. It's kind of playing out in real time. The software world with open source has gone mainstream. The conversation was moved to the cloud. Okay. People move to the cloud. Cloud native emerges devil has been around for a while. But now the conversation is cloud for the enterprise that uh, the enterprises, it's a tough world. You gotta, it's complicated is a lot of legacies, a lot of value and you want the new stuff. This is what the conversation is now. It's shifted to I got cloud, it's hybrid. What's your reaction to that? >>Well, you know, it really is, as you say, it's complicated but it's evolving and really, really fast. I mean, you know, I think you remember we've been here a lot. You first remember first software is eating the world and open source software is eating the world and in every every company is becoming a software company. All true. But that evolution continues today with the proliferation of hybrid cloud environments that it encompasses everything from data centers to public cloud services to And even now we'll talk about two for far flung edge deployments. That's all now part of the cloud. I mean, this is all what makes up hybrid. I like to always say that Hybrid really is the new data centers but now see IOS and I thi leaders, they need to reconsider what their roles, what their role here is and the way we look at it as every C I O now needs to be a cloud operator because because Hybrid is what their environment is now today, that used to be all in their data center. So, so but one of the things that really makes a choice even more important and its leaders, they need to address address specific needs, um not only to the organization, but even as they change and evolve in this because it really is a dynamic environment, I mean think about it and just mentioned edge and how how important that is to see IOS, we weren't even talking about that two years ago, so, so it's not a single answer here, right? Um and and you know, and there as there wasn't a single answer when it was all in one building or in one data center, but now it's even it's even more complex. So, so we need to enable really a new wave of cloud operators here with technologies that can be deployed as cloud services as well as on premises. We'll talk more about this too, but and we'll talk about this at the summit. We talked about the summit. Cloud services become really important, especially managed services, for example, because, um because we're so complex, Hybrid brings so much power, but it is complex. You know, see I need help with this, they need help managing this now. And so that's really where a lot of our focus is today. >>It's interesting you say there's no single answer. I would agree with you because it's now you can actually do a lot more customization with cloud and Hybrid. I think there's a general sentiment and directionally correct answer uh in the industry is that hybrid is operating model right? And I think you guys are have a whole division of SRS google talks about this all the time and their cloud site reliability engineers. And I think you're seeing that in educational institutions which we'll talk about. But I think this idea of cloud scale as the new I. T. And you mentioned hybrids, the new data center. You know, I don't I don't want to offend my I. T. Friends out there but they're kind of all realizing it to that if they don't understand how to operate cloud scale they'll be irrelevant and they're and they understand that their jobs are not just provisioning storage, networking and servers. Those are now involved in a hybrid architecture. And by the way, there is no one recipe, it's dependent. Each enterprise can have its own set of architecture based on their workloads again. So I buy that no single answer, but there is hybrid and I think it's pretty well understood. I mean, do you agree with that? >>I absolutely agree with that. But let's take a look at this, unpack it a little bit and take a look at the building blocks a bit. Right. Um, you know, we talked about open sources, what's driving all of this now and and everything we're talking about here is built in and around Lennox and it was only possible because Lennox was so open, so available and became so powerful, that's now been the platform that all this new innovation is built around. I mean, I oftentimes saying it's true the cloud just wouldn't be here had Lennox not only made its way in the open source development environment, but made its way into the enterprise to enable it to companies like us that make it enterprise ready, secure etcetera. So I think that's really an important thing to understand here. So when you talk about skills that the Ceos need certainly SRE skills, operation skills etcetera, but they also need Lennox skills and even open source skills. So so I think I think that's important, everything that's coming down the road and in in this space in um in his open source based and built in and around Lennox things like ai quantum computing, autonomous vehicles um IOT in and out to the edge all built on a foundation of Lennox and open source. So we see it in the enterprise everywhere now. I mean a survey where you know we did a survey out there and looking at the survey of C I O s out there, open is predominant out there, Lennox is predominant out there in hybrid is predominant and growing in a pretty big clip every year. >>You know, paul, I want to get your reaction to something because this may be kind of a dot connecting moment for me because I want to get your thoughts on this because it's a it's a pattern I'm seeing emerging now multiple times and usually I thought this was kind of a one off, but I'm starting to see it. So I'm going to get your thoughts on this. You guys have been super successful with open source in the enterprise, Super successful over decades, building a community and an ecosystem now with open source with with cloud Native, specifically we're seeing end users participating more in the, in the contribution starts out with the hyper scale ear's but now you're seeing kind of, I would call general purpose mainstream enterprises contributing projects, not necessarily their expertise, but they've been participating in taking the goodness of open source and bringing that into the into the enterprise. And I'll see you relying on you guys as well. But now I'm starting to see the pattern where people are relying on you to bring your community to them and they merge their communities with you guys and being kind of a steward there, is that a pattern? Do you see that evolving? Because we've heard that on multiple interviews on the cube where we've heard end users say we love the red hat ecosystem and and that seems to be more and more about they want to be building their ecosystem. So you did it for yourselves, you did it for the industry. Now, enterprises want this service is this is this is a pattern. And what's your reaction to that? >>It actually is a pattern because it's actually one of the reasons why innovation is moving so quickly right now. As I just said, you know, you know, this whole area here in infrastructure and cloud and development environments, Hybrid included. It's all built in and around, it's all built in and around Lennox. And in the past, what's happening and driven by open source development in the past? What happened? Look at the old fashioned way, right, where a company like us would be in a company, software company, not like us, but any old software company would be, you know, in their stovepipe, talking to their customers, getting their requirements and then bringing those requirements back from the customer base and then trying to work that into their products over time, get that back out to the customer to test it and try it, see it as it works. That's probably a five year, there's probably a five year journey, uh, for big, big requirements for big change requirements you look at now with, with actually end users now participating in upstream development, they're building their requirements into that upstream, which is our development environment. And actually that's what feeds our products. And so we've cut out the middleman, if you will completely in there now when we're building those requirements into our future future, R and D work in the upstream and then we bring that down into a product back into their enterprise for them to use in production. So it cuts out years of time for that innovation to get from concept to building to product, rising to production. And, and I think, you know, john, that's one of the big reasons why that customer base participating is one of the big reason why we're seeing innovation move like we've never seen it before in the enterprise, which in the old days that was a stodgy place where they didn't want to move very quickly. >>Yeah. And the values there, I mean I think it's clear what the pandemic we get to this towards the the last last talking track here. But with the pandemic I think it's pretty clear what the value is and the speed to capture opportunities and growth. I think enterprises are realizing that I think the power of the ecosystem is a modern error kind of phenomenon that is now kind of showing its its value and clearly in the market. And I think people who harness communities and ecosystems not try to fork them but connect them and and intersect them and kind of played well together. So again this is an open source concept kind of re imagined so we'll keep an eye on that. So, um, I want to get to your comment in the kino you mentioned at the top here every C I. O. It has to be a cloud operator. You know, that reminds me of all the start ups and all the positioning statements. Every company needs to be a software company. Every company needs to be a media company. Every company needs to be a cloud operator. So I love that. What does it mean? Because I could say, hey paul, I have a cloud, I'm working on amazon Or is that it? Or wait a minute as yours got, I got 365 over here and I'm using big query over here. I might use oracle over here. I mean all these multi cloud conversations. So it's confusing. >>Yeah. Tell me what, you know, if you look at, if you look at it, we were really one of the first ones to really build around this hybrid, this hybrid concept. And the reason why we were one of the first ones is because what amazon hit the world 12 or 13 years ago or something like that, They were the first major cloud and at the time that the narrative was that, you know, every application was going to move to the cloud tomorrow. Right well, because as I said earlier, everything is built in and in and around open source. And legs were very involved with our customers as they tried to move those first applications to the cloud. So certainly is a lot of value and moving to the cloud. But our customers quickly realized with us helping them, quickly realized that you know what, this is great. But not every application suited for the cloud, um for any cloud, but also I may want to run multiple clouds because another cloud provider over here might have a better service than this particular service over here, vice versa. And so we were in the middle of that. So one of the decisions we made seven or eight years ago, everything we did in that last seven or eight years around the portfolio, whether it was building products, m and A, requiring new companies etcetera, was built around that hybrid portfolio. What that means is a common platform that sits both on premise and bare metal machines. Virtual machines, private clouds on premise multiple clouds across out in the enterprise, that common platform so that developers, operators and the security people have that common platform to build with because just like in Lenox, even though they are all derived from open source upstream, they're all different, they all make different choices and how they're going to configure themselves. So, so that's important. So now we're out there with these multiple clouds. One of our surveys we see our Ceo is telling us now that You're using on the average I think six Clouds today and they expect that to go 8-10 over the next 3-5 years. So how are they going to manage that? How are they going to secure that? How are their operations people going to operate with that? That's all the things that we've been working on over the last number of years. So from that common platform, which is sort of the basis which is open shift to underneath it, which is the Linux operating system, which is well that spans all those footprints that I talked about. And then also you look at one of the latest trends is as well as manage services because what customers are now telling us is okay I got this environment that this hybrid is now my data center. It means I have to worry about these apps all in different footprints. Um I want to the platform to act like a cloud in some cases I don't want to I don't want to even manage it. I want you to manage it for me because for many reasons I want great up time. I might not have the right skill sets in my organization and so I want you to manage it. And so that's where we develop managed services and that's where we have set a large group today large SRE group that's providing those managed services no matter where our platform runs for our customers. Also, what I talked about in my keynote today is that to support that thought process is that we're doing a lot of research in this and so, you know, in a typical computer science research world, you know, of the past, you might really be into the into the real computer science of Research. We with the consortium around mass Open cloud with Boston University, MIT, Harvard Northeastern with this consortium. We're running mass Open cloud on all Red Hat with the collaboration of these universities and we're really focusing on the sorry aspect of it. What do we need to manage it? What do we need around automation to manage it? What do we need around ai to manage it? What do we need for tools to manage it? And and that's really goes down to what I fully briefly said in the beginning, is that every C I O N I T uh executive now has to be their own cloud operator because they are effectively stitching all these disparate clouds together. So that's where a big part of our focus takes us all the way from, You know, upstream development to product to the research we're doing for the next 3-5 plus years. >>You know, I gotta say the hybrid cloud is a new data center which is implying I T in the cloud operators with C X O S and C IOS is interesting because it's validated by Mckinsey's recent report that came out that said there's a trillion dollars of untapped value in one retrofitting existing infrastructure and operations and to net new operate use cases that the cloud enables. So there's clearly not two categories of value proposition that businesses are facing. One is, you know, kind of take care of the existing and then also bring in the new that cloud enables. So, you know, I think that's really key and that will drive the business leaders to foresight, if you will to be agile and adaptive to that. So so totally agree on that. I love this open cloud initiative, you mentioned the mass open cloud which I know is kind of like this beanpot for techies, um people who know what that means, uh it's in the boston area these institutions um this is gonna be a training and an opportunity to train the next generation and if you take it to the next level cybersecurity is also in this kind of net new novelty, interdisciplinary components. So you got engineering which is like devops engineering and then Systems Engineering and Computer Science intersecting together with kind of this data discipline. So it hits cybersecurity which is a board level conversation, it hits the new business model opportunities which is a driver, this is new, this is there's no pre existing curriculum. What how do you explain that to heads of the departments and the deans of these institutions saying, you know, it's an engineering thing. No, it's computer science thing. No, it's a it's a business school thing with data science. What's your what's your conversation with folks in the industry when you say this is a different thing? >>Uh you know, the university, you know, the university is getting, it was actually one of the one of the first things this is you know what you'll see. You know, I talked to uh dr bob Brown from President bu earlier in an interview and and this is what we imagined with them early on and even they brought those disciplines together now in in in what they call a harry institute, where to bring data, computer science engineering as you say. And now even operations, it's almost like, you know, systems engineering on steroids, it's a really big spanning system. And so so the universities are starting understand that's why these universities in the consortium, that's why we're working here. But also, you know, the industry's kind of learning it the hard way because now that they get some of their developers starting to move some of their application developments out into one, maybe two clouds and having the now they have to figure out how they're going to do all those things that we talked about, develop, secure operated. So they're they're learning the hard way that this is the new discipline because that's reality. I also think that, you know, as I said, like anything in tech, we always say this is going to happen tomorrow. I also think, like I said, when when cloud first came came out, everybody saying, I'm moving every app to the cloud tomorrow. We even had customers that bought into that said we're moving going full board but they realized once they get into it it wasn't practical. Don't take me wrong. Cloud brings a ton of value here but from a practical perspective it's going to be some apps and across many clouds and and so now they're having to deal with the I. T. Execs and the C. I. Was having to deal with it. So they're learning really fast because of the reality that they have to deal with. Now having said all that to it also brings up why managed services you're seeing so popular right now because as that's moving so fast they just don't have the skills necessary in many cases to really operate and run in this in this type of environment. It brings so much power but the skills aren't necessarily there in the industry. So that now you see the connection between the industry where we sit and even the university now looking at this whole big problem as as you put said, john, actually a new discipline, >>I think, I think, and I think one final leg of a three legged stool is at the business schools because when you think about systems programming, you mentioned that and you know, I love to go back in history and look at the history of operating systems. And you know, paul, we've talked us in the past and you guys know a lot about operating systems from a technology standpoint, it's not just about a productivity suite for a user or a department with the system, it's a company that needs to be programmed. So when people want to globally operate their business, that software defined this isn't now and this is now happening, right? So this the new leaders in these companies that want to run these global companies that scale operate them, just like operating the business not necessary. Operating a tech or shiny new toy, have to build the operating system for the business. To me, I think that's where I see IBM looking at cloud differently and saying, hey, this is an operating system under the covers for the business. The applications are multi fold from, you know, an application for productivity to an edge device, industrial or consumer user work at home. I mean it's a plethora of applications. What's your reaction to that? And you you see the same thing? >>I mean frankly, I think this is an area that a lot of the infrastructure players missed in the past. And I think I think this is what IBM saw with with bringing us in as well. It's all about the application. You know, I said earlier that, you know, we said every every company was a software company is true. And so that means the companies are running their businesses on these applications. So it's all about the app and I think a lot of infrastructure companies miss that. And and so with Hybrid now you have that ability to run the app wherever makes the most sense for for a whole host of reasons. And so now, but now comes the complexity of all of that. I think, I think IBM with bringing us in saw that that Hybrid was maybe as big, if not a bigger opportunity than cloud itself because of of the complexity it's going to bring, the power is going to bring. But also the complexity is gonna bring. I see that's why, you see Arvind, I sort of doubling down the entire IBM company on on hybrid services that are that are going to be really important here, that they provide these applications on top that are going to be really important, but that have to be architected in such a way that they can run in a hybrid environment. And finally there's all the infrastructure and tools and development pieces that we bring to the table. So, So yeah, I think I think are really, really understood that as they made the decision to bring redheaded, >>I talked to a center all the time and they also have this kind of concept of re factoring and reprogramming your business. Uh, it's not, it's a holistic view. This is kind of what's happening. So my final question for you is as as that becomes software enabled and programmed if you will with applications the business with many different subsystems in there. Um a lot of companies now looking at the light at the end of the tunnel with the pandemic and they're seeing vaccines coming out. Some say vaccines will be pretty much everywhere, everyone over 12 by the fall. So we're back to real life. There's gonna be a pullback of some projects on doubling down on others. As you as you mentioned, what are we doing? We're starting to see hybrid as companies come out of the pandemic, they're all jockeying to make sure that they have either done their work to re factor or reposition, reprogrammed their business and be set up for net new opportunities. >>What >>do you see as a growth model or growth opportunities for companies? You want to come out with a growth strategy out of the gate of the pandemic. What's your thoughts? >>Well, I mean, I think you have to plan for companies have to plan for your workforce to be anywhere, but in order to be anywhere in and to be productive, you need you need services like we're on right now for example, but you need the infrastructure to be able to do that. You need you need a way for your customers if you buy the fact that every company is a software company, you're running a business through their applications either way for your customers to be able to interact with you anywhere from where they are anywhere in a real time way. And so I think that's why from our perspective, things like that we're pushing a lot on the edge. Now, that's why you're seeing the hybrid cloud moved all the way out into the edge and you can see it in every vertical, you know, in the telco space. The edge means you gotta do, you have data and compute that needs to be done on the set on the cell tower in the manufacturing world. You have the state and compute that needs to be done on the factory floor, in the retail vertical. We see the edge really being significant in all these verticals, but but that edge is now extends that hybrid data center that we've been talking so much about. So even though you have all these edge devices way out there on the edge, it's a critical part of the business. So you have to have, your developers need need to be able to develop for it, you need to secure it, you need to and you need to operate it and manage it. So now, you know, in a very short period of time, hybrids taken on another dimension, bringing you out to all these points on the edge which is the same but slightly different in every vertical. Now comes complexity and that's why automation is so important because with that power comes complexity but it's going to take automation to keep it all running, >>paul. Great insight. Thanks for coming on the cube. Open innovation out in the open with with you guys again continue. And the focus of the evolution of software and the cloud with enterprise I. T. Clearly a lot of innovation and your contribution to academia and the mass open cloud and all the open cloud initiatives, phenomenal. The world's going. Open source and continues and continues. Doesn't stop. The operating system of businesses is coming and you guys are well positioned. Thanks for coming on. >>Thanks again john. Always a pleasure. >>Okay paul, Cormier, President Ceo of Red Hat here on the Cuban, john for your host. Thanks for watching. Yeah. Yeah. Mhm mm.

>>From around the globe, it's the Cube with digital coverage of IBM, think 2021 brought to you by IBM. >>Welcome to the cubes, digital coverage of IBM Think 2021 fine lisa martin. Next joining me is Leo Lebron's director of global strategic initiatives at Aws. Leo, Welcome to the cube. >>Thank you. >>So, talk to me about AWS and IBM. What's going on there with the relationship? What are some of the things that are significant for both partners? >>Yeah, absolutely. You know, IBM relationship really started with us around 2016, I would say it was a little bit more opportunistic at the time, we knew there was an opportunity to go to market together. We knew there were some great things we could do for our customers, but we haven't quite cracked, cracked the code, so to speak, on, on when and where and why we're going to partner at that point. Um you fast forward into the sort of 2017 to 2019 timeframe, um and we became a lot more intentional about how we're going to go to market where we were going to invest. Areas such as S. A. P, et cetera, were early, want to be identified. Um and I'd say the ball really started rolling sort of in the 2018 time Frank, a combination of a number of different things occurred. Uh You know, the the acquisition of Red Hat obviously, you know, Red Hat is a very significant, was a very significant partner with a W. S prior to the acquisition. Um And so post acquisition, you combine that with ramping up a workforce focused on AWS, combined with a number of different competencies at A W or IBM really invested in around migration as an example or S. A. P. Um and you know, the ball really started to roll quickly. Um after that, you know, I'd say in the last 18 months or so, we've both invested, significant in the relationship expansion around the world really, and in joint resources and capability to make sure that we're going to mark, it's sort of a partnered intentional way rather than sort of opportunistic. Uh >>Oh God, >>yeah, I'd say so far that's that's absolutely been paying off. Um and that we are seeing a number of winds all around the world across a broad set of industries as well as a broad set of technologies. Um so, you know, the strength of IBM consulting services in particular, but also their software, combined with the strength of our platform, is really proven to be successful for our customers. >>So you said started in 2016, really started taking shape in the last couple of years. That redhead acquisition talk to me about what's in this for customers. I imagine customers that are, that are expanding or needing to move workloads into the cloud or maybe more of a hybrid cloud approach. What are some of the big benefits that customers are going to gain from this partnership? >>Yeah, absolutely. Uh, reality is um, IBM has a long and storied history and relationship with their customers, right? Um, They run and manage many of the workloads. Um, they really know the customer's business incredibly well. Um They have domain expertise and industry, um, and then the technology expertise from a professional services perspective to really help navigate the waters and and determine what the right strategy is around moving to the cloud, right? You combine that with the depth and breadth of the skills and capabilities and services the WS provides. Um and the fact that IBM has invested significantly in making sure their professional services are deeply steeped in our technology and capabilities. Um, it's a great combination of really understanding the customer's needs plus the art of the possible honestly, when it comes to technology that we provide, really can accelerate both and mitigate risk when it comes to move into the club, >>that risk mitigation is key. So you guys, recently a W has recently launched, I'm gonna get this right red hat, open shift service on AWS or Rosa. Can you talk to me a little bit about rosa? >>Yeah, so um Red Hat obviously very well known and ultimately adopted within the enterprise. Um, we have built a fully managed service around red hat on AWS. Um, what that means is um, you'll have access to essentially the capabilities that that red hat would normally provide, but all containerized within a solution that allows you to have access to AWS services, right. Um, the other benefit here is normally you would get sort of a multi vendors with invoicing and cost model right? Where you get built from red hat get built from amazon, you get built from IBM um, in this case it's it's essentially a holistic service in which there is a single sort of invoicing and vendor relationship. Right? Um, so it's a combination of capabilities that normally would be provided the red hat combined with access to cloud and all the interfaces and capabilities around um, open shift etcetera that you could do their um, plus a more interesting and beneficial commercial model. >>So streamlined pricing model, streamlined operating model for customers. Talk to me about some of the customers that have adopted it. Give me a look into some of the industry's where you've seen good adoption and some of the results that they're gaining so far. >>Yeah, one second. Sorry. It's like insanely love uh worries. >>Let's just take it, let's just take a >>pause. Like we can >>just we can just so yeah, we'll go right as if lisa lisa just finish the question. Um so just take a breather. Yeah, as long as it as it needs. Um and then whenever you're ready, whenever that's that's died down, just just give it a beat, give it like a second and then just write as if she >>just yeah. >>Oh cut it out as if nothing happened. >>Give me >>two minutes. Mhm. >>So actually on your question, I know the answer from things that I've done recently, but was there an official answer Teresa, I'm supposed to give them the >>No, not >>really. I mean, I think what you're talking about on Red Hat specifically >>right earlier. >>No, I mean there's a product page and stuff, it's really about just the >>the >>ability of customers to be able to run those solutions on the AWS console is really the gist of it and then it's fully integrated. >>Not sure advantage of the examples I know of are publicly referenced. >>That's okay. You could just say customer in X y z industry. That's totally fair. Not to worry about that. Yeah, >>I don't know if uh, so rosa, lisa rosa was just launched in March and so it's brand new. So I don't know, I'm the customer stories yet, >>so >>that's why I don't have them listed for leo >>that's fine. That's totally fine. Maybe we can talk about, you know, since the launch was just around the corner, some of the things that have been going on the momentum interest from customers questions conversations, you mean more like that as you're launching the GTM >>Yeah, and there's certainly a couple of industries that they have targeted. So as well as a couple of customers. >>Yeah, thank you >>lisa. Of course. I think they went around the corner. >>All right, let me know and I'll re ask the question. I'll tweak it a little >>bit. Alright, >>so talk to me about Rosa just launched very recently. Talked to me about customer interest adoption. Maybe some of the industry's in particular if you're seeing any industry that's kind of really leading edge here and taking advantage of this new manage service. >>Yeah. So no big surprise, right. The existing customer base that currently uses red at Lenox and some of the options and open shift etcetera that are out today are then the right customers to potentially look at this when it comes to moving forward. Um, you know, industry wise, certainly there are areas in financial services, banking, insurance, um, et cetera. We're also seeing some around manufacturing a little a little less so, but some in media and telco as well. Um, So it's, it's a broad swath of the applicability of red hat and open shift is somewhat universal, but the early customer base is larger than sort of in those three areas. >>What I'm curious what the key target audiences are these Red Hat customers are these AWS customers? IBM all three. >>Yeah. I mean there isn't necessarily the perfect customer that we're not necessarily looking for as much as um if there are existing customers that are currently using Lennox for using Red Hat. Um, if there are someone who, a customer who currently has a relationship with either a W. S. Or IBM, um, there's an opportunity to essentially look at it from any of the angles if you're already on cloud or you've already experienced AWS in some shape or form, there's an opportunity to potentially to leverage rosa to further expand that capability and also have some more flexibility, so to speak. Um if you're already using IBM as a professional services provider and advisory firm, then they absolutely have the expertise and understanding of this product set to help you understand how it could be best leverage. Right? So you can kind of look at it from either the dimensions. Um if it's a customer that's completely new to all of us, then we're happy to talk to you. But um, it's uh, it's something that we'll definitely take a little bit more explanation to understand or why why you should or shouldn't consider this multi cloud open shift. Absolution >>got it. Let's shift gears a bit and talk about ASAP when we think about customers looking to migrate ASAP workloads to the cloud, looking at the right cloud provider providers and those are really big challenging strategic decisions for leadership to make. Talk to me about why when you're in those conversations, AWS is the best choice. >>Absolutely. I mean, really AWS and say with S A P N with many of our services is really looking to give all the options that you could conceivably need or want in order to engage in cloud migration and transformation. Um, press safety specifically right, There are a number of different options, right? You could go for a lift and shift or upgrade from many database. Too sweet on safety hana. Um, could potentially look to modernize and leverage cloud services, post post migration as well as the sort of final Pinnacle of that is a complete transformation to S four, S 4 Hana as far as why AWS specifically beyond just choice. Um, You know, from a from a cost perspective, uh it's a pretty, pretty compelling and we have some pretty compelling business and use cases around ultimately the cost savings that come when, when you move from an on premise S A. P implementation to cloud. Beyond that, usually the cloud migration itself as an opportunity to uh condense or reduce the number of instances you're paying for from an S A S a P perspective, which then further reduces cost um from a reliability perspective, you know, AWS is is the world's most secure, extensive, reliable part infrastructure, right? Um, any of the instances that you put on AWS are uh, instantly and say fairly instantly provision in such a way that they're they are provided across multiple what we call availability zones, um, which is giving you for the resiliency and the stability that really no other cloud broke Right. Um On the security front, I mean, this is really a unique position in that AWS plus IBM and the security, the depth and security services, you know, numerous years of professional services work um that IBM has done the security space um you know, they have roughly 8000 or so cybersecurity experts with an IBM so the combination of their expertise and security plus the security of our platform um is a great combination. Um I'd say the final one is around performance. Right. AWS offers many more cloud native options around certified ASAP instances specifically all the way from 256 gigabyte option all the way up to 24 terabytes, which is the largest of its kind. Um and as as those who have implemented ASAP No, it's a very resource intensive so having the ability to do that from a performance perspective is is a key differentiator for sure. >>Talk to me from your opinion about why IBM for S. A. P on AWS, why should customers go that direction for their projects? >>Yeah. You know, ASAP has, sorry, safety, IBM has over 40 years of experience in implementing ASAP for their customers. Right. They've done I think it's over 6000 S. A. P migrations, uh 40,000 global S A. P consultants around the world. Right. So from a capability and depth of experience, uh yeah, there's a lot of nuance to doing a safety implantation, particularly one that's been moving from on prem to the cloud. Um you know, they've got they've got the experience right beyond that, they have industry specific solutions that are pre configured. So I think that is 12 industry specific industry solutions we configured for S. A. P. It allows, you know, roughly 20-30 acceleration when it comes to implementation of platform. So um combination of just depth of experience, death of capability combined with these solutions to accelerate are all key key reasons for sure. >>The acceleration yet you bring up, sorry, is interesting because we saw in the last year the acceleration of digital transformation projects and businesses needing to pivot again and again and again to figure out how to survive and be successful in this very dynamic market in which we're still living anything industry. Why is it specific that you saw that was really driving the acceleration and the use cases for Rosa in the last year? Yeah, >>yeah. So you ASAP we saw an interesting trend as a result of what everyone's been experiencing in the last year with Covid etcetera. Um you know, many organizations postponed large european implementations and large as a few migrations because of what you just said, right, they weren't entirely sure um what would need to be done in order to survive either competitive threats or more? Just the global threats that are occurring. Um so what we saw was really none of, none of the transformations went away. They were put on hold for a period of time, let's say 6-9 months ago, maybe even a year ago almost um in lieu of I would say more um top line revenue generating or innovative type solutions that maybe we're focused specifically at, you know, the changing dynamic with with Covid. Um Since then we've seen a combination of those new ideas, right? Combination of the new innovation around health care of course, but also public sector and um you know, a lower unemployment and you know, the engagement there, we sent a combination of those new ideas and new innovations with the original goal of optimizing transforming ASAP, europe et cetera, And then combining the two to allow access to the data right that sits inside the S. A. P. Implementation ASAP, Combined the data asap with all these new innovations and then ultimately use that to sort of capitalize on what the future business is going to be. Um that's been huge. It's been very interesting to see some organizations completely changed their business model over the course of the last 12 months um in ways they probably had never intended you before. Right? But it's it's absolutely become an opportunity, you know, time with a lot of challenges. >>I agree there are silver linings and we've seen a lot of those interesting opportunities to your point and businesses probably would never have come up with had there not been a forcing function like we've been living with Julio. Thank you for joining me today. Talking to me about what's going on with I. B. M. And A W. S will be excited to follow. What happens with Rosa as a, uh, continues to roll out and we appreciate you joining us on the program. >>Absolutely. Thank you for time. >>Pearly Lebron chime lisa martin. You're watching the cubes digital coverage of IBM think 2021. Mhm.

>>from around the globe. It's the Cube presenting enterprise. Digital resilience on hybrid and multi cloud Brought to You by Iota Ho. Hello, everyone, and welcome to our continuing Siri's covering data automation brought to you by Io Tahoe. Today we're gonna look at how to ensure enterprise resilience for hybrid and multi cloud. Let's welcome in age. Eva Hora, who is the CEO of Iota A J. Always good to see you again. Thanks for coming on. >>Great to be back. David Pleasure. >>And he's joined by Fozzy Coons, who is a global principal architect for financial services. The vertical of financial services. That red hat. He's got deep experiences in that sector. Welcome, Fozzie. Good to see you. >>Thank you very much. Happy to be here. >>Fancy. Let's start with you. Look, there are a lot of views on cloud and what it is. I wonder if you could explain to us how you think about what is a hybrid cloud and and how it works. >>Sure, yes. So the hybrid cloud is a 90 architecture that incorporates some degree off workload, possibility, orchestration and management across multiple clouds. Those clouds could be private cloud or public cloud or even your own data centers. And how does it all work? It's all about secure interconnectivity and on demand. Allocation of resources across clouds and separate clouds can become hydrate when they're similarly >>interconnected. And >>it is that interconnectivity that allows the workloads workers to be moved and how management can be unified in off the street. You can work and how well you have. These interconnections has a direct impact on how well your hybrid cloud will work. >>Okay, so we'll fancy staying with you for a minute. So in the early days of Cloud that turned private Cloud was thrown a lot around a lot, but often just meant virtualization of an on PREM system and a network connection to the public cloud. Let's bring it forward. What, in your view, does a modern hybrid cloud architecture look like? >>Sure. So for modern public clouds, we see that, um, teams organizations need to focus on the portability off applications across clouds. That's very important, right? And when organizations build applications, they need to build and deploy these applications as small collections off independently, loosely coupled services, and then have those things run on the same operating system which means, in other words, running it on Lenox everywhere and building cloud native applications and being able to manage and orchestrate thes applications with platforms like KUBERNETES or read it open shit, for example. >>Okay, so that Z, that's definitely different from building a monolithic application that's fossilized and and doesn't move. So what are the challenges for customers, you know, to get to that modern cloud? Aziz, you've just described it. Is it skill sets? Is that the ability to leverage things like containers? What's your view there? >>So, I mean, from what we've seen around around the industry, especially around financial services, where I spent most of my time, we see that the first thing that we see is management right now because you have all these clouds and all these applications, you have a massive array off connections off interconnections. You also have massive array off integrations, possibility and resource allocations as well, and then orchestrating all those different moving pieces. Things like storage networks and things like those are really difficult to manage, right? That's one. What s O Management is the first challenge. The second one is workload, placement, placement. Where do you place this? How do you place this cloud? Native applications. Do you or do you keep on site on Prem? And what do you put in the cloud? That is the the the other challenge. The major one. The third one is security. Security now becomes the key challenge and concern for most customers. And we could talk about how hundreds? Yeah, >>we're definitely gonna dig into that. Let's bring a J into the conversation. A J. You know, you and I have talked about this in the past. One of the big problems that virtually every companies face is data fragmentation. Um, talk a little bit about how I owe Tahoe unifies data across both traditional systems legacy systems. And it connects to these modern I t environments. >>Yeah, sure, Dave. I mean, fancy just nailed it. There used to be about data of the volume of data on the different types of data. But as applications become or connected and interconnected at the location of that data really matters how we serve that data up to those those app. So working with red hat in our partnership with Red Hat being able Thio, inject our data Discovery machine learning into these multiple different locations. Would it be in AWS on IBM Cloud or A D. C p R. On Prem being able thio Automate that discovery? I'm pulling that. That single view of where is all my data then allows the CEO to manage cast that can do things like one. I keep the data where it is on premise or in my Oracle Cloud or in my IBM cloud on Connect. The application that needs to feed off that data on the way in which you do that is machine learning. That learns over time is it recognizes different types of data, applies policies to declassify that data. Andi and brings it all together with automation. >>Right? And that's one of the big themes and we've talked about this on earlier episodes. Is really simplification really abstracting a lot of that heavy lifting away so we can focus on things A. J A. Z. You just mentioned e nifaz e. One of the big challenges that, of course, we all talk about his governance across thes disparity data sets. I'm curious as your thoughts. How does Red Hat really think about helping customers adhere to corporate edicts and compliance regulations, which, of course, are are particularly acute within financial services. >>Oh, yeah, Yes. So for banks and the payment providers, like you've just mentioned their insurers and many other financial services firms, Um, you know, they have to adhere Thio standards such as a PC. I. D. S s in Europe. You've got the G g d p g d p r, which requires strange and tracking, reporting documentation. And you know, for them to to remain in compliance and the way we recommend our customers to address these challenges is by having an automation strategy. Right. And that type of strategy can help you to improve the security on compliance off the organization and reduce the risk after the business. Right. And we help organizations build security and compliance from the start without consulting services residencies. We also offer courses that help customers to understand how to address some of these challenges. And that's also we help organizations build security into their applications without open sources. Mueller, where, um, middle offerings and even using a platform like open shift because it allows you to run legacy applications and also continue rights applications in a unified platform right And also that provides you with, you know, with the automation and the truly that you need to continuously monitor, manage and automate the systems for security and compliance >>purposes. Hey, >>Jay, anything. Any color you could add to this conversation? >>Yeah, I'm pleased. Badly brought up Open shift. I mean, we're using open shift to be able. Thio, take that security application of controls to to the data level. It's all about context. So, understanding what data is there being able to assess it to say who should have access to it. Which application permission should be applied to it. Um, that za great combination of Red Hat tonight. Tahoe. >>But what about multi Cloud? Doesn't that complicate the situation even even further? Maybe you could talk about some of the best practices to apply automation across not only hybrid cloud, but multi >>cloud a swell. Yeah, sure. >>Yeah. So the right automation solution, you know, can be the difference between, you know, cultivating an automated enterprise or automation caress. And some of the recommendations we give our clients is to look for an automation platform that can offer the first thing is complete support. So that means have an automation solution that provides that provides, um, you know, promotes I t availability and reliability with your platform so that you can provide, you know, enterprise great support, including security and testing, integration and clear roadmaps. The second thing is vendor interoperability interoperability in that you are going to be integrating multiple clouds. So you're going to need a solution that can connect to multiple clouds. Simples lee, right? And with that comes the challenge off maintain ability. So you you you're going to need to look into a automation Ah, solution that that is easy to learn or has an easy learning curve. And then the fourth idea that we tell our customers is scalability in the in the hybrid cloud space scale is >>is >>a big, big deal here, and you need a to deploy an automation solution that can span across the whole enterprise in a constituent, consistent manner, right? And then also, that allows you finally to, uh, integrate the multiple data centers that you have, >>So A J I mean, this is a complicated situation, for if a customer has toe, make sure things work on AWS or azure or Google. Uh, they're gonna spend all their time doing that, huh? What can you add really? To simplify that that multi cloud and hybrid cloud equation? >>Yeah. I could give a few customer examples here Warming a manufacturer that we've worked with to drive that simplification Onda riel bonuses for them is has been a reduction cost. We worked with them late last year to bring the cost bend down by $10 million in 2021 so they could hit that reduced budget. Andre, What we brought to that was the ability thio deploy using open shift templates into their different environments. Where there is on premise on bond or in as you mentioned, a W s. They had G cps well, for their marketing team on a cross, those different platforms being out Thio use a template, use pre built scripts to get up and running in catalog and discover that data within minutes. It takes away the legacy of having teams of people having Thio to jump on workshop cause and I know we're all on a lot of teens. The zoom cause, um, in these current times, they just sent me is in in of hours in the day Thio manually perform all of this. So yeah, working with red hat applying machine learning into those templates those little recipes that we can put that automation toe work, regardless of which location the data is in allows us thio pull that unified view together. Right? >>Thank you, Fozzie. I wanna come back to you. So the early days of cloud, you're in the big apple, you know, financial services. Really well. Cloud was like an evil word within financial services, and obviously that's changed. It's evolved. We talked about the pandemic, has even accelerated that, Um And when you really, you know, dug into it when you talk to customers about their experiences with security in the cloud it was it was not that it wasn't good. It was great, whatever. But it was different. And there's always this issue of skill, lack of skills and multiple tools suck up teams, they're really overburdened. But in the cloud requires new thinking. You've got the shared responsibility model you've got obviously have specific corporate requirements and compliance. So this is even more complicated when you introduce multiple clouds. So what are the differences that you can share from your experience is running on a sort of either on Prem or on a mono cloud, um, or, you know, and versus across clouds. What? What? What do you suggest there? >>Yeah, you know, because of these complexities that you have explained here, Miss Configurations and the inadequate change control the top security threats. So human error is what we want to avoid because is, you know, as your clouds grow with complexity and you put humans in the mix, then the rate off eras is going to increase, and that is going to exposure to security threat. So this is where automation comes in because automation will streamline and increase the consistency off your infrastructure management. Also application development and even security operations to improve in your protection, compliance and change control. So you want to consistently configure resources according to a pre approved um, you know, pre approved policies and you want to proactively maintain a to them in a repeatable fashion over the whole life cycle. And then you also want to rapid the identified system that require patches and and reconfiguration and automate that process off patching and reconfiguring so that you don't have humans doing this type of thing, right? And you want to be able to easily apply patches and change assistant settings. According Thio, Pre defined, based on like explained before, you know, with the pre approved policies and also you want is off auditing and troubleshooting, right? And from a rate of perspective, we provide tools that enable you to do this. We have, for example, a tool called danceable that enables you to automate data center operations and security and also deployment of applications and also obvious shit yourself, you know, automates most of these things and obstruct the human beings from putting their fingers on, causing, uh, potentially introducing errors right now in looking into the new world off multiple clouds and so forth. The difference is that we're seeing here between running a single cloud or on prem is three main areas which is control security and compliance. Right control here it means if your on premise or you have one cloud, um, you know, in most cases you have control over your data and your applications, especially if you're on Prem. However, if you're in the public cloud, there is a difference there. The ownership, it is still yours. But your resources are running on somebody else's or the public clouds. You know, e w s and so forth infrastructure. So people that are going to do this need to really especially banks and governments need to be aware off the regulatory constraints off running, uh, those applications in the public cloud. And we also help customers regionalize some of these choices and also on security. You will see that if you're running on premises or in a single cloud, you have more control, especially if you're on Prem. You can control this sensitive information that you have, however, in the cloud. That's a different situation, especially from personal information of employees and things like that. You need to be really careful off that. And also again, we help you rationalize some of those choices. And then the last one is compliant. Aziz. Well, you see that if you're running on Prem or a single cloud, um, regulations come into play again, right? And if you're running a problem, you have control over that. You can document everything you have access to everything that you need. But if you're gonna go to the public cloud again, you need to think about that. We have automation, and we have standards that can help you, uh, you know, address some of these challenges for security and compliance. >>So that's really strong insights, Potsie. I mean, first of all, answerable has a lot of market momentum. Red hats in a really good job with that acquisition, your point about repeatability is critical because you can't scale otherwise. And then that idea you're you're putting forth about control, security compliance It's so true is I called it the shared responsibility model. And there was a lot of misunderstanding in the early days of cloud. I mean, yeah, maybe a W s is gonna physically secure the, you know, s three, but in the bucket. But we saw so many Miss configurations early on. And so it's key to have partners that really understand this stuff and can share the experiences of other clients. So this all sounds great. A j. You're sharp, you know, financial background. What about the economics? >>You >>know, our survey data shows that security it's at the top of the spending priority list, but budgets are stretched thin. E especially when you think about the work from home pivot and and all the areas that they had toe the holes that they had to fill their, whether it was laptops, you know, new security models, etcetera. So how do organizations pay for this? What's the business case look like in terms of maybe reducing infrastructure costs so I could, you know, pay it forward or there's a There's a risk reduction angle. What can you share >>their? Yeah. I mean, the perspective I'd like to give here is, um, not being multi cloud is multi copies of an application or data. When I think about 20 years, a lot of the work in financial services I was looking at with managing copies of data that we're feeding different pipelines, different applications. Now what we're saying I talk a lot of the work that we're doing is reducing the number of copies of that data so that if I've got a product lifecycle management set of data, if I'm a manufacturer, I'm just gonna keep that in one location. But across my different clouds, I'm gonna have best of breed applications developed in house third parties in collaboration with my supply chain connecting securely to that. That single version of the truth. What I'm not going to do is to copy that data. So ah, lot of what we're seeing now is that interconnectivity using applications built on kubernetes. Um, that decoupled from the data source that allows us to reduce those copies of data within that you're gaining from the security capability and resilience because you're not leaving yourself open to those multiple copies of data on with that. Couldn't come. Cost, cost of storage on duh cost of compute. So what we're seeing is using multi cloud to leverage the best of what each cloud platform has to offer That goes all the way to Snowflake and Hiroko on Cloud manage databases, too. >>Well, and the people cost to a swell when you think about yes, the copy creep. But then you know when something goes wrong, a human has to come in and figured out um, you brought up snowflake, get this vision of the data cloud, which is, you know, data data. I think this we're gonna be rethinking a j, uh, data architectures in the coming decade where data stays where it belongs. It's distributed, and you're providing access. Like you said, you're separating the data from the applications applications as we talked about with Fozzie. Much more portable. So it Z really the last 10 years will be different than the next 10 years. A. >>J Definitely. I think the people cast election is used. Gone are the days where you needed thio have a dozen people governing managing black policies to data. Ah, lot of that repetitive work. Those tests can be in power automated. We've seen examples in insurance were reduced teams of 15 people working in the the back office China apply security controls compliance down to just a couple of people who are looking at the exceptions that don't fit. And that's really important because maybe two years ago the emphasis was on regulatory compliance of data with policies such as GDP are in CCP a last year, very much the economic effect of reduce headcounts on on enterprises of running lean looking to reduce that cost. This year, we can see that already some of the more proactive cos they're looking at initiatives such as net zero emissions how they use data toe under understand how cape how they can become more have a better social impact. Um, and using data to drive that, and that's across all of their operations and supply chain. So those regulatory compliance issues that may have been external we see similar patterns emerging for internal initiatives that benefiting the environment, social impact and and, of course, course, >>great perspectives. Yeah, Jeff Hammer, Bucker once famously said, The best minds of my generation are trying to get people to click on ads and a J. Those examples that you just gave of, you know, social good and moving. Uh, things forward are really critical. And I think that's where Data is gonna have the biggest societal impact. Okay, guys, great conversation. Thanks so much for coming on the program. Really appreciate your time. Keep it right there from, or insight and conversation around, creating a resilient digital business model. You're watching the >>Cube digital resilience, automated compliance, privacy and security for your multi cloud. Congratulations. You're on the journey. You have successfully transformed your organization by moving to a cloud based platform to ensure business continuity in these challenging times. But as you scale your digital activities, there is an inevitable influx of users that outpaces traditional methods of cybersecurity, exposing your data toe underlying threats on making your company susceptible toe ever greater risk to become digitally resilient. Have you applied controls your data continuously throughout the data Lifecycle? What are you doing to keep your customer on supply data private and secure? I owe Tahoe's automated, sensitive data. Discovery is pre programmed with over 300 existing policies that meet government mandated risk and compliance standards. Thes automate the process of applying policies and controls to your data. Our algorithm driven recommendation engine alerts you to risk exposure at the data level and suggests the appropriate next steps to remain compliant on ensure sensitive data is secure. Unsure about where your organization stands In terms of digital resilience, Sign up for a minimal cost commitment. Free data Health check. Let us run our sensitive data discovery on key unmapped data silos and sources to give you a clear understanding of what's in your environment. Book time within Iot. Tahoe Engineer Now >>Okay, let's now get into the next segment where we'll explore data automation. But from the angle of digital resilience within and as a service consumption model, we're now joined by Yusuf Khan, who heads data services for Iot, Tahoe and Shirish County up in. Who's the vice president and head of U. S. Sales at happiest Minds? Gents, welcome to the program. Great to have you in the Cube. >>Thank you, David. >>Trust you guys talk about happiest minds. This notion of born digital, foreign agile. I like that. But talk about your mission at the company. >>Sure. >>A former in 2011 Happiest Mind is a born digital born a child company. The reason is that we are focused on customers. Our customer centric approach on delivering digitals and seamless solutions have helped us be in the race. Along with the Tier one providers, Our mission, happiest people, happiest customers is focused to enable customer happiness through people happiness. We have Bean ranked among the top 25 i t services company in the great places to work serving hour glass to ratings off 41 against the rating off. Five is among the job in the Indian nineties services company that >>shows the >>mission on the culture. What we have built on the values right sharing, mindful, integrity, learning and social on social responsibilities are the core values off our company on. That's where the entire culture of the company has been built. >>That's great. That sounds like a happy place to be. Now you said you had up data services for Iot Tahoe. We've talked in the past. Of course you're out of London. What >>do you what? Your >>day to day focus with customers and partners. What you focused >>on? Well, David, my team work daily with customers and partners to help them better understand their data, improve their data quality, their data governance on help them make that data more accessible in a self service kind of way. To the stakeholders within those businesses on dis is all a key part of digital resilience that will will come on to talk about but later. You're >>right, e mean, that self service theme is something that we're gonna we're gonna really accelerate this decade, Yussef and so. But I wonder before we get into that, maybe you could talk about the nature of the partnership with happiest minds, you know? Why do you guys choose toe work closely together? >>Very good question. Um, we see Hyo Tahoe on happiest minds as a great mutual fit. A Suresh has said, uh, happiest minds are very agile organization um, I think that's one of the key things that attracts their customers on Io. Tahoe is all about automation. Uh, we're using machine learning algorithms to make data discovery data cataloging, understanding, data done. See, uh, much easier on. We're enabling customers and partners to do it much more quickly. So when you combine our emphasis on automation with the emphasis on agility that happiest minds have that that's a really nice combination work works very well together, very powerful. I think the other things that a key are both businesses, a serious have said, are really innovative digital native type type companies. Um, very focused on newer technologies, the cloud etcetera on. Then finally, I think they're both Challenger brands on happiest minds have a really positive, fresh ethical approach to people and customers that really resonates with us at Ideo Tahoe to >>great thank you for that. So Russia, let's get into the whole notion of digital resilience. I wanna I wanna sort of set it up with what I see, and maybe you can comment be prior to the pandemic. A lot of customers that kind of equated disaster recovery with their business continuance or business resilient strategy, and that's changed almost overnight. How have you seen your clients respond to that? What? I sometimes called the forced march to become a digital business. And maybe you could talk about some of the challenges that they faced along the way. >>Absolutely. So, uh, especially during this pandemic, times when you say Dave, customers have been having tough times managing their business. So happiest minds. Being a digital Brazilian company, we were able to react much faster in the industry, apart from the other services company. So one of the key things is the organisation's trying to adopt onto the digital technologies. Right there has bean lot off data which has been to manage by these customers on There have been lot off threats and risk, which has been to manage by the CEO Seo's so happiest minds digital resilient technology, right where we bring in the data. Complaints as a service were ableto manage the resilience much ahead off other competitors in the market. We were ableto bring in our business continuity processes from day one, where we were ableto deliver our services without any interruption to the services. What we were delivered to our customers So that is where the digital resilience with business community process enabled was very helpful for us. Toe enable our customers continue their business without any interruptions during pandemics. >>So I mean, some of the challenges that customers tell me they obviously they had to figure out how to get laptops to remote workers and that that whole remote work from home pivot figure out how to secure the end points. And, you know, those were kind of looking back there kind of table stakes, But it sounds like you've got a digital business. Means a data business putting data at the core, I like to say, but so I wonder if you could talk a little bit more about maybe the philosophy you have toward digital resilience in the specific approach you take with clients? >>Absolutely. They seen any organization data becomes. The key on that, for the first step is to identify the critical data. Right. So we this is a six step process. What we following happiest minds. First of all, we take stock off the current state, though the customers think that they have a clear visibility off their data. How are we do more often assessment from an external point off view on see how critical their data is, then we help the customers to strategies that right. The most important thing is to identify the most important critical herself. Data being the most critical assert for any organization. Identification off the data's key for the customers. Then we help in building a viable operating model to ensure these identified critical assets are secure on monitor dearly so that they are consumed well as well as protected from external threats. Then, as 1/4 step, we try to bring in awareness, toe the people we train them >>at >>all levels in the organization. That is a P for people to understand the importance off the digital ourselves and then as 1/5 step, we work as a back up plan in terms of bringing in a very comprehensive and a holistic testing approach on people process as well as in technology. We'll see how the organization can withstand during a crisis time, and finally we do a continuous governance off this data, which is a key right. It is not just a one step process. We set up the environment, we do the initial analysis and set up the strategy on continuously govern this data to ensure that they are not only know managed will secure as well as they also have to meet the compliance requirements off the organization's right. That is where we help organizations toe secure on Meet the regulations off the organizations. As for the privacy laws, so this is a constant process. It's not on one time effort. We do a constant process because every organization goes towards their digital journey on. They have to face all these as part off the evolving environment on digital journey. And that's where they should be kept ready in terms off. No recovering, rebounding on moving forward if things goes wrong. >>So let's stick on that for a minute, and then I wanna bring yourself into the conversation. So you mentioned compliance and governance when when your digital business, you're, as you say, you're a data business, so that brings up issues. Data sovereignty. Uh, there's governance, this compliance. There's things like right to be forgotten. There's data privacy, so many things. These were often kind of afterthoughts for businesses that bolted on, if you will. I know a lot of executives are very much concerned that these air built in on, and it's not a one shot deal. So do you have solutions around compliance and governance? Can you deliver that as a service? Maybe you could talk about some of the specifics there, >>so some of way have offered multiple services. Tow our customers on digital against. On one of the key service is the data complaints. As a service here we help organizations toe map the key data against the data compliance requirements. Some of the features includes in terms off the continuous discovery off data right, because organizations keep adding on data when they move more digital on helping the helping and understanding the actual data in terms off the residents of data, it could be a heterogeneous data soldiers. It could be on data basis, or it could be even on the data legs. Or it could be a no even on compromise all the cloud environment. So identifying the data across the various no heterogeneous environment is very key. Feature off our solution. Once we identify classify this sensitive data, the data privacy regulations on the traveling laws have to be map based on the business rules So we define those rules on help map those data so that organizations know how critical their digital assets are. Then we work on a continuous marching off data for anomalies because that's one of the key teachers off the solution, which needs to be implemented on the day to day operational basis. So we're helping monitoring those anomalies off data for data quality management on an ongoing basis. On finally, we also bringing the automated data governance where we can manage the sensory data policies on their later relationships in terms off mapping on manage their business roots on we drive reputations toe Also suggest appropriate actions to the customers. Take on those specific data sets. >>Great. Thank you, Yousef. Thanks for being patient. I want to bring in Iota ho thio discussion and understand where your customers and happiest minds can leverage your data automation capability that you and I have talked about in the past. I'm gonna be great if you had an example is well, but maybe you could pick it up from there, >>John. I mean, at a high level, assertions are clearly articulated. Really? Um, Hyoty, who delivers business agility. So that's by, um accelerating the time to operationalize data, automating, putting in place controls and actually putting helping put in place digital resilience. I mean way if we step back a little bit in time, um, traditional resilience in relation to data often met manually, making multiple copies of the same data. So you have a d b A. They would copy the data to various different places, and then business users would access it in those functional style owes. And of course, what happened was you ended up with lots of different copies off the same data around the enterprise. Very inefficient. ONDA course ultimately, uh, increases your risk profile. Your risk of a data breach. Um, it's very hard to know where everything is. And I realized that expression. They used David the idea of the forced march to digital. So with enterprises that are going on this forced march, what they're finding is they don't have a single version of the truth, and almost nobody has an accurate view of where their critical data is. Then you have containers bond with containers that enables a big leap forward so you could break applications down into micro services. Updates are available via a p I s on. So you don't have the same need thio to build and to manage multiple copies of the data. So you have an opportunity to just have a single version of the truth. Then your challenge is, how do you deal with these large legacy data states that the service has been referring Thio, where you you have toe consolidate and that's really where I attack comes in. Um, we massively accelerate that process of putting in a single version of the truth into place. So by automatically discovering the data, discovering what's dubica? What's redundant? Uh, that means you can consolidate it down to a single trusted version much more quickly. We've seen many customers have tried to do this manually, and it's literally taken years using manual methods to cover even a small percentage of their I T estates. With our tire, you could do it really very quickly on you can have tangible results within weeks and months on Ben, you can apply controls to the data based on context. So who's the user? What's the content? What's the use case? Things like data quality validations or access permissions on. Then, once you've done there. Your applications and your enterprise are much more secure, much more resilient. As a result, you've got to do these things whilst retaining agility, though. So coming full circle. This is where the partnership with happiest minds really comes in as well. You've got to be agile. You've gotta have controls. Um, on you've got a drug toward the business outcomes. Uh, and it's doing those three things together that really deliver for the customer. >>Thank you. Use f. I mean you and I. In previous episodes, we've looked in detail at the business case. You were just talking about the manual labor involved. We know that you can't scale, but also there's that compression of time. Thio get to the next step in terms of ultimately getting to the outcome. And we talked to a number of customers in the Cube, and the conclusion is, it's really consistent that if you could accelerate the time to value, that's the key driver reducing complexity, automating and getting to insights faster. That's where you see telephone numbers in terms of business impact. So my question is, where should customers start? I mean, how can they take advantage of some of these opportunities that we've discussed today. >>Well, we've tried to make that easy for customers. So with our Tahoe and happiest minds, you can very quickly do what we call a data health check. Um, this is a is a 2 to 3 week process, uh, to really quickly start to understand on deliver value from your data. Um, so, iota, who deploys into the customer environment? Data doesn't go anywhere. Um, we would look at a few data sources on a sample of data. Onda. We can very rapidly demonstrate how they discovery those catalog e on understanding Jupiter data and redundant data can be done. Um, using machine learning, um, on how those problems can be solved. Um, And so what we tend to find is that we can very quickly, as I say in the matter of a few weeks, show a customer how they could get toe, um, or Brazilian outcome on then how they can scale that up, take it into production on, then really understand their data state? Better on build. Um, Brasiliense into the enterprise. >>Excellent. There you have it. We'll leave it right there. Guys, great conversation. Thanks so much for coming on the program. Best of luck to you and the partnership Be well, >>Thank you, David Suresh. Thank you. Thank >>you for watching everybody, This is Dave Volonte for the Cuban are ongoing Siris on data automation without >>Tahoe, digital resilience, automated compliance, privacy and security for your multi cloud. Congratulations. You're on the journey. You have successfully transformed your organization by moving to a cloud based platform to ensure business continuity in these challenging times. But as you scale your digital activities, there is an inevitable influx of users that outpaces traditional methods of cybersecurity, exposing your data toe underlying threats on making your company susceptible toe ever greater risk to become digitally resilient. Have you applied controls your data continuously throughout the data lifecycle? What are you doing to keep your customer on supply data private and secure? I owe Tahoe's automated sensitive data. Discovery is pre programmed with over 300 existing policies that meet government mandated risk and compliance standards. Thes automate the process of applying policies and controls to your data. Our algorithm driven recommendation engine alerts you to risk exposure at the data level and suggests the appropriate next steps to remain compliant on ensure sensitive data is secure. Unsure about where your organization stands in terms of digital resilience. Sign up for our minimal cost commitment. Free data health check. Let us run our sensitive data discovery on key unmapped data silos and sources to give you a clear understanding of what's in your environment. Book time within Iot. Tahoe Engineer. Now. >>Okay, now we're >>gonna go into the demo. We want to get a better understanding of how you can leverage open shift. And I owe Tahoe to facilitate faster application deployment. Let me pass the mic to Sabetta. Take it away. >>Uh, thanks, Dave. Happy to be here again, Guys, uh, they've mentioned names to be the Davis. I'm the enterprise account executive here. Toyota ho eso Today we just wanted to give you guys a general overview of how we're using open shift. Yeah. Hey, I'm Noah Iota host data operations engineer, working with open ship. And I've been learning the Internets of open shift for, like, the past few months, and I'm here to share. What a plan. Okay, so So before we begin, I'm sure everybody wants to know. Noel, what are the benefits of using open shift. Well, there's five that I can think of a faster time, the operation simplicity, automation control and digital resilience. Okay, so that that's really interesting, because there's an exact same benefits that we had a Tahoe delivered to our customers. But let's start with faster time the operation by running iota. Who on open shift? Is it faster than, let's say, using kubernetes and other platforms >>are >>objective iota. Who is to be accessible across multiple cloud platforms, right? And so by hosting our application and containers were able to achieve this. So to answer your question, it's faster to create and use your application images using container tools like kubernetes with open shift as compared to, like kubernetes with docker cry over container D. Okay, so we got a bit technical there. Can you explain that in a bit more detail? Yeah, there's a bit of vocabulary involved, uh, so basically, containers are used in developing things like databases, Web servers or applications such as I have top. What's great about containers is that they split the workload so developers can select the libraries without breaking anything. And since Hammond's can update the host without interrupting the programmers. Uh, now, open shift works hand in hand with kubernetes to provide a way to build those containers for applications. Okay, got It s basically containers make life easier for developers and system happens. How does open shift differ from other platforms? Well, this kind of leads into the second benefit I want to talk about, which is simplicity. Basically, there's a lot of steps involved with when using kubernetes with docker. But open shift simplifies this with their source to image process that takes the source code and turns it into a container image. But that's not all. Open shift has a lot of automation and features that simplify working with containers, an important one being its Web console. Here. I've set up a light version of open ship called Code Ready Containers, and I was able to set up her application right from the Web console. And I was able to set up this entire thing in Windows, Mac and Lennox. So its environment agnostic in that sense. Okay, so I think I've seen the top left that this is a developers view. What would a systems admin view look like? It's a good question. So here's the administrator view and this kind of ties into the benefit of control. Um, this view gives insights into each one of the applications and containers that are running, and you could make changes without affecting deployment. Andi can also, within this view, set up each layer of security, and there's multiple that you can prop up. But I haven't fully messed around with it because with my luck, I'd probably locked myself out. So that seems pretty secure. Is there a single point security such as you use a log in? Or are there multiple layers of security? Yeah, there are multiple layers of security. There's your user login security groups and general role based access controls. Um, but there's also a ton of layers of security surrounding like the containers themselves. But for the sake of time, I won't get too far into it. Okay, eso you mentioned simplicity In time. The operation is being two of the benefits. You also briefly mention automation. And as you know, automation is the backbone of our platform here, Toyota Ho. So that's certainly grabbed my attention. Can you go a bit more in depth in terms of automation? Open shift provides extensive automation that speeds up that time the operation. Right. So the latest versions of open should come with a built in cryo container engine, which basically means that you get to skip that container engine insulation step and you don't have to, like, log into each individual container host and configure networking, configure registry servers, storage, etcetera. So I'd say, uh, it automates the more boring kind of tedious process is Okay, so I see the iota ho template there. What does it allow me to do? Um, in terms of automation in application development. So we've created an open shift template which contains our application. This allows developers thio instantly, like set up our product within that template. So, Noah Last question. Speaking of vocabulary, you mentioned earlier digital resilience of the term we're hearing, especially in the banking and finance world. Um, it seems from what you described, industries like banking and finance would be more resilient using open shift, Correct. Yeah, In terms of digital resilience, open shift will give you better control over the consumption of resource is each container is using. In addition, the benefit of containers is that, like I mentioned earlier since Hammond's can troubleshoot servers about bringing down the application and if the application does go down is easy to bring it back up using templates and, like the other automation features that open ship provides. Okay, so thanks so much. Know us? So any final thoughts you want to share? Yeah. I just want to give a quick recap with, like, the five benefits that you gained by using open shift. Uh, the five are timeto operation automation, control, security and simplicity. You could deploy applications faster. You could simplify the workload you could automate. A lot of the otherwise tedious processes can maintain full control over your workflow. And you could assert digital resilience within your environment. Guys, >>Thanks for that. Appreciate the demo. Um, I wonder you guys have been talking about the combination of a Iot Tahoe and red hat. Can you tie that in subito Digital resilience >>Specifically? Yeah, sure, Dave eso when we speak to the benefits of security controls in terms of digital resilience at Io Tahoe, we automated detection and apply controls at the data level, so this would provide for more enhanced security. >>Okay, But so if you were trying to do all these things manually. I mean, what what does that do? How much time can I compress? What's the time to value? >>So with our latest versions, Biota we're taking advantage of faster deployment time associated with container ization and kubernetes. So this kind of speeds up the time it takes for customers. Start using our software as they be ableto quickly spin up io towel on their own on premise environment are otherwise in their own cloud environment, like including aws. Assure or call GP on IBM Cloud a quick start templates allow flexibility deploy into multi cloud environments all just using, like, a few clicks. Okay, so so now just quickly add So what we've done iota, Who here is We've really moved our customers away from the whole idea of needing a team of engineers to apply controls to data as compared to other manually driven work flows. Eso with templates, automation, previous policies and data controls. One person can be fully operational within a few hours and achieve results straight out of the box on any cloud. >>Yeah, we've been talking about this theme of abstracting the complexity. That's really what we're seeing is a major trend in in this coming decade. Okay, great. Thanks, Sabina. Noah, How could people get more information or if they have any follow up questions? Where should they go? >>Yeah, sure. They've. I mean, if you guys are interested in learning more, you know, reach out to us at info at iata ho dot com to speak with one of our sales engineers. I mean, we love to hear from you, so book a meeting as soon as you can. All >>right. Thanks, guys. Keep it right there from or cube content with.

>>from around the >>globe. It's the Cube with digital coverage of AWS reinvent 2020 Special coverage sponsored by AWS Worldwide Public Sector >>Hi and welcome to the Q Virtual and our coverage of AWS reinvent 2020 with special coverage of the public sector. I'm your host, Rebecca >>Knight. >>Today we have two guests for our segment. We have Kevin McCallum Jr. He is the chief technology officer at Maximus. Thanks for joining us, Kevin, and we have way. And we have Steve Zimmerman, who is the vice president of consulting services at Insight. Thank you so much for coming on the show. Steve. >>Thank you for having us appreciate it. >>So I want to start by asking. You both have to tell us a little bit more about your company's. Kevin. Let's start with you. Tell us a little bit more about Maximus. >>Yes, Thanks for having me. Maximus is a 40 year old company. We partner with state, federal and local governments to provide communities with critical health and human service programs. We leverage extensive experience to develop high quality services and solutions that are cost effective and tailored to their unique needs. One of the things that we do is offer government's ability to programs rapidly and scalable so that we can focus on the automation and their operations. We do services from Medicare to Medicaid, Welford work, and we have comprehensive solutions. Help the government's run effectively and efficiently. >>Great, Steve, tell us a little bit about insight. >>Yeah, sure. Um, Insight is a Fortune 500 company, you know, in 2020 will roughly do you know, probably a plus billion dollars in revenue. Global company. You know, we have thousands of treaty GIC relationships, but I'd say we have probably a couple 100 partners. We focus on one of those key partners to us is a W s. Right. As we go to market, Azzawi start, you know, working with our customers around transformation, of which we're gonna talk a little bit about that today with Kevin as it relates, Thio incite public sector. It's >>a pretty sizable >>part of our business. You know, we'll do about $1.5 billion in revenue. We have 200 plus contract vehicles, will work out there over 500 plus teammates, and we're seeing that business grow quarter over quarter, 20% growth. So It's a big investment for us and really looking forward to hearing Kevin talk about Maximus, uh, to the team, because obviously it's a big lever for us for inside public sector to get the word out there about the great transformation work. What you do with our customers. >>That's a great segue. So let's go back to you, Kevin, and talk a little bit about Maximus. Cloud transformation. Why did you hire insight for help you with this? >>Yeah, A Z We started our journey. One of the things we realized is as we were moving to the cloud is the experience. We needed a trusted partner and we ran an RFP process looking for partners out there that have done it that have done major data center programs. You're moving large companies, you know, We're moving about 6000 workloads 160 plus applications. So it was not a light or easy project and insight fit that. Aziz, We went through the interview process. It became very clear that they have done this for Fortune 500 companies in the past and their experience is beneficial to helping us drive to the future and the other factors is we wanted to make sure that once we were done with the project, we had the experience internally that they helped us with Thio drive forward. >>So talking about the importance of a trusted partner, which is such a key component of digital transformation cloud journeys tell us a little bit about the the strategy tied to the data center transformation and why you chose AWS. >>Sure. So, as we started doing our research, we did analysis across all of the cloud providers who were out there. AWS is clear leader in the marketplace. Their technology is better aligned with what Maximus has as the underlying technologies were, ah, majority of Lennox Base. We also have windows. We have Oracle, which, with the AWS depth on breath of our offerings, tied better to what we had. The other thing we were looking to do is get rid of our monolithic off the shelf products and use mawr of the cloud based products that are out there. Amazon has a very deep, uh, native technology that allows you to replace your old services where you had to bolt on or purchase another product to something that is integrated and streamlined, you know, down Thio, how do you monitor your systems? How do you do logs things like that. And, you know, as we looked at the time frame, we had to deliver this. They had to be able to grow with us. So as we were building out, new infrastructure were able to build where previously internally. With data centers, you have to buy infrastructure. You wait for it to arrive, you install it. Amazon has it at the click of a ah button. So we're able Thio basically have environment stood up in a day rather than having to wait weeks for it. So and the last thing was up time. So you know Amazon. They're five nines plus in up time and most of our contracts or three nines or better requirements. We had to find a bender that had multiple availability zones and regions that allowed us to be flexible in how we deployed. >>So talking about the convenience and the ability to streamline, and also the need for flexibility in the covert era. Of course, the word hybrid work environments has taken on a new meaning. But I want to ask you about how you see the hybrid era in the long term affecting Maximus. >>Yeah. Since Maximus is a government contractor, we will always be in a hybrid, uh, set up. So some of our contracts are very restrictive, especially when you get into our S d. O. D. And some of those agencies you have a fed ramp requirement is right. Well, with some of the federal agencies. So some of those components about to stay internally So where we can force, uh, you know, moving to the cloud because of the flexibility we have to deploy, that is the right will go. Um, co vid has introduced a new complexity. When it started back in March, you know, Maximus had 30,000 or so employees, and we instantly were thrown into You gotta make those employees get those employees to work from home. So we used Amazon's workspace Thio push our employees to work from home, where, you know, some of the employees and some of our contracts are customer owned equipment. So we couldn't actually take that equipment home. So we had to move to a B y o d model on Amazon workspaces in order to get the users to work from home and the complexity that, with what Amazon has to offer, allowed us to quickly move over 25,000 employees on the Amazon workspaces and work from home and then keeping the data center migration moving in the middle of it has also been, ah, challenge. So we will, in our federal space, still have internal data centers. Integration points that Amazon offers with their inter connects is key toe. How we make it a seamless process because we may have a business unit has stuff sitting in the data center and at Amazon, and they have to look at the seamless package. >>Steve, I want to bring you in here a little bit into this conversation. Cloud transformation, digital transformation. These are These are difficult and huge undertaking in the best of times. How does this pandemic this health crisis emergency. How has that affected the way you help your clients the way you work with your clients? Collaborate, communicate, talk a little bit about the effect of Kobe on this on the >>eso I would. I'll answer the question in a couple different ways, so I would agree with Kevin because, you know, forget about what we do with our customers. You know, we had a pivot really quick to write all remote workforce. You know, I think about my team, you know, 1000 plus teammates. Everyone's 80% travel all gone like, um, and I write eso everybody working remote. Everybody work from their homes. And but the challenging part was working with our customers. And, you know, I look at you know, I looked at with Kevin. You know, I've never met Kevin in person, you know, frankly, and there's teammates have come on to our to the project and execute executing this program remotely, so it makes it that much harder working with the customer. Um, you know, doing more video chats. You know, our methodology is built to be all remote. We have a proprietary tool called snap start that allows to bail scan environments. All that things done. Remote migrations could be done remote. The hard part is when you have to go on site because there's this stuff you have to go on site for around physical inventory to look at the equipment, but it just makes it that much harder. You know, I think he taking advantage of these video tools like we're doing today. You know, I can't tell me how many Skype You know how many calls have been on with Kevin like this and with his peers and with his leadership. But communication is really important program like this because, you know, in a program like this, there will be problems, right? And there will be challenges and, you know, getting on a call on being I will look at Kevin face to face and see what his reaction is really key. But you gotta work that much harder. You gotta work that much harder now in the pandemic. You know, I have other projects right now leaving with this other projects that, frankly, we have sold all remote and we're doing it all remote. And what I'm seeing with the bidam IQ is an acceleration of digital transformation. So, other similar projects like we're doing with Kevin. We're doing for other large fortune 500 companies because it's an acceleration of Hey, look, we gotta be old digital now, so it'll be interesting to see you know how the pandemic effects is long term because it is definitely accelerating out their digital transformation if you haven't done it, you're in trouble because it's gonna eat your company alive. >>Mhm. So, Kevin, he's talking. He talked a little bit about she talked a little bit about the importance of communication, particularly when work so many people are working from home. Um, talk a little bit of about other best practices that have emerged. Things that you have noticed. Things that you advice you would have to your peers. I mean, a Z we heard from Steve. If you're not there yet, you're in trouble. But for the for the people, for the executives out there who are watching this, What advice would you have for them? >>Yeah, I think that you know this this is brought to light. You know, there was always a view that you had to be in an office on a white board and actual actually functioning in that fashion. So, you know, before the pandemic, I was traveling three weeks a month on now, not traveling. I feel that I actually get more work done. I actually feel that I'm closer to the team just because we've introduced a lot of different digital channels. So now we have slack we have teams we do zoom. I require everybody to be on a on video, whereas previously before the pandemic you'd rarely have anybody on video. Um, and you've seen Ah, transformation is people pick up the phone a lot quicker than they did in the past. So it is, actually, I believe, brought the team closer together because now you know, everybody's on. Um, the downside of it is everybody's on all the time. So you've also had to have people step away from work because generally when they take PTO, they leave the office that go somewhere with their family. Now it's your kind of at home. There's not much to dio. You kinda have to force them to take the time off. One of the major factors that has has been interesting is we're doing this transformation in the middle of co vid with moving. All of our resource is the home. So we've we've had to take pauses, toe focus on getting everybody to work from home. Okay, now their work from home back to the project. And, you know, it's kind of a change the timeline a little bit, but in the end, you know we have some hard deadlines to meet. So it's been an interesting transition. You >>know, Kevin, um, I wanna agree with you two points is, uh you know, I think we're also getting not only your time, but also senior leadership, that I think, frankly, we never would have gotten, you know, I'm talking, you know, your peers and your leadership, Like I would fly for those meetings. I think about all the time that I've saved. But then again, it never ends, right? Never. It begins and never ends. And, you know, one of the things I'm concerned about is you know, the long term burnout factor for these folks because and depending on what state you're in, it never ends. You don't have anywhere to go, right. And you know, I think about teammates. I think you know, Kevin, I have talked about this related to our project like burdens and really thing right now for sure. 889 months into this thing. It's a real thing. Is people they have to focus on. Is is work sometimes. So it's a it's a concern for all of us is a project team is we start looking at the executing. This continue to execute this program for the next year. >>And it really highlights the importance of visionary leadership and a leader who cares who is empathetic, who is checking in with his or her team and making sure that the colleagues feel appreciated and cared for. I want you both to just give us look into your crystal ball is a little bit and talk about the where you see things 12, 24 months from now. Hopefully there will be a vaccine and we will return to somewhat of a of a new normal. Um, talk a little bit about where you see the Maximus transformation in two years. Absolutely. Yeah. Start with you. >>So s so you know, our cloud migration. We have some hard deadlines through next year, so we have a focus with insight to get that completed by September next year because our data center contracts are up and we've got to get out. You know, one of the the advantages of where we're headed is to move into more of a Dev ops model where you know you're able thio enable groups that have previously not been able to do work just do thio. The infrastructure was set up your now, enabling them to do deployments, get into production and have full stack ownership. That's really where our focus is. Is enablement of the teams that couldn't do the work previously because now you're in a different type of environment. Um, the other thing is being able thio be more agile. So as we move forward into the cloud journey, we as a company are consort contracts quicker. We are part of the, you know, contract tracing on unemployment insurance. We've done a lot of contracts with states that you know previously most of our contracts or anywhere from a 62 120 day startup. These contracts and contact tracing and covert projects. We've had to start them up in three days. That's having 500 employees online on workspaces on Genesis Cloud and fully functional, and it has been a challenge. But it also has introduced a a better way to do business because now we can we can move quicker for our customers and we can get contracts where they come and say, Hey, I need something in the next couple days. If you look further down the road. You know, it's taking the advantage of what Amazon has to offer, you know, moving from arm or monolithic programs like, you know, we sit on Oracle on Lenox today. You know, we could move into Aurora, which opens up the doors and floodgates, because then you manage, er a little differently. You manage your data a little differently. That's really where I think the the market's going and where we can actually transform our business. Even better, Thio, where we could be more flexible. We can start up quicker and, you know, be doom or things for our customers. >>The final word from you >>e I think it's gonna be a hybrid world, right? It's at least in the short term. And you know, we believe it's all about the workload and getting those workloads or applications, you know, in in the right spot, whether it be public or private and helping our customers with that journey, you know, just a pile on with Kevin talked about around Dev ops. Once you get a guy to get once you get all the stuff over there, you still got to manage it, Whether it's in a W. S or, you know, on Prem. You still gotta have a process to do that. So we see a lot of opportunity around the Modern I t operations and helping with that way. We want to continue to be a trusted partner. Thio Maximus. It's been a great relationship, but I want to thank Kevin and his his leadership team for trusting in us. And we look forward, Um, or more success with him in the future. >>Excellent. Thank you both so much. Kevin and Steve, thanks so much for coming on the Cube. >>Absolutely. Thank you. >>I'm your host, Rebecca. Night. Stay tuned. For more of the Cube virtual coverage of AWS reinvent with special coverage of the public sector.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud, Native Computing Foundation and Ecosystem Partners. Hello, everyone. And welcome back to the cubes Ongoing coverage of Cuba con North America. Joe Fernandez is here. He's with Stephanie, Cheras and Joe's, the V, P and GM for core cloud platforms. That red hat and Stephanie is this s VP and GM of the Red Hat Enterprise. Lennox bu. Two great friends of the Cube. Awesome seeing you guys. How you doing? >>It's great to be here, Dave. Yeah, thanks >>for the opportunity. >>Hey, so we all talked, you know, recently, uh, answerable fest Seems like a while ago, but But we talked about what's new? Red hat really coming at it from an automation perspective. But I wonder if we could take a view from open shift and what's new from the standpoint of you really focus on helping customers, you know, change their operations and operationalize. And Stephanie, Maybe you could start, and then, you know, Joe, you could bring in some added color. >>No, that's great. And I think you know one of the things we try and do it. Red hat clearly building off of open source. We have been focused on this open hybrid cloud strategy for, you know, really years. Now the beauty of it is that hybrid cloud and open hybrid cloud continues to evolve right with bringing in things like speed and stability and scale and now adding in other footprints, like manage services as well as edge and pulling that all together across the whole red hat portfolio from the platforms, right? Certainly with Lennox and roll into open shift in the platform with open shift and then adding automation, which certainly you need for scale. But it's ah, it's continues to evolve as the as the definition of open hybrid cloud evolves. >>Great. So thank you, Stephanie jokes. You guys got hard news here that you could maybe talk about 46? >>Yeah. Eso eso open shift is our enterprise kubernetes platform. With this announcement, we announced the release of open ship 4.6 Eso eso We're doing releases every quarter tracking the upstream kubernetes release cycle. So this brings communities 1.19, which is, um but itself brings a number of new innovations, some specific things to call out. We have this new automated installer for open shift on bare metal, and that's definitely a trend that we're seeing is more customers not only looking at containers but looking at running containers directly on bare metal environments. Open shift provides an abstraction, you know, which combines Cuban. And he's, uh, on top of Lennox with RL. I really across all environments, from bare metal to virtualization platforms to the various public clouds and out to the edge. But we're seeing a lot of interest in bare metal. This is basically increasing the really three automation to install seamlessly and manage upgrades in those environments. We're also seeing a number of other enhancements open shifts service mesh, which is our SDO based solution for managing, uh, the interactions between micro services being able to manage traffic against those services. Being able to do tracing. We have a new release of that on open shift Ford out six on then, um, some work specific to the public cloud that we started extending into the government clouds. So we already supported AWS and Azure. With this release, we added support for the A W s government cloud as well. Azaz Acela's Microsoft Azure government on dso again This is really important to like our public sector customers who are looking to move to the public cloud leveraging open shift as an abstraction but wanted thio support it on the specialized clouds that they need to use with azure gonna meet us Cup. >>So, joke, we stay there for a minute. So so bare metal talking performance there because, you know, you know what? You really want to run fast, right? So that's the attractiveness there. And then the point about SDO in the open, open shift service measure that makes things simpler. Maybe talk a little bit about sort of business impact and what customers should expect to get out of >>these two things. So So let me take them one at a time, right? So so running on bare metal certainly performances a consideration. You know, I think a lot of fixed today are still running containers, and Cuban is on top of some form of virtualization. Either a platform like this fear or open stack, or maybe VMS in the in one of the public clouds. But, you know containers don't depend on a virtualization layer. Containers only depend on Lennox and Lennox runs great on bare metal. So as we see customers moving more towards performance and Leighton see sensitive workloads, they want to get that Barry mental performance on running open shift on bare metal and their containerized applications on that, uh, platform certainly gives them that advantage. Others just want to reduce the cost right. They want to reduce their VM sprawl, the infrastructure and operational cost of managing avert layer beneath their careers clusters. And that's another benefit. So we see a lot of uptake in open shift on bare metal on the service match side. This is really about You know how we see applications evolving, right? Uh, customers are moving more towards these distributed architectures, taking, you know, formally monolithic or enter applications and splitting them out into ah, lots of different services. The challenge there becomes. Then how do you manage all those connections? Right, Because something that was a single stack is now comprised of tens or hundreds of services on DSO. You wanna be able to manage traffic to those services, so if the service goes down, you can redirect that those requests thio to an alternative or fail over service. Also tracing. If you're looking at performance issues, you need to know where in your architecture, er you're having those degradations and so forth. And, you know, those are some of the challenges that people can sort of overcome or get help with by using service mash, which is powered by SDO. >>And then I'm sorry, Stephanie ever get to in a minute. But which is 11 follow up on that Joe is so the rial differentiation between what you bring in what I can just if I'm in a mono cloud, for instance is you're gonna you're gonna bring this across clouds. I'm gonna You're gonna bring it on, Prem And we're gonna talk about the edge in in a minute. Is that right? From a differentiation standpoint, >>Yeah, that That's one of the key >>differentiations. You know, Read has been talking about the hybrid cloud for a long time. We've we've been articulating are open hybrid cloud strategy, Andi, >>even if that's >>not a strategy that you may be thinking about, it is ultimately where folks end up right, because all of our enterprise customers still have applications running in the data center. But they're also all starting to move applications out to the public cloud. As they expand their usage of public cloud, you start seeing them adopted multi cloud strategies because they don't want to put all their eggs in one basket. And then for certain classes of applications, they need to move those applications closer to the data. And and so you start to see EJ becoming part of that hybrid cloud picture on DSO. What we do is basically provide a consistency across all those environments, right? We want run great on Amazon, but also great on Azure on Google on bare metal in the data center during medal out at the edge on top of your favorite virtualization platform. And yeah, that that consistency to take a set of applications and run them the same way across all those environments. That is just one of the key benefits of going with red hat as your provider for open hybrid cloud solutions. >>All right, thank you. Stephanie would come back to you here, so I mean, we talk about rail a lot because your business unit that you manage, but we're starting to see red hats edge strategy unfolded. Kind of real is really the linchpin I wanna You could talk about how you're thinking about the edge and and particularly interested in how you're handling scale and why you feel like you're in a good position toe handle that massive scale on the requirements of the edge and versus hey, we need a new OS for the edge. >>Yeah, I think. And Joe did a great job of said and up it does come back to our view around this open hybrid cloud story has always been about consistency. It's about that language that you speak, no matter where you want to run your applications in between rela on on my side and Joe with open shift and and of course, you know we run the same Lennox underneath. So real core os is part of open shift that consistently see leads to a lot of flexibility, whether it's through a broad ecosystem or it's across footprints. And so now is we have been talking with customers about how they want to move their applications closer to data, you know, further out and away from their data center. So some of it is about distributing your data center, getting that compute closer to the data or closer to your customers. It drives, drives some different requirements right around. How you do updates, how you do over the air updates. And so we have been working in typical red hat fashion, right? We've been looking at what's being done in the upstream. So in the fedora upstream community, there is a lot of working that has been done in what's called the I. O. T Special Interest group. They have been really investigating what the requirements are for this use case and edge. So now we're really pleased in, um, in our most recent release of really aid relate 00.3. We have put in some key capabilities that we're seeing being driven by these edge use cases. So things like How do you do quick image generation? And that's important because, as you distribute, want that consistency created tailored image, be able to deploy that in a consistent way, allow that to address scale, meet security requirements that you may have also right updates become very important when you start to spread this out. So we put in things in order to allow remote device mirroring so that you can put code into production and then you can schedule it on those remote devices toe happen with the minimal disruption. Things like things like we all know now, right with all this virtual stuff, we often run into things like not ideal bandwidth and sometimes intermittent connectivity with all of those devices out there. So we put in, um, capabilities around, being able to use something called rpm Austria, Um, in order to be able to deliver efficient over the air updates. And then, of course, you got to do intelligent rollbacks for per chance that something goes wrong. How do you come back to a previous state? So it's all about being able to deploy at scale in a distributed way, be ready for that use case and have some predictability and consistency. And again, that's what we build our platforms for. It's all about predictability and consistency, and that gives you flexibility to add your innovation on top. >>I'm glad you mentioned intelligent rollbacks I learned a long time ago. You always ask the question. What happens when something goes wrong? You learn a lot from the answer to that, but You know, we talk a lot about cloud native. Sounds like you're adapting well to become edge native. >>Yeah. I mean, I mean, we're finding whether it's inthe e verticals, right in the very specific use cases or whether it's in sort of an enterprise edge use case. Having consistency brings a ton of flexibility. It was funny, one of our talking with a customer not too long ago. And they said, you know, agility is the new version of efficiency. So it's that having that sort of language be spoken everywhere from your core data center all the way out to the edge that allows you a lot of flexibility going forward. >>So what if you could talk? I mentioned just mentioned Cloud Native. I mean, I think people sometimes just underestimate the effort. It takes tow, make all this stuff run in all the different clouds the engineering efforts required. And I'm wondering what kind of engineering you do with if any with the cloud providers and and, of course, the balance of the ecosystem. But But maybe you could describe that a little bit. >>Yeah, so? So Red Hat works closely with all the major cloud providers you know, whether that's Amazon, Azure, Google or IBM Cloud. Obviously, Andi, we're you know, we're very keen on sort of making sure that we're providing the best environment to run enterprise applications across all those environments, whether you're running it directly just with Lennox on Ralph or whether you're running it in a containerized environment with Open Chef, which which includes route eso eso, our partnership includes work we do upstream, for example. You know, Red Hat help. Google launched the Cuban community, and I've been, you know, with Google. You know, we've been the top two contributors driving that product that project since inception, um, but then also extends into sort of our hosted services. So we run a jointly developed and jointly managed service called the Azure Red Hat Open Shift Service. Together with Microsoft were our joint customers can get access to open shift in an azure environment as a native azure service, meaning it's, you know, it's fully integrated, just like any other. As your service you can tied into as you're building and so forth. It's sold by by Azure Microsoft's sales reps. Um, but you know, we get the benefit of working together with our Microsoft counterparts and developing that service in managing that service and then in supporting our joint customers. We over the summer announced sort of a similar partnership with Amazon and we'll be launching are already doing pilots on the Amazon Red Hat Open ship service, which is which is, you know, the same concept now applied to the AWS cloud. So that will be coming out g a later this year, right? But again, whether it's working upstream or whether it's, you know, partnering on managed services. I know Stephanie team also do a lot of work with Microsoft, for example, on sequel server on Lenox dot net on Lenox. Whoever thought be running that applications on Linux. But that's, you know, a couple of years old now, a few years old, So eso again. It's been a great partnership, not just with Microsoft, but with all the cloud providers. >>So I think you just shared a little little He showed a little leg there, Joe, what's what's coming g A. Later this year. I want to circle back to >>that. Yeah, eso we way announced a preview earlier this year of of the Amazon Red Hat Open ships service. It's not generally available yet. We're you know, we're taking customers. We want toe, sort of be early access, get access to pilots and then that'll be generally available later this year. Although Red Hat does manage our own service Open ship dedicated that's available on AWS today. But that's a service that's, you know, solely, uh, operated by Red Hat. This new service will be jointly operated by Red Hat and Amazon together Idea. That would be sort of a service that we are delivering together as partners >>as a managed service and and okay, so that's in beta now. I presume if it's gonna be g a little, it's >>like, Yeah, that's yeah, >>that's probably running on bare metal. I would imagine that >>one is running >>on E. C. Two. That's running an A W C C T V exactly, and >>run again. You know, all of our all of >>our I mean, we you know, that open shift does offer bare metal cloud, and we do you know, we do have customers who can take the open shift software and deploy it there right now are managed. Offering is running on top of the C two and on top of Azure VM. But again, this is this is appealing to customers who, you know, like what we bring in terms of an enterprise kubernetes platform, but don't wanna, you know, operated themselves, right? So it's a fully managed service. You just come and build and deploy your APS, and then we manage all of the infrastructure and all the underlying platform for you >>that's going to explode. My prediction. Um, let's take an example of heart example of security. And I'm interested in how you guys ensure a consistent, you know, security experience across all these locations on Prem Cloud. Multiple clouds, the edge. Maybe you could talk about that. And Stephanie, I'm sure you have a perspective on this is Well, from the standpoint of of Ralph. So who wants to start? >>Yeah, Maybe I could start from the bottom and then I'll pass it over to Joe to talk a bit. I think one of these aspects about security it's clearly top of mind of all customers. Um, it does start with the very bottom and base selection in your OS. We continue to drive SC Lennox capabilities into rural to provide that foundational layer. And then as we run real core OS and open shift, we bring over that s C Lennox capability as well. Um, but, you know, there's a whole lot of ways to tackle this we've done. We've done a lot around our policies around, um see ve updates, etcetera around rail to make sure that we are continuing to provide on DCA mitt too. Mitigating all critical and importance, providing better transparency toe how we assess those CVS. So security is certainly top of mind for us. And then as we move forward, right there's also and joke and talk about the security work we do is also capabilities to do that in container ization. But you know, we we work. We work all the way from the base to doing things like these images in these easy to build images, which are tailored so you can make them smaller, less surface area for security. Security is one of those things. That's a lifestyle, right? You gotta look at it from all the way the base in the operating system, with things like sc Lennox toe how you build your images, which now we've added new capabilities. There And then, of course, in containers. There's, um there's a whole focus in the open shift area around container container security, >>Joe. Anything you want to add to that? >>Yeah, sure. I >>mean, I think, you know, obviously, Lennox is the foundation for, you know, for all public clouds. It's it's driving enterprise applications in the data center, part of keeping those applications. Security is keeping them up to date And, you know, through, you know, through real, we provide, you know, securing up to date foundation as a Stephanie mentioned as you move into open shift, you're also been able to take advantage of, uh, Thio to take advantage of essentially mutability. Right? So now the application that you're deploying isn't immutable unit that you build once as a container image, and then you deploy that out all your various environments. When you have to do an update, you don't go and update all those environments. You build a new image that includes those updates, and then you deploy those images out rolling fashion and, as you mentioned that you could go back if there's issues. So the idea, the notion of immutable application deployments has a lot to do with security, and it's enabled by containers. And then, obviously you have cured Panetti's and, you know, and all the rest of our capabilities as part of open Shift managing that for you. We've extended that concept to the entire platform. So Stephanie mentioned, real core West Open shift has always run on real. What we have done in open shift for is we've taken an immutable version of Ralph. So it's the same red hat enterprise Lennox that we've had for years. But now, in this latest version relate, we have a new way to package and deploy it as a relic or OS image, and then that becomes part of the platform. So when customers want toe in addition to keeping their applications up to date, they need to keep their platform up to dates. Need to keep, you know, up with the latest kubernetes patches up with the latest Lennox packages. What we're doing is delivering that as one platform, so when you get updates for open shift, they could include updates for kubernetes. They could include updates for Lennox itself as well as all the integrated services and again, all of this is just you know this is how you keep your applications secure. Is making sure your you know, taking care of that hygiene of, you know, managing your vulnerabilities, keeping everything patched in up to date and ultimately ensuring security for your application and users. >>I know I'm going a little bit over, but I have I have one question that I wanna ask you guys and a broad question about maybe a trends you see in the business. I mean, you look at what we talk a lot about cloud native, and you look at kubernetes and the interest in kubernetes off the charts. It's an area that has a lot of spending momentum. People are putting resource is behind it. But you know, really, to build these sort of modern applications, it's considered state of the art on. Do you see a lot of people trying to really bring that modern approach toe any cloud we've been talking about? EJ. You wanna bring it also on Prem And people generally associate this notion of cloud native with this kind of elite developers, right? But you're bringing it to the masses and there's 20 million plus software developers out there, and most you know, with all due respect that you know they may not be the the the elites of the elite. So how are you seeing this evolve in terms of re Skilling people to be able, handle and take advantage of all this? You know, cool new stuff that's coming out. >>Yeah, I can start, you know, open shift. Our focus from the beginning has been bringing kubernetes to the enterprise. So we think of open shift as the dominant enterprise kubernetes platform enterprises come in all shapes and sizes and and skill sets. As you mentioned, they have unique requirements in terms of how they need toe run stuff in their data center and then also bring that to production, whether it's in the data center across the public clouds eso So part of it is, you know, making sure that the technology meets the requirements and then part of it is working. The people process and and culture thio make them help them understand what it means to sort of take advantage of container ization and cloud native platforms and communities. Of course, this is nothing new to red hat, right? This is what we did 20 years ago when we first brought Lennox to the Enterprise with well, right on. In essence, Carozza is basically distributed. Lennox right Kubernetes builds on Lennox and brings it out to your cluster to your distributed systems on across the hybrid cloud. So So nothing new for Red Hat. But a lot of the same challenges apply to this new cloud native world. >>Awesome. Stephanie, we'll give you the last word, >>all right? And I think just a touch on what Joe talked about it. And Joe and I worked really closely on this, right? The ability to run containers right is someone launches down this because it is magical. What could be done with deploying applications? Using a container technology, we built the capabilities and the tools directly into rural in order to be able to build and deploy, leveraging things like pod man directly into rural. And that's exactly so, folks. Everyone who has a real subscription today can start on their container journey, start to build and deploy that, and then we work to help those skills then be transferrable as you movinto open shift in kubernetes and orchestration. So, you know, we work very closely to make sure that the skills building can be done directly on rail and then transfer into open shift. Because, as Joe said, at the end of the day, it's just a different way to deploy. Lennox, >>You guys are doing some good work. Keep it up. And thanks so much for coming back in. The Cube is great to talk to you today. >>Good to see you, Dave. >>Yes, Thank you. >>All right. Thank you for watching everybody. The cubes coverage of Cuba con en a continues right after this.

from the cube studios in Palo Alto in Boston connecting with thought leaders all around the world this is a cube conversation hi I'm Stu minimun and welcome to the cube from our Boston area studios we've been doing a series of CXO leadership discussions talking about how everyone's dealing with the global global endemic I've been welcome program a first-time guest Katy Bullard she is the president of a tile guru of course a cloud guru a online learning company we've had on the cube many times over the years Katy thanks so much thank you so much sue for having me I really appreciate it all right so Katie I remember I saw the in I think the announce was the end of at the beginning of the year your based at the headquarters in Austin you know online you know learning is a huge topic cloud of course you know one of those mega waves that we've been walking a long time and then you know out of nowhere global pandemic you know it's striking us so you know bring us inside you know obviously you know taking a new role in a new organization as it own challenges normally it's like okay what am I going to do for the first 90 days and make that plan tell us you know how were you reacted in how the company has reacted with the koban 19 did you get a chance to look at my 90-day plan dude that was exactly where it was no well let me take you back I'll take you back to kind of why I chose to come to ECG because I think it informs actually what's happening right now as well when I when I was looking for the next opportunity what I look for is I look for two things primarily in a company one is a product that's in a market that's growing really really fast and a product that has raving customer bands and obviously ACG really you know check both of those boxes you think about this is pre Co but if you think about the cloud computing market growing you know 50 60 % a year and the number one challenge for people who are both moving to the cloud or moving to a multi cloud strategy was having enough skilled workers to to do that effectively there really wasn't a better intersection of two you know two who value propositions than what a CG offered which was serving the cloud computing market and skilling up workers in that market fast forward to February you know was interesting I actually went out to Australia offices in mid-february as this was starting to heat up came back just in time I think to not go into quarantine but we very quickly saw the impact and you know this isn't easy for anybody in in any situation but what we are hearing from our customers and from the market is that that move to the cloud is even more important now I think the latest that I saw from the the 2028 odd report said 65 percent of companies are planning a cloud migration 95 percent are of companies are employing a multi cloud strategy so that is accelerating and then of course we're all sitting at home right now and you're getting me in my in my dining room and we have the both learn online versus in person there's no longer in-person training there's no longer events for us to go to lives we're doing that online we also are seeing that you know the way that we use our time is changing so we're not spending hours anymore muting we have a lot of customers who are saying let's use that time instead of muting to learn improve ourselves improve our skills so you know everything is very unpredictable in this environment but we do feel like at ACG our fundamental mission is to help customers get through this to give them the skills that they need so that hopefully as everybody emerges from this later this year they're better positioned to take advantage of the opportunities in front of them ya know you hit on a lot of topics you know so much right now you know remote learning remote work or you know a big discussion the developer world has been looking at that for a long time and you know when I see you know the the the elementary and high school children as well as you know colleges and how they're handling distant learning I was well come on the Cronenberg's brothers you know built something in you know two or three week from your mother's basement Amazon and serverless and they framed millions of people now yeah you know good absolutely translate but it's challenging so I'm curious yes you know and you're working with the team is there anything you're doing to connect to some of the broader audience you know lessons that can be learned as I said you're you know highly scalable you know large scale and you know you have nowhere near the budget of you know these municipalities and colleges yet you do reach you know a very broad audience with some very important skill yes I mean if I think about the actual products itself and why it worked worked so well previously right why the Cronenberg brothers brought to market something that was so beloved but but more importantly why I think it's working so well now is that there was a recognition that we learn these days in bite-sized chunks right most of us don't have four hours a day or three days a week just to sit leave our job and go learn something and so from the very beginning their concept was let's break every single lesson up into these 20 minutes chunks so whether you know I'm on my commute in a previous world or whether I'm you know using some time that I used to spend on the road learning something new I can do it in very digestible forms and in a way that's really engaging to me so I think that model that they've employed from day one is even more valuable now in today's environment I think the other thing is that there was a recognition that we all have different learning styles right we all learn a little bit differently and so whether it's learning in 20 minute chunks so that's learning through video and PowerPoint or whether it's learning hands-on testing things breaking things building things the platform has evolved in a way to enable people no matter where they are in that cloud learning journey whether they're novice that's just getting started and wanting to learn kind of you know the PowerPoint basics like me when I first came on board right of the or a seasoned architect who's trying to get in and build new applications so I think those things are the things that allowed the platform to really resonate with the developer audience for so long and now as we have you know added out of the platform specifically for enterprises where previously you know is for individual developers we now have both I think that's the other thing that is really attractive to large enterprises is the fact that they now right are trying to train thousands of workers at the same time realizing again that every single one of them has a different learning style yeah Katie is as you said before there is you know a broad need or the skill set of cloud computing I'm curious have you seen anything in kind of your customer base either from the enterprise side or individuals is there are there any skill sets that are bubbling up right now that are a critical need or anything that is grown and you know we're curious we're always you know there's some people it's like oh I'm gonna come out of this you know whole experience and you know I love you know work in my home gym and you know learn new languages and become a master baker of sourdough you know me personally I've been really busy so you know I wish I had more spare time travel has definitely reduced thing but it's also given up the time that normally I was gonna you know read a book or you know catch up on raining yeah the sourdough bread is definitely not in my wheelhouse so we well we have seen some really interesting trends actually over the last few months the first one is that we've seen the percentage of our users that are logging in on a daily basis go up about 30 percent so people are taking advantage I think of a little bit of extra time to accelerate their learning the other thing that we are seeing and I was just looking at these stats last week is the kinds of courses and content that are being consumed are changing some of this was happening free covert and some of this was happening post covitz all split those up freako but what we've seen over the last order two 2/4 actually is a pretty significant increase in consumption across multi-cloud skills as you're in particular is seeing about a three times higher increase in consumption than the other two large CCS these although they're all three increasing rapidly so as we think about like the curriculum and our instructors that we're bringing on and what we're building up know historically ACG specifically had grown up in the AWS world but we are responding to that change very very late and in investing in you know a juror GCP and some of the other cloud adjacent courses so that we had been seeing happening over the last couple of quarters most recently what we're seeing is an increase in what i call our beginner or fundamental courses they think that is a direct reflection of people who are looking at this as an opportunity to rescale to set themselves up for a new career i'm so you know our introduction to AWS or introduction to Azure fundamentals or the introduction to DCP those are actually the courses that are increasing the fastest in ranking and anecdotally one of my favorite things to do is to go on LinkedIn or Twitter each day and look at you know what people are saying about ACG and over the last week especially I can't even count the number of folks who've said I'm using my lock down I'm for you know learning or I'm putting my my time and Quarantine to the best use by you know getting trained on ECG and so I think that what we are seeing there is a direct reflection of that alright yeah Katie maybe you can give us a little bit of the update on you know a cloud guru there was the Linux Academy acquisition and if you can share a little bit about this kind of the the the numbers of how many people have gone through your programmed you attract how many people actually get certifications afterwards which I know they need to go to the providers you know pay a fee for that kind of thing yeah we do yeah there's only been a few things happening over here in the last six months right I've got a small acquisition and then you know we're dealing with this now so we acquire Linux Academy in December so actually I came on board about the same time that we acquired the business one of my favorite stories is when I first started talking to Sam and team back in June a cg had about a hundred employees total by the time I was actually accepting an offer in October I think it was 200 employees in total so in a four month span the company had actually doubled we acquired Lenox Academy which was of equivalent size the ACG and so by the end of December we were a 400 person company a company that had been a hundred people know in in the middle of 2019 so 400 people now we are our biggest office is here in Austin we do have a large office in Melbourne Australia which was where the company was originally founded and where Sam is we have an office in London where Ryan is and Linux Academy was actually headquartered right outside of Fort Worth Texas so we've got an office there in Fort Worth as well so it's been amazing to see this company essentially quadruple in size over the last six months everything that goes into scaling a business like that bringing two competitors together integrating the business you know we are in the process of integrating the products and the content and the course dialogues right now so we're excited to bring that market later this year all in the midst of everyone also getting used to this very new and unprecedented environment yeah you know congratulations you know that you know always good to see great growth you know the thing I've noticed is you know ACG just as really goodwill in the community I see the orange shirts at many of the shows I you know right many of the other teams yeah we'll definitely have to get back to you about being on brain feed I was trying to coordinate with my background um one of the other things you know is some of my favorite content over the last few years that we've done the cube has been the serverless cough event so you know any discussion about you know will there be smokers to that or are we just going to need the weight or you know the physical events return before we see those so we actually have just started a new virtual event calendar actually our very first one was yesterday we had almost 3,000 people registering to attend and so it will be a series it's a series of virtual events and webinars that are done in partnership with other leading influencers and practitioners in the industry so expects if anyone's interested you can go online and register for one of the ACG webinars but we'll be having those every two week through the course of this year awesome love that and I guess the last thing Katie there's some other things you've been doing help unity in this need of the pandemic tell us a little bit about that yeah so two things in particular that we've really focused on the first one is across both the Linux Academy and the ACG platforms we have lowered permanently the price of our individual memberships so for individuals from 449 down to 379 we've seen that that has helped enable more people to be able to afford it who otherwise couldn't afford it so that's now in in market the other thing that we're really excited about that we launched this week is a free educational assistance program so we are offering 1,000 subscriptions to ACG for the year so annual subscriptions for people who have been most impacted by kovat so we have a couple of different specific criteria but if you've lost your job due to Ovid and you're in one of the the most heavily impacted industries whether that you know retail or hospitality or travel and are looking to really change careers get into the tech field get your initial certification we do now have a program for that so you go online to our website you're able to apply to that program we launched it yesterday maybe two days ago and I know we already have hundreds of applications so we're really excited to offer that all right well we'll make sure to get this out to the community is build out of that all right Katie thanks so much really pleasure to act up with you and I'm glad Congrats on all the progress thank you so much - thanks for having me alright serverless absolutely one of the topics I've been personally enjoying digging into the last couple years hope you've enjoyed I'm an attorney I'm sue minimun and as always thank you for watching thank you [Music]

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Hi, I'm Stew Minimum And and this is the Cube's coverage of Red Hat Summit 2020 course Digital event This year. We're not together at Mosconi, but we are bringing together many of the speakers thought leaders, customers in this very important ecosystem. Really excited to welcome back to our program. Stephanie Cheers. Who's the vice president and general manager of the Red Hat Enterprise Linux business unit inside of Red Hat. Stephanie. So great to see you have to give you a virtual hug high five year, but you know, always great to see and have you on the program. >>Oh, thank you. So it's great to be here, and this is what together means today. But it's great to be together with you >>again. Here it's limit. >>Yeah, the discussion is you talk on it together apart for for a time we talk in tact. That change is one of the only constants that we have, and there are more changes than ever happening right now. So before we get into kind of your B you talk a little bit about, You know, some of the big changes. There's organizational changes, you know, I know we spoke to you about in 2019 at IBM Think and Red Hat Summit because you've worked for both sides of the equation here, Uh, give us kind of the latest from your standpoint. >>Yes, certainly the leadership changes which have been public now for a couple weeks. Those were a big change >>for for us. I think one of the things that has come through is IBM has really been respecting what red hat is. What? Um, what we do. But also how we do it is very important and valued. And we at red Hat >>believe in it so strongly. We're sticking to what Red Hat does best. Everything is open source. Everything is collaborative. And honestly, I have to say it. It >>feels great as a red Hatter to see Jim in the position he's in at IBM Um, Paul's passion, >>which clearly comes across in his keynotes and >>his passion for how we do have an open source development model. It's great to have them now take over the CEO role for Red hat. So it's it's really exciting times. I think. Last year when we spoke, it was, um it was a bit of a wait and see and see what happens. And I think now the recent announcements really solidify this sort of synergy and partnership that IBM and Red Hat have and what our intentions are in the market. But at Red Hat, we still stay red hat, and we're still driving things the way we always have. And that's great. Feels that >>that that's great. And thank you so much for the update. So when we talk about your business unit that the Red Hat Enterprise, Linux, of course, Rehl, um, you know, I've got a little too much history, you know. I go back when it was, whereas, you know, before well and kind of wash the growth of Linux sto become really, you know, the underlying fabric of so much of what we see out there today for all of businesses, so many companies could not exist if it wasn't for Linux. And in the seven years we've been having the Cube, of course, we've really watched that that moved from Lennox to not only be some of the foundations of what's happening in customer's environments, but also a major piece of cloud and cloud. Native S O. You know, give us that up date as to, you know, here in 2020. You know why? You know Linux has been around for quite a long time, but, you know, it's still is relevant. >>Yeah, so that's it. That's a >>great leader and ties exactly to how we look at well in the red hat sort of entire portfolio. Um, when you look at Lenox of how it evolved, it started out as being a bit of a cheaper alternative to units. But it quickly became, because of the open source way and collaborative way it's developed. It quickly became sort of this springboard for innovation because you have all these incredible innovators collaborating upstream. All of that has fed to a whole different view of what Linux is. Is cloud exists because of Linux is containers are just a different deployment mechanism or Lennox workloads, artificial intelligence. All those APS are built on Linux, so it's become this standardized foundation upon which innovation is done today, And for me, that's the most exciting thing, because it red hat and rail. Our goal is to one. Have it just work right? It has >>to be the standard. And, um well, sometimes that can be misinterpreted. It >>is boring or a commodity. It is anything but a commodity. It's probably one of the most strategic decisions that someone makes. Is which Raoul Distribution? Which Red Hat, which Lennox distribution did they use and that really take real pride that it's built for the enterprise? It's build for security. It's built for resiliency, and all of that build it once deploy anywhere, translates into also using all the innovation, all the container ization capabilities, using it across multiple public clouds. So it's really that combination of having it just work, be the foundation of where you build once and then being able to leverage all the innovation that's coming out of the open source world today. >>Yeah, really interesting points. Stephanie, I think back to when we talked for years about the consumer nation consumers, consumer ization. Excuse me of I t and people thought that therefore, there wouldn't be differentiation, you know, just by white box things and everything will be off the shelf. But if you look at how most companies build things, they really hyper optimize that. I need to build what I need. I need to use the tools that are available, and I need to be able to be agile. You know, I want one of my highlights last year talking to a lot of companies going through their digital transformation and a number of them at Red Hat Summit last year where they talked about both the organization and technology changes that they're making to move faster. And, of course, your portfolio is a big piece of helping them move forward. >>And that's one thing we're seeing that that ability to consume, innovation and get the >>most and extract the most out of what they're running today in their data center. As customers transform and take on this digital transformation, it's not just a technology statement. In most cases, it's an organizational statement as well. And how do you bridge both those and move it forward? It's one thing we focus a lot on right with the open innovation labs, with a lot of customers as well, because it's not just about the technology, it's about the way we work in the way we do things as well. >>Yeah. So, Stephanie, you know, every every year or so I hear it's like, Oh, well, we've got a new way to To the operating system. There was the Jeff just enough operating system for for a while when container ization came out, there was little company named core Os. That was like, Oh, we're going to make a thin version or core OS is now Ah, piece of red hat. Um, so still, with the cloud, there's always, you know, we're going to change the way the operating system it's done. Um, we just love your viewpoint as to, you know, Red Hat has, you know, a few options and kind of a spectrum of offerings. But how do your customers think about the OS these days? And you know, how should we be thinking about rail specifically in that overall spectrum? >>No, it's so that's a great question, too. And we look at >>it as Lennox and Rehl is be one thing that stays the same and helps you get the value out of all the work you've already put in all the development work you've already put in. And make sure that that translates to the future, where everything is changing, how you deploy where you deploy what you deploy. All of that may change, but if you want to get the value out of the work in the development that has been done yesterday, you need something to stay the same. In our view, that's real. We build it with um in mind for the enterprise along lifecycle security support. We build all of that into it so that when you build on a rail monorail kernel, you can take that. If you want to deploy it in a container, you can deploy on Rehl itself. Or if you need orchestration, you can deploy it on open shift. And that's part of the reason why you mentioned Core OS. So we now have a rail core. OS is within open shift 4.0, on beyond, of course. But what we did was we tailor down what is. In reality, it's the same packages. It's the same certification, security, all of that work that we put in. We take the core OS piece of it, what's essential and really optimized for open shift. We build that into an immutable image, and it goes out as part of open shift. It's not available separately because it's really tailored. What we pick the life cycle is all matching open shift, >>and what that does >>is provide you on open shift experience. That's easy to update fully across the board, all the way down to the kernel. But you know, it's the same Lennox that you have in rail, >>and it's that consistency >>of technology that we really strive for. Um, same thing in public Cloud. So when you build an image on Prem on REL, you can take that image up into the public cloud. And no, it's the same level of security and it just will work, you know, part of part of my team. And we take a lot of pride in the fact that it will just work on. And while that >>may not sound super exciting, particularly in days >>like like right now, being dependable and being reliable and knowing that it's secure, all of that is really important when you run your business that those those features or anything but commoditized >>Well, yeah, I think one of the real volumes that customers see with real specifically is there's so much change going on there, and you look at the Linux community, you look at what open shifts doing in the Kubernetes community. There's so much coaches going on red hat packages that make sure that you don't need to think about the almost chaos that's going out there in all of those communities. But you packaged those together. So Stephanie rarely was, of course, one of the highlights of last year's Red Hat Summit. So we'd love to hear you know, if you've got any good customer stories, really, the momentum of relate as you've seen it, you roll out around the world as and then we'll talk about the new updates. You have this. >>Yeah, great. So Rehl eight was a big deal for us last year, as you remember, and partly because not >>only all the features and functions, of course, which we put into it, but also because we really wanted to reposition what the value of an operating system is within a data center and within their innovation future. So we really focus all the features and functions into two buckets. One is about how do we help you with the operating system? Run your business better, more efficiently If the most out of the systems you have in the critical workloads that you run today and how do we use the operating system to help you bridge into the next level of innovation? What's coming down the pipeline? Things like containers. >>And we really wanted to >>make sure that, as we see you know, most customers are looking to how they digitally transform. But of course, no one has the freedom to throw away everything they've done in the past. They want to build upon that and get value out of it. So we really focused on balancing those two things now, as we look at. In fact, one of the commitments we made because we heard it from customers was they wanted a more predictable deployment of our minor releases and our major releases. And we committed, um, at the REHL eight launch that we would be delivery minor releases every six months, major releases every three years, and we have held to that. We delivered 816 months after we delivered eight. And now you saw last week we delivered eight dot too. Um, this is what it means for us to stand by our world and be dependable as an operating system. And the beauty of the subscription with well is that if you're a customer and you're running REL seven, particularly in times right now, it's It's not that easy to get into your data center, perhaps. And so if you don't choose to update to eight now, you can stay on seven until that time works. That's to me. That's part of the beauty and the flexibility of the subscription model. We have course want to continue to bring your new capabilities and new features. But the subscription Our goal is to have a value subscription that you can you can get the most value from No matter when you decide to upgrade or no forward with, uh, with a different releases, we have >>Well, you can go. And congratulations on keeping the releases going on schedule. One of the nice things about open source is we can see the roadmap out there. You've made this Ah, this promise and you're keeping to it. So ah is you said the announcements we made has been talked about in the keynote. So give us a couple of highlights. Says what people to be looking at and looking to learn more when they dig into a thought to >>Yeah, great. So we really wanted to stick with a few key >>messages with it, and they do really tie to How do we help you run your business? And how do we help you grow your business? It's one thing that we announced and what we pivoted to, um, with the eight dot io is we >>really moved to? How do we How do we >>deliver what we called an intelligent OS, which means an OS that helps you bridge the gap and brings more value to you in your data center than you got before? One of the key aspects to this was adding in the capability of red hat insights, and we added insights capability into every single rail subscription that is under current support. So whether or not you moved to relate whether you have real seven, if you have a supported version of real six, all of those had insights added to it, and what insights is is a as a service on cloud at red hat dot com and link up your servers, and >>it will give you insight >>into operational capability. Is it configured correctly is it could be optimized for better performance. Where are you on your C V E updates and what it does is take all that knowledge that Red Hat has from all the support cases and things that we're seeing what's happening in the industry, what we're seeing other customers have, and we can even proactively help customers. The feedback on this capability has been huge. In fact, you'll see in the announcement last week we've added a lot of new capabilities into this specifically For that reason we've had customers, you know, it's like having it's like having more ops people on my team because I'm getting this input in directly from Red Hat for things to look at. And so that, to me, was probably one of the key aspects that, as we look from going to eight into eight dot too, how do we build up that capability? And of course, last week you saw we added a lot to that, and I think now more than ever, we want to make sure that everyone who has a real subscription is getting the most value out of that and I think insights is one of the places where if you have a subscription and, um, you can value or you can get more value from operational help, insights is a place where we want to help you. Um, we everything we had prior we have now bucket sized into a capability and insights called advisor is really about performance, stability and security and doing an analysis for you. We've added a new capabilities around vulnerability, Right. How do you re mediate common vulnerabilities and exposures, compliance aspect, patch aspect policies and drift? Um, kind of all of those we've now bucket it in into that insights capability. So this friends a lot more value to something that we have already seen. Customers say, You know, we didn't expect to get this amount of input and continuous growth because we constantly add new new rules into that engine. And so you know what? What we what we knew yesterday will be what we know tomorrow, and we look forward to sharing with that with everyone >>who has a subscription. So this is >>a place where I think it's ah, it's an important place for folks to look, particularly now because operational efficiency is really key. And security is really we have a lot of capabilities in both. What? Yes, Please, >>please, please, go ahead. Now, >>one other aspect on that that I wanted to mention >>was we also added a capability called subscription watch and subscription Watch helps you get a very simple, clean view of all the subscriptions you have and where they're running. And that was one thing that we saw. Customers say there was friction. And how do I know where my entitlements are? How I'm using them across my entire enterprise Corruption watch can help with that. So, um, this sort of cloud dot red hat dot com capability that we can assist with and is already part of your subscription. These are the kinds of things that we really want to help augment this to make Really intelligent os for the enterprise. >>Yeah. Stuff Stephanie. The comment I was gonna make is there's certain shows that I go to that every year. You go to it, You say Okay, it's a little bit bigger. They announce something. They made some progress on it. What has impressed me most about going to the red Hat show year after year is really the the growth of the of the portfolio, if you will. So when I first started going to it, it was, you know, a lot of the people there were, you know, the hard core Linux people. Um And then, you know, there's some storage people, some networking people is cloud containers really grew. It really blossomed into this really robust ecosystem. Oh, and growth there. So would love just to get your viewpoint on, you know, the skill set because, you know, I'm sure there's plenty of companies out there that are like, Well, you know, I've got some people that are, you know, my limits people, and they do things that aren't there. But, you know, how do you see kind of the skill set and what what Red Hat's doing really permeating more and more of, of companies, day to day activity. >>I think one of the things that I'm >>most proud of is even since last year's all the deeper collaborations we have between the various product lines. Certainly we'll talk with Joe Fitzgerald, and he and I work together very closely. Capabilities like insights. How do we add answerable capabilities directly into real. And what that does is really help. I think in any customer today, skills is probably one of the biggest concerns that they have. How do they grow those skills? How do they help folks grow and learn more and progress into the innovation areas? But clearly they still need their their mission critical applications to run and how do they span that? And I think what we're really trying to do is be able to bring the strength of the portfolio together to help a customer have more flexibility in how they leverage their skills and how they grow their skills. >>Because I think coming back to >>that statement that that you made earlier it's not just about technology. It's about how, if >>you really want to be, have agile, it's about >>how a company has organized. And I think we're hoping that we bring together the strength of the portfolio so that a customer is able todo leverage their organization and leverage their skills and the best way possible. I think another place where we worked hard on eight dot too. Some similar lines of bridging the portfolio was, you know, we announced back in eight dot io. We were putting container ization tools directly in Terrell with build a pod made in scope e 08 dot too. We brought in the newest versions of Scope EO and Build Up. In fact, in tech preview, you get containerized versions of those, and so we're continuing to add. What we are seeing is the container ization is a journey for customers. Many customers just want to deploy a single container on a server. Or they were. They want to deploy a single container in a VM Um, they're not ready for orchestration. We wanted to put the tools in so that a customer could do that on REHL. Get started, get those containers deployed on REHL. Put those tools directly, and we added it to old protocol, which is a tool built for security. It brings that security of SC Lennox and brings that up and adds value at the container level. It's those kinds of things as you see the bridge from well into open shift. How do we help a customer rich? That skill journey as well along that path and I think right now in kubernetes and Containers skills is a is a big, big area of focus, so the more we can help ease that across the portfolio and bring those things together is really important. And I know we're working very closely with the chefs in the, um and the team there in order to help bridge that. >>Excellent. Stephanie, I just want to give you the last word. We talked a lot about the ongoing journey that customers are going through. So give us your final take away as to how customers should be thinking about red hat in general and role specifically as their journey goes forward. >>I think I think one of the things >>we're very proud of here at Red Hat is that we always, particularly in the open source communities with our customers, with our partners, we want to roll up our sleeves and help, and that's we want. So, developer, we wanna work upstream with you. It's one of the things we're very proud of, and now, particularly in this time it's We want to make sure that folks understand we're here to help, and we want to make sure that you're getting the most out of the subscriptions you have, Um, and we help. We help you on that journey both to get the most out of you can out of your data center today. But also be ready for the innovation that you want to consume going forward. And we're collectively working across red Hat in order to make that happen. But it's, um >>even though this is different and it's there the virtual Experience edition of Red Hat Summit. It's >>great to be together and be able to share the whole message. >>Well, Stephanie, the open source community is definitely used to collaborating remotely. So thank you so much for joining us. It's a pleasure to see you. And we would hope to talk again soon. >>Great to see you too. Thank you for the time. >>Alright. You're watching the Cube's coverage of Red Hat Summit 2020 digitally with remote guests from around the globe. Instrument a man and thank you for watching the Cube. >>Yeah, yeah, yeah.

>>live from Atlanta, Georgia. It's the Q covering answerable Best 2019. Brought to you by Red Hat. >>Welcome back. Everyone keeps live coverage of answerable fast here in Atlanta. Georgia John for my coach do Minutemen were here. Stephanie chairs to the vice president of general manager of the rail business unit. Red Hat. Great to see you. Nice to see you, too. You have all your three year career. IBM now Invincible. Back, Back in the fold. >>Yeah. >>So last time we chatted at Red Hat Summit Rail. Eight. How's it going? What's the update? >>Yeah, so we launched. Related some. It was a huge opportunity for arrested Sort of Show it off to the world. A couple of key things we really wanted to do There was make sure that we showed up the red hat portfolio. It wasn't just a product launch. It was really a portfolio. Lunch feedback so far on relate has been great. We have a lot of adopters on their early. It's still pretty early days. When you think about it, it's been about a little over 445 months. So, um, still early days the feedback has been good. You know it's actually interesting when you run a subscription based software model, because customers can choose to go to eight when they need those features and when they assess those features and they can pick and choose how they go. But we have a lot of folks who have areas of relate that they're testing the feature function off. >>I saw a tweet you had on your Twitter feed 28 years old, still growing up, still cool. >>Yeah, >>I mean 28 years old, The world's an adult now >>know Lennox is running. The enterprise is now, and now it's about how do you bring new innovation in when we launched Relate. We focused really on two sectors. One was, how do we help you run your business more efficiently? And then how do we help you grow your business with innovation? One of the key things we did, which is probably the one that stuck with me the most, was we actually partnered with the Redhead Management Organization and we pulled in the capability of what's called insights into the product itself. So all carbon subscription 678 all include insights, which is a rules based engine built upon the data that we have from, you know, over 15 years of helping customers run large scale Lennox deployments. And we leverage that data in order to bring that directly to customers. And that's been huge for us. And it's not only it's a first step into getting into answerable. >>I want to get your thoughts on We're here and Ansel Fest ate one of our two day coverage. The Red Hat announced the answer Automation platform. I'll see. That's the news. Why is this show so important in your mind? I mean, you see the internal. You've seen the history of the industry's a lot of technology changes happening in the modern enterprises. Now, as things become modernized both public sector and commercial, what's the most important thing happening? Why is this as well fest so important this year? >>To me, it comes down to, I'd say, kind of two key things. Management and automation are becoming one of the key decision makers that we see in our customers, and that's really driven by. They need to be efficient with what they have running today, and they need to be able to scale and grow into innovation. platform. So management and automation is a core critical decision point. I think the other aspect is, you know, Lennox started out 28 years ago proving to the world how open source development drives innovation. And that's what you see here. A danceable fest. This is the community coming together to drive innovation, super modular, able to provide impact right from everything from how you run your legacy systems to how you bring security to it into how do you bring new applications and deploy them in a safe and consistent way? It spans the whole gambit. >>So, Stephanie, you know, there's so much change going on in the industry you talked about, you know what's happening in Relate. I actually saw a couple of hello world T shirts which were given out at Summit in Boston this year, maybe help tie together how answerable fits into this. How does it help customers, you know, take advantage of the latest technology and and and move their companies along to be able to take advantage of some of the new features? >>Yeah, and so I really believe, of course, that unopened hybrid cloud, which is our vision of where people want to go, You need Lennox. So Lenox sits at the foundation. But to really deploy it in in a reasonable way in a Safeway in an efficient way, you need management on automation. So we've started on this journey. When we launched, we announced its summit that we brought in insights and that was our first step included in we've seen incredible uptick. So, um, when we launch, we've seen 87% increase since May in the number of systems that are linked in, we're seeing 33% more increase in coverage of rules based and 152% increase in customers who are using it. What that does is it creates a community of people using and getting value from it, but also giving value back because the more data we have, the better the rules get. So one interesting thing at the end of May, the engineering team they worked with all the customers that currently have insights. Lincoln and they did a scan for Specter meltdown, which, of course, everyone knows about in the industry with the customers who had systems hooked up, they found 100 and 76,000 customer systems that were vulnerable to Spector meltdown. What we did was we had unanswerable playbook that could re mediate that problem. We proactively alerted those customers. So now you start to see problems get identified with something like insights. Now you bring an answerable and answerable tower. You can effectively decide. So I want to re mediate. I can re mediate automatically. I can schedule that remediation for what's best for my company. So, you know, we've tied these three things together kind of in the stepwise function. In fact, if you have a real subscription, you've hooked up to insights. If insights finds an issue, there's a fix it and with answerable, creates a playbook. Now I can use that playbook and answerable tower so really ties through nicely through the whole portfolio to be able to to do everything in feeling. >>It also creates collaboration to these playbooks can be portable, move across the organization, do it once. That's the automation pieces that >>yeah, absolutely. So now we're seeing automation. How do you look at it across multiple teams within an organization so you could have a tower, a tower admin be able to set rules and boundaries for teams, I can have an array l writes. I t operations person be able to create playbooks for the security protocols. How do I set up a system being able to do things repeatedly and consistently brings a whole lot of value and security and efficiency? >>One of the powers of answerable is that it can live in a header Ji. In this environment, you got your windows environment. You know, I've talked of'em where customers that are using it and, of course, in cloud help help us understand kind of the realm. You know why rail plus answerable is, you know, an optimal solution for customers in those header ingenious environment. And what would love I heard a little bit in the keynote about kind of the road map where it's going. Maybe you can talk to about where those would fit together. >>Yeah, perfect and e think your comment about Header genius World is is Keith. That is the way we live, And folks will have to live in a head or a genius, a cz far as the eye can see. And I think that's part of the value, right to bring choice when you look at what we do with rail because of the close collaboration we have between my team and Theo team. That in the management bu around insights are engineering team is actively building rules so we can bring added value from the sense of we have our red Hat engineers who build rail creating rules to mitigate things, to help things with migration. So us develop well, Aden adoption. We put in in place upgrades, of course, in the product. But also there's a whole set of rules curated, supported by red hat that help you upgrade to relate from a prior version. So it's the tight engineering collaboration that we can bring. But to your point, it's, you know, we want to make sure that answerable and answerable tower and the rules that are set up bring added value to rebel and make that simple. But it does have to be in a head of a genius world. I'm gonna live with neighbors in any data center. Of course, >>what one of the pieces of the announcement talked about collections, eyes there, anything specific from from your team that it should be pointed out about from a collections in the platform announcement. >>So I think I think his collection starts to starts to grow on. Git brings out sort of the the simplicity of being pulled. It pulled playbooks and rolls on and pull that all in tow. One spot. We'll be looking at key scenarios that we pulled together that mean the most Terrell customers. Migration, of course, is one. We have other spaces, of course. Where we work with key ecosystem partners, of course, ASAP, Hana, running on rail has been a big focus for us in partnership with S A P. We have a playbook for installing ASAP Hana on Well, so this collaboration will continue to grow. I think collections offers a huge opportunity for a simpler experience to be able to kind of do a automated solution, if you will kind of on your floor >>automation for all. That's the theme here. >>That's what I >>want to get your thoughts on. The comment you made about analytical analytics keep it goes inside rail. This seems to be a key area for insights. Tying the two things together so kind of cohesive. But decoupled. I see how that works. What kind of analytical cables are you guys serving up today and what's coming around the corner because environments are changing. Hybrid and multi cloud are part of what everyone's talking about. Take care of the on premises. First, take care of the public cloud. Now, hybrids now on operating model has to look the same. This is a key thing. What kind of new capabilities of analytics do you see? >>Yes, that's it. So let me step you through that a little bit because because your point is exactly right. Our goal is to provide a single experience that can be on Prem or off Prem and provides value across both, as as you choose to deploy. So insights, which is the analytics engine that we use built upon our data. You can have that on Prem with. Well, you can have it off from with well, in the public cloud. So where we have data coming in from customers who are running well on the public cloud, so that provides a single view. So if you if you see a security vulnerability, you can skin your entire environment, Which is great. Um, I mentioned earlier. The more people we have participating, the more value comes so new rules are being created. So as a subscription model, you get more value as you go. And you can see the automation analytics that was announced today as part of the platform. So that brings analytics capabilities to, you know, first to be able to see what who's running what, how much value they're getting out of analytics, that the presentation by J. P. Morgan Chase was really compelling to see the value that automation is delivering to them. For a company to be ableto look at that in a dashboard with analytics automation, that's huge value, they can decide. Do we need to leverage it here more? Do we need to bring it value value here? Now you combine those two together, right? It's it, And being informed is the best. >>I want to get your reaction way Make common. Are opening student in our opening segment around the J. P. Morgan comment, you know, hours, two minutes, days, two minutes, depending on what the configurations. Automation is a wonderful thing. Where pro automation, as you know, we think it's gonna be huge category, but we took, um ah survey inside our community. We asked our practitioners in our community members about automation, and then they came back with the following. I want to get your reaction. Four. Major benefits. Automation focused efforts allows for better results. Efficiency. Security is a key driver in all this. You mentioned that automation drives job satisfaction, and then finally, the infrastructure Dev ops folks are getting re skilled up the stack as the software distraction. Those are the four main points of why automation is impacting enterprise. Do you agree with that? You make comments on some of those points? >>No, I do. I agree. I think skills is one thing that we've seen over and over again. Skills is skills. His key. We see it in Lennox. We have to help, right? Bridge window skills in tow. Lennox skills. I think automation that helps with skills development helps not only individuals but helps the company. I think the 2nd 2nd piece that you mentioned about job satisfaction at the end of the day, all of us want to have impact. And when you can leverage automation for one individual toe, have impact that that is much broader than they could do before with manual tasks. That's just that's just >>you know, Stew and I were talking also about the one of the key note keywords that kept on coming out and the keynote was scales scales, driving a lot of change in the industry at many levels. Certainly, software automation drives more value. When you have scale because you scaling more stuff, you can manually configure his stuff. A scale software certainly is gonna be a big part of that. But the role of cloud providers, the big cloud providers see IBM, Amazon, all the big enterprises like Microsoft. They're traveling massive scale. So there's a huge change in the open source community around how to deal with scale. This is a big topic of conversation. What's your thoughts on this? Sending general opinions on how the scales change in the open source equation. Is it more towards platforms, less tools, vice versa? Is there any trends? You see? >>I think it's interesting because I think when I think a scale, I think both volume right or quantity as the hyper scale ours do. I think also it's about complexity. I think I think the public clouds have great volume that they have to deal with in numbers of systems, but they have the ability to customize leveraging development teams and leveraging open source software they can customize. They can customize all the way down to the servers and the processor chips. As we know for most folks, right, they scale. But when they scale across on Prem in off from its adding complexity for them. And I think automation has value both in solving volume issues around scale, but also in complexity issues around scale. So even you know mid size businesses if they want a leverage on Prem, an off ramp to them, that's complexity scale. And I think automation has a huge amount of value to >>bring that abstracts away. The complexity automated, absolutely prized job satisfaction but also benefits of efficiency >>absolutely intimately. The greatest value of efficiency is now. There's more time to bring an innovation right. It's a zoo, Stephanie. >>Last thing I wondering, What feedback are you hearing from customers? You know, one of the things that struck me we're talking about the J. P. Morgan is they made great progress. But he said they had about a year of working with security of the cyber, the control groups to help get them through that knothole of allowing them toe really deploy automation. So, you know, usually something like answerable. You think? Oh, I can get a team. Let me get it going. But, oh, wait, no, Hold on. Corporate needs to make its way through. What is that something you hear generally? Is that a large enterprise thing? You know what? What are you hearing from customers that you're >>talking? I think I think we see it more and more, and it came up in the discussions today. The technical aspect is one aspect. The sort of cultural or the ability to pull it in is a whole separate aspect. And you think that technology from all of us who are engineers, we think, Well, that's the tough bit. But actually, the culture bit is just it's hard. One thing that that I see over and over again is the way cos air structured has a big impact. The more silo the teams are, do they have a way to communicate because fixing that so that you, when you bring in automation, it has that ability to sort of drive more ubiquitous value across. But if you're not structured toe leverage that it's really hard if your I T ops guys don't talk to the application folks bringing that value is very hard, so I think it is kind of going along in parallel right. The technical capabilities is one aspect. How you get your organization structure to reap the benefits is another aspect, and it's a journey. That's that's really what I see from folks. It is a journey. And, um, I think it's inspiring to see the stories here when they come back and talk about it. But to me the most, the greatest thing about it's just start right. Just start wherever you are and and our goal is to try and help on ramps for folks wherever their journey is, >>is a graft over people's careers and certainly the modernization of the enterprise and public sector and governments from how they procure technology to how they deploy and consume it is radically changing very quickly. By the way too scale on these things were happening. I've got to get your take on. I want to get your expert opinion on this because you have been in the industry of some of the different experiences. The cloud one Datta was the era of compute storage startups started Airbnb start all these companies examples of cloud scale. But now, as we start to get into the impact to businesses in the enterprise with hybrid multi cloud, there's a cloud. 2.0 equation again mentioned Observe Ability was just network management at White Space. Small category. Which company going public? It's important now kind of subsystem of cloud 2.0, automation seems to feel the same way we believe. What's your definition of cloud to point of cloud? One daughter was simply stand up some storage and compete. Use the public cloud and cloud to point is enterprise. What does that mean to you? What? How would you describe cloud to point? >>So my view is Cloud one Dato was all about capability. Cloud to Dato is all about experience, and that is bringing a whole do way that we look at every product in the stack, right? It has to be a seamless, simple experience, and that's where automation and management comes in in spades. Because all of that stuff you needed incapability having it be secure, having it be reliable, resilient. All of that still has to be there. But now you now you need the experience or to me, it's all about the experience and how you pull that together. And that's why we're hoping. You know, I'm thrilled here to be a danceable fast cause. The more I can work with the teams that are doing answerable and insights and the management aspect in the automation, it'll make the rail experience better >>than people think it's. Software drives it all. Absolutely. Adam, Thanks for sharing your insights on the case. Appreciate you coming back on and great to see you. >>Great to be here. Good to see >>you. Coverage here in Atlanta. I'm John for Stupid Men Cube coverage here and answerable Fest Maur coverage. After the short break, we'll be right back. >>Um

>> from our studios in the heart of Silicon Valley. HOLLOWAY ALTO, California It is a cube conversation. >> Welcome to this Special Cube conversation here in Palo Alto, California at the Cube Studios at the Cube headquarters. I'm John for the host, like you were a Dustin Kirkland product manager and Google friend of the Cuban. The community with Cooper Netease been on the Cube Cube alumni. Dustin. Welcome to the Cube conversation. >> Thanks. John's a beautiful studio. I've never been in the studio and on the show floor a few times, but this is This is fun. >> Great to have you on a great opportunity to chat about Cooper Netease yet of what you do out some product man's working Google. But really more importantly on this conversation is about the fifth anniversary, the birthday of Cuba Netease. Today we're celebrating the fifth birthday of Cooper Netease. Still, it's still a >> toddler, absolutely still growing. You think about how you know Lennox has been around for a long time. Open stack has been around these other big projects that have been around for, you know, going on decades and Lenox this case and Cooper nineties. It's going so fast, but It's only five years old, you know. >> You know, I remember Adam Open Stack event in Seattle many, many years ago. That was six years ago. Pubes on his 10th year. So many of these look backs moments. This is one of them. I was having a beer with Lou Tucker. J J Kiss Matic was like one of the first comes at the time didn't make it, But we were talking about open stagger like this Cooper Netease thing. This is really hot. This paper, this initiative this could really be the abstraction layer to kind of bring all this cloud Native wasn't part of the time, but it was like more of an open stack. Try and move up to stack. And it turned out it ended up happening. Cooper Netease then went on to change the landscape of what containers did. Dr. Got a lot of credit for pioneering that got the big VC funding became a unicorn, and then containers kind of went into a different direction because of Cooper duties. >> Very much so. I mean, the modernization of software infrastructure has been coming for a long time, and Cooper nutty sort of brings it all brings it all together at this point, but putting software into a container. We've been doing that different forest for for a lot of time, uh, for a long time, but But once you have a lot of containers, what do you do with that? Right? And that was the problem that Cooper Nettie solved so eloquently and has, you know, now for a couple of years, and it just keeps getting better. >> You know, you mentioned modernization. Let's talk about that because I think the modernization the theme is now pretty much prevalent in every vertical. I'll be in D. C. Next week for the Amazon Webster was public sector Summit, where modernization of governments and nations are being discussed. Education, modernization of it. We've seen it here. The media business that were participating in is about not where you store the code. It's how you code. How you build is a mindset shift. This has been the rial revelation around the Dev Ops Movement Infrastructures Code, now called Cloud Native. Share your thoughts on this modernization mindset because it really is how you build. >> Yeah, I think the cross pollination actually across industries and we even we see that even just in the word containers, right and all the imagery around shipping and shipping containers, we've applied these age old concepts that have been I don't have perfected but certainly optimized over decades of, actually centuries or millennia of moving things across water in containers. Right. But we apply that to software and boom. We have the step function difference in the way that we we manage and we orchestrated and administer code. That's one example of that cross pollination, and now you're talking about, like optimizing optimized governments or economies but being able to maybe then apply other concepts that we've come a long way in computer science do de bop set a good example? You know, applying Dev ops principles to non computer feels. Just think about that for a second. >> It's mind blowing. And if you think about also the step function you mentioned because I think this actually changed a lot of the entrepreneurial landscape as well and also has shaped open source and, you know, big news this this quarter is map are going to shut down due one of the biggest do players. Cloudera merge with Horton Works fired their CEO, the founder Michael. So has retired, Some say forced out. I don't think so. I think it's more of his time. I'm Rodel still there. Open source is a business model, you know. Can we be the red hat for her? Duped the red? Not really kind of the viable, but it's evolving. So open source has been impacted by this step function. There's a business impact. Talk about the dynamics with step function both on the business side and on how software's built specifically open source. >> You know, you and I have been around open source for a long, long time. I think it started when I was in college in the late nineties on then through my career at IBM. And it's It's interesting how on the fringe open source was for so long and such so so much of my BM career. And then early time spent onside it at Red Hat. It was it was something that was it was different, was weird. It was. It was very much fringe where the right uh, but now it's in mainstream and it's everywhere, and it's so mainstream that it's almost the defacto standard to just start with open source. But you know, there's some other news that's been happening lately that she didn't bring up. But it's a really touchy aspect of open source right now on that's on some of the licenses and how those licenses get applied by software, especially databases. When offered as a service in the cloud. That's one of the big problems. I think that that's that we're we're working within the open >> source, summarize the news and what it means. What's what's happening? What's the news and what's the really business? Our technical impact to the licensing? What's the issue? What's the core issue? >> Yeah, eso without taking judgment any any way, shape or form on this, the the the TL D are on. This is a number of open source database is most recently cockroach D. B. I have adopted a different licensing model that is nonstandard from an open source perspective. Uh, and from one perspective, they're they're adopting these different licensing models because other vendors can take that software and offered as a service, yes, and in some some cases, like Amazon like Sure, you said, uh, and offered as a as a service, uh, and maybe contribute. Maybe pay money to the smaller startup or the open source community behind it. But not necessarily. Uh, and it's in some ways is quite threatening to open source communities and open source companies on other cases, quite empowering. And it's going to be interesting to see how that plays out. The tension between open sourcing software and eventually making money off of it is something that we've we've seen for, you know, at least 25. >> And it continues to go on today, and this is, to me a real fascinating area that I think is going to be super important to keep an eye on because you want to encourage contribution and openness. Att the same time we look at the scale of just the Lenox foundations numbers. It's pretty massive in terms of now, the open source contribution. When you factor in even China and other nations, it's it's on exponential growth, right? So is it just open source? Is the model not necessarily a business? Yeah. So this is the big question. No one knows. >> I think we crossed that. And open source is the model. Um, and this is where me is a product manager. That's worked around open source. I've spent a lot of time thinking about how to create commercial offerings around open source. I spent 10 years at Economical, the first half of which, as an engineer, the second half of which, as a product manager around, uh, about building services, commercial services around 12 And I learned quite a few things that now apply absolutely to communities as well as to a number of open source startups. That that I've advised on DH kind of given them some perspective on maybe some successful and unsuccessful ways to monetize that that opens. >> Okay, so doesn't talk about Let's get back to Coburg. And so I think this is the next level Talk track is as Cooper Netease has established itself and landed in the industry and has adoption. It's now an expansion votes the land adopted expand. We've seen adoption. Now it's an expansion mode. Where does it go from here? Because you look at the tale signs things like service meshes server. Listen, you get some interesting trends that going to support this expansionary stage of uber netease. What is your view about the next expansion everyway what >> comes next? Yeah, I I think I think the next stage is really about democratizing communities for workloads that you know. It's quite obvious where when communities is the right answer at the scale of a Google or a Twitter or Netflix or, you know, some of these massive services that it is obviously and clearly the best answer to orchestrating containers. Now I think the next question is, how does that same thing that works at that massive scale Also worked for me as a developer at a very small scale helped me develop my software. My small team of five or 10 people. Do I need a coup? Burnett. He's If I'm ah five or 10 person startup. Well, I mean, not the original sort of borde vision of communities. It's probably overkill, but actually the tooling has really advanced, and we now >> have >> communities that makes sense on very small scales. You've got things like a three s from from Rancher. You've got micro Kates from from my colleagues at economical other ways of making shrinking communities down to something that fits, perhaps on devices perhaps at the edge, beyond just the traditional data center and into remote locations that need to deploy manage applications >> on the Cooper Netease clustering the some of the tech side. You know, we've seen some great tech trends as mentioned in Claudia Horton. Works and map Our Let's Take Claudia and Horton work. Remember back in the old days when it was booming? Oh, they were so proud to talk about their clusters. I stood up all these clusters and then I would ask them, Well, what do you doing with it? Well, we're storing data. I think so. That became kind of this use case where standing up the cluster was the use case and they're like, OK, now let's put some data in it. It's a question for you is Coburn. Eddie's a little bit different. I'm not seeing they were seeing real use cases. What are people standing up? Cuban is clusters for what specific Besides the same Besides saying I've done it. Yeah, What's the what's the main use case that you're seeing this that has real value? >> Yeah, actually, there's you just jog t mind of really funny memory. You know, back in those big data days, I was CEO of a startup. We were encrypting data, and we were helping encrypt healthcare data for health care companies and the number of health care companies that I worked with at that time who said they had a big data problem and they had all of I don't know, 33 terabytes worth of worth of data that they needed to encrypt. It was kind of humorous sometimes like, Is that really a big, big data problem? This fits on a single disc, you know, Uh, but yeah, I mean, it's interesting how >> that the hype of of the tech was preceding. The reality needs needs, says Cooper Nettie. So I have a Cuban Eddie's cluster for blank. Fill in the blank. What are people saying? >> Yeah, uh, it's It's largely about the modernization. So I need to modernize my infrastructure. I'm going to adopt the platform. That's probably not, er, the old er job, a Web WebSphere type platform or something like that. I'm investing in hardware investing in Software Middle, where I'm investing in people, and I want all of those things to line up with where industry is going from a software perspective, and that's where Cooper Nighties is sort of the cornerstone piece of that Lennox Of course, that's That's pretty well established >> canoes delivery in an integration piece of is that the pipeline in was, that was the fit on the low hanging fruit use cases of Cooper Netease just development >> process. Or it's the operations it's the operations of now got software that I need to deploy across multiple versions, perhaps multiple sites. Uh, I need to handle that upgrade ideally without downtime in a way that you said service mash in a way that meshes together makes sense. I've got a roll out new certificates I need to address the security, vulnerability, thes air, all the things that Cooper and I used to such a better job at then, what people were doing previously, which was a whole lot of four loops, shell strips and sshh pushing, uh, pushing tar balls around. Maybe Debs or rpm's around. That is what Cooper not he's actually really solves and does an elegant job of solving as just a starting point. And that's just the beginning and, you know, without getting ve injury here, you know, Anthros is the thing that we had at Google have built around Cooper Netease that brings it to enterprise >> here the other day did a tweet. I called Anthem. I just typing too fast. I got a lot of crap on Twitter for that mission. And those multi cloud has been a big part of where Cubans seems to fit. You mentioned some of the licensing changes. Cloud has been a great resource for a lot of the new Web scale applications from all kinds of companies. Now, with several issues seeing a lot more than capabilities, how do you see the next shift with data State coming in? Because God stateless date and you got state full data. Yeah, this has become a conversation point. >> Yeah, I think Kelsey Hightower has said it pretty eloquently, as he usually does around the sort of the serval ist movement and lets lets developers focus on just their code and literally just their code, perhaps even just their function in just their piece of code, without having to be an expert on all of the turtles all the way, all the way down. That's the big difference about service have having written a couple of those functions. I can I can really invest my time on the couple of 100 lines of code that matter and not choosing a destro choosing a cougar Nati is choosing, you know, all the stack underneath. I simply choose the platform where I'm gonna drop that that function, compile it, uploaded and then riff and rub. On that >> fifth anniversary, Cooper Netease were riffing on Cooper Netease. Dustin Circle here inside the Cube Cube Alumni you were recently at the coop con in overseas in Europe, Barcelona, Barcelona, great city. Keeps been there many times. Do was there covering for us. Couldn't make this trip, Unfortunately, had a couple daughter's graduating, so I didn't make the trip. Sorry, guys. Um, what was the summary? What was the takeaway? Was the big walk away from that event? What synthesized? The main stories were the most important stories being >> told. >> Big news, big observations. >> It was a huge event to start with. It was that fear of Barcelona. Um, didn't take over the whole space. But I've been there a number of times from Mobile World Congress. But, you know, this is this is cube con in the same building that hosts all of mobile world Congress. So I think 8,000 attendees was what we saw. It's quite celebratory. You know, I think we were doing some some pre fifth birthday bash celebrations, Key takeaways, hybrid hybrid, Cloud, multi Cloud. I think that's the world that we've evolved into. You know, there was a lot of tension. I think in the early days about must stay on. Prem must go to the cloud. Everything's there's gonna be a winner and a loser and everything's gonna go one direction or another. I think the chips have fallen, and it's pretty obvious now that the world will exist in a very hybrid, multi cloud state. Ultimately, there's gonna be some stuff on Prem that doesn't move. There's going to be some stuff better hosted in one arm or public clouds. That's the multi cloud aspect, Uh, and there will be stubborn stuff at the edge and remote locations and vehicles on oil rigs at restaurants and stores and >> so forth. What's most exciting from a trans statement? What do you what? What's what's getting you excited from what you see on the landscape out there? >> So the tying all of that to Cooper Netease, Cuban aunties, is the thing that basically normalizes all of that. You write your application put it in a container and expect to communities to be there to scale that toe. Operate that top grade that to migrate that over time. From that perspective, Cooper nineties has really ticked, ticked all the boxes, and you've got a lot of choices now about which companies here, you're going to use it and where >> beyond communities, a lot of variety of projects coop flow, you got service messes out there a lot of difference. Project. What's What's a dark horse? What's something that sets out there that people should be paying attention to? That you see emerging? That's notable. That should be paying attention. To >> think is a combination of two things. One is pretty obvious, and that's a ML is coming like a freight train and is sort of the next layer of excitement. I think after Cooper, Netease becomes boring, which hopefully if we've done our jobs well, that communities layer gets settled and we'll evolve. But the sort of the hockey stick hopefully settles down and it becomes something super stable. Uh, the application of machine learning to create artificial intelligence conclusions, trends from things that is sort of the next big trend on then I would say another one If you really want the dark horse. I think it's around communications. And I think it's around the difference in the way that we communicate with one another across all forms of media voice, video chat, writing, how we interact with people, how we interact with our our tools with our software and in fact, how our software in Iraq's with us in our software acts with with other software that communications industry is, it's ripe for some pretty radical disruption. And you know some of the organizations and they're doing that. It's early early days on those >> changes. Final point you mentioned earlier in our conversation here about how Dev Ops is influencing impacting non tech and computer science. Really? What did you mean by that? >> Uh, well, I think you brought up unexpectedly and that that you were looking at the way Uh, some other industries are changing, and I think that cross pollination is actually quite quite powerful when you take and apply a skill and expertise you have outside of your industry. But it adds something new and interesting, too, to your professional environment. That's where you get these provocative operations. He's really creative, innovative things that you know. No one really saw it coming. >> Dave Ops principles apply to other disciplines. Yeah, agility. That's that's pointing down waterfall based processes. That's >> one phenomenal example. Imagine that for governments, right to remove some of the like the pain that you and I know. I've got to go and renew my license. My birthday's coming up. I gotta go to renew my driver's license. You know much. I'm dreading going to the the DMV Root >> Canal driver's license on the same. Exactly >> how waterfall is that experience. And could we could we beam or Mohr Agile More Dev Autopsy and some of our government across >> the U. S. Government's procurement practices airbase upon 1990 standards they still want Request a manual, a physical manual for every product violent? Who does that? >> I know that there are organizations trying to apply some open source principles to government. But I mean, think about, you know, just democracy and how being a little bit more open and transparent in the way that we are in open source code, the ability to accept patches. I have a side project, a passion for brewing beer and I love applying open source practices to the industry of brewing. And that's an example of where use professional work, Tio. Compliment a hobby. >> All right, we got to bring some cubic private label, some Q beer. >> If you like sour beer, I'm in the sour beer. >> That's okay. We like to get the pus for us. Final question for you. Five years from now, Cooper needs to be 10 years old. What's the world gonna look like when we wake up five years from now with two Cuban aunties? >> Yeah, I think, uh, I don't think we're struggling with the Cooper nutties. Uh, the community's layer. At that point, I think that's settled science, inasmuch as Lennox is pretty settled. Science, Yes, there's a release, and it comes out with incremental features and bug fixes. I think Cuban aunties is settled. Science management of of those containers is pretty well settled. Uh, five years from now, I think we end up with software, some software that that's writing software. And I don't quite mean that in the way That sounds scary, uh, and that we're eliminating developers, but I think we're creating Mohr powerful, more robust software that actually creates that that software and that's all built on top of the really strong, robust systems we have underneath >> automation to take the heavy lifting. But the human creation still keeping one of the >> humans Aaron the look it's were We're many decades away from humans being out of the loop on creative processes. >> Dustin Kirkland, he a product manager of Google Uh, Cooper Netease guru also keep alumni here in the studio talking about the coup. Burnett. He's 50 year anniversary. Of course, the kid was president creation during the beginning of the wave of communities. We love the trend we love Cloud would left home a tec. I'm Sean for here in Palo Alto. Thanks for watching.

>> Ladies and gentlemen, please welcome Red Hat President Products and Technologies. Paul Cormier. Boring. >> Welcome back to Boston. Welcome back. And welcome back after a great night last night of our opening with with Jim and talking to certainly saw ten Jenny and and especially our customers. It was so great last night to hear our customers in how they set their their goals and how they met their goals. All possible because certainly with a little help from red hat, but all possible because of because of open source. And, you know, sometimes we have to all due that has set goals. And I'm going to talk this morning about what we as a company and with community, have set for our goals along the way. And sometimes you have to do that. You know, audacious goals. It can really change the perception of what's even possible. And, you know, if I look back, I can't think of anything, at least in my lifetime, that's more important. Or such a big golden John F. Kennedy setting the gold to the American people to go to the moon. I believe it or not, I was really, really only three years old when he said that, honestly. But as I grew up, I remember the passion around the whole country and the energy to make that goal a reality. So let's sort of talk about in compare and contrast, a little bit of where we are technically at that time, you know, tto win and to beat and winning the space race and even get into the space race. There was some really big technical challenges along the way. I mean, believe it or not. Not that long ago. But even But back then, math Malik mathematical calculations were being shifted from from brilliant people who we trusted, and you could look in the eye to A to a computer that was programmed with the results that were mostly printed out. This this is a time where the potential of computers was just really coming on the scene and, at the time, the space race at the time of space race it. It revolved around an IBM seventy ninety, which was one of the first transistor based computers. It could perform mathematical calculations faster than even the most brilliant mathematicians. But just like today, this also came with many, many challenges And while we had the goal of in the beginning of the technique and the technology to accomplish it, we needed people so dedicated to that goal that they would risk everything. And while it may seem commonplace to us today to trust, put our trust in machines, that wasn't the case. Back in nineteen sixty nine, the seven individuals that made up the Mercury Space crew were putting their their lives in the hands of those first computers. But on Sunday, July twentieth, nineteen sixty nine, these things all came together. The goal, the technology in the team and a human being walked on the moon. You know, if this was possible fifty years ago, just think about what Khun B. Accomplished today, where technology is part of our everyday lives. And with technology advances at an ever increasing rate, it's hard to comprehend the potential that sitting right at our fingertips every single day, everything you know about computing is continuing to change. Today, let's look a bit it back. A computing In nineteen sixty nine, the IBM seventy ninety could process one hundred thousand floating point operations per second, today's Xbox one that sitting in most of your living rooms probably can process six trillion flops. That's sixty million times more powerful than the original seventy ninety that helped put a human being on the moon. And at the same time that computing was, that was drastically changed. That this computing has drastically changed. So have the boundaries of where that computing sits and where it's been where it lives. At the time of the Apollo launch, the computing power was often a single machine. Then it moved to a single data center, and over time that grew to multiple data centers. Then with cloud, it extended all the way out to data centers that you didn't even own or have control of. But but computing now reaches far beyond any data center. This is also referred to as the edge. You hear a lot about that. The Apollo's, the Apollo's version of the Edge was the guidance system, a two megahertz computer that weighed seventy pounds embedded in the capsule. Today, today the edge is right here on my wrist. This apple watch weighs just a couple of ounces, and it's ten ten thousand times more powerful than that seventy ninety back in nineteen sixty nine But even more impactful than computing advances, combined with the pervasive availability of it, are the changes and who in what controls those that similar to social changes that have happened along the way. Shifting from mathematicians to computers, we're now facing the same type of changes with regards to operational control of our computing power. In its first forms. Operational control was your team, your team within your control? In some cases, a single person managed everything. But as complexity grows, our team's expanded, just like in the just like in the computing boundaries, system integrators and public cloud providers have become an extension of our team. But at the end of the day, it's still people that are still making all the decisions going forward with the progress of things like a I and software defined everything. It's quite likely that machines will be managing machines, and in many cases that's already happening today. But while the technology at our finger tips today is so impressive, the pace of changing complexity of the problems we aspire to solve our equally hard to comprehend and they are all intertwined with one another learning from each other, growing together faster and faster. We are tackling problems today on a global scale with unsinkable complexity beyond anyone beyond what any one single company or even one single country Khun solve alone. This is why open source is so important. This is why open source is so needed today in software. This is why open sources so needed today, even in the world, to solve other types of complex problems. And this is why open source has become the dominant development model which is driving the technology direction. Today is to bring two brother to bring together the best innovation from every corner of the planet. Toe fundamentally change how we solve problems. This approach and access the innovation is what has enabled open source To tackle The challenge is big challenges, like creating the hybrid cloud like building a truly open hybrid cloud. But even today it's really difficult to bridge the gap of the innovation. It's available in all in all of our fingertips by open source development, while providing the production level capabilities that are needed to really dip, ploy this in the enterprise and solve RIA world business problems. Red Hat has been committed to open source from the very, very beginning and bringing it to solve enterprise class problems for the last seventeen plus years. But when we built that model to bring open source to the enterprise, we absolutely knew we couldn't do it halfway tow harness the innovation. We had to fully embrace the model. We made a decision very early on. Give everything back and we live by that every single day. We didn't do crazy crazy things like you hear so many do out there. All this is open corps or everything below. The line is open and everything above the line is closed. We didn't do that, and we gave everything back Everything we learned in the process of becoming an enterprise class technology company. We gave it all of that back to the community to make better and better software. This is how it works. And we've seen the results of that. We've all seen the results of that and it could only have been possible within open source development model we've been building on the foundation of open source is most successful Project Lennox in the architecture of the future hybrid and bringing them to the Enterprise. This is what made Red Hat, the company that we are today and red hats journey. But we also had the set goals, and and many of them seemed insert insurmountable at the time, the first of which was making Lennox the Enterprise standard. And while this is so accepted today, let's take a look at what it took to get there. Our first launch into the Enterprise was rail two dot one. Yes, I know we two dot one, but we knew we couldn't release a one dato product. We knew that and and we didn't. But >> we didn't want to >> allow any reason why anyone of any customer anyone shouldn't should look past rail to solve their problems as an option. Back then, we had to fight every single flavor of Unix in every single account. But we were lucky to have a few initial partners and Big Eyes v partners that supported Rehl out of the gate. But while we had the determination, we knew we also had gaps in order to deliver on our on our priorities. In the early days of rail, I remember going to ask one of our engineers for a past rehl build because we were having a customer issue on it on an older release. And then I watched in horror as he rifled through his desk through a mess of CDs and magically came up and said, I found it here It is told me not to worry that the build this was he thinks this was the bill. This was the right one, and at that point I knew that despite the promise of Lennox, we had a lot of work ahead of us. The not only convinced the world that Lennox was secure, stable, an enterprise ready, but also to make that a reality. But we did. And today this is our reality. It's all of our reality. From the Enterprise Data Center standard to the fastest computers on the planet, Red Hat Enterprise, Lennox has continually risen to the challenge and has become the core foundation that many mission critical customers run and bet their business on. And an even bigger today Lennox is the foundation of which practically every single technology initiative is built upon. Lennox is not only standard toe build on today, it's the standard for innovation that builds around it. That's the innovation that's driving the future as well. We started our story with rail two dot one, and here we are today, seventeen years later, announcing rally as we did as we did last night. It's specifically designed for applications to run across the open hybrid. Clyde Cloud. Railed has become the best operating simp system for on premise all the way out to the cloud, providing that common operating model and workload foundation on which to build hybrid applications. Let's take it. Let's take a look at how far we've come and see this in action. >> Please welcome Red Hat Global director of developer experience, burst Sutter with Josh Boyer, Timothy Kramer, Lars Carl, it's Key and Brent Midwood. All right, we have some amazing things to show you. In just a few short moments, we actually have a lot of things to show you. And actually, Tim and Brandt will be with us momentarily. They're working out a few things in the back because we have a lot of this is gonna be a live demonstration, some incredible capabilities. Now you're going to see clear innovation inside the operating system where we worked incredibly hard to make it vast cities. You're free to manage many, many machines. I want you thinking about that as we go to this process. Now, also, keep in mind that this is the basis our core platform for everything we do here. Red hat. So it is an honor for me to be able to show it to you live on stage today. And so I recognize the many of you in the audience right now. Her hand's on systems administrators, systems, architect, citizens, engineers. And we know that you're under ever growing pressure to deliver needed infrastructure. Resource is ever faster, and that is a key element to what you're thinking about every day. Well, this has been a core theme, and our design decisions find red Odd Enterprise Lennox eight and intelligent operating system, which is making it fundamentally easier for you manage machines that scale. So hold what you're about to see next. Feels like a new superpower and and that redhead azure force multiplier. So first, let me introduce you to a large. He's totally my limits guru. >> I wouldn't call myself a girl, but I I guess you could say that I want to bring Lennox and light meant to more people. >> Okay, Well, let's let's dive in. And we're not about the clinic's eight. >> Sure. Let me go. And Morgan, >> wait a >> second. There's windows. >> Yeah, way Build the weft Consul into Really? That means that for the first time, you can log in from any device including your phone or this standard windows laptop. So you just go ahead and and to my Saturday lance credentials here. >> Okay, so now >> you're putting >> your limits password and over the web. >> Yeah, that might sound a bit scary at first, but of course, we're using the latest security tech by T. L s on dh csp on. Because that's the standard Lennox off site. You can use everything that you used to like a stage keys, OTP, tokens and stuff like this. >> Okay, so now I see the council right here. I love the dashboard overview of the system, but what else can you tell us about this council? >> Right? Like right here. You see the load of the system, some some of its properties. But you can also dive into logs everything that you're used to from the command line, right? Or lookit, services. This's all the services I've running, can start and stuff them and enable >> OK, I love that feature right there. So what about if I have to add a whole new application to this environment? >> Good that you're bringing that up. We build a new future into hell called application streams. Which the way for you to install different versions of your half stack that are supported I'LL show you with Youngmin a command line. But since Windows doesn't have a proper terminal, I'll just do it in the terminal that we built into the Web console Since the browser, I can even make this a bit bigger. Go to, for example, to see the application streams that we have for Poskus. Ijust do module list and I see you know we have ten and nine dot six Both supported tennis a default on defy enable ninety six Now the next time that I installed prescribes it will pull all their lady towards from them at six. >> Ok, so this is very cool. I see two verses of post Chris right here What tennis to default. That is fantastic and the application streams making that happen. But I'm really kind of curious, right? I loved using know js and Java. So what about multiple versions of those? >> Yeah, that's exactly the idea way. Want to keep up with the fast moving ecosystems off programming language? Isn't it a business? >> Okay, now, But I have another key question. I know some people were thinking it right now. What about Python? >> Yeah. In fact, in a minimum and still like this, python gives you command. Not fact. Just have to type it correctly. You can't just install which everyone you want two or three or whichever your application needs. >> Okay, Well, that is I've been burned on that one before. Okay, so no actual. Have a confession for all you guys. Right here. You guys keep this amongst yourselves. Don't let Paul No, I'm actually not a linnet systems administrator. I'm an application developer, an application architect, And I recently had to go figure out how to extend the file system. This is for real. And I'm going to the rat knowledge base and looking up things like, you know, PV create VD, extend resized to f s. And I have to admit, that's hard, >> right? I've opened the storage space for you right here, where you see an overview of your storage. And the council has made for people like you as well not only for people that I knew that when you two lunatics, right? It's if you're running, you're running some of the commands only, you know, some of the time you don't remember them. So, for example, I haven't felt twosome here. That's a little bit too small. Let me just throw it. It's like, you know, dragging this lighter. It calls all the command in the background for you. >> Oh, that is incredible. Is that simple? Just drag and drop. That is fantastic. Well, so I actually, you know, we'll have another question for you. It looks like now this linen systems administration is no longer a dark heart involving arcane commands typed into a black terminal. Like using when those funky ergonomic keyboards you know I'm talking about right? Do >> you know a lot of people, including me and people in the audience like that dark out right? And this is not taking any of that away. It's on additional tool to bring limits to more people. >> Okay, well, that is absolute fantastic. Thank you so much for that Large. And I really love him installing everything is so much easier, including a post gra seeker and, of course, the python that we saw right there. So now I want to change gears for a second because I actually have another situation that I'm always dealing with. And that is every time I want to build a new Lenox system, not only I don't want to have to install those commands again and again, it feels like I'm doing it over and over. So, Josh, how would I create a golden image? One VM image that can use and we have everything pre baked in? >> Yeah, absolutely. But >> we get that question all the time. So really includes image builder technology. Image builder technology is actually all of our hybrid cloud operating system image tools that we use to build our own images and rolled up in a nice, easy to integrate new system. So if I come here in the web console and I go to our image builder tab, it brings us to blueprints, right? Blueprints or what we used to actually control it goes into our golden image. Uh, and I heard you and Lars talking about post present python. So I went and started typing here. So it brings us to this page, but you could go to the selected components, and you can see here I've created a blueprint that has all the python and post press packages in it. Ah, and the interesting thing about this is it build on our existing kickstart technology. But you can use it to deploy that whatever cloud you want. And it's saved so that you don't actually have to know all the various incantations from Amazon toe azure to Google, whatever it's all baked in on. When you do this, you can actually see the dependencies that get brought in as well. Okay. Should we create one life? Yes, please. All right, cool. So if we go back to the blueprints page and we click create blueprint Let's, uh let's make a developer brute blueprint here. So we click great, and you can see here on the left hand side. I've got all of my content served up by Red Hat satellite. We have a lot of great stuff, and really, But we can go ahead and search. So we'LL look for post grows and you know, it's a developer image at the client for some local testing. Um, well, come in here and at the python bits. Probably the development package. We need a compiler if we're going to actually build anything. So look for GCC here and hey, what's your favorite editor? >> A Max, Of course, >> Max. All right. Hey, Lars, about you. I'm more of a person. You Maxim v I All right, Well, if you want to prevent a holy war in your system, you can actually use satellite to filter that out. But we're going to go ahead and Adam Ball, sweetie, I'm a fight on stage. So wait, just point and click. Let the graphical one. And then when we're all done, we just commit our changes, and our image is ready to build. >> Okay, So this VM image we just created right now from that blueprint this is now I can actually go out there and easily deploys of deploy this across multiple cloud providers. And as well as this on stage are where we have right now. >> Yeah, absolutely. We can to play on Amazon as your google any any infrastructure you're looking for so you can really hit your Clyburn hybrid cloud operating system images. >> Okay. All right, listen, we >> just go on, click, create image. Uh, we can select our different types here. I'm gonna go ahead and create a local VM because it's available image, and maybe they want to pass it around or whatever, and I just need a few moments for it to build. >> Okay? So while that's taking a few moments, I know there's another key question in the minds of the audience right now, and you're probably thinking I love what I see. What Right eye right hand Priceline say. But >> what does it >> take to upgrade from seven to eight? So large can you show us and walk us through an upgrade? >> Sure, this's my little Thomas Block that I set up. It's powered by what Chris and secrets over, but it's still running on seven six. So let's upgrade that jump over to my house fee on satellite on. You see all my relate machines here, including the one I showed you what Consul on before. And there is that one with my sun block and there's a couple others. Let me select those as well. This one on that one. Just go up here. Schedule remote job. And she was really great. And hit Submit. I made it so that it makes the booms national before. So if anything was wrong Kans throwback! >> Okay, okay, so now it's progressing. Here, >> it's progressing. Looks like it's running. Doing >> live upgrade on stage. Uh, >> seems like one is failing. What's going on here? Okay, we checked the tree of great Chuck. Oh, yeah, that's the one I was playing around with Butter fest backstage. What? Detective that and you know, it doesn't run the Afghan cause we don't support operating that. >> Okay, so what I'm hearing now? So the good news is, we were protected from possible failed upgrade there, So it sounds like these upgrades are perfectly safe. Aiken, basically, you know, schedule this during a maintenance window and still get some sleep. >> Totally. That's the idea. >> Okay, fantastic. All right. So it looks like upgrades are easy and perfectly safe. And I really love what you showed us there. It's good point. Click operation right from satellite. Ok, so Well, you know, we were checking out upgrades. I want to know Josh. How those v ems coming along. >> They went really well. So you were away for so long. I got a little bored and I took some liberties. >> What do you mean? >> Well, the image Bill And, you know, I decided I'm going to go ahead and deploy here to this Intel machine on stage Esso. I have that up and running in the web. Counsel. I built another one on the arm box, which is actually pretty fast, and that's up and running on this. Our machine on that went so well that I decided to spend up some an Amazon. So I've got a few instances here running an Amazon with the web console accessible there as well. On even more of our pre bill image is up and running an azure with the web console there. So the really cool thing about this bird is that all of these images were built with image builder in a single location, controlling all the content that you want in your golden images deployed across the hybrid cloud. >> Wow, that is fantastic. And you might think that so we actually have more to show you. So thank you so much for that large. And Josh, that is fantastic. Looks like provisioning bread. Enterprise Clinic Systems ate a redhead. Enterprise Enterprise. Rhetta Enterprise Lennox. Eight Systems is Asian ever before, but >> we have >> more to talk to you about. And there's one thing that many of the operations professionals in this room right now no, that provisioning of'em is easy, but it's really day two day three, it's down the road that those viens required day to day maintenance. As a matter of fact, several you folks right now in this audience to have to manage hundreds, if not thousands, of virtual machines I recently spoke to. Gentleman has to manage thirteen hundred servers. So how do you manage those machines? A great scale. So great that they have now joined us is that it looks like they worked things out. So now I'm curious, Tim. How will we manage hundreds, if not thousands, of computers? >> Welbourne, one human managing hundreds or even thousands of'em says, No problem, because we have Ansel automation. And by leveraging Ansel's integration into satellite, not only can we spin up those V em's really quickly, like Josh was just doing, but we can also make ongoing maintenance of them really simple. Come on up here. I'm going to show you here a satellite inventory and his red hat is publishing patches. Weaken with that danceable integration easily apply those patches across our entire fleet of machines. Okay, >> that is fantastic. So he's all the machines can get updated in one fell swoop. >> He sure can. And there's one thing that I want to bring your attention to today because it's brand new. And that's cloud that red hat dot com And here, a cloud that redhead dot com You can view and manage your entire inventory no matter where it sits. Of Redhead Enterprise Lennox like on Prem on stage. Private Cloud or Public Cloud. It's true Hybrid cloud management. >> OK, but one thing. One thing. I know that in the minds of the audience right now. And if you have to manage a large number servers this it comes up again and again. What happens when you have those critical vulnerabilities that next zero day CV could be tomorrow? >> Exactly. I've actually been waiting for a while patiently for you >> to get to the really good stuff. So >> there's one more thing that I wanted to let folks know about. Red Hat Enterprise. The >> next eight and some features that we have there. Oh, >> yeah? What is that? >> So, actually, one of the key design principles of relate is working with our customers over the last twenty years to integrate all the knowledge that we've gained and turn that into insights that we can use to keep our red hat Enterprise Lennox servers running securely, inefficiently. And so what we actually have here is a few things that we could take a look at show folks what that is. >> OK, so we basically have this new feature. We're going to show people right now. And so one thing I want to make sure it's absolutely included within the redhead enterprise in that state. >> Yes. Oh, that's Ah, that's an announcement that we're making this week is that this is a brand new feature that's integrated with Red Hat Enterprise clinics, and it's available to everybody that has a red hat enterprise like subscription. So >> I believe everyone in this room right now has a rail subscriptions, so it's available to all of them. >> Absolutely, absolutely. So let's take a quick look and try this out. So we actually have. Here is a list of about six hundred rules. They're configuration security and performance rules. And this is this list is growing every single day, so customers can actually opt in to the rules that are most that are most applicable to their enterprises. So what we're actually doing here is combining the experience and knowledge that we have with the data that our customers opt into sending us. So customers have opted in and are sending us more data every single night. Then they actually have in total over the last twenty years via any other mechanism. >> Now there's I see now there's some critical findings. That's what I was talking about. But it comes to CVS and things that nature. >> Yeah, I'm betting that those air probably some of the rail seven boxes that we haven't actually upgraded quite yet. So we get back to that. What? I'd really like to show everybody here because everybody has access to this is how easy it is to opt in and enable this feature for real. Okay, let's do that real quick, so I gotta hop back over to satellite here. This is the satellite that we saw before, and I'll grab one of the hosts and we can use the new Web console feature that's part of Railly, and via single sign on I could jump right from satellite over to the Web console. So it's really, really easy. And I'LL grab a terminal here and registering with insights is really, really easy. Is one command troops, and what's happening right now is the box is going to gather some data. It's going to send it up to the cloud, and within just a minute or two, we're gonna have some results that we can look at back on the Web interface. >> I love it so it's just a single command and you're ready to register this box right now. That is super easy. Well, that's fantastic, >> Brent. We started this whole series of demonstrations by telling the audience that Red Hat Enterprise Lennox eight was the easiest, most economical and smartest operating system on the planet, period. And well, I think it's cute how you can go ahead and captain on a single machine. I'm going to show you one more thing. This is Answerable Tower. You can use as a bell tower to managing govern your answerable playbook, usage across your entire organization and with this. What I could do is on every single VM that was spun up here today. Opt in and register insights with a single click of a button. >> Okay, I want to see that right now. I know everyone's waiting for it as well, But hey, you're VM is ready. Josh. Lars? >> Yeah. My clock is running a little late now. Yeah, insights is a really cool feature >> of rail. And I've got it in all my images already. All >> right, I'm doing it all right. And so as this playbook runs across the inventory, I can see the machines registering on cloud that redhead dot com ready to be managed. >> OK, so all those onstage PM's as well as the hybrid cloud VM should be popping in IRC Post Chris equals Well, fantastic. >> That's awesome. Thanks to him. Nothing better than a Red Hat Summit speaker in the first live demo going off script deal. Uh, let's go back and take a look at some of those critical issues affecting a few of our systems here. So you can see this is a particular deanna's mask issue. It's going to affect a couple of machines. We saw that in the overview, and I can actually go and get some more details about what this particular issue is. So if you take a look at the right side of the screen there, there's actually a critical likelihood an impact that's associated with this particular issue. And what that really translates to is that there's a high level of risk to our organization from this particular issue. But also there's a low risk of change. And so what that means is that it's really, really safe for us to go ahead and use answerable to mediate this so I can grab the machines will select those two and we're mediate with answerable. I can create a new playbook. It's our maintenance window, but we'LL do something along the lines of like stuff Tim broke and that'LL be our cause. We name it whatever we want. So we'Ll create that playbook and take a look at it, and it's actually going to give us some details about the machines. You know what, what type of reboots Efendi you're going to be needed and what we need here. So we'LL go ahead and execute the playbook and what you're going to see is the outputs goingto happen in real time. So this is happening from the cloud were affecting machines. No matter where they are, they could be on Prem. They could be in a hybrid cloud, a public cloud or in a private cloud. And these things are gonna be remediated very, very easily with answerable. So it's really, really awesome. Everybody here with a red hat. Enterprise licks Lennox subscription has access to this now, so I >> kind of want >> everybody to go try this like, we really need to get this thing going and try it out right now. But >> don't know, sent about the room just yet. You get stay here >> for okay, Mr. Excitability, I think after this keynote, come back to the red hat booth and there's an optimization section. You can come talk to our insights engineers. And even though it's really easy to get going on your own, they can help you out. Answer any questions you might have. So >> this is really the start of a new era with an intelligent operating system and beauty with intelligence you just saw right now what insights that troubles you. Fantastic. So we're enabling systems administrators to manage more red in private clinics, a greater scale than ever before. I know there's a lot more we could show you, but we're totally out of time at this point, and we kind of, you know, when a little bit sideways here moments. But we need to get off the stage. But there's one thing I want you guys to think about it. All right? Do come check out the in the booth. Like Tim just said also in our debs, Get hands on red and a prize winning state as well. But really, I want you to think about this one human and a multitude of servers. And if you remember that one thing asked you upfront. Do you feel like you get a new superpower and redhead? Is your force multiplier? All right, well, thank you so much. Josh and Lars, Tim and Brent. Thank you. And let's get Paul back on stage. >> I went brilliant. No, it's just as always, >> amazing. I mean, as you can tell from last night were really, really proud of relate in that coming out here at the summit. And what a great way to showcase it. Thanks so much to you. Birth. Thanks, Brent. Tim, Lars and Josh. Just thanks again. So you've just seen this team demonstrate how impactful rail Khun b on your data center. So hopefully hopefully many of you. If not all of you have experienced that as well. But it was super computers. We hear about that all the time, as I just told you a few minutes ago, Lennox isn't just the foundation for enterprise and cloud computing. It's also the foundation for the fastest super computers in the world. In our next guest is here to tell us a lot more about that. >> Please welcome Lawrence Livermore National Laboratory. HPC solution Architect Robin Goldstone. >> Thank you so much, Robin. >> So welcome. Welcome to the summit. Welcome to Boston. And thank thank you so much for coming for joining us. Can you tell us a bit about the goals of Lawrence Livermore National Lab and how high high performance computing really works at this level? >> Sure. So Lawrence Livermore National >> Lab was established during the Cold War to address urgent national security needs by advancing the state of nuclear weapons, science and technology and high performance computing has always been one of our core capabilities. In fact, our very first supercomputer, ah Univac one was ordered by Edward Teller before our lab even opened back in nineteen fifty two. Our mission has evolved since then to cover a broad range of national security challenges. But first and foremost, our job is to ensure the safety, security and reliability of the nation's nuclear weapons stockpile. Oh, since the US no longer performs underground nuclear testing, our ability to certify the stockpile depends heavily on science based science space methods. We rely on H P C to simulate the behavior of complex weapons systems to ensure that they can function as expected, well beyond their intended life spans. That's actually great. >> So are you really are still running on that on that Univac? >> No, Actually, we we've moved on since then. So Sierra is Lawrence Livermore. Its latest and greatest supercomputer is currently the Seconds spastic supercomputer in the world and for the geeks in the audience, I think there's a few of them out there. We put up some of the specs of Syrah on the screen behind me, a couple of things worth highlighting our Sierra's peak performance and its power utilisation. So one hundred twenty five Pata flops of performance is equivalent to about twenty thousand of those Xbox one excess that you mentioned earlier and eleven point six megawatts of power required Operate Sierra is enough to power around eleven thousand homes. Syria is a very large and complex system, but underneath it all, it starts out as a collection of servers running Lin IX and more specifically, rail. >> So did Lawrence. Did Lawrence Livermore National Lab National Lab used Yisrael before >> Sierra? Oh, yeah, most definitely. So we've been running rail for a very long time on what I'll call our mid range HPC systems. So these clusters, built from commodity components, are sort of the bread and butter of our computer center. And running rail on these systems provides us with a continuity of operations and a common user environment across multiple generations of hardware. Also between Lawrence Livermore in our sister labs, Los Alamos and Sandia. Alongside these commodity clusters, though, we've always had one sort of world class supercomputer like Sierra. Historically, these systems have been built for a sort of exotic proprietary hardware running entirely closed source operating systems. Anytime something broke, which was often the Vander would be on the hook to fix it. And you know, >> that sounds >> like a good model, except that what we found overtime is most the issues that we have on these systems were either due to the extreme scale or the complexity of our workloads. Vendors seldom had a system anywhere near the size of ours, and we couldn't give them our classified codes. So their ability to reproduce our problem was was pretty limited. In some cases, they've even sent an engineer on site to try to reproduce our problems. But even then, sometimes we wouldn't get a fix for months or else they would just tell us they weren't going to fix the problem because we were the only ones having it. >> So for many of us, for many of us, the challenges is one of driving reasons for open source, you know, for even open source existing. How has how did Sierra change? Things are on open source for >> you. Sure. So when we developed our technical requirements for Sierra, we had an explicit requirement that we want to run an open source operating system and a strong preference for rail. At the time, IBM was working with red hat toe add support Terrell for their new little Indian power architecture. So it was really just natural for them to bid a red. A rail bay system for Sierra running Raylan Cyril allows us to leverage the model that's worked so well for us for all this time on our commodity clusters any packages that we build for X eighty six, we can now build those packages for power as well as our market texture using our internal build infrastructure. And while we have a formal support relationship with IBM, we can also tap our in house colonel developers to help debug complex problems are sys. Admin is Khun now work on any of our systems, including Sierra, without having toe pull out their cheat sheet of obscure proprietary commands. Our users get a consistent software environment across all our systems. And if the security vulnerability comes out, we don't have to chase around getting fixes from Multan slo es fenders. >> You know, you've been able, you've been able to extend your foundation from all the way from X eighty six all all the way to the extract excess Excuse scale supercomputing. We talk about giving customers all we talked about it all the time. A standard operational foundation to build upon. This isn't This isn't exactly what we've envisioned. So So what's next for you >> guys? Right. So what's next? So Sierra's just now going into production. But even so, we're already working on the contract for our next supercomputer called El Capitan. That's scheduled to be delivered the Lawrence Livermore in the twenty twenty two twenty timeframe. El Capitan is expected to be about ten times the performance of Sierra. I can't share any more details about that system right now, but we are hoping that we're going to be able to continue to build on a solid foundation. That relish provided us for well over a decade. >> Well, thank you so much for your support of realm over the years, Robin. And And thank you so much for coming and tell us about it today. And we can't wait to hear more about El Capitan. Thank you. Thank you very much. So now you know why we're so proud of realm. And while you saw confetti cannons and T shirt cannons last night, um, so you know, as as burned the team talked about the demo rail is the force multiplier for servers. We've made Lennox one of the most powerful platforms in the history of platforms. But just as Lennox has become a viable platform with access for everyone, and rail has become viable, more viable every day in the enterprise open source projects began to flourish around the operating system. And we needed to bring those projects to our enterprise customers in the form of products with the same trust models as we did with Ralph seeing the incredible progress of software development occurring around Lennox. Let's let's lead us to the next goal that we said tow, tow ourselves. That goal was to make hybrid cloud the default enterprise for the architecture. How many? How many of you out here in the audience or are Cesar are? HC sees how many out there a lot. A lot. You are the people that our building the next generation of computing the hybrid cloud, you know, again with like just like our goals around Lennox. This goals might seem a little daunting in the beginning, but as a community we've proved it time and time again. We are unstoppable. Let's talk a bit about what got us to the point we're at right right now and in the work that, as always, we still have in front of us. We've been on a decade long mission on this. Believe it or not, this mission was to build the capabilities needed around the Lenox operating system to really build and make the hybrid cloud. When we saw well, first taking hold in the enterprise, we knew that was just taking the first step. Because for a platform to really succeed, you need applications running on it. And to get those applications on your platform, you have to enable developers with the tools and run times for them to build, to build upon. Over the years, we've closed a few, if not a lot of those gaps, starting with the acquisition of J. Boss many years ago, all the way to the new Cuban Eddie's native code ready workspaces we launched just a few months back. We realized very early on that building a developer friendly platform was critical to the success of Lennox and open source in the enterprise. Shortly after this, the public cloud stormed onto the scene while our first focus as a company was done on premise in customer data centers, the public cloud was really beginning to take hold. Rehl very quickly became the standard across public clouds, just as it was in the enterprise, giving customers that common operating platform to build their applications upon ensuring that those applications could move between locations without ever having to change their code or operating model. With this new model of the data center spread across so many multiple environments, management had to be completely re sought and re architected. And given the fact that environments spanned multiple locations, management, real solid management became even more important. Customers deploying in hybrid architectures had to understand where their applications were running in how they were running, regardless of which infrastructure provider they they were running on. We invested over the years with management right alongside the platform, from satellite in the early days to cloud forms to cloud forms, insights and now answerable. We focused on having management to support the platform wherever it lives. Next came data, which is very tightly linked toe applications. Enterprise class applications tend to create tons of data and to have a common operating platform foyer applications. You need a storage solutions. That's Justus, flexible as that platform able to run on premise. Just a CZ. Well, as in the cloud, even across multiple clouds. This let us tow acquisitions like bluster, SEF perma bitch in Nubia, complimenting our Pratt platform with red hat storage for us, even though this sounds very condensed, this was a decade's worth of investment, all in preparation for building the hybrid cloud. Expanding the portfolio to cover the areas that a customer would depend on to deploy riel hybrid cloud architectures, finding any finding an amplifying the right open source project and technologies, or filling the gaps with some of these acquisitions. When that necessarily wasn't available by twenty fourteen, our foundation had expanded, but one big challenge remained workload portability. Virtual machine formats were fragmented across the various deployments and higher level framework such as Java e still very much depended on a significant amount of operating system configuration and then containers happened containers, despite having a very long being in existence for a very long time. As a technology exploded on the scene in twenty fourteen, Cooper Netease followed shortly after in twenty fifteen, allowing containers to span multiple locations and in one fell swoop containers became the killer technology to really enable the hybrid cloud. And here we are. Hybrid is really the on ly practical reality in way for customers and a red hat. We've been investing in all aspects of this over the last eight plus years to make our customers and partners successful in this model. We've worked with you both our customers and our partners building critical realm in open shift deployments. We've been constantly learning about what has caused problems and what has worked well in many cases. And while we've and while we've amassed a pretty big amount of expertise to solve most any challenge in in any area that stack, it takes more than just our own learning's to build the next generation platform. Today we're also introducing open shit for which is the culmination of those learnings. This is the next generation of the application platform. This is truly a platform that has been built with our customers and not simply just with our customers in mind. This is something that could only be possible in an open source development model and just like relish the force multiplier for servers. Open shift is the force multiplier for data centers across the hybrid cloud, allowing customers to build thousands of containers and operate them its scale. And we've also announced open shift, and we've also announced azure open shift. Last night. Satya on this stage talked about that in depth. This is all about extending our goals of a common operating platform enabling applications across the hybrid cloud, regardless of whether you run it yourself or just consume it as a service. And with this flagship release, we are also introducing operators, which is the central, which is the central feature here. We talked about this work last year with the operator framework, and today we're not going to just show you today. We're not going to just show you open shift for we're going to show you operators running at scale operators that will do updates and patches for you, letting you focus more of your time and running your infrastructure and running running your business. We want to make all this easier and intuitive. So let's have a quick look at how we're doing. Just that >> painting. I know all of you have heard we're talking to pretend to new >> customers about the travel out. So new plan. Just open it up as a service been launched by this summer. Look, I know this is a big quest for not very big team. I'm open to any and all ideas. >> Please welcome back to the stage. Red Hat Global director of developer Experience burst Sutter with Jessica Forrester and Daniel McPherson. All right, we're ready to do some more now. Now. Earlier we showed you read Enterprise Clinic St running on lots of different hardware like this hardware you see right now And we're also running across multiple cloud providers. But now we're going to move to another world of Lennox Containers. This is where you see open shift four on how you can manage large clusters of applications from eggs limits containers across the hybrid cloud. We're going to see this is where suffer operators fundamentally empower human operators and especially make ups and Deb work efficiently, more efficiently and effectively there together than ever before. Rights. We have to focus on the stage right now. They're represent ops in death, and we're gonna go see how they reeled in application together. Okay, so let me introduce you to Dan. Dan is totally representing all our ops folks in the audience here today, and he's telling my ops, comfort person Let's go to call him Mr Ops. So Dan, >> thanks for with open before, we had a much easier time setting up in maintaining our clusters. In large part, that's because open shit for has extended management of the clusters down to the infrastructure, the diversity kinds of parent. When you take >> a look at the open ship console, >> you can now see the machines that make up the cluster where machine represents the infrastructure. Underneath that Cooper, Eddie's node open shit for now handles provisioning Andy provisioning of those machines. From there, you could dig into it open ship node and see how it's configured and monitor how it's behaving. So >> I'm curious, >> though it does this work on bare metal infrastructure as well as virtualized infrastructure. >> Yeah, that's right. Burn So Pa Journal nodes, no eternal machines and open shit for can now manage it all. Something else we found extremely useful about open ship for is that it now has the ability to update itself. We can see this cluster hasn't update available and at the press of a button. Upgrades are responsible for updating. The entire platform includes the nodes, the control plane and even the operating system and real core arrests. All of this is possible because the infrastructure components and their configuration is now controlled by technology called operators. Thes software operators are responsible for aligning the cluster to a desired state. And all of this makes operational management of unopened ship cluster much simpler than ever before. All right, I >> love the fact that all that's been on one console Now you can see the full stack right all way down to the bare metal right there in that one console. Fantastic. So I wanted to scare us for a moment, though. And now let's talk to Deva, right? So Jessica here represents our all our developers in the room as my facts. He manages a large team of developers here Red hat. But more importantly, she represents our vice president development and has a large team that she has to worry about on a regular basis of Jessica. What can you show us? We'LL burn My team has hundreds of developers and were constantly under pressure to deliver value to our business. And frankly, we can't really wait for Dan and his ops team to provisioned the infrastructure and the services that we need to do our job. So we've chosen open shift as our platform to run our applications on. But until recently, we really struggled to find a reliable source of Cooper Netease Technologies that have the operational characteristics that Dan's going to actually let us install through the cluster. But now, with operator, How bio, we're really seeing the V ecosystem be unlocked. And the technology's there. Things that my team needs, its databases and message cues tracing and monitoring. And these operators are actually responsible for complex applications like Prometheus here. Okay, they're written in a variety of languages, danceable, but that is awesome. So I do see a number of options there already, and preaches is a great example. But >> how do you >> know that one? These operators really is mature enough and robust enough for Dan and the outside of the house. Wilbert, Here we have the operator maturity model, and this is going to tell me and my team whether this particular operator is going to do a basic install if it's going to upgrade that application over time through different versions or all the way out to full auto pilot, where it's automatically scaling and tuning the application based on the current environment. And it's very cool. So coming over toothy open shift Consul, now we can actually see Dan has made the sequel server operator available to me and my team. That's the database that we're using. A sequel server. That's a great example. So cynics over running here in the cluster? But this is a great example for a developer. What if I want to create a new secret server instance? Sure, we're so it's as easy as provisioning any other service from the developer catalog. We come in and I can type for sequel server on what this is actually creating is, ah, native resource called Sequel Server, and you can think of that like a promise that a sequel server will get created. The operator is going to see that resource, install the application and then manage it over its life cycle, KAL, and from this install it operators view, I can see the operators running in my project and which resource is its managing Okay, but I'm >> kind of missing >> something here. I see this custom resource here, the sequel server. But where the community's resource is like pods. Yeah, I think it's cool that we get this native resource now called Sequel Server. But if I need to, I can still come in and see the native communities. Resource is like your staple set in service here. Okay, that is fantastic. Now, we did say earlier on, though, like many of our customers in the audience right now, you have a large team of engineers. Lost a large team of developers you gotta handle. You gotta have more than one secret server, right? We do one for every team as we're developing, and we use a lot of other technologies running on open shift as well, including Tomcat and our Jenkins pipelines and our dough js app that is gonna actually talk to that sequel server database. Okay, so this point we can kind of provisions, Some of these? Yes. Oh, since all of this is self service for me and my team's, I'm actually gonna go and create one of all of those things I just said on all of our projects, right Now, if you just give me a minute, Okay? Well, right. So basically, you're going to knock down No Jazz Jenkins sequel server. All right, now, that's like hundreds of bits of application level infrastructure right now. Live. So, Dan, are you not terrified? Well, I >> guess I should have done a little bit better >> job of managing guests this quota and historically just can. I might have had some conflict here because creating all these new applications would admit my team now had a massive back like tickets to work on. But now, because of software operators, my human operators were able to run our infrastructure at scale. So since I'm long into the cluster here as the cluster admin, I get this view of pods across all projects. And so I get an idea of what's happening across the entire cluster. And so I could see now we have four hundred ninety four pods already running, and there's a few more still starting up. And if I scroll to the list, we can see the different workloads Jessica just mentioned of Tomcats. And no Gs is And Jenkins is and and Siegel servers down here too, you know, I see continues >> creating and you have, like, close to five hundred pods running >> there. So, yeah, filters list down by secret server, so we could just see. Okay, But >> aren't you not >> running going around a cluster capacity at some point? >> Actually, yeah, we we definitely have a limited capacity in this cluster. And so, luckily, though, we already set up auto scale er's And so because the additional workload was launching, we see now those outer scholars have kicked in and some new machines are being created that don't yet have noticed. I'm because they're still starting up. And so there's another good view of this as well, so you can see machine sets. We have one machine set per availability zone, and you could see the each one is now scaling from ten to twelve machines. And the way they all those killers working is for each availability zone, they will. If capacities needed, they will add additional machines to that availability zone and then later effect fast. He's no longer needed. It will automatically take those machines away. >> That is incredible. So right now we're auto scaling across multiple available zones based on load. Okay, so looks like capacity planning and automation is fully, you know, handle this point. But I >> do have >> another question for year logged in. Is the cluster admin right now into the console? Can you show us your view of >> operator suffer operators? Actually, there's a couple of unique views here for operators, for Cluster admits. The first of those is operator Hub. This is where a cluster admin gets the ability to curate the experience of what operators are available to users of the cluster. And so obviously we already have the secret server operator installed, which which we've been using. The other unique view is operator management. This gives a cluster I've been the ability to maintain the operators they've already installed. And so if we dig in and see the secret server operator, well, see, we haven't set up for manual approval. And what that means is if a new update comes in for a single server, then a cluster and we would have the ability to approve or disapprove with that update before installs into the cluster, we'LL actually and there isn't upgrade that's available. Uh, I should probably wait to install this, though we're in the middle of scaling out this cluster. And I really don't want to disturb Jessica's application. Workflow. >> Yeah, so, actually, Dan, it's fine. My app is already up. It's running. Let me show it to you over here. So this is our products application that's talking to that sequel server instance. And for debugging purposes, we can see which version of sequel server we're currently talking to. Its two point two right now. And then which pod? Since this is a cluster, there's more than one secret server pod we could be connected to. Okay, I could see right there the bounder screeners they know to point to. That's the version we have right now. But, you know, >> this is kind of >> point of software operators at this point. So, you know, everyone in this room, you know, wants to see you hit that upgrade button. Let's do it. Live here on stage. Right, then. All >> right. All right. I could see where this is going. So whenever you updated operator, it's just like any other resource on communities. And so the first thing that happens is the operator pot itself gets updated so we actually see a new version of the operator is currently being created now, and what's that gets created, the overseer will be terminated. And that point, the new, softer operator will notice. It's now responsible for managing lots of existing Siegel servers already in the environment. And so it's then going Teo update each of those sickle servers to match to the new version of the single server operator and so we could see it's running. And so if we switch now to the all projects view and we filter that list down by sequel server, then we should be able to see us. So lots of these sickle servers are now being created and the old ones are being terminated. So is the rolling update across the cluster? Exactly a So the secret server operator Deploy single server and an H A configuration. And it's on ly updates a single instance of secret server at a time, which means single server always left in nature configuration, and Jessica doesn't really have to worry about downtime with their applications. >> Yeah, that's awesome dance. So glad the team doesn't have to worry about >> that anymore and just got I think enough of these might have run by Now, if you try your app again might be updated. >> Let's see Jessica's application up here. All right. On laptop three. >> Here we go. >> Fantastic. And yet look, we're We're into two before we're onto three. Now we're on to victory. Excellent on. >> You know, I actually works so well. I don't even see a reason for us to leave this on manual approval. So I'm going to switch this automatic approval. And then in the future, if a new single server comes in, then we don't have to do anything, and it'll be all automatically updated on the cluster. >> That is absolutely fantastic. And so I was glad you guys got a chance to see that rolling update across the cluster. That is so cool. The Secret Service database being automated and fully updated. That is fantastic. Alright, so I can see how a software operator doesn't able. You don't manage hundreds if not thousands of applications. I know a lot of folks or interest in the back in infrastructure. Could you give us an example of the infrastructure >> behind this console? Yeah, absolutely. So we all know that open shift is designed that run in lots of different environments. But our teams think that as your redhead over, Schiff provides one of the best experiences by deeply integrating the open chief Resource is into the azure console, and it's even integrated into the azure command line toll and the easy open ship man. And, as was announced yesterday, it's now available for everyone to try out. And there's actually one more thing we wanted to show Everyone related to open shit, for this is all so new with a penchant for which is we now have multi cluster management. This gives you the ability to keep track of all your open shift environments, regardless of where they're running as well as you can create new clusters from here. And I'll dig into the azure cluster that we were just taking a look at. >> Okay, but is this user and face something have to install them one of my existing clusters? >> No, actually, this is the host of service that's provided by Red hat is part of cloud that redhead that calm and so all you have to do is log in with your red hair credentials to get access. >> That is incredible. So one console, one user experience to see across the entire hybrid cloud we saw earlier with Red update. Right and red embers. Thank Satan. Now we see it for multi cluster management. But home shift so you can fundamentally see. Now the suffer operators do finally change the game when it comes to making human operators vastly more productive and, more importantly, making Devon ops work more efficiently together than ever before. So we saw the rich ice vehicle system of those software operators. We can manage them across the Khyber Cloud with any, um, shift instance. And more importantly, I want to say Dan and Jessica for helping us with this demonstration. Okay, fantastic stuff, guys. Thank you so much. Let's get Paul back out here >> once again. Thanks >> so much to burn his team. Jessica and Dan. So you've just seen how open shift operators can help you manage hundreds, even thousands of applications. Install, upgrade, remove nodes, control everything about your application environment, virtual physical, all the way out to the cloud making, making things happen when the business demands it even at scale, because that's where it's going to get. Our next guest has lots of experience with demand at scale. and they're using open source container management to do it. Their work, their their their work building a successful cloud, First platform and there, the twenty nineteen Innovation Award winner. >> Please welcome twenty nineteen Innovation Award winner. Cole's senior vice president of technology, Rich Hodak. >> How you doing? Thanks. >> Thanks so much for coming out. We really appreciate it. So I guess you guys set some big goals, too. So can you baby tell us about the bold goal? Helped you personally help set for Cole's. And what inspired you to take that on? Yes. So it was twenty seventeen and life was pretty good. I had no gray hair and our business was, well, our tech was working well, and but we knew we'd have to do better into the future if we wanted to compete. Retails being disrupted. Our customers are asking for new experiences, So we set out on a goal to become an open hybrid cloud platform, and we chose Red had to partner with us on a lot of that. We set off on a three year journey. We're currently in Year two, and so far all KP eyes are on track, so it's been a great journey thus far. That's awesome. That's awesome. So So you Obviously, Obviously you think open source is the way to do cloud computing. So way absolutely agree with you on that point. So So what? What is it that's convinced you even more along? Yeah, So I think first and foremost wait, do we have a lot of traditional IAS fees? But we found that the open source partners actually are outpacing them with innovation. So I think that's where it starts for us. Um, secondly, we think there's maybe some financial upside to going more open source. We think we can maybe take some cost out unwind from these big fellas were in and thirdly, a CZ. We go to universities. We started hearing. Is we interviewed? Hey, what is Cole's doing with open source and way? Wanted to use that as a lever to help recruit talent. So I'm kind of excited, you know, we partner with Red Hat on open shift in in Rail and Gloucester and active M Q and answerable and lots of things. But we've also now launched our first open source projects. So it's really great to see this journey. We've been on. That's awesome, Rich. So you're in. You're in a high touch beta with with open shift for So what? What features and components or capabilities are you most excited about and looking forward to what? The launch and you know, and what? You know what? What are the something maybe some new goals that you might be able to accomplish with with the new features. And yeah, So I will tell you we're off to a great start with open shift. We've been on the platform for over a year now. We want an innovation award. We have this great team of engineers out here that have done some outstanding work. But certainly there's room to continue to mature that platform. It calls, and we're excited about open shift, for I think there's probably three things that were really looking forward to. One is we're looking forward to, ah, better upgrade process. And I think we saw, you know, some of that in the last demo. So upgrades have been kind of painful up until now. So we think that that that will help us. Um, number two, A lot of our open shift workloads today or the workloads. We run an open shifts are the stateless apse. Right? And we're really looking forward to moving more of our state full lapse into the platform. And then thirdly, I think that we've done a great job of automating a lot of the day. One stuff, you know, the provisioning of, of things. There's great opportunity o out there to do mohr automation for day two things. So to integrate mohr with our messaging systems in our database systems and so forth. So we, uh we're excited. Teo, get on board with the version for wear too. So, you know, I hope you, Khun, we can help you get to the next goals and we're going to continue to do that. Thank you. Thank you so much rich, you know, all the way from from rail toe open shift. It's really exciting for us, frankly, to see our products helping you solve World War were problems. What's you know what? Which is. Really? Why way do this and and getting into both of our goals. So thank you. Thank you very much. And thanks for your support. We really appreciate it. Thanks. It has all been amazing so far and we're not done. A critical part of being successful in the hybrid cloud is being successful in your data center with your own infrastructure. We've been helping our customers do that in these environments. For almost twenty years now, we've been running the most complex work loads in the world. But you know, while the public cloud has opened up tremendous possibilities, it also brings in another type of another layer of infrastructure complexity. So what's our next goal? Extend your extend your data center all the way to the edge while being as effective as you have been over the last twenty twenty years, when it's all at your own fingertips. First from a practical sense, Enterprises air going to have to have their own data centers in their own environment for a very long time. But there are advantages of being able to manage your own infrastructure that expand even beyond the public cloud all the way out to the edge. In fact, we talked about that very early on how technology advances in computer networking is storage are changing the physical boundaries of the data center every single day. The need, the need to process data at the source is becoming more and more critical. New use cases Air coming up every day. Self driving cars need to make the decisions on the fly. In the car factory processes are using a I need to adapt in real time. The factory floor has become the new edge of the data center, working with things like video analysis of a of A car's paint job as it comes off the line, where a massive amount of data is on ly needed for seconds in order to make critical decisions in real time. If we had to wait for the video to go up to the cloud and back, it would be too late. The damage would have already been done. The enterprise is being stretched to be able to process on site, whether it's in a car, a factory, a store or in eight or nine PM, usually involving massive amounts of data that just can't easily be moved. Just like these use cases couldn't be solved in private cloud alone because of things like blatant see on data movement, toe address, real time and requirements. They also can't be solved in public cloud alone. This is why open hybrid is really the model that's needed in the only model forward. So how do you address this class of workload that requires all of the above running at the edge? With the latest technology all its scale, let me give you a bit of a preview of what we're working on. We are taking our open hybrid cloud technologies to the edge, Integrated with integrated with Aro AM Hardware Partners. This is a preview of a solution that will contain red had open shift self storage in K V M virtual ization with Red Hat Enterprise Lennox at the core, all running on pre configured hardware. The first hardware out of the out of the gate will be with our long time. Oh, am partner Del Technologies. So let's bring back burn the team to see what's right around the corner. >> Please welcome back to the stage. Red Hat. Global director of developer Experience burst Sutter with Kareema Sharma. Okay, We just how was your Foreign operators have redefined the capabilities and usability of the open hybrid cloud, and now we're going to show you a few more things. Okay, so just be ready for that. But I know many of our customers in this audience right now, as well as the customers who aren't even here today. You're running tens of thousands of applications on open chef clusters. We know that disappearing right now, but we also know that >> you're not >> actually in the business of running terminators clusters. You're in the business of oil and gas from the business retail. You're in a business transportation, you're in some other business and you don't really want to manage those things at all. We also know though you have lo latest requirements like Polish is talking about. And you also dated gravity concerns where you >> need to keep >> that on your premises. So what you're about to see right now in this demonstration is where we've taken open ship for and made a bare metal cluster right here on this stage. This is a fully automated platform. There is no underlying hyper visor below this platform. It's open ship running on bare metal. And this is your crew vanities. Native infrastructure, where we brought together via mes containers networking and storage with me right now is green mush arma. She's one of her engineering leaders responsible for infrastructure technologies. Please welcome to the stage, Karima. >> Thank you. My pleasure to be here, whether it had summit. So let's start a cloud. Rid her dot com and here we can see the classroom Dannon Jessica working on just a few moments ago From here we have a bird's eye view ofthe all of our open ship plasters across the hybrid cloud from multiple cloud providers to on premises and noticed the spare medal last year. Well, that's the one that my team built right here on this stage. So let's go ahead and open the admin console for that last year. Now, in this demo, we'LL take a look at three things. A multi plaster inventory for the open Harbor cloud at cloud redhead dot com. Second open shift container storage, providing convert storage for virtual machines and containers and the same functionality for cloud vert and bare metal. And third, everything we see here is scuba unit is native, so by plugging directly into communities, orchestration begin common storage. Let working on monitoring facilities now. Last year, we saw how continue native actualization and Q Bert allow you to run virtual machines on Cabinet is an open shift, allowing for a single converge platform to manage both containers and virtual machines. So here I have this dark net project now from last year behead of induced virtual machine running it S P darknet application, and we had started to modernize and continue. Arise it by moving. Parts of the application from the windows began to the next containers. So let's take a look at it here. I have it again. >> Oh, large shirt, you windows. Earlier on, I was playing this game back stage, so it's just playing a little solitaire. Sorry about that. >> So we don't really have time for that right now. Birds. But as I was saying, Over here, I have Visions Studio Now the window's virtual machine is just another container and open shift and the i d be service for the virtual machine. It's just another service in open shift open shifts. Running both containers and virtual machines together opens a whole new world of possibilities. But why stop there? So this here be broadened to come in. It is native infrastructure as our vision to redefine the operation's off on premises infrastructure, and this applies to all matters of workloads. Using open shift on metal running all the way from the data center to the edge. No by your desk, right to main benefits. Want to help reduce the operation casts And second, to help bring advance good when it is orchestration concept to your infrastructure. So next, let's take a look at storage. So open shift container storage is software defined storage, providing the same functionality for both the public and the private lads. By leveraging the operator framework, open shift container storage automatically detects the available hardware configuration to utilize the discs in the most optimal vein. So then adding my note, you don't have to think about how to balance the storage. Storage is just another service running an open shift. >> And I really love this dashboard quite honestly, because I love seeing all the storage right here. So I'm kind of curious, though. Karima. What kind of storage would you What, What kind of applications would you use with the storage? >> Yeah, so this is the persistent storage. To be used by a database is your files and any data from applications such as a Magic Africa. Now the A Patrick after operator uses school, been at this for scheduling and high availability, and it uses open shift containers. Shortest. Restore the messages now Here are on premises. System is running a caf co workload streaming sensor data on DH. We want toe sort it and act on it locally, right In a minute. A place where maybe we need low latency or maybe in a data lake like situation. So we don't want to send the starter to the cloud. Instead, we want to act on it locally, right? Let's look at the griffon a dashboard and see how our system is doing so with the incoming message rate of about four hundred messages for second, the system seems to be performing well, right? I want to emphasize this is a fully integrated system. We're doing the testing An optimization sze so that the system can Artoo tune itself based on the applications. >> Okay, I love the automated operations. Now I am a curious because I know other folks in the audience want to know this too. What? Can you tell us more about how there's truly integrated communities can give us an example of that? >> Yes. Again, You know, I want to emphasize everything here is managed poorly by communities on open shift. Right. So you can really use the latest coolest to manage them. All right. Next, let's take a look at how easy it is to use K native with azure functions to script alive Reaction to a live migration event. >> Okay, Native is a great example. If actually were part of my breakout session yesterday, you saw me demonstrate came native. And actually, if you want to get hands on with it tonight, you can come to our guru night at five PM and actually get hands on like a native. So I really have enjoyed using K. Dated myself as a software developer. And but I am curious about the azure functions component. >> Yeah, so as your functions is a function is a service engine developed by Microsoft fully open source, and it runs on top of communities. So it works really well with our on premises open shift here. Right now, I have a simple azure function that I already have here and this azure function, you know, Let's see if this will send out a tweet every time we live My greater Windows virtual machine. Right. So I have it integrated with open shift on DH. Let's move a note to maintenance to see what happens. So >> basically has that via moves. We're going to see the event triggered. They trigger the function. >> Yeah, important point I want to make again here. Windows virtue in machines are equal citizens inside of open shift. We're investing heavily in automation through the use of the operator framework and also providing integration with the hardware. Right, So next, Now let's move that note to maintain it. >> But let's be very clear here. I wanna make sure you understand one thing, and that is there is no underlying virtual ization software here. This is open ship running on bear. Meddle with these bare metal host. >> That is absolutely right. The system can automatically discover the bare metal hosts. All right, so here, let's move this note to maintenance. So I start them Internets now. But what will happen at this point is storage will heal itself, and communities will bring back the same level of service for the CAFTA application by launching a part on another note and the virtual machine belive my great right and this will create communities events. So we can see. You know, the events in the event stream changes have started to happen. And as a result of this migration, the key native function will send out a tweet to confirm that could win. It is native infrastructure has indeed done the migration for the live Ian. Right? >> See the events rolling through right there? >> Yeah. All right. And if we go to Twitter? >> All right, we got tweets. Fantastic. >> And here we can see the source Nord report. Migration has succeeded. It's a pretty cool stuff right here. No. So we want to bring you a cloud like experience, but this means is we're making operational ease a fuse as a top goal. We're investing heavily in encapsulating management knowledge and working to pre certify hardware configuration in working with their partners such as Dell, and they're dead already. Note program so that we can provide you guidance on specific benchmarks for specific work loads on our auto tuning system. >> All right, well, this is tow. I know right now, you're right thing, and I want to jump on the stage and check out the spare metal cluster. But you should not right. Wait After the keynote didn't. Come on, check it out. But also, I want you to go out there and think about visiting our partner Del and their booth where they have one. These clusters also. Okay, So this is where vmc networking and containers the storage all come together And a Kurban in his native infrastructure. You've seen right here on this stage, but an agreement. You have a bit more. >> Yes. So this is literally the cloud coming down from the heavens to us. >> Okay? Right here, Right now. >> Right here, right now. So, to close the loop, you can have your plaster connected to cloud redhead dot com for our insights inside reliability engineering services so that we can proactively provide you with the guidance through automated analyses of telemetry in logs and help flag a problem even before you notice you have it Beat software, hardware, performance, our security. And one more thing. I want to congratulate the engineers behind the school technology. >> Absolutely. There's a lot of engineers here that worked on this cluster and worked on the stack. Absolutely. Thank you. Really awesome stuff. And again do go check out our partner Dale. They're just out that door I can see them from here. They have one. These clusters get a chance to talk to them about how to run your open shift for on a bare metal cluster as well. Right, Kareema, Thank you so much. That was totally awesome. We're at a time, and we got to turn this back over to Paul. >> Thank you. Right. >> Okay. Okay. Thanks >> again. Burned, Kareema. Awesome. You know, So even with all the exciting capabilities that you're seeing, I want to take a moment to go back to the to the first platform tenant that we learned with rail, that the platform has to be developer friendly. Our next guest knows something about connecting a technology like open shift to their developers and part of their company. Wide transformation and their ability to shift the business that helped them helped them make take advantage of the innovation. Their Innovation award winner this year. Please, Let's welcome Ed to the stage. >> Please welcome. Twenty nineteen. Innovation Award winner. BP Vice President, Digital transformation. Ed Alford. >> Thanks, Ed. How your fake Good. So was full. Get right into it. What we go you guys trying to accomplish at BP and and How is the goal really important in mandatory within your organization? Support on everyone else were global energy >> business, with operations and over seventy countries. Andi. We've embraced what we call the jewel challenge, which is increasing the mind for energy that we have as individuals in the world. But we need to produce the energy with fuel emissions. It's part of that. One of our strategic priorities that we >> have is to modernize the whole group on. That means simplifying our processes and enhancing >> productivity through digital solutions. So we're using chlo based technologies >> on, more importantly, open source technologies to clear a community and say, the whole group that collaborates effectively and efficiently and uses our data and expertise to embrace the jewel challenge and actually try and help solve that problem. That's great. So So how did these heart of these new ways of working benefit your team and really the entire organ, maybe even the company as a whole? So we've been given the Innovation Award for Digital conveyor both in the way it was created and also in water is delivering a couple of guys in the audience poll costal and brewskies as he they they're in the team. Their teams developed that convey here, using our jail and Dev ops and some things. We talk about this stuff a lot, but actually the they did it in a truly our jail and develops we, um that enabled them to experiment and walking with different ways. And highlight in the skill set is that we, as a group required in order to transform using these approaches, we can no move things from ideation to scale and weeks and days sometimes rather than months. Andi, I think that if we can take what they've done on DH, use more open source technology, we contain that technology and apply across the whole group to tackle this Jill challenge. And I think that we use technologists and it's really cool. I think that we can no use technology and open source technology to solve some of these big challenges that we have and actually just preserve the planet in a better way. So So what's the next step for you guys at BP? So moving forward, we we are embracing ourselves, bracing a clothed, forced organization. We need to continue to live to deliver on our strategy, build >> over the technology across the entire group to address the jewel >> challenge and continue to make some of these bold changes and actually get into and really use. Our technology is, I said, too addresses you'LL challenge and make the future of our planet a better place for ourselves and our children and our children's children. That's that's a big goal. But thank you so much, Ed. Thanks for your support. And thanks for coming today. Thank you very much. Thank you. Now comes the part that, frankly, I think his best part of the best part of this presentation We're going to meet the type of person that makes all of these things a reality. This tip this type of person typically works for one of our customers or with one of with one of our customers as a partner to help them make the kinds of bold goals like you've heard about today and the ones you'll hear about Maura the way more in the >> week. I think the thing I like most about it is you feel that reward Just helping people I mean and helping people with stuff you enjoy right with computers. My dad was the math and science teacher at the local high school. And so in the early eighties, that kind of met here, the default person. So he's always bringing in a computer stuff, and I started a pretty young age. What Jason's been able to do here is Mohr evangelize a lot of the technologies between different teams. I think a lot of it comes from the training and his certifications that he's got. He's always concerned about their experience, how easy it is for them to get applications written, how easy it is for them to get them up and running at the end of the day. We're a loan company, you know. That's way we lean on accounting like red. That's where we get our support front. That's why we decided to go with a product like open shift. I really, really like to product. So I went down. The certification are out in the training ground to learn more about open shit itself. So my daughter's teacher, they were doing a day of coding, and so they asked me if I wanted to come and talk about what I do and then spend the day helping the kids do their coding class. The people that we have on our teams, like Jason, are what make us better than our competitors, right? Anybody could buy something off the shelf. It's people like him. They're able to take that and mold it into something that then it is a great offering for our partners and for >> customers. Please welcome Red Hat Certified Professional of the Year Jason Hyatt. >> Jason, Congratulations. Congratulations. What a what a big day, huh? What a really big day. You know, it's great. It's great to see such work, You know that you've done here. But you know what's really great and shows out in your video It's really especially rewarding. Tow us. And I'm sure to you as well to see how skills can open doors for for one for young women, like your daughters who already loves technology. So I'd liketo I'd like to present this to you right now. Take congratulations. Congratulations. Good. And we I know you're going to bring this passion. I know you bring this in, everything you do. So >> it's this Congratulations again. Thanks, Paul. It's been really exciting, and I was really excited to bring my family here to show the experience. It's it's >> really great. It's really great to see him all here as well going. Maybe we could you could You guys could stand up. So before we leave before we leave the stage, you know, I just wanted to ask, What's the most important skill that you'LL pass on from all your training to the future generations? >> So I think the most important thing is you have to be a continuous learner you can't really settle for. Ah, you can't be comfortable on learning, which I already know. You have to really drive a continuous Lerner. And of course, you got to use the I ninety. Maxwell. Quite. >> I don't even have to ask you the question. Of course. Right. Of course. That's awesome. That's awesome. And thank you. Thank you for everything, for everything that you're doing. So thanks again. Thank you. You know what makes open source work is passion and people that apply those considerable talents that passion like Jason here to making it worked and to contribute their idea there. There's back. And believe me, it's really an impressive group of people. You know you're family and especially Berkeley in the video. I hope you know that the redhead, the certified of the year is the best of the best. The cream of the crop and your dad is the best of the best of that. So you should be very, very happy for that. I also and I also can't wait. Teo, I also can't wait to come back here on this stage ten years from now and present that same award to you. Berkeley. So great. You should be proud. You know, everything you've heard about today is just a small representation of what's ahead of us. We've had us. We've had a set of goals and realize some bold goals over the last number of years that have gotten us to where we are today. Just to recap those bold goals First bait build a company based solely on open source software. It seems so logical now, but it had never been done before. Next building the operating system of the future that's going to run in power. The enterprise making the standard base platform in the op in the Enterprise Olympics based operating system. And after that making hybrid cloud the architecture of the future make hybrid the new data center, all leading to the largest software acquisition in history. Think about it around us around a company with one hundred percent open source DNA without. Throughout. Despite all the fun we encountered over those last seventeen years, I have to ask, Is there really any question that open source has won? Realizing our bold goals and changing the way software is developed in the commercial world was what we set out to do from the first day in the Red Hat was born. But we only got to that goal because of you. Many of you contributors, many of you knew toe open source software and willing to take the risk along side of us and many of partners on that journey, both inside and outside of Red Hat. Going forward with the reach of IBM, Red hat will accelerate. Even Mohr. This will bring open source general innovation to the next generation hybrid data center, continuing on our original mission and goal to bring open source technology toe every corner of the planet. What I what I just went through in the last hour Soul, while mind boggling to many of us in the room who have had a front row seat to this overto last seventeen plus years has only been red hats. First step. Think about it. We have brought open source development from a niche player to the dominant development model in software and beyond. Open Source is now the cornerstone of the multi billion dollar enterprise software world and even the next generation hybrid act. Architecture would not even be possible without Lennox at the core in the open innovation that it feeds to build around it. This is not just a step forward for software. It's a huge leap in the technology world beyond even what the original pioneers of open source ever could have imagined. We have. We have witnessed open source accomplished in the last seventeen years more than what most people will see in their career. Or maybe even a lifetime open source has forever changed the boundaries of what will be possible in technology in the future. And in the one last thing to say, it's everybody in this room and beyond. Everyone outside continue the mission. Thanks have a great sum. It's great to see it