we've made just tremendous progress over the last several years with Microsoft you know started back in 2015 where we you know cross certified hypervisors and that's kind of a basic you know let's work together over the last couple years it's truly blossomed into a really good partnership where you know I think they've and we both gotten over this you know Linux vs. Windows thing and you know I said we've gotten over I think we both recognized you know we need to serve our customers in the best possible way and that clearly means is two of the largest infrastructure software providers working closely together and what's been interesting as we've gone forward we find more and more common ground about how we can better serve our customers whether that's you know what might sound mundane that's a big deal sequel server on realm and setting benchmarks around that or dotnet running on our platforms now all the way to really being able to deliver a hybrid cloud with a seamless experience with openshift from you know on premise - - to Azure and I mean having to H Bank on States twenty five thousand containers running in production moving back and forth - sure and I think it's more building on what I talked to you about a year ago if I remember last May May of 2018 in San Francisco so I was exposing very heavily look the world's going to move towards containers the world is already embraced Linux this is the time to have a new architecture that enables hybrid much along the lines that gem and all of the clients as well as Ginni and Sasha we're talking about on stage yesterday so you put all that together and you say that is what we mentioned last year and we were clear that is where the world is going to go nice step forward a few months from there into October of 2018 and on 29th of October we announced that IBM intends to acquire Red Hat so then you say wow we put actually our money where amount was we were talking about the strategy we were talking about Linux containers openshift the partnership we announced last May was IBM software products together with OpenShift that is we already believed in that but now this allows us coming together it's it's more like a marriage then sort of loose partners passing each other in the middle of the night we are so excited and you know having put in all the time part of this is representing all the work the team has done and the communities have done when you think about all the work that goes into a Linux distribution it is everybody it's the community's it's the partners so we released the Red Hat Enterprise Linux eight beta in November mid-november we've had 40,000 downloads of that beta since November people who have provided feedback and comments suggestions all of that fed into what we've released today as the Red Hat Enterprise Linux eight general availability so it's a big day and part of it is we're just so proud of how we've done it and what we've done and we've really redefined what are not the value of an operating system with Red Hat Enterprise limits eight tech transformation started about ten years ago bean CI over the company about ten years and frankly the first five years were just fixing the basics so getting in place what we'd call world-class systems doing a bunch of stuff on resilience and security and all of that kind of stuff and the other thing and this is the dramatic change you know ten years ago when I joined the company we were 85% outsource to managed service vendors so I had technology people that basically were signing contractors and managing service agreements if we didn't have technology DNA and so you know over those five years and the full ten years actually we've been to not about just in sourcing and rebuilding our technical muscle if you like so now we're we've gone from 85% outsource to 90% in sourced so we run build and manage our own we're at word now a technology company yeah and and five years ago we had a real big shift and you know we were we were closest to what was going on in China and so probably saw this before many many of the other banks saw this around the world of what Alibaba was doing with ant financial and $0.10 and this whole just just complete disruption of how customers interact with the banking industry so we got an early lead on this digital transformation and really for the last five six years would be doubling down on building a pure digital offering and we see ourselves as a technology company providing banking services not as a bank with some technology department in the backend open source is the innovation model going forward period end of story full stop and I think as I said in my keynote yesterday you know leading up to the the biggest acquisition ever for a software company not an open source software coming a software company that happened to be an open source software company I don't think there's any doubt that that open source has one here here today it and it's because of the pace of innovation yeah our goal is to make sure we're supporting those upstream communities so all of all of Red Hat software is open source and we work with a whole community of individuals and companies and the upstream open source software and we want to make sure that we're not just contributing features that we want but that we're a good player or that we're helping to make sure those communities are healthy and so for a number of the projects that were involved in we actually assigned a full-time Community Manager a community lead to help make sure that project is healthy so we have someone on everything from Saif and Gloucester to fedora to kubernetes I'm just making sure the community does well yeah we do a little bit of both and so a lot of it is responding to the community and that's one of the areas that Red Hat is really excelled as taking what's popular what's working upstream and helping moving along make it a stable product or stable solution that developers can use but we also have a certain agenda or certain platforms that we want to present so we start from like various runtimes to actually contain our platforms and so we want to have to kind of drive some of that initiatives on our own to help drive fill that need because we hear it from customers a lot it's like things are doing are great but like there's all these projects that need to come together sort as a product or unified experience and so we spend a lot of our time trying to bring those things together as a way to help developers do those different tasks and also focus across like not just the Java runtimes which we hit a lot of Java so you might have baked security in right I mean we have a secure supply chain and you talk about difficult things for la right every package that we that comes in that is we totally refresh everything from upstream but when they come in we have to inspect all the crypto we have to run them through security scans vulnerability scanners we've got three different vulnerability scanners that we're using we run them through penetration testing so there's a huge amount of work that just comes just to inherit all that from the upstream but in addition to that we've put a lot of work into making sure that well our crypto has to be Fitz certified right which means you've got to meet standards we also have work that's gone in to make sure that you can enable a security policy consistently across the system so that no application that you load on can violate your security policy we've got enough tables in their new firewalling Network bound disk encryption that actually it kind of ties in with a lot of the system management work that we've done so a thing that I think differentiates rl8 is we put a lot of focus on making it easy to use on day one and easy to manage day two well we're not getting there were there what that allows us to do is to take the reference designs that we have and the testing that we've we've previously validated with Intel and Red Hat and be able to snap pieces together so it's just a matter of what's different and unique for the client in the client situation and their growth pattern what's great about trueskill is that in this model is that we can predictably analyze or consumption forward based on the business growth so for example if you're using open shipped and you start with a small cluster for say one or two lines of business as they adopt DevOps methodologies going from either waterfall or agile we can we can predictably analyze the consumption forward that they're going to need so they can plan years in advance as they progress and as such the other snap-ins say uh storage that they're going to need for data and motion or data at rest so it's it's actually smarter and what that ends up doing is obviously saving the money but it saves some time you know typical model is going back to IT and saying we need these servers we need the storage and the software and bolt it all together and the IT guys are you know hair on fire running around already so so they can you know as long as IT approves it they can sort of bypass that that big heavy lift we're trying to do is create role models for women and girls who would like to participate in technology but perhaps are not sure that that's the way that they can go and they don't see people that are like them so they're less tendency to join into this type of communities so with the community award winner we're looking at a professional who's been contributing to open source for a period of time and with our academic winner we're looking to spur more people who are in university to think about it and of course the big idea is you'll all be looking at these women as people that will inspire you to potentially do more things with open source and more things with technology we've been hearing for many many years that we definitely need to have more gender diversity in tech in general in an open source and Red Hat is kind of uniquely situated to focus on the open source community and so with our role is the open source leader we really feel like we need to make that commitment and to be able to foster that right so so Sierra's a supercomputer and what's unique about these systems is that we're solving there's lots of systems that network together maybe are bigger a number of servers than us but we're doing scientific simulation and that kind of computing requires a level of parallelism and it's very tightly coupled so all the servers are running a piece of the problem they all have to sort of operate together if any one of them is running slow it makes the whole thing go slow so it's really this tightly coupled nature of supercomputers that make things really challenging you know we talked about performance if if one server is just running slow for some reason you know everything else is going to be affected by that so we really do care about performance and we really do care about just every little piece of the hardware you know performing as it should so we thought okay let's take all of these best practices that we have and build more or less a methodology around it how to make this actually works like how to do this we really broke it down into like individual sprints do dissin sprint one the distance sprint do to really have the results within three months six months 12 months whatever the places that you want to run on and then we realize talking to customers this by itself isn't still enough so that's why we started to open up this to an entire ecosystem so we brought ecosystem partners along like working closely with red a lot of other companies but also system integrators who can help us we speak up projects because we as a company are software companies we're not a services or consulting company and we do support customers and some of those engagement but if you think of like a really fortune 500 company that's a multi-year project it will keep hundreds of busy people busy so to recap like built-in methodology we built the ecosystem to deliver on that promise at scale and now the last step was we as we were doing this we also built like a reference architecture for it and was just in an internal IDE so how do we like structure this bill that reference architecture and then realize okay I think it's kind of like super helpful for customers so that this way we then decided to open source this reference architecture is fabric as well to like the entire software community so they can also use it so technically these three pieces it's the methodology it's the ecosystem and it's like the reference architecture that you can work with to help you achieve you [Music]

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

(electronic music) >> Presenter: Live from Boston, Massachusetts. It's theCUBE! Covering Red Hat Summit 2019, brought to you by Red Hat (electronic music) >> Welcome back here on The Cube, continuing our live coverage at Red Hat Summit 2019 as we come to a near conclusion of our three days of wall to wall coverage for you here. All the keynotes, it's been and the guests we've had just a lot of fun and certainly an educational opportunity for Stu Menimen and myself and we're looking forward to our next couple of guests here. We have Khurshid Sohail, an application developer at UPS and Nish Jani, a senior application development manager at UPS. Gentlemen, thank you for joining us. We appreciate the time. [Developers] Thanks for having us. >> Presenter: Thank you. And so you have representation on the keynote stage of this morning. UPS did, talking about some of the changes underway there and your Red Hat relationship for those at home who work privy to that. Just to set the stage for in terms of what you're doing with Red Hat and what you're gonna be doing with them as they came up with a couple of releases this week. Nish, if you would? >> Sure. So as you know, UPS is delivering products and services to over 200 countries and from a scalability perspective, we deliver over 21,000,000 packages per day and during our peak season, it grows to over 30,000,000 packages a day, and last year we averaged 200,000,000 tracks a day on our tracking system and last peak we went to 335,000,000 tracks in a single day and that was all built on a new open-shift platform that we developed. >> Just a little bit of data. >> Yeah. >> All right. >> Yeah, you know I love when you talk to, you know, so many customers today who scale and it's like "oh, okay. How many transactions we have." It's like "oh, you talk logistics", you're like oh, okay. You talked a lot of numbers there but when you talk about the driver and how many officers they have and the amount of data that goes in. It's like, okay, how many supercomputers do you have? And you know, hundreds of PhDs solving this. Maybe we're just a little bit in tide, you know, the logistical pieces that go there and how, you know, I mean this is not, you know, a just "Okay, go do your route" as we have in the past. >> Yeah, so from a driver perspective, we've offered services to the drivers that take out the human search for needing to deliver packages. We have an orion system which tells the driver exactly where to go and where to deliver the packages and optimize the routes for them from a visibility perspective which is the products and services Khurshid and I support. The driver is able to do their jobs and deliver their status and deliver packages on time so for our customers, they see an updated status in real time. From a VI perspective, which is our visibility information business engine which was our new platform that we built last year, it was a long journey into the process, part of our digital transformation. We got into the transformation as a need for customers who wanted more out of their products and services that we offered today, and as far as being able to do faster market and provide visibility in a real-time sense. >> Presenter: Yeah. >> We always love when you hear some of these digital transformations. Like okay, you know, I think if UPS does logistics, those were pretty complicated before. >> Absolutely. So, like you needed a digital transformation. Maybe we could start with, you know, what were some of the objectives, what were we, you know, what was holding you back or limited before and you know, let's go to the after when you get through there. >> Sure. So before we were on a monolithic system, a legacy system and the costs per track were very expensive and your to drive new need we needed to redevelop ourselves and redesign ourselves and the way we did that was we transformed by moving away from our traditional waterfall models which typically took six months to deploy new services and we went to within weeks, and the way we did that was to develop agile methodologies and using open-shift we were able to develop and deploy applications more quickly and Khurshid can talk a little bit more about VI application and how it works. >> So pretty much what our goal was to get the old track system off the legacy model off into a containerized, on premise, cloud-based platform. So we successfully accomplished that, essentially 20 years worth of data we did in a year, so we're pretty proud of that, not to toot our own horn, but yeah. We got everything going with open-shift, and a couple of other Red Hat products like AMQ, JBoss, Fuse for AMQ and we also worked like Nish mentioned with the agile methodologies and principles so we were successfully able to create a type of environment for other applications that UPS see as a, you know, kind of a look up to so other applications can see what we've did and they can get themselves over in the same direction. >> Yeah, so can you bring us inside a little bit the organization. Was this a new team that came in? Was there a combination of the new and old? You know, the retraining. >> Yeah, so the team was formed out of some of the old members of the team that knew visibility inside and out. My team done the front-end of UPS.com's tracking application and we've brought in team members that were new and were able to develop the application in a short amount of time. So we've nearly formed a team, we've put together a parallel path from the old system to the new system then we transitioned over and it was seamless to the custom. >> You were talking about customer choice, we were speaking earlier before just about competition, so you have to be extremely responsive to customer needs and my choice is something that comes to my mind that you offer that gives great flexibility to a customer but tremendous complexity I would think to you because you have kind of like an X and a Y, you have a package, you've got a delivery point and now you throw the Z in with a time of day change or location change and to coordinate that so your efficiencies, your fuel efficiencies and route efficiencies are still maintained. And how do you do that in your environment? And whether that's something that Red Hat, is that something that is enabled by the technology that you're deploying of theirs? >> Sure, from a visibility perspective my choice product? have been very successful. We're able to deliver B to C packages to our individual customers or our consignees which help them choose where and when they want their package and also be able to see a delivery time. From a complexity perspective, sure. It adds a ton of complexity because we need to know what addresses to go to and what changes are done to the packages prior to them being delivered. From an open-shift perspective, that's partly going to be our digital transformation to transform that visibility and provide that information and bringing more products and services to those customers and lower latency of time. >> Okay, so containerization is something that's relatively prevalent for the audience here, but it's still relatively young in maturity. Just wondering as you rolled out the solutions, any learnings you had or any, you know, I don't want to say stumbling blocks, but you know, things that you learned along the way that maybe your peers should, could learn for. >> Yeah, I mean, I think you should say stumbling blocks 'cus as anybody knows, whenever you go through anything new there's opportunities to learn and there's monumental opportunities of failure and I think UPS knows and we've pride ourselves in failing fast, learning from our mistakes and getting to the next level. So like you mentioned with containerization and open-shift, the ability for us when we used to deploy every six months, now we get to deploy in two weeks to production and before that we could deploy in a matter of minutes so we could test all these tools and everything that open-shift offers gives us the ability to serve our business and give the most information to our customers. So open-shift and Red Hat have done a great job in helping us reach our maximum potential and we look to continue that partnership. >> Yeah, so was there anything, you know, in that speed to delivery and being more agile that, you know, "Oh jeez, security, "we should have pulled them in sooner." Or you know, so and so should have, but we forgot to include them in the original discussions. >> No, when we went through the transformation of moving the tracking application, we went through all the options and open-shift was just a natural partner, a natural fit. At the time we were going through a proof of concept with the product with another team and as the VI project came along it was just a natural fit to use containerization and use the speed of deployment, automated testing and pipelines in order to deploy this new application. (coughing) >> You used an interesting phrase there, for shit about failing fast and we've heard that a couple of times this week in different flavors. What about the lack of fear and failure and almost like that failure is not always a bad thing because it leads to improvement. But you have to have a certain amount of confidence underpinning that. So talk, I'm just curious from a company culture standpoint, what kind of confidence is there about that failing fast and how technology allows you to make up the ground that you might have lost by failure, especially in today's world, there's so much more capability and so much more at your disposal. >> Yeah, so I may, I think that benefits us and allows us to fail fast is management like Nish and our upper level management, they give us the opportunity to make these mistakes because they know we're going to learn from them and just talking about open-shift and like you said, when we fail, we have to make up that ground. When we make those mistakes the platform that we're on allows us to pivot from that and make it a success story right away. So we noticed that we were able to learn from mistakes quickly and with the help and support of management we were able to implement real-time solutions and deploy them right away. >> Yeah, in addition to that we're able to deploy in a short period of time so we know we're at a minimum two weeks away from the next deployment. So we could quickly restore functionality within minutes or within days if necessary. So, you know, previously we weren't able to do that, so fail fast didn't quite work in the waterfall method. >> So Nish, you know, the VI project has rolled out. What does that mean to your relationship to the business? And also ultimately, how has it impacted your ultimate customers? >> Sure, so from an external customer perspective, obviously we're able to, speed to market products and services faster to our customers and provide better visibility to the customers. From internally in the organization, we've significantly reduced our cost to serve and as we continue to transform on the VI platform using open-shift and partnering with Red Hat, we'll be able to transform other visibility products in the future and going forward we're able to take folks like Khurshid and develop them further and use our skill sets that we've learned and develop our people faster. >> So where do you want to jump in next? I mean, in your world Krashid, I would think that's probably one of the more exciting questions is, you know, what now? What next? Where are we going with this? In terms of your core business, you know, where's the efficiency gain that you'd like to see? Where's the customer service you'd like to improve? >> Yeah I mean, from a business perspective we're always looking to serve our business and bring products to platform that are gonna be useful to the customers. So what we currently have in VI today, we're looking to create more visibility products for our customers and from a technical standpoint, and we were at Red Hat Summit 2019, they've announced some crazy cool things. >> What's the craziest cool thing you've heard this week? >> We're looking forward to open-shift 4, we're looking forward to Cofcus Dreams, and Corcus which is really cool, and just operators, the list goes on and on. I could talk to you about it for days and days. We were here for three days, you got three more days ready? >> Sure. (laughing) Tape is cheap. (laughing) >> Yeah, we're looking forward to a lot of cool things that Red Hat's going to provide and we're gonna run with it. >> Yeah. We're looking forward to continued relationship with Red Hat and offering new products and services that can make our businesses run better. >> Like for example, if you could, if I were to say, a military build a rocket ship right now, you know, what's it gonna look like? What area of your business would you like to literally dabble in and say "Okay, I think this will work." It might right now, look to be a little bit futuristic or down the road, what scenario could you paint possibly to give us an idea about what you're thinking? >> So our next focus to business is to serve up the small and medium business, right? So we've been talking about the modulus product and serving residential addresses and serving residential folks but we want to start focusing on the small and medium businesses and offering the same services and capabilities so our next plateau, our next capability is to provide those services to the small and medium businesses so they can grow and partner with UPS. >> And I think, as Nish mentioned, with the utilizations from Cofcun actually bringing some of these technologies into our containers, bringing more security layers like there's a lot of great vendors here and partnering with them and bringing them into our services, it will open the doors for us a lot, and like Nish mentioned with my choice and small business, I think will allow them a better customer experience with partnering up with some of these new people. >> Presenter: You bet. Well thank you both. Thanks for being here and sharing your time, good to see you. Good keynote this morning as well, so please be sure to pass that along and we look forward to seeing you down the road. >> Developers: Thank you. >> Thank you both. Back with more coverage from Red Hat Summit 2019, you are watching theCUBE live from Boston. (electronic music)

>> Announcer: Live from Boston, Massachusetts, it's theCUBE, covering Red Hat Summit 2019. Brought to you by Red Hat. >> Welcome back here on theCUBE, joined by Stu Miniman, I'm John Walls, as we wrap up our coverage here of the Red Hat Summit here in 2019. We've been here in Boston all week, three days, Stu, of really fascinating programming on one hand, the keynotes showing quite a diverse ecosystem that Red Hat has certainly built, and we've seen that array of guests reflected as well here, on theCUBE. And you leave with a pretty distinct impression about the vast reach, you might say, of Red Hat, and how they diversified their offerings and their services. >> Yeah, so, John, as we've talked about, this is the sixth year we've had theCUBE here. It's my fifth year doing it and I'll be honest, I've worked with Red Hat for 19 years, but the first year I came, it was like, all right, you know, I know lots of Linux people, I've worked with Linux people, but, you know, I'm not in there in the terminal and doing all this stuff, so it took me a little while to get used to. Today, I know not only a lot more people in Red Hat and the ecosystem, but where the ecosystem is matured and where the portfolio is grown. There's been some acquisitions on the Red Hat side. There's a certain pending acquisition that is kind of a big deal that we talked about this week. But Red Hat's position in this IT marketplace, especially in the hybrid and multi-cloud world, has been fun to watch and really enjoyed digging in it with you this week and, John Walls, I'll turn the camera to you because- >> I don't like this. (laughing) >> It was your first time on the program. Yeah, you know- >> I like asking you the questions. >> But we have to do this, you know, three days of Walls to Miniman coverage. So let's get the Walls perspective. >> John: All right. >> On your take. You've been to many shows. >> John: Yeah, no, I think that what's interesting about what I've seen here at Red Hat is this willingness to adapt to the marketplace, at least that's the impression I got, is that there are a lot of command and control models about this is the way it's going to be, and this is what we're going to give you, and you're gonna have to take it and like it. And Red Hat's just on the other end of that spectrum, right? It's very much a company that's built on an open source philosophy. And it's been more of what has the marketplace wanted? What have you needed? And now how can we work with you to build it and make it functional? And now we're gonna just offer it to a lot of people, and we're gonna make a lot of money doing that. And so, I think to me, that's at least what I got talking to Jim Whitehurst, you know about his philosophy and where he's taken this company, and has made it obviously a very attractive entity, IBM certainly thinks so to the tune of 34 billion. But you see that. >> Yeah, it's, you know, some companies say, oh well, you know, it's the leadership from the top. Well, Jim's philosophy though, it is The Open Organization. Highly recommend the book, it was a great read. We've talked to him about the program, but very much it's 12, 13 thousand people at the company. They're very much opinionated, they go in there, they have discussions. It's not like, well okay, one person pass this down. It's we're gonna debate and argue and fight. Doesn't mean we come to a full consensus, but open source at the core is what they do, and therefore, the community drives a lot of it. They contribute it all back up-stream, but, you know, we know what Red Hat's doing. It's fascinating to talk to Jim about, yeah you know, on the days where I'm thinking half glass empty, it's, you know, wow, we're not yet quite four billion dollars of the company, and look what an impact they had. They did a study with IDC and said, ten trillion dollars of the economy that they touch through RHEL, but on the half empty, on the half full days, they're having a huge impact outside. He said 34 billion dollars that IBM's paying is actually a bargain- >> It's a great deal! (laughing) >> for where they're going. But big announcements. RHEL 8, which had been almost five years in the works there. Some good advancements there. But the highlight for me this week really was OpenShift. We've been watching OpenShift since the early days, really pre-Kubernetes. It had a good vision and gained adoption in the marketplace, and was the open source choice for what we called Paths back then. But, when Kubernetes came around, it really helped solidify where OpenShift was going. It is the delivery mechanism for containerization and that container cluster management and Red Hat has a leadership position in that space. I think that almost every customer that we talked to this week, John, OpenShift was the underpinning. >> John: Absolutely. >> You would expect that RHEL's underneath there, but OpenShift as the lever for digital transformation. And that was something that I really enjoyed talking to. DBS Bank from Singapore, and Delta, and UPS. It was, we talked about their actual transformation journeys, both the technology and the organizational standpoint, and OpenShift really was the lever to give them that push. >> You know, another thing, I know you've been looking at this and watching this for many many years. There's certainly the evolution of open source, but we talked to Chris Wright earlier, and he was talking about the pace of change and how it really is incremental. And yet, if you're on the outside looking in, and you think, gosh, technology is just changing so fast, it's so crazy, it's so disruptive, but to hear it from Chris, not so. You don't go A to Z, you go A to B to C to D to D point one. (laughing) It takes time. And there's a patience almost and a cadence that has this slow revolution that I'm a little surprised at. I sense they, or got a sense of, you know, a much more rapid change of pace and that's not how the people on the inside see it. >> Yeah. Couple of comment back at that. Number one is we know how much rapid change there is going because if you looked at the Linux kernel or what's happening with Kubernetes and the open source, there's so much change going on there. There's the data point thrown out there that, you know, I forget, that 75% or 95% of all the data in the world was created in the last two years. Yet, only 2% of that is really usable and searchable and things like that. That's a lot of change. And the code base of Linux in the last two years, a third of the code is completely overhauled. This is technology that has been around for decades. But if you look at it, if you think about a company, one of the challenges that we had is if they're making those incremental change, and slowly looking at them, a lot of people from the outside would be like, oh, Red Hat, yeah that's that little Linux company, you know, that I'm familiar with and it runs on lots of places there. When we came in six years ago, there was a big push by Red Hat to say, "We're much more than Linux." They have their three pillars that we spent a lot of time through from the infrastructure layer to the cloud native to automation and management. Lots of shows I go to, AnsiballZ all over the place. We talked about OpenShift 4 is something that seems to be resonating. Red Hat takes a leadership position, not just in the communities and the foundations, but working with their customers to be a more trusted and deeper partner in what they're doing with digital transformation. There might have been little changes, but, you know, this is not the Red Hat that people would think of two years or five years ago because a large percentage of Red Hat has changed. One last nugget from Chris Wright there, is, you know, he spent a lot of time talking about AI. And some of these companies go buzzwords in these environments, but, you know, but he hit a nice cogent message with the punchline is machines enhance human intelligence because these are really complex systems, distributed architectures, and we know that the people just can't keep up with all of the change, and the scope, and the scale that they need to handle. So software should be able to be helping me get my arms around it, as well as where it can automate and even take actions, as long as we're careful about how we do it. >> John: Sure. There's another, point at least, I want to pick your brain about, is really the power of presence. The fact that we have the Microsoft CEO on the stage. Everybody thought, well (mumbles) But we heard it from guest after guest after guest this week, saying how cool was that? How impressive was that? How monumental was that? And, you know, it's great to have that kind of opportunity, but the power of Nadella's presence here, it's unmistakable in the message that has sent to this community. >> Yeah, you know, John, you could probably do a case study talking about culture and the power of culture because, I talked about Red Hat's not the Red Hat that you know. Well, the Satya Nadella led Microsoft is a very different Microsoft than before he was on board. Not only are they making great strides in, you know, we talk about SaaS and public cloud and the like, but from a partnership standpoint, Microsoft of old, you know, Linux and Red Hat were the enemy and you know, Windows was the solution and they were gonna bake everything into it. Well, Microsoft partnered with many more companies. Partnerships and ecosystem, a key message this week. We talked about Microsoft with Red Hat, but, you know, announcement today was, surprised me a little bit, but when we think about it, not too much. OpenShift supported on VMware environments, so, you know, VMware has in that family of Dell, there's competitive solutions against OpenShift and, you know, so, and virtualization. You know, Red Hat has, you know, RHV, the Red Hat Virtualization. >> John: Right, right, right. >> The old day of the lines in the swim lanes, as one of our guests talked about, really are there. Customers are living in a heterogeneous, multi-cloud world and the customers are gonna go and say, "You need to work together, before you're not gonna be there." >> Azure. Right, also we have Azure compatibility going on here. >> Stu: Yeah, deep, not just some tested, but deep integration. I can go to Azure and buy OpenShift. I mean that, the, to say it's in the, you know, not just in the marketplace, but a deep integration. And yeah, there was a little poke, if our audience caught it, from Paul Cormier. And said, you know, Microsoft really understands enterprise. That's why they're working tightly with us. Uh, there's a certain other large cloud provider that created Kubernetes, that has their own solution, that maybe doesn't understand enterprise as much and aren't working as closely with Red Hat as they might. So we'll see what response there is from them out there. Always, you know, we always love on theCUBE to, you know, the horse is on the track and where they're racing, but, you know, more and more all of our worlds are cross-pollinating. You know, the AI and AI Ops stuff. The software ecosystems because software does have this unifying factor that the API economy, and having all these things work together, more and more. If you don't, customers will go look for solutions that do provide the full end to end solution stuff they're looking for. >> All right, so we're, I've got a couple in mind as far as guests we've had on the show. And we saw them in action on the keynotes stage too. Anybody that jumps out at you, just like, wow, that was cool, that was, not that we, we love all of our children, right? (laughing) But every once in awhile, there's a story or two that does stand out. >> Yeah, so, it is so tough, you know. I loved, you know, the stories. John, I'm sure I'm going to ask you, you know, Mr. B and what he's doing with the children. >> John: Right, Franklin Middle School. >> And the hospitals with Dr. Ellen and the end of the brains. You know, those tech for good are phenomenal. For me, you know, the CIOs that we had on our first day of program. Delta was great and going through transformation, but, you know, our first guest that we had on, was DBS Bank in Singapore and- >> John: David Gledhill. >> He was so articulate and has such a good story about, I took outsourced environments. I didn't just bring it into my environment, say okay, IT can do it a little bit better, and I'll respond to business. No, no, we're going to total restructure the company. Not we're a software company. We're a technology company, and we're gonna learn from the Googles of the world and the like. And he said, We want to be considered there, you know, what was his term there? It was like, you know, bank less, uh, live more and bank less. I mean, what- >> Joyful banking, that was another of his. >> Joyful banking. You don't think of a financial institution as, you know, we want you to think less of the bank. You know, that's just a powerful statement. Total reorganization and, as we mentioned, of course, OpenShift, one of those levers underneath helping them to do that. >> Yeah, you mentioned Dr. Ellen Grant, Boston Children's Hospital, I think about that. She's in fetal neuroimaging and a Professor of Radiology at Harvard Medical School. The work they're doing in terms of diagnostics through imaging is spectacular. I thought about Robin Goldstone at the Livermore Laboratory, about our nuclear weapon monitoring and efficacy of our monitoring. >> Lawrence Livermore. So good. And John, talk about the diversity of our guests. We had expats from four different countries, phenomenal accents. A wonderful slate of brilliant women on the program. From the customer side, some of the award winners that you interviewed. The executives on the program. You know, Stefanie Chiras, always great, and Denise who were up on the keynotes stage. Denise with her 3D printed, new Red Hat logo earrings. Yeah, it was an, um- >> And a couple of old Yanks (laughing). Well, I enjoyed it, Stu. As always, great working with you, and we thank you for being with us as well. For now, we're gonna say so long. We're gonna see you at the next Red Hat Summit, I'm sure, 2020 in San Francisco. Might be a, I guess a slightly different company, but it might be the same old Red Hat too, but they're going to have 34 billion dollars behind them at that point and probably riding pretty high. That will do it for our CUBE coverage here from Boston. Thanks for much for joining us. For Stu Miniman, and our entire crew, have a good day. (funky music)

>> Announcer: Live from Boston, Massachusetts, it's theCUBE, covering your Red Hat Summit 2019, brought to you by Red Hat. >> Well, good afternoon, welcome back here on theCUBE. As we continue live coverage from Boston. We're at Red Hat Summit 2019. I'm John Walls along with Stu Miniman. It's been so good to have you here for all three days of our exclusive coverage of this exciting event, great event it's been. We're joined by Joe Fitzgerald who's the VP of and GM management business unit at the Red Hat. Joe, good to see you sir. >> Good afternoon. >> Pleasure, thanks for having us here at this, and it's been a great show. I hope the same can be said from your side of the fence. I'd like to hear about that. we're talking earlier but announcements and whatever. Tell me, what's your feel for the flavor, what happened here, and all that you've heard in terms of the keynotes stage and some of the big news. >> It's really that I am a great bunch here. I mean we really had some big announcements. My area of management automation really complements the platform announcements that we made. As people are deploying stuff across really complex environments and multi clouds, management automation like becomes really important for them to keep all that running and compliance secure. So I'm pretty excited that my area was able to compliment the platform offerings that we announced in a really big way. >> Now, you look now you look ahead to the road coming, right? So this is new world, great opportunity, great challenge, but it I would think you guys a pretty jazzed about being central to that right? And becoming this kind of a new layer, new part, and new piece of that equation. >> Yeah, Red Hat's really, you know, at a key point in terms of IT infrastructures and what people are doing. You can definitely feel the excitement in our customers, in our partners that what they're trying to build and this is not the end, this is really the beginning of where everybody's going. I mean, really, the open chips announcements we made these are platforms that people are building the future on. So this story is really got a long way to go, right, and there is just a tremendous amount of excitement. We're really on the front edge of what people building, how they're digitally transforming their business. And they're building that stuff on our platform which is really exciting to see. >> So, Joe, you know when we look at some of the big themes we've been talking about here at the show, you know you mentioned some of the big announcements, but you know, the world is more heterogeneous and more complex than it ever was in a multi-cloud environment. And therefore if I look at management specifically, you know, we know in the IT industry it's been something that for decades we've been trying to talk about. How do I simplify things? When I talk to my friends that are admins, you know the joke is, how do you spell single pane of glass? You know P-A-I-N, never what you would think it would be. So, explain how in you know in this ever complex, multi-cloud environment, you know Red Hat is helping to progress the journey of management? >> Sure, so it's an area that is near and dear to me. So every time there is these great technological innovations, the platform, or the application, or the process level. There is a secondary effect which is the management changes, the physics of the environments change. And then the management has to adapt to those new physics. So as people are taking advantage of all these great new public cloud services, and private cloud services, and hyper clouds, and multi-cloud. The management complexity of trying to manage something that is now distributed across all different platforms and all kinds of management tools and interfaces and each one of those platforms. Somebody has to sort that out where that will become a barrier, to people trying to leverage that to advance their business. So Red Hat, is sort of in an interesting place, at the crossroads of things like analytics and automation, to help bring some technology innovations to helping to manage these really complex environments. >> You know, so, can you just put in a framework for us because if we say there are so many pieces of the stack and so many distributed environments, there have been management tools that have become central to administrator roles. You know, I think of if I'm a network person, there's you know certain company that is rather dominant in the space. Same thing when it came to server virtualization and today the multi-cloud where every public cloud has their own dashboards. You know, and the data center there are lots of tools so, you know, where does Red Hat fit in that overall picture? And you know, what would be different than people that know Red Hat from just a few years ago? >> Sure, so I think you know, Red Hat's philosophy of open hybrid is really key even in management. You know, each platform sort of has invested interest in sort of trying to lock you in and providing set of tools that selfishly manage their stuff but nobody else's stuff. Red Hat is really in the business about enabling hybrid cloud and hybrid applications across these clouds. And so what that means is that we have to provide management that enables them to cross those clouds and manage in a comprehensive, unified way. And a lot of management innovation is taking place in open, just like most other innovations. So some of the open innovation technologies like Ansible for example, right have like incredible growth in the community, and the kinds of automation we can do across all these clouds and across layers of the stack, totally in an open source solution is really amazing. >> So you talk about hybrid and you're talking about management and smart management in way here, but that seems to me like that should just come with the territory right? We're going to make you smart and we're going to have you, give you better tools to make sure that you have your efficiencies and your operations, and everything is going just as it should. Like that's like, duh. But yet, it's much more than that, I like curious about your perspective on truly what defines smart management, and how that comes into practice? >> Yeah so, smart management for us means an easy way for people to manage a state of systems that deployed across all these different kinds of clouds. Private, public, physical, virtual environments, it gets very complicated. And it sounds like it should be easy, right, to make smart management, but it's really hard to make something easy, when you have the level of complexity that all these environments sort of extrude, right? So it's hard, right? And what you've seen over the decades is that as the paradigms change, management technologies change along he way, right? So we're in the middle of sort of a paradigm shift in terms of how people think of automation. The speed, scale, and complexity of these environments is so high now, that you certainly can't do it with people. You know, following things around. You know, the speed at which vulnerabilities need to be addressed, or the way that things need to be deployed, or scaled up or down, or managed, it defies people running around. So it all has to be automated. You're seeing a lot of other technologies like analytics and AI type technologies being applied to take all the data from these environments, figure out what's going on and then turn around and drive automation into those environments. >> So, Joe, when I look at the keynote there is something that jumped out at me. You were talking a lot about the, going to cloud.redhat.com. They started out with a windows interface, which you know Satya Nadella is up on stage, but still being at the linux conference here is that the core underneath everything. You know, sure it's going mobile and you want to make sure everyone can do it, but, you know, maybe talk a little about the importance of, you know, working even from a windows standpoint and part of the overall SAS delivery model for how management works today. >> Yeah, so I think there's a couple things going on. First of all, you know, certainly in our consumer lives we're used to ease of use. You know, very simple interfaces whether that's voice, or mobile, or whatever it is. We need things fast and we need things easy. Okay, that crosses over into the management realm as well. Okay, we need to make things frictionless. We need to really take the time and the cognitive load off people trying to manage these environments. Okay, so what you saw in our announcements across the board was this, reduction of fiction, this ease of use, the simplicity in the way you build, deploy, and manage use these systems. Okay, which allows people to focus not on the task of build the infrastructure, which is very interesting, but actually advancing their business needs. You know, writing that next application, or scaling it, or you know, making changes to compete at speeds that you really couldn't do before because of the manual impediments and all the process changes. >> And how are the pressures changing, from the management side of the fence? Because of the volume of data, the number of transactions that are occurring, just that shear scope to me, puts a whole different kind of onus on the responsibility to make sure these processes are occurring naturally, and accurately. You got on one hand you're making some really big promises about how secure this environment is going to be, how effective it's going to be, and now you got to back that up. So it seems like you're shine, or at least your side of the fence, shining a little brighter light and putting a little burden on the backs of your tools and your folks. >> Well, so we're leveraging technologies. So for a case of, you know, of managing and securing these environments, using things like analytics. Like one of the things we announced this week was the ability with our Red Hat insights offering now which is bundled with RHEL, to be able to analyze these environments and figure out whether they have vulnerability, or performance, or reliability issues ahead of time predictively. And then be able to automatically address it and remediate it, that's really powerful. That saves somebody running a report to see which systems might have vulnerabilities and then trying to figure out what to do with that , and then scheduling some jobs to go fix some stuff, and meanwhile somebody has been going in their network or going into their systems quite some time. >> Right. >> So it's all that speed and leveraging technology that help do these things. >> All right so, Joe, glad you brought up analytics. Let's go back to that discussion of automation and Ansible. Help connect us the dots, you know, is there, I haven't heard like AI and ML. You know maybe Red Hat is trying to make sure they don't AI wash things too much, but where does analytics fit into automation these days? So, the future, I think is basically you know, we have a lot of data from these environments and all different levels of everything from the hardware, to the software, to the clouds, the apps, the usage patterns and things like that where a wash in data. Okay, so everybody is trying to bring analytics to things like their business, or bring it to things like infrastructure and things like that. There's an explosion of analytics use across, you know, every industry vertical, across technology. I see analytics coming up with tremendous insights into what's going on into environment or business. The next thing after that will be, I need to change something, or fix something, or scale up or down, or optimize, or do something. That backs into automation. So I think that, you know things like Ansible, are a natural to plug into analytic systems that come up with incredible insights, or actions that need to be taken. What's a standard way I can do that automation? Ansible would be my answer. >> Yeah so, you know, when I read some of the other analysts in the industry look at this space, they float out this term AIOps. Do you agree with that terminology? Is that fit into the framework you were just talking about? If not just taking the data, but being able to have that automation take action? >> Yeah so, I think it's a direction, you know, I think, you know, in the news recently there's been automation gone wrong. You see it occasionally where automation, if it's not, you know, doesn't have the right sort of checks and balances can do bad things really fast. Just like it can do good things really fast. So, I think that there's sort of a crawl, walk, run, for a lot of these things. Where people say, okay, you have this result from analytics or AI, it's recommending an action, let me confirm that, and I'll go ahead and take the action. Overtime people become more comfortable with these closed looped systems and then just say, okay, you know what you're doing there, go ahead and automate that. They can move on to a higher level, you know, function. >> Just one follow up on that, you know, RPA is something we've been taking a look at. It's a hot space and getting a lot of development. Are there any connections between what Red Hat's doing and the ecosystem with some of the RPA solutions out there? >> So it's sort of adjacent to the RPA space. You know, this year I would say automation is at the top of most enterprises list. And you know it's a spectrum of automating their traditional, sometimes legacy processes, to squeeze cost out. So they can move some of those people and some of that money to do their differentiating digital transforming, you know, applications, that are going to put them ahead of their competitors. Right, so we're seeing automations replace old tools that they have for perhaps, you know a decade or more, to the front edge where they're using our tools and you know devops tool chains to deploy things multiple times a day. Right? So, automation across the board I think is a high priority for enterprises right now. >> Can you make this easier for me? If you're writing all this great insight, right, and predictive analytics and but I've got data coming in from all kinds of places. And all of a sudden I've got to go find all these reports right? I've gotta, can you consolidate at all? Can you simplify my search if you will, or make my job of monitoring any easier just because maybe I have a lot more data coming in that I'm used to? I might want it a little more simplified, or at least laid out so it is a little clearer for me. >> Well I think there is two things going on. On the data side we're putting a lot more, you know, software in place to evaluate data and to get insights out of the data. Okay, on the automation side, you know, as we were talking about management tools over the years, there's been scripting languages and programming languages. And automation was really almost a programming exercise. One of the things that we've done in the Ansible environment is we sort of democratized automation. In other words, we made it easy for non-programmers to be able to do automation. So now I don't have to get programmers, which are expensive, and in short supply these days to write automation. I can expand that to ops teams and QE teams and I can democratize automation. So I think the physics there are putting more software, analyzing data, deriving insights. Whether that's machine learning, or full AI, or simple linear regression, and some other techniques, to get out of the data what's going on, and then turn that into actionable automation. >> Well congratulations to the Red Hat team. Good week. The summit I'm sure it went well for you as well and job well done, and good luck down the road. I know you've got your hands full now, but it's a good kind of full right? >> It's an exciting time to be at Red Hat and thank you very much. >> You betcha, thank you. Back with more from Red Hat Summit 2019. You're watching theCUBE. (upbeat techno music)

>> live from Boston, Massachusetts. It's the queue covering your red. Have some twenty nineteen brought to you by bread hat. >> Well, good afternoon. Where you might be watching us here on the Cube. We are live in Boston. Is we wrap up our coverage headed toward the homestretch? You might say of Red had Summit twenty nineteen. Want was to Mittleman. I'm John Walls. And thank you for joining us here. We're now joined by Ah, Louise, right. Bower, who was the vice president and chief technical strategists and head of innovation lab at Dinah Trees. And always good to see you today. Thanks for being with us. Hello. Thanks for having me s O software intelligence that that's your your primary focus. You've got headquarters here in the Boston area back in Austria. Tell a little bit about it. You would, Dina Trace. And I guess first off, what this news this week has met to you in terms of the release is and then maybe what you're doing in general. You know what Dina Trace is all about? >> Yes. Oh, that phrase has been around for, like quite a time. Started out as an a P M. Company. like fourteen years ago have been reinventing ourselves over and over again on DH. So we move from the traditional monitoring approach. So the innovation we had in the very beginning when we launched the first product was really would be practical, pure passer. The ability trace and went that way a lot about facing racing, like becoming super cool for micro services. So it would be like the first teacher we could be burying, doing, tracing before it was cool, like forty, fifty years ago. And then I was were involving the product more, more Skilling into bigger and bigger environments. So what's bigger and bigger mean? I remember in the beginning when we were working on environments who we're talking about, like one hundred host has a big environment like five hundred told that that's a big environment today, we say, for even one hundred thousand toast. Okay, it's a big environment, but they can't get even bigger then. The massive change was really for us five years ago, where way implemented our entire product offering, built the new Dina trays, Mr Focus, that we realize that okay, it's data and between people date and having them analyzed data is nice, but it's only getting you so far. So the more complex the replication get, more data you get to analyze. And it's just more exponentially scaling how many people you would need to deal with this. And that's why five years ago, we started to incorporate a I into our new court platform, then for automatic problem analysis. That's also where we're not just BPM. That's just what we call like the Dogg Tools data on glass tools to show a lot of data. Do some analysis on top of it. But it don't help you, too, really resolve a problem. So we used build in the eye, and that automatic would cause analysis again. Next teacher doing Aye, aye ops, affordable school like five years ago. Andi. The latest evolution. We also so again, and not a change in the way people are using monitoring tools. Um, we've invested a lot into building out in AP eyes don't see monitoring tools like be the Martin still here and the application over there, but having them monitoring who being highly integrated into the fabric fire eyes. So we have, As of today, eighty percent of our customers are using the product also via reprise, but tying them into operational automation. What we heard even today in the keynote here about a ABS and Howie iop starts to control and manage that form. More is becoming the intelligence or the back plane behind a modern native stack. >> So we have Chris right on. Who was in the keynote this morning? Came on our program this morning, too, when we talked about just the rippling effects of distributed architectures. I look at my applications there, you know, going to micro service architectures. You look at where's customers data? Well, lots of stuff all over the clouds and sass, and that has a ripple. Effect it to your space. You know, I hear observe, ability monitoring, you know, hack even bring up, like, you know, the civilised world. It becomes a whole separate meeting. So Donna Trace has been going through a transformation. You know, give >> us a >> point check ins to you know, where your customers are, how you're helping them move through this modernization and, you know, move to distributed architectures where that fits in >> so that their customers we focus on mostly are like Fortune five hundred customers who we work with. And obviously they have everything that exists on the planet. When we talk about self for like even from the mainframe to cloud native to serve less, as you mentioned here. And they were in this transition process right now, like modernizing their applications, which, as a necessity, we all want to move fast. There we want therefore flexible architects is we want to build more enough innovative products but at the same time to realize that this is also a message business risk behind following this approach. Think about you in the role of the CEO and say where we're going to modernize our architecture. We're going to rebuild everything we platform and so forth. You can if you succeed. Everybody would say you had. Yes, you did what you had to do. I mean, sorry if you failed, you failed. It's s so for them, it's a It's a big risk to move down that route and retired to take that risk out of the process as much as possible. Really Starting, obviously was monitoring their traditional sex, as they have to today, but really supporting that along that entire journey to a cloud native architecture er, starting with what we referred to as our support for monoliths to micro service architecture's. So Theodore is basically you don't want to rip apart the replication and figure out how it's going to work in my purse services world. But we have to technology that's called smart scape smart. Skip Moelis bills a real time, all of your entire data center and old applications running into it. And it was virtually that sect. You're marvelous, you came. How would they look like in a microt services architecture without catching any codes and then making it work? So once you've done this once, you've decided to move there the next step? Obviously, yes, you could have rebuilt that application. Usually we see applications with micro services architectures being significantly Mohr complex or more distributed by the sign that a traditional that you might have Web server application, Teo Database Server. Now you might be talking about maybe two hundred micro services or more so twenty times ranges. Writer on this under under lower bound here, which means that your traditional operational approach up okay, it's either the database of observer. The application server doesn't work anymore. on top of this. You did all of this to deploy fast. Like for like, bi weekly releases, even maybe daily off, like a smaller granularity. So you were reading a lot of entropy to that system and you have to analyze way more data. Did he ever had to do before? And this is where we kind of getting to the level where theoretically humans could do it. But it would just take us too long where the Holy I ops capability come in where we let let the machines that a monitoring tto take care of it at that level. So we helping them to operation US thieves processes and then really supporting them along the whole journey, where every customer we talked like this vision. But we're also here today in the keynote of an autonomous cloud and with carbonated, we already made a great step in this direction, looking at the interest, actually, like today say, I need five replicas off this container. I don't know, given that it's does it open shift and specifically here, it's going to happen. But if we move to the application layer is a lot, that has to be done and it has to make it easier for people to do. And that's where we tied into the entire customers. Ecosystem toe, automate like their cloud environment and have actually built a practice around which we call autonomous cloud management that we have been working with with customers on to enable them to achieve this over time. But it's going to be a lot maturity there. >> Yes, I mean, so what it talked about that you know, a CIA autonomous cloud management. What exactly you know, is that and how are you bringing that to your customer >> base? Autonomous Cloud Management resulted out off two different areas. The first one was when we were implement re implementing our platform. What I mentioned before, one step for us was to move to the SAS platform, and we looked at all the operation practices that were around back then, you know, we don't want to tell the doc I really don't want to do it. Like having people twenty four seven look at dashboards, then goingto a wicky, then reading a description of how to fix the problem. If you're the engineer, that why why do we do this this way? Must make any sense. So we developed our own practice, which we referred to as no wops. I know it doesn't mean that you're not doing operations. That would be pretty crazy, but not doing this traditional Naga type of operation, sitting there staring at a screen twenty four seven and then mentally executing any operation. So we had our own practice that we've built around it and, quite frankly, which has spilled it because we needed it for ourselves, and then we kept talking to customers and partisan, he says. Really cool what you did there like, Oh, how did you do this? What's like yourself? Respect behind this and what does the practices? What do your process? What's the culture change? So we were engaging with some customers, and then we were seeing that some of our customers back then, even we're doing bits and pieces off. This isthe well because there's a lot of practice and a lot of knowledge around. How did the autonomous count management and at the same time that we talked about the other customers who not yet on a charity who definitely want to get there? But I'm not quite sure how to do it, and I don't want to figure it out themselves. So we thought, Okay, let's take all of these best practices that we have and build more or less a methodology around it. How to make this actually works like how to do this. We really broke it down into, like, individual sprints to distance sprint one that distance sprint to to really have the results within three months, six months, twelve months. Whatever the cases that you want to run on. And then we realised talking to customers. This by itself isn't still enough. So that's why we started to open up this to an entire ecosystem. So WeII brought ecosystem partners along, like working closely with read a lot of our companies, but also system integrators who can help us. We speak of projects because we as a company, our software companies were not a services are consulting company, and we do support customer that some of those engagement. But if you think of like a really Fortune five hundred company that's a multi approaches, it will keep hundreds of people busy. So to recap like built in methodology, we built ecosystem to deliver on that promise at scale. And now the last step was we were doing this. We also built like a reference architecture for it, and I was just in an eternal ideas. So how do we, like structure this building reference architecture and then realized Okay, It's kind of like super helpful for customers. So that is why we don't decided to open source this reference architecture this fabric as well, too, like the tires after community, so they can also use it. So technically, stability is three pieces. It's the methodology, it's the ecosystem. And it's like the reference architecture that you can work with to help you, Chief. Go. >> All right, um, tell us how your a I fit into this. I've heard some analyst firms are saying, you know, some of the next generation of your space could be a I ops. Do you consider yourselves moving in that direction, or do you have some counter view on that? >> I think today a lot of things ar e I upset my now b a i ops, and it's a very undefined goal. This mentioned earlier. We decided to have aye aye based algorithms as powerful platform five years ago and nobody back then was talking about the layoffs. Funny story. Some of our competitors even told us you can't use the eye for monitoring just like totally stupid that there are other companies that they were doing it. But again, so the whole industry is learning here. I think it's really about data analysis. If you look at, if you scare the bigger and bigger environment, you really have to look at the process off what human operations people are doing on. There's obviously some hard decisions that you have to take their have. You have to work with teams to resolve our problems. But the biggest portion is really data analysis interpretation, right and a lot of this can be put into, and a I component that doesn't What's the Dyna trees, eh? I does it more. This is like your saree in codes, so to speak, which is able to find what's broken in the education, what was related to an issue in the application and being able to automatically find the root cause. Very importantly, we're kind of like opinionated and how in a I for operational practices should be working because one thing you don't want it serious you want? Don't want it happening. Iop system tell you well, you should. We start this service because some neural and that were told to do so. That's a building, a lot of confidence. That's why our approach is really tio follow. Like what we call a deterministic a pia a sari. And hey, I did it able to explain back to the user White came to a certain conclusion. So why should their we sort this herb is west of the rollback, this deployment or why that's the I b. Believe that if I fixed this problem, then like the bigger problem will be solved. So that's our approach, Teo T. I actually started like, roughly four years ago, five years ago, even a bit more than that on you. And I think that have a lot of experience, really rolling it out its scale and seeing it will help people because the next the ultimate next question, without always Scott Wass. If you wanna know what the problem is, why don't you fix it? And that's exactly the conversation you want to have, maybe just briefly at here, because it usually comes up okay, f a I and isat replacing people's jobs? I don't think so. We also heard it in the keynote today from Chris. It's augmenting our capabilities. There's hard decisions that you have to take, but just going through tons and tons of data. It's not going to your isn't very often when we talked at operations team or almost every time. First of all, you can't hire enough people anyways to get all the old done that's on your plate. Secondly, um, just by the amount of data and the time that I had to react. It's just long with a human understanding scenario way. Do this demo on self healing, often application. Where were deployed, something broken into production and have it being rolled back and we can do fifty one seconds. No human can do it that fast. That's just what pure, softer automation can do for you. So I think that then you can focus on other areas and more important, new project with us people in on the off space. What's what the three projects that you want to work and you never have time to work out and usually come up with the list. Yet this is what we give you back that time to work on exactly the things that move your business forwards. You >> said fifty one seconds. You've never seen Stew in action. You still have a lot of confidence. >> Well, we we love the machine, enhance human intelligence. You're definitely We could all use those machines to help us all get away from the drudgery and be able to do more. >> Always safe travels. Thanks for being with us. Headed back to Austria. Say, hide all your folks back in Austria, right There always is on his way home on his way to the airport. Thank you for being with us here on the Cube. Thanks. Appreciate the time our coverage continues here. Red hat some twenty nineteen. You're watching the cube?

>> live from Boston, Massachusetts. It's the queue covering your red. Have some twenty nineteen brought to you by bread. >> Welcome back to the Cube. Continuing coverage here read. Had some twenty nineteen day three of our three days of covering some nine thousand attendees, great keynotes, great educational sessions and a couple of great guests for you to meddle. And John Walls were joined by Marco Bill Peter, who is the senior vice president of customer experience and engagement at Red Hat. Good to see you, Marco. Thanks for having the job on the keynote stage this morning. And Dr Christoph back, who was the head of infrastructure from Hilty and Christof. Thank you for being here is Well, thankyou. Hailing from from election Stein. And we think you're the first guest alum were to check our database, But But we've set a new record today. So thanks for adding to our having. First off, let's talk about Hilty. I'm sure people don't stay healthy. I've seen them, but this building probably wouldn't be here without you. Have imagined half the city wouldn't be here without you. But just tell folks at home a healthy a little bit about where you fit into the construction. >> Lt was founded in the nineteen forties in principality of a Lichtenstein as and is now today leading supplier for the construction industry. We provide tours, consumables, services and software solutions for professional construction companies. Daddy's from hammer drills, two anchors to calculation software and overall complete services for the industry. That's what hell is doing. >> So you did a very good job this morning on the keynote of painting that picture about about the scope of your work and the necessity of your work, the vitality of it. Because construction projects, as we all know, how very strict deadlines. Sometimes they have unique needs. They have immediate needs emergency needs, and you're in the center of all that. And so your technology is central to your general operation. >> Absolutely yes. I mean, with twenty five thousand or twenty nine thousand employees, twenty five thousand users in our system, basically, everybody's using everyday ASAP or the fast majority of users. We have ten thousand concurrent users every day on our system. That deal with customer requests with orders with quotes, but also, of course, with complaints with repair handling and so on. In >> just a few. Yeah, just >> so Marco, I hear ASAP and, you know, bring me back to when? Oh, well, you know, Lennox was that stuff that sat on little sidelines. We're well past that. You've got so many customers that run their business, you know, mission critical around the globe. Just give give, give us a little bit of background on the partnership with Hilty and Red Hat and Solutions like asap. >> Yes, sure. Yeah. The Department of Hilty goes back to, I think, two thousand seven for me. Personally, I started working with Hilton for another company in ninety three. So I know where the hell did Quite well, actually studied in the same town next to Lichtenstein, Son of the mail. And And it's it's amazing to see the journey kind of two thousand nine going all s ap mission critical on rail and now actually moved to Asa P s for Han. And yes, Hill is one ofthe declines. But it kind of talks that we can handle this mission. Critical applications are mission critical customers and built this good relationship to make sure they have these these courage to actually do this Bold jumps limited The last six months. >> Christoph, you know you've got a broad, you know, roll at the at the company way talked to so many companies on becoming a tech company on becoming a software company. Well, software is critical, but at the end of the day, you know, infrastructure and running your business is core. You know, you're not going to become a fully digital software. You have real stuff in the physical world that lots of people and lots of, you know, physical things that need to go to a little bit about that balance. And now the company has been changing over those last ten years. >> I was excited to be open with you. I was really excited when our executive board a couple of years ago, besides tools, consumables and services also added software into a strategic pillar for Hilty. Um, and while I believe that software will be an interesting pillar for us, well will generate additional revenue, will generate additional sales from early. Also in the consumables and tools and services piece software becomes more and more important when you look at the journey off building a building like this. As you mentioned John, I mean it starts with specifying it starts with the planning on CD, and it ends at the end with with Asset Management. Where are the tours and so on. So it's a complete life cycle through out the building off off throughout the construction of ah building. You >> know, Marco had mentioned that you made this decision to migrate Ohana last year right? Twenty eighteen or or where he might be rated last year? Isn't last year's decision made before that? Talk about that a little bit, if you would please and where Red Hat fit into that? Because that that's that's not a small decision, right? I mean, that's a That's a very calculated and I wouldn't not risky, but it's It's just a big move. Yeah, and so the confidence that you had a CZ well, that red hat was your partner to make that happen. >> Absolutely. I mean, the announcement of SAPI to support Hana as thie only database after twenty twenty five voice one off the factors to push us into that direction, that that was then clear for us that we want to go there. And it was also pretty clear for us that in our size it was not that easy to move in twenty twenty three or something like that in that direction, but that we have to be the first movers to be fully supported by ASAP and >> all >> these Parkins because later on, they will be busy with migrating all the big shots. So Wade took the decision to move first and soon, and that allowed us to be in the focus off all thes attached partners ASAP. But also read had also tell emcee for storage and HP for for servers. That meant that we had confidence that we have full attention from all these providers and partners to help us to migrate. On the other hand, it was clear the the the journey we started in two thousand nine has indicated by Marko that we moved to an open software that we move to commodity hardware. Intel based server hardware was a move that had paid off in the past, and we didn't want to go away from that and move again to a proprietary hardware or software solutions. So it was very clear that we want to do that jointly with red hat on commodity and until based service and That's how we went there, Right? >> So, Christophe, big theme, we hear not only at this show, but almost every show we go to is today customers. It's, you know, the hybrid and multi cloud world I see ASAP at all of the Big Cloud shows that that that we cover well, we're just cloud fit into your over discussion, you know, at your company. And then, you know, we can drill down to the specifics of that sapien red hat. But it's what do you have? A cloud strategy, as it were? >> Oh, yes, you know, we moved fairly soon to Amazon with all our customer facing workload. So when you go to hilton dot com or any of our Web pages, you typically land on a ws powered website because that one gave us the flexibility off operating systems off databases of whatever we needed. That was that was available there with our internal workload. However, So all the software we use Internet eternally toe run the company. We have a world that is split between ASAP, which runs entirely on Red hat, um, and the rest of the workload. Witches to a large degree, windows based workload so there. We decided a few years ago to Movinto Microsoft Azure platform to move the internal workload into Azure as it is mainly Windows based. >> So Marco actually want one a depart from healthy for a second. Just give us a little bit of a broad view. You know, we've talked to you many times. You talked about the stage. You know, the customer experiences a critical piece of red hats mission out there When I talk to customers today, One of the biggest changes they've seen the last few years is I'm managing a lot of stuff that's not in my environment. It's the stuff I'm responsible for it and something goes wrong. I'm absolutely getting a call, but you know, it's not my network. It's not my servers. It's not my piece there, but I have to do all of them, you know, got imagine. That's been a transformation for red Hat in the partnerships, and you're everywhere, so it just gets a little context. Yeah, I >> mean, you described it very well, right? I mean, I think the last two years before, I think it was just like some use cases in the public club. But today. The harder cloud is here, right? And everybody does it right. It's not like just one company from a customer experience to stand behind. Like I mentioned it on the state gets harder. Right? And you gonna have these partnerships, right? One partnership, right. We can talk about the azure. We have people in enrichment, right? Think about it today. And then everything changed with start having on stage here. But we have support people in micro for the last two or three years, right? Same diff ASAP as an example, right? We have people. We actually build a fairly large teeming, involved off to be close of us. Time together. I want to do that speed ASAP. A cloud bead on regular bear closes in general. Yes, That challenges. You mentioned networking, right? It gets tricky, right? And he shifted from, but it's unavoidable, right? It shifted from, like, okay, we own and control the stacked kind of too. Yes, you need to know you're open source after and to have really partnerships. Right? And I think the announcement Microsoft, too have this managed services offering that we do joint. It's That's what we're driving so that we can do this better together with partners. >> Marco is great to hear you that but Christoph, he's not listening. Tell us to reality. You've worked with Red Hat for ten years. You're going to cloud how they doing? How's the ecosystem, the vendors in general? They're all up on stage, holding hands. I mean, it's it's seamless and nobody ever point fingers. I'm sure >> to be very, very honest with you. I mean, I appreciate it last year, hearing that redhead will be offered in Azure. I mean, that was not possible to mention those two company names in one sentence in the past, at least for us as customers, and that that was a bold statement last year that those two parties will suddenly join. That fits very well in our strategy, because we believe internal workload for Hilton should run in in In Azure seeing on last Tuesday, Microsoft and Red Hat shaking hands and movie. Even beyond that one was, for me, them almost the most exciting event here, or the most exciting statement that I saw here during these few days because that reemphasized the close relationship that those two have, and that exactly fits our road map. That's exciting. >> And, you know, we heard that, you know, again from from both CEO Saying customers really kind of brought us together. They made this deal work because we kept hearing that they love us and they love you, and they like us together. So So we got that. We understand that. So? So Marco customers drove that to a certain degree. You've got a customer here who made this big Hana jump, which is you say small guy. You know, I would beg to differ little bit that you had him before the big guys did. But what, like an initiative like that? What is that doing for you? What? Red hat. In terms of carrying that over to other customers. Now, you've learned from one you've seen what they've gone through. What kind of confidence does that give you? What kind of interest does it give you about how to approach this game? >> Absolutely. You know what we learned from give you one example right? If you moved his heart ever closer Christopher Hilty uses systems have twelve terabytes memory. Think about it that fairly large systems and that foot train tried to actually test our softer with that footprint and then even think about the next. Next journey is in if you want to do this in the cloud. What does that mean? If you take a twelve terabyte image and running in a double? Yes. And so that is, since my team also does quality assurance and product security. That's for them as well as in. Okay, we've seen what tilted can do work. How do we actually make this more robust? How do we test you are there? And how do we do that in this journey? It's, I think I'm pretty proud of how we actually learn from these instances, and health is not the only one. It's just one the republic. But yet it's every time. I think that's the only survived is into industry. If you really learn continuously and also applied right. I mean our whole setup involved or we shifted completely and not just from the people. They have theirs. So we have people that do open. Chief. There were people do Lennox and performance, but also from structure. I really be sure that they were set up for success and know what the next they have customers is obviously every casting off. A message we will do will go through a journey license over the next ten years. >> Kristoff obviously being on stage, you know it is good for the company, but coming to Red Hat Summit one. Just give our audience that if they hadn't come to it. Some of the value is, too what you place in some, the activities that have excited you most here this week. >> I mean, one thing is, of course, hearing about latest technologies, new releases, off software, off new possibilities and opportunities for us as customers from Red Hat. But also, it's great to see how on the floor out there other partners customers on DH fingers mingle around the ecosystem that created that was created around open software about, ah, not only operating system, but also about containers about all these those different technologies, which I have an important role for all of us in nineteen the future. >> Sure. Well, good week, that's for sure. Very nice job you get on the Kino stage to both of you and good luck with the partnership on down the road. And again, I would make the difference that way. little guys got in early hilt. He's no small fry in inner world, that's for sure. Thanks for the time, Krystof. Marco. Thank you. Thank you very much. Back with more. We're live here in Boston and we're covering the red hat. Summer twenty nineteen on the

>> Voiceover: Live from Boston, Massachusetts, it's the CUBE. Covering your Red Hat Summit 2019. Brought to you by Red Hat. >> And welcome back to our coverage here on the CUBE Red Hat Summit 2019. We're at the BCEC in Beantown, Boston, Massachusetts playing host this week to some 9000 strong attendees, pack keynotes. Just a great three days of programming here and educational sessions. Stu Miniman and I'm John Walls. We're joined by Mike Piech, who's the VP and general manager of Middleware at Red Hat. Mike, good to see you today. >> Great to be back. >> And Mark Little, VP of engineering Middleware at Red Hat. Mark, Good to see you as well, sir. >> You too. >> Yeah. First of, let's just talk about your ideas at the show here. Been here for a few days. As we've seen on the keynote stage, wide variety of first off, announcements and great case studies, great educational sessions. But your impressions of what's going on and some of the announcements we've heard about this week. >> Well, sure. I mean definitely some very big announcements with RHEL 8 and OpenShift 4. So as Middleware we're a little bit more in sort of gorilla mode here while some of the bigger announcements take a lot of the limelight. But nevertheless those announcements and the advances that they represent are very important for us as Middleware. Particularly OpenShift 4 as sort of the next layer up from OpenShift which the developers sort of touch and feel and live and breathe on a daily basis. We are the immediate beneficiaries of much of the advances in OpenShift and so that's something that, we as the Middleware guys sort of make real for the enterprise application developer. >> I'd say, probably for me, building on that in a way, one of the biggest announcements, one of the biggest surprises is gotta be the first keynote where we had Satya from Microsoft on stage with Jim announcing the collaboration that we're doing. I never believed that would ever happen and that's, that's fantastic. Has a benefit for Middleware as well but just for Red Hat as a whole. Who would've thought it? >> John: Who would have thought it, right? Yeah, we actually just had Marco Bill-Peter on and he was talking about, he's like "Look, we've actually had some of our support people up in Redmond now for a couple of years." And we had Chris Wright on earlier and he says "You know, sometimes we got to these shows and you get the big bang announcement. It's like, well, really we're working incrementally along the way and open source you can watch it. Sure sometimes you get the new chipset or there's a new this or that. But you know, it's very very small things." So in the spirit of that, maybe, you know, give us the updates since last time we got together. What's happening in the Middleware space as you said. If we build up the stack, you know, we got RHEL 8, we got OpenShift 4 and you're sitting on top. >> Yeah. Well one aspect that's an event like this makes clear in almost a reverse sort of way. We put a lot of effort particularly in Mark's team in getting to a much more frequent and more incremental release cycle and style, right. So getting away from sort of big bang releases every year, couple of years, to a much more agile incremental again sort of regime of rolling out functionality. Now, one of the downsides of that is that you don't have these big grand product announcements to make a big deal about in the same way as RHEL just did with 8 for example. So we need to rethink how we sort of (Laughs) >> absence the sort of big .0 releases, you know how we sort of batch up interesting news and roll it out at a large event like this. Now one of the things that we have been working on is our application environment narrative. Right now, the whole idea of the story here is that many people talk about Cloud-Native and about having lot's of different capabilities and services in a cloud environment. And as we've sort of gone through the, particularly the last year or so, it's really become apparent from what our customers tell us and from what we really see as the opportunities in the cloud-native world. The value that we bring is engineering all these pieces together, right? So that it's not simply a list of these disparate, disconnected, independent services but rather Middleware in the world of cloud native re-imagined. It is capabilities that when engineered together in the right way they make for this comprehensive, unified, cohesive environment within which our customers can develop applications and run those applications. And for the developer, you get developer productivity and then at runtime, you're getting operational reliability. So there really is a sort of a dual-sided value proposition there. And this notion of Middleware engineered together for the cloud is what the application environment idea is all about. >> Yeah. I'd add kinda one of the things that ties into that which has been big for us at least at summit this year is an effort that we kicked off or we announced two months ago called Quakers and as you all know a lot of what we do within Middleware, within Red Hat is based on Java and Java is still the dominant language in the enterprise but it's been around for 20 years. It developed in a pre-cloud era and that made lots of assumptions on the way in which the Java language and the JVM on which it runs would develop which aren't necessarily that conducive for running, in a cloud environment, a hybrid cloud environment and certainly public cloud environment based on Linux containers and Kubernetes. So, we've been working for a number of years in the upstream open JDK community to try and make Java much more cloud-native itself. And Quakers kind of builds on that. It essentially is what we call a kub-native approach where we optimize all of the Middleware stack upfront to work really really well in Kubernetes and specifically on OpenShift. And it's all Java though, that's the important thing. And now if people look into this they'll find that we're showing performance figures and memory utilization that is on a per with some of the newer languages like Go for instance, very very fast. Typically your boot time has gone from seconds to tens of milliseconds. And people who have seen it demonstrated have literally been blown away cause it allows them to leverage the skills that they've had invested in their employees to learn Java and move to the cloud without telling them "You guys are gonna have to learn a completely new language and start from scratch" >> All right, so Mark, if I get it right cause we've been at the Kubernetes show for a bunch of years but this is, you're looking at kinda the application side of what's happening in those Kubernetes environment >> Mark: Yeah. So many times we've talked about the platforms and the infrastructure down but it's the the art piece on top. Super important. I know down the DevZone people were buzzing around all the Quaker stuff. What else for people that are you know, looking at that kinda cloud-native containerization space? What other areas that they should be looking at when it comes to your space? >> Well, again, tying into the up environment thing, hopefully, you know, you'll have heard of knative and Istio. So knative is, to put it in a quick sentence is essentially an enabler for serverless if you like. It's where we're spinning containers really really quickly based on events. But really any serverless platform lives and dies based on the services in which your business logic can then rely upon. Do I have a messaging service there? Do I have a transaction service or a database service? So, we've been working with, with Google on knative and with Microsoft on knative to ensure that we have a really good story in OpenShift but tying it into our Middleware suite as well. So, many of our Middleware products are now knative enabled if you like. The second thing is, as I mentioned, Istio which is a sidecar approach. I won't go into details on that but again Istio the aim behind that is to remove from the application developer some of the non-functional business logic that they had to put in there like "How do I use a messaging service? How do I secure this endpoint and push it down the infrastructure?" So the security servers, the messaging servers, the cashing servers et cetera. They move out of the business logic and they move into Istio. But from our point of view, it's our security servers that we've been working on for years, it's our transactional servers that we've been working on for years. So, these are bullet-proof implementations that we have just made more cloud-native by embedding them in a way in Istio and like I said, enabling them with knative. >> I think we'd mentioned that Chris Wright was on earlier and one of the things he talked about was, this new data-eccentric focus and how, that's at the core so much of what enterprise is doing these days. The fact that whenever speed is distributed, they are and you've got so many data inputs come in from, so to a unified user trying to get their data the way they wanna see it. You might want it for a totally other reason, right? I'm just curious, how does that influence or how has that influenced your work in terms of making sure that transport goes smoothly? Because you do have so much more to work with in a much more complex environment for multiple uses that are unique, right? >> (Mike) Yeah. >> It's not all the same. >> Huge, huge impact for sure. The whole idea of decomposing an application into a much larger number of much smaller pieces than was done in the past has many benefits probably one of the most significant being the ability to make small changes, small incremental changes and afford a much more trial and error approach to innovation versus more macro-level planning waterfall as they call it. But one of the implications of that is now you have a large number of entities. Whether they be big or small, there's a large number of them running within the estate. And there's the orchestration of them and the interconnection of them for sure but it's a n-squared relationship, right. The more these entities you have, the more potential connections between each of them you have to somehow structure and manage and ensure are being done securely and so on. So that has really driven the need for new ways of tying things together, new ways essentially of integration. It has definitely amplified the need for disciplines, EPI management for example. It has driven a lot of increase demand for an event-driven approach where you're streaming in realtime and distributing events to many receivers and dealing with things asynchronously and not depending on round-trip times for everything to be consistent and so on. So, there's just a myriad of implications there that are very detailed technical-level drive some of the things that we're doing now. >> Yeah, I'll just add that in terms of data itself, you've probably heard this a number of times, data is king. Everything we do is based on data in one way or another, So we as Red Hat as a whole and Middleware specifically, we've had a very strong data strategy for a long time. Just as you've got myriad types of data, you can't assume that one way of storing that data is gonna be right for every type of data that you've got. So, we've worked through the integration efforts on ensuring that no sequel data stores, relational data stores^, in-memory data caching and even the messaging services as a whole is a way of sto^ring data in transit, that allows you to, in some ways it allows you to actually look at it in an event-driven way and make intelligent decisions. So that's a key part of what anybody should do if they are in the enterprise space. That's certainly what we're doing because at the end of the day people are building these apps to use that data. >> Well, gentlemen, I know you have another engagement. We're gonna cut you loose but I do wanna say you're the first guests to get applause. (guests laugh) >> From across all the way there. People at home can't hear but, so congratulations. You've been well received already. >> I think they're clearly tuned in to the renaissance of the job in here. >> Yes. >> Thank you both. >> Thanks for the time. >> Mark: Thanks so much. >> We appreciate that. Back with more, we are watching a Red Hat summer 2019 coverage live on the CUBE. (Upbeat music)

>> live from Boston, Massachusetts. It's the you covering your red hat some twenty nineteen brought to you by bread hat. >> Welcome back to our continuing live coverage here, read. Had summat. Twenty nineteen. You're watching Cube. I'm John Wallis along with stewed minimum. Nice to have you here with us as we head toward the homestretch. Day three of our three days of coverage here on the Q. We're now joined by a couple of guys who they put on their traveling shoes to get here, both hailing from Sydney, Australia. Gilman, pull a Matisse who's a senior innovation lead at Optimise and Vasily Check Culkin, who's a principal software architect, also adopted, which is the second largest mobile phone service provider in Australia. Gentlemen, thanks for being with us. Thanks, fiving. It's a long way to come, right? >> Yes, it is, but it's very worst trip. >> Excellent. Well, you're both on the keynote stage this morning. We'LL talk about that in just a little bit for folks who might not be familiar with obvious once you tell us a little bit about your footprint in Australia and what brings you here to talk about red hat and open >> shift well as you mentioned the obvious is a leading telco in Australia way are lucky that we own our infrastructure, which makes it a fantastic place As software engineers or infrastructure engineers working a CZ, we can develop new products and new solutions or innovate. It was in this network. Um all roles for the city and I adopted is essentially to identify new opportunities to innovate within our networks. We use our core I sets to innovate, but not on ly Just do this research and development also execute on this way. Call this a bit of an applied innovation where a ninety we would work really hard in in taking it, Teo to realise come but live writing on Colossus. >> So we're having a lot of stories with customers about transformation and telecommunications is one that's fascinating to look at because, you know, you work on software, you know, when I think back to tell Comet was, you know, fiber and towers and you know, physical implementation. But, you know, software, such a large part of what's going on. You tell us some of the changes going on and you know what's impacting your role in Annapolis? >> Uh, it's it's impacting all. Tell CAS actually, but yes, kill Cosa Switching from this old mine set off just fathers just hours. And this is Dan movements and five hundred Carmen, which is driving a lot of changes. People start thinking about social network functions and how we can dip alone on edge. How we can help our customers and developers to collaborate on next features how we can leverage although technologists and a state we have. >> I think if you think of software defined network and they moved to naturalization, you can now think of this. Australia is a big country that so you can not think of this entire infrastructure is being virtualized and could be made available for Also use a CZ well, so it's really changing that sense that it's not closed anymore and you can open to new cases. >> You know, you bring up it. Just a point about the pure geography of Australia. Huge country. Twenty five million people. No way would jealous here in the States, you had twenty five just, you know, in the Boston New York area. Probably I would think somewhere around there, but house that factor and just in terms of your operations in general that you do have nine million subscribers spread out over so much geography on dure trying to deliver the state of the art circuit service. Just, >> I said I couldn't take this one. So in terms of distance that there is an important impact. But what Today we were talking about phone calls. Video is essentially managing infrastructure, and you know, it's such a large country as its challenges. But it's something we're getting very good at a CZ. We pushing very hard to be present in regional Australia so you can sink of this beautiful landscape in getting five of there being a challenge, but with challenges that they did. The luck that comes with this is that we get to a parade, a scaled network, maybe not with the scale of subscribers that you have in any US, but we're the same challenges. So when it comes to innovation way, get the opportunities to way find you. >> So in the keynote, there was a lot of residents in the audience when you, you know, talked about breaking the language barrier. Maybe, you know, go in share with our audience here, just a tidbit as to what you were talking about. How that works from a technology standpoint. Roll >> out from technology. A point off you telephone you're stuck is it's complex thing. And if you want to integrate directly this telephone system directly with a phone call, it's our job. Okay, I did it. It's tough we did it. I'm never getting so. And the software developers what we tend to do when the get some complex things to solve. We obstructed away, and for us it was off the solution. We need to obstruct away all this complex ing all complex signaling nadiya handling and a very simple way off getting additional voice services within phone call. It's additional challenges like distance, and you can't just kind of older in the cloud because we need to be close to the customer. Otherwise, it will be very, very but quality. Always what and yeah, and it's opens availability toe innovate further, we can bring more services, not only voice, translation and transcription, but just think about it. You got your voice. We can help you. We can like new exciting services on plain old. >> So we had translate today and that we were here to talk about the technology may also the culture changed around. If on network becomes more open. And if we have these opportunities to live rage this network to try to build new products on DH, there are plenty of products that way. Also working on that are based on this idea that waken build products like people build APS to build a napkin, a smartphone or you need this environment way can expose the network in the same digital environment on DH. Translation is very interesting because it's emotional. If you think of communication, language can be a barrier. The a. D that we digitize the phone call and that we can then let build products or or engineer products that break barriers is very exciting. And so this is where we pick the specific use case for for the keynote today, Aziz, you mentioned before it has a emotional showing it, >> but there was if I got it right and police correct me if I didn't, um, you were engaged in a real time phone call right now and then if we pretended that one of you spoke one language, one of you spoke another. There was an immediate translation from English to French, French to English. And the call was being transcribed in real time as well. So it could be used another medium, right? I want to use it in, you know, e mails or other communications text, whatever. So you were stockpiling all this capability right in through the transcription, but doing real time voice translation. >> Take the venue, We idea. So things like translation is something that Microsoft, for example, does really well and many club companies to really well, the value we add is to move from having an adult translation request conditions like this to Russian, to integrating this in in one of the most natural communication channel, which is person to person. Phone call is a perfect place to start, because if there is one place where you're going to a language barrier as phone calls global, you can call anywhere in the world. This's pretty exciting environment. >> Oh, I thought so. I mean, >> you know, it's fascinating to think kind of history of telecommunications. It's well, you know, every country has their own, you know, system. But there needs to be that interconnection so that you know, today I don't think about whether you know I'm calling across the street across the country or across the globe. It takes care of that boy. If I could just plug into some of the available services on INDU translation, you know, right you're goingto bring Bring the world a little bit closer together. >> And the phone. Nichole's of Quintus, You don't sign up to brand, so you do sign up to a telescope. But this is regardless of your device. You can establish a phone call on used the services. I >> know some teenagers I'd like to have their conversations translated for May. Really helpful. >> You can build it a cz. Well, >> can you do work on that? Good. I'll have to think about it. What about five g And what is that doing for you? Just from a purely technical standpoint, the opportunities that you see coming with that I know rollouts. Probably still year or twenty four months away from taking place. I don't know what the Australia rollout is compared to the U. S. But in terms of what that speed is going to do for you, what kinds of possibilities you think the ceiling exist? I >> must after very developed. I'm thinking, like from Pew Software Development Point of view. Excuse me. Perfect opportunity to be connect customers with developers on an edge on a on your network. Andi, it's all the world later NCIS and bend with and you can do fascinating thing on edge ofthe network I raise that sings real time Rachael here at the open to reality five g will enable it and we'LL keep thiss development and improve speed off this stuff. And I'm looking forward to have all of this available not only for me as I'm looking for Loker, I don't want it close the opening network we're opening Tell Kal Toh the cool world off wonderful software development and it's fascinating >> The Savages. Also, if you think of five, you gotta think about momentum. There is this momentum that we have now to improve our networks, and it's not entirely just five g. We've got network function visualizations. We've got Coyote, and that momentum is very interesting because as we improve our network, it becomes more digital and especially mentioned as it becomes more digital. It's more open and enables new opportunities for enterprise customers off for startups to innovate in this environment. >> Okay, so my understanding from what you talked about and, you know, this is built on open shift, you know, what's the importance? You know, why Open shift and what is that enable for your business and ultimately your customers? >> This is actually something way quite proud off. When we started this journey in this software engineering space, it's inclined narrative. It's only natural to build functions in containers, but there was There was effectively that gap between building new applications in the current state of a network that has a a very different approach of operation. So, communities, where's the right tool for us? But when you operate a carrier network, you need strong support and you need Teo. You need to have a very firm Acela's because you don't drop phone calls. This is very important minute communication, and this is where we had a fantastic relationship is really to find a way to operationalize thiss deployment. >> Ricardo wasn't only like operating this thing way worked hand in hand last few years, they've helped a lot this designing systems like best practices. We learned a lot off each other and it was fantastic journey way really enjoyed working on this. It's extremely professional team, >> No, in from a timing perspective Oh, our journey came together a same time, as read it started seeing telcos has being where the next big thing or the next something to very much start focusing on. >> So so what's your next big thing? We're talking about five G and what that's going to open up, and we've read a lot about it here in the States. But from your perspective, you know what? What is that going to enable? What kind of services? Because for G's already, you know, blowing everybody's mind in some respects, right with the data capabilities there imaging transactions, those kinds of things, but five g your thought, I think, >> previews. Innovation cycles things three G for G Always came, came in with a pre pre baked benefits, often speeds with five minutes a little. My opinion is a little bit different. What's happening? What we're doing is is an example of this is in a V that you have a new environment and important environment where new things can happen and so you're going to see this as Oppen versus closed what it means is that the next big thing is not necessarily five year. And Evie. Next big thing is what software developers will make of this environment. And that might be a start up. Or they could be enterprised could bring you cooperate, right? And we are very much very much open to start conversation with anyone that would like to make use of this. He's >> got the next big thing. That was God the next big thing yet, Right, gentlemen, thank you for making the long trip. I know not just to see us, but we do appreciate your carving out some time for us. Good job this morning. And, uh, good luck down the road. >> Thank you for having us. >> Thank you. Thank you. Back with more live from Boston. You're watching the Cuban. You're watching coverage from Red Hat Summit twenty nineteen

>> live from Boston, Massachusetts. It's the you covering your red have some twenty nineteen rots. You buy bread hat. >> Good to have you back here on the Cube as we continue our coverage. Live at the Red Had Summit twenty nineteen, Day three of our coverage with you since Tuesday. And now it's just fresh off the keynote stage, joining stew, Minutemen and myself. Chris. Right? VP and chief technology officer at Red Hat. Good job there, Chris. Thanks for being with us this morning. Yeah. >> Thank you. Glad to be here. >> Great. Right? Among your central things, you talked about this, this new cycle of innovation and those components and how they're integrating to create all these great opportunities. So if you would just share for those with those at home who didn't have an opportunity to see the keynote this morning, it's what you were talking about. I don't think they play together. And where that lies with red hat. Yeah, you bet. >> So, I think an important first kind of concept is a lot of what we're doing. Is lane a foundation or a platform? Mean red hats focuses in the platform space. So we think of it as building this platform upon which you build an innovate. And so what we're seeing is a critical part of the future is data. So we're calling it a Kino data centric. It's the data centric economy. Along with that is machine learning. So all the intelligence that comes, what do you dividing? The insights you're grabbing from that data. It introduces some interesting challenges data and privacy and what we do with that data, I mean, we're all personally aware of this. You see the Cambridge Analytica stuff, and you know, we all have concerns about our own data when you combine all of us together techniques for how we can create insights from data without compromising privacy. We're really pushing the envelope into full distributed systems, EJ deployments, data coming from everywhere and the insights that go along with that. So it's really exciting time built on a consistent platform like lycopene shift. >> So, Chris, I always loved getting to dig in with you because that big trend of distributed systems is something that you know we've been working on for quite a long time. But, you know, we fully agree. You said data at the center of everything and that roll of even more distributed system. You know, the multi cloud world. You know, customers have their stuff everywhere and getting their arms around that, managing it, being about leverage and take advantage. That data is super challenging. So you know where where, you know, help us understand some of the areas that red hat in the communities are looking to solve those problems, you know, where are we and what's going well and what's still left to work on. >> Well, there's a couple of different aspect. So number one we're building these big, complex systems. Distributed systems are challenging distribute systems, engineers, air really solving harder problems. And we have to make that accessible to everybody operations teams. And it's one of the things that I think the cloud taught us when you sort of outsource your operations is somebody else. You get this encapsulated operational excellence. We need to bring that to wherever your work clothes are running. And so we talked a lot about a I ops, how you harness the value of data that's coming out of this complex infrastructure, feed it through models and gain insights, and then predict and really Ultimately, we're looking at autonomic computing how we can create autonomous clouds, things that really are operating themselves as much as possible with minimal human intervention. So we get massive scale. I think that's one of the key pieces. The other one really talking about a different audience. The developers. So developers air trying to incorporate similar types of intelligence into their applications were making recommendations. You're tryingto personalize applications for end users. They need easy access to that data. They need easy access to train models. So how do we do that? How do we make that challenging data scientist centric workflow accessible to developers? >> Yeah, just some of the challenges out there. I think about, you know, ten, fifteen years ago, you talk to people, it was like, Well, I had my central source of truth and it was a database. And you talk to most companies now and it's like, Well, I've got a least a dozen different database and you know, my all my different flavors of them and whether in the cloud or whether I have them in my environment, you know, things like a ops trying to help people get involved with them. You talked a little bit in your keynote about some of the partners that you're working on. So how do you, you know, bring these together and simplify them when they're getting, you know, even more and more fragmented? >> Well, it's part of the >> challenge of innovation. I mean, I think there's a there's a natural cycle. Creativity spawns new ideas. New ideas are encapsulated in projects, so there's a wave of expansion in any kind of new technology time frame. And then there's ultimately, you see some contraction as we get really clear winners and the best ideas and in the container orchestration space communities is a great example of that. We had a lot of proliferation of different ways of doing it. Today we're consolidating as an industry around Cooper Netease. So what we're doing is building a platform, building a rich ecosystem around that platform and bringing our partners in who have specific solutions. They look at whether it's the top side of the house, talking to the operations teams or whether it's giving developers easy access to data and training models through some partners that we had today, like perceptive labs and each to a A I this partnership. Bringing it to a common platform, I think, is a critical part of helping the industry move forward and ultimately will see where these best of breed tools come into play. >> Here, uh, you know, maybe help a little bit with with in terms of practical application, you got, you know, open source where you've got this community development going on and then people customized based on their individual needs all well, great, right? How does the inverse happen? Where somebody who does some custom ization and comes up with a revelation of some kind and that applies back to the general community. And we can think of a time where maybe something I'm thinking like Boston children, their imaging, that hospital we saw actually related to another industry somehow and gave them an ah ha moment that maybe they weren't expecting an open source. Roy was the driver that >> Yeah, I think what we showed today were some examples of what If you distill it down to the core, there's some common patterns. There's data, they're streaming data. There's the data processing, and there's a connection of that processed data or train model to an application. So we've been building an open source project called Open Data Hub, where we can bring people together to collaborate on what are the tools that we need to be in this stack of this kind of framework or stack And and then, as we do, that we're talking to banks. They're looking at any money laundering and fraud detection. We're talking to these hospitals that were looking at completely different use cases like HC Healthcare, which is taking data to reduce the amount of time nurses need to spend, gathering information from patients and clearly identify Septus sepsis concerns totally different applications, similar framework. And so getting that industry level collaboration, I think is the key, and that having common platforms and common tools and a place to rally around these bigger problems is exactly how we do that through open source. >> So Lynn exits and an interesting place in the stack is you talked about the one commonality and everything like that. But we're actually at a time where the proliferation of what's happen to get the hardware level is something that you know of an infrastructure and harbor guy by background, and it was like, Oh, I thought We're going to homogenize everything, standardize everything, and it's like, Oh, you're showing off Colin video stuff. And when we're doing all these pieces there, there's all these. You know, new things, Every been things you know you work from the mainframe through the latest armed processors. Give us a little insight as to how your team's geeking out, making sure that they provide that commonality yet can take advantage of some of the cool, awesome stuff that's out there that's enabling that next wave of innovation. >> Yeah, so I share that infrastructure geek nous with you. So I'm so stoked the word that we're in this cycle of harbor innovation, I'll say something that maybe you sounds controversial if we go back in time just five years or a little, a little more. The focus was around cloud computing and bringing massive number of APS to the cloud, and the cloud had kind of a T shirt size, small, medium, large view of the world of computer. It created this notion that Khun computers homogenous. It's a lie. If you go today to a cloud provider and count the number of different machine types they have or instance types it's It's not just three, it's a big number. And those air all specialized. It's for Io throughput. It's for storage acceleration. It's big memory, you know. It's all these different use cases that are required for the full set of applications. Maybe you get the eighty percent in a common core, but there's a whole bunch of specific use cases that require performance optimization that are unique. And what we're seeing, I think, is Moore's law. The laws of physics are kind of colliding a little bit, and the way to get increased acceleration is through specialized hardware. So we see things like TP use from Google. We see until doing deal boost. We've got GPS and even F p G A s and the operating system is there TIO give a consistent application run time while enabling all those hardware components and bringing it all together so the applications can leverage the performance acceleration without having to be tied directly to it. >> Yeah, you actually think you wrote about that right now, one of your a block post that came about how hardware plays this hugely important role. You also talked about innovation and change happening incrementally and And that's not how we kind of think about like big Banks, right? Yeah. Wow, this is But you pointed out in the open source, it really is step by step by step. Which way? Think about disruption is being very dramatic. And there's nothing sexy about step by step. Yeah, that's how we get to Yeah, disruption. I kind of >> hate this innovation, disruption and their buzz words. On the one hand, that's what captures attention. It's not necessarily clear what they mean. I like the idea that, you know, in open source, we do every day, incremental improvements. And it's the culmination of all these improvements over time that unlock new opportunities. And people ask me all the time, where is the future? What do we do and what's going on? You know, we're kind of doing the same thing we've been doing for a long time. You think about micro services as a way to encapsulate functionality, share and reuse with other developers. Well, object oriented programming decades ago was really tryingto tryingto established that same capability for developers. So, you know, the technologies change we're building on our history were always incrementally improving. You bring it all together. And yes, occasionally you can apply that in a business case that totally disrupts an industry and changes the game. But I really wanted encourage people to think about what are the incremental changes you can make to create something fundamentally new. >> All right, I need to poke it that a little bit, Chris, because there's one thing you know, I looked back in my career and look back a decade or two decades. We used to talk about things like intelligence and automation. Those have been around my entire career. Yeah, you look it today, though, you talk about intelligence and talk about automation, it's not what we were doing, you know, just the amount of degrees, what we're having there. It is like if we'd looked at it before, it was like, Oh, my gosh, science fiction's here so, you know, way sometimes lose when we're doing step by step, that something's there making step function, improvements. And now the massive compact, massive changes. So love your opinions there. >> Yeah, well, I think it's a combination, so I talk about the perpetual pursuit of excellence. So you pick up, pick a field, you know, we're talking about management. We got data and how you apply that data. We've been working towards autonomic computing for decades. Concepts and research are old, the details and the technologies and the tools that we have today are quite different. But I'm not. You know, I'm not sure that that's always a major step function. I think part of that is this incremental change. And you look at the number for the amount of kind of processing power and in the GPU today No, this is a problem that that industry has been working on for quite a long time. At some point, we realize, Hey, the vector processing capabilities in the GPU really, really suit the machine learning matrix multiplication world real world news case. So that was a fundamental shift which unlocked a whole bunch of opportunity in terms of how we harness data and turn it into knowledge. >> Yes. So are there any areas that you look at? Now that we've been working at that, you feel we're kind of getting to those tipping points or the thie waves of technology or coming together to really enable Cem Cem massive change? >> I do think our ability to move data around, like generate data. For one thing, move data around efficiently, have access to it from a processing capability. And turning that into ah, >> model >> has so fundamentally changed in the past couple of decades that we are tapping into the next generation of what's possible and things like having this. This holy grail of a self healing, self optimizing, self driving cluster is not as science fiction as it felt twenty years ago. It's >> kind of exciting. You talk about you've been there in the past, the president, but there is very much a place in the future, right? And how would that future looks like just from from again? That aye aye perspective. It's a little scary, sometimes through to some people. So how are you going about, I guess, working with your partners to bring them along and accept certain notions that maybe five six years ago I've been a little tough to swallow or Teo feel comfortable with? >> Yeah, well, there's a couple of different dimensions there. One is, uh, finding tasks that air computers are great at that augment tasks that humans were great at and the example we had today. I love the example, which was, Let's have computers, crunch numbers and nurses do what they do best, which is provide care and empathy for the patients. So it's not taking the nurse's job away. In fact, is taking the part that is drudgery ITT's computation >> and you forget what was the >> call it machine enhanced human intelligence right on a couple of different ways of looking at that, with the idea that we're not necessarily trying to eliminate humans out of the loop. We're trying to get humans to do what they do best and take away the drudgery that computers air awesome at repetitive tasks. Big number crunching. I think that's one piece. The other pieces really, from that developer point of view, how do you make it easily accessible? And then the one step that needs to come after that is understanding the black box. What happens inside the machine learning model? How is it creating the insights that it's creating and there's definitely work to be done there? There's work that's already underway. Tto help understand? Uh, the that's really what's behind the inside so that we don't just trust, which can create some problems when we're introducing data that itself might already be biased. Then we assumed because we gave data to a computer which is seemingly unbiased, it's going to give us an unbiased result, right? Garbage in garbage out. >> So we got really thoughtful >> about what the models are and what the data is that we're feeding >> It makes perfect sense it. Thanks for the time. Good job on the keynote stage again this morning. I know you've got a busy afternoon scheduled as well, so yeah, I will let you. We'Ll cut you loose. But thank you again. Always good to see you. >> Yeah. I always enjoy being here >> right at that's right. Joining us from red hat back with Wharton Red Hat Summit forty nineteen. You're watching live here on the Cube?

why from Boston Massachusetts it's the queue covering Red Hat summit 2019 watch you bye Red Hat well good morning welcome back to our live coverage here in Boston with the BCC and we're at Red Hat summit 2019 you're watching exclusive coverage here on the cube this is day three of three great days here at the summit's two minimun John wall's and we're joined now by Paul Cormier who's the president of products and technologies at Red Hat good morning Paul morning how are you doing I'm doing great great so are we a wonderful job on the on the keynote stage yesterday and we're gonna jump into that a little bit but I wanted to run something by you here a great man once said every great achievement begins with a bold goal I heard that I'm looking at that man yeah so one of the many statements that I thought really jumped out yesterday let's talk about that in terms of just the Red Hat philosophy what's happened with rl8 where you've gone with openshift for and just how that is embedded in your mind to how red hat goes about its business well you know we've we've we've been in the enterprise space for 17 plus years and prior to that red had you know we were basically through the retail through the retail channel but first and foremost Red Hat started as an open source company that's where they started not as an enterprise company once we decided with the bold goal that we're gonna get this into the enterprise that's what we really set you know really transformed into what you've maybe heard before from out of my mouth is where we're we're not an open source company although everything we do is open source for an enterprise software company with an open source development model that was kind of the beginning of the first bold goal let's get Linux to the enterprise and so that's sort of how we've thought about it from day one is let's take it one step at a time you know as I said get Linux in the enterprise make make rel the operating system in the enterprise now let's take on virtualization versus n then KVM and then as that all happens so much innovation happened around Linux that all these other pieces came you know Hadoop kubernetes all the other pieces so we just kept growing with that because it's all intertwined with Linux that's one step at a time so Paul before we get off this place I want you to put a fine point on it for our audience because you look out there you know open source is not a community it's lots of communities and it's not you know one thing it's many things out there and today people will look at there's certain companies how do I create IP and monetize what we're doing and you know where the project and the company are you know sometimes intertwined and licensing models changing you know Red Hat has a very simple philosophy on it and it's not something that's necessarily easily replicatable yeah I mean there's simple simple philosophy is it so it's it's upstream first that that's that's our philosophy yes we are a business and certainly making our products successful is is is important number number number one goal number zero goal before that is make the project successful our products can't be successful unless we're we're built on a successful project and it's not something that we even think about because it's just ingrained it's it's it's in our DNA so I mean I'll give you examples you know even kubernetes we didn't start the project Google started the project but we knew in order if we were going to incorporate that in a big way into our products that we had to be prominent in the community so that's what we did first and then it rolled out into the products it's just ingrained it's in the DNA yeah so let's talk a little bit about kubernetes openshift you've now got over a thousand customers congratulations on that and openshift for we spent a bunch of time talking with the team but let's start a little bit higher level because you know there's dozens of you know kubernetes options out there people look at is there interoperability between them you know in the early days customers would just spin their own pieces and on you know today every cloud provider has at least one option if not multiple options and there's all the independent how does this play out you know where are we along the maturity and how do all these pieces fit together or do they I mean if you look if you look at kubernetes I mean the thing here's the the good news the good news is open source has become so prominent in in everywhere we wear now ourselves included we make this mistake ourselves we've confused projects with products so kubernetes is a project it's a development project and we all talk about that like it's a product the same it's the same thing with Linux so I'll give you an example with the Linux kernel where all you know all the commercial vendors and everyone else is in that same upstream development tree with the Linux kernel but when the commercial guys like ourselves when we go to build a product we make choices of which file systems we're going to support which installers we're going to support you know what we're gonna do for management what we're gonna support for storage and for many reasons we all make different decisions so that's why at the end of the day when we come down to our products even though they're all completely open you know rel is different from Susu which is different from a bun too which is different from all the others it's the same exact thing with kubernetes we all develop here but now we bring that down into a platform like open shift that kubernetes touches userspace api's it such as kernel a api's and so unless you you integrate those and they all move forward in the lifecycle of that platform at the same time we get out of sync with each other and that's one of the reasons why it's a product and they don't necessarily work across each other with you know with all the other products it's the same exact principle that made rel and at the same exact principle how linux works right so what advice do you give to customers is how they look at this because they're like oh wait there's now azure an open shift this jointly offered solution but do I use that or Duty as the native you know aks solution out there you've got partnership to the AWS you know where does open shift versus anthos on google fit it's it definitely is a little bit fragmented well the other thing that's happened around the cloud one of the things that happened in early in the cloud a lot of the cloud providers said every applications going to the cloud tomorrow I think that was ten years ago and the last number I thought sorry we're about 20 percent there and so and that's great we think that's great but customers still have on-premise applications and they have a running on-premise either bare metal virtual machine they have their own private clouds in many cases and now they want to go across clouds every customer I talked to and it's not just for lock-in that's definitely an issue they want to go across clouds because this cloud provider might have a better service here than that cloud provider and vice versa so what customers want to do is they want one common operating environment both of the applications developer in the operators they can't afford to have five different silos because just like the example I used with Linux distributions being different every one of these kubernetes distributions is different and so anthos for example if you're gonna have all your applications including bare metal applications on Google Linux then that's good because your operators have one operating environment you developers have one development environment but that's impractical and that's why that's that's not gonna work I mean the reason why I think Microsoft is one of our best partners here is they understand this which is why they've embraced openshift so so deeply even though they have aks in their stable and the reason why I think they understand this is because they like us have been in the enterprise space for a long time this is how enterprise computing works and I think that's the model that our customers they don't have no choice to deploy they just can't afford to have five different you know operating environments it's like the UNIX days it's like the UNIX days all over again and you know when you had one vertical stack and you know customers started to roll out a common fact that's why Rell succeeded because we gave them that commonality and they couldn't afford five different silos to try to manage and develop their applications to you know is there a different rhythm or unique rhythm to the open source community in terms of development in terms of new products that might be a little different than then old older models because you know if I'm saying if I if there's an interest that focuses maybe in one area and the interests of ER you know or momentum shifts over to a different direction and and maybe this standard or this old way kind of loses a little bit of its impetus or its force I mean what that creates decision challenges on customer sign but but absolutely and and that's why as they said even with kubernetes we didn't jump in full force exactly right away you know we sort of we sort of worked in many of it with many container orchestration technologies out there most of which besides kubernetes are gone by the wayside a bit now and you know we sort of sort of look at that and see where this plays out well we get involved but we also try to make make the best technical decision as well kubernetes now it's got way too much momentum in in in the in with open source because it's got so much momentum that's where the innovation is happening and at the end of the day customers even though they have confused many projects with products they still want they still want the right technology to solve their business business problems right and so cuckoo Bernays has so much momentum around it that's where the innovation is happening so that's that's that's the plot that's the big part of the platform right now and so I think that's the other thing I think that a lot of people that try to jump into this space miss is if you're gonna base your enterprise product on an upstream project you better have good influence in that upstream project because when your customers ask you to address an issue or or take it in a direction or help take it in the direction if you don't have that influence you can't satisfy your customers so we learned very very early on that upstream is is not a bolt-on for us it's an integral part that starts even before the product starts so Paul I've heard many people often call Red Hat the Switzerland of IT you know being where you sit in the community and you know for years at this show we've interviewed you know all of the hardware players and everything like that sorry sorry I'm taking important calls it's no worries you know live audience can wait we'll show you the clip of John Cleese when we got interrupted on a program once we won't think was my admin telling me I needed to come here you're good but so you know with Red Hat starting as that as that Switzerland when I look at the multi cloud world its you've got interesting combination you know Satya Nadella up on stage is not something that we would have thought of right five years ago so you know VMware supporting OpenShift announced today is not something that many people will look at and be like oh geez you know that seems surprising to me because you know we have you know fights over virtualization or various piece of the stack what do you see in kind of the software and multi cloud world today that's maybe a little different than it was five or ten years ago I think I mean to VMware's credit they're trying to satisfy their customers and their customers are saying I want OpenShift and so we we work with trying to satisfy our customers to the Microsoft arrangement I mean as you guys probably well know we weren't the best of friends you know five six seven eight years ago and I think Satya said it on stage and they our customers got us together literally we had a set of big customers that almost took us in a room and said you guys need to talk and and frankly I think they're one of our best partners right now I'm not sure it could have happened without Satya but they're one of our best partners because we're both interested in satisfying our customers in and as I said I think Microsoft really understands the enterprise world and that's why we're going in the common direction we almost when we get in the room with their engineers we almost complete each other's sentences of you know when we start talking about what we need to do you know there's been an announcement early in the week ahead of a global economic study done IDC came up with this huge number right 10 trillion dollar impact that Linux is having globally speaking just if you would just curious about your perspective on that what kind of a statement that is and and the dollar values that are achieved or the incremental values that are achieved in terms of applying these technology I think it's a couple things I think I think it's a statement that this is the innovation most so open-source is the innovation model going forward period end of story full stop and I think as I said in my keynote yesterday you know leading up to the the biggest acquisition ever for a software company not an open-source software coming a software company that happened to be an open-source software company I don't think there's any doubt that that open source has one here here today it and it's because of the pace of innovation I mean yes I mean we've been at rel for 17 plus years well we probably spent the first third or so without 17 plus years trying to convince the world that Linux was secure and it was stable and it was ready for the enterprise once we got through that hurdle it was just off to the races from there and kubernetes what you know I said yesterday containers came on the scene although they've been here technically for a long time they came on the scene in 14 herba Nettie's in 15 it's only 2019 it's really not that far downstream where were as you said we've got a thousand commercial customers and the keynote this morning talking about some of the use cases that we're solving with with OpenShift I mean Boston Children's Hospital is just unbelievable of what they can do in a matter of a week that used to take them a matter of a month to do right that's because of the innovation model we have dr. Ellen Grant on yesterday by the way so if you haven't watched that yet go back to the cube net and check that interview out yeah I mean fascinating kind of customer conversation we've had about transformation but want to get your take on the only constant in our industry which is change I wrote right after the the announcement of the acquisition and meeting with your changes Red Hat the one thing that they've actually built themselves for is to deal with the massive amounts of change you know you could tell better than more how fast the Linux kernel is changing you know a third of the codes changed in the last two years and kubernetes is actually not as many lines of code as Linux but it's massive amounts of change I heard you know we relate out to about five years of development on that I heard the the pace going forward will only get faster every three years you're gonna have a major release every six months right a minor release so how do you get the team in the community and all these things you know ever keeping up and even turning it up to 11 that day that's that's probably the one of the biggest parts of our job our customers can't deal with that change you know frankly I think in the bidding beginning of OpenStack one of the one of the mistakes that we as a community did for our customers was there were some vendors out there trying to tell customers you need to stay close to the head to the upstream head you need to stay close to the head and we really all try to get things out in six months that's great to try to start to evaluate innovation and how what you can do with that it's not great for necessarily running a stable business on and that's what and that's what I think our job is is to help our customers consume open-source developed technologies in a way that they can continue to run their business and that was the goal that was the audacious goal of rel from the beginning is that the model of rel it's in it's no I it's it's not necessarily about the bits because they're free it's about the life cycle of that and how we can help our customers consume that and that's what we do that frankly it to the core well just to follow up on that if you ask your customer and you say hey you're using Azure what version you are using they're like Microsoft patches and updates that constantly as opposed to the traditional you know Patch Tuesday in Windows so you know we seem to be closing that gap a little but it's challenging between the stuff I control and the stuff that I consume well we'll look at even OpenShift for we used I mean I know ashesh was on yesterday talking about that but we used a lot of the great technology we got from core OS to start to bring that model bet on to even on premise if you so choose with open shift because there's so many of the components that are that are intertwined with each other you know you've got kubernetes with talking the user space talking the kernel user space talking to the kernel talking the storage talking to networking so now automating that for our customers for that updates is is is what they want because that's how they consume it in the cloud I remember when we first started rel we used to put the the features on the side of the box and the first thing was what version of the kernel it was that quickly went away - they don't want to have to worry about that because they don't have the expertise to do to be added' eyewire themselves well congratulations Paul great week thank you very much again well done now on the keynote stage yesterday fascinating stuff this morning - so well done on the program inside and we wish you look down the road and don't forget to check your voicemail no I will thank you guys very much might be important all right always a pleasure back with more here from Red Hat summit 2019 you're watching us live here on the Q [Music]

>> live from Boston, Massachusetts. It's the you covering your red hat. Some twenty nineteen brought to you by bread hat. >> Well, good morning. And welcome to Day three of our coverage here, Right? Had some twenty nineteen. We're live here on the Cube, were in Boston, Massachusetts, and was soon Merriman. I'm John Wall's. Glad to have you with us for our last day of coverage. We're now joined by the SPP. Adele Technologies. Pete. Myka, Pete. Good to see you this morning. And Pete, by the way, is coming with I'm sure song in this heart of smile on his face two and a half hours to get in today. >> It was a long drive in, but I'm here now. I'm excited to be here. This is a great show. And here with great partners. >> Yeah, the tough part's over, right? >> We're in Boston, not in Vegas, so that you gotta be a little >> bit there some consolation. Let's just first off, let's paint the umbrella here a little bit about the overall partnership between Delhi, um state right and red hat and how that's evolved. And currently, word stands with all the new releases I've heard about this week. >> Yeah, it's been a great partnership for almost two decades now, right? Della and red hat of working together on a lot of different products from ready stack are ready architectures and ready nodes to software sales. Support customer engagements has been a tremendous partnership for twenty years, and I expect to be going for another twenty years. >> All right, that's digging a little bit walking through the stacks, if you Well, so we understand. You know, Red Hat is an operating system, you know, long history working on, you know, all the del platforms. You've got the converge environment. Where where does red hat fit in? What pieces of there ever broadening portfolio fit in? >> Right. So really, on the ready solution side of the world, which is another part of the products I managed for Del. So within the ready solutions environment, we worked with red hat on open stack way. Deliver hardened, supported open stack products to both. Tell Cohen Enterprise Markets on that. We also deliver open shift and already noted ready solution environment so we can deliver that container men's container environment for those same enterprise and serves customers. >> Yeah, so if you know, the Cubans at, you know Del Technologies World last week and at that show in here, I >> saw a sizable >> break out for telecommunications. You know, we could talk a lot about Enterprise, but, you know, telcos got some certain special requirements needed to make sure it's certified for certain things and, you know, gotta be tested out. Maybe we talk a little bit about what those customers are looking for and why that match you red hat makes sense. >> Sure mean Telco really wants to have control over their environment they wantto have. Open source is a great technology for Tell Cole, right, and they love taking the technology customizing for their environment, reselling components to their end users in open stack from Red Hat is a perfect fit for that market. And so again, we deliver that and the hardened solution on top Adele Technologies on Del Partridge servers deliver that to the telco market and provide them the tools and the capabilities they need to deliver the solutions to their customers. >> What what is it? Let's go dive in just a little bit. Then about those specific traits or attributes, you think in terms of the telecom market goes, you know what is specifically about you think there needs that they find so attractive about open source and what makes them stand apart from other industry sectors. Yet to me, it's controlling >> customization. So rather than taking a packaged app that shrink wrapped in running it like everybody else, they want to get a customized control for their markets. They have certain as to mention they have certain standards and compliance you don't have to deal with. They also want to differentiate within that telecom market. So it's hard to do without having control around the underlying stack. I think those are the big attractiveness around. And then, um, you know that the solution from Red Hat combined with Dellis is such a enterprise quality product for the telecom market, which I think has certain advantages. >> Okay, so you mentioned you know, the ready solutions and open stack piece, and then on top of that, there could be open ships. So that's right, a news, you know, talk to you know, many of the customers, the executive team on the team here, open shift for showing good momentum over thousand customers. So how does that fit in with the solutions you're >> offering well, so we offer a ready solution for open shift this wall, right? And we see that as the container solution for the the market that really wants those open source type products and has a line themselves with red hat in Lenox. And so it's a perfect solution for that. And, you know, we really see Oprah shift as the ability to create a managed environment for containers as we saw from Polish Kino with Over shit for now provides a tremendous hybrid cloud experience for customers at one of my great workloads, both on premises to cloud and back. And so we think that's tremendous technology that we'll add value. And with our hardware technology underneath that we could provide a stack that we think services the market quite well. >> Yeah, it's funny, Pete, you know, you've got a lot of history and I've worked with you for many years on this the ultimate A lot of these technologies, you go back to server virtual ization. You look a container ization in Cuba. Netease. They're like, Well, we want to extract upto, allow the applications to be able to be modernized and do these wonderful things. And I shouldn't have to think about the infrastructure. Right. But we know what the end of the day It lives on something, and it needs to be good talk a little bit of things, like Corinne, eh? Tease. And you know where Del thinks they fit from an infrastructure standpoint compared to communities. >> Yeah. What we want to do is provide the infrastructure that makes it easy to four workloads and applications to preside on, including open shifting cabernets environments. Right? And so, really, what you want to do? And for years, as you say, we've got a lot of history in this. We've been trying to push that complexity and management up the stack. So the hardware and even the virtual ization layer and the container layer becoming afterthought, right? And you know, what I saw from open ship for is that really puts the power back into the application developers and makes it easier to manage and control your underlying harder environment. So, with tight integrations into the open ship community with our del technology Zach, we can provide that sort seamless infrastructure layer that allows the application developers to go do what they need to do not be worried about infrastructure management. >> Do you have any customer examples that might help highlight the partnership? >> Um, no, I >> don't have any good. I >> didn't I'm sorry. I didn't >> know the customer. Well, let's hope out for a little bit. And you talk about hybrid and what that's going to enable there, is that the, uh Oh, here we go for you on this in terms of what's new, What's the latest? I mean, what about the capabilities? You're going to get nowt for what's going to be offered and what is that? That's kind of jumping off the page to you. This is Yeah, this was worth the wait. Well, >> to me, it was all about the management in the automation, the underlying infrastructure just again taking that complexity away from the developers and putting it, um, allowing the application developers tools they need to do to very quickly developed applications, but also migrate them to the proper landing spot and maybe cloud one day and maybe on premises the next. You know, one of the beauties of cloud is is there are classes of applications that may not necessarily fit on a public cloud. You may not know that. Do you? Get there and you want to have the flexibility to push them out, see how they work and bring them back in and open Shift gives you all this capability open shit for yeah, >> eso Absolutely what we hear from customers. It it's not. The future is hybrid and multi cloud. It's today, and the future are voting hybrid and multi class today. To that point, I wonder if you could help us. Just It's not Dell specific, but VM wear made an announcement today that they're supporting open shift for on top of'Em. Where can you maybe t explain where that fits into the overall discussion? >> Yeah, So look, Dell's always writing choices, the customers and we want it we want to be. And we are the essential infrastructure company to the enterprise and commercial environments. And so open shift on VM were just another example of choice and customers. They're gonna have different location environments out there. They're going to run some containers. They're going to run. Some of'em are going to run some native way. Want to be the infrastructure provided for that. We want to work with partners like you had a choice to our customers. >> You know, we've heard a lot this week about flexibility, right on a scale and options and all. And I understand providing choice is a great thing, you know, the customers. But what does that do for you in terms of having to answer to all of that desire? The flexibility? Well, it's it's >> opportunity in this challenge, right? Supporting all these different environments, of course, is a challenge for engineering teams. But it's also opportunity if we want to be. And we are the essential, you know, hardware technology, player in the industry. We have to support all these leading platforms and open shifts. Just example of that. The >> challenge on that side of it. I get opportunity, but you have to develop that expertise We do know throughout your force, and that probably has its own challenges. >> It doesn't mean we have to have expertise only and our own technologies like VM wear, but also open shift and other technologies or red hat technologies. We have to higher and cultivate, um, open source engineers, you know, which is not always easy to find on DH. We have to develop those expertise that know how to integrate those components together. Rights, not just a matter of taking the software and laying on top of the next eighty six architecture and saying it's done way, want Toby to integrate that. So we provide the best experience to the customers. So having that capability to understand what's happening at the hardware infrastructure layer also, what's happening at the virtual ization and container layer is a critical piece of knowledge that we have to. We have to grow and continue to work with >> you. But what about, I mean, as far as the competitive nature of the work force, then I kind of thinking about It's almost like ways. The more people who use that, the tougher it is to get around right, Because so the more people who are moving toward open source, the more which is great. But it also the more competitive the hiring becomes, the training becomes that it does bring with it. Certainly I would say barriers by any means, but a different factor. >> It's a challenge across the entire industry right now, hiring good technical people, and it's not just on open source space. It's an all space is open source is a particular challenge because it takes a certain set of skills to work in that environment. Dell has a philosophy where we are continually looking at university hires and growing from within. We try to hire a CZ. Many new hires, new grads as we can, But the reality is we have to look everywhere in order to try to find those. Resource is very hard to come by, and it's very competitive to get these employees are these candidates. Once you find them, it's hard to get him in the head of environment. >> So it it's interesting. Just step back for a second here last week at your show, it was I opening to see such a nadella, you know, up on stage with Pak else, right? While Microsoft Environments have lived on V EMS for a long time, you know, far as I know the first time the two CEOs have been public scene together fast word to here. And once again we saw touching Adela up on stage with, you know, red hat. It's, you know, for years we think about the industry as to the competitive nature and what's going on and Who's fighting who. Multi cloud. It's not like it's everybody's holding hands and singing, you know, Cooper Netease, Kumbaya. But it is a slightly different dynamic today than it might have been >> is very different in the past. When there are maur infrastructure players, Mohr software players, you could pick your swim lanes. You can compete now, the lines are blurred, and cloud definitely has a lot to do with that. Right and hybrid Multi cloud has everything to do with that, because if your applications going run on eight of us one day on premises the next day in azure the next day you better have tools, processes and procedures that allow those applications the migrate across that multi cloud experience. And so what if forces vendors to do is get together and participate in a cooperative in whatever your favorite word is for competitors working together. But that's really what it is, is we've realized you look a Del Technologies UVM. Where is part of our family? But we're working with Red Hat. What, working with Microsoft and Red Hat, as you see, is doing the same thing. It's necessary in today's market in today's environment that you just have to do that. >> Well, Paul, you mentioned swim lanes. I hope the Express lane is open for you on the ride home. So good luck with that. Thanks for the time this morning, too. Good to see you. It's a home game for you. So it's not all bad. It's not all >> bad. No, this is a great place to be and a great event. I'm glad I could be part of the >> burger. Thanks for being with us. Thank you. Back with more live coverage here. You're watching the Cube. Our coverage, right. Had summat twenty nineteen.

>> Announcer: Live from Boston, Massachusetts, it's theCUBE covering Red Hat Summit 2019. Brought to you by Red Hat. >> Welcome back to our coverage here on theCUBE of Red Hat Summit 2019. We're live in Boston right now, and I'm joined by a couple of award winning professionals. And we're looking forward to hearing what their story is because it's fascinating on both fronts. And also by DeLisa Alexander who has a great job title at Red Hat. Chief People Officer. I love that title. DeLisa, thanks for joining us. >> Thanks for having us. >> Also with us, Limor Fried who is the and founder and lead engineer of Adafruit and Saloni Garg who is an undgergrad student, third year student, at the LNM Institute of Technology. And that's in Jaipur, India. So Saloni, glad to have you with us. And Limor, a pleasure as well. >> Thank you. >> And you're all lit up. You've got things going on there, right? >> I'm glowing, we're gonna get all into that. >> We'll get into that later. First, let's talk about the award that, they're two women in open-source are our winners this year. On the community side, Limor won, on the academic side, Saloni won, so talk about the awards if you would, DeLisa. The process and really what you're trying to do with recognizing these kinds of achievements. >> Well, this is our fifth year for the Women in Open-Source Award. So after this period of time, I can tell you what we wanna do is make an impact by really fostering more diverse communities, particularly gender diverse in open-source. And so that's the whole goal. Five years into it, what we've discovered is that when you really focus on diversity and inclusion within a community, you actually can make an impact. And the thing that's so exciting this year is that our award winners are really evidence of that. >> So talk about the two categories then if you would please. You have community on one side, academics on the other. It appears to be pretty clear cut what you're hoping to achieve there by recognizing an active contributor, and then somebody who is in the wings and waiting for their moment. But go ahead and fill in a little bit about, >> Yeah, absolutely. >> Limor and Saloni too about, why are they here. >> Limor: Why am I here? >> Yes, well, really what we're trying to do is create role models for women and girls who would like to participate in technology but perhaps are not sure that that's the way that they can go. And they don't see people that are like them, so there's less a tendency to join into this type of community. So with the community award winner, we're looking at the professional who's been contributing to open-source for a period of time. And with our academic winner, we're looking to score more people who are in university to think about it. And, of course, the big idea is you'll all be looking at these women as people that will inspire you to potentially do more things with open-source and more things with technology. We've been hearing for many, many years that we definitely need to have more gender diversity in tech in general and in open-source. And Red Hat is kind of uniquely situated to focus on the open-source community, and so with our role as the open-source leader, we really feel like we need to make that commitment and to be able to foster that. >> Well, it makes perfect sense. Obviously. Great perfect sense. Saloni, if you would, let's talk first about your work. You've been involved in open-source for quite some time. I know you have a lot of really interesting projects that you're working on right now. We'll get to that in a bit, but just talk about, I guess, the attraction for you in terms of open-source and really kind of where that came from originally through your interest in stem education. >> Okay, so when I first came to college, I was really influenced to contribute to open-source by my seniors. They have already selected in programs like Google Summer of Code Outreach channel, so they actually felt empowered by open-source. So they encouraged me to join it too. I tried open-source, and I feel really, like, I'm a part of something bigger than myself. And I was helped greatly by my seniors, so I feel it's my duty to give it back to my juniors and to help them when they need it so that they can do wonders, yeah. >> Great. And Limor, for you, I know you founded the company. 100% female owned. You've got-- >> Yeah, 100% me. >> Yeah, right. 100% you. >> It's my fault. >> Right. Well, I wasn't going to blame you. I'll credit you instead. >> Yeah, that's our big thing. We wanna change. Get blame to get credit. >> Right. It's all about credit. >> More positive. >> So 100 employees? Is that right? >> 100, 150, yep. >> Okay, talk a little bit about kind of the origin, the genesis of the company and where that came from and then your connection on the open-source side. >> Well, I, yeah, so I grew up actually in Boston. So I've lived here a very long time. >> You said like a block from here. Two blocks. >> I used to live, actually, yes, in South Station nearby. I used to live by the Griffin Book line, and so Wilson has a very strong open-source community, you know. Ephesoft is here. And, yeah, that's kind of the origins of a lot of this free software and open-source software community. And when I went to school, I ended up going to MIT, and the open-source software and open-source technology is kind of part of, like, the genetics there. There's actually this thinking that you wouldn't do it. It's kind of by default. People write code, you open-source, you release it. There's a culture of collaboration. Scientists, engineers, students, researchers. All working together and sharing code. And when I was in school, so I had to take Thesis. I really didn't wanna do it, and so instead, I started building, like, MP3 players and video games. Taking all the engineering that I was studying and, like, not doing the work I was supposed to be doing. But instead, I was having fun and building cool electronic parts, and I would publish these projects online. I had, like, a MediaLab webs page, and I would publish, you know, here's all the chips and the schematics and the layout. And people sort of started coming up with the idea of open-source hardware. Let's take the philosophy of open-source software where we release the source code. But, in here, you release CAD files, firmware, layouts, 3D models. And so I did that, and I was publishing here's how you make this, like, Lite-Brite toy for Burning Man or an MP3 player or a cell phone jammer. All these fun projects, and people would end up contacting me and saying, hey, these are really cool projects. I would like to build this project myself, but unlike software where you just, like, type in, like, make, config, and compile and all that. You actually have to buy parts, you have to get these physical things. And so they said, you know, could you sell me a kit, like a box, where we'd get it and take it home and be able to build it. And I was totally like, no, I'm busy. I have to, like, not write this thesis. >> That's not what I do. >> But eventually, I did write the thesis. And then I was really stuck because I'm like, now what do I do? So I ended up selling kits. So I sold the synthesizer kits and such, and I did an art fellowship and stuff. And then, eventually, I was kind of like, this is, I was doing, you know, it's, you kind of fall into business by accident because if you knew what you were getting into, you wouldn't do it in my opinion. So I ended up sort of developing that, and that was 13 years ago. And now we have 4,000 products in the store, you know. >> 4,000 products? >> Yeah, I know. Ridiculous, right? That's a lot. >> Yeah, who's doing that inventory, right? >> Well, we have a pretty intense inventory system that I'd love to talk to you about, but it's kind of boring. >> I'll bet you do. Now, I was reading something about an circuit playground express. >> Yes. >> Is that right? So is that what this is all about is-- >> Yes! I knew you'd ask, and that's why I wore this. >> So it's a, kind of, an exploratory circuit board of-- >> Yeah! It's open-source, open-source hardware, open-source software and firmware. And we had a lot of parents and teachers and educators and camp counselors come to us and say, we wanna teach physical computing. We wanna teach coding but with physical hardware because, you know, we all, all the tier coders, right? No, I don't know. But, eventually, you're like, I'm typing on the screen. And you want to take that and you wanna make it physical. You wanna bring it out into the world where there's a wearable or a cosplay or assistive technology, or you wanna make video games, that are, like, physical video games. And the problem that teachers had were the classrooms, a lot of these classrooms, they don't have a lot of money. So they said it has to be very low-cost. It has to be durable because these kids are, like, chewing on it and stuff, which is fun. And it also has to work on any computer, even extremely old computers. 'Cause a lot of these schools, they only have a budget every seven years to buy laptops. And so this actually becomes a very difficult technological problem. How do you design something that's $20 but can teach physical computing to anybody? From kids who are not even good at typing all the way to college students who wanna implement fast 48 transforms, and so we designed this hardware. It's open-source, and it's cool 'cause people are, like, remixing it and making improvements to it. It's open-source circuit playground, and I'm wearing it. And it's glowing, and I don't know. It's fun! It's got LEDs and sensors. And you can just alligator clip to it and make projects, and we've got schools from around the world learning how to code. And I think it's a much more fun experience than just typing at a computer. >> Absolutely. Yeah, Solani, on your side of the fence, so I obviously, in your education years if you will, not that we ever stop learning, but formally right now. But you're involved, among the many projects that you've been involved with, a smart vehicle. >> Yeah, I'm working on it. >> Project, right? So tell us a little bit about that and how open-source has come into play with what you're looking at in terms of, I assume, traffic and congestion and flows and those kinds of things. >> Yeah. So what we're working on is, basically, we'll be fitting cameras and Raspberry Pis on buses, college buses. And then they'll detect, like, they'll detect lane detection and traffic signal violation and will report the assigned people. If there's any breakage of law or any breakage of traffic signals, so that's what, basically, we are working on and how open-source comes into the play is that we actually knew nothing about OpenCV and all the technology that is before all this. So I looked up some open-source projects that had already the lump sum of all this, and I got to learn a lot about how things actually work on the code-based side. So that's how open-source actually helped me to make this project. >> And, ultimately, who do you report to on that? Or how is that data gonna become actionable or, I assume it can be. >> Yeah. >> At some point, right? I mean, who's your partner in that? Or who is the agency or the body that, you know, can most benefit from that? >> Yeah, so, currently, this is an academy project, and a classmate of mine has been working with me. And we are working on a faculty member. And so, basically, we have decided to expand this project and to use it as a government project. And we, authorities we'll be reporting to whenever there's a signal or law breakage is that the traffic police department will be notifying them in case of any signal breakage. >> So if there's an uptick in speeding or red light running in Jaipur, we know who to blame. >> Yeah. >> Right? >> Shouldn't have run a report. >> It's, Solani, why'd you do that to them, right? All right, ladies, if you would. And I'm gonna end with DeLisa, but I'd like to hear your thoughts about each other. Just about, as you look at the role of women in tech and the diversity that Red Hat is trying to encourage, Limor, what have you seen in Solani here over the last day, day and a half, that maybe you think will leave a lasting impression on you? >> I love Solani's energy and her passion, and I can just, she's has this emanated strength. I can just tell that nothing stops her from achieving what she wants. Like, she wants to, like, do this Raspberry Pi traffic camera. She's just gonna figure out what it takes to solve that problem. She's gonna use open-source software, hardware, whatever it takes. And she's just gonna achieve her goal. I totally sense that from her from the last few days we've been together. >> That's great. >> Thank you. >> Yeah! >> All right. Solani, your turn. For Limor. >> What I have done is just a fraction of what she has been doing. She's, like, inspiration. I look up to her, and I, also, I mean, I hope I start my own company someday. And she's really a role model and an inspiration for me. So yeah. >> Yeah, I think you've got a pretty good mentor there in that respect. And then, DeLisa, when you see young ladies like this who are, you know, their achievements are so impressive in their respects. What does that say to you about Red Hat, the direction of the program, and then the impact on young women that you're having? >> Well, the program has gotten so much more participation. So many people, 8,000 people actually voted to select our winners. And all of our finalists were so impressive. We have major contributors to open-source, and so, along with our finalists, our winners are people who are just role models. And I am just so impressed with them, and I think that every year, we're learning something different from each of the winners. And so, as they round down into a community, the things that they'll be able to mentor people on will just be exponentially increasing. And so it's really exciting. >> Fantastic. Well, thank you all. The three of you, the ladies. Congratulations on your recognition, your accomplishments. Well done. Safe travels back to New York and back to India as well, and I would look forward to hearing more about what you're up to down the road. I think this is not the last we're gonna hear from the two of you. >> Thank you for having us. >> And thank you for calling me a young lady. >> Absolutely. I mean, look at the source. Open-source, you might say. That was awful. All right, back with more Red Hat Summit 2019. We're live here on theCUBE in Boston. (gentle music)

>> live from Boston, Massachusetts. It's the queue covering your red hat. Some twenty nineteen. You buy bread. >> Oh, good afternoon. And welcome back as the Cube continues our live coverage. Exclusive coverage of Redhead Summit twenty nineteen here in Boston. Some nine thousand strong attendees here. Key notes have been jam packed, but we just finished our afternoon session not too long ago again. Very well attended. Dynamic speakers stew Minimum. John Walls. We're joined now by Lee Dae. Who's the Vice president of Marketing Communications? That Red Hatley. Good to see you. I see you and Michael brats, who was a teacher of English as a second language of Franklin Middle School in Minneapolis, Minnesota. Mr B. Good to see you, sir. And that's what your your students call you, Mr B. Is that right? What they do, we saw that way. Might just follow through on that tradition right now. All right, let's talk about why the two of you are here together. And I know you're Michael School has an interesting history that they've been kind of following somewhat independently, you know, in terms of open source and work. And only you found them through your marketing work some really very interesting. Two avenues that you have on your platform. So tell me a little bit about how how you got here. And then we'LL get into it after that. >> Okay, Great. So Red Hat has a program called co lab and this sir program where we go into schools and we teach kids how to code. So we do things like circuit boards and programming on raspberry pies. Kids have program raspberry pies into cameras to go around cities and take pictures. And we have had collapse in many cities, and we hadn't hit the Midwest. And we chose Minneapolis. And we found, fortunately, Franklin Middle School in that great group of girls and two awesome teachers that are very inspirational on, So the relationship didn't stop it. That week of coal lab, we have stayed in touch, and here at the summit, we've showcased the work in the police ship that we have together. Yeah, >> and I know a lot of the focus that the program is toward, uh, appealing to younger ladies. You know, young girls trying to get them or involved in stem education. We just had the two award winners for the women and open source with us just a few moments ago. So this is Ahh, a company wide. Durant wants a directive initiative that you said, Okay, we we have a responsibility, and we think we have a role here to play >> absolutely well. It's important to us to see the next generation of technologists. And when you feel like women, especially young women sometimes feel like technology is inaccessible to them, and they're not often in technology programs and university. So it's our initiative. Teo help young people feel comfortable and good about technology and that they can actually code. And they can actually do things that they didn't think were possible to them previously. >> So, Mr B. Help us understand how this fixing curriculum and give us a little bit of the story of how it went down. >> Well, it's funny asset. I mean, this opportunity for us is a home run out the part because we're a steam school science, technology, engineering, arts in math. So today, not only did our students perform on the main stage a song that we were able to collaborate right and go through a >> whole production process >> with music were also able to on there right now as we speak down running a booth, building circuits, presenting those circuits, presenting those circuit boards, and collaborating altogether down there with attendees of this conference right now. So, I mean, we're covering every one of those steam components, basically, in one project, one large scale technology project. So this opportunity homeland out the >> part. >> I love that because that was the first thing I went to mind. I heard photography involved. You say steam and so much, you know, we can't just have tech for Tex take. You know, I worried I studied engineering and, like, things like design and those kind of things right weren't in the curriculum. But you know what? I went to school. Creative side. Yeah. How important is that? You kind of get especially think young people get the enthusiasm going. That creative side would, you know, get them deeper into it. >> Well, you know, I always look att, individual students. Everybody has their individual gifts and talents, and it's about, you know, finding those leadership skills within each one of those gifts. And so within this, you're able to find someone that might be more creative in one area, maybe more technical and more, you know, logic orientated in other areas. So with that, you're able to just have Mohr a broader spectrum to be ableto find people's individual gives in towns and for them to in the collaboration also contribute their gifts and talents in different avenues instead of it just being one lane like just this part of technology or just this part of production and just this part of design were able to kind of integrate all of that into one thing and to take it one step further. After we did the, um So Cola came out with their mobile container to US Bank Stadium in Minneapolis, Minnesota, and it was right downtown, right outside of where our football team players brand new stadium Super Bowl is is there two years ago now And, um, so with our students being there after we got done with that, that cold lamb, when they were asking us, you know, to take it a step further in the classroom are students actually designed with our future boys Lo Bill Future Girls logo a card and then presented it to Red hat and they ended up printing off the cars and they were able to use it to build the circuit. So we weren't just using the coal lab cars. But we also got to design our own, too. >> So, you know, you said future boy's feet. So that's that's a new organization, the club that you formed the school Future Boys and Girls Club for the express purpose of what? >> Well, so we actually tie in all different content areas into assault. Obviously, this is just the future girls that are here in Boston and did the technology side with us and that parts of Spain the cold because it's an initiative for girls in technology but of the future boys and girls, uh, overall program. We encompass a lot of different continent as we integrate performing arts with academics and all the components of esteem school, um, into learning. And we do interest based learning. We do project based learning, and basically, you know, kids are learning a lot without realizing how much they're really learning, you know, and we make it fun and relevant. But we also teach the leadership skills in the hard work that goes in with it. And I mean, even just coming out here to Boston for this, uh, for this opportunity here in this summit, I mean, the amount of work that it took for the students to get here and the process, the ups and downs, especially with middle school students. You know, the marathon, not a sprint mentality, you know, has been absolutely amazing. >> Good luck with that eye. Well, >> I always say I >> haven't had a bad day yet. Just an overstimulating one. >> So lately, you know, we love having stories on the Cube and especially tech for good is something that we always get a good dose here at Red had some it. You know what else can share some of the open tour stories that were going on around the event? >> We're really thrilled. Today. We're launching our newest open source story, which is about agriculture and which we choose topics with open source stories that are important every everyone so medicine, helping to find cures for cancer, even our government and artificial intelligence. And today it's about open hardware and open agriculture. And we're launching a new film this afternoon. >> It's all future farming, right? Right. That that's the viewing today. >> Yes, and we had someone showing their their farming computer on our stage, and it's actually done in Summit >> Show for today. So you've got the open studio, you know, working and you have a number of projects. I assume this fell into one of those slots right where you were Using one of those platforms to feature great work of future farming is another example of this, But But you have some, I think, pretty neat things that you've created some slots that give you a chance to promote open source in a very practical and very relatable way. >> Yes, exactly. So our Opens our open studio is our internal creative community agency. But we do get ideas from everyone around, you know, around the world. So wait, get ideas about open agriculture, eh? I, uh, what we can do with kids and programming with kids. And then we take those ideas into the open studio and it is a meritocracy. So the best ideas when and that's what we choose to bring to life. And we have designers and writers and filmmakers and strategist and a whole group of people that make up the open studio inside a red hat >> And you've done a new feature, Frank. >> Yes. So, yeah. We work together to create the container that doctor be mentioned and to create the container. And then we work. When >> you have you >> have. You know, one of the girls Taylor actually taught me just now I am not technical. I will just give that caveat. But they they make, they made circuit boards, and they're making circuit boards here. Some issue and mine doesn't work. So don't That's okay. Just, basically were you can see here we have different designs that are attendees can choose from, and then we have electrical tape that you are sorry, competent and an led light. And so the idea is to toe form a circuit and to have led light item the card. That's great. So one of the one of the girls actually taught me how to make it, but I think I didn't follow >> her. Instructed you to go back to school. Wouldn't be the first time that I would have fallen apart either on that. So where Michael, Where would you be now without red hat? Or, you know, you were doing your own thing right independently. But now you've received some unexpected support. Where would you be? You think was out that help. And how much of a difference have they made >> you? Well, let me tell you. I mean, you know, when we look at it being an after school program, the amount of enrichment and opportunities that redhead has created for us has been, honestly, just unbelievable. It's been first class, and we're so appreciative. I mean, even even in our meeting with the future girls last night, we just talked about gratitude and how grateful we are for it. I mean, when you look at this circuit, this is an abbreviated version of what the students actually participate in. This is, you know, just a one one, uh, one led light and a small formation our students were doing. I think there were seven or eight on ours. And so the amount of learning in the modern opportunity that this presented to him not only have they learned how to do the technical piece of it, they've learned howto present. They've learned howto speak and present. They've learned howto call lab, collaborate, work together on huge levels, and I mean, they learned what they can take on an airplane, you know, coming out here. So I mean, the amount of things that through the learning process of, like, eye color, large scale technology project that we've been participating since October since they brought the mobile lab out to Minneapolis. I called a large scale tech, you know, technology project, and going through that whole process has been huge. And let me tell you this as a teacher and those that are parents you're competing was so much in this day and age to keep kids attention, right? I mean, everything is swiped the phone every which way and everything. So instant gratification. So for students to actually engage in this cola program for to be set up so well from Red Hat and to actually stick with it and stay engaged with it really speaks volumes denying the program. But also, you know, our students staying engaged with it, but they've they've stuck with it, they've been engaged, and it's very interest based, the project I've seen it through. But then also the renewed opportunities and being ableto one of the things on our rubric as the teacher is toe expand and extend the learning I don't mean to be long winded, but we wanted, you know, expand on the learning that's already taken place and being out here, it's just it's just a continuous continuation of the learning, you know, not just one level going to next level going on next long light, next level. And that's that, honestly, is where the real learning really takes place. >> So, Michael, you know, from its very nature being an open source company, you know, Red Hat talks a lot about it. Ecosystem in community. If I five red right in the notes, they're you know, your student really getting the value and understanding of community. There's something about they wrote a song. Talk >> about that. We become stronger. Yeah, that's the name of the song is we become stronger And you know what the idea was. We were looking at the power point for this summer and for this summit, and in that there was, uh there was a phrase that said ideas become stronger and that's the collaboration. And so we started tossed around ideas and things like that were like, Well, we liked the idea of stronger, and then we're like, Well, this is more of the coal lab experience, not just the ideas of the technical side. And that's why we become stronger. And yet we developed a song specifically for this summit. I think you go top for, you know. >> Yeah, the performance was amazing. >> Yeah, you don't want >> one top forty, to be honest with you, but no. I mean, uh, you know, and that was another whole another phase, you know, like, I talked about the steam side of the school. Um uh, integrating the arts in and the whole production side of that, you know, it was a lot of work and another project, but it was another area of content that we're able to integrate into this project, and, uh, and we're able to perform it on stage. So, like I said, they literally just got off stage performing. We become stronger singing the whole production of song a dance routine choreography and then went straight to the boot to now present circuits and teach attendees here at the summit howto build a circuit. I don't know how much better can get in that. >> That is so cool. That's great. Now is this the song that you recorded in the same studio. Lenny Kravitz. Atlantis More. Tell me you didn't like that, huh? >> I mean, you know, it's all right. >> That's good. That's great. Congratulations, Roy. On this collaboration, it's really it is exciting to see what they're doing to inspire young people on Michael. I can tell you like your job. Don't you love it? I love it. Yeah, yeah, yeah, absolutely. Well, keep up the great work. And we appreciate the time here. And I look forward to hearing that song. Maybe if it hits, you know, the ice store. You know, Apple Store, maybe, You know, maybe good things will happen, right? Hey, you never know. She's Vice president marketing. We're gonna figure this. I'm checking out. I tio go by weight, become stronger. Thanks, Michael. We appreciate Lee. Thank you for having me back with more. Here on the Cube. You're watching our coverage, right? Had some twenty nineteen, but