>>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 and cube coverage here with matt Hicks. Executive vice president of products and technologies at red hat cuba lum I've been on many times, knows the engineering side now running all the process of technologies matt. Great to see you. Thanks for coming on remote. I wish we were in real real life in person. I RL but doing it remote again. Thanks for coming on. >>Hey, thanks thanks for having me today. >>Hey, so what a year you know, um, I was just talking to a friend and another interview with the red hat colleagues. Chef on your team in 2019 I interviewed Arvin at IBM right before he bought red hat and you smile on his face and he wasn't even ceo then um, he is such a big fan of cloud native and you guys have been the engine underneath the hood if you will of IBM this transformation huge push now and with Covid and now with the visibility of the post Covid, you're seeing cloud Native at scale with modern applications just highly accelerated across the board In almost every industry, every vertical. This is a very key trend. You guys at the, at the center of it always have been, we've been covering you for many years, interesting time and so now you guys are really got the, got the formula at red hat, take us through the key transit you see on this wave for enterprises and how is red hat taking that, taking that through? >>Yeah, no, absolutely. It has been, it's been a great ride actually. I remember a couple years ago standing on stage with Arvin prior to the acquisition. So it's been uh, it's been a world one but I think if we look at Really would emerge in 2020, we've seen three trends that we hope we're gonna carry through in 2021 just in a better and better year for that. That the first is open hybrid cloud is really how customers are looking to adapt to change. They have to use what they have um assets they have today. On premise, we're seeing a lot of public cloud adoption that blend of being hybrid is just, it is a reality for how customers are having to deliver a edge computing I think is another area I would say uh the trend is really not going to be a fad or a new, you know, great texture. Um the capabilities of computing at the edge, whether that is automotive vehicles, radio access network capabilities to five G. It's pretty astounding at this point. So I think we're gonna see a lot of pushing edge computing for computing, getting closer to users. Uh but then also the choice aspect we're seeing with Ceos, we often talk about technology is choice, but I think the model of how they want to consume technology has been another really strong trend in 2020. Uh We look at this really is being able to deliver a cloud managed services in addition to technology that ceos around themselves. But those, those will probably be the three that stand out to me at least in 2020 we've seen, >>so matt take us through in your minds and red hats, perspective the workloads that are going to be highlighted in this cloud native surge that's happening. We're seeing it everywhere. You mentioned edge industrial edge to consumer Edge to lightweight, edge, massive new workloads. So take us through how you see kind of the existing workloads evolving and potentially new workloads that emerging. >>Yeah. So I think um you know first when you talk about edge workloads a big umbrella but if you look at data driven workloads, especially in the machine learning artificial intelligence spectrum of that, that's really critical. And a reason that those workloads are important is five G. Aside for now when you're running something at the edge you have to also be able to make decisions pretty well at the edge. And that that is that's where your data is being generated and the ability to act on that closely. Whether that's executing machine learning models or being able to do more than that with A I. That's going to be a really really critical workload. Uh huh. Coupled to that, we will see I think five G. Change that because you're going to see more blending in terms of what can you draw back to uh closer to your data center to augment that. So five G will shift how that's built but data driven workloads are going to be huge then I think another area will see is how you propagate that data through environment. Some Kafka has been a really popular technology will actually be launching a service in relation to that. But being able to get that data at the edge and bring it back to locations where you might do more traditional processing, that's going to be another really key space. Um and then we'll still have to be honest, there is still a tremendous amount of work loads out there that just aren't going to get rebuilt. And So being able to figure out how can you make them a little more cloud native? You know, the things your companies have run on for the last 20 years, being able to step them closer to cloud native, I think it's going to be another critical focus because he can't just rewrite them all in one phase and you can't leave them there as well. So being able to bridge shadow B T to >>what's interesting if folks following red hat, No, no, you guys certainly at the tech chops you guys have great product engineering staff been doing this for a long time. I mean the common Lennox platform that even the new generation probably have to leave it load limits on the server anymore. You guys have been doing this hybrid environment in I T for I T Sloan for decades. Okay. In the open, so, you know, it's servers, virtualization, you know, private, public cloud infrastructures and it's been around, we've been covering it in depth as you know, but that's been, that's a history. But as you go from a common Lennox platform into things with kubernetes as new technologies and this new abstraction layers, new control plane concept comes to the table. This need for a fully open platform seems to be a hot trend this year. >>How do you >>describe that? Can you take a minute to explain what this is, this is all about this new abstraction, this new control plane or this open hybrid cloud as you're calling? What is this about? What does it mean? >>Yeah, no, I'll do a little journey that she talked about. Yeah. This has been our approach for almost a decade at this point. And it started, if you look at our approach with Lennox and this was before public clouds use migrants existed. We still with Lennox tried to span bare metal and virtualized environments and then eventually private and public cloud infrastructure as well. And our goal there was you want to be able to invest in something, um, and in our world that's something that's also open as in Lennox but be able to run it anywhere. That's expanded quite a bit. That was good for a class of applications that really got it started. That's expanded now to kubernetes, for example, kubernetes is taking that from single machines to cluster wide deployments and it's really giving you that secure, flexible, fast innovation backbone for cloud native computing. And the balance there is just not for cloud native, we've got to be able to run traditional emerging workloads and our goal is let those things run wherever rail can. So you're really, you're based on open technologies, you can run them wherever you have resources to run. And then I think the third part of this for us is uh, having that choice and ability to run anywhere but not being able to manage. It can lead to chaos or sprawl and so our investments in our management portfolio and this is from insights the redhead advanced cluster management to our cluster security capabilities or answerable. Our focus has been securing, managing and monitoring those environments so you can have a lot of them, you can run where you want, but she just sort of treat it as one thing. So you are our vision, how we've executed up to this point has really been centered around that. I think going forward where you'll see us um really try to focus is, you know, first you heard paul announced earlier that we're donating more than half a billion dollars to open. I would cloud research and part of this reason is uh running services. Cloud native services is changing. And that research element of open source is incredibly powerful. We want to make sure that's continuing but we're also going to evolve our portfolio to support this same drive a couple areas. I would call out, we're launching redhead open shift platform plus and I talked about that combination from rail to open shift to being able to manage it. We're really putting that in one package. So you have the advanced management. So if you have a huge suites of cloud native real estate there, you can manage that. And it also pushes security earlier into the application, build workflows. This is tied to some of our technology is bolstered by the stack rocks acquisition that we did. Being able to bring that in one product offering I think is really key to address security and management side. Uh we've also expanded Redhead insights beyond Rehl to include open shift and answerable and this is really targeted it. How do we make this easier? How do we let customers lean on our expertise? Not just for Lennox as a service, but expand that to all of the things you'll use in a hybrid cloud. And then of course we're going to keep pushing Lennox innovation, you'll see this with the latest version of red hat enterprise, like so we're gonna push barriers, lower barriers to entry. Uh But we're also going to be the innovation catalyst for new directions include things like edge computing. So hopefully that sort of helps in terms of where, where we started when it was just Lennox and then all the other pieces were bringing to the table and why and some new areas. Uh We're launching our investment going forward. >>Yeah, great, that's great overview. Thanks for taking the time to do that. I think one of the areas I that's jumping out at me is the uh, advanced cluster management work you guys are doing saw that with the security peace and also red hat insights I think is is another key one and you get to read that edge. But on the inside you mentioned at the top of this interview, data workloads pretty much being, I mean that pretty much everything, much more of an emphasis on data. Um, data in general but also, you know, serve abilities a hot area. You know, you guys run operating system so you know, in operating systems you need to have the data, understand what's being instrumented. You gotta know that you've got to have things instrument and now more than ever having the data is critical. So take us through your vision of insights and how that translates. Because he said mentions in answerable you're seeing a lot more innovations because Okay I got provisions everything that's great. Cloud and hybrid clouds. Good. Okay thumbs up everyone check the box and then all of a sudden day too As they call day two operations stuff starts to, you know, Get getting hairy, they start to break. Maybe some things are happening. So day two is essentially the ongoing operational stability of cloud native. You need insights, you need the data. If you don't have the data, you don't even know what's going on. You can't apply machine learning. It's kind of you if you don't get that flywheel going, you could be in trouble. Take me through your vision of data driven insights. >>Yeah. So I think it's it's two aspects. If you go to these traditional traditional sport models, we don't have a lot of insight until there's an issue and I'm always amazed by what our teams can understand fix, get customers through those and I think that's a lot of the success red hats had at the same note, we want to make that better where if you look at real as an example, if we fixed an issue for any customer on the planet of which we fix a lot in the support area, we can know whether you're going to hit that same issue or not in a lot of cases and so that linkage to be able to understand environments better. We can be very proactive of not just hey apply all the updates but without this one update, you risk a kernel panic, we know your environment, we see it, this is going to keep you out of that area. The second challenge with this is when things go do break or um are failing the ability to get that data. We want that to be the cleanest handshake possible. We don't want to. Those are always stressful times anyway for customers being able to get logs, get access so that our engineering knowledge, we can fix it. That's another key part. Uh when you extend this to environments like open shift things are changing faster than humans can respond in it. And so those traditional flows can really start to get strained or broken broken down with it. So when we have connected open shift clusters, our engineering teams can not only proactively monitor those because we know cooper net is really well. We understand operators really well. Uh we can get ahead of those issues and then use our support teams and capabilities to keep things from breaking. That's really our goals. Finding that balance where uh we're using our expertise in building the software to help customers stay stable instead of just being in a response mode when things break >>awesome. I think it's totally right on the money and data is critical in all this. I think the trust of having that partnership to know that this pattern recognition is gonna be applied from the environment and that's been hurting the cybersecurity market people. That's the biggest discussion I had with my friends and cyber is they don't share the data when they do, things are pretty obvious. Um, so that's good stuff there and then obviously notifications proactive before there's a cause or failure. Uh great stuff. This brings up a point that paul come here, said earlier, I want to get your reaction to this. He said every C. I. O. Is now a cloud operator. >>That's a pretty bold >>statement. I mean, that's simply means that it's all cloud all the time. You know? Again, we've been saying this on the queue for many years, cloud first, whatever people want to call it, >>what does that actually >>mean? Cloud operator, does that just mean everything's hybrid? Everything's multiple. Cloud. Take me through an unpacked what that actually means? >>Yeah. So I think for the C I O for a lot of times it was largely a technology choice. So that was sort of a choice available to them. And especially if you look at what public clouds have introduced, it's not just technology choice. You're not just picking Kafka anymore. For example, you really get to make the choice of do I want to differentiate my business by running it myself or is this just technology I want to consume and I'm going to consume a cloud, native service and other challenges come with that. It's an infrastructure, not in your control, but when you think about a ceo of the the axes they're making decisions on, there are more capabilities now and I think this is really crucial to let the C i O hone in on where they want to specialist, what do they want to consume, what do they really want to understand, differentiate and Ron? Um and to support this actually, so we're in this vein, we're going to be launching three new managed cloud services and our our focus is always going to be hybrid in these uh but we understand the importance of having managed cloud services that red hat is running not the customers in this case. So one of those will be red hat open shift streams for Patrick Kafka. We've talked about that, that data connectivity and the importance of it and really being able to connect apps across clouds across data centers using Kafka without having to push developers to really specialize in running. It is critical because that is your hybrid data, it's going to be generated on prim, it's going to be generated the edge, you need to be able to get access to it. The next challenge for us is once you have that data, what do you do with it? And we're launching a red hat open shift data science cloud service and this is going to be optimized for understanding the data that's brought in by streams. This doesn't matter whether it's an Ai service or business intelligence process and in this case you're going to see us leverage our ecosystem quite a bit because that last mile of AI workloads or models will often be completed with partners. But this is a really foundational service for us to get data in and then bring that into a workflow where you can understand it and then the last one for us is that red hat open shift api management and you can think of this is really the overseer of how apps are going to talk to services and these environments are complex, their dynamic and being able to provide that oversight up. How should my apps be consuming all these a. P. S, how should they be talking? How do I want to control? Um and understand that is really critical. So we're launching these, these three and it fits in that cloud operator use, we want to give three options where you might want to use Kafka and three Scale technologies and open data hub, which was the basis of open shift data sides, but you might not want to specialize in running them so we can run those for you and give you as a C. I. O. That choice of where you want to invest in running versus just using it. >>All right, we're here with matt Hicks whose executive vice president prospect technology at red hat, matt, your leader at red hat now part of IBM and continues to operate um in the red hat spirit, uh innovating out in the open, people are wearing their red hat uh hoodies, which has been great to see. Um I ask every executive this question because I really want to get the industry perspective on this. Um you know, necessity is the mother of invention as the saying goes and, you know, this pandemic was a challenge for many In 2020. And then as we're in 2021, some say that even in the fall we're gonna start to see a light at the end of the tunnel and then maybe back to real life in 2022. This has opened up huge visibility for CSOS and leaders and business in the enterprise to say, Hey, what's working, what do we need? We didn't prepare for everyone to be working at home. These were great challenges in 2020. Um, and and these will fuel the next innovations and achievements going forward. Um again necessity is the mother of all invention. Some projects are gonna be renewed and double down on some probably won't be as hybrid clouds and as open source continues to power through this, there's lessons to be learned, share your view on what um leaders in in business can do coming out of the pandemic to have a growth strategy and what can we learn from this pandemic from innovation and and how open source can power through this adversity. >>Yeah. You know, I think For as many challenging events we had in 2020, I think for myself at least, it it also made me realize what companies including ourselves can accomplish if we're really focused on that if we don't constrain our thinking too much, we saw projects that were supposed to take customers 18 months that they were finishing in weeks on it because that was what was required to survive. So I think part of it is um, 2020 broke a lot of complacency for us. We have to innovate to be able to put ourselves in a growth position. I hope that carries into 2021 that drives that urgency. When we look at open source technologies. I think the flexibility that it provides has been something that a lot of companies have needed in this. And that's whether it could be they're having to contract or expand and really having that moment of did the architectural choices, technology choices, will they let me respond in the way I need? Uh, I'm biased. But first I think open models, open source development Is the best basis to build. That gives you that flexibility. Um, and honestly, I am an optimist, but I look at 2021, I'm like, I'm excited to see what customers build on sort of the next wave of open innovation. I think his life sort of gets back to normal and we keep that driving innovation and people are able to collaborate more. I hope we'll see a explosion of innovation that comes out and I hope customers see the benefit of doing that on a open hybrid cloud model. >>No better time now than before. All the things are really kind of teed up and lined up to provide that innovation. Uh, great to have you on the cube. Take a quick second to explain to the folks watching in the community What is red hat 2021 about this year? And red hat someone, I'll see. We're virtual and we're gonna be back in a real life soon for the next event. What's the big takeaway this year for the red hat community and the community at large for red hat in context of the market? >>You know, I think redhead, you'll keep seeing us push open source based innovation. There's some really exciting spaces, whether that is getting closer and closer towards edge, which opens up incredible opportunities or providing that choice, even down to consumption model like cloud managed services. And it's in that drive to let customers have the tools to build the next incredible innovations for him. So, And that's what summit 2021 is going to be about for us, >>awesome And congratulations to, to the entire team for the donation to the academic community, Open cloud initiative. And these things are doing to promote this next generation of SRS and large cloud scale operators and developers. So congratulations on that props. >>Thanks john. >>Okay. Matt Hicks, executive vice president of products and technology. That red hat here on the Cube Cube coverage of red hat 2021 virtual. I'm John Ferrier. Thanks for watching. Yeah.

>> From around the globe, it's The Cube, with digital coverage of Red Hat Summit 2020, brought to you by Red Hat. >> Hi, and welcome back, I'm Stu Miniman, this is The Cube's coverage of the Red Hat 2020, bringing you guests from Red Hat and their partner ecosystem, practitioners, where they are around the globe, bringing to them this digital event, and while we wish we could all be together in person, we'll just be together apart for 2020. Happy to welcome to the program, a longtime Red Hatter, but first time, on The Cube, Rich Sharples, who's the senior director of product management inside Red Hat, Rich, thank you so much for joining us. >> Yeah, thanks for the invitation, great to be here. >> All right, so the topic we're going to talk about today is something you've got a long background of the middleware space. But in, Quarkus so, I personally was not familiar with Quarkus. Obviously we know, god, I believe someone told me once that there's like, 2 million open source projects out there, so I believe I can be forgiven for not having every one of them memorized there, but of course anybody in our community is going to know Java. What a huge impact that has had on the industry. Linux and Java are two of the, you know, major movers of how we, you know, build an, you know, deal with application today, so give us a little bit of a framework as to what Quarkus is, you know, why it was created. >> Yeah, so it's no secret that as organizations and developers move to this kind of new styled cloud native development, developing applications running in containers or in a kind of serverless environment that Java is not necessarily the best fit. Java does many incredible things, it's an amazing field of engineering. But many of the coolest things it does, assumes that it's going to be a long running application, it can do this cool dynamic class loading and dynamic optimization as the application runs. Those things are pretty impressive, but they're also fairly, very heavyweight. And in our kind of ephemeral environments, whether containers or functions of service, you don't have long running applications. And you can't make use of those things, so in a Java environment you pay for those radical features that you don't necessarily get any benefit from them. So, you know, where we're really trying to lay focus is ensure developers to continue to use Quarkus, it's still the, you know, the dominant language for enterprise development. You still get the benefits of these new architectures, so ensuring that Java continues to be you know, performant and efficient in these new you know, constrained environments. >> Okay, excellent, so we're not calling it cloud native Java though, right Rich? But we are bringing, if I heard right, Java for things like containers Kubernetes, I even heard functions as a service so, we're talking to server lists of you know, open shift server lists something that's being talked about this week. So help us understand you know, if Java was long in the tooth. You know, what stays the same, what's different, how have people been managing and you know building applications in this environment, because obviously you know, we've been dealing with containers for a number of years now, so what have they been doing so far and, you know, why is Quarkus different from some of the alternatives that are out there. >> Really, the goal is to introduce those that stayed the same. It's not a different language, it's not a fork. It is Java, you're writing Java applications, essentially in the same way you used to write them. And you may be using Microsoft still functions so slight difference in terms of design, but it's, you know, we want to ensure that you can bring your favorite frameworks and wipers with you as well. When you're accessing databases or message brokers. We want to ensure you can still use those technologies so we're trying to bring the whole ecosystem with us, with Quarkus, so those things can run well, in a you know, container or service environment as well. And that's super important because the real benefit here is any organizations face the choice of I want to develop cloud native, I want to develop functions, but I've got this huge investment in Java in terms of skills and you know, tools and tool trains and I don't want to go learn a new language, just because I need to you know, take advantage of things new environments so we're essentially giving developers their cake and allowing them to eat it. We are trying to provide the best of both worlds. Stick with the language you already know and you know, have lots of experience with, and still be able to get the benefits of running in our containerized environment. >> Okay. what are some of the challenges here, so you know from an infrastructure standpoint. My background is, you know, virtualization broke a lot of pieces and containerization does the same thing. As you mentioned, things you know, spin up really fast and they don't stay on nearly as long. You know, god, you mentioned functions as a service, often we're measuring things in milliseconds, so everything genomes, understand what's up how do I manage it, how do I monitor it all of those pieces so, you know, I understand you're saying we take the skill set and what we know. But, you know, there's got to be some on ramp here and some considerations >> Yes, so, yeah, absolutely so, Red has taken on the ramp and ensuring that this ecosystem moves with us. We do a lot of hard work within Quarkus, so developers don't have to. We do some very, very clever stuff that very few organizations, would be able to do because they don't have the depth of knowledge of the Java virtual machine that we do. We're able to take a lot of things that you'd normally start off once only, like loading classes and you know, building kind of memory data around, all the kind of reading configurations all of the things applications do once and only once. Why do it another time? Why not build that into the component time, you're going to do it once but take it out of your runtime environment completely, so there are many ways where we're having to kind of rethink the way you know, applications run. We have to do a reset on what job was built for this environment of long running applications where, if the application took 10 minutes to load up all the stage area and classes and config, it didn't really matter, because it's not going to run for 36 months. You got to do a resale on those design decisions and think very very differently and given with our deep experience with containers and you know, working on things like native, serverless and on deep, deep roots in Java, we were able to do that and really think differently. So, Quarkus takes a lot of that kind of work away from developers they don't have to think too much about it. And by and large, what they can do is focus on their applications and their micro services and read all of that wiring and optimization for them. And hopefully deliver some you know, real significant improvements both in development productivity, but also the kind of runtime resource utilization as well to really lower costs. >> Okay, and Rich, what's is great that's been really the nirvana when you talk about developers is they don't want to have to think about some of that underlying you know, gobbledygook. That was why you know, the term serverless is so polarizing is because from a developer standpoint I don't think about this but everybody screams, but there are servers and there is networking and there's you know, things underneath that I need to think about. So, what is the underlying assumption here. We talked about you know, containers, Kubernetes, functions as a service, what integration is done there? Does this live across? Is it kind of like, you know, does it sit just just on RHEL and therefore everywhere the RHEL lives it's there? Or, help me understand kind of what that underlying you know, substrate is. >> Yeah, right now our focus is RHEL x86, 'cause that's kind of the dominant platform in a cloud. It is just Java, some have that natural kind of portability and you know, as other architectures become important, we can certainly look at those as well. The reason why the underlying machine architecture is important, is because one of the options you have with Quarkus is actually the ability to compile everything down to a binary executable, right? That may give you some additional footprint reduction and performance enhancements. And also if we compile down to native, we do need to think about the underlying operating system and the architecture. But by and large, as a developer you really don't have to care. Just like to you don't have to care with Java today. You also have the option with Quarkus, to run on conventional JVM, open JDK is our preference and if you can run on open JDK, then you can pretty much run anywhere. Under you know, different reasons for compiling down a native, this is running on a traditional JDK, different optimizations, different trade-offs that you'd like to make. >> All right, so Rich, an open source project here, can you tell us a little bit about you know, who's contributed to this, you know, what general adoption is this, and, you know, where are we with the solution today. Is it today ready for production environments? >> Yeah, it's getting close to production ready, yeah, we'll be making this Germany available and during Summit and many of the components we use are tried and tested, again we're not reinventing everything from the ground up. We leverage things like REHL VM, we leverage open JDK, we leverage all our frameworks and library, the developer that are familiar with, we just have to optimize them for Quarkus, so, yeah, much of this is not brand new technology. The existing technology that has that kind of maturity and tolling support. So yeah, we're confident it's production ready. One of the early stages of the development of Quarkus, was to use some of Red Hats own products as goody picks. Actually, you know, optimize those products for containerized environments by rebuilding them on top of Quarkus and that gave us obviously a lot of insight into the general readiness, yeah, the whole kind of eating around and dog food principle. In terms of the organizations in investing Quarkus, you know, we have this kind of have old addedge, we often use at Red Hat, which is you know, if you want to, if you want to move quickly, go alone. If you want to go far, then go with others. We're at a stage, where we've been developing Quarkus very, very rapidly and that's mostly been a Red Hat effort. We've certainly got some help from the mothership IBM and I expect that to be an increase overtime and we're now in a point where we have a Germany available product coming up and we're ready to really kind of expand the ecosystem. So, we're looking for you, whether you're a framework provider, you've written a framework for Java and you want to have that Quarkus provider, ensure that runs really well and partly the kind of growing ecosystem around Quarkus, we're looking for that, we're for, you know, cloud providers to you know, take this technology and see how it runs in other environments and give us feedback. So, yeah, definitely looking to expand that ecosystem of contributors, so we can really turn this into kind of the facto technology for the cloud. >> So, Richard, stop back for us for a second, you've got a long history with Java. You know, why in 2020 is you know, Java still, I believe it's like number two on the language list there. Why is it so important today and why is moving forward to all of these cloud solutions so important for that ecosystem. >> Yeah, I think it comes down to you know, organizations are faced with a tough choice. That they stick with the language that they know and love, which is Java, the language, the relevant applications for the last decade and not be able to take the best advantage of cloud and native or serverless environment. Whereas if they go and learn a new language, Datalog or No.js and you know, kind of hunt around and trying to see if that has the same kind of ecosystem and support. So, we want give organizations a better choice, which is you can stick with a language you already know and love and you have skills and the resources, yeah, you can still take advantage of these new environments and that's you know, I'm mean, fundaments the problem we're trying to solve for your customers. That twice open source projects are, they live or die, depending on, they really do scratch an itch, you know, fulfill a need with real developments. I'm going to think we've certainly from the adoption and interest we've seen with Quarkus, we really do think we've found a very real problem to solve. >> Yeah, Rich, before we wrap up, I just want to give you the opportunity, you know, how is your teams doing, I think you know, Red Hat's making a real concerted effort to make you know, an appropriate tone for the event this week. Trying to make sure it's not you know, some of the usual glam that we normally expect to see, full on the community all together, but, you know, the community is so important and you know, the network of people that, you know, built not only you know, technologies but also careers and you know, relationships, so, give us a insight as to how your teams doing, everybody in these challenging times. >> I think this is another good example of where open source really does show it's resilience. Open source projects are simply very, very distributed. No open source projects rely on an office being open, so your word distributed team all used to work using distributed tools across the world, different time zones. It's kind of natural for us, so we're kind of plugging on, you know, just as we have them in the task, you have a few more dogs in the background and crying babies and you know, we're all humans, we all tolerate that. We have great support from our leaderships, that's Red Hat and IMB. They're very clear that they've got people and families before revenue and that's good to know. Everybody's you know continuing as they can to you know, ensure that we have you know, great technology out there 'cause like I said there's real demand here that needs to filled and we're going to continue doing that. So, yeah, everybody's kind of holding up pretty well, so, let's just see how long this thing goes but again, I do think it is a valuable kind of lesson on the resilience of distributed teams and open source in particular. So, yeah. >> All right, well thank you for that Rich. Just to bring it on home, as you said, the general availability of Quarkus you know, is in front of us here, really expecting the ecosystem in costumers move. Give us a little bit of what we should be looking at going forward, what are some of the kind of maturity steps and what should we expect to see, through the remainder of 2020. >> Yeah, it's going to be a pretty exciting year, I mean, given the changes we were all going through we are going to try and come meet developers, where they are, which is you know, on their laptops and in front of their computers, so, we're going to do, we're playing through a bunch of you know, kind of very quick webinars, you know, quick bye what it takes, you know, interesting features, we're going to do some virtual hackathons as well, so you can actually get people with time and talk with some experts. We have platform for doing that. So, we're pretty excited, we, you know, again with the incident, we can reach a lot of developers very easily. Actually far more than we could at a live even like Summit, so, we're going to make the best of it and try to get at to as many developers as we can with Quarkus and you know, hopefully they'll repay us by investing a little bit of time into it and giving us some feedback and you know, trying some applications and you know, see how it goes. >> All right and you know, final, final question for your Rich, you know, Quarkus, I have to imagine that the Quark, the subatomic particle, you know, came into the naming there. Is there some connection with that? I guess why the name to the project? >> Yeah, I mean that's pretty much it, you know, the Quarkus you know, kind of. (mumbles) Arguably the smallest fundamental particle. >> And can we find something smaller? >> Well, there potentially is something smaller but that's kind of in the realm of quantum mechanics and physics, which I'm not an expert on, so, but yeah, it's meant to mean small and the us bit, the US bit. I'd like to think there was a really good big meaning around that. The meaning is that we understand, that trying to do any kind of brand leadership or trademark protection on a well know server like Quark, is it possible? So, we had to add something to Quark and Quarkus kind of sounded cool. >> All right, Rich Sharples, pleasure to catch up with you, congrats on the progress for Quarkus, definitely looking forward to watching it's progression in the future. >> Thanks, great talking to you. >> All right, I'm Stu Minneman. Lot's more coverage here at Red Hat Summit 2020. Thank you as always for watching The Cube. (gentle 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.

>> 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

>> live from Boston, Massachusetts. It's the you covering your red hat. Some twenty nineteen >> rots. >> You buy bread >> hat, >> and we'LL go back here on the Cube as we continue our coverage here. Red Hat Summit day. One of three days of Walter Wall coverage coming to you exclusively here on the Q. I'm John Walls was too Millman. Thank you for joining us. And we're now joined by a couple of gentlemen. Guess the dynamic duo of the container World it at Red Hat. Scott McCarty is the principal product manager of Containers. That open shift and Forell. Scott. Good to see you, sir. >> You could see it >> and been. Bree are Who's the principal product? Manager of Containers and Koro s, Of course. Also it Red hat Been. Thank you for joining us. First off, just your thought about show. Obviously, there's a lot of educational programming going on up down, big crowds, a lot of buzz. Good activity day one, at least from our perspective. How are you guys seeing this so far? >> I love it. I mean, it's been great so far. We just had us. I just had a session, just got out of it. was completely full of people trying to get in that were lined up against a wall. So it's been very exciting so far. >> Yeah. Ben. So it's one of >> my favorite times of the year, right? It's so much energy. Everybody comes with the exchange of ideas, just feedback and everything is one of my favorites. >> Oh, good. Right now s o l e made available publicly today for the first time. We talked about that a lot so far on the program, I'd like to hear from >> your side of the fence. Then what does that mean to you in terms of the container world and the impact that you, you know, from here going forward, you've got a whole new world of concern, I would think Scott. >> Yeah. I mean, with the relic, it's it's >> exciting because we're releasing, uh, you know, a lot of new tools around containers, >> a ton of new operational, you know, management capabilities. I mean, it's just it's an exciting release, Ben. It's a It's a big step forward, right? Every single release is a big deal, and we look at the container space. It's evolved a lot in the past for five years right when we came out. Seven. So technology's matured, Really, it's Ah, it's a smooth, easy experience to get to the release. And if lots going into it a lot, >> Yeah, so, Scott, It's funny. I think back. Turn back. Five years ago, we had a lot of jokes about doctors. You mean the pants? Because container ization and, you know, limits, containers and everything. That was something most people hadn't heard about here. Twenty nineteen, You said, There's, you know, crowds trying to get in the door. And it's not what but there really digging in and understand the tools we give a little bit of. You know what? What's what's with the excitement these days? Where are the customers? And you know what? What do you digging into >> with them? Yeah, well ah, >> funny example. So I asked I asked this last session, You know, raise your hand if you've used containers. If you just even fired up a container before and everyone raise your hand. And now, five years ago, that was, like one person >> and then even last you worked for Google. Yeah. Even last >> year that it was still maybe forty percent of the people, and now it's one hundred percent when they come to a session. So I mean, it's it is it is definitely changed, a tremendous amount. And now it's about So I joked, You know, five years ago is about using a chef knife, you know, just like you cut everything with it, right? You cut it. Vegetables, meat, whatever. And there was like one thing, and you just figured out Doctor and Cooper names was even on the radar Yet now it's about refining all the tools and getting to a place where, like, it's really getting excited, cause now we have special paring knives and chef knife and, you know, hibachi, knife and all these different, more specialized >> tools. So it's getting saying >> You think it's easy to >> adopt now to write, because years ago everyone was hedging their bets on you know what orchestration am I going to use? What piece? Um, I'm gonna build my stack. We have >> now. It's much, much clear, well defined. You know, Cooper Netease is dominant factor, right? Mean, open shift is huge, huge growth for us in that space. So I mean, it's it's it's a lot easier for customers to get in that game now than it was, you know? Yeah, just a couple years ago. Yeah, just a couple years ago. All right, so let's let's sticking out security a little bit because that was one of the big question marks in the early days. And you know something? We talk about it all the shows. It's it's definitely a focus of the real late launch. So where were the container world today and anything new or nuance that the audience should understand? I think on the security side you've got I have three or four big points there. One is the container tools of worshipping. Today they basically inherit the full Lennox security model. Right? So no longer do you have ah, privilege socket. That is, I kind of that weak factor, if you will, that's gone on. Really? So that's a big That's a big win right there. Beyond that, we've got a new crystal policies. You can set a central policy for the O. S. And that works in the containers well, so of you and enforce a particular kind of floor, if you will, of crypto. You could do that with relate for the host way and images as well. That's a that's a big part of it. And then we also have new tools that you can build smaller containers because how did the security is what is in my container? So if you're putting less less packages and content in that image, that's a much smaller Becker as well. Soon. >> Yeah. So, um, from from a security perspective, too, you know, you know the fact that now we have, um, kind of we've got a set of tools now that we can do experiments with things like ruthless, for example. You know, we're tech preview release of ruthless contract, so historically have always ran them, you know, as route. That's just how it works. I mean, we kind of figured it out one way and did it, and it was cool. And then at a certain point, we went all right, we need these other use cases where want developers to build to do it. For example, I just talked to a customer that it has four two hundred. I'm sorry, developers that are all running instances on their laptops PM's with pod man and build a running and, you know, using these tools to actually build containers, and they want to do ruthless bad. They want to do it in all their essentially all their environment, so that people are really hungry for a lot of these security features that we're working on now and relate. And it's something that we're releasing even as a vato. >> How did the capabilities changed in terms of relate now and what you have to provide the support? So what's transformed? And then what will be the need in order to build on that toe work on that and to make it more secure stables on so >> far? Well, I think I think you kind of have to dig into, like, a selection of what tools we decided to go in. Relate you'LL see that it's pod man. Build a scope. Here are the three main lower level tools that we have, and those tools are built serving a Unix mindset where it's like you can pipe things together and do things and use them collaboratively together to go remotely inspect images, pull them, build them from scratch, you know, run them locally, not as roots run them as a non route, contains things like that way or not at, you know, we're not releasing doctrine. Relate. And so so the transition. There is probably the biggest transition for users. Kind of realizing. Okay, we're going kind of broken this apart into three little or tools that we can then use Todd Man being the main one you go to. And then and then it's got a command line that's very similar. And so it's very easy, tio kind of transition over. But then you start to again kind of my my chef knife reference. You realize once you transition from, say, Dr Pod man, you kind of that's your chef knife. You kind of know what? How to start doing things that way. But then you start to get more refined and start to dig deeper into, you know, like, you know, into building scope. You essentially teacher. Yeah. >> You're good there. Yeah. I don't know. All right. Whatever he says. Scott >> Universal base image. Something we've talked a little bit about to tell us how that this is going to impact, you know, talk about everybody building things on their laptop. Seems like that's an extension of where this fits. Help help us understand? >> Yeah, I can't hide my enthusiasm. One how excited I am by Eva, and I will admit Ivory had a couple people come to me and say, This is the most exciting thing for me at Summit period And I think that's interesting because it's not actually something new and that, you would say from a technology perspective, how exciting is that? I don't know, but like it allows a set of collaboration that we've never been able to like, really, really do with a well base image historically, and I think the real base image is the highest quality basement temperament out there. But the problem is, even if you had something really simple, like so you had one university and that created some kind of science experiment in a container, and then they want to push that out to a public registry, then pull it down a different university and share it. They couldn't do that under the terms of the rail base image. So that was that. Was that create a little bit of friction with the FBI? Now that's completely gone. You can now run it anywhere you want, distribute anywhere you want, just the distribution alone is exciting. It and the fact that when you >> run it on rail, you >> build on rail, run on relics completely supported Israel. But you can now push it out to a public registry and let it sit out there and other people can >> use it in an experiment. So is the, you know, coming together of container ization in that distribution is that would kind of is really new with this, as opposed to the ways that I used to be able to share lennox images in the past. >> Well, all I think I think the challenge was you'd have some people that would want to do something. They want to build a distributed anywhere they want have that freedom. But they still wanted the quality of the rail basement. Now that created friction, right? So then they'd have to make an unnatural choice between, like, a fedora or I use, you know, well, maybe how you sent to less and your lying and none of those have all the things that I want, right? It was like a card game trying to get all the components that you want. You want sport, ability of Raoul. You want the security of the performance center center. But you couldn't. You couldn't distribute anywhere, so that created friction where you make on natural choices on basement. Now you be. I just The name implies that universal use it for anything you want. >> Same for communities to write because they don't want to make one that could freely distribute and then another like supported variant. They have more to maintain its more cycles and everything so simple. Find that it is a big deal. Yeah, >> and migration between base images is a linen migration, so it's frustrating to do. You don't want to do it. You want to build on one thing. And then I thought I distribute that thing anywhere. Well, then it's >> interesting, you know, go back a few years. There was this big movement to do, like just enough OS. How do I slim down the core? Os was I don't need everything that you know Realm necessarily does. So have we gotten over that? And we now gotten with you know, the things like you be I down to like a nice unit that's easily terrible and distributed. It's a good question. It's a topic that we'LL never go away. I don't think we're still. It's just changing its form, right? It still exists on the host. It's still exists in images. It's still exist with unit colonels and everything. I >> think where we >> are today. That was a really good spot, right? We've got several footprints of FBI. If there's several footprints of Rehl, including well, Core OS, which is like bedded version of rail into open shift right for a small form factor container host. So where we are today is very strong, but it's going to continue to evolve and get better. So, yeah, >> and we I mean, we look at the future and we're we're looking at ways toe. Make it even smaller, you know, you're always looking at, but yeah, Ben, mention there's three footprints of you B i today. There's a minimal image. There's a standard image, and then there's even a little bit bigger images allows you run multiple services, but you know that's the selection today. But in the future, we're looking at making the minimal one more minimal. Were even looking at, you know, making the standard one more minimal. >> Yeah, we're not done. Yeah, we're not done. You're never done. I guess the last thing I have on this, you know, multi cloud is such you know where customers are today. You know, you're gonna have the CEO Microsoft up on stage today. Two years ago, when I was here, it was the partnership between Red had an eight of us was all the discussion. I spoke to the Red Hat team, the Cloud show recently. So how does the tooling that you have fit in tow all the clouds discussion that I have when I talked to users? You know, one of the biggest lock ins they have is the skill set and the understanding of different tools and knowledge. And so you know, where we standardize and where do we still have work to do in this space? That's a big question. So yeah, I guess way addressing a multiple levels right at the core. The center Israel. Right. So well ate right now today on all those cloud platforms that you just name, right. So same say maybe I level guarantee that ten years hard work everything. It's it's everywhere. It's pervasive today. Level up, right. You've got the container images and stuff same story. They're Goa level. You've got open shift that is pervasive everywhere. And now we're doing really cool things. And Cooper Net. He's like a machine, a p I and all these other things toe actually control those individual cloud infrastructures which abstracts all of the customers ations per for food for him, which is >> powerful. So I think, for me was the most exciting things is the open shift for paradigm shift that shift from managing individual nodes to ship to managing the cluster as a computer, which we've said for what, twenty years? The sun? I think you know the cluster is the computer, you know? But we're really there today. Like we have a single E p I. Ben mention the machine, the machine, a PR machine configure operator. There's there's essentially automation built into the chip platform now that allows you to appoint the same on any cloud. So eight of us azure, you know, open stack, even on VM, where even on, you know, even in liver gonna look a laptop. There's a way to deploy it in the identical, you know, in an identical configuration. To me, that's exciting, because now I have one set of things I could learn. And then again in the standard red hat way. If you feel locked in, you can go use a Okay, Daddy, you can use the upstream. So you're never locked into our product, Which that's something. Get a lot with Kat drives, right? Like if you're locked in there, you're you're locked in there. There's no there's no, you know, open source version of that to get out of that. >> So you've talked about growth opportunities? You said, No, we're not done yet. Making the joke about your own work. You've talked about a twenty year evolution, you know, Just refer to that. And if you could look, you know, whether it's three, four, five, whatever years down the road, where's the big leap? Where's that have to come? Where do you think it's going to come in terms of the capabilities that you want to work on and what you want to be able to deliver from where you are right? Now >> get my crystal ball. Yeah. >> Yeah, Well, I think you've got one. Yeah. Then I have a lot of confidence in you, but if you had to say okay, this is this is atleast where we're gonna be. We're gonna have to spend a lot of our time because this this is the area that we think I think needs most attention. A >> couple of things, right? People only scale so much. So automation is an area that's bulletproof going forward, and it's going to evolve and take many forms. Right now, our big push has been on the operator space and obviously technologies like answerable that's going to continue to evolve and make make people scale better. That's probably one of the biggest ones. And I >> think that's one of the biggest ones. I think I think for me, probably where my mind wanders, is around partners and building that ecosystem in the open ship space similar to what you see in the realm. Because system today I think three, four years from now you're going to see it really exploded at ABC that I already see it exploding. But by then you'LL see it maturing and you'LL really see. I think if you look at the operator paradigm, I'm very excited by that because it's kind of like the Emma science dollar that Microsoft invented. You know that kind of made that that ubiquitous that install experience. Except that operators make it you because they install and managed a too. So I think, like, kind of to his point of, like making that the install really simple and then the operation of it. Over time, I think you're going to see a lot of I think. I think you couldn't fill a room and ask him, Like what I in fact, I did. I asked what an operator was, you know, and they they weren't super aware of it yet. But I think in the next five years, that will become the big with this way of just installing software. >> All right, well, we're going to check back in five. We'LL see how it turns out and been by then. Bring that crystal ball back with wood. Ok, I'll do a good deal. Thanks, gentlemen. Thanks for the time you haven't put on the Cuba as we continue our coverage here. Red Hat Summit. We're in Boston back with more right after this

>> live from Boston, Massachusetts. It's the queue covering your red hat. Some twenty nineteen lots. You buy bread >> and good morning. Welcome to Beantown, Boston, Massachusetts to Mina Mons Hometown by the police Town of residents. John Wallis was stupid from here on the Q. Bert had summit and stew for you. Good to see you here. And a home game. >> Yeah, John, Thanks so much. Nice. You know, Boston, The Cube loves Boston. The B C E C is actually where the first cube event was way back in twenty ten. And we wish there were more conferences here in Boston. Gorgeous weather here in the spring. Ah, little chilly at night with the wind coming off the water, but really good. Here is the sixth year we've had the Cube here, right? Had some in my fifth year at the show. Great energy. And, you know, thirty four billion reasons why people are spending a lot of time keeping a close eye on. Let's just know. Yeah, >> jump right in thirty four billion dollar deal. I am red hatt gotta prove by doj uh, here in the States. But there's still some hurdles that they have to get over in order for that to come to fruition, Maybe later this year. That's the expectation. But just your thoughts right now about about that synergy about that opportunity that that we think is about to have. >> Yeah, so? So right, let's get this piece out of the way. Because here at the conference, we're talking about Red Hat. The acquisition has not completed. So while the CEO of IBM you know Jenny will be up on stage tonight along with, you know, Jim White Hirsi over at Hat and Sakina della, you know, flying in from Seattle, where you might get your name yesterday. So you know, at least two of those three your Cuba Lem's. So we'LL get Jenny on one of these days. But, you know, this is a big acquisition, the largest software acquisition ever, and third largest acquisition in tech history. Now we watched the first biggest tech acquisition in history, which was Del buying AMC just a couple of years ago. And this is not the normal. Okay? Hey, we announced it and you know, it closed quietly in a few months. So as you mentioned, DOJ approved it. There's a few more government agencies Europe needs to go through. You never know what China might ask to come in here, but, you know, really, at the core if you look at it, you know, IBM and Red Hat have worked together for decades. You know, we wrote a lot about this when the announcement happened. You know, IBM is no stranger to open source. IBM is no stranger to the clinics and the areas where Red Hat has been growing and expanded too. You see, IBM, they're so communities, you know, super hot space. If you look, you know, Red hat is they're they're open shift platform, which is what Red Hat does for cloud. Native Development has over a thousand customers. They're adding between one hundred one hundred fifty a quarter is what they talk about publicly. We're gonna have some of those customers on this week. So huge area. That multi cloud hybrid cloud world absolutely is where it's at. We did four days of broadcast from IBM. Think earlier this year in San Francisco. And, you know, once again, Jim white hairs and Jenny were on stage together. They're talking about where they've been working together for a long time. and just, you know, some things will change, but from IBM standpoint, they said, Look, you know, the day after this closes, you know, Red Hat doesn't go away. That had just announced new branding, and everybody's like, Well, why are they changing their branding? You know, when you know IBM is taking over and the answer was, Look, Red Hat's going to stay as a standalone entity. IBM says they're not going to have a single lay off, not even HR consolidation, at least in the beginning. We understand, you know, give me your stuff to work out some of these pieces, but there are ears. They will work together. I look at it. John is like the core. What is the biggest piece of IBM's business is services. That Army of services, both from IBM and all of their Esai partners and everybody they worked with Khun really supercharge and help scale some of the environment that red hats doing so really interesting. Expect them to talk a little bit about it. Red hat is way more transparent than your average company. They had an analyst event like a week or two after it happened, and I was really surprised how much they would tell us and that we could talk about publicly. As I said, just cause I've seen so many acquisitions happen, including some you know, mega ones in the past. And we know how little usually you talk about until it it's done and it's signed. And, you know, the bankers and lawyers have been paid all their fees. >> Let me ask you, you raise an interesting point. Um, you know that there are some different approaches, obviously, between IBM redhead, just in terms of their institutional legacies in terms of processes. Red hat. You mentioned very transparent organization. Open source. Right. So we're all about the rebrand. They come out, you know, the drop shadow, man, They got the hat. What's that cultural mix going to be like? Can they truly run independently? Yeah, they're a big piece. So And if your IBM can you let that run on its own? >> So, John, that is the question most of us have. So, you know, I've worked with Red Hat for coming up on twenty years now, you know, Remember when Lennox was just this mess of colonel dot organ. So much changes that red hat came and gave, you know, adult supervision to help move that forward on. The thing I I wrote about is what Red Hat is really, really good at. If you look at the core, there do is managing that chaos and change on the industry. If you look how many changes happen, toe Lennox, you know every you know, day, week, month and they package all that together and they test all that same thing in Kou Burnett is the same thing in so many different spaces where that open source world is just frenetic and changing. So they're really geared for today's industry. You talk what's the only constant in our industry? John is it is changed. IBM, on the other hand, is like, you know, over one hundred years old, and I tried and true, you know, Big Blue. You know, I ibm is this, you know, the big tanker, you know, it's not like they turn on a dime and you know, rapid pace of change. You think of IBM, you think of innovation. You think of, you know, trust. You think of all the innovations that have come out over the century. Plus do there and absolutely there is a little bit of impeded mismatch there and we'LL see So if ibm Khun truly let them do their own thing and not kind of merged suit groups and take over where the inertia of a larger group can slow things down I hope it will be successful But they're definitely our concerns And time will tell we'll see But you know analytics front You know, they just announced this morning Rehl eight Red hat enterprise linen, you know, just got announced and definitely something will be spent a lot of time So >> let's just jump in a relative Look again, We're gonna hear a little bit later on. We have several folks coming on board to talk aboutthe availability. Now what? What do you see from the outside? Looking at that. What is it going to allow you or us to do that? Seven Didn't know. Where did they improve? Is that on the automation side? Is it being maybe more attentive, Teo Hybrid environment or just What is it about? Really? That makes that special? >> Yes. So you know, first of all, you know these things take a while in the nice thing about being open sources. We've had transparency. If you wanted to know it was going to be in relate. You just look in the Colonel and and it's all out there. They've been working on this since twenty thirteen. Well, seven came out back in June of twenty fourteen. This has been a number of years in the mix. You know, security. The new, like crypto policy is a big piece that that's in their thie bullets that I got when I got the pre briefing on, It was, you know, faster and easier Deploy faster on boarding for non lennox users on, you know, seamless nondestructive migration from earlier versions of rail. So that's one of the things they really want to focus on is that it needs to be predictable, and I need to be able to move from one version the other. If you look at the cloud world, you know, when you don't go asking customers say, Hey, what version of Azure a ws are you running on your running on the latest and greatest? But if you look at traditional shrink wrap software, it was well, what virginity running? Well, I'm running in minus two and Why is that? Because I have to get it. I have to test it out. And then I, you know, find a time that I'm gonna roll that out, work it in my environment. So there is stability and understanding of the release cycle. My understanding is that they're going to do major releases every three years and minor releases every six months. So that cadence a little bit more like the cloud. And as I said, getting from one version a rail to the next should be easier and more non disruptive. Ah, a lot of people are going to want manage offerings where they don't really think about this. I have the latest version because that has not just the latest features but the latest security setting, which, of course, is a major piece of my infrastructure today to make sure that if there was some vulnerability released, I can't wait, You know, six or nine months for me to bake that in there. The limits community's always good have done a good job of getting fixes into it. But how fast can I roll that out into my environment is >> something I would assume that's that's a major factor in any consideration right now is is on the security front, because every day we hear about one more problem and these are just small little issues. These these air are could be multi billion dollar problems. But in terms of making products available today, how Muchmore important? How's that security shift? If you could put a percentage on it used to be, you know, axe and now it's X plus. I mean I mean, what kind of considerations are being given? >> You know what I'd say? Used to be that security got great lip service A. Said it was usually top of mind, but often towards bottom of budget. When you talk to administrators and you say, Oh, hey, where's your last security initiative? And that, like I've had that thing sitting on my desk for the last six months and I haven't had a chance to roll that out. I will get to it, but I want to again. If you go to that cloud operating model. If you talk about you know Dev, Ops movement is, I need to bake security into the process. If I'm doing C i D. It's not, I do something and then think about security afterwards. Security needs to be built in from the ground level. A CZ. You know, I I've heard people in the industry. Security is everyone's responsibility, and security must be baked in everywhere. So from the application all the way down to the chipset, we need to be thinking about security along the bar. Mind it is a board level discussion. Any user you talk too, you know, you don't say, Hey, where's the security sitting? Your priorities. You know, it's up there towards the top, if not vey top, because that's the thing that could put us out of business or, you know, definitely ruin careers. If if it doesn't go >> right, so there are there are probably a couple of platforms, every will or pillars. I think you like to call them that. You're looking forward to learning more about this week. I think in terms of red hats work one of those green hybrid cloud infrastructure, and we'LL get to the other to a little bit. But just your thoughts about how they're addressing that with the products that they offered the services they offer and where they're going in that >> Yeah, so look everything for red at start with rail. Everything is built on Lenox, and that's a good thing, because Lennox Endeavor is everywhere. If last year is that Microsoft ignite for the first time. And when you hear them talking a Microsoft talking about how Lennox is the majority of the environment, more than fifty percent of the environment are running linen goto a ws Same thing. All the cloud deployment Lennox is the preferred substrate underneath and Rehl doing very well to live in all those environment. So what we look at is, you know, some people say, is this olynyk show. It's like, well, at the core. Lin IX is the piece of it and relate the latest and greatest substantiation. But everywhere you go, there's going to be Lennox there from doing container ization. If a building on top of it with the the new cloud native models, it's there. And if you talk about how I get from my data center to a multi cloud environment, it's building things like Cooper Netease, which read that of course, uses open shift and you know those ties to eight of us and azure and you know, Google they're all there. So we mention Santina della's on stage tonight at Microsoft build. Yesterday there was announcement of this thing called Kita ke e d A, which has, like as your functions and ties in with open shift and spend a little time squinting it, trying to tease it apart. We've got some guests this week that'LL hopefully give some clarity, but it is. The answer is people today have multiple clouds and they have a lot of different ways they want. They want to do things, and Red has going to make sure that they help bridge the gap and simplify those environments across the board. Two years ago, when we were at the show big announcement about how open shift integrates with a W s so that if I'm using a ws But I want to have things in my environment still leverage some of those services. That was something that that Red had announced. I was, you know, quite impressed a time it was, you know, just last week being at the Del Show, it's V m. Where is the del strategy for how they get you know, A W, S, G, C, P and Azure and, you know, Red Hat does that themselves. Their software company. They live in all these cloud worlds, and therefore, open shift will help you extend from your data center through all of those public cloud environments on DH, you know? Yeah. So it's fascinating >> you've talked about Lennox to we're going to hear a little bit later on to about a fascinating the global economic study, that Red Hat Commission with the I. D. C. Of that talks about this ten trillion dollar impact of Lennox around the globe like to dive into that a little bit later on. >> Yeah, well, it's interesting, you know, it's the line I used is you say, and you say, Oh, well, how much impact is Lennox had? You know? You know, Red hats now, a three billion dollar company. That's good. But I was like, Okay, let's just take Google. You know, no slots of a company. Google underneath. It's not Red Hat Lennox, but Lennox is the foundation. I don't really think that Google could become the global search and advertising powerhouse they were. If it wasn't for Lennox to be able to help them get environment, there's a CZ we always talk with these technologies. You talk about Lennox, you talk about How do you talk about, you know, Cooper Netease? There are companies that will monetize it, but the real value is what business models and creation by. You know, all the enterprise is the service riders in the hyper scales that those technologies help enable. And that's where open source really shines is, you know, the order of magnitude network effect, that open source solutions have that its you say okay, three billion dollars? And is that what ten trillion dollars? It doesn't faze me, doesn't surprise me at all, but because my attention it look it. I'm not trying to trivialize. There's no But, you know, I've been watching clinics for twenty years, and I've seen the ripples of that effect. And if you dig down underneath your often finding it inside, >> I mentioned pillars that you were talking about cloud native development being another. But automation, let's just hit on that real quick before we head off on DH just again, with how that is being, I guess, highlighted. Or that's a central focus at and relate and and what automation? How that's playing in there I guess the new efficiencies they're trying to squeeze out. >> Yes. So? So what we always looked for it shows you're probably the last year is you know, you. How are they getting beyond the buzzwords? Aye, aye. When you talk about automation on area that that we've really enjoyed digging into is like robotic process automation. How do I take something that was manual? And maybe it was a fish injure? Not great. How can I make it perfectly efficient and use software robots to do that? So where are the places where I know that the amount of change and the scale and the growth that we have that I couldn't just put somebody to keyboard, you know, and have them typing or even a dashboard to be able to monitor and keep up with things? If I don't have the automation and intelligence in the system to manage things, I can't reach the scale and the growth that I need to. So where are you know, real solutions that are helping customers, you know, get over a little bit of the fear of Oh, my gosh, I'm losing a job. Or will this work or will this keep my business running and oh, my gosh, this will actually enabled me to be able to grow work on that security issue if I need to, rather than some of the other pieces and help really allow it agility to meet the requirements of what the business requires to help me move forward. So those are some of the things we kind of look across the shows. So, you know? Yeah. How much do we get? You know, buzzword, Bingo at the show. Where How much do we hear? You know, real customers with real solutions digging in and having, you know, new technologies that a couple of years ago would have had a saying, Wow, that's magic. >> But you say, Oh, my gosh. Yeah, and I don't want gosh right back with more. You're watching to serve the cube with the red had summit. We're in Boston, Massachusetts, that we'll be back with more coverage right after this