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]

>> [Disembodied Voice] From New York, it's the cube. Covering escape 19. >> Welcome back to the Cube's coverage here in New York City for the inaugural multi-cloud conference called Escape 2019. This is a conference dedicated, first conference dedicated to conversations and content and people around the trend of multi-cloud, which I've been critical of, I've called BS in the past. But it is multi-vendor it's developing and the architecture for true multi-cloud is on the horizon. Where well, we will be relevant. Our next guest is Daniel Wall, senior Distinguished Engineer at Red Hat, working on a lot of the technology around what Kubernetes and containers is create a lot of buzz around and that is the abstraction layer around working across clouds. Daniel, welcome to The Cube. >> Thank you for having me. >> I'm sure I butchered what you do, but I know you make a lot of tools. You make containers work. Talk about your role at Red Hat real quick. >> So my role at Red Hat is I am the technical lead of container technology, everything basically underneath Kubernetes main projects over the last few years is to look at what Docker did and then split them into individual tasks. I believe that Docker should be broken into four different main tasks move and container images around playing with containers, building container images, and running containers in production. And then we can run different security realms around each one of them. So we have tools to do that a Scopio, Podman build, and CRI-O is the one we use for Kubernetes. >> And how's it going? Good? >> It's going great. Yeah, we're getting great up. A lot of community support. A lot of people are really excited about some of the security features for so you can run full containers where you traditionally would do a darker you can run a totally non routes and much more secure. >> Well, I'm really interested in your talk you're giving here because the folks that follow The Cube know some of my tirades I've been on the past. I've been saying for a long time that there's been a very non-selection of clouds outside the big three, >> Right. >> And you had a power law that has, know who the big guys and a long tail of people creating their own little niche services. But income, the essentials and the global size and channel part is people using cloud. We have a video cloud, we're building more and more clouds for our media business. This, I was talking about the rise of these new clouds right?. >> Right. >> You're actually put some structure around this around, You're talking about Walmart clouds and niche clouds. Could you explain so this is really important. I want you to take some time to explain that. >> Okay, so my talk today I call it the Walmart clouds, although the analogy is when Walmart first started showing up in the United States and different areas, all of the department stores basically went out of business because Walmart was able to out-commoditize everything in the universe. And so, all these major vendors, district department stores went out of business. The one thing that didn't go out of business was sort of like specialty stores. So, I always kid around and say my wife has me every weekend sitting out front of these specialty stores that she loves to stop shop at. So if I look at the way the clouds have happened is basically most people say there's three major clouds, although I think they ignore one. So you look at Amazon, you have Google and you have Microsoft Azure, although I think Alibaba is going to become important in the future. And I call those the Walmart clouds, because basically, their whole goal is to commoditize and get rid of all the other, >> And scale up and provide more and more departments more services, >> But basically it they will always be rushing to get to the cheapest price. But there were a bunch of other cloud vendors out of the specialty cloud vendors like you talking about the Cube one, you this might be the best one to do in video. So I might want to put part of my workload in the Microsoft cloud or the Amazon cloud to get the cheapest price but I want to run certain certain workloads inside the U.S. We look at another example that is Nvidia right? and there's the Nvidia cloud and they might put the best GPUs in there. And you might want to do your machine learning your AI technologies might want to go in there because they might work better. IBM, who obviously bought Red Hat, but but IBM, you look at what they're doing in their cloud, they can have power series, they can have, mainframe workload z series. They might even have, some of their future, super duper computers type things in it. And then you have Oracle and Oracle would have database, they're probably going to do databases, they've massive database technologies inside of their cloud. So when you really >> Well, they think they're one of the big clouds. But they're not. >> They do. >> But their specialty Database Cloud. >> Basically, I believe that they are. I believe IBM, I think all of them are niche, especially clouds. But the bottom line is you need an API to move between these clouds so you can put workloads in different instances. And I believe that the Walmart clouds the the AWS and Microsoft and Google, their whole goal is to get you into their cloud. They might talk a little bit about on prem cloud and supporting your data centers. But their real goal is to get you off your data centers into their cloud, so they can start making money. They won't have no interest in supporting these, sort of the specialty cloud vendors. But if you look at open shift, which Kubernetes, from Red Hat, our goal is to basically make moving your cloud instances around and keep commodity and stability and move to clouds around. >> Let's take it through a working example. So there's couples and use cases that I see happening, I want to get your reaction. One is our cloud. We're (mutters intelligibly) which we do have. It's coming out. It's on Amazon. So we were small, self funded, company growing having fun. We're building on Amazon. We don't do any work in Azure our solutions on Amazon. Another use case might be a vendor that says hey I have proprietary software, I'm going to stand up my own cloud infrastructure and do all that and build it from the ground up. Is there a difference between the two? Because one is co-locating essentially on Amazon. leveraging the cheap commodity, but building differentiated niche on top of it, versus the standing up a full cloud? >> Well, what I would argue, first of all is is I would want you are your cloud, the one that you're saying is in say, Amazon, it what is the chance of you guys basically getting an offer from Azure to a nickel less per hour. >> Pretty high!(laughs amusingly) >> To be able to move your cloud over, >> It might be high. >> And the problem I would see is if your cloud inside of Amazon cloud starts to take advantage of Amazon's features, then all of a sudden it gets harder and harder for you. the cost of moving off is going to get harder and harder. If you use open source solutions, pure open source and not tied to individual cloud vendors. Then it would become much easier for you to move around. So you could take advantage of, commodity, right? And that you mean, another analogy I use with the big cloud vendors is Hansel and Gretel right. They all want you to come on in and come on in have some of our candy, have some our candy. And next thing you know, you're inside the cage. And, you know, but if you stick to open source, right, this is in a lot of ways the major cloud vendors is a major threat to open source, and that they're trying to lock everybody in right there. We lost it. >> Okay so what's the path? So I told it, by the way, I'm getting what your saying. So I say great I'll take advantage of the cheap I as the infrastructure service layer. But then what an open source toy usually open shift, I still got to build my app, I got to still host it. >> Right. So you build you build your app on top of it. So let me define what open shift is. And so open shift is basically Red Hat's enterprise version of Kubernetes. So if you look at Kubernetes, Kubernetes in some ways is just a higher level distribution of software. So when when Red Hats got into Linux business, there were lots and lots of Linux distributions. And what Red Hat did is they picked a whole kernel and a whole bunch of packages and joined them together and created a distribution that everybody could agree on and build on. So with open shift we're doing is we're taking Kubernetes, but there's a whole bunch of CNCF projects, and we're joining them all together and then testing them and making enterprise so that ready. But really Kubernetes is the key factor here in that if you build everything Kubernetes you CNCF open source projects, for your, save your storage, put it on staff, so Gloucester, one of the network based file systems in the open source world, instead of diving directly into Amazon, now you have the flexibility to be able to get out of the- >> So here's an Architectural question. So I got to ask you as multi-cloud conversation starts to heat up, and by the way, I think people have multiple clouds. It's just not multi-clouding. Right, right, right. Yeah, but it's coming. So architecturally what do someone have to think about architecturally for multi cloud? What's in the mind of the technical architect out there? >> What's on them? What are they should be thinking about from an architecture because you don't want to forclose the future. But I also want to get the best what I can get today from the clouds. >> I mean, I keep keep on hammering on it, but stick to the open source projects to do this as the CNCF projects just to allow you flexibility. A lot of it, the real problem with a lot of this technology right now is it's developing so fast. I mean, I think we have a Kubernetes version every two weeks, it seems at least in my team and see it feels like it. >> So you think Red Hat's of good vendor for the supplier for that person. >> Obviously >> Yeah you know some stuff is hard to deal with so it (mutters) look I'm so busy, these guys, I'm trying to get the transformation going. I don't have time to keep track of what's going on in CNCF. >> Yeah, well, we're a co worker of mine talks about your Red Hat and open shift is a plumbing tool or an electric we're building the foundation of your house and we put the electrical systems and the plumbing empties into your house, but we still need applications to run so we need you you need a toast or you need a toilet, you need a sink. And the applications and one of the one of the differences between Red hat and sort of the cloud vendors is we try not to get into the product, the lab and product business. So we want to support open source projects and other products running in our environment. If you compare that to running inside a cloud, you know if you become incredibly successful inside of Amazon, your video cloud business wants to prevent Amazon to say, oh, we'll just do video will steal everything they're doing and all a sudden we'll do the video inside of Amazon and then put your your cloud out of business. And, your only option then is now you're competing Amazon in Amazon against Amazon. How do you get out of Amazon >> That's called 3D chess.I think. Or maybe 4D chess. >> So if you you know My point being if you have an opportunity to get out and compete against Amazon say on Microsoft compete on your local compete on one of the niche clouds So any vendor that basically ties totally to Amazon, >> This is this is absolutely why I'm here because I believe multi-vendor, that was the buzzword in the 80s and 90s. Is everyone wants to they want to homogeneous they want a heterogeneous network. So multi-vendor will be around multi-cloud has to survive, it will survive. But right now we are in the foundational stages. The second interview, he has talked about plumbing and streets, and that's what we're at. So I guess the final question for you is, as we're setting the foundational infrastructure for multi-cloud, what's the big takeaway that you see that you could share? You mentioned get involved in open source what specifically architecturally should should folks think about in terms of foundational. >> I think, look at what the CNCF that cloud cloud native foundation is doing for open source projects, depends on what level you want to come in. And the bottom line is, built on top of Kubernetes use open standards to do it. Don't fall for the Hansel and Gretel effect of eating the candy because you will find yourself in a cage. >> Well, multi cloud is arrived and it's being thought through by industry leaders from entrepreneurs. We just had the former CEO of Sierra on, now running AVA trace, industry veteran, lot of tech chops in here, laying down the lines, if you will. A lot of good stuff Kubernetes is a key part of the containers. >> Okay, huge part of it. Thanks for coming on. >> Thanks for having me. >> And thanks for sharing the insights here on The Cube. We're in New York City for the inaugural multi-cloud conference Escape 19. I'm John Furrier back with more after this short break (pulsating music) (pulsating music)

>>Live from Copenhagen, Denmark. It's the cube covering Nutanix dot. Next 2019 brought to you by Nutanix. >>Welcome back everyone to the cubes live coverage of next here in Copenhagen. We are of course here at the Nutanix show. We are wrapping up a fantastic today show. I'm your host, Rebecca Knight. Been Cosa hosting alongside of Stu Miniman. We are joined by Simon Taylor. He is the CEO of haiku, a good friend of the cube. Thank you so much for coming back on the show. It's a pleasure to be here. It's great to see you guys again. Final guest. Oh my gosh. It's a, it's a fare to stay interested in your energy. Yes. So for our viewers who are not as familiar with haiku, tell us a little bit about your business and how you are a strategic partner of Nutanix. >> Sure, sure. So haiku actually is a software company that focuses on data protection as a service. We actually started by spinning out of a much larger company called calm train that had about a thousand engineers and was doing all sorts of things, but they had an amazing talent for building backup and recovery software. >>Um, my vision was really that we can move up the value chain and we can establish ourselves as our own brand, as long as we could find a place in the market that was fast growing, building like a rocket ship and was really requiring a new kind of data protection and backup. And honestly, as soon as we fell, we saw Nutanix, we sort of fell in love. We realized that, you know, they had developed an entirely new category of business with hyperconverged and they were really a pioneer in that space. So we said is why don't we build the world's first purpose-built backup and recovery for Nutanix? And that's exactly what we did. And I think, you know, Stu was actually one of the first people to ever hear about it. Uh, we came on the cube and we talked about that. We've GA that in 2017 in July. I think@that.next, um, so just two and a half years later, we now have 1200 customers and we're in 62 countries around the world. So it's been absolutely astonishing. It's been wonderful growth. We're seeing 300% year over year growth. Uh, and really a lot of that is just based on our ability to protect the data of Nutanix customers around the world. >>Well and and Simon, right? That early question was, is new CanOx is going to be big enough to support ISV is that, you know, can run the, you know, grow their business underneath them before we get further and talk about mine and everything. Give us a little bit, you know, the state of the state for haiku because started with Nutanix, but that's not the only solution they are offering Dave. So just give us kind of the snapshot of the whole business. >>What we realized as we were building out high Q in this purpose build backup recovery for new TEDx. We said that's the on-prem, you know, but there's a lot of on prem that is still legacy three tier architecture. So we added a VMware product. But really the goal was to offer true multi-cloud data protection as a service. So what we did is we built the independent purpose-built backup and recovery service from Nutanix, one for VMware. Then we built the world's first purpose build backup as a service for Google cloud. And I'm really thrilled to announce the next month we're launching Azure backup as well. And the brilliant thing about our system and our solution is that we actually enabled customers to not only back up their data independently for that cloud, but that then migrate their data to whatever other cloud they want to use. So we actually becomes data protection as a service, data migration, and dr. >>So for, for customers, this is wonderful, but how is it to be strategic partners with all of these big players? >> Oh yeah, absolutely. I think you have to place your bets, right? So if you notice, I didn't say AWS and almost every company that I talked to says, why wouldn't you start with AWS? They're the biggest, you know, that's never been our philosophy. You know, I think the fact that we attach ourselves to Nutanix so early, not just because they were a rocket ship on fire, but also because we truly believed in their vision. We believe in the Nutanix products, we love Daraja entire philosophy around simplicity and customer delight and we felt like we could be students of Nutanix, we could actually build out our product with those same philosophies and principles in mind. You know? So I think really going deep with Nutanix is number one for us remains number one. I would also say though that you know, Google has been an excellent partner and Microsoft been an excellent partner. So with the large cloud providers you have to take a different approach. You cannot offer a downloadable product, right? All of our public cloud backup and recovery is a true managed service. You go into their app store, you turn it on rather than download it, you configure and you're able to perform all your backup and do all your recovery right from the console. >>All right, so Simon let, let's get into the kind of the, the, the guts of what's happening at Nutanix. Mine, of course is a partnership to extend for data protection, partnering with Veeam and haikus as a, as the first two partners. Uh, the other thing that everybody's pretty excited about is XY clusters. And that sounds like, and we've talked to Newtanics people, you know, as Nutanix brings their stack into the clouds, not just on the clouds, will that pull things like mine along with them. And so, so give us what you're seeing with mine first and maybe he's, I clusters along. >>Yeah. So maybe we start with mine, right? This whole concept that I think that these guys have pioneered and they've done a really terrific job of it. I think, you know, the, the vision there, and you know, I count marketing or Meyer in this group and Tim Isaacs and some wonderful folks on the product team in Nutanix. Their vision was, you know, there's rubric and there's Cohesity, there's these sort of large secondary storage platforms. Personally, when I look at them, what I see as Newtanics with a backup workload, right? And I think that, you know, Nutanix being the original is the best. It's the most complete solution. And it's very, very comprehensive. So I think the, the tannics folks understood this intuitively and their idea was instead of us building our own backup and going after that space, we've got amazing partners like haiku. Why don't we just natively integrate them into the mind platform and offer that sort of secondary storage workload, uh, as a key part of Nutanix is product proposition. >>So the really exciting thing for us is that we are skewed up with Nutanix. Nutanix, we'll be able to resell haiku as a part of mine. Uh, and I think that's gonna really complete their end tour tire story when it comes to being able to own the data center, uh, and really own the sort of cloud in general. You know. So I think your second question still was about clusters. And I think that the answer there is very simple. You know, multi Gloucester is, has become extremely important for Nutanix customers. They've done a great job of going after that. The simple fact is if you don't support XY clusters as a backup vendor, you really can't compete in this market. So I'm really thrilled to announce, of course, that haiku is the first backup recovery vendor that does support. Gluster. >>Okay. So interesting. We talked about how you hadn't done a solution for AWS. Sounds like this might be a path for you to get with Nutanix onto AWS. >>Absolutely, absolutely. And again, for us it's not about looking for some Trojan horse or backdoor into a go to market strategy. It's about making sure that the customers are truly delighted by the value that we provide. And I think that when we go after a specific market, we want to do it the best, you know, so we don't go shallow and just sort of check the box. We want to make sure, for example, when we build out Azure that we're not just dealing with, you know, the, the general principle of backing up and keeping things consistent. We want to make sure the applications people are running on Azure or supported by haiku. That's what we do with Nutanix. That's what we do with GCP. We want to always go as deep as possible so we can really compliment the platform in a really, really comprehensive way. >>One of the things you said earlier was that your philosophy is very much aligned with Nutanix, your your end goal to simplify and delight the customer, uh, this, this much more intuitive, uh, youth and user interface. So talk a little bit about how you, you said you wanted to become a student of Nutanix, yo, this, this cross company learning is very interesting to me. How, how, what have you learned? Yeah. What have you learned and how do you go about being tutored by your customers? >>No, I'm a very visual guy, right? And whenever I think about Nutanix, I always had this image in my head. All right. Whenever I thought about legacy, three-tier architecture and the move to hyperconverged, rather, I always pictured an 80 stereo system. Remember those big eighties boxes? And they have all the graphic equalizers and all the way down. And some kid would come and push them all down. You could never reset the darn things, you know? And then along comes, you know, automation and suddenly, you know, you press a button and you listen to jazz and it sounds like good jazz and the treble and the bass all fixed themselves. You know, I effectively think that Nutanix brought that same concept, funnily enough into the data center. They simplified so much that was impossible to handle for admins across the world. They made it so simple to use their product that actually the customers could start to enjoy their work more. >>And I really love that. That's a true, that's a really an intangible sort of value proposition that I think people don't talk about it enough. Yes, you want to save time. Yes, you want to save money, but if you could enjoy your job more as a result of getting a product, what's better than that? Um, so I think that philosophy is something we baked into haiku in the following ways. You know, the first is when we were designing the UI, we wanted it to look and feel like the platform it supports. So when you use haiku for Nutanix, it looks like prism, when you are using our console for GCP, you're gonna feel like you're using GCP. The idea is that backup and recovery should be an extension of that cloud expression, that platform, so that the customer who is an expert with that platform can easily manage this with no training at all. So again, driving that simplicity right there and in the platform. >>Yeah. So Simon, you know, one of the things we love to do is get hear from customers and what they're doing. Of course you've got 1200 customers that are Nutanix customers. So we'd love to hear, you know, any insights you have in a lot of discussion about AHV in the last 12 months has been about half of the deployment. Is there anything around HV or any of the, you know, new software features and products and experiences that Nutanix has been launching that you hear customers buzzing and talking to you about? >>I mean, I, I, the first thing I would say is it is truly a multicloud world now. Um, I think that legacy vendors are having a harder and harder time coping with the fact that cloud washing no longer works. You know, if you show up to the market and you say, Oh, this, now I can deploy an agent into this cloud, it's sort of stop, stop, don't say agent around me. You know? So I think, I think the ability to really natively integrate into any of these clouds and support all of these clouds equally is key. You know? So in the past a vendor would start with one thing and it would be great, right? And I won't use names here, but then they would do something else. They might move to another hypervisor and it was a little bit less great. Right. And I think that that notion has to change in a multicloud world, which brings me to the concept of HV. >>I think that HV has really grown. I mean, I would say that right now, you know, over half of our customers are HV customers. And I would say that that grows every single quarter and it not only grows in terms of net new logos, it also grows in terms of existing customers that we're finding SWAT to switch to HV and they want to switch fast. You know, they don't want to pay the V tax anymore, but more than that, I think they're seeing HV as a really robust enterprise hypervisor that really meets the complete need for the customer. And I think that's, that's been terrific to watch. So when you hear at.next, and this is not your first hot next, but what kinds of conversations are you having? What's been interesting to you? What are you going to take back to haiku? Yeah, head back to Brookline. Yeah. >>I mean obviously there's all the new stuff. I mean, Kubernetes, you know, containers. Um, I think these are all things we've been working on for some time. We'll have some surprises for you guys in Q4 at the end of Q four around that. Um, but you know, I think the big takeaway for me is we spent the first two years building our brand, getting the word out there, proving to companies and customers around the world that we were truly enterprise ready cause we were the new kid on the block. And you have to sort of start somewhere and show that. I think now we, you know, we added physical last year, we added tape support, we've really got all of the major applications covered at this point. I think that conversation, we've checked the box, right? So today's conversations are about what's next, how much more deeply will you integrate with Nutanix? >>How can I use Nutanix to then manage my data in the cloud and bring it back again? And can haikus support that or will it distract me? And you know, the simple answer is it will support that completely because it's so natively integrated. You know. And again, I think when you choose a platform at this stage, and this is something we've seen again and again and again, people do not want a second silo, right? In order to, you know, run their backup and recovery. You know, customers who are choosing Nutanix or choosing any platform want to run that platform and they want to make that one holistic experience. You know, they want to reduce the training required and they want to make sure they get the most out of their investment. So we're where I think two or three years ago, Stu, when we first met, everybody was trying new things, right? It was sort of, there were all these new platforms and it was all very exciting. I think now people are doubling, tripling, quadrupling down on the platforms they fundamentally believe in. And we're thrilled about that because we support those platforms and we'll continue to do so. >>Great. Excellent little. Simon, thank you so much for coming on the cube. It was a real pleasure talking to you and it's been great. Yes, no, absolutely. Thank you very much. Thank you so much. Thank you for having me. That wraps up two brilliant days in Copenhagen at the Bella center at Nutanix dot. Next. Thank you so much for joining us and we hope to see you next time.

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

(upbeat music) >> Hi everybody, welcome back to London. You're watching The Cube, and we have a special coverage here of the pre-day at AWS headquarters in London. I'm Dave Vellante and The Cube, we go out to the events, we extract the signal from the noise. Alastair Allen is here, the chief technical officer of Healthcare Kainos Software. It's a Belfast based company, publicly traded company. Alastair, welcome to The Cube. Great to see you, thanks for coming out. You were downstairs earlier addressing the audience, we're gonna talk about that. But first of all, tell us about Kainos. >> So Kainos, Belfast based company, formed in the late '80's a spin out of Queens University in Belfast. We've grown to now over 1300 people and we build digital technology to help people work faster, smarter and better. There's two things we do. We provide digital services, bespoke services for public and private sector organizations across the world, and we provide digital platforms for work day customers and also for healthcare organizations. >> So, when you say digital platforms. What exactly do you mean by that? Tell our audience. >> So, our digital platforms in healthcare is something that we can talk about. So platforms to enable both hospitals to digitize their workflow and also regions, so CCG's , STP's within the NHS. To bring information together using a platform and normalizing that data and making it available to clinicians and patients. >> And this is, your flagship product is called Evolve. Correct? >> Correct. >> And you're one of the sort of founders or inventors of Evolve. Tell us more about Evolve. >> So Evolve, originated just over ten years ago, our first customer was Ipswich Hospital and Ipswich had a big problem with paper, with a large medical records library and they asked us to come in and help them digitize that and make it available in an easy to view, accessible format for their clinicians. >> So tell me more about that. So you digitize it, you take all this mounds of paper and what does that do? Other than reduce the amounts of paper. Does it make it searchable? >> Yeah, we index the content, we apply metadata whenever we capture it, trying to make it accessible for clinicians. I think when you digitize paper , the one good thing paper had going for it was you could pick it up and it was tactile. So we've done a lot of work to try and make it mobile, make it accessible, make it searchable and increasingly now with some of the services that AWS provide, we're able to look at taking that even further and getting more information out of that content. >> Add some color to that. So how has the AWS cloud affected your ability to deliver these capabilities to your customers? >> Well I think, the breathe and depth of services that AWS provide, enables us to be able to innovate quickly, to use services like I've mentioned like comprehend medical. That take the heavy lifting, away from us and helps us focus on delivering better applications for our customers. >> So part of what you do, is you architected the software that's running on the cloud. Can you talk a little bit about the architecture? What you guys have built. Presumably the cloud allows you to scale. >> Alastair Allen: Yeah. >> And take advantage of more innovations. But discuss the architecture if you would. >> So, the product that I originally talked about in 2009 and about four years ago in 2015, we decided to re-platform for the cloud. And that was in response to a number of problems that we were seeing in the market. And moved to patient centered care, a drive to try and standardize care away from the variable nature that was there and also to get away from closed silos of information. And we decided at that point to create our platform natively in the cloud and using the services of Amazon web services. So we created a microservices based architecture that runs in multi-candidate cloud native way. With a AWS. That allows us to adopt disciplines like continuous delivery and cultures like DeVops. We've been able to release value quickly and often to our customers. >> So it was a total rewrite of the platform? >> Yes. So we started again from scratch and we developed that using the modern cloud services. And we've used that then for all use cases as well so we've moved beyond just settings within a hospital. And been able to take that beyond the walls of a hospital, out into the community, into primary care, mental health. And delivering solutions like that, across regions within the NHS, to join up information. Where before clinicians would simply not have had access to those. >> In a sense you're migrating your existing install base to the cloud based platform, as I presume it's a SAS based platform. Is that right? >> So, Evolve Integrated Care is a platform it's a SAS based platform. So we run it, we monitor it, we maintain it and we deliver that as a service to our customers. >> And so your existing customers now have an opportunity to migrate and how does that all work? >> Yeah, so we're talking to our existing customers, how they can leverage the cloud based platform and the breathe of different services that it provides. We very much see an opportunity for helping to digitize a hospital. So how do you optimize the flow of patients through a hospital and making sure that clinicians have access to the information. Many of customers have hundreds of applications, information spread across their estate, bringing that together and orchestrating the workflow for particular pathways or particular conditions. >> Plus they have to manage their own infrastructure, I presume. >> Absolutely, and we want to build applications quickly, they want to focus on delivering healthcare. They don't want to focus on managing ten and server rooms within their hospitals. So, our move to the cloud really came about because of our customers telling us that they're struggling to manage this infrastructure. They wanted us to take some of that burden away from them and to help them with some of their security challenges, availability challenges. Quite often their local infrastructure was not very resilient. And by moving to AWS, we were able to use native cloud services to address many of those challenges. >> So you're taking away that heavy lifting for them. AWS takes it away for you. >> Alastair Allen: Yeah. >> In a large regard as well. While your engineers can obviously program the infrastructure. But how have you seen the customers that have moved and taken advantage of this. What has it done for their business specifically? What's the impact? >> So, what I think, it frees up people within their organization to scale up in other areas to do other things. It frees up physical space as well in many cases. It takes away risks and we've all heard of some of the recent security incidents. Wanna Cry was a huge thing in the NHS not so long ago. Coming around from just simple things like not patching servers and work stations. So, by taking on that responsibility we're freeing up those hospital systems to focus on what they do best. >> How do they do that? Do they kind of retrain folks? What's that been like? I presume it wasn't frictionless but it's an opportunity for people to advance their careers. Do you have any visibility on how your customers have handled that? >> To be honest, not a huge amount. It has, I agree, there has been some friction there. It's not always an easy journey, there's a whole mindset change of what people used to do before and the types of activity that they'll do tomorrow. And it's something that our customers are still on a journey on. And so we're quite early on in that process. >> But I would say to folks in the IT community of your expertise's of managing storage arase, there's probably a better future for you if you can move up the stack and learn more about applications , data, machine intelligence. >> Absolutely, higher up the value chain and getting closer to the user, closer to the customer. >> I mean, that's where the difference is. And it's particularly in healthcare right? You try to balance the cost of healthcare, everybody's aware of the rising cost of healthcare with the patient outcomes. And technology is a way to address that problem. Isn't it? >> Absolutely, and I think never before. I think it's just a great time to work in health IT. We've now got access to some fantastic services the rise of artificial intelligence, the machine learning has never before been so available. And really having organizations such as ourselves to really solve those problems that our customers have and introduce those efficiencies and ultimately better patient outcomes. >> So how are you using the data that lives in Evolve, I presume you're looking at applying artificial intelligence and the like, talk about that. But also, how do you ensure security, privacy, etcetera? >> So, a couple things on data, I think one of the things we've done recently is the adoption of the FHIR standard within healthcare and all the data that we aggregate from the various clinical systems, we normalize that down into a single FHIR data profile and that really helps us then have a common data model that our application can use. But that's only the start, that creates the potential then to use that for secondary usage, such as publishing health data analytics and ultimately machine learning. And we're looking at a number of errors in machine learning, I think there are some ethical challenges there to be aware of and we've started with a recent examples of understanding how we can use machine learning to try and get that structured data out of the documents, that's something that we're working on with data with the AWS team at the minute, to leverage a lot of that scanned content that we have and evolve and be able to create the structured outcome. Really to make it easier for clinicians to find information within the medical record. >> So the AWS reinvent last fall, you know Sage Maker was of course buzzing. Is that something that you're looking at? >> It's something, so we haven't used it in Evolve so far but within Kainos we have an AI practice and we have a group of guys that are focused on the AI capability. Evaluating those tools, working with AWS and helping us understand how we can use that technology to solve the problems of our customers. >> Yeah, it's early days. So you talk about helping solve the problems of the customers. Summarize for us the key problems that you see machine intelligence, AI solving. >> I think there's probably different categories of how you could use it. There's the diagnostic sort of use case where you could use AI to help process imagery, to help with the diagnostic process. There's being able to add personalization to whether that be to patients or to clinicians, helping to provide insight into whatever the use case may be and all the use cases similar to that. >> Last words, so you're addressing the pre-day healthcare reform that's going on here at AWS. What's that like, what's going on downstairs, what did you tell the audience? >> Yeah, great day. So we had a group of healthcare professionals across the NHS in Ireland, very interesting group. We spoke this morning, I spoke with our customer Gloucester CC chief and we talked about the shared care record solution that we've delivered into Gloucester. So that's bringing information together for over 600,000 patients across the region and providing information in a single joined up view that was not available before. So great feedback, great interaction, lots of questions afterwards so looking forward to going back down and chatting some more to the group. >> Excellent. Hard to do that without the cloud I would imagine , accommodating all of the 600,000 customers right. >> Not possible. >> Alastair thanks so much for coming to The Cube. >> Thanks, Dave. >> Appreciate having you. Alright, thanks for watching everybody. Keep it right there, we'll be back with our next guest. You're watching The Cube from AWS headquarter in London. We'll be right back. (upbeat music)