>>Hey everyone, it's Vegas. Welcome back. We know you've been watching all day. We appreciate that. We always love being able to bring you some great content on the Cube Live from AWS Reinvented 22. Lisa Martin here with Paul Gill. And Paul, we've had such a great event. We've, I think we've done nearly 70 interviews since we started on the Cube on >>Monday night. I believe we just hit 70. Yeah, we just hit 70. You must feel like you've done half of >>Them. I really do. But we've been having great conversations. There's so much innovation going on at aws. Nothing slowed them down during the pandemic. We love also talking about the innovation, the flywheel that is their partner ecosystem. We're gonna have a great conversation about that >>Next. And as we've said, going back to day one, the energy of the show is remarkable. And here we are, we're getting late in the afternoon on day two, and there's just as much activity, just as much energy out there as, as the beginning of the first day. I have no doubt day three will be the >>Same. I agree. There's been no slowdown. We've got two guests here. We're gonna have a great conversation. Chuck Kubota joins us, senior Director of Cloud Services, GTM at Red Hat. Great to have you on the program. And Ted Stanton, global head of Sales, red Hat at IBM at aws. Welcome. >>Thanks for having us. >>How's the show going so far for you guys? >>It's a blur. Is it? Oh my gosh. >>Don't they all >>Blur? Well, yes, yes. I actually like last year a bit better. It was half the size. Yeah. And a lot easier to get around, but this is back to normal, so >>It is back to normal. Yeah. And and Ted, we're hearing north of 50,000 in-person attendees. I heard a, something I think was published. I heard the second hand over like 300,000 online attendees. This is maybe the biggest one we ever had. >>Yeah, yeah, I would agree. And frankly, it's my first time here, so I am massively impressed with the overall show, the meeting with partners, the meeting with customers, the announcements that were made, just fantastic. And >>If you remember back to two years ago, there were a lot of questions about whether in-person conferences would ever return and the volume that we used to see them. And that appears to be >>The case. I think we, I think we've answered, I think AWS has answered that for us, which I'm very pleased to see. Talk about some of those announcements. Ted. There's been so much that that's always one of the things we know and love about re men is there's slew of announcements. You were saying this morning, Paul, and then keynote, you lost, you stopped counting after I >>Lost 15, I lost count for 15. I think it was over 30 announcements this morning alone >>Where IBM and Red Hat are concern. What are some of the things that you are excited about in terms of some of the news, the innovation, and where the partnership is going? >>Well, definitely where the partnership is going, and I think even as we're speaking right now, is a keynote going on with Aruba, talking about some of the partners and the way in which we support partners and the new technologies and the new abilities for partners to take advantage of these technologies to frankly delight our customers is really what most excites me. >>Chuck, what about you? What's going on with Red Hat? You've been there a long time. Sales, everything, picking up customers, massively transforming. What are some of the things that you're seeing and that you're excited >>About? Yeah, I mean, first of all, you know, as customers have, you know, years ago discovered it's not competitively advantageous to manage their own data centers in most cases. So they would like to, you know, give that responsibility to Amazon. We're seeing them move further up the stack, right? So that would be more beyond the operating system, the application platforms like OpenShift. And now we have a managed application platform built on OpenShift called Red Out OpenShift service on AWS or Rosa. And then we're even further going up the stack with that with, we just announced this week that red out OpenShift data science is available in the AWS marketplace, runs on Rosa, helps break the land speed record to getting those data models out there that are so important to make, you know, help organizations become more, much more data driven to remain competitive themselves. >>So talk about Rosa and how it differs from previous iterations of, of OpenShift. I mean, you had, you had an online version of OpenShift several years ago. What's different about Rosa? >>Yeah, so the old OpenShift online that was several years old, right? For one thing, wasn't a joint partnership between Amazon and Red Hat. So we work together, right? Very closely on this, which is great. Also, the awesome thing about Rosa, you know, if you think about like OpenShift for, for, as a matter of fact, Amazon is the number one cloud that OpenShift runs on, right? So a lot of those customers want to take advantage of their committed spins, their EDPs, they want one bill. And so Rosa comes through the one bill comes through the marketplace, right? Which is, which is totally awesome. Not only that or financially backing OpenShift with a 99.95% financially backed sla, right? We didn't have that before either, right? >>When you say financially backed sla, >>What do you mean? That means that if we drop below 99.95% of availability, we're gonna give you some money back, right? So we're really, you know, for lack of better words, putting our money where our mouth is. Absolutely right. >>And, and some of the key reasons that we even work together to build Rosa was frankly we've had a mirror of customers and virtually every single region, every single industry been using OpenShift on AWS for years, right? And we listened to them, they wanted a more managed version of it and we worked very closely together. And what's really great about Rosa too is we built some really fantastic integrations with some of the AWS native services like API gateway, Amazon rds, private link, right? To make it very simple and easy for customers to get started. We talked a little bit about the marketplace, but it's also available just on the AWS console, right? So customers can get started in a pay as you go fashion start to use it. And if they wanna move into a more commitment, more of a set schedule of payments, they can move into a marketplace private offer. >>Chuck, talk about, how about Rosen? How is unlocking the power of technology like containers Kubernetes for customers while dialing down some of the complexity that's >>There? Yeah, I mean if you think about, you know, kind of what we did, you know, earlier on, right? If you think about like virtualization, how it dialed down the complexity of having to get something rack, get a blade rack, stack cable and cooled every time you wanted to deploy new application, right? So what we do is we, our message is this, we want developers to focus on what matters most. And that's build, deploy, and running applications. Most of our customers are not in the business of building app platforms. They're not in the business of building platforms like banks, I, you know, financials, right? Government, et cetera. Right? So what we do is we allow those developers that are, enable those developers that know Java and Node and springing and what have you, just to keep writing what they know. And then, you know, I don't wanna get too technical here, but get pushed through way and, and OpenShift takes care of the rest, builds it for them, runs it through a pipeline, a CICD pipeline, goes through all the testing and quality gates and things like that, deploys it, auto wires it up, you know, to monitoring which is what you need. >>And we have all kinds of other, you know, higher order services and an ecosystem around that. And oh, by the way, also plugging into and taking advantage of the services like rds, right? If you're gonna write an application, a tradition, a cloud native application on Amazon, you're probably going to wanna run it in Rosa and consuming one of those databases, right? Like RDS or Aurora, what have you. >>And I, and I would say it's not even just the customers. We have a variety of ecosystem partners, both of our partners leveraging it as well. We have solos built their executive management system that they go ahead and turn and sell to their customers, streamlines data and collects data from a variety of different sources. They decided, you know, it's better to run that on top of Rosa than manage OpenShift themselves. We've seen IBM restack a lot of their software, you know, to run on top of Rose, take advantage of that capabilities. So lots of partners as well as customers are taking advantage of fully managed stack of that OpenShift that that turnkey capabilities that it provides >>For, for OpenShift customers who wanna move to Rose, is that gonna be a one button migration? Is that gonna be, can they run both environments simultaneously and migrate over time? What kind of tools are you giving them? >>We have quite, we have quite a few migration tools such as conveyor, right? That's one of our projects, part of our migration application toolkit, right? And you know, with those, there's also partners like Trilio, right? Who can help move, you know, applications back 'em up. In fact, we're working on a pretty cool joint go to market with that right now. But generally speaking, the OpenShift experience that the customers that we have know and love and those who have never used OpenShift either are coming to it as well via Rosa, right? The experience is primarily the same. You don't have to really retrain your people, right? If anything, there's a reduction in operational cost. We increase developer productivity cuz we manage so much of the stack for you. We have SRE site reliability engineers that are backing the platform that proactively get ahead of anything that may go wrong. So maybe you don't even notice if something went wrong, wrong. And then also reactively fixing it if it comes to that, right? So, you know, all those kind of things that your customers are having to do on their own or hire a contractor, a consultant, what have to do Now we benefit from a managed offering in the cloud, right? In Amazon, right? And your developers still have that great experience too, like to say, you know, again, break the land speed record to prod. >>I >>Like that. And, and I would actually say migrations from OpenShift are on premise. OpenShift to Rosa maybe only represents about a third of the customers we have. About another third of the customers is frankly existing AWS customers. Maybe they're doing Kubernetes, do it, the, you know, do it themselves. We're struggling with some of the management of that. And so actually started to lean on top of using Rosa as a better platform to actually build upon their applications. And another third, we have quite a few customers that were frankly new OpenShift customers, new Red Hat customers and new AWS customers that were looking to build that next cloud native application. Lots of in the startup space that I've actually chosen to go with Rosa. >>It's funny you mention that because the largest Rosa consumer is new to OpenShift. Oh wow. Right. That's pretty, that's pretty powerful, right? It's not just for existing OpenShift customers, existing OpenShift. If you're running OpenShift, you know, on EC two, right. Self-managed, there's really no better way to run it than Rosa. You know, I think about whether this is the 10th year, 10 year anniversary of re right? Right. Yep. This is also the 10 year anniversary of OpenShift. Yeah, right. I think it one oh came out about sometime around a week, 10 years ago, right? When I came over to Red Hat in 2015. You know, if you, if you know your Kubernetes history was at July 25th, I think was when Kubernetes ga, July 25th, 2015 is when it g you have >>A good >>Memory. Well I remember those days back then, right? Those were fun, right? The, we had a, a large customer roll out on OpenShift three, which is our OpenShift RE based on Kubernetes. And where do you think they ran Amazon, right? Naturally. So, you know, as you move forward and, and, and OpenShift V four came out, the, reduces the operational complexity and becomes even more powerful through our operator framework and things like that. Now they revolved up to Rosa, right? And again, to help those customers focus on what matters most. And that's the applications, not the containers, not those underlying implementation and technical details while critically important, are not necessarily core to the business to most of our customers. >>Tremendous amount of innovation in OpenShift in a decade, >>Pardon me? >>Tremendous amount of innovation in OpenShift in the >>Last decade. Oh absolutely. And, and and tons more to come like every day. Right. I think what you're gonna see more of is, you know, as Kubernetes becomes more, more and more of the plumbing, you know, I call 'em productive abstractions on top of it, as you mentioned earlier, unlocking the power of these technologies while minimizing, even hiding the complexity of them so that you can just move fast Yeah. And safely move fast. >>I wanna be sure we get to, to marketplaces because you have been, red Hat has made, has really stepped up as commitment to the AWS marketplace. Why are you doing that now and how are, how are the marketplaces evolving as a channel for you? >>Well, cuz our customers want us to be there, right? I mean we, we, we are customer centric, customer first approach. Our customers want to buy through the marketplace. If you're an Amazon, if you're an Amazon customer, it's really easy for you to go procure software through the marketplace and have, instead of having to call up Red Hat and get on paper and write a second check, right? One stop shop one bill. Right? That is very, very attractive to our customers. Not only that, it opens up other ways to buy, you know, Ted mentioned earlier, you know, pay as you go buy the drink pricing using exactly what you need right now. Right? You know, AWS pioneered that, right? That provides that elasticity, you know, one of the core tenants at aws, AWS cloud, right? And we weren't able to get that with the traditional self-managed on Red Hat paper subscriptions. >>Talk a little bit about the go to market, what's, you talked about Ted, the kind of the three tenants of, of customer types. But talk a little bit about the gtm, the joint go to market, the joint engineering, so we get an understanding of how customers engage multiple options. >>Yeah, I mean, so if you think about go to market, you know, and the way I think of it is it's the intersection of a few areas, right? So the product and the product experience that we work together has to be so good that a customer or user, actually many start talk, talking about users now cuz it's self-service has a more than likely chance of getting their application to prod without ever talking to a person. Which is historically not what a lot of enterprise software companies are able to do, right? So that's one of those biggest things we do. We want customers to just be successful, turn it on, get going, be productive, right? At the same time we wanna to position the product in such a way that's differentiating that you can't get that experience anywhere else. And then part of that is ensuring that the education and enablement of our customers and our partners as such that they use the platform the right way to get as much value out of as possible. >>All backed by, you know, a very smart field that ensures that the customer get is making the right decision. A customer success org, this is attached to my org now that we can go on site and team with our customers to make sure that they get their first workloads up as quickly as possible, by the way, on our date, our, our dime. And then SRE and CEA backing that up with support and operational integrity to ensure that the service is always up and available so you can sleep, sleep, sleep well at night. Right? Right. One of our PMs of, of of Rosa, he says, what does he say? He says, Rosa allows organizations, enables organizations to go from 24 7 operations to nine to five innovation. Right? And that's powerful. That's how our customers remain more competitive running on Rosa with aws, >>When you're in customer conversations and you have 30 seconds, what are the key differentiators of the solution that you go boom, boom, boom, and they just go, I get it. >>Well, I mean, my 32nd elevator pitch, I think I've already said, I'll say it again. And that is OpenShift allows you to focus on your applications, build, deploy, and run applications while unlocking the power of the technologies like containers and Kubernetes and hiding or minimizing those complexities. So you can do as fast as possible. >>Mic drop Ted, question for you? Sure. Here we are at the, this is the, I leave the 11th reinvent, 10th anniversary, 11th event. You've been in the industry a long time. What is your biggest takeaway from what's been announced and discussed so far at Reinvent 22, where the AWS and and its partner ecosystem is concerned? If you had 30 seconds or if you had a bumper sticker to put on your DeLorean, what would you say? >>I would say we're continuing to innovate on behalf of our customers, but making sure we bring all of our partners and ecosystems along in that innovation. >>Yeah. I love the customer obsession on both sides there. Great work guides. Congrats on the 10th anniversary of OpenShift and so much evolution, the customer obsession is really clear for both of you guys. We appreciate your time. You're gonna have to come back now. Absolutely. Absolutely. Thank you. All right. Thank you so much for joining us. For our guests and for Paul Gillin. I'm Lisa Martin. You're watching The Cube, the leader in live enterprise and emerging tech coverage.

>> Announcer: From around the globe, it's theCUBE with coverage of KubeCon + CloudNativeCon Europe 2020 Virtual brought to you by Red Hat, the Cloud Native Computing Foundation and Ecosystem partners. >> Welcome back I'm Stu Miniman, this is theCUBE's coverage of KubeCon + CloudNativeCon Europe 2020, the virtual event. Of course, when we talk about Cloud Native we talk about Kubernetes there's a lot that's happening to modernize the infrastructure but a very important thing that we're going to talk about today is also what's happening up the stack, what sits on top of it and some of the new use cases and applications that are enabled by all of this modern environment and for that we're going to talk about artificial intelligence and machine learning or AI and ML as we tend to talk in the industry, so happy to welcome to the program. We have two first time guests joining us from Red Hat. First of all, we have Abhinav Joshi and Tushar Katarki they are both senior managers, part of the OpenShift group. Abhinav is in the product marketing and Tushar is in product management. Abhinav and Tushar thank you so much for joining us. >> Thanks a lot, Stu, we're glad to be here. >> Thanks Stu and glad to be here at KubeCon. >> All right, so Abhinav I mentioned in the intro here, modernization of the infrastructure is awesome but really it's an enabler. We know... I'm an infrastructure person the whole reason we have infrastructure is to be able to drive those applications, interact with my data and the like and of course, AI and ML are exciting a lot going on there but can also be challenging. So, Abhinav if I could start with you bring us inside your customers that you're talking to, what are the challenges, the opportunities? What are they seeing in this space? Maybe what's been holding them back from really unlocking the value that is expected? >> Yup, that's a very good question to kick off the conversation. So what we are seeing as an organization they typically face a lot of challenges when they're trying to build an AI/ML environment, right? And the first one is like a talent shortage. There is a limited amount of the AI, ML expertise in the market and especially the data scientists that are responsible for building out the machine learning and the deep learning models. So yeah, it's hard to find them and to be able to retain them and also other talents like a data engineer or app DevOps folks as well and the lack of talent can actually stall the project. And the second key challenge that we see is the lack of the readily usable data. So the businesses collect a lot of data but they must find the right data and make it ready for the data scientists to be able to build out, to be able to test and train the machine learning models. If you don't have the right kind of data to the predictions that your model is going to do in the real world is only going to be so good. So that becomes a challenge as well, to be able to find and be able to wrangle the right kind of data. And the third key challenge that we see is the lack of the rapid availability of the compute infrastructure, the data and machine learning, and the app dev tools for the various personas like a data scientist or data engineer, the software developers and so on that can also slow down the project, right? Because if all your teams are waiting on the infrastructure and the tooling of their choice to be provisioned on a recurring basis and they don't get it in a timely manner, it can stall the projects. And then the next one is the lack of collaboration. So you have all these kinds of teams that are involved in the AI project, and they have to collaborate with each other because the work one of the team does has a dependency on a different team like say for example, the data scientists are responsible for building the machine learning models and then what they have to do is they have to work with the app dev teams to make sure the models get integrated as part of the app dev processes and ultimately rolled out into the production. So if all these teams are operating in say silos and there is lack of collaboration between the teams, so this can stall the projects as well. And finally, what we see is the data scientists they typically start the machine learning modeling on their individual PCs or laptops and they don't focus on the operational aspects of the solution. So what this means is when the IT teams have to roll all this out into a production kind of deployment, so they get challenged to take all the work that has been done by the individuals and then be able to make sense out of it, be able to make sure that it can be seamlessly brought up in a production environment in a consistent way, be it on-premises, be it in the cloud or be it say at the edge. So these are some of the key challenges that we see that the organizations are facing, as they say try to take the AI projects from pilot to production. >> Well, some of those things seem like repetition of what we've had in the past. Obviously silos have been the bane of IT moving forward and of course, for many years we've been talking about that gap between developers and what's happening in the operation side. So Tushar, help us connect the dots, containers, Kubernetes, the whole DevOps movement. How is this setting us up to actually be successful for solutions like AI and ML? >> Sure Stu I mean, in fact you said it right like in the world of software, in the world of microservices, in the world of app modernization, in the world of DevOps in the past 10, 15 years, but we have seen this evolution revolution happen with containers and Kubernetes driving more DevOps behavior, driving more agile behavior so this in fact is what we are trying to say here can ease up the cable to EIML also. So the various containers, Kubernetes, DevOps and OpenShift for software development is directly applicable for AI projects to make them move agile, to get them into production, to make them more valuable to organization so that they can realize the full potential of AI. We already touched upon a few personas so it's useful to think about who the users are, who the personas are. Abhinav I talked about data scientists these are the people who obviously do the machine learning itself, do the modeling. Then there are data engineers who do the plumbing who provide the essential data. Data is so essential to machine learning and deep learning and so there are data engineers that are app developers who in some ways will then use the output of what the data scientists have produced in terms of models and then incorporate them into services and of course, none of these things are purely cast in stone there's a lot of overlap you could find that data scientists are app developers as well, you'll see some of app developers being data scientist later data engineer. So it's a continuum rather than strict boundaries, but regardless what all of these personas groups of people need or experts need is self service to that preferred tools and compute and storage resources to be productive and then let's not forget the IT, engineering and operations teams that need to make all this happen in an easy, reliable, available manner and something that is really safe and secure. So containers help you, they help you quickly and easily deploy a broad set of machine learning tools, data tools across the cloud, the hybrid cloud from data center to public cloud to the edge in a very consistent way. Teams can therefore alternatively modify, change a shared container images, machine learning models with (indistinct) and track changes. And this could be applicable to both containers as well as to the data by the way and be transparent and transparency helps in collaboration but also it could help with the regulatory reasons later on in the process. And then with containers because of the inherent processes solution, resource control and protection from threat they can also be very secure. Now, Kubernetes takes it to the next level first of all, it forms a cluster of all your compute and data resources, and it helps you to run your containerized tools and whatever you develop on them in a consistent way with access to these shared compute and centralized compute and storage and networking resources from the data center, the edge or the public cloud. They provide things like resource management, workload scheduling, multi-tendency controls so that you can be a proper neighbors if you will, and quota enforcement right? Now that's Kubernetes now if you want to up level it further if you want to enhance what Kubernetes offers then you go into how do you write applications? How do you actually make those models into services? And that's where... and how do you lifecycle them? And that's sort of the power of Helm and for the more Kubernetes operators really comes into the picture and while Helm helps in installing some of this for a complete life cycle experience. A kubernetes operator is the way to go and they simplify the acceleration and deployment and life cycle management from end-to-end of your entire AI, ML tool chain. So all in all organizations therefore you'll see that they need to dial up and define models rapidly just like applications that's how they get ready out of it quickly. There is a lack of collaboration across teams as Abhinav pointed out earlier, as you noticed that has happened still in the world of software also. So we're talking about how do you bring those best practices here to AI, ML. DevOps approaches for machine learning operations or many analysts and others have started calling as MLOps. So how do you kind of bring DevOps to machine learning, and fosters better collaboration between teams, application developers and IT operations and create this feedback loop so that the time to production and the ability to take more machine learning into production and ML-powered applications into production increase is significant. So that's kind of the, where I wanted shine the light on what you were referring to earlier, Stu. >> All right, Abhinav of course one of the good things about OpenShift is you have quite a lot of customers that have deployed the solution over the years, bring us inside some of your customers what are they doing for AI, ML and help us understand really what differentiates OpenShift in the marketplace for this solution set. >> Yeah, absolutely that's a very good question as well and we're seeing a lot of traction in terms of all kinds of industries, right? Be it the financial services like healthcare, automotive, insurance, oil and gas, manufacturing and so on. For a wide variety of use cases and what we are seeing is at the end of the day like all these deployments are focused on helping improve the customer experience, be able to automate the business processes and then be able to help them increase the revenue, serve their customers better, and also be able to save costs. If you go to openshift.com/ai-ml it's got like a lot of customer stories in there but today I will not touch on three of the customers we have in terms of the different industries. The first one is like Royal Bank of Canada. So they are a top global financial institution based out of Canada and they have more than 17 million clients globally. So they recently announced that they build out an AI-powered private cloud platform that was based on OpenShift as well as the NVIDIA DGX AI compute system and this whole solution is actually helping them to transform the customer banking experience by being able to deliver an AI-powered intelligent apps and also at the same time being able to improve the operational efficiency of their organization. And now with this kind of a solution, what they're able to do is they're able to run thousands of simulations and be able to analyze millions of data points in a fraction of time as compared to the solution that they had before. Yeah, so like a lot of great work going on there but now the next one is the ETCA healthcare. So like ETCA is one of the leading healthcare providers in the country and they're based out of the Nashville, Tennessee. And they have more than 184 hospitals as well as more than 2,000 sites of care in the U.S. as well as in the UK. So what they did was they developed a very innovative machine learning power data platform on top of our OpenShift to help save lives. The first use case was to help with the early detection of sepsis like it's a life-threatening condition and then more recently they've been able to use OpenShift in the same kind of stack to be able to roll out the new applications that are powered by machine learning and deep learning let say to help them fight COVID-19. And recently they did a webinar as well that had all the details on the challenges they had like how did they go about it? Like the people, process and technology and then what the outcomes are. And we are proud to be a partner in the solution to help with such a noble cause. And the third example I want to share here is the BMW group and our partner DXC Technology what they've done is they've actually developed a very high performing data-driven data platform, a development platform based on OpenShift to be able to analyze the massive amount of data from the test fleet, the data and the speed of the say to help speed up the autonomous driving initiatives. And what they've also done is they've redesigned the connected drive capability that they have on top of OpenShift that's actually helping them provide various use cases to help improve the customer experience. With the customers and all of the customers are able to leverage a lot of different value-add services directly from within the car, their own cars. And then like last year at the Red Hat Summit they had a keynote as well and then this year at Summit, they were one of the Innovation Award winners. And we have a lot more stories but these are the three that I thought are actually compelling that I should talk about here on theCUBE. >> Yeah Abhinav just a quick follow up for you. One of the things of course we're looking at in 2020 is how has the COVID-19 pandemic, people working from home how has that impacted projects? I have to think that AI and ML are one of those projects that take a little bit longer to deploy, is it something that you see are they accelerating it? Are they putting on pause or are new project kicking off? Anything you can share from customers you're hearing right now as to the impact that they're seeing this year? >> Yeah what we are seeing is that the customers are now even more keen to be able to roll out the digital (indistinct) but we see a lot of customers are now on the accelerated timeline to be able to say complete the AI, ML project. So yeah, it's picking up a lot of momentum and we talk to a lot of analyst as well and they are reporting the same thing as well. But there is the interest that is actually like ramping up on the AI, ML projects like across their customer base. So yeah it's the right time to be looking at the innovation services that it can help improve the customer experience in the new virtual world that we live in now about COVID-19. >> All right, Tushar you mentioned that there's a few projects involved and of course we know at this conference there's a very large ecosystem. Red Hat is a strong contributor to many, many open source projects. Give us a little bit of a view as to in the AI, ML space who's involved, which pieces are important and how Red Hat looks at this entire ecosystem? >> Thank you, Stu so as you know technology partnerships and the power of open is really what is driving the technology world these days in any ways and particularly in the AI ecosystem. And that is mainly because one of the machine learning is in a bootstrap in the past 10 years or so and a lot of that emerging technology to take advantage of the emerging data as well as compute power has been built on the kind of the Linux ecosystem with openness and languages like popular languages like Python, et cetera. And so what you... and of course tons of technology based in Java but the point really here is that the ecosystem plays a big role and open plays a big role and that's kind of Red Hat's best cup of tea, if you will. And that really has plays a leadership role in the open ecosystem so if we take your question and kind of put it into two parts, what is the... what we are doing in the community and then what we are doing in terms of partnerships themselves, commercial partnerships, technology partnerships we'll take it one step at a time. In terms of the community itself, if you step back to the three years, we worked with other vendors and users, including Google and NVIDIA and H2O and other Seldon, et cetera, and both startups and big companies to develop this Kubeflow ecosystem. The Kubeflow is upstream community that is focused on developing MLOps as we talked about earlier end-to-end machine learning on top of Kubernetes. So Kubeflow right now is in 1.0 it happened a few months ago now it's actually at 1.1 you'll see that coupon here and then so that's the Kubeflow community in addition to that we are augmenting that with the Open Data Hub community which is something that extends the capabilities of the Kubeflow community to also add some of the data pipelining stuff and some of the data stuff that I talked about and forms a reference architecture on how to run some of this on top of OpenShift. So the Open Data Hub community also has a great way of including partners from a technology partnership perspective and then tie that with something that I mentioned earlier, which is the idea of Kubernetes operators. Now, if you take a step back as I mentioned earlier, Kubernetes operators help manage the life cycle of the entire application or containerized application including not only the configuration on day one but also day two activities like update and backups, restore et cetera whatever the application needs. Afford proper functioning that a "operator" needs for it to make sure so anyways, the Kubernetes operators ecosystem is also flourishing and we haven't faced that with the OperatorHub.io which is a community marketplace if you will, I don't call it marketplace a community hub because it's just comprised of community operators. So the Open Data Hub actually can take community operators and can show you how to run that on top of OpenShift and manage the life cycle. Now that's the reference architecture. Now, the other aspect of it really is as I mentioned earlier is the commercial aspect of it. It is from a customer point of view, how do I get certified, supported software? And to that extent, what we have is at the top of the... from a user experience point of view, we have certified operators and certified applications from the AI, ML, ISV community in the Red Hat marketplace. And from the Red Hat marketplace is where it becomes easy for end users to easily deploy these ISVs and manage the complete life cycle as I said. Some of the examples of these kinds of ISVs include startups like H2O although H2O is kind of well known in certain sectors PerceptiLabs, Cnvrg, Seldon, Starburst et cetera and then on the other side, we do have other big giants also in this which includes partnerships with NVIDIA, Cloudera et cetera that we have announced, including our also SaaS I got to mention. So anyways these provide... create that rich ecosystem for data scientists to take advantage of. A TEDx Summit back in April, we along with Cloudera, SaaS Anaconda showcased a live demo that shows all these things to working together on top of OpenShift with this operator kind of idea that I talked about. So I welcome people to go and take a look the openshift.com/ai-ml that Abhinav already referenced should have a link to that it take a simple Google search might download if you need some of that, but anyways and the other part of it is really our work with the hardware OEMs right? And so obviously NVIDIA GPUs is obviously hardware, and that accelerations is really important in this world but we are also working with other OEM partners like HP and Dell to produce this accelerated AI platform that turnkey solutions to run your data-- to create this open AI platform for "private cloud" or the data center. The other thing obviously is IBM, IBM Cloud Pak for Data is based on OpenShift that has been around for some time and is seeing very good traction, if you think about a very turnkey solution, IBM Cloud Pak is definitely kind of well ahead in that and then finally Red Hat is about driving innovation in the open-source community. So, as I said earlier, we are doing the Open Data Hub which that reference architecture that showcases a combination of upstream open source projects and all these ISV ecosystems coming together. So I welcome you to take a look at that at opendatahub.io So I think that would be kind of the some total of how we are not only doing open and community building but also doing certifications and providing to our customers that assurance that they can run these tools in production with the help of a rich certified ecosystem. >> And customer is always key to us so that's the other thing that the goal here is to provide our customers with a choice, right? They can go with open source or they can go with a commercial solution as well. So you want to make sure that they get the best in cloud experience on top of our OpenShift and our broader portfolio as well. >> All right great, great note to end on, Abhinav thank you so much and Tushar great to see the maturation in this space, such an important use case. Really appreciate you sharing this with theCUBE and Kubecon community. >> Thank you, Stu. >> Thank you, Stu. >> Okay thank you and thanks a lot and have a great rest of the show. Thanks everyone, stay safe. >> Thanks you and stay with us for a lot more coverage from KubeCon + CloudNativeCon Europe 2020, the virtual edition I'm Stu Miniman and thank you as always for watching theCUBE. (soft upbeat music plays)

>>Live from San Diego, California It's the Q covering Koopa and Cloud Native Cot brought to you by Red Cloud, Native Computing Pounding and its ecosystem March. >>Welcome back to the Cube here at Q. Khan Club native Khan, 2019 in San Diego, California Instrumental in my co host is Jon Cryer and first of all, happy to welcome back to the program. Diane Mueller, who is the technical of the tech lead of cloud native technology. I'm sorry. I'm getting the wrong That's director of community development Red Hat, because renew. Goodbye is the technical lead of cognitive technologies at in video game to the end of day one. I've got three days. I gotta make sure >>you get a little more Red Bull in the conversation. >>All right, well, there's definitely a lot of energy. Most people we don't even need Red Bull here because we're a day one. But Diane, we're going to start a day zero. So, you know, you know, you've got a good group of community of geeks when they're like Oh, yeah, let me fly in a day early and do like 1/2 day or full day of deep dives. There So the Red Hat team decided to bring everybody on a boat, I guess. >>Yeah. So, um, open ships Commons gathering for this coup con we hosted at on the inspiration Hornblower. We had about 560 people on a boat. I promised them that it wouldn't leave the dock, but we deal still have a little bit of that weight going on every time one of the big military boats came by. And so people were like a little, you know, by the end of the day, but from 8 a.m. in the morning till 8 p.m. In the evening, we just gathered had some amazing deep dives. There was unbelievable conversations onstage offstage on we had, ah, wonderful conversation with some of the new Dev ops folks that have just come on board. That's a metaphor for navigation and Coop gone. And and for events, you know, Andrew Cliche for John Willis, the inevitable Crispin Ella, who runs Open Innovation Labs, and J Bloom have all just formed the global Transformation Office. I love that title on dhe. They're gonna be helping Thio preach the gospel of Cultural Dev ops and agile transformation from a red hat office From now going on, there was a wonderful conversation. I felt privileged to actually get to moderate it and then just amazing people coming forward and sharing their stories. It was a great session. Steve Dake, who's with IBM doing all the SDO stuff? Did you know I've never seen SDO done so well, Deployment explains so well and all of the contents gonna be recorded and up on Aaron. We streamed it live on Facebook. But I'm still, like reeling from the amount of information overload. And I think that's the nice thing about doing a day zero event is that it's a smaller group of people. So we had 600 people register, but I think was 560 something. People show up and we got that facial recognition so that now when they're traveling through the hallways here with 12,000 other people, that go Oh, you were in the room. I met you there. And that's really the whole purpose for comments. Events? >>Yeah, I tell you, this is definitely one of those shows that it doesn't take long where I say, Hey, my brain is full. Can I go home. Now. You know I love your first impressions of Q Khan. Did you get to go to the day zero event And, uh, what sort of things have you been seeing? So >>I've been mostly I went to the lightning talks, which were amazing. Anything? Definitely. There. A number of shout outs to the GPU one, of course. Uh, friend in video. But I definitely enjoyed, for example, of the amazing D. M s one, the one about operators. And generally all of them were very high quality. >>Is this your first Q? Khan, >>I've been there. I've been a year. This is my third con. I've been accused in Europe in the past. Send you an >>old hat old hand at this. Well, before we get into the operator framework and I wanna love to dig into this, I just wanted to ask one more thought. Thought about open shift, Commons, The Commons in general, the relationship between open shift, the the offering. And then Okay, the comments and okay, D and then maybe the announcement about about Okay. Dee da da i o >>s. Oh, a couple of things happened yesterday. Yesterday we dropped. Okay, D for the Alfa release. So anyone who wants to test that out and try it out it's an all operators based a deployment of open shift, which is what open ship for is. It's all a slightly new architectural deployment methodology based on the operator framework, and we've been working very diligently. Thio populate operator hub dot io, which is where all of the upstream projects that have operators like the one that Reynolds has created for in the videos GP use are being hosted so that anyone could deploy them, whether on open shift or any kubernetes so that that dropped. And yesterday we dropped um, and announced Open Sourcing Quay as project quay dot io. So there's a lot of Io is going on here, but project dia dot io is, um, it's a fulfillment, really, of a commitment by Red Hat that whenever we do an acquisition and the poor folks have been their acquired by Cora West's and Cora Weston acquired by Red Hat in an IBM there. And so in the interim, they've been diligently working away to make the code available as open source. And that hit last week and, um, to some really interesting and users that are coming up and now looking forward to having them to contribute to that project as well. But I think the operator framework really has been a big thing that we've been really hearing, getting a lot of uptake on. It's been the new pattern for deploying applications or service is on getting things beyond just a basic install of a service on open shift or any kubernetes. And that's really where one of the exciting things yesterday on we were talking, you know, and I were talking about this earlier was that Exxon Mobil sent a data scientist to the open ship Commons, Audrey Resnick, who gave this amazing presentation about Jupiter Hub, deeper notebooks, deploying them and how like open shift and the advent of operators for things like GP use is really helping them enable data scientists to do their work. Because a lot of the stuff that data signs it's do is almost disposable. They'll run an experiment. Maybe they don't get the result they want, and then it just goes away, which is perfect for a kubernetes workload. But there are other things you need, like a Jeep use and work that video has been doing to enable that on open shift has been just really very helpful. And it was It was a great talk, but we were talking about it from the first day. Signs don't want to know anything about what's under the hood. They just want to run their experiments. So, >>you know, let's like to understand how you got involved in the creation of the operator. >>So generally, if we take a step back and look a bit at what we're trying to do is with a I am l and generally like EJ infrastructure and five G. We're seeing a lot of people. They're trying to build and run applications. Whether it's in data Center at the and we're trying to do here with this operator is to bring GPS to enterprise communities. And this is what we're working with. Red Hat. And this is where, for example, things like the op Agrestic A helps us a lot. So what we've built is this video Gee, few operator that space on the upper air sdk where it wants us to multiple phases to in the first space, for example, install all the components that a data scientist were generally a GPU cluster of might want to need. Whether it's the NVIDIA driver, the container runtime, the community's device again feast do is as you go on and build an infrastructure. You want to be able to have the automation that is here and, more importantly, the update part. So being able to update your different components, face three is generally being able to have a life cycle. So as you manage multiple machines, these are going to get into different states. Some of them are gonna fail, being able to get from these bad states to good states. How do you recover from them? It's super helpful. And then last one is monitoring, which is being able to actually given sites dr users. So the upper here is decay has helped us a lot here, just laying out these different state slips. And in a way, it's done the same thing as what we're trying to do for our customers. The different data scientists, which is basically get out of our way and allow us to focus on core business value. So the operator, who basically takes care of things that are pretty cool as an engineer I lost due to your election. But it doesn't really help me to focus on like my core business value. How do I do with the updates, >>you know? Can I step back one second, maybe go up a level? The problem here is that each physical machine has only ah limited number of NVIDIA. GPU is there and you've got a bunch of containers that maybe spawning on different machines. And so they have to figure out, Do I have a GPU? Can I grab one? And if I'm using it, I assume I have to reserve it and other people can't use and then I have to give it up. Is that is that the problem we're solving here? So this is >>a problem that we've worked with communities community so that like the whole resource management, it's something that is integrated almost first class, citizen in communities, being able to advertise the number of deep, use their your cluster and used and then being able to actually run or schedule these containers. The interesting components that were also recently added are, for example, the monitoring being able to see that a specific Jupiter notebook is using this much of GP utilization. So these air supercool like features that have been coming in the past two years in communities and which red hat has been super helpful, at least in these discussions pushing these different features forward so that we see better enterprise support. Yeah, >>I think the thing with with operators and the operator lifecycle management part of it is really trying to get to Day two. So lots of different methodologies, whether it's danceable or python or job or or UH, that's helm or anything else that can get you an insult of a service or an application or something. And in Stan, she ate it. But and the operator and we support all of that with SD case to help people. But what we're trying to do is bridge the to this day to stuff So Thea, you know, to get people to auto pilot, you know, and there's a whole capacity maturity model that if you go to operator hab dot io, you can see different operators are a different stages of the game. So it's been it's been interesting to work with people to see Theo ah ha moment when they realize Oh, I could do this and then I can walk away. And then if that pod that cluster dies, it'll just you know, I love the word automatically, but they, you know, it's really the goal is to help alleviate the hands on part of Day two and get more automation into the service's and applications we deploy >>right and when they when they this is created. Of course it works well with open shift, but it also works for any kubernetes >>correct operator. HAB Daddio. Everything in there runs on any kubernetes, and that's really the goal is to be ableto take stuff in a hybrid cloud model. You want to be able to run it anywhere you want, so we want people to be unable to do it anywhere. >>So if this really should be an enabler for everything that it's Vinny has been doing to be fully cloud native, Yes, >>I think completely arable here is this is a new attack. Of course, this is a bit there's a lot of complexity, and this is where we're working towards is reducing the complexity and making true that people there. Dan did that a scientist air machine learning engineers are able to focus on their core business. >>You watch all of the different service is in the different things that the data scientists are using. They don't I really want to know what's under under the hood. They would like to just open up a Jupiter Hub notebook, have everything there. They need, train their models, have them run. And then after they're done, they're done and it goes away. And hopefully they remember to turn off the Jeep, use in the woods or wherever it is, and they don't keep getting billed for it. But that's the real beauty of it is that they don't have to worry so much anymore about that. And we've got a whole nice life cycle with source to image or us to I. And they could just quickly build on deploy its been, you know, it's near and dear to my heart, the machine learning the eyesight of stuff. It is one of the more interesting, you know, it's the catchy thing, but the work was, but people are really doing it today, and it's been we had 23 weeks ago in San Francisco, we had a whole open ship comments gathering just on a I and ML and you know, it was amazing to hear. I think that's the most redeeming thing or most rewarding thing rather for people who are working on Kubernetes is to have the folks who are doing workloads come and say, Wow, you know, this is what we're doing because we don't get to see that all the time. And it was pretty amazing. And it's been, you know, makes it all worthwhile. So >>Diane Renaud, thank you so much for the update. Congratulations on the launch of the operators and look forward to hearing more in the future. >>All right >>to >>be here >>for John Troy runs to minimum. More coverage here from Q. Khan Club native Khan, 2019. Thanks for watching. Thank you.

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

>> Announcer: Live, from Boston, Massachusets, it's theCUBE covering Red Hat Summit, 2019. Brought to you by Red Hat. >> Well, welcome back here in Boston. We're at the BCEC as we are starting to wrap up our coverage here of day two of the Red Hat Summit, 2019. Along with Stu Miniman, I'm John Walls, and we're now joined by Ashesh Badani, who is the senior vice president of Cloud Platforms at Red Hat. Been a big day for you, hasn't it Mr. Badani? >> It sure has, thanks for having me back on! >> You bet! All right, so OpenShift 4, we saw the unveiling, your baby gets introduced to the world. What's the reaction been between this morning and this afternoon in terms of people, what they're asking you about, what they're most curious about, and maybe what their best reaction is. >> Yeah, so it's not necessarily a surprise for the folks who have been following OpenShift closely, we put the beta out for a little while, so that's the good news, but let me roll back just a little. >> John: Sure >> I think another part of the news that was really important for us is our announcement of a milestone that we crossed, which is a thousand customers, right? And it was at this very summit and theCUBE definitely knows this well, right, because they've been talking for a while. At this very Summit in 2015, four years ago, that we launched OpenShift Version 3. Right and so, you know you fast forward four years, right, and now the diversity of cases that we see, you know, spanning, established apps, cloud native apps, we heard Exxon talking about AIML data signs that they're putting on the platform, in a variety of different industries, is amazing. And I think the way OpenShift 4 has come along for us, is us having the opportunity to learn what have all these customers been doing well, and what else do we need to do on the platform to make that experience a better one. How do we reimagine enterprise kubernetes, to take it to the next level. And I think that's what we're introducing to the industry. >> Ashesh I think back four years ago, kubernetes was not something that was on the tip of the tongues of most people here. Congratulations on 1,000. >> Thank you. >> I hear what, 100, 150, new customers every quarter is the current rate there, but what I've really enjoyed, talked to a CIO and they're like okay, we're talking about digital transformation, we're talking about how we're modernizing all of our environments, and OpenShift is the platform that we do it. So, talk a little bit, from a customer's standpoint, the speeds, the feeds, the technical pieces, but that outcome, what is it an enabler of for your customers? >> Yeah, so excellent points Stu, we've seen whole sale complete digital transformations underway with our customers. So whether it's Deutsche Bank, who came and talked about running thousands of containers now, moving a whole bunch of workload onto the platform, which is incredible to see. Whether it's a customer like Volkswagen, who talking yesterday, if you caught that, about building an autonomous, self-driving, sets of technologies on the platform. What we're seeing is not just what we thought we would only see in the beginning which is one built, cloud native apps, and digital apps, and so on. Or, more nice existing apps, and bring them on the platform. But also, technologies that are making a fundamental difference, and I'll call one out. So I'm a judge for The Innovation Awards, we do this every year, I have been for many years, I love it, it's one of my favorite parts of the show. This year, we had one entry, which is one of the winners, which is HCA, which is a healthcare provider, talking about how they've been using the OpenShift platform as a means to make a fundamental difference in patients' lives. And when I say fundamental difference, actually saving lives. And you'll hear more about their story, but what they've done, is be able to say, look how can we detect early warning signals, faster than we have been, take some AI technology, and correlate against that, and see how we can reduce sepsis within patients. It's a very personal story for me, my mother died of sepsis. And the fact that they've been able to do this, and I think they're reporting they've already saved dozens of lives based on this. That's when you know, the things that you're doing are making a real difference, making a real transformation, not just in an actual customers' lives, but in users and people around the world. >> You were saying earlier too, Ashesh, about looking at what customers are doing and then trying to improve upon that experience, and give them a more effective experience, whatever the right adjective might be, in terms of what you're doing with 4. If you had to look at it, and say okay, these are the two or three pillars of this where I think we've made the biggest improvement or the biggest change, what would those be? >> Yes, so, one is to look at the world as it is in some sense, which is what a customer's doing. Customers weren't deployed to hybrid cloud, right? They want choice, they want independence with regard to which environments are rented on, whether it's physical, virtual, private, or any public cloud. Customers want one platform, to say I want to run these next generation, cloud native, market service based applications, along with my established stateful applications. Customers want a platform for innovation, right? So for example, we have customers that say, look, I really need a modern platform because I want to recruit the next generation of developers from colleges, if I don't give them the ability to play with Go, or Python, or new databases, they're gonna go to some Silicon Valley company, and I'm going to deplete my pool of talent that I need to compete, right? 'Cause digital transformation is about taking existing companies, and making them digitally enabled. Going forward, what we're also seeing is the ability for us to say well maybe the experience we've given existing customers can be improved. How do we for example, give them a platform, that's more autonomous in nature, more self-driving in nature, that can heal itself, based on for example, there's a critical update that's required that we can send over the air to them. How can we bring greater automation into the platform? It's all of those ideas that we've got based on how customers are using it today, is what we're bringing to bear, going forward. >> Ashesh, one of the errors we have trying to help customers parse through the language is, everybody's talking about platforms, if you look at the public clouds, everybody's all in on kubernetes, a few weeks ago, we were at the Google Cloud event, talked to Red Hat there, there's Anthos, there's OpenShift, look at Azure, we Satya Nadella up on stage, and you're like, okay they've got their own kubernetes platform, but I've got OpenShift fully integrated there. >> Ashesh: Yeah. >> Can you help is kinda understand how those fit together because it's an interesting and changing dynamic. >> Well it's a very Silicon Valley buzzword, right? Everyone wants a platform, everyone wants to build a platform, Facebook's a platform, Uber's a platform, Airbnb is, everything's seeming a platform, right? What I really want to focus on more is in regard to, we want to be able to give folks literally an abstraction level, an ability for companies to say I want to embrace digital transformation. Before we get there, someone's like what's digital transformation, I don't even understand what that means anymore. My simple definition is basically flipping the table. Typically companies spend 80% on maintenance, 20% innovation, how do we flip that? So they're spending 80% innovation, 20% maintenance. So if we're still thinking in those terms, let me give you a way to develop those applications, spend more time and energy on innovation, and then allow for you to take advantage of what I'll call a pool of resources. Compute, network, and storage. Across the environment that you have in place. Some of which you might own, some of which some third parties might provide for you, and some of which you get from public cloud. And take advantage of innovation that's being done outside. Innovative services that come from either public cloud providers, or ISPs, or separate providers, and then be able to do that innovated rapid fashion, you know, develop, deploy, iterate quickly. So to me that is really fundamentally what we're trying to provide customers, and it takes different forms, internal packaging. >> Maybe you can explain to me, the Azure OpenStack seems different than some of the other partnerships. Two years ago, when we were sitting in this building, we talked to you about AWS with OpenShift in that partnership, so what's differentiated and special about the Azure OpenStack integration. >> Yeah, so the Azure partnership, it's a good question because we've now taken our partnering with the public cloud providers to the next level, if you will. With Azure there's a few things in play, first it's a jointly offered managed service from Red Hat and Microsoft, where we're both supporting it together. So in the case of OpenShift and AWS, that's you know OpenShift directly to the ring of service, in this case, it's right out of Microsoft, working close together to make that happen. It's a native service to Azure, so if you saw in the keynote, you could use a command line to call OpenShift directly integrate into the Azure command line. It's available within the interface of Microsoft-Azure. So it feels like a native service, you can take advantages of other Azure services, and bring those to bear, so obviously increases developer experience from that perspective. We also inherit all the compliances, certifications, that Microsoft-Azure has, as well, for that service, as well as all the availability requirements that they put out there, so it's much more closely integrated together, much better developer experience, native to Azure, and then the ability for the Microsoft sales team to go out and sell it to their customers in conjunction. >> You talk a lot about different partnerships, and bringing this collaborative, open-mindset to each and every relationship, how hard is that to do? Because you have your of way of doing things and it's worked very well, and yet, you go out and you have these new partnerships or extensions of partnerships, and not everybody with whom you work does things the same way, and so, everybody's gotta be malleable to a certain extent, but just in terms of being that flexible all the time, what does that do for you? >> So, we take that for granted sometimes, the way we work. And I don't mean to say that to be boastful, or arrogant, in any fashion. I had an interview earlier today, and the reporter said why don't you put on your page, that you're 100% open source? And I said we never put that on our page because that's just how we work, we assume that, we assume everyone knows that about us, and we're going forward. And he says, well, I don't know, perhaps there's others that don't know. And he's right. The world's changing, we're expanding our opportunities in front of folks. In the same way we've only and always known, we used to collaborate with others in the community, before we fully embraced OpenStack, there were certain projects that Red Hat was investing in that were Red Hat driven, and we say maybe there wasn't as much community around it, we're gonna go down and embrace and fully parse an OpenStack community. Same's the case, for example, in kubernetes too. It's not necessarily a project that we created on our own, in conjunction with Google, and many others in the community. And so that's something that's part of our DNA, I'm not sure we're doing anything different, in engaging with communities, just how we work. >> So, Ashesh, I know your team's busy doing a lot of things. We've been hearing about what sessions are overflowing, down in the expo floor, so why don't you give us some visibility. But there was one specific one I wondered if you could start with. >> Ashesh: Sure. >> So down on the expo floor, it's a containerized environment and it has something to do with puppies, and therefor how does that connect with OpenShift 4 if we can start there. >> That's a tough one, you're gonna have to go and ask the puppies how to make a difference in the world. (laughing) >> John: So we go from kubernetes to canines, (laughing) that's what we're doing here. >> I do believe they're comfort dogs, but there was coding and some of the other stuff, so give us a little bit of the walk around, the expo flow, the breakouts and the like, in some of the hot areas, that your team's working on. >> Fair enough, fair enough. Maybe not puppies, but maybe we're trying to herd cats, close enough, right? >> John: Safer terrain. >> The amount of interest, the number of sessions, with OpenShift, or container based technologies, cloud based technologies, it's tremendous to see that. So regardless if whether you see the breakouts that are in place, the customer sessions, I think we've got over 100 customers, I think. Who are presenting on all aspects of their journey. So to me, that's remarkable. Lots of interest in our road map going forward, which is great to see, standing room only for OpenShift 4 and where we're taking that. Other technology that's interesting, the work, for example, we're doing in serverless. We announced an OpenSource collaboration with Mircrosoft, something called KEDA, the Kubernetes eventually. Our scaling project, so interesting how customers can kind of engage around that as well. And then the partner ecosystem, you can walk around and see just a plethora of ISVs, we're all looking to build operators, or have operators and are certifying operators within our ecosystem. And then it's ways for us to expose that to our joint customers. >> We're gonna cut you loose, and let you go, the floor's gonna be open for a few minutes, those puppies are just down behind Stu, we'll let you go check that out. >> Alright, thanks, I hear you can adopt them if you want to, as well. >> Before we let you go see the comfort dogs, 1,000 customers, where do you see, when we come back a year from now, where you are, where you wanna see it go, show us a little bit looking forward. >> So there's been some news around Red Hat that has probably happened over the last few months, the people are hearing this, I look at that as a great opportunity for us to expand our reach into markets, both in terms of industries perhaps we haven't necessarily gone into, that other companies have been. Perhaps we say it's manufacturing, perhaps this is the opportunity for us to cross the chasm, have a lot more trained consultants who can help get more customers on the journey, so I fully expect our reach increasing over a period time. And then you'll see, if you will, iterations of OpenShift 4 and the progress we've made against that, and hopefully many more success stories on the stage. >> Alright, looking forward to catching up next year, if not sooner. >> Ashesh: Okay, excellent. >> John: And congratulations on today, and best of luck down the road. >> Thanks again for having me. >> And good to see you! >> Ashesh: Yeah, likewise! >> Back with more on theCube, you are watching our coverage live, here from Red Hat Summit, 2019, in Boston, Massachusetts. (upbeat techno music)

>> Live from Barcelona, Spain it's theCUBE. Covering Cisco Live Europe. Brought to you by Cisco and its ecosystem partners. >> Welcome back to Cisco Live Barcelona, this is day two of theCUBE, the leader in live tech coverage. We go out to the events, we extract the signal from the noise. I'm Dave Vellante, my co-host Stu Miniman. Ben Nye is here, the CEO of Boston-based Turbonomic . Great to see you again, Ben. Thanks for coming on. >> Thanks for having me, Dave, appreciate it. >> So, what a show for you guys. Everything is multi-cloud, I mean that's your sweet spot. You saw the keynotes yesterday, you've got to love the messaging here. It's really a tail wind for you guys. >> The fit and the strategic rationale, it makes you feel good about a partnership we established a year and a half ago when it was still nascent, right? They were just starting the change to becoming a software company, to becoming a multi-cloud vendor, not making a decision at the time not to have a cloud of their own. And boy, does it feel good now. But, boy it's been interesting to watch the changes in organization, people, all the different elements of this monster company, $200 billion public market value company going through this change in the public markets. >> Well, and you guys have really executed well. Obviously, you did some nice raises, you've got that velocity marketing thing down, and you're scrappy. And now you've got some resources behind you, and you've also got some partnerships that are starting to bear some fruit. So, let's get into the Cisco partnership specifically. What's that like, what's it all about? Give us some details there. >> So, Cisco sells our product under their name. It's called Cisco Workload Optimization Manager, the acronym is CWON. But, our thesis, and I think what they buy into enormously is that as we've decomposed the infrastructure and decomposed the applications, right? Think about it, we used to have monolithic applications all the way down now to VMs, and soon microservices, right? Containers and pods. You're going to need to think about how to resource those things at a scale that humans can't possibly manage. So the workload, the little humble workload becomes the centerpiece of everything. And Workload Optimization Manager is that. It's an AI Op's ability to assure the performance, manage the compliance policies, and make it cost effective all the time. And those are trade offs, so you can't do it once. As demand changes, you've got to be able to make those trade offs ongoing, and that's the uniqueness. So, the partnership was really embracing that concept. And what's fun is you can see how it's expanded with multi-cloud manager and the move to containers. Just that many more zeros when you think about the number of workloads, and the number of containers. >> Yep. Ben, I've loved watching this discussion of workloads and applications, 'cause I've worked with Cisco most of my career. But, you know, I spent a decade on the storage side looking at the network people. And it was just, oh well, the applications to the data is just bits that run over the pipe. And therefore, Cisco didn't really necessarily care that much. It was just, I want more traffic, yes. But maybe they do some things to optimize a little bit, but Workload Optimized Management seems a very new thing for Cisco to be able to embrace and understand and fits into that whole software strategy. Maybe give us a little bit about how you've seen the maturation and change, about how Cisco has data in the center of their keynote yesterday. >> Right. >> Where it was, wait, this is the networking company Cisco. And ports and gear and massive million dollar purchases that you roll out and get certified on as opposed to kind of the new software world. >> So, I think if you look at it, data without logic is data. Right? It's when you put the two together, and that's what a workload is, that you build all the way up. If you really say "Where did they get it?" They were always great at moving the data to service the logic in the application. Buying App D I think was a critical and decisive move to really put them at the top of the stack. Anchor the application, and you can then make sure everything else is brought along with it. So, App D gave them both the ability to look at the depology of the application, the response time of the application. It also gave them this thing called Business IQ, which is, the application runs your business, right? How do I take the data in the organization throughout, make sure I'm servicing it right, but also making sure that the application is running at all times well. And applications really, are just an aggregation of workloads. And so it goes back into the application, the workload, and then the infrastructure which shares it all. >> Ben, you talked about kind of what it is, the Workload Optimization Manager. What's the secret sauce behind it? Can you talk a little bit about the engineering and how it works. >> How C1 works? >> Yes. >> Yeah, I call it The three As. There's the Approach, then there's the Abstraction, and then there's the Analytics. The first one is the approach. Everything we're doing is about putting demand in charge of supply. So, we literally own the patent on using the principles of economics to manage IT. In other words, what's the best resource allocator we know? Markets. Let the workloads pick the resources on which they need to run, and do it in that way as opposed to us trying to us trying to service some ephemeral demand when we're actually managing supply. The way it works is you have to have an abstraction. And that means that I can't have every single vendor's product be different. So, to a workload, all the flavors of storage, it just looks like IOPs and DIS, so they can trade them. An abstraction we all use in everyday life? Currency, right? That's how markets work, we have to have a common currency. And then the last one is the Analytics. If you let the workload pick the resources it needs, it knows it because it knows how much demand. Demand goes up, more resources. Demand goes down, you leave resources. But then, we know the right order of the resourcing that it needs. All the way down the stack, from the application to the virtual to the physical. And that allows us to give exact right actions, not recommendations. Recommendations we think, are like opinions. You can't automate them. And alerts. But if you think about being able to be so accurate, and so exact in the analytics you produce, that you can actually automate them. That's the ah-ha. >> Well, it's brilliant. I mean, you've got the marketplace demand, and that decides. But, you've also got to do this is near real time, right? To have this impact. >> Continuously, correct. >> So, that's your analytics, that's some machine intelligence going on under the cover? >> So, people talk about AI ops, this is AI ops. We have a data model, the data model covers the customer's on prem environment as well as their off prem if it's Amazon or Azure. And now, I can see all the workloads I run, and all of the performance issues, all of the compliance exposure, and all of the efficiency opportunities inherent in each one workload. We show it to the customer, and then they can run What if Scenarios in offline, not with a synthetic, but with their actual workloads. Say, how would you like to see that workload in one of these other environments, in any direction? Now we're getting into multi-cloud management, right? >> Yeah, and abstract all that API complexity and all that diversity. And just one more follow up if I may, Stu. I want to understand the business impact. >> Sure. >> We covered kind of what it is and how it works. Why do customers buy? What's the business impact? >> So, the most important thing is you've got to have application performance. If your apps aren't running, your business isn't running. Fair? The second one though is, boy, compliance regulations just keep coming, right? And there's lots of different forms of compliance in policies. It could be a static one like HA, or data afinity, or an anti-afinity, things like that. But then there's also a myriad of raising level orders. People are trying to enforce all of these policies manually, which means they don't really know at any given time, whether they're in conformity with their own policies. Then you could ask, well, then why have them? So, that's a second big driver. The third one, is just cost. If we actually run the environments well, and we know that demand picks it, then actually you don't need to over provision the virtual, or the physical, or both environments, which is what most people have been doing for years. >> Then the area I want to drill into is that multi-cloud management that you mentioned there. Managing environments has always been a challenging situation for IT. You know, you think back ten years ago, you know V Center is the center of the world for anybody in virtualization. System center for Microsoft Shops, in the multi-cloud world, it's still a bit of a jump ball. You know, Cisco of course with their cloud center sweep, want to have a strong position to live in that multi-cloud world. Tell us, what are you seeing in the marketplace today? Where does, you know, your OEM solution with Cisco fit into this overall orchestration, and what are you hearing from customers? >> So, there's a couple of things. If you look in the customer side, when you go multi-cloud, you have to have different skill sets. They're different platforms, different vendors, right? And, by the way, so extreme in some cases, where one is principally a fixed cost environment, verus two that are variable expense based environments. Right? So, I have to think about which is the type of workload I want to run based on the demand parameters for each of those to make the most economic sense and the best performance attainable. If I have something that's going to scale massively, I want to leverage the elasticity of the public cloud, more likely than not. But, to do that, I better be ready to manage it in that fashion, right? And so somebody has to understand the nature of demand, and when to scale that up and when to scale it down. We've had customers literally take monthly change control windows, down to nightly in order to manage that because the savings are so material, right? So, it's really a matter of they need some level of automation, Stu, to be able to know which workloads should run in a given environment, in a given way consistent with what the platform vendor is offering. And that's what we do. >> I love stories like this, right? They harken back to Frank Sluteman, who's kind of a mini business hero of mine. He was the founder of David Domain, well CEO, and obviously helped service Now Gro. And he would say to me, "I love ROI stories." Like, going in, and just being able to show people bottom line impact. You clearly have that here. Application performance is very clear, how you affect that. When you talk to customers about the economic potential, what are you seeing? If you sort of scanned your customer base. You know, what kind of savings are you seeing? It sounds to me, I'm inferring 20% is kind of a no brainer, but I could imagine 30% plus savings. What are you seeing if you took an anecdotal scan of your customer base? >> So, very typically we can find, because the VM is over provisioned, the virtual layer, and the physical is over provisioned to manage the environment, try and assure performance. Typically we will find 40, 50% of a customer's data center available to be made more efficient, okay? When you then go, though, and this is really interesting. If you go to, let's say ECS and Amazon. There's 1.7 million combinations that you can pick from in ECS. So, Amazon refers to us as a customer control plane, because we understand the fundamental demand on the workloads, we'll pick the right instance family; so you don't have to go and try to pick and guess and allocate based on compute instance types, memory, network, storage, then whether or not to put an RI, Reserved Instance, against it, what region to run it in, all of those things, we could take care of, and help find and land that thing in the right order. When you don't have that, people will naturally allocate. They're going to do what's called a lift and shift, take an over provisioned VM on Prem, and bring it into the cloud. And that's the source of these incredible cloud bills. People go, wait a minute, this is too expensive, cloud was supposed to be cheaper. Well, that's because they didn't optimize it before they moved it. So, our strong preference is let's look at your workloads on Prem, let's find you the right home and the right instance family off Prem, to assure performance and then we'll manage it ongoing with that continuous actions that we do. >> And that changes the operating model. And, of course, when you talk to Amazon about this, they actually love that because they understand that there is price elasticity. If they're saving customer's money, that means the customer is going to buy more compute, they're going to buy more storage. >> Yep. >> Have you seen that in your customer base? >> Absolutely. So, Amazon is on record as having cut price in EC2 62 times. They have a retailer's mindset, and Microsoft has to match them and does. Okay? So they're both interested in taking costs down to serve the customer. When they don't, there's a problem. The problem is, the customer gets a cloud bill that was far in excess of what they expected to see. Gardener has some great data on this, about just how big those numbers can be. But what happens is two things. One, they go into a pause. And that pause can reduce the rate of migration for a year or better while they're trying to digest and get the skills and learn how to manage their workloads in that environment. The second thing is there's a loss, a slight erosion of trust. And then they want a dual source, and then they want to bring in other vendors and so forth. And the reason is they're just trying to figure out how to make this migration, which they know they have to, every CIO has a cloud MBO, but they have to have a way to know that they're not going to bleed themselves out in the process. Those are the two things that I see most frequently from customers. >> Yeah. Ben, as an observer, I want to get what you've seen from customers. How do they look at Cisco as a software provider in general, and as a partner in this multi-cloud world, specifically today? >> Well, I think Cisco has done a number of things. Again, I would go back to they really set a new direction with the direction that Chuck Robbins has provided as CEO, with the purchase of App D, with the services. If you go to the Innovation Hall, and you'll see the Solutions Hall. You'll see the Cloud services that they're offering, and then I think finding folks like Turbonomic. Literally, branding it under their name and selling it at CWAM. Those are pretty big de-marketers of their commitment to cloud, to multi-cloud, and to software. >> So, we were talking in our open about this whole multi-cloud, you know, marketplace. The horse is on the track. You know Cisco, clearly coming at it from a networking standpoint. Obviously, you've got VM Ware doing its thing, coming at it from what used to be purely Hypervisor, now expanding. You've got IBM and Red Hat, certainly Microsoft in the mix. It's a really interesting dynamic. You guys are a best of breed player, that's your strategy to keep ahead of the competition or the supposed competition, and partner with some of the big guys. What gives you confidence, Ben, that you guys can keep that technical lead and that market lead relative to both the competition and some of your partners? >> Because smaller companies have to focus, right? So we focus. We focus on workloads, and we're going to let those workloads run. We do not have a bias in our pricing model, in our infrastructure allegiances or anything. We have a bias on making sure the workload is always performant, compliant, and cost effective wherever it runs. So, our thesis is customers will always want to have multi-clouds. Not one provider, but multiple. And therefore, want the best workloads that will stay and grow with them. And so, that's why we have such good alliance with both Microsoft and Amazon. Because again, they're the net receivers of a lot of these workloads. One of the reasons we have such a good alliance with Cisco is because they're not going to be a cloud-vider. They're going to be a technology provider to those that want to provide services and technology to the Cloud providers. So, I think there's a nice match there in terms of our focus and our ability to continue to evolve. And let's just remember how dynamic this is. I mean, we were just talking about VMs in the last 10 years. Now, in the next five, you're going to see a complete shift over to containers, pods, and microservices. Different kinds of schedulers, different kind of IP stack; and that's the bed I think you mentioned that Red Hat and IBM are making as well. >> Well, your timing has been phenomenal. I mean obviously, coming out of the downturn, Cloud had a huge uptick. And now it's very clear, like you said, every CIO has an MBO on getting the Cloud. And you guys are well on your way to hitting escape velocity. Congratulations on that. >> Thank you. >> And thanks so much for coming on theCUBE. >> Thank you, Dave; thank you, Stu, pleasure. >> Okay, you're welcome. Alright, keep it right there everybody. We'll be back with our next guest. Dave Vellante and Stu Miniman, we're live from Cisco Live Barcelona, you're watching theCUBE. Thanks. (electronic music)

>> Live from Seattle, Washington, it's theCUBE, covering KubeCon, and CloudNativeCon North America 2018. Brought to you by Red Hat, the CloudNative Computing Foundation, and the Antigo System Partners. >> Hey, welcome back everyone live here in Seattle for the theCUBE's coverage of KubeCon and CloundNativeCon 2018. I'm John Furrier, theCUBE with Stu Miniman, breaking down all the action. Three days of coverage, we're in day two. A lot of action at Open-source. 8,000 attendees, up from 4,000 North America, they were in China, they were all over Europe. The community's growing in a massive way. We had two great guests from Red Hat, all making it happen, part of the community. We've got Diane Mueller, whose theCUBE alumni director of community development, many times on theCUBE, good to see you, and Rob Szumski, principal product manager, both at Red Hat. Guys, thanks for coming on. Great to see you again. >> Yeah, glad to be here. - Great to be here. >> So the world's changing a lot, and there was some news recently around Red Hat. I can't remember what it was. Recently, something big news, but you guys have been big players in Open-source for years. We always cover it, we always wax on about the origination of it and how the evolution, but the CloudNative piece has gotten so real, and your role in it particularly, we've had many conversations, going maybe back to the OpenStack days of how OpenShift was developing, then the bet on Kubernetes that you made, Core OS acquisition, those two things I think, to me, at least from my perspective, really catalyzed a lot of things at the right time, right? So, from there, just a lot of things has just been happening really in a good way. Big tail wind for you guys, CloudNative app developers are using Open-source, CI/CD pipeline, and then also policy based up under the hood, completely big shift in moving the game down the field. So big congratulations first of all. But what's new? What's the update? >> The update is Operators. I think the next big thing that we are really focusing on, and that's a game changer for all the second day operations type things, and we'll make Rob talk about it in detail, is the rise of Kubernetes' Operators. It's not a scary thing, it's not like terminator day, or anything like that, but it is really the thing that helps us make the service catalogs, the Kubernetes marketplaces really accessible to all of the data bases as a service, and all of the other things, and takes out some of the complexity of delivering applications and database  as a Service to anybody running Kubernetes anywhere. >> Take a minute to explain Operator, real quick, and then we can jump into it, because I think this is a fundamental trend, that we're seeing. Developer trend is pretty obvious, it's been that word for awhile, CloudScale, ML, machine learning, and all the goodness around application development, but the Operator side of it has been an IT thing. But now you guys have a different, a new approach that's winning. What is it? What is Operator? >> Well, it's Kubernetes that has the approach, and I'll let you-- >> Yeah, so it's basically like the rise of containers was great, because you could take a single container and package an application and give to somebody, and know that they can run it successfully. And Operator does that for a distributed system in the exact same way. So you're using all the Kubernetes primitives, so you're not reinventing service discovery, and seeker management, and all that. And you can give somebody an entire Kafka stack, or a machine learning stack, or whatever it is, these very complex distributed systems, and have them run it without having to be an expert. They need to know Kafka at a high level, but not exactly all the underpinnings of it, because that's all baked in the software. >> And the benefit and the impact of the organization is what? >> And just to clarify, so this was added in, I believe Kubernetes is like 1.7, it's something that's in there, it's not something Red Hat specific- >> Yeah, it's like-- >> So you're extending Kubernetes so that you have a custom resource definition, which is an extensible mechanism for saying, hey, I've got a deployment or a staple set, but what if I want to have a new object called a MongoDB? That knows how to deploy, and manage, and upgrade MongoDB. So that's the extension mechanism that we're using. >> Yeah, so you got to think, there's certain applications that this is going to make, just a lot easier how I manage them, deploy them, things like that. Any specific examples you want to share as to-- >> All the clustered data bases. >> There's a lot of the application side in this model have been very excited about this. >> So its all the vendors and partners that want a hybrid Cloud story, just targeting Kubernetes, and we're using Kubernetes under the hood, and then everybody wants to run like a staple data base tier, whether that's Mongo and Couchbase, and Cassandra, whatever. And these are all distributed systems. >> Alright, so I want you to just perch, you said a hybrid Cloud. Explain that model, because there's just something in general discussion that is hybrid or multi means I'm running multiple places, I'm not necessarily stretching an application, but I have instances there, just want to make sure we're on the same page. >> So this would be more the compatibility that you're programming against when you're building an operator, is Kubernetes. It's not a Cloud offering, it's not OpenShift, so you're just targeting Kubernetes, and so you can run MongoDB on prem, in the Cloud, and have it function the exact same, by standing up one of these Operators. And then if that Operator has higher level constructs for how to do multi-cluster aware data rebalancing, you can take advantage of that too. >> And the Open-source status of this product is what? >> It's all Open-source, it's all in the github repos, there's a Google group for Operator framework, that anyone can come and participate in. We hold SIG meetings on the third Friday of every month, 9 a.m. Pacific Time, and it's a completely Open-source project. There's a whole framework around it, so there's the Operator SDK, the Operator Lifecycle Management, and Operator metering, all the tooling there to help people build and manage these Operators, and it's all being built out there in the open with the community's support and feedback loops. >> What's the feedback? What's the top feedback you guys are getting right now? Seeing right now? >> I have to say, this is really, like I've been hanging out with you guys like for the past three, four months on this topic, trying to get my head around it and everything, and we came here and we had two sessions, an intro session and a deep dive session, intro yesterday, deep dive today. Today's deep dive, the room was about 250 people, and they're were people outside of it-- >> Security guards blocking people from coming in. >> Nobody could come in and it's like, it's insane. It's like, everybody needs these things, and everybody wants to figure out that, and when you ask people in the room whose building one, half the room raises their hands. It's just crazy. This thing crept up on us really, maybe not on Core OS, okay, it crept up on me very quickly, and it's very rapid adoption. We have a Kubernetes Operators workshop on Friday, so not only do we have pre-conference days of like OpenShift Cons that are huge now, but now we're starting to book end, CNCF events and put on other things, just because, and that, we had 100 seats that we were hoping we would fill, and it sold out in like minutes once it got in there, and there's a waiting list of like 300 people. It is like one of, aside from Knative, and all the other wonderful hot things too, it is one of the most interesting developments I think right now. >> Thirst for the content. Would it impact? >> Yeah, and you can get all of the documentation is out there now, and people are already building them. We have a list of 50 community Operators. It's just, it's phenomenal how quickly it's growing. >> You know, Diane and Rob, it's funny because you know, we do so many of these theCUBE interviews, and this is our 10th year doing theCUBE coming up, and I remember the conversations going back in the OpenStack days, we would ask questions like, if you had a magic wand, what would you like, hope to have happened, right? And you know, those are parts of the evolution, where it's like, it's aspirational, things are being built. It seems now with Kubernetes, it's almost like, wait a minute, it's actually, this is like the goodness is so compelling, above and below Kubernetes that it's almost like uncomprehendible. You think about, oh this is actually happening. Finally the kinds of steady state kind of operational things that have been a pain in the butt for years-- >> Yeah, the toil, it's gone, for the most part. >> Yeah. >> So Rob, I've been having a lot of just thinking back to, you're employee number two at Core OS, when I first talked to Core OS, it was, we're going to build all of these individual tools, and we're going to Open-source them, and it's going to be good. We watched this just rising ecosystem and the CNCF, and it feels like what's nice and what's different that I see, compared to some previous things, is it's not one product or even a small group of companies. It's, I have this tool kit, and some of them work together, but many of them are independently used. We've talked to your peers earlier about it, etCD. etCD is totally stand alone, doesn't need to be Kubernetes. What have you seen, if you go back to that original vision, would Core OS just been, part of this whole ecosystem, and done it, if this was available, and has this delivering on a promise that your team had hoped to work on? >> Yeah, so we've always filled in where we see gaps, and so something like etCD, the concept is not new, and it comes from Google, and they have a system internally, and as Brandon got up on stage and said, we needed that coordinate, reboot, to grow out, to cluster of machines. It didn't exist so we had to build it. Same thing with how we wanted to manage Linux. There was no distro that even resembled what we were doing. Wanted to do automatic upgrades, people thought that was crazy, so we had to go build it. And so, but we always adopted the best of breed technology, when it existed. In our early bet Kubernetes, we just saw, this is the thing, and went for it. I don't even remember what version, but it was months and months before it was zero point oh, or one point oh, so it was, we've been doing it forever. And you just see the right thing, and it's the little nugget that you need, and if you don't see it, then you build it. >> What are you surprised about Rob, in terms of the ecosystem now, you mentioned some goodness is happening, still a lot more to do, visibility around value creation, you're starting to see spots where value can be created in the ecosystem, which is great. Still more work areas, but what's surprising you? What do you see as opportunities, challenges? Your thoughts, because this vision of ease of use and programmability, is happening, right? So there's still more work to do. What's your vision there? What's your thoughts? >> I mean, I think self service is key, so this is like the rise of the Cloud comes from self service for developers, and Kubernetes gives you the right abstraction, where self service for VM's, like OpenStack, which is not quite at the level of what you want. You don't want a VM, you actually wanted a place to deploy an application, you wanted load balancing, you wanted service discovery, you didn't want like a bare Ubuntu VM, and so Kubernetes raises you up to where you're productive, and then it's about building stuff on top. But what's interesting, in the space is, we're still kind of competing on Kubernetes installers, and stuff like that, so we're not even really into like the phase where people are being super productive on the platform, other than these leading companies. So I think we'll democratize that, and we'll have a whole new landscape. >> And so 2019 you see as what being a key theme for Kubernetes? >> I think it'll be Core stuff built on top, like all the serverless frameworks, a bunch of container natives storage solutions, solving some of these problems that folks are reaching out to external machine learning, but bringing that onto the cluster, GPU support, that type of stuff. It's all about the workloads. >> And tradition end users, you have a huge install base, with Red Hat, well documented, as the end users start coming in and looking at CloudNative, and doing a reimagine of their environment, whether it's IT span, IT investments, to have a run their coding and the deployments. It's going to change. 2019's going to have an impact on what I call mainstream enterprise, for lack of a better description. What's the impact of those guys, 'cause now, they now have head room, they can do more, what's the main stream enterprise look like right now with the impact of Kubernetes? >> I think they're going to start deploying applications and get like lower the time to business value, much, much lower. And I was just talking to a customer, and they ordered bare metal machines like a year ago, and they're still not racked and in the data center. And so people are still getting over that type of stuff, but once you have like a shared Kubernetes layer, you can onboard teams like crazy. I mean, name spaces are free, quote, unquote, and you can get 35 engineering teams on a Kubernetes cluster super easy. >> So they can ramp up in development teams basically, as they bring value in-house, versus outsourcing everything. They start getting development teams, this is where the action is. >> I think you're also going to see the rise of those end users contributing back things, to the Kubernetes community and as Lyft, and Uber, and everybody are great examples of that. Uber with Jaeger, and Lyft is, we were just in the Operators thing, and they raised their hand that they are about to Open-source it, a few Operators that they're building and stuff, and you're just going to see people that you didn't normally see. Often these large foundation driven things are vendor driven, but I think what you see here, is the end user community is now embracing the Open-source, is getting the legal teams there, allowing them to share their things, because one, they get more people to maintain them, and more people working on them, but it's really I think the rise of the end user we'll see, as they start participating more and more in here. And that's the promise of Open-source. >> And that's where CNCF really made it's bones. It wasn't really vendor led per se, it was really end users, the guys building out their stuff for the first time. You see Lyft for instance, great example, you guys did a Core OS, this is like the new generational model. Final question before we break. I want to get this out there. Get a plug in for Red Hat. What are you guys, what's the focus for the show? What's the news? What's the big story for Red Hat here at KubeCon this year? >> I think it's Operators, that's what we're here talking about. It's a really big push to once again get smarter workloads onto the cluster. We've got a really great hybrid story, we've got a really great over the air upgrade story that we're bringing from some of the Core OS technology, and then the next thing is, once it's easy to run 35 clusters, we need a bunch of workloads to put on there. And so we want to save folks from the toil of running all those workloads as well, just like we did at the cluster level. >> Awesome. >> Well put. I couldn't add more. One of the things that Core OS did, you hit the nail on the head earlier, is when there was something missing, they helped us build it, and with the Operator SDK, and the Lifecycle Management, and the metering, and whatever else the tooling is, they have really been inspirational inside of Red Hat. And so they filled a number of gaps, and it's just been all Operators all the time right now. >> It's great when a plan comes together. You guys got a great tail wind. Congratulations on all the success, and it's just the beginning of the wave. It's theCUBE, covering the wave of innovation here at KubeCon CloudNativeCon 2018, we'll be back with more live coverage. Day two of Three days of Kube Coverage. We'll be right back. (upbeat music)

>> Live from Seattle,Washington, it's theCUBE. Covering KubeCon andCloudNativeCon North America 2018 brought to you by Red Hat, the Cloud Native Computing Foundation, and it's ecosystem partners. >> Hey, welcome back everyone,live Cube coverage here at KubeCon, CloudNativeCon2018 in Seattle. I'm John Furrier with Stu Miniman hosting three days of coverage. Wall to wall, 8,000 people,double from last year, North America, expanding intoChina, Europe, everywhere. The CNCF is expanding, so is Kubernetes. The rise of Kubernetes has spawned the Cloud Native movement going mainstream that's ecosystem driven. We got a great guest here. Steven Bower, data andanalytics infrastructure lead at Bloomberg, featuredthem on siliconangle.com in one of our special reportsand user using Kubernetes and the variety of Cloud Native. Steven welcome to theCUBE. >> Thanks for having me. >> Thanks for coming on,award winning end user, given all the end users,everyone's kind of award winning. >> Yeah, yeah, yeah. >> Congratulations. Bloomberg's known, we've covered you guys, great development team. You guys have a lot ofengineers at Bloomberg as well as being a media company on cable, Bloomberg terminal, everything else. You've got a lot of datascience, you've got a lot of engineers, you're building stuff. What's the focus on Kubernetes? Where are you using it? How are you contributing? What's the dynamic? Why are you winning with Kubernetes? >> Sure, that's a good question. I think, well we're usingit all over the place in lots of different things. We have a huge engineeringteam that does all kinds of different things. So in the area that I manage,which is data and analytics infrastructure, we have been we basically managedatabases and search engines and all kinds of other tech like that. What we've ended uprealizing is that we built something that looks a lot like Kubernetes but doesn't work nearlyas well for all of those different systems, tomanage them at scale. You know, we're talkingthousands of instances of post cross and solar andall kinds of different things and having a singletool, or single platform which we can kind of levelup all of those things really makes a lot of sense in terms of not necessarily like cuttingcosts and things like that 'cause that's actuallynot as interesting to me as actually allowing theteams that manage those things to actually contribute to those projects, contribute to solar or postcross and stuff like that and free them from havingto spend a lot of time managing infrastructure. >> Tim Hopkins said, itwas just on theCUBE here before you came on,from Google, one of the co-leads on Kubernetesat gkegoogles@cloud. He said something interesting. I want to get your reaction to this. One of the benefits of Kubernetesis to give the confidence that deployments are going to be reliable and that confidence gets a flywheel and then people startshipping more as a matter of course of the business,not like oh my God we got to push a new code,oh my God, fingers crossed, press the button. The old model was fingers cross, go, QA, no, no, confidence, theconfidence and the iteration. Is that where you'reseeing the value, too? Does that relate to you? Does that make sense to you?Does that resonate with you? >> Yeah, it definitely does. A lot of the models thatwe're trying to move towards are really like declarative model of both how we develop software andthen how we deploy software and then how we manage it in production. Kubernetes offers that, thatecosystem across the board. That's been really, trying to think of a great way to put this. Being able to have that tooland being able to do that and the repeatability. In the world that I livein, everything we do we don't do one of it,we do, I think we run something like 2000 solar clusters. So all we're doing all daylong is just stamping out the same thing over and overagain and if I can build one system that doesthat very, really cleanly and simply and then I canuse that same system for running post tests orrunning something else that gives us the confidenceand we can test it, we can run it on our laptops. Our developers can developand do all that kind of stuff and it works the same everywherethey go and we can just rinse, lather, repeat kind of. >> So Steve, step back for a second. Your infrastructure, is thisall Bloomberg Data Center's? How does cloud fit into the discussion? >> Yeah, I mean, we dohave some infrastructure running in the cloud but primarily it's all on prem and data center. In my world it's all onmetal because we have all these data systemsthat need direct access to SSDs and MME andall this kind of stuff. >> Can you give us, withoutsharing state secrets, a little bit of the scaleof what you're doing? I love data's at the centerof what you're doing there. We can all understand howimportant data is to your business but talk aboutwhat the requirements are that why you have some special requirements that thetypical enterprise wouldn't. >> Sure, I think, youcan look at Bloomberg as a media company, wehave news, all that stuff. We obviously have the Bloomberg terminal and really what drives that terminal, it's all kinds of software but in the end it's data, right, andit's all kinds of data. What is that definition,big data and all these whatever stuff that everyonewas pitching five years ago. We have all of those problems. We have data that is movingat millions of ticks a second. We have enormous data sets. We have really complex data sets like people scanning courtfilings from tiny little courts all around thecountry and sending that data in and we have tonormalize that and put it in. So all these crazy differenttypes of information. They are both demanding interms of the complexities of parsing data and puttingthem and structuring them into those systems as wellas the scale so we have some pretty enormous andhigh performance systems that require us and kindof drive us to that need for metal and very focused on performance in all different aspects. >> Great, wonder, give us your engagement with this ecosystem here. One of the big questionscoming in is okay, Kubernetes, the thingwe here from the CNTF is well, it's getting kind of boring. I don't know that I agree with the term. I understand they'resaying it's becoming mature and therefore there's less drama around it which is good but this ecosystemis anything but boring. You ask a user like yourself, you've got complex requirements. There's more than 30different projects a year. What do you use out of here? What do you build yourself? What do you contribute to? How do you consideropen-source contributions? It's a big nut and wedon't have a ton of time but if you could scratch thesurface on some of those. >> I think the number onelesson that I've learned from this ecosystem isthat it's moving so rapidly that when we decide tobuild something on our own we have a talk tomorrow aboutour data science platform which we built about ayear-and-a-half, two-years ago. By the time we were ready to talk about it and everything like that,you have all the other different technologiesthat have moved forward. So it made us realize thatif we're going to start something internally,a new project, either A we should go look and seewhat's out there and contribute to that or we should juststart it in open source to begin with rather thanthat oh, let's build it and then we'll open source it. >> Chasing your tail kind of thing. >> Yeah, it's like we have tobecome part of the ecosystem in our entirety. >> That brings up a good question. I want to ask you this incontext of thinking about your peers that mightnot be as progressive as Bloomberg on the tech side. You guys certainly do a greatjob and it's well documented. Classic IT shop, racking andstacking servers and boxes and now we got the wholedigital transformation thing going on, same old, same old but now, 2019, real impact. The investments they'remaking on how to change their IT, their data isnow in front of them. They have to deal with them. This is right front andcenter 'cause companies are realizing they'regoing to go out of business if they don't actually make the adoption 'cause the data's super valuable. So how do you see the Kubernetesand the CNC of ecosystem changing the investment practices of a classic enterprise IT? You know, if your peerscalled you and said hey Steven, hey help me out,what's the secret playbook? Where do I go? I don't want to get, Igot to make some changes. What do they change? What's the impact of theinvestment with Kubernetes? What's the end game? What's the real impact? >> I think, it's a toughthing, right, 'cause Bloomberg is really notlike your typical IT shop. We are a software company at heart and so that makes us alittle bit different. When I talk to other people,I say that in the sense that not a lot of companiescan afford to decide to make a project open-- >> 'cause they outsource everything. >> Right, outsource it. Well, I mean-- >> They outsource everything. >> That's actually a huge change though. We're not sitting heretalking about hundreds of commercial products that are owned by a small handful of vendorsthat are multi-million dollar investments foreverything we're doing. We're talking about lotsof little tiny companies that have products thatare really, really valuable that are in the open sourceworld that we can get our hands on and startworking with before we even make a decision about talkingabout support or whatever. There's all kinds of technologies that, I walk into this room andthese are like friends all around 'cause we'veworked with all their software and we're like hey, theseguys have a company now. This was just a GitHubrepo a couple years ago and I think that that's abig change and embracing that, that's probablyreally hard for your typical kind of IT shop where theywant to have this clear line of I can call techsupport and get someone on the phone and that's like the main-- >> The classic old software model but it's changed. >> So Steve, one of thethings we're trying to get some insight on here isit's not just running Kubernetes in production,it's what am I doing with it. How does that change my business? I understand ML is a big pieceof what you're doing there. Give us some insight as to how does this transform your business? Does it transform your business? >> Specifically on the MLside and we'll talk about this actually that's kind of thefocus of our talk tomorrow so I don't want to stealtheir thunder too much but a lot of it was really about looking at okay, how did ML, deep ML people work? How did they want to work? If you ask an ML personwhat they really want they want an infinitely scalable cluster that it's just theirs and they want to an assay to manage all theinfrastructure for them and a data engineer to managecleaning up all the data and all these things and they wanted that all to themselves and not haveto share it with anyone else. So a lot of what we try tofigure out is how we can actually deliver that to themand it really has transformed. Once people realize that onour platform they had access to an enormous pool of GPUs,it went from oh, I want to work on my box and can you giveme GPUs on my one little box to wow, I can dohyper-parameter tuning across hundreds of GPUs overnight or during the day or whatever their needs are. It really unlocked people's capabilities and they're actuallylike, they went from being skeptical of a systemthat they had to share and things like that 'causeit actually just works and that's really the-- >> That's really thedopamine effect for them. They can see value withouthaving to go through the slogging of the configurationsand the normal stuff >> Yeah, exactly.>> that they had to do. >> Authentication. >> So we've been hearingthreads of the CICD pipeline is a big benefit,which you're kind of seeing as well but whatwe're also seeing people building below Kubernetes seeing storage and networking getting better. How do you see that holistically? Are you seeing is thenetwork more performant, that notion of programmabilitybecomes now part of it, automation, it's software. Everyone has to build software. In fact, I talked to theVP of Technology Innovation at Proctor and Gamble andhe's saying hey, we outsourced everything, I got to start hiring software so maybe not as big asBloomberg but the trend is let's get more software people on board but they still got networks,they still got storage, they still got the gear. What's the impact, the under-the-hood? >> Yeah, I think it'scomplex because you typically have these structures thatare built inside companies where you have a networkingteam and you have an infrastructure, ahardware team and whatever. One of the SREs on my team the other day, he was like, do you thinkwe can talk to the network team about puttingsoftware on their switches? That's a really interestingquestion to start asking and he actually had areally good use case. That makes a lot of sense, maybewe should think about that. And then dealing with, there'sobviously the technology aspect of that but there's also skillsets. Someone that's been workingwith a bunch of switches for a bunch of years isn'tnecessarily a programmer, used to a typical CICDprocess and things like that. >> On the flip side, I thinkthat's cool to recognize the networking guy butwe heard Tim Hopkins say there's a lot of policyknobs in Kubernetes that the networking guyscould potentially take advantage of so it mightwork the other way. Are the network guys looking at Kubernetes saying hey, or are theynot yet that sophisticated but they would love, they'd love policy. Network guys write policy. Wouldn't you want-- >> Yeah, yeah, oh absolutely. It's actually one of thebiggest draws of using Kubernetes in our ecosystem. We've made heavy use ofapplying network policy down to the workload level which means that from a securityperspective, if I know that I'm transmittingdata between two different places and I've only openedup assets for that one application, for thatone particular use case, rather than saying well,I know that I'm running the same workload on thesame box and I got to open it up for everyoneon that box but maybe someone might use thatthing but maybe they won't and like worrying about stuff like that, it's like no, I can runa workload and I know that these are the only two end points that it can talk to. >> Oh, that's a relief. That's like, hey, we're done. >> So for them this is their panacea. I know exactly whatworkloads are doing exactly what on the network andwhat they're capable of so that's been-- >> That's real progress. That's progress. >> Oh, it's huge progress, yeah. And we've been able todo things that we used to not be able to do for years. >> Talk about the-- >> I just had a quicklittle question there. You mentioned you've gotten SREs. When did you pick that up asa term that you called there and how do you see if you talk a little bit to the skill set and the jobs of peoplethat you have inside. >> Bloomberg's a big companyso the terminology of it and what actuallyindividual teams are doing is probably a little bitvaried across the organization. It's been something that'scome in over probably the last two to three years at Bloomberg. In my organization, it wasactually really interesting 'cause when I started off with, you know, you read the Google book and whatever. What I did is I wentto the guys on my team that were going to becomethe SREs for the organization and I had them write thismanifesto about how we should build and deploy and managesoftware and I didn't tell them necessarily up front thatthis is what was going to happen but when they finishedwriting that and agreed that this is how thingsshould work and they argued for a while, I said, okay,now go build all the tooling to make this easy forpeople to do, all right. And that's what we, and thenthey've just been building off their tooling. Turns out when you're workingwith a lot of the tools and the CNTF and then with Kubernetes, that's actually not that hard. There's lots of thingsthere that are just easy when you get to that place and so that's the kind of journey we'vebeen on to really try to build that infrastructure andthey've done a good job. The engineers downstream of them the speed that they're able to develop and the assurance that there was a CVE forKubernetes two weeks ago and we patched it theafternoon the CVE came out. Being able to do that in anysort of company of scale is I've worked a lot ofbanking and stuff like that in my past and it's unheard of to be able to deploy things in that speed. >> And that's really, Imean this is the goodness of clouds, the goodnessof having that kind of consistency operationally. It's funny you use SRE,that's a Google term. It's a great term andyou've got developers, you got operations kindof working together now. That's the magic. Well Steven, thank you so much for sharing this great insight on theCUBE. Certainly great valuefor the folks watching. Lot of traction, a lot ofpeople, end users contributing and consuming Kubernetes,building around it. Great trend, it's really fun to watch. A lot of composable servicesup and down the stack so congratulations. Steve Bower, Data andAnalytics Infrastructure Lead at Bloomberg. This is theCUBE bringingyou all the action, sharing the data here at KubeCon. This is theCUBE. We'll be right back withmore after this short break. (electronic music)

>> Live from Seattle, Washington, it's the Cube, covering KubeCon and Cloud Native Con North America 2018. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partners. >> Welcome back everyone. We are live in Seattle for KubeCon 2018, Cloud Native Con. It's the Cube, I'm John Furrier, your host with Stu Miniman. Our next guest is Ashesh Badani, who is the Vice-President and General Manager of Cloud Platforms at Red Hat. Great to see you, welcome back to the Cube. >> Thanks for having me on. Always good to be back. >> So you guys, again, we talk every year with you. It's almost like a check-in. So what's new? You got some big, obviously, the news about the IBM. We don't really want to get into that detail. I know you just a stop on that because it's already out there. But you guys had great success with platformers of service. Now you got the growth of Kubecon and Cloud Native Con, 8000 attendees and users. There's uptake. What's the update on the Red Had side? >> Yeah, we're excited. Excited to be back at Kubecon. It's bigger and better than it's ever been, I think so. That's fantastic. We've been investing in this community for over four years now, since 2014. Really, from the earliest days. Based the entire platform on it. Continue growing that, adding lots of customers across the world. And I think what's really been gratifying for us to see is just the diversity of participants. Both in user perspective as well as the wider ecosystem. So whether you're a storage player, a networking player, management, marketing, what have you. Everything sort of building around this ecosystem. I think we're creating a great amount of value and we're seeing diverse applications being built. >> So you guys have been good then on (mumbles), good timing, a lot of things are going on. This show is an open-source community, right. And that's been a great thing. This is kind of where the end users come from. But two other personas come in that we're seeing participate heavily. The IT pro, the IT expert, and then the classic developer. So you have kind of a melting pot of how this is kind of horizontally connecting. You guys have been successful in the IT side. Where is this impacting the end users?6 How is this open-source movement impacting IT, specifically, and at the end of the day, the developers who are writing code? Have to get more stuff out. What's your thoughts? >> So, we hosted OpenShift Commons yesterday. OpenShift Commons, for the the folks who don't know, is our gathering of participants within the larger OpenShift community. We had lots of end users come and talk about the reason they're adopting a Kubernetes-based platform is to get greater productivity. So for example, if you're someone like Progressive Insurance, an established organization, how do you release applications quicker? How do you make your developers more productive? How do you enable them to have more languages, tools, frameworks at their disposal? To be able to compete in this world where you've got start-ups, you've got other companies trying to compete aggressively with you. I think it's a big dent here, right? It's not just for if you work traditional IT. But it's for if you were a company of all sizes. >> When you talk about customers, every customer is different. You've got, you look at IT, everything is additive, it tends to be a bit of a heterogeneous mess when you get there. Help connect for us what are you hearing from customers? How does, not just Kubernetes, but everything going on here in the Cloud Native environment? How is it helping them? How is it changing the way that they do their business and how's Red Hat involved? >> So one thing we've been noticing is that Hybrid Cloud is here and here to stay. So we've consistently been hearing this from customers. They've invested lots of money and time and energy, skills, in their existing environments. And they want to take advantage of public clouds. But they want to do that with flexibility, with portability, to bring to bear. What we've been trying to do is focus on exactly that. How do we help solve that problem and provide an abstraction. How do you provide primitives. So, for example, we announced our support of Knative, and how we'll make that available as part of OpenShift. Why's that? Well, how can we provide Serverless primitives within the platform so folks can have the flexibility to be able to adopt next-generation technologies. But to be able to do that consistently regardless of where they deploy. >> So, I love that. Talk about meeting the customers there. One of the things that really strikes me, there's so much change going on in the industry. And that's an area that Red Hat has a couple decades of experience. Maybe help explain how Red Hat in bringing some of that enterprise, oversight. Just like they've done for Linux for a long time. >> Yeah, yeah. Stu, you're following us very closely, as are you John, and the team at the Cube. We're trying to embrace that change as it comes upon us. So, I think the last time I was here, I was here with Alex Polvi of Core OS. Red Hat acquired Core OS in January. >> Big deal. >> Yeah, big acquisition for us. And now we're starting to see the fruits of some of that labor. In terms of integrating that technology. Why did we do that? We wanted to get more automation into the platform. So, customers have said, hey, look, I want these clusters to be more self-managing, self-healing. And so we've been really focused on saying how can we take those challenges the customers have, bring that directly into a platform so they're performing more and more like the expectations that they have in the public cloud, but in these diverse, introgenous, environments. >> That speaks to the operating model of cloud. You guys have a wholistic view because you're Red Hat. You got a lot of customers. You have the Dev House model, you got the Kubernetes container orchestration, micro-services. How does that all connect together for the customer? I mean, is it Turn Key and Open Shift? You guys had that nice bet with Core OS, pays big, huge dividends. What are some of those fruits in the operating model? So the customer has to think about the systems. It's a systems model, it's an operating system, so-to-speak. But they still got to develop and build apps. So you got to have a systems-wholistic view and be able to deliver the value. Where does it all connect? What's your explanation? >> So distributed systems are complex. And we're at the point where no individual can keep track of the hundreds, the thousands, the hundred-thousand containers that are running. So, the only way, then, to do it is to be able to say, how can the system be smart? So, at the Commons yesterday we had sort of a tongue-in-cheek slide that said, the factory of the future will only have two employees, a man and a dog. The man's there to feed the dog, and the dog's in place to ensure the man doesn't go off and actually touch the equipment. And the point really being, how can we bring technology that can bring that to bare. So, one example of that is actually through our Core OS acquisition. The Core OS team was working on a technology called, operators. Which is to say, how can we take the human knowledge that exists. To take complex software that's built by third parties and bring that natively into the platform and then have the platform go and manage them on behalf of the actual customer itself. Now we've got over 60 companies building operators. And we've, in fact, taken entire open-shift platforms, put operators to work. So it's completely automated and self-managed. >> The trend of hybrid is hot. You mentioned it's here to stay. We would argue that it's going to be a gateway to multi-cloud. And as you look at the stacks that are developing and the choices, the old concept of a stack-- and Chris was on earlier, the CTO of CNCF. And I kind of agree with him. The old notion of stack is changing because if you've got a horizontal, scale-able cloud framework, you got specialty with machine learning at the top, you got a whole new type of stack model. But, multi-cloud is what the customers want choice for. Red Hat's been around long enough to know what the multi-vendor word was years ago. Multi-vendor choice, multi-cloud choice. Similar paradigms happening now. Modern version of multi-vendor is multi-cloud. How do you guys see the multi-cloud evolution? >> So we keep investing and helping to make that a reality. So, last week, we made some announcements around Open Shift dedicators. Open Shift dedicators is the Open Shift manage service, or AWS. Open Shift is available in ways where it can be self-managed directly by customers in a variety of environments. Directly run around any public cloud or open stack, or what you'd like environment. We have third-party partners. For example, DXC D-systems providing managed versions of Open Shift. And then you can have Red Hat managed Open Shift for you. For example, on AWS, or coming next year, with Microsoft. Through our partnership for Open Shift on Azure. So you as a customer now have, I think, more choice than you ever had before. In terms of adopting Dev-Ops or dealings with micro-services. But then having flexibility with regard to taking advantage of tools, services, that are coming from, pretty much, every corner of IT industry. >> You guys have a huge install base. You've been servicing customers for many, many years, decades. Highest level support. Take us through what a customer, a traditional Red Hat customer that might not be fully embracing the cloud in the past, now is on-boarding to the cloud. What's the playbook? What do you guys offer them? How do you engage with them? What's the playbook? Is it, just buy Open Shift? Is there a series of-- how do you guys bring that Red Hat core Lenux customer that's been on Prim. Maybe a little bit out of shadow IT in the cloud, saying, hey, we're doing additional transformation. What's the playbook? >> So, great question, John. So, first fall into the transformation might be an over-hyped term. Might be a peak hype at this point in time. But I think that the bigger point from my perspective is how do you move more dollars, more euros, more spend towards innovation. That's what every company is sort of trying to do. So, our focus is, how can we build on the investments that they've made? At this point in time, (mumbles) Lenux probably has 50,000 customers. So, pretty much, every customer, any size, around the world, is some kind of Lenux user. How can we then say, how can we now provide you a platform to have greater agility and be able to develop these services quicker? But, at the same time, not forget the things that enterprises care about. So, last week we had our first big security issue released on Kubernetes. The privilege escalation flaw. And so, obviously, we participate in the community. We had a bunch of folks, along with others addressing that, and then we rolled our patches. Our patch roll-out went back all the way to version 3.2, 3.2 shipped in early 2016. Now, the one hand you say, hey, everyone has Dev-Ops, why do you need to have a patch for something that's from 2016? That's because customers still aren't moving as quickly as we'd like. So, I just want to temper, there's an enthusiasm with regard to, everyone's quick, everything's lightning fast. At the same time, we often find-- and so, going back to your question, we often find some enterprises will just take a little bit longer, in reality to kind of get-- (both speaking at once) >> Work loads, they're not going to be moving overnight. >> That's right. >> So there's some legacy from those workloads. >> Right, right. And so, what we want to do is ensure, for example, the platform. So we talked about the security and lifecycle. But, is supporting these Cloud Native, next generation, stateless applications, but also established legacy stateful applications all on the same platform. And so the work we're doing is ensure we don't-- you know, it's like, leave no application behind. So, either the work that we'll do, for example, with Red Hat Innovation Labs. We help sort of move that forward. Or with GSIs, global integrated, real integrators to bring those to bare. >> Ashesh, wonder if we could drill a little bit. There's a lot of re-training that needs to happen. I've been reading lots on there. It's not, oh, I bring in this new Cloud Native team that's just going to totally re-vamp it and take my old admins and fire them all. That's not the reality. There's not enough training people to do all of this wonderful stuff. We see how many people are at this show. Explain what Red Hat's doing. Some of the training maturation, education paths. >> So we do a lot of work on the just core training aspect, learning services, get folks up to speed. There's work that happens, for example, in CNCF. But we do the same thing around certifications, around administering the systems, developing applications, and so on. So that's one aspect that needs to be learned. But then there's another aspect with regard to how do we get the actual platform, itself, to be smart enough to do things, that in the past, individual people had to do? So, for example, if we were to sort of play out the operator vision fully and through execution. In the past, perhaps you needed several database admins. But, if you had operators built for databases, which, for example couch, base, and mongo, and others, have built out. You can now run those within the platform and then that goes and manages on behalf. Now you don't need as many database admins, you free those people up now to build actual business innovation value. So, I think what we're trying to do is increasingly think about how we sort of, if you will, move value up the stack to free up resources to kind of work on building the next generation of services. And I think that's our business transformation work. >> And I think, even though digital transformation is totally over-hyped, which I agree, it actually is really relevant. Because I think the cloud wave, right now, has been certainly validated. But what's recognized is that, people have to re-imagine how they do their infrastructure. And IT is programmable. You're seeing the network. The holy trinity of IT is storage, networking, and compute. So, when you start thinking about that in a way that's cloud-based, it's going to require them to, I don't want to say re-platform, but really move to an operating-environment that's different, that they used to have. And I think that is real. We're seeing evidence of that. With that in mind, what's next? What do you guys got on the horizon? What's the momentum here? What's the most important story that you guys are telling here at Red Hat? And what's around the corner? >> Yeah, so obviously, I talked about a few announcements that we made right around Open Shift Dedicated and the upgrades around that. And things like, for example, supporting bring-your-own-cloud. So, if you got your own Amazon security credentials, we help support that. And manage that on your behalf, as well. We've talked this week about our support native, trying to introduce more server-less technologies into Open Shift. We announced the contribution of SCD to the Cloud Native Computing Foundation. So, continuing re-affirming our commitment to the community I think looking ahead, going forward, our focus next year will be on Open Shift four, which will be the next release of the platform. And there, it's all about how do we give you a much better install than upgrade experience than you've had before? How do we give you these clusters that you can deploy in multiple different environments and manage that better for you? How do we introduce operators to bring more and more automation to the platform? So, for the next few months our focus is on creating greater automation in the platform and then enabling more and more services to be able to run on that. >> Pretty exciting for you guys riding the wave, the cloud wave. Pretty dynamic. A lot of action. You've guys have had great success, congratulations. >> Thank you very much. >> You're fun to watch. The Cube coverage here. We're in Seattle for KubeCon 2018 and Cloud Native Con. I'm John your host. Stay with us for more coverage of day one of three days of coverage after this short break. We'll be right back. (upbeat music)

(technological music) >> From Yorktown Heights, New York, it's theCUBE covering IBM Cloud Innovation Day, brought to you by IBM. >> Hi, I'm Peter Burris and we are broadcasting theCUBE from IBM Innovation Day at the Thomas J. Watson Research Lab in Yorktown, New York. We've got a great number of guests to talk about. We're going to start with Hillery Hunter, who's the CTO and vice-president of cloud infrastructure at IBM. Hillery, welcome to theCUBE. >> Thank you very much. Pleasure to be here. >> So, you're relatively new in your role. Tell us about some of the things that you're focusing on as the CTO of cloud infrastructure here at IBM. >> As CTO for cloud infrastructure, I'm focused on making our cloud the best possible place that it can be for people to bring their data, bring their applications, and overall, come into that modernization journey with us, the process of transforming to become a digital enterprise. >> So, one of the things that people talk about all the time is how fast data's being generated. Nobody seems to be talking about how fast software is being generated, and yet, that seems to be one of the advantages and potentially the liabilities of doing cloud wrong. Talk to us a little bit about how IBM sees the world of software changing as we move forward with the cloud. >> [Hillery] There are parts that are consistent with what we've seen for about the past 20 years in open source, and there are parts that certainly, we feel like are accelerating and changing. With regard to the pace of software and its change today, open source is clearly this innovation space. It's this playground where lots of people can go and can contribute. We can take... We're here at the IBM research facility. We can take the latest in innovations and math that helps us accomplish great AI and AI insights. We can take that into open source. We can take microservice integration capabilities and take it into open source and work there collaboratively with people across the industry. What we see, therefore, is a tremendous rate and pace in change of software and the capability of software and its ability to analyze data and bring insights to data and realize the promises of big data, of getting insight out of that data, is just really on a tremendous growth rate. When you move to cloud, you're not just doing what they used to say of converting capital expense on premises into opex and renting a server in the cloud. You're bringing your overall workload and modernizing it and bringing it into this era where you're able to apply through microservices and cloud-based programming methodology, you're able to bring the latest of software capability to your data and get more insights out of it. >> You're really able to alter the operating model of how not only your technology group works, but also how your business works. >> Absolutely. >> How does Red Hat play a role in this? >> We have shared principles with Red Hat. We both have been active in the open source communities. IBM famously had billion dollars of investment in LINUX going back 20 years ago, and Red Hat is a prominent name in open source. We have a shared understanding of the value of open source and the value of rate and pace of innovation that's commensurate with what open source provides. We have a shared value around what enterprises need and a shared client-centric view that you need support on your software, that you need certifications, that you expect security, those kind of things. There's tremendous amount of shared value proposition in what we see as the rate and pace of innovation as well as then moving that into an enterprise context. Enterprises make these choices very carefully. As consumers of enterprise capabilities, we expect them to guard our data, we expect them to do things on our data in a secure way, and there are many foundational elements in philosophy that are similar between the two of us. >> You mentioned that cloud started out as this notion of capex to opex, move all your data to a single place, let somebody else deal with it. Increasingly, enterprise is starting to recognize that their data may sometimes have to remain in place. We start talking about innovation, open source, these new classes of services. What is it going to mean to bring the cloud experience to the data from IBM's perspective? >> We really see that the data today exists in multiple places, that largely because of that, people are partway through their journey to overall modernization. They're partway through their journey to the cloud. We really think that the world is going to be hybrid, meaning that... Or, the world is hybrid, I guess I would say, meaning that there is data and there is cloud function needed on premises and in public clouds. There's a need for private, dedicated environments in the public cloud as well. There's a significant amount of IT that is currently traditional in that people are in the process of modernizing, and that may initially be through a private cloud context on the journey to overall workload modernization. We also see that the world is multi-cloud. People are using upwards of 9 clouds or more in many cases, and that, in a lot of cases, has to do with this intersection of function and data residency and being able to bring together all of those pieces of where the data needs to be or where the data currently is, and then bring software function to the data is something that we see as critically important. >> Without being too specific in the use of the word binding, today, the idea is you bring your data to a cloud supplier and then, you can run the services of that cloud supplier supplies on that data. Do you and IBM foresee a world in which the customer's going to be able to control their own data and then acquire the services from the cloud and bring it to their data? Is that the direction you think it's going to go? >> Not only do we see that it will be possible, we think that it is possible and we're putting things in market already today that enable people to bring cloud function to their data. The IBM Cloud private offerings and IBM Cloud private for data enable people to, in their environment, where their data resides, bring sophisticated data, warehousing data analytics and AI capabilities. Fundamentally, that process of workload modernization is a set of steps and it starts with data and it starts with modernization of that environment and it matures then into being able to get deep insights through the power of AI on that data. >> Let me ask you one more question. In February, IBM's going to host 30,000+ people in San Francisco. Unbelievable opportunity for networking, learning, and IBM Think. What kind of conversations do you expect that you're going to be having in Think in 2019? >> I think you hit at the heart of the conversations that we're going to be having at Think and our positioning of the hybrid multi-cloud environment. Our other core tenets there are open and open source and keeping up with the rate and pace of open source as an innovation stream, providing choice in how folks are deploying cloud and deploying systems. We also are going to be having conversations around security. That's a core enterprise value proposition and ultimately, management. You want to not just declare that the world is hybrid and multi-cloud, but provide solutions to that and we believe we have strong answers to how to bring these pieces together and enable people to successfully move at the rate and pace of innovation that they need, yet in a secure context, and leverage the ability to deploy cloud capabilities where their data currently is, be that on private or public context. >> Hillery Hunter, CTO and vice president of cloud infrastructure at IBM, thanks for talking to theCUBE here today at the IBM Innovation Day. >> Thank you so much for having me. It was a pleasure. >> And, we will be back momentarily with more conversations at IBM Innovation Day.

>> Narrator: Live from San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> And welcome back once again to theCUBE. We're here live and open in this open-source conference, Red Hat Summit 2018 here in Moscone Center in San Francisco. My name's John Troyer. We are coming close to the end of the day three of Red Hat Summit. Been here, catching all the live coverage on theCUBE.net. Great to have with us: our two guests here from UPS, Innovation Award winners here at the show, gentlemen, welcome. >> Thank you. >> Thank you. >> Mark Falto and Dan Savarese. So, welcome folks. So, we're going to talk about your journey to using OpenShift, how you guys picked it, what you guys stood up, and as we were just kind of, I saw the on-stage story, and as I was just talking to you now before we went live, I'm just so impressed by the time to market, time to value, that you guys were able to achieve. You and your teams. Which, if you think about it is really, the fact that this is a real story, and it's not just a marketing example is really great. We're living, and sometimes I wake up and I say we're living in wonderful times in 2018. So, Dan, kind of set the stage for us. You are a principal infrastructure architect, you're one of the folks that helped bring the system in, you were already Red Hat Linux ... >> Yes we were. >> ... users, but what were you looking at as you were trying to make this decision, and what were some of the drivers to bring OpenShift in-house? >> Well, we knew we wanted to go cloud, but we weren't sure whether it was public or private, so we felt that in order to start the transformation to cloud we should really focus on private. These boundaries to get that up and running, and a way to modernize our applications to be cloud ready. So that was the goal when we set this up. We had a very tight timeline, we had applications that wanted to go cloud, so we made the decision... >> Mark Falto: (mumbles) was knocking at the door. >> Everybody was knocking at the door. Right, so it was a matter of just what did we want to do? Like anything, we viewed a number of different private cloud solutions, and we really liked OpenShift because of it's flexibility, it's open-source capabilities, and the fact that it was... docket containers, which was our container strategy going forward, which we wanted to use. >> Was this the beginning of your container strategy? Had you been using them before? >> No, we hadn't been using them before. We just made the decision, prior to making the cloud decision, that we wanted to go containers and docket with the containers that we wanted to use. >> So, you some sort of evaluation, you say you know, this seems like something worth happening. In the olden days, we'd go off and you'd do some sort of POC, and you'd spend a couple months doing that, and then you'd look at it, and what are the toy projects? >> Dan Savarese: Right, yeah. >> You guys wanted to actions, so can you talk a little bit about that and the timeline there? >> Right, so we made the decision in late fall 2016 to do this. My team runs all the infrastructure, architecture, so we work with the applications to design new architectures for them, and basically we started working with Red Hat on success criteria that we established for the product, and then once we got through that we started having sessions with Red Hat and using collaborative dev ops approach with everybody in your organization who'd be affected by this private cloud we're putting in. So Mark, our info sec folks, our networking folks. We were on a very tight timeline, we had an application wanting to go quickly as possible, and they wanted to be up and running in like the late spring, early summer timeframe, so they didn't give us much time. So, a lot of work and effort into figuring out how we wanted our architects OpenShift for, not only to be operationally successful for us, but from an application perspective. So, it was important we do this in a collaborative manner, and get everybody's input in doing that. >> Yeah, that's something that's going to be interesting to dip into, right, because you can't just turn on speed like that. As I've been kind of jokingly referring to, right, you have to turn into kind of a dev ops in an agile organization. Even at the infrastructure layer. >> [Dan Savarese} Yep. >> So, Mark, within a few months you've got OpenShift up and running. Now you've got to put some apps on it. These are not new apps. You have all your existing portfolios still having to run, but so, yeah, what were you looking at putting up there, and how did you approach that in terms of native practice. >> Our strategy was to take new applications. We're trying to find app teams that we thought had at least a sophisticated enough process that they could take on the automation that we really wanted to drive with the platform as well, right? It was not just containerization, but the transformation in dev process that came with that. So it's get a pipeline in place. Understand how to use Jenkins, how to use the plugins that are necessary to make that happen. You need the right app teams that are ready to take that on. We had an example application as part of our edge initiative called Sipe, which that team we thought was ready to take this on, it was the only way we were really going to meet their timelines, too. So we worked with them for a number of weeks, and not just us, but we also had Red Hat partners helping us too, to freely build out the automation for the pipelines, get an example running for their complete automated pipeline. >> Right, so can you describe a little bit what it does? It's a business line app to help managers do some decision making and planning. >> Yeah, it's a decision assistance application for supervisors at hub facilities where, you know, where you move packages. >> Okay, so real business impact. Before, they had, I don't know what they were... Either papers, or... >> Most of it was manual processes, and it wasn't like the speed to market. The information wasn't real-time, so Sipe was all about driving real-time decisions in the field. >> Right, right, so it must have had an immediate impact, then. So, it sounds like you were up, and then also within a few months of it. >> Yes. Yeah, yeah. I mean, we're able to get at least a pipeline going within weeks for them, and that demonstrates the capacity to get yourself to production, right? And then, they're in production within a number of months after that. A couple of months after that. >> Yeah, that's great, and I'm assuming you'd then be able to revise it and kind of improve the functionality since. That and some other apps. >> Mark Falto: Yep, yep, yeah. >> Was that a big shift for you and your developers, to kind of get to this stance, of frequent releases and a pipeline? >> Yeah, it's a huge process shift, it's a cultural shift for app teams, they have more capability from the infrastructure than they have ever had before. So, they now have tools to deliver much faster than they're used to, so they change their team structures to help us facilitate that. They bring in Red Hat or other consultants to help them backfill their skillsets, so it's big transformation, yeah. >> Nice, nice. Now, I wanted to explore a little bit. One word you hear a lot here: hybrid cloud, multi cloud, we've been hearing that a lot this week. This particular app runs on Prem, right? >> Dan Savarese: Runs on Prem, yes. >> Let's make sure we it right, on PremiSys. >> Dan Savarese: On PremiSys, right. It runs actually, between today at the centers. >> Yeah, I'll get extra bonus points for that. But, as a portfolio that you have to manage, your IT department and infrastructure, UPS does take advantage of different clouds and different code running and different places, as well as sas and everything else, I'm sure. Can you talk a little bit about to portfolio? >> Sure, so we have a wide variety, as companies as large as UPS, you can imagine we have a lot of IT solutions. We leverage all of them to our benefits, so we have past solutions in the cloud, a lot of analytic stuff that we'll do out there, and we also have a lot of sas solutions that we use to do different various works across our organization. So, we are using cloud in multiple ways. Out next journey is hybrid cloud. How do we take OpenShift now, 'cause what we have is a situation where we need a lot of processing power for what we call out peak season, Christmas of course, right, but when we size today on OnPrem we size for that peak season. So, the challenge is for us now is how can we use OnPrem for, say, nine months out of the year, then expand into the cloud for peak season, reduce cost, and then drop that down after we're done with peak season? To really drive us really efficiently from across the spectrum. >> Right, right, right, and obviously OpenShift is going to be a probably key element to that. >> Dan Savarese: It is a key element. It is a key element. >> Yeah. You know, this only took a, this journey was, if you just look at the timeline we just talked about, really only a few months, and it seems like this was kind of a corner-turn for your engineering organization. I mean, is that inaccurate? >> I would say so, both from an infrastructure perspective, the biggest thing when you run a common environment, which we do in OpenShift, in other common environments you have no control over how the applications affect one another. For us, what we like about OpenShift, it gives us that capability, so application 'A' doesn't step on application 'B'. And, I think, for us, it just made our lives a lot easier from an operational perspective for that reason. >> Right, it wasn't about the tool, but the tool helped enable the processes, and then that yielded the time to market and time to value. >> Yeah, and from an app side, building these new architectures really requires containerization. It requires the automations, so we can't attack the proper microservice patterns and practices really without OpenShift as a platform underneath it. It's foundational. >> And I'd like to stress the fact that it really was all of us knew we had to get something done. We all came together. There was no... The silos were merely broken down. We knew we had a mission to get through, we knew had something to get done in a short period of time, and we just came together in such a strong, collaborative way of driving the solution. >> Wow, that's great, and congratulations. Innovation Award here at the show, it's been a great week here at Red Hat Summit. So, Mark Falto, Dan Savarese from UPS. Congrats, and thanks for being here on theCube. >> Well, thank you John. >> All right. Well we are here live in San Francisco. We are finishing up day three. We'll be back after a short break, and all of our live coverage of Red Hat Summit on theCube. (light percussive music)

[Music] [Music] [Music] [Music] [Music] [Music] that will be successful in the 21st century [Music] being open is really important because it comes with a lot of trust the open-source community now has matured so much and that contribution from the community is really driving innovation [Music] but what's really exciting is the change that we've seen in our teams not only the way they collaborate but the way they operate in the way they work [Music] I think idea is everything ideas can change the way you see things open-source is more than a license it's actually a way of operating [Music] ladies and gentlemen please welcome Red Hat president and chief executive officer Jim Whitehurst [Music] all right well welcome to day two at the Red Hat summit I'm amazed to see this many people here at 8:30 in the morning given the number of people I saw pretty late last night out and about so thank you for being here and have to give a shout out speaking of power participation that DJ is was Mike Walker who is our global director of open innovation labs so really enjoyed that this morning was great to have him doing that so hey so day one yesterday we had some phenomenal announcements both around Red Hat products and things that we're doing as well as some great partner announcements which we found exciting I hope they were interesting to you and I hope you had a chance to learn a little more about that and enjoy the breakout sessions that we had yesterday so yesterday was a lot about the what with these announcements and partnerships today I wanted to spin this morning talking a little bit more about the how right how do we actually survive and thrive in this digitally transformed world and to some extent the easy parts identifying the problem we all know that we have to be able to move more quickly we all know that we have to be able to react to change faster and we all know that we need to innovate more effectively all right so the problem is easy but how do you actually go about solving that right the problem is that's not a product that you can buy off the shelf right it is a capability that you have to build and certainly it's technology enabled but it's also depends on process culture a whole bunch of things to figure out how we actually do that and the answer is likely to be different in different organizations with different objective functions and different starting points right so this is a challenge that we all need to feel our way to an answer on and so I want to spend some time today talking about what we've seen in the market and how people are working to address that and it's one of the reasons that the summit this year the theme is ideas worth it lorring to take us back on a little history lesson so two years ago here at Moscone the theme of the summit was the power of participation and then I talked a lot about the power of groups of people working together and participating are able to solve problems much more quickly and much more effectively than individuals or even individual organizations working by themselves and some of the largest problems that we face in technology but more broadly in the world will ultimately only be solved if we effectively participate and work together then last year the theme of the summit was the impact of the individual and we took this concept of participation a bit further and we talked about how participation has to be active right it's a this isn't something where you can be passive that you can sit back you have to be involved because the problem in a more participative type community is that there is no road map right you can't sit back and wait for an edict on high or some central planning or some central authority to tell you what to do you have to take initiative you have to get involved right this is a active participation sport now one of the things that I talked about as part of that was that planning was dead and it was kind of a key my I think my keynote was actually titled planning is dead and the concept was that in a world that's less knowable when we're solving problems in a more organic bottom-up way our ability to effectively plan into the future it's much less than it was in the past and this idea that you're gonna be able to plan for success and then build to it it really is being replaced by a more bottom-up participative approach now aside from my whole strategic planning team kind of being up in arms saying what are you saying planning is dead I have multiple times had people say to me well I get that point but I still need to prepare for the future how do I prepare my organization for the future isn't that planning and so I wanted to spend a couple minutes talk a little more detail about what I meant by that but importantly taking our own advice we spent a lot of time this past year looking around at what our customers are doing because what a better place to learn then from large companies and small companies around the world information technology organizations having to work to solve these problems for their organizations and so our ability to learn from each other take the power of participation an individual initiative that people and organizations have taken there are just so many great learnings this year that I want to get a chance to share I also thought rather than listening to me do that that we could actually highlight some of the people who are doing this and so I do want to spend about five minutes kind of contextualizing what we're going to go through over the next hour or so and some of the lessons learned but then we want to share some real-world stories of how organizations are attacking some of these problems under this how do we be successful in a world of constant change in uncertainty so just going back a little bit more to last year talking about planning was dead when I said planning it's kind of a planning writ large and so that's if you think about the way traditional organizations work to solve problems and ultimately execute you start off planning so what's a position you want to get to in X years and whether that's a competitive strategy in a position of competitive advantage or a certain position you want an organizational function to reach you kind of lay out a plan to get there you then typically a senior leaders or a planning team prescribes the sets of activities and the organization structure and the other components required to get there and then ultimately execution is about driving compliance against that plan and you look at you say well that's all logical right we plan for something we then figure out how we're gonna get there we go execute to get there and you know in a traditional world that was easy and still some of this makes sense I don't say throw out all of this but you have to recognize in a more uncertain volatile world where you can be blindsided by orthogonal competitors coming in and you the term uber eyes you have to recognize that you can't always plan or know what the future is and so if you don't well then what replaces the traditional model or certainly how do you augment the traditional model to be successful in a world that you knows ambiguous well what we've heard from customers and what you'll see examples of this through the course of this morning planning is can be replaced by configuring so you can configure for a constant rate of change without necessarily having to know what that change is this idea of prescription of here's the activities people need to perform and let's lay these out very very crisply job descriptions what organizations are going to do can be replaced by a greater degree of enablement right so this idea of how do you enable people with the knowledge and things that they need to be able to make the right decisions and then ultimately this idea of execution as compliance can be replaced by a greater level of engagement of people across the organization to ultimately be able to react at a faster speed to the changes that happen so just double clicking in each of those for a couple minutes so what I mean by configure for constant change so again we don't know exactly what the change is going to be but we know it's going to happen and last year I talked a little bit about a process solution to that problem I called it that you have to try learn modify and what that model try learn modify was for anybody in the app dev space it was basically taking the principles of agile and DevOps and applying those more broadly to business processes in technology organizations and ultimately organizations broadly this idea of you don't have to know what your ultimate destination is but you can try and experiment you can learn from those things and you can move forward and so that I do think in technology organizations we've seen tremendous progress even over the last year as organizations are adopting agile endeavor and so that still continues to be I think a great way for people to to configure their processes for change but this year we've seen some great examples of organizations taking a different tack to that problem and that's literally building modularity into their structures themselves right actually building the idea that change is going to happen into how you're laying out your technology architectures right we've all seen the reverse of that when you build these optimized systems for you know kind of one environment you kind of flip over two years later what was the optimized system it's now called a legacy system that needs to be migrated that's an optimized system that now has to be moved to a new environment because the world has changed so again you'll see a great example of that in a few minutes here on stage next this concept of enabled double-clicking on that a little bit so much of what we've done in technology over the past few years has been around automation how do we actually replace things that people were doing with technology or augmenting what people are doing with technology and that's incredibly important and that's work that can continue to go forward it needs to happen it's not really what I'm talking about here though enablement in this case it's much more around how do you make sure individuals are getting the context they need how are you making sure that they're getting the information they need how are you making sure they're getting the tools they need to make decisions on the spot so it's less about automating what people are doing and more about how can you better enable people with tools and technology now from a leadership perspective that's around making sure people understand the strategy of the company the context in which they're working in making sure you've set the appropriate values etc etc from a technology perspective that's ensuring that you're building the right systems that allow the right information the right tools at the right time to the right people now to some extent even that might not be hard but when the world is constantly changing that gets to be even harder and I think that's one of the reasons we see a lot of traction and open source to solve these problems to use flexible systems to help enterprises be able to enable their people not just in it today but to be flexible going forward and again we'll see some great examples of that and finally engagement so again if execution can't be around driving compliance to a plan because you no longer have this kind of Cris plan well what do leaders do how do organizations operate and so you know I'll broadly use the term engagement several of our customers have used this term and this is really saying well how do you engage your people in real-time to make the right decisions how do you accelerate a pace of cadence how do you operate at a different speed so you can react to change and take advantage of opportunities as they arise and everywhere we look IT is a key enabler of this right in the past IT was often seen as an inhibitor to this because the IT systems move slower than the business might want to move but we are seeing with some of these new technologies that literally IT is becoming the enabler and driving the pace of change back on to the business and you'll again see some great examples of that as well so again rather than listen to me sit here and theoretically talk about these things or refer to what we've seen others doing I thought it'd be much more interesting to bring some of our partners and our customers up here to specifically talk about what they're doing so I'm really excited to have a great group of customers who have agreed to stand in front of 7,500 people or however many here this morning and talk a little bit more about what they're doing so really excited to have them here and really appreciate all them agreeing to be a part of this and so to start I want to start with tee systems we have the CEO of tee systems here and I think this is a great story because they're really two parts to it right because he has two perspectives one is as the CEO of a global company itself having to navigate its way through digital disruption and as a global cloud service provider obviously helping its customers through this same type of change so I'm really thrilled to have a del hasta li join me on stage to talk a little bit about T systems and what they're doing and what we're doing jointly together so Adelle [Music] Jim took to see you Adele thank you for being here you for having me please join me I love to DJ when that fantastic we may have to hire him no more events for events where's well employed he's well employed though here that team do not give him mics activation it's great to have you here really do appreciate it well you're the CEO of a large organization that's going through this disruption in the same way we are I'd love to hear a little bit how for your company you're thinking about you know navigating this change that we're going through great well you know key systems as an ICT service provider we've been around for decades I'm not different to many of our clients we had to change the whole disruption of the cloud and digitization and new skills and new capability and agility it's something we had to face as well so over the last five years and especially in the last three years we invested heavily invested over a billion euros in building new capabilities building new offerings new infrastructures to support our clients so to be very disruptive for us as well and so and then with your customers themselves they're going through this set of change and you're working to help them how are you working to help enable your your customers as they're going through this change well you know all of them you know in this journey of changing the way they run their business leveraging IT much more to drive business results digitization and they're all looking for new skills new ideas they're looking for platforms that take them away from traditional waterfall development that takes a year or a year and a half before they see any results to processes and ways of bringing applications in a week in a month etcetera so it's it's we are part of that journey with them helping them for that and speaking of that I know we're working together and to help our joint customers with that can you talk a little bit more about what we're doing together sure well you know our relationship goes back years and years with with the Enterprise Linux but over the last few years we've invested heavily in OpenShift and OpenStack to build peope as layers to build you know flexible infrastructure for our clients and we've been working with you we tested many different technology in the marketplace and been more successful with Red Hat and the stack there and I'll give you an applique an example several large European car manufacturers who have connected cars now as a given have been accelerating the applications that needed to be in the car and in the past it took them years if not you know scores to get an application into the car and today we're using open shift as the past layer to develop to enable these DevOps for these companies and they bring applications in less than a month and it's a huge change in the dynamics of the competitiveness in the marketplace and we rely on your team and in helping us drive that capability to our clients yeah do you find it fascinating so many of the stories that you hear and that we've talked about with with our customers is this need for speed and this ability to accelerate and enable a greater degree of innovation by simply accelerating what what we're seeing with our customers absolutely with that plus you know the speed is important agility is really critical but doing it securely doing it doing it in a way that is not gonna destabilize the you know the broader ecosystem is really critical and things like GDP are which is a new security standard in Europe is something that a lot of our customers worry about they need help with and we're one of the partners that know what that really is all about and how to navigate within that and use not prevent them from using the new technologies yeah I will say it isn't just the speed of the external but the security and the regulation especially GDR we have spent an hour on that with our board this week there you go he said well thank you so much for being here really to appreciate the work that we're doing together and look forward to continued same here thank you thank you [Applause] we've had a great partnership with tea systems over the years and we've really taken it to the next level and what's really exciting about that is you know we've moved beyond just helping kind of host systems for our customers we really are jointly enabling their success and it's really exciting and we're really excited about what we're able to to jointly accomplish so next i'm really excited that we have our innovation award winners here and we'll have on stage with us our innovation award winners this year our BBVA dnm IAG lasat Lufthansa Technik and UPS and yet they're all working in one for specific technology initiatives that they're doing that really really stand out and are really really exciting you'll have a chance to learn a lot more about those through the course of the event over the next couple of days but in this context what I found fascinating is they were each addressing a different point of this configure enable engage and I thought it would be really great for you all to hear about how they're experimenting and working to solve these problems you know real-time large organizations you know happening now let's start with the video to see what they think about when they think about innovation I define innovation is something that's changing the model changing the way of thinking not just a step change improvement not just making something better but actually taking a look at what already exists and then putting them together in new and exciting lives innovation is about to build something nobody has done before historically we had a statement that business drives technology we flip that equation around an IT is now demonstrating to the business at power of technology innovation desde el punto de vista de la tecnología supone salir de plataform as proprietary as ADA Madero cloud basado an open source it's a possibility the open source que no parameter no sir Kamala and I think way that for me open-source stands for flexibility speed security the community and that contribution from the community is really driving innovation innovation at a pace that I don't think our one individual organization could actually do ourselves right so first I'd like to talk with BBVA I love this story because as you know Financial Services is going through a massive set of transformations and BBVA really is at the leading edge of thinking about how to deploy a hybrid cloud strategy and kind of modular layered architecture to be successful regardless of what happens in the future so with that I'd like to welcome on stage Jose Maria Rosetta from BBVA [Music] thank you for being here and congratulations on your innovation award it's been a pleasure to be here with you it's great to have you hi everybody so Josemaria for those who might not be familiar with BBVA can you give us a little bit of background on your company yeah a brief description BBVA is is a bank as a financial institution with diversified business model and that provides well financial services to more than 73 million of customers in more than 20 countries great and I know we've worked with you for a long time so we appreciate that the partnership with you so I thought I'd start with a really easy question for you how will blockchain you know impact financial services in the next five years I've gotten no idea but if someone knows the answer I've got a job for him for him up a pretty good job indeed you know oh all right well let me go a little easier then so how will the global payments industry change in the next you know four or five years five years well I think you need a a Weezer well I tried to make my best prediction means that in five years just probably will be five years older good answer I like that I always abstract up I hope so I hope so yah-yah-yah hope so good point so you know immediately that's the obvious question you have a massive technology infrastructure is a global bank how do you prepare yourself to enable the organization to be successful when you really don't know what the future is gonna be well global banks and wealth BBBS a global gam Bank a certain component foundations you know today I would like to talk about risk and efficiency so World Bank's deal with risk with the market great the operational reputational risk and so on so risk control is part of all or DNA you know and when you've got millions of customers you know efficiency efficiency is a must so I think there's no problem with all these foundations they problem the problem analyze the problems appears when when banks translate these foundations is valued into technology so risk control or risk management avoid risk usually means by the most expensive proprietary technology in the market you know from one of the biggest software companies in the world you know so probably all of you there are so those people in the room were glad to hear you say that yeah probably my guess the name of those companies around San Francisco most of them and efficiency usually means a savory business unit as every department or country has his own specific needs by a specific solution for them so imagine yourself working in a data center full of silos with many different Hardware operating systems different languages and complex interfaces to communicate among them you know not always documented what really never documented so your life your life in is not easy you know in this scenario are well there's no room for innovation so what's been or or strategy be BES ready to move forward in this new digital world well we've chosen a different approach which is quite simple is to replace all local proprietary system by a global platform based on on open source with three main goals you know the first one is reduce the average transaction cost to one-third the second one is increase or developers productivity five times you know and the third is enable or delete the business be able to deliver solutions of three times faster so you're not quite easy Wow and everything with the same reliability as on security standards as we've got today Wow that is an extraordinary set of objectives and I will say their world on the path of making that successful which is just amazing yeah okay this is a long journey sometimes a tough journey you know to be honest so we decided to partnership with the with the best companies in there in the world and world record we think rate cut is one of these companies so we think or your values and your knowledge is critical for BBVA and well as I mentioned before our collaboration started some time ago you know and just an example in today in BBVA a Spain being one of the biggest banks in in the country you know and using red hat technology of course our firm and fronting architecture you know for mobile and internet channels runs the ninety five percent of our customers request this is approximately 3,000 requests per second and our back in architecture execute 70 millions of business transactions a day this is almost a 50% of total online transactions executed in the country so it's all running yes running I hope so you check for you came on stage it's I'll be flying you know okay good there's no wood up here to knock on it's been a really great partnership it's been a pleasure yeah thank you so much for being here thank you thank you [Applause] I do love that story because again so much of what we talk about when we when we talk about preparing for digital is a processed solution and again things like agile and DevOps and modular izing components of work but this idea of thinking about platforms broadly and how they can run anywhere and actually delivering it delivering at a scale it's just a phenomenal project and experience and in the progress they've made it's a great team so next up we have two organizations that have done an exceptional job of enabling their people with the right information and the tools they need to be successful you know in both of these cases these are organizations who are under constant change and so leveraging the power of open-source to help them build these tools to enable and you'll see it the size and the scale of these in two very very different contexts it's great to see and so I'd like to welcome on stage Oh smart alza' with dnm and David Abraham's with IAG [Music] Oh smart welcome thank you so much for being here Dave great to see you thank you appreciate you being here and congratulations to you both on winning the Innovation Awards thank you so Omar I really found your story fascinating and how you're able to enable your people with data which is just significantly accelerated the pace with which they can make decisions and accelerate your ability to to act could you tell us a little more about the project and then what you're doing Jim and Tina when the muchisimas gracias por ever say interesado pono true projecto [Music] encargado registry controller las entradas a leda's persona por la Frontera argentina yo sé de dos siento treinta siete puestos de contrôle tienen lo largo de la Frontera tanto area the restreamer it EEMA e if looool in dilute ammonia shame or cinta me Jonas the tránsito sacra he trod on in another Fronteras dingus idea idea de la Magneto la cual estamos hablando la Frontera cantina tienen extension the kin same in kilo metros esto es el gada mint a maje or allege Estancia kaeun a poor carretera a la co de mexico con el akka a direction emulation s tambien o torgul premios de de residencia control a la permanencia de los rancheros en argentina pero básicamente nuestra área es prevenir que persona que estén in curie end o en delito transnational tipo pero remo trata de personas tráfico de armas sunday muy gravis SI yo que nosotros a Samos es para venir aquí es uno para que nadie meso and he saw some vetoes pueden entrada al Argentine establecer see not replaceable Terry Antone see koalas jenner are Yap liquor make animo para que - no Korra NL Angelo Millie see sighs a partir de la o doc mil DC says turmoil affirm a decision de cambiar de un sistema reactive Oh foreign c'est un sistema predict TiVo say Previn TiVo yes I don't empezamos s target area con el con las Judah in appreciable de la gente del canto la tarea el desafío era integra todo es desconocido vasa de datos propias estructura Radha's no instruct Radha's propias del organ is mo y de otros Organa Mo's del estado y tambien integral akan el mundo si si si como cinta yo el lo controls the Interpol o empezamos @n información anticipable pasajeros a travell CT ma p tambien intent ahmo's controller latrans Sybilla de en los happiness a través de en er de todo esto fue possible otra vez de la generation dune irreparable econo penchev y la virtualization de datos si esto fue fundamental por que entra moseyin una schema se en un modelo de intelligent a artificial eden machine learning KD o por resultado jimmy esto que todas esas de datos integral as tanto Nacional como Internacional A's le provision a nuestros nuestras an Aleta que antes del don't build Isis ice tenían que buscar say información integral Adel diferentes sistema z-- c yatin de Chivo manuals tarde Ando auras odious en algunos casos a tener toda la información consolidate a integra dope or poor pasajero en tiempo real esto que hizo mejor Oh el tiempo y la calidad de la toma de decisiones de nuestros durante la gente / dueño and affinity regime de lo que se trata esto es simplemente mejor our la calidad de vida de atras de mettre personas SI y meet our que el delito perform a trois Natura from Dana's Argentine sigue siendo en favor de esto SI temes uno de los países mess Alberto's Allah immigration en Latin America yah hora con una plataforma mas segunda first of all I want to thank you for the interest is played for our project the National migration administration or diem records the entry and exit of people on the Argentine territory it grants residents permits to foreigners who wish to live in our country through 237 entry points land air border sea and river ways Jim dnm registered over 80 million transits throughout last year Argentine borders cover about 15,000 kilometers just our just to give you an idea of the magnitude of our borders this is greater than the distance on a highway between Mexico City and Alaska our department applies the mechanisms that prevent the entry and residents of people involved in crimes like terrorism trafficking of persons weapons drugs and others in 2016 we shifted to a more preventive and predictive paradigm that is how Sam's the system for migration analysis was created with red hats great assistance and support this allowed us to tackle the challenge of integrating multiple and varied issues legal issues police databases national and international security organizations like Interpol API advanced passenger information and PNR passenger name record this involved starting private cloud with OpenShift Rev data virtualization cloud forms and fuse that were the basis to develop Sam and implementing machine learning models and artificial intelligence our analysts consulted a number of systems and other manual files before 2016 4 days for each person entering or leaving the country so this has allowed us to optimize our decisions making them in real time each time Sam is consulted it processes patterns of over two billion data entries Sam's aim is to improve the quality of life of our citizens and visitors making sure that crime doesn't pierce our borders in an environment of analytic evolution and constant improvement in essence Sam contributes toward Argentina being one of the leaders in Latin America in terms of immigration with our new system great thank you and and so Dave tell us a little more about the insurance industry and the challenges in the EU face yeah sure so you know in the insurance industry it's a it's been a bit sort of insulated from a lot of major change in disruption just purely from the fact that it's highly regulated and the cost of so that the barrier to entry is quite high in fact if you think about insurance you know you have to have capital reserves to protect against those major events like floods bush fires and so on but the whole thing is a lot of change there's come in a really rapid pace I'm also in the areas of customer expectations you know customers and now looking and expecting for the same levels of flexibility and convenience that they would experience with more modern and new startups they're expecting out of the older institutions like banks and insurance companies like us so definitely expecting the industry to to be a lot more adaptable and to better meet their needs I think the other aspect of it really is in the data the data area where I think that the donor is now creating a much more significant connection between organizations in a car summers especially when you think about the level of devices that are now enabled and the sheer growth of data that's that that's growing at exponential rates so so that the impact then is that the systems that we used to rely on are the technology we used to rely on to be able to handle that kind of growth no longer keeps up and is able to to you know build for the future so we need to sort of change that so what I G's really doing is transform transforming the organization to become a lot more efficient focus more on customers and and really set ourselves up to be agile and adaptive and so ya know as part of your Innovation Award that the specific set of projects you tied a huge amount of different disparate systems together and with M&A and other you have a lot to do there to you tell us a little more about kind of how you're able to better respond to customer needs by being able to do that yeah no you're right so we've we've we're nearly a hundred year old company that's grown from lots of merger and acquisition and just as a result of that that means that data's been sort of spread out and fragmented across multiple brands and multiple products and so the number one sort of issue and problem that we were hearing was that it was too hard to get access to data and it's highly complicated which is not great from a company from our perspective really because because we are a data company right that's what we do we we collect data about people what they what's important to them what they value and the environment in which they live so that we can understand that risk and better manage and protect those people so what we're doing is we're trying to make and what we have been doing is making data more open and accessible and and by that I mean making data more of easily available for people to use it to make decisions in their day-to-day activity and to do that what we've done is built a single data platform across the group that unifies the data into a single source of truth that we can then build on top of that single views of customers for example that puts the right information into the into the hands of the people that need it the most and so now why does open source play such a big part in doing that I know there are a lot of different solutions that could get you there sure well firstly I think I've been sauce has been k2 these and really it's been key because we've basically started started from scratch to build this this new next-generation data platform based on entirely open-source you know using great components like Kafka and Postgres and airflow and and and and and then fundamentally building on top of red Red Hat OpenStack right to power all that and they give us the flexibility that we need to be able to make things happen much faster for example we were just talking to the pivotal guys earlier this week here and some of the stuff that we're doing they're they're things quite interesting innovative writes even sort of maybe first in the world where we've taken the older sort of appliance and dedicated sort of massive parallel processing unit and ported that over onto red Red Hat OpenStack right which is now giving us a lot more flexibility for scale in a much more efficient way but you're right though that we've come from in the past a more traditional approach to to using vendor based technology right which was good back then when you know technology solutions could last for around 10 years or so on and and that was fine but now that we need to move much faster we've had to rethink that and and so our focus has been on using you know more commoditized open source technology built by communities to give us that adaptability and sort of remove the locking in there any entrenchment of technology so that's really helped us but but I think that the last point that's been really critical to us is is answering that that concern and question about ongoing support and maintenance right so you know in a regular environment the regulator is really concerned about anything that could fundamentally impact business operation and and so the question is always about what happens when something goes wrong who's going to be there to support you which is where the value of the the partnership we have with Red Hat has really come into its own right and what what it's done is is it's actually giving us the best of both worlds a means that we can we can leverage and use and and and you know take some of the technology that's being developed by great communities in the open source way but also partner with a trusted partner in red had to say you know they're going to stand behind that community and provide that support when we needed the most so that's been the kind of the real value out of that partnership okay well I appreciate I love the story it's how do you move quickly leverage the power community but do it in a safe secure way and I love the idea of your literally empowering people with machine learning and AI at the moment when they need it it's just an incredible story so thank you so much for being here appreciate it thank you [Applause] you know again you see in these the the importance of enabling people with data and in an old-world was so much data was created with a system in mind versus data is a separate asset that needs to be available real time to anyone is a theme we hear over and over and over again and so you know really looking at open source solutions that allow that flexibility and keep data from getting locked into proprietary silos you know is a theme that we've I've heard over and over over the past year with many of our customers so I love logistics I'm a geek that way I come from that background in the past and I know that running large complex operations requires flawless execution and that requires great data and we have two great examples today around how to engage own organizations in new and more effective ways in the case of lufthansa technik literally IT became the business so it wasn't enabling the business it became the business offering and importantly went from idea to delivery to customers in a hundred days and so this theme of speed and the importance of speed it's a it's a great story you'll hear more about and then also at UPS UPS again I talked a little earlier about IT used to be kind of the long pole in the tent the thing that was slow moving because of the technology but UPS is showing that IT can actually drive the business and the cadence of business even faster by demonstrating the power and potential of technology to engage in this case hundreds of thousands of people to make decisions real-time in the face of obviously constant change around weather mechanicals and all the different things that can happen in a large logistics operation like that so I'd like to welcome on stage to be us more from Lufthansa Technik and Nick Castillo from ups to be us welcome thank you for being here Nick thank you thank you Jim and congratulations on your Innovation Awards oh thank you it's a great honor so to be us let's start with you can you tell us a little bit more about what a viet are is yeah avatars are a digital platform offering features like aircraft condition analytics reliability management and predictive maintenance and it helps airlines worldwide to digitize and improve their operations so all of the features work and can be used separately or generate even more where you burn combined and finally we decided to set up a viet as an open platform that means that we avoid the whole aviation industry to join the community and develop ideas on our platform and to be as one of things i found really fascinating about this is that you had a mandate to do this at a hundred days and you ultimately delivered on it you tell us a little bit about that i mean nothing in aviation moves that fast yeah that's been a big challenge so in the beginning of our story the Lufthansa bot asked us to develop somehow digital to win of an aircraft within just hundred days and to deliver something of value within 100 days means you cannot spend much time and producing specifications in terms of paper etc so for us it was pretty clear that we should go for an angel approach and immediately start and developing ideas so we put the best experts we know just in one room and let them start to work and on day 2 I think we already had the first scribbles for the UI on day 5 we wrote the first lines of code and we were able to do that because it has been a major advantage for us to already have four technologies taken place it's based on open source and especially rated solutions because we did not have to waste any time setting up the infrastructure and since we wanted to get feedback very fast we were certainly visited an airline from the Lufthansa group already on day 30 and showed them the first results and got a lot of feedback and because from the very beginning customer centricity has been an important aspect for us and changing the direction based on customer feedback has become quite normal for us over time yeah it's an interesting story not only engaging the people internally but be able to engage with a with that with a launch customer like that and get feedback along the way as it's great thing how is it going overall since launch yeah since the launch last year in April we generated much interest in the industry as well from Airlines as from competitors and in the following month we focused on a few Airlines which had been open minded and already advanced in digital activities and we've got a lot of feedback by working with them and we're able to improve our products by developing new features for example we learned that data integration can become quite complex in the industry and therefore we developed a new feature called quick boarding allowing Airlines to integrate into the via table platform within one day using a self-service so and currently we're heading for the next steps beyond predictive maintenance working on process automation and prescriptive prescriptive maintenance because we believe prediction without fulfillment still isn't enough it really is a great example of even once you're out there quickly continuing to innovate change react it's great to see so Nick I mean we all know ups I'm still always blown away by the size and scale of the company and the logistics operations that you run you tell us a little more about the project and what we're doing together yeah sure Jim and you know first of all I think I didn't get the sportcoat memo I think I'm the first one up here today with a sport coat but you know first on you know on behalf of the 430,000 ups was around the world and our just world-class talented team of 5,000 IT professionals I have to tell you we're humbled to be one of this year's red hat Innovation Award recipients so we really appreciate that you know as a global logistics provider we deliver about 20 million packages each day and we've got a portfolio of technologies both operational and customer tech and another customer facing side the power what we call the UPS smart logistics network and I gotta tell you innovations in our DNA technology is at the core of everything we do you know from the ever familiar first and industry mobile platform that a lot of you see when you get delivered a package which we call the diad which believe it or not we delivered in 1992 my choice a data-driven solution that drives over 40 million of our my choice customers I'm whatever you know what this is great he loves logistics he's a my choice customer you could be one too by the way there's a free app in the App Store but it provides unmatched visibility and really controls that last mile delivery experience so now today we're gonna talk about the solution that we're recognized for which is called site which is part of a much greater platform that we call edge which is transforming how our package delivery teams operate providing them real-time insights into our operations you know this allows them to make decisions based on data from 32 disparate data sources and these insights help us to optimize our operations but more importantly they help us improve the delivery experience for our customers just like you Jim you know on the on the back end is Big Data and it's on a large scale our systems are crunching billions of events to render those insights on an easy-to-use mobile platform in real time I got to tell you placing that information in our operators hands makes ups agile and being agile being able to react to changing conditions as you know is the name of the game in logistics now we built edge in our private cloud where Red Hat technologies play a very important role as part of our overage overarching cloud strategy and our migration to agile and DevOps so it's it's amazing it's amazing the size and scale so so you have this technology vision around engaging people in a more effect way those are my word not yours but but I'd be at that's how it certainly feels and so tell us a little more about how that enables the hundreds of thousands people to make better decisions every day yep so you know we're a people company and the edge platform is really the latest in a series of solutions to really empower our people and really power that smart logistics network you know we've been deploying technology believe it or not since we founded the company in 1907 we'll be a hundred and eleven years old this August it's just a phenomenal story now prior to edge and specifically the syphon ishutin firm ation from a number of disparate systems and reports they then need to manually look across these various data sources and and frankly it was inefficient and prone to inaccuracy and it wasn't really real-time at all now edge consumes data as I mentioned earlier from 32 disparate systems it allows our operators to make decisions on staffing equipment the flow of packages through the buildings in real time the ability to give our people on the ground the most up-to-date data allows them to make informed decisions now that's incredibly empowering because not only are they influencing their local operations but frankly they're influencing the entire global network it's truly extraordinary and so why open source and open shift in particular as part of that solution yeah you know so as I mentioned Red Hat and Red Hat technology you know specifically open shift there's really core to our cloud strategy and to our DevOps strategy the tools and environments that we've partnered with Red Hat to put in place truly are foundational and they've fundamentally changed the way we develop and deploy our systems you know I heard Jose talk earlier you know we had complex solutions that used to take 12 to 18 months to develop and deliver to market today we deliver those same solutions same level of complexity in months and even weeks now openshift enables us to container raise our workloads that run in our private cloud during normal operating periods but as we scale our business during our holiday peak season which is a very sure window about five weeks during the year last year as a matter of fact we delivered seven hundred and sixty-two million packages in that small window and our transactions our systems they just spiked dramatically during that period we think that having open shift will allow us in those peak periods to seamlessly move workloads to the public cloud so we can take advantage of burst capacity economically when needed and I have to tell you having this flexibility I think is key because you know ultimately it's going to allow us to react quickly to customer demands when needed dial back capacity when we don't need that capacity and I have to say it's a really great story of UPS and red hat working you together it really is a great story is just amazing again the size and scope but both stories here a lot speed speed speed getting to market quickly being able to try things it's great lessons learned for all of us the importance of being able to operate at a fundamentally different clock speed so thank you all for being here very much appreciated congratulate thank you [Applause] [Music] alright so while it's great to hear from our Innovation Award winners and it should be no surprise that they're leading and experimenting in some really interesting areas its scale so I hope that you got a chance to learn something from these interviews you'll have an opportunity to learn more about them you'll also have an opportunity to vote on the innovator of the year you can do that on the Red Hat summit mobile app or on the Red Hat Innovation Awards homepage you can learn even more about their stories and you'll have a chance to vote and I'll be back tomorrow to announce the the summit winner so next I like to spend a few minutes on talking about how Red Hat is working to catalyze our customers efforts Marko bill Peter our senior vice president of customer experience and engagement and John Alessio our vice president of global services will both describe areas in how we are working to configure our own organization to effectively engage with our customers to use open source to help drive their success so with that I'd like to welcome marquel on stage [Music] good morning good morning thank you Jim so I want to spend a few minutes to talk about how we are configured how we are configured towards your success how we enable internally as well to work towards your success and actually engage as well you know Paul yesterday talked about the open source culture and our open source development net model you know there's a lot of attributes that we have like transparency meritocracy collaboration those are the key of our culture they made RedHat what it is today and what it will be in the future but we also added our passion for customer success to that let me tell you this is kind of the configuration from a cultural perspective let me tell you a little bit on what that means so if you heard the name my organization is customer experience and engagement right in the past we talked a lot about support it's an important part of the Red Hat right and how we are configured we are configured probably very uniquely in the industry we put support together we have product security in there we add a documentation we add a quality engineering into an organization you think there's like wow why are they doing it we're also running actually the IT team for actually the product teams why are we doing that now you can imagine right we want to go through what you see as well right and I'll give you a few examples on how what's coming out of this configuration we invest more and more in testing integration and use cases which you are applying so you can see it between the support team experiencing a lot what you do and actually changing our test structure that makes a lot of sense we are investing more and more testing outside the boundaries so not exactly how things must fall by product management or engineering but also how does it really run in an environment that you operate we run complex setups internally right taking openshift putting in OpenStack using software-defined storage underneath managing it with cloud forms managing it if inside we do that we want to see how that works right we are reshaping documentation console to kind of help you better instead of just documenting features and knobs as in how can how do you want to achieve things now part of this is the configuration that are the big part of the configuration is the voice of the customer to listen to what you say I've been here at Red Hat a few years and one of my passion has always been really hearing from customers how they do it I travel constantly in the world and meet with customers because I want to know what is really going on we use channels like support we use channels like getting from salespeople the interaction from customers we do surveys we do you know we interact with our people to really hear what you do what we also do what maybe not many know and it's also very unique in the industry we have a webpage called you asked reacted we show very transparently you told us this is an area for improvement and it's not just in support it's across the company right build us a better web store build us this we're very transparent about Hades improvements we want to do with you now if you want to be part of the process today go to the feedback zone on the next floor down and talk to my team I might be there as well hit me up we want to hear the feedback this is how we talk about configuration of the organization how we are configured let me go to let me go to another part which is innovation innovation every day and that in my opinion the enable section right we gotta constantly innovate ourselves how do we work with you how do we actually provide better value how do we provide faster responses in support this is what we would I say is is our you know commitment to innovation which is the enabling that Jim talked about and I give you a few examples which I'm really happy and it kind of shows the open source culture at Red Hat our commitment is for innovation I'll give you good example right if you have a few thousand engineers and you empower them you kind of set the business framework as hey this is an area we got to do something you get a lot of good IDs you get a lot of IDs and you got a shape an inter an area that hey this is really something that brings now a few years ago we kind of said or I say is like based on a lot of feedback is we got to get more and more proactive if you customers and so I shaped my team and and I shaped it around how can we be more proactive it started very simple as in like from kbase articles or knowledgebase articles in getting started guys then we started a a tool that we put out called labs you've probably seen them if you're on the technical side really taking small applications out for you to kind of validate is this configured correctly stat configure there was the start then out of that the ideas came and they took different turns and one of the turns that we came out was right at insights that we launched a few years ago and did you see the demo yesterday that in Paul's keynote that they showed how something was broken with one the data centers how it was applied to fix and how has changed this is how innovation really came from the ground up from the support side and turned into something really a being a cornerstone of our strategy and we're keeping it married from the day to day work right you don't want to separate this you want to actually keep that the data that's coming from the support goes in that because that's the power that we saw yesterday in the demo now innovation doesn't stop when you set the challenge so we did the labs we did the insights we just launched a solution engine called solution engine another thing that came out of that challenge is in how do we break complex issues down that it's easier for you to find a solution quicker it's one example but we're also experimenting with AI so insights uses AI as you probably heard yesterday we also use it internally to actually drive faster resolution we did in one case with a a our I bought basically that we get to 25% faster resolution on challenges that you have the beauty for you obviously it's well this is much faster 10% of all our support cases today are supported and assisted by an AI now I'll give you another example of just trying to tell you the innovation that comes out if you configure and enable the team correctly kbase articles are knowledgebase articles we q8 thousands and thousands every year and then I get feedback as and while they're good but they're in English as you can tell my English is perfect so it's not no issue for that but for many of you is maybe like even here even I read it in Japanese so we actually did machine translation because it's too many that we can do manually the using machine translation I can tell it's a funny example two weeks ago I tried it I tried something from English to German I looked at it the German looked really bad I went back but the English was bad so it really translates one to one actually what it does but it's really cool this is innovation that you can apply and the team actually worked on this and really proud on that now the real innovation there is not these tools the real innovation is that you can actually shape it in a way that the innovation comes that you empower the people that's the configure and enable and what I think is all it's important this don't reinvent the plumbing don't start from scratch use systems like containers on open shift to actually build the innovation in a smaller way without reinventing the plumbing you save a lot of issues on security a lot of issues on reinventing the wheel focus on that that's what we do as well if you want to hear more details again go in the second floor now let's talk about the engage that Jim mentioned before what I translate that engage is actually engaging you as a customer towards your success now what does commitment to success really mean and I want to reflect on that on a traditional IT company shows up with you talk the salesperson solution architect works with you consulting implements solution it comes over to support and trust me in a very traditional way the support guy has no clue what actually was sold early on it's what happens right and this is actually I think that red had better that we're not so silent we don't show our internal silos or internal organization that much today we engage in a way it doesn't matter from which team it comes we have a better flow than that you deserve how the sausage is made but we can never forget what was your business objective early on now how is Red Hat different in this and we are very strong in my opinion you might disagree but we are very strong in a virtual accounting right really putting you in the middle and actually having a solution architect work directly with support or consulting involved and driving that together you can also help us in actually really embracing that model if that's also other partners or system integrators integrate put yourself in the middle be around that's how we want to make sure that we don't lose sight of the original business problem trust me reducing the hierarchy or getting rid of hierarchy and bureaucracy goes a long way now this is how we configured this is how we engage and this is how we are committed to your success with that I'm going to introduce you to John Alessio that talks more about some of the innovation done with customers thank you [Music] good morning I'm John Alessio I'm the vice president of Global Services and I'm delighted to be with you here today I'd like to talk to you about a couple of things as it relates to what we've been doing since the last summit in the services organization at the core of everything we did it's very similar to what Marco talked to you about our number one priority is driving our customer success with red hat technology and as you see here on the screen we have a number of different offerings and capabilities all the way from training certification open innovation labs consulting really pairing those capabilities together with what you just heard from Marco in the support or cee organization really that's the journey you all go through from the beginning of discovering what your business challenge is all the way through designing those solutions and deploying them with red hat now the highlight like to highlight a few things of what we've been up to over the last year so if I start with the training and certification team they've been very busy over the last year really updating enhancing our curriculum if you haven't stopped by the booth there's a preview for new capability around our learning community which is a new way of learning and really driving that enable meant in the community because 70% of what you need to know you learned from your peers and so it's a very key part of our learning strategy and in fact we take customer satisfaction with our training and certification business very seriously we survey all of our students coming out of training 93% of our students tell us they're better prepared because of red hat training and certification after Weeds they've completed the course we've updated the courses and we've trained well over a hundred and fifty thousand people over the last two years so it's a very very key part of our strategy and that combined with innovation labs and the consulting operation really drive that overall journey now we've been equally busy in enhancing the system of enablement and support for our business partners another very very key initiative is building out the ecosystem we've enhanced our open platform which is online partner enablement network we've added new capability and in fact much of the training and enablement that we do for our internal consultants our deal is delivered through the open platform now what I'm really impressed with and thankful for our partners is how they are consuming and leveraging this material we train and enable for sales for pre-sales and for delivery and we're up over 70% year in year in our partners that are enabled on RedHat technology let's give our business partners a round of applause now one of our offerings Red Hat open innovation labs I'd like to talk a bit more about and take you through a case study open innovation labs was created two years ago it's really there to help you on your journey in adopting open source technology it's an immersive experience where your team will work side-by-side with Red Hatters to really propel your journey forward in adopting open source technology and in fact we've been very busy since the summit in Boston as you'll see coming up on the screen we've completed dozens of engagements leveraging our methods tools and processes for open innovation labs as you can see we've worked with large and small accounts in fact if you remember summit last year we had a European customer easier AG on stage which was a startup and we worked with them at the very beginning of their business to create capabilities in a very short four-week engagement but over the last year we've also worked with very large customers such as Optim and Delta Airlines here in North America as well as Motability operations in the European arena one of the accounts I want to spend a little bit more time on is Heritage Bank heritage Bank is a community owned bank in Toowoomba Australia their challenge was not just on creating new innovative technology but their challenge was also around cultural transformation how to get people to work together across the silos within their organization we worked with them at all levels of the organization to create a new capability the first engagement went so well that they asked us to come in into a second engagement so I'd like to do now is run a video with Peter lock the chief executive officer of Heritage Bank so he can take you through their experience Heritage Bank is one of the country's oldest financial institutions we have to be smarter we have to be more innovative we have to be more agile we had to change we had to find people to help us make that change the Red Hat lab is the only one that truly helps drive that change with a business problem the change within the team is very visible from the start to now we've gone from being separated to very single goal minded seeing people that I only ever seen before in their cubicles in the room made me smile programmers in their thinking I'm now understanding how the whole process fits together the productivity of IT will change and that is good for our business that's really the value that were looking for the Red Hat innovation labs for us were a really great experience I'm not interested in running an organization I'm interested in making a great organization to say I was pleasantly surprised by it is an understatement I was delighted I love the quote I was delighted makes my heart warm every time I see that video you know since we were at summit for those of you who are with us in Boston some of you went on our hardhat tours we've opened three physical facilities here at Red Hat where we can conduct red head open Innovation Lab engagements Singapore London and Boston were all opened within the last physical year and in fact our site in Boston is paired with our world-class executive briefing center as well so if you haven't been there please do check it out I'd like to now talk to you a bit about a very special engagement that we just recently completed we just recently completed an engagement with UNICEF the United Nations Children's Fund and the the purpose behind this engagement was really to help UNICEF create an open-source platform that marries big data with social good the idea is UNICEF needs to be better prepared to respond to emergency situations and as you can imagine emergency situations are by nature unpredictable you can't really plan for them they can happen anytime anywhere and so we worked with them on a project that we called school mapping and the idea was to provide more insights so that when emergency situations arise UNICEF could do a much better job in helping the children in the region and so we leveraged our Red Hat open innovation lab methods tools processes that you've heard about just like we did at Heritage Bank and the other accounts I mentioned but then we also leveraged Red Hat software technologies so we leveraged OpenShift container platform we leveraged ansible automation we helped the client with a more agile development approach so they could have releases much more frequently and continue to update this over time we created a continuous integration continuous deployment pipeline we worked on containers and container in the application etc with that we've been able to provide a platform that is going to allow for their growth to better respond to these emergency situations let's watch a short video on UNICEF mission of UNICEF innovation is to apply technology to the world's most pressing problems facing children data is changing the landscape of what we do at UNICEF this means that we can figure out what's happening now on the ground who it's happening to and actually respond to it in much more of a real-time manner than we used to be able to do we love working with open source communities because of their commitment that we should be doing good for the world we're actually with red hat building a sandbox where universities or other researchers or data scientists can connect and help us with our work if you want to use data for social good there's so many groups out there that really need your help and there's so many ways to get involved [Music] so let's give a very very warm red hat summit welcome to Erica kochi co-founder of unicef innovation well Erica first of all welcome to Red Hat summit thanks for having me here it's our pleasure and thank you for joining us so Erica I've just talked a bit about kind of what we've been up to and Red Hat services over the last year we talked a bit about our open innovation labs and we did this project the school mapping project together our two teams and I thought the audience might find it interesting from your point of view on why the approach we use in innovation labs was such a good fit for the school mapping project yeah it was a great fit for for two reasons the first is values everything that we do at UNICEF innovation we use open source technology and that's for a couple of reasons because we can take it from one place and very easily move it to other countries around the world we work in 190 countries so that's really important for us not to be able to scale things also because it makes sense we can get we can get more communities involved in this and look not just try to do everything by ourselves but look much open much more openly towards the open source communities out there to help us with our work we can't do it alone yeah and then the second thing is methodology you know the labs are really looking at taking this agile approach to prototyping things trying things failing trying again and that's really necessary when you're developing something new and trying to do something new like mapping every school in the world yeah very challenging work think about it 190 countries Wow and so the open source platform really works well and then the the rapid prototyping was really a good fit so I think the audience might find it interesting on how this application and this platform will help children in Latin America so in a lot of countries in Latin America and many countries throughout the world that UNICEF works in are coming out of either decades of conflict or are are subject to natural disasters and not great infrastructure so it's really important to a for us to know where schools are where communities are well where help is needed what's connected what's not and using a overlay of various sources of data from poverty mapping to satellite imagery to other sources we can really figure out what's happening where resources are where they aren't and so we can plan better to respond to emergencies and to and to really invest in areas that are needed that need that investment excellent excellent it's quite powerful what we were able to do in a relatively short eight or nine week engagement that our two teams did together now many of your colleagues in the audience are using open source today looking to expand their use of open source and I thought you might have some recommendations for them on how they kind of go through that journey and expanding their use of open source since your experience at that yeah for us it was it was very much based on what's this gonna cost we have limited resources and what's how is this gonna spread as quickly as possible mm-hmm and so we really asked ourselves those two questions you know about 10 years ago and what we realized is if we are going to be recommending technologies that governments are going to be using it really needs to be open source they need to have control over it yeah and they need to be working with communities not developing it themselves yeah excellent excellent so I got really inspired with what we were doing here in this project it's one of those you know every customer project is really interesting to me this one kind of pulls a little bit at your heartstrings on what the real impact could be here and so I know some of our colleagues here in the audience may want to get involved how can they get involved well there's many ways to get involved with the other UNICEF or other groups out there you can search for our work on github and there are tasks that you can do right now if and if you're looking for to do she's got work for you and if you want sort of a more a longer engagement or a bigger engagement you can check out our website UNICEF stories org and you can look at the areas you might be interested in and contact us we're always open to collaboration excellent well Erica thank you for being with us here today thank you for the great project we worked on together and have a great summer thank you for being give her a round of applause all right well I hope that's been helpful to you to give you a bit of an update on what we've been focused on in global services the message I'll leave with you is our top priority is customer success as you heard through the story from UNICEF from Heritage Bank and others we can help you innovate where you are today I hope you have a great summit and I'll call out Jim Whitehurst thank you John and thank you Erica that's really an inspiring story we have so many great examples of how individuals and organizations are stepping up to transform in the face of digital disruption I'd like to spend my last few minutes with one real-world example that brings a lot of this together and truly with life-saving impact how many times do you think you can solve a problem which is going to allow a clinician to now save the life I think the challenge all of his physicians are dealing with is data overload I probably look at over 100,000 images in a day and that's just gonna get worse what if it was possible for some computer program to look at these images with them and automatically flag images that might deserve better attention Chris on the surface seems pretty simple but underneath Chris has a lot going on in the past year I've seen Chris Foreman community and a space usually dominated by proprietary software I think Chris can change medicine as we know it today [Music] all right with that I'd like to invite on stage dr. Ellen grant from Boston Children's Hospital dr. grant welcome thank you for being here so dr. grant tell me who is Chris Chris does a lot of work for us and I think Chris is making me or has definitely the potential to make me a better doctor Chris helps us take data from our archives in the hospital and port it to wrap the fastback ends like the mass up and cloud to do rapid data processing and provide it back to me in any format on a desktop an iPad or an iPhone so it it basically brings high-end data analysis right to me at the bedside and that's been a barrier that I struggled with years ago to try to break down so that's where we started with Chris is to to break that barrier between research that occurred on a timeline of days to weeks to months to clinical practice which occurs in the timeline of seconds to minutes well one of things I found really fascinating about this story RedHat in case you can't tell we're really passionate about user driven innovation is this is an example of user driven innovation not directly at a technology company but in medicine excuse me can you tell us just a little bit about the genesis of Chris and how I got started yeah Chris got started when I was running a clinical division and I was very frustrated with not having the latest image analysis tools at my fingertips while I was on clinical practice and I would have to on the research so I could go over and you know do line code and do the data analysis but if I'm always over in clinical I kept forgetting how to do those things and I wanted to have all those innovations that my fingertips and not have to remember all the computer science because I'm a physician not like a better scientist so I wanted to build a platform that gave me easy access to that back-end without having to remember all the details and so that's what Chris does for us is brings allowed me to go into the PAC's grab a dataset send it to a computer and back in to do the analysis and bring it back to me without having to worry about where it was or how it got there that's all involved in the in the platform Chris and why not just go to a vendor and ask them to write a piece of software for you to do that yeah we thought about that and we do a lot of technical innovations and we always work with the experts so we wanted to work with if I'm going to be able to say an optical device I'm going to work with the optical engineers or an EM our system I'm going to work with em our engineers so we wanted to work with people who really knew or the plumbers so to speak of the software in industry so we ended up working with the massive point cloud for the platform and the distributed systems in Red Hat as the infrastructure that's starting to support Chris and that's been actually a really incredible journey for us because medical ready medical softwares not typically been a community process and that's something that working with dan from Red Hat we learned a lot about how to participate in an open community and I think our team has grown a lot as a result of that collaboration and I know you we've talked about in the past that getting this data locked into a proprietary system you may not be able to get out there's a real issue can you talk about the importance of open and how that's worked in the process yeah and I think for the medical community and I find this resonates with other physicians as well too is that it's medical data we want to continue to own and we feel very awkward about giving it to industry so we would rather have our data sitting in an open cloud like the mass open cloud where we can have a data consortium that oversees the data governance so that we're not giving our data way to somebody else but have a platform that we can still keep a control of our own data and I think it's going to be the future because we're running of a space in the hospital we generate so much data and it's just going to get worse as I was mentioning and all the systems run faster we get new devices so the amount of data that we have to filter through is just astronomically increasing so we need to have resources to store and compute on such large databases and so thinking about where this could go I mean this is a classic feels like an open-source project it started really really small with a originally modest set of goals and it's just kind of continue to grow and grow and grow it's a lot like if yes leanest torval Linux would be in 1995 you probably wouldn't think it would be where it is now so if you dream with me a little bit where do you think this could possibly go in the next five years ten years what I hope it'll do is allow us to break down the silos within the hospital because to do the best job at what we physicians do not only do we have to talk and collaborate together as individuals we have to take the data each each community develops and be able to bring it together so in other words I need to be able to bring in information from vital monitors from mr scans from optical devices from genetic tests electronic health record and be able to analyze on all that data combined so ideally this would be a platform that breaks down those information barriers in a hospital and also allows us to collaborate across multiple institutions because many disorders you only see a few in each hospital so we really have to work as teams in the medical community to combine our data together and also I'm hoping that and we even have discussions with people in the developing world because they have systems to generate or to got to create data or say for example an M R system they can't create data but they don't have the resources to analyze on it so this would be a portable for them to participate in this growing data analysis world without having to have the infrastructure there and be a portal into our back-end and we could provide the infrastructure to do the data analysis it really is truly amazing to see how it's just continued to grow and grow and expand it really is it's a phenomenal story thank you so much for being here appreciate it thank you [Applause] I really do love that story it's a great example of user driven innovation you know in a different industry than in technology and you know recognizing that a clinicians need for real-time information is very different than a researchers need you know in projects that can last weeks and months and so rather than trying to get an industry to pivot and change it's a great opportunity to use a user driven approach to directly meet those needs so we still have a long way to go we have two more days of the summit and as I said yesterday you know we're not here to give you all the answers we're here to convene the conversation so I hope you will have an opportunity today and tomorrow to meet some new people to share some ideas we're really really excited about what we can all do when we work together so I hope you found today valuable we still have a lot more happening on the main stage as well this afternoon please join us back for the general session it's a really amazing lineup you'll hear from the women and opensource Award winners you'll also hear more about our collab program which is really cool it's getting middle school girls interested in open sourcing coding and so you'll have an opportunity to see some people involved in that you'll also hear from the open source Story speakers and you'll including in that you will see a demo done by a technologist who happens to be 11 years old so really cool you don't want to miss that so I look forward to seeing you then this afternoon thank you [Applause]

from San Francisco it's the queue covering Red Hat summit 2018 brought to you by Red Hat hey welcome back everyone live here in San Francisco California Moscone West is the cubes live coverage of Red Hat Summer 2018 I'm John furry and my co-host John Troyer our next guest is Denise Dumas vice president software engineering operating system group the Red Hat welcome back to the cube good to see you thank you so much great to be here with you so operating systems Linux the base base with everything yeah now you got all those other goodness going on you have some acquisitions permit bit we were just talking about before he came on a lot of action going on yeah what's new well you know you think that the world of operating systems would be boring but honest to god it is so not especially now right because there is a whole generation of change going on in the hardware and when the hardware changes the operating system has got to change to keep up right you look at the stuff that's going on with GPUs with FPGA right I mean and that's just like tip of the iceberg yeah and everything has to be programmable so you need software to keep track of it so it's not just the patches you gotta keep on top of the DevOps automations a big part of it and security models are changing with the cloud there's no perimeter so you have to have maybe chip level encryption os the way up this is challenging so what is it what's the impact to Red Hat as these new things come on because you know you got you know fishing out there sphere fishing is a big problem you got to handle it all how do you guys handle all the security challenges well you know it's it's actually interesting because rel is the base the core of Red Hat's product line which means that we provide the firm underpinning for everything else in the portfolio so we have the FIP certification we're doing the Common Criteria certification we provide the reliable crypto that everybody else can just expect to have in their world and we have to be the really firm basis for everything that layers on top and it's really great to have the additional products in the portfolio working very closely with us to make sure that we can be end-to-end secure end-to-end compliant and that we're looking at the bigger problems because it's not about the operating system it's about the infrastructure and what you're going to run on top of it right a lot of people have been saying security oh it's hard to do security open source is actually a problem for security and then the world shifts back and says wait a minute open source is better to attack security problem because it's out more people working on it versus the human problem of having proprietary so obviously open source is a good thing - security what's the modern approach that you see now that that that you guys are watching and building around that because that's the number one question that coot at kubernetes con we saw a great thing do some kubernetes we saw is do service meshes but Security's got to be thought of on the front end of all the application developers that means it's on you put it into the OS and it's a different world right because the application developers are not accustomed to having to deal with that because that was always the job of the IT guys right that was a problem for the infrastructure to deal with and so clearly we have to provide better security better better tooling available to them but the operations guys right they still they need help in this new world as well because suddenly there's this explosion of containers in their environment and who knows what's in those containers right we've got to have the ability to scan the containers and make sure that they get patched regularly right so it's just it's a whole different set of problems but it all starts with making sure it's secure underneath all the rest of it well so that's that brings up the console of this concept of layers right there's all the operational things there's the apps and the containers and then you know rail is running underneath that that's the hardware and the micro code and all the rest of the stuff so this year we the whole entire IT industry - the kind of a gasp with with the meltdown inspector problems that that surfaced or you know I guess it was in January I think yeah when they were Republican what that was that was how the colonel team spent their Christmas vacation oh my goodness yeah I the colonel team the performance team the security team the virtualization team all those guys so Red Hat shuts down for a week at Christmastime if they didn't yeah that was exciting I mean we've been trained security is one of these things but there's another one coming because cyber attacks are there what's that what's the viewpoint how do you keep on how do you how do you keep on top of it yeah well you know we have a fabulous security team so if you happen to get up to the second floor go talk with chrome Chris Robinson his guys they monitor what's going on in the upstreams they work with mitre they work with the organization's right and when they discover that something is in the wind they come to us and disclose people as needed and then we get to go and figure out how we're gonna get fixes in usually a lot of this stuff happens as you know under embargo so we really we can't talk about it that's a real problem if a lot of the upstream hasn't been read in right so like for instance with meltdown inspector a lot of that was going on not so much in the upstream so there were kind of divergent patches that we got to bring back together that was really we knew that well we had a really strong suspicion that the embargo was gonna break early there that's why my guys were over Christmas right they had to have something ready secure for when it broke and then we could worry about the performance afterwards yeah right and then you had to roll that out into the entire customer base there's some fairly standard mechanisms was there anything special with that because it was fairly high priority I suppose yeah well I mean anything like that we make available a synchronously cuz we want to have it available that the day that that embargo goes public right because that's when we're gonna be getting the phone calls that's when people say oh my god now what do I do but if but the hard part with this one was that you had to have the microcode as well right but we had to do a lot of Education because this was this the side channel attacks it's just a different way of thinking right it's not so much a flaw in the code as in the overall hardware architecture that we get to deal with that stuff what did you learn what's the learnings that were magnifying we have to be as transparent as we can possibly be because security researchers are going to keep on looking for this kind of flaw and we you know we just have to be able to work as much in the open as we can but we also have to have an education function right this is not an area of core expertise for a lot of people who are working in databases right or who are who are designing Java apps and yet we have to be able to explain to them why there's a performance impact on some of the stuff that they're doing and how we can work together to try to get back some of that performance over time no meltdown inspector that's kind of off my radar now but I don't think we're completely out of it right you people have had to patch and reboot and and update but it sounds like we're not I don't think we're at 100% for sure of all systems yeah well you know IT infrastructure right there's your window in which you can actually afford to reboot your systems and I think a lot of those are very tightly scheduled I mean we have customers who get you know ten minutes a year yeah up times of years and years I mean old rebooting is kind of old fashioned at this point yeah really right as it should be as it should be but but when it's the minor code you're kind of stuck yeah I mean that's a hardware thing getting back to the hardware still hardware's even though cloud is extracting away the complexities Hardware still is out there so you never gonna go away for you and as you said it's changing look at the GPU side and you got all kinds of new things coming on the horizon like blockchain and decentralized infrastructure that's encrypted amen right so you know this is you know systems level code mm-hmm with software guys who don't know micro code mm-hmm so you guys got to be on top of it so so I guess the big question is is that operating system that you guys have is very reliable and the support is phenomenal use of industries how do you take the support and the engineering in rel and operating systems and bring that operate system mindset to the next level up as you move up the stack kubernetes new OpenStack as well openshift yeah and apps they all want the same reliability you all want the same kind of robustness nature of an ecosystem at the same time more people are being certified yeah so you have a balance of growth and reliability how do you how do you guys see that and it's also speed and time to market right which is the other factor because there's so much pressure on any emerging technology to get the features out there that you end up carrying the technical debt right or you end up not being able to be as hardened as you might like to be the instant that you go out the door and so it's always gonna be a balancing act and a trade-off so you I know you guys were just talking with Mark Oh bill Peter and he was probably talking about how we're trying to focus on use cases right we need to understand the use cases that our customers have and now those are clearly across the entire product portfolio right but those are the test scenarios that I need to get in flight and those are also the the paths that I need to make sure we've optimized for right and so it's a partnership with the rest of the products in the portfolio and we really do a lot to work together as tightly as we can which is one of the benefits of being at the core right I'm working with everybody yeah and you got the instrumentation too so the other theme yeah the automation big time theme here is breaking down the two of real granular level sets of services which actually is a good thing because if you can instrument it then it's just easy to manage because then he can isolate things so I mean this is a good thing in the OS people love this because you can see couple and make things work well but the instrumentation if you have the API API and you need the instrumentation and looking in so how is that created a challenge because it's all those great for Red Hat's business and then you see in the the forecast and the analysts are seeing the growth you guys are seeing the successes but it makes your job harder a bit that one's a harder but I mean it's you know you get it right more code and make glue layers of abstraction layers yeah but I wouldn't want it to be boring well I do want it to I want it to be boring for our customers I want our customers to just be able to pick up and no drum and exciting homes not ringing with no spectra again it's working like a charm no problem yeah drama llama does not live here yeah yeah that's an interesting point though just a lot of talk about the whole Red Hat stack here right and you got as we've said you the base of it where does where does Linux where is this Linux and especially rail go from here what are you looking at that over the next few years some different technologies you're looking to pull it etc mm-hmm there's always I mean we have to keep up with the hardware advances clearly right but then there's let's oh look at our permaban what a great ad right so perma bit for people who don't know they do a video virtual data optimizer so they do D dupe and compression on the fly on the path to the disk and with rail 75 as part of your subscription you get so we buy we buy companies and we open-source their soft code side their software and we make it available to you as part of your subscription right how good is that so is when you deploy 75 in your environment now suddenly you're gonna need a whole lot less storage right depending on of course it depends upon your data footprint right but but you might find that you're able to shrink the amount of all that expensive storage and expensive cloud storage particularly that you need significantly and you get the compression right was avenge compression was very popular we know we followed in fallen permit bit question on permit bit for you was that open source was that they build their front open stores because now and are you guys open sourcing that that's okay so you have to go gain and and then open it up and do a review and clean it up and yeah yeah and we have to help them get it into an upstream right so they actually they were fabulous the perma because they have been so fabulous to work with best acquisition ever seems to be pretty good at acquiring companies and incorporating their tacit that seems to be part of the culture here yeah that's cuz we're not you know people think we're like big and scary right I'll tell you I have worked for companies that are big and scary Red Hat is not it we're really open and it's really in many ways in engineering culture which is wonderful it's a great fit if you happen to be from a startup culture because we don't overwhelm you with process right I mean we a lot of smart people again I can attest to my interactions over the years smart people very humble a lot of systems people to which is cooperating system hello the world's turning into an operating system good for that but humble and plays the long game you guys I've been you deserve credit for that and that's that's attracting and reason why you successful but you know the thing is we really believe in our core values right we really truly honest-to-god believe in open source and the power that it has to change the world that you know you say oh yeah sure right she's part of the management change she's gonna see him anyway yeah but you guys are growing so I mean over the years again since we started the cube nine years ago we've watched red add just in that time span grow significantly I'll see it's well documented an alternative to the other proprietary os's second-tier citizen now running the world the first tier great job so the youth success business model of open source is now mainstream but you got to onboard more people more ecosystem partners in a really dynamic big wave of innovation coming yeah how do you maintain the recruiting how do you get the great people how do you preserve the culture I'm sure these are questions how do you the more inclusion and diversity questions this is all happening right they're gonna have to catch him at nine years old and grown I mean although honest to god we do a lot of university outreach right if you look in the Czech Republic for instance we have a huge operation in Brno which is the second largest city there and we are so tied in to the university system we bring in lots and lots and lots of interns and it's wonderful right because we want to teach people about open-source we find people who have passion projects and we bring them in this is this is our world right we don't we want non-traditional people as well as traditional computer science majors open-source is a great leveler your CV is online I mean imagine right you're you want to change careers you want a new life you love to code you've been working on writing games in your in your spare time you are our people that's the code your code is who you are your code is it's your CV well this is what Oh doing your things on the open means and also it's been great for your business and we had gym writers on earlier there's no a/b testing they just go into the community and find out what's they want and they just that's the a B C's e testing it's just right there you guys do the due diligence sometimes make big time real fun decisions on features based upon what is in demand practically speaking not just focusing on the new tech that's a good business model we hope so cuz you know I mean as as one of our former CFO I said there are a lot of people a lot of Associates at Red Hat who are dependent on Red Hat for a paycheck and it's very important to us that we remain profitable stable and and really good for our people right we've got a lot of people that we need to take care of in the time it's a good place to be in the timing spray with kubernetes and containers we're taking it up a notch and bringing that extensibility you know just beyond stand-alone Linux so congratulations Denise thanks for coming on and sharing your perspective as always we love these conversations in the cube talk and everything from operating systems to core OS and kubernetes and culture as the cue here out in the open on the floor at Moscone West John Troy yer stay with us we'll be back with more day two of three days of live coverage on the cube net we'll be right back

live from San Francisco it's the cube covering Red Hat summit 2018 brought to you by Red Hat okay welcome back everyone would live here in San Francisco California the Moscone West for the cubes exclusive coverage of Red Hat summit 2018 I'm John for the co-host of the cube was my closest week analyst John Troy a co-founder of tech reckoning advisory and Community Development firm our next two guests is erica kochi co-founder of unicef innovation the United Nations Children's Fund and Mike Walker director of open innovation labs at Red Hat welcome to the cube thanks for coming joining us thanks love this story so Erica take a minute to talk about what you're working on at UNICEF you guys doing a lot of great stuff you got the relationship with Red Hat innovation labs but you doing some pretty amazing things take them into explain what you're doing at UNICEF some of the projects and what we're going to talk about here with the school and the magic fox all the greatness sure so UNICEF innovation essentially what we do is take technology and apply it to the problems facing children around the world and we do that in a variety of ways I think the things that we're probably most most known for is our work in mobile technology to connect frontline health workers and young people to to governments and have let them have a say in what's happening in in you know the halls of government and we have a program called you report which has five million young people from all over the world who are talking directly to their government representatives they need that now more than ever we certainly do yeah so open source obviously with red hat big shared vision talk about the shared mission like what's going on but there where's the connection I was the open source was great for society we've seen the benefits all around the world how is this translating for you guys yeah so I've been at Red Hat for a while and obviously we're the world's largest open source enterprise open source software company and I as a consultant been able to see Red Hat open source software used for many different purposes in every vertical you can think of but this one was really unique because we found a natural partnership I think between some of UNICEF innovations vision to use open source and open principles for maximum impact for good and so when I learned about innovation at UNICEF really by chance I just ran into a colleague at a meeting in New York and and she gave me a few words about it I said this is incredible because we can leverage all of what we learned at Red Hat our knowledge of open source to impact people and culture and not just for technical reasons and and partnered with UNICEF to make maximum social impact for children that need it most and you got red house key a technology company a lot of smart people there but with open source there's been a DNA in your bloodstream of the company around democratization and now we're out in the open with everyone online and everything's good this is a democratization piece talk about some of that the things that you guys are doing with red hat what specifically are you celebrating together here so we had a great collaboration with with Red Hat there at their labs program which really took a look at our challenge of using big data to read or understand what's happening on the ground especially in schools in countries that are either coming out of emergencies or have limited access to a lot of the parts of the country and so we layered satellite imagery information on poverty other sets of data you can really get a clear picture about where we should be allocating our resources and how we should be planning for emergencies and this collaboration just just finished up a couple days ago right and it's really been great what's some of the impact give an example of some of the use cases so actually saving time money will be things around yeah what what are some of the impact things that you see with this project what are some of the things a lot of countries right now are thinking about how they can connect all of their schools and make sure all of it their schools are online and give children this access to information that's really essential to to thrive in the world of today and tomorrow and if you don't know where your schools are and you don't know if they're connected or not and you can't see you know what else is happening it's in the socio-economic way in those areas it's really hard to figure out what to do and where to start so we're really just at the beginning of that process to try to connect every school in the world and we're at the moment we're trying to lay the groundwork to understand where we're at and where we need a level of insight you're providing once you connect the schools you can get people can know what to do and how to align with what's happening it's interesting I was just in Puerto Rico a couple weeks ago and the young kids there have self formed their own blockchain network between the schools and they're teaching themselves how to program because they recognize that to get out of their world and the mess that they're challenging through now post-hurricane they want to participate in the new economy so as someone not knowing that if I know I could help you're kind of providing a window into that kind of dynamic where is that kind of the use case is that how it's working so it's but participation and contribution is absolutely participation is key you know for young people and they need to it like really learn how to acquire the skills that they're gonna need to you know become successful productive adults in the future and school is you know one of the entry points to do that so that's really important and everyone loves that - yeah I'm kind of curious about the structure of the project today in the keynote you know Jim why does she start us off by saying well you know we can't plan everything we've got to be a little bit more agile here's a framework for how to how to really approach problems when we really don't know what the outcome or even what we're gonna hit so can you talk a little bit maybe about the structure of the of the process and did you know did you start with a blank piece of paper or do you know how did how did you figure out the pathway to the ultimate outcome here yeah I can take it first um that's a great question because at labs we experiment with ways to get fast feedback and really in a very short amount of time usually one to three months and a very limited amount of funds how can we make maximum impact using open technologies and open practices so the project was already in progress like most IT projects are right Gardi been some research we have data scientists to work with and one of the first things we did was really talk about really our concerns and fears about how we might work together using an exercise called how might we we kind of came together and said how might we solve this problem or that problem and just got it out on the table one of the aspects that I think work really is dedicating a small team in a residency style engagement where we worked off premise so Red Hatters left their office UNICEF folks left their office we came together in akola works based in New York City that was fairly convenient and you know we all focused on a tough problem and we decided really early on that in order to make sure that this problem actually would be usable and in the hands of end users in the field across the world we needed to get face to face so we made a trip to Latin America to work with a UNICEF field office to get fast feet up feedback on prototypes and that helped us adjust what we ended up shipping as the product at the end of the two months cycle Erika how was the outcome for you and your game it's great I think you know one of the things that really aligns RedHat and UNICEF is not just a commitment to open source and the values around that but also this agile methodology I think that you know to really move something a product forward or sort of a program forward you need to step away from the daily part of life you know and move away from the the email and the connection to the laptop and the phone and I think we were able to do that I also think that you need to ground truth things and so that you know that trip to the field and to really understand the context and the problems that that people are facing is is completely critical to success and that's like agile programming you kind of gotta get get out in the front lines not ask about the data I'm really intrigued so you got multiple data sources coming in love the satellite thing you're changing lives but you're saving lives too is your talk about you may name real-time efforts here what's the data science thing what's the tech behind I mean is it ingesting data as a third party data Z how does it work I mean can you share some some of the mechanics on the date of data science piece er yeah I think there's probably a lot we can talk about I could talk about data all day love data but some of the things that I think were fundamentally really exciting about this project and about what UNICEF innovation has done so let's take for example Facebook they have a whole lot of data but that's one company and it's sort of one lens to the world right it's it's quite broad and we get a lot of information but it's one company what UNICEF innovation has done is found ways to partner with private and public companies and private and public data sources in a way that maintains the security and integrity of that data so that it's not exposing proprietary information but they've been able to create those that community essentially that's willing to share information to solve a really tough challenge for social good and so we have actually a really wide variety of data at our disposal and our job was to create a sandbox that allow data scientists to really both proactively plan for things that might happen and reactively plan when events occur when we don't even know what that event might be so you know I like to think back to Jim Whitehurst's speech last year at summit where I said planning is dead we've got to try learn and modify I think that's exactly what we aim to build a platform that you know hasn't been planned for any one event or action but provides the flexibility for data scientists to try experiment pull different data together learn from it sharing Maps we integrated geospatial data and maps to be able to pass this along quickly and then modify based on the results so we can more quickly achieve something with the greatest impact that's awesome yeah so for example if you take you know you take like for example epidemics right so many factors are so many different types of data are needed to really understand what's happening in an epidemic for example take Zika you have temperature right mosquitos only breed at a certain at a certain temperature you have poverty or which really indicates standing water where mosquitoes can breed you have socioeconomic factors so it does the house more likely does it have mosquito screens or not and then you have the social right what are people talking about what are they concerned about and I think like a really interesting picture emerges when you can start to layer all of these kinds of data and that really helps us see where we should be focusing it's great discovery information using the data to drive kind of we're to look at and we're to focus efforts exactly and also a global footprint right and in previous decades maybe this would have run on a piece with some sort of a proprietary GIS thing or or yeah I'm not even sure right you chip around discs maybe but I mean not not to be too product oriented right built on OpenShift we've seen a whole lot this week right these global footprint you could take it live on any cloud I assume that's a piece of it right at global accessibility now for they out for the the resulting application absolutely and we want to take you know what we've done in one scenario and apply it to many others in many other locations and so being an open source is key for this because we wouldn't be able to do this in other locations are replicated just as easily handed to local folks have them an adapted and/or take it further or have other people work on it whether it's academics other companies us nice I love the structure like how its agile I got a Eric I ought to ask you about this because we're seeing a big trend with open source obviously that's well on its way to becoming it is the standard of doing software but mission driven technology activities aren't just nonprofits anymore you starting to see collaboration the JOBS Act that Obama put in place really set the table for new kind of funding so you've seen a lot more younger people coming in and saying hey you know what I can build it on the cloud and grants aware but the code gets live on right so you seeing a new flywheel around mission driven nonprofits and for-profits a new kind of entrepreneurship culture can you share insight into how this is developer you see a lot of it you have a lot of thoughts on this your them please so I think that you know as technology companies become so much more influential in our lives you know they're not just showing you the news anymore they were they're moving into every aspect of our lives whether it's in our into our homes or even inside our bodies that they're they're occupying as so much more influential role in an individual's life with that comes a tremendous amount of responsibility and I think that while it's not enough to say you should do good because it's the right thing to do I think that employees also really demand it I think that you know and that shift will occur because employees realize that they want to they want to be doing good in the world and if they're gonna be influencing so many people's lives that's really really it's a new citizenship model for the younger generations early Millennials want to work in a company that's not just the profit hungar motive but also there's some dynamics going on with the infrastructure world you look at Facebook as a classic example you know the word weaponizing content has been a bad thing but we've been talking about in the queue there's actually a reverse of that polar opposite which is you can weaponize content for good meaning that all the same principles that do bad things can be used for good things so this is where we started to see a lot more people saying hey let's do more of the fad and punish so the new kind of rules are developing in the society so I find it fascinating and I'm just curious is this known within the societal entrepreneurship culture or what's the what's your view on how to do more how to do better I'm doing a lot of work in what AI is gonna be meaning what's what it's gonna mean for children in the world and you know there are so many opportunities we've been talking about some of them but there are also a lot of risks right what does it mean when your child's best friend is a robot what does that change about our us us you know as human beings and so I think it's you know you have to look at both sides and you have to be very conscious about designing the technology that you want to see in the world that's gonna make the world a good place to live in and I think that there definitely is an awakening and that's going and there's a lot this is a first generation set of problems that social entrepreneurship brings a just society I mean who sets the policy which side of the road the cars drive on or you know there's these new issues that are evolving that I've never been seen before you know cyber bullying - all kinds of things happening so congratulations on all those success so what's the forecast for Red Hat innovation has more of this gonna continue double down on it what are the things do you guys have going on yeah so Labs is growing quite largely we are now live in North America amia and a pack with plans to expand extend to Latin in the future and we're growing quite quickly in terms of our ability to execute I guess you know the labs team is relatively small a small number of specialists but we are all of RedHat so the way we operate is based on what we're trying to achieve together we will look at all of red hat and sometimes even outside of red hat to figure out who we can bring to the table to help solve that problem and so it allows me to work with our engineering with our business units even with our marketing so we brought marketing in to the first meeting not simply because we're creating a marketing event but we realized we need to advertise internally and externally what we build in order to gain adoption it's part of building a community and what I have found is because Labs has an injective that goes beyond you know simply a technological objective we're aiming to change ways of working and to change culture it's really easy to build a lot of interest and adoption among all Red Hatters to bring them together to solve a tough problem a really an interesting facet a lot about labs I know you do these pop-up labs and I think this was what you know you don't make necessarily make people come to you you son can come to them but I think like you said it's important to get outside your your office and your day-to-day for these focused projects you talked a little bit about your approach to yeah so we've learned a lot you know Labs is almost exactly two years old I think we launched in April of 2016 at OpenStack summit and one thing we learned is you know the world is a big place and we can't necessarily have a physical lab location everywhere so we do have first-class facilities in Boston Singapore in London but I would say the large majority of the work efforts we've done to date have been in what we call pop-up labs and what that allows us to do is create that immersion and focus on a tough challenge by getting people out of the office but also provide the ability to go home at the end of the day and have dinner at your home which a lot of people enjoy and from the red head perspective we've got a lot of folks used to travel so we can make that happen meet in the middle and and it's been a good hybrid approach that we end up doing more and more great stuff here actually is my final question for then to take from Jim Whitehouse keynote today how is blockchain changing this open for good economics that's absolutely right and I mean Erika you might want to weigh in as well but I think I love blockchain first of all I love math and I love the science behind it but I love the fact that it was developed in the open it was debated in the open it's radically transparent you can see all of the transactions of anyone in the chain and it's being used in ways that no one ever dreamed of I mean it was meant for a universal currency but you know think about this we might be able to use it as a token system so that we can actually ensure that humanitarian efforts that are done are actually recognized by people that they may not otherwise have funds right someone with very little money can still use so perhaps takers making sure the money gets put to use absolutely and endpoints we have accountability you know we're using it to exchange electronic health records securely and privately with the people that need them and only the people that need them so I don't know where blockchain will be in five years but I am optimistic that I think the mathematics and the fundamental is a blockchain or sound and I think more than anything it's the community that will drive new applications of blockchain and really define and answer that question for you well I know we'll be in New York next week with blockchain for consensus of ennum there's a lot of ents going on we've seen wealthy entrepreneurs donating Bitcoin and aetherium there's a really great project so and a lot of young people love the blockchain and crypto so who knows got to be on that labs we're definitely look you know looking into it and we have a couple experiments around the world that range from trying to do some smart contracts you know in in country environments to taking donations in in blockchain armies Arion cryptocurrencies I think that there are a lot of exciting applications for it in this due to do good space I also think that there's a tremendous amount of hype and you know you really have to ask yourself the key question of like does this need a central trusted Authority or is there one that exists that already is great um and do we need to record every transaction if you can answer those two questions then the other baby going somewhere well great point the other thing I would answer that agree hundred percent and that is is that blockchain and crypto our token economic certainty not the ico scams but is an efficiency heat-seeking missile it it targets efficiencies where there's inefficiencies announced where I see a lot of the action going on and you know efforts and for good are highly inefficient yeah so hey you knows well we'd love blockchain as you can tell we talk about all day long smart contracts token economics thanks for coming on and congratulations on your project thank you you're good to stuff their cube coverage here day two of three days live coverage here in San Francisco the Red Hat summit 2018 moved back after this short break stay with us