>> (upbeat music) >> production: From around the globe, it's the Cube covering Google cloud Next on-Air 20. (Upbeat music) >> Welcome back. I'm Stu Miniman and this is the CUBE coverage of Google cloud Next on Air 20. Of course, the nine week distributed all online program that Google cloud is doing and going to be talking about, of course, multi-cloud, Google of course had a big piece in multi-cloud. When they took what was originally Borg, They built Kubernetes. They made that open source and gave that to the CNCF and one of Google's partners and a leader in that space is of course, Red Hat. Happy to welcome to the program Sathish Balakrishnan, he is the Vice President of hosted platforms at Red Hat. Sathish, thanks so much for joining us. >> Thank you. It's great to be here with you on Google Cloud Native insights. >> Alright. So I, I tied it up, of course, you know, we talk about, you know, the hybrid multicloud and open, you know, two companies. I probably think of the most and that I've probably said the most about the open cloud are Google and Red Hat. So maybe if we could start just, uh, you hosted platforms, help us understand what that is. And, uh, what was the relationship between Red Hat and the Open Shift team and Google cloud? >> Absolutely. Great question. And I think Google has been an amazing partner for us. I think we have a lot of things going on with them upstream in the community. I think, you know, we've been with Google and the Kubernetes project since the beginning and you know, like the second biggest contributor to Kubernetes. So we have great relationships upstream. We also made Red Hat Enterprise Linux as well as Open Shift available on Google. So we have customers using both our offerings as well as our other offerings on Google cloud as well. And more recently with the hosted our offerings. You know, we actually manage Open Shift on multiple clouds. We relaunched our Open Shift dedicated offering on Google cloud back at Red Hat Summit. There's a lot of interest for the offering. We had back offered the offering in 2017 with Open Shift Three and we just relaunched this with Open Shift Four and we received considerable interest for the Google cloud Open Shift dedicated offering. >> Yeah, Sathish maybe it makes sense if we talk about kind of the maturation of open source solutions, managed services has seen really tremendous growth, something we've seen, especially if we were talking about in the cloud space. Maybe if you could just walk us through a little bit out that, you know, what are you hearing from customers? How does Red Hat think about managed solutions? >> Absolutely. Stu, I think it was a good question, right? I think, uh, as we say, the customers are looking at, you know, multiple infrastructure footprints, Be iteither the public cloud or on-prem. They'll start looking at, you know, if I go to the cloud, you know, there's this concept of, I want something to be managed. So what Open Shift is doing is in Open Shift, as you know it's Red Hat's hybrid cloud platform and with Open Shift, all the things that we strive to do is to enable the vision of the Open Hybrid Cloud. Uh, so, but Open Hybrid Cloud, it's all about choice, So we want to make sure the customers have both the managed as well as the self managed option. Uh, so if you really look at it, you know, Red Hat has multiple offerings from a managed standpoint. One as you know, we have Open Shift dedicated, which runs from AWS and Google. And, you know, we just have, as I mentioned earlier. We relaunched our Google service at Red Hat Summit back in May. So that's actually getting a lot of traction. We also have joint offerings with Azure that we announced a couple of years back and, there's a lot of interest for that offering as well as the new offering that we announced post-summit, the Amazon-Red Hat Open Shift, which basically is another native offering that we have on Amazon. If you really look at, having, having spoken about these offerings, if you really look at Red Hat's evolution as a managed service provider in the public cloud, we've been doing this since 2011. You know, that's kind of surprising for a lot of people, but you know, we've been doing Open Shift online, which is kind of a multi-tenant parcel multi-talent CaaS solution 2011. And we are one of the earliest providers of managed kubernetes, you know, along with Google Kubernetes engine GKE, we are our Open Shift dedicated offering back in 2015. So we've been doing Kubernetes managed since, Open Shift 3.1. So that's actually, you know, we have a lot of experience with management of Kubernetes and, you know, the devolution of Open Shift we've now made it available and pretty much all the clouds. So that customers have that exact same experience that they can get any one cloud across all clouds, as well as on-prem. Managed service customers now have a choice of a self managed Open Shift or completely managed Open Shift. >> Yeah. You mentioned the choice and one of the challenges we have right now is there's really the paradox of choice. If you look in the Kubernetes space, you know, there are dozens of offerings. Of course, every cloud provider has their offerings. You know, Google's got GKE, they have Anthos, uh, they, they have management tools around there. You, you talked a bit about the, you know, the experience and all the customers you have, the, you know, there's one of the fighters talks about, there's no compression algorithm for experience. So, you know, what is Red Hat Open Shift? What really differentiates in the market place from, you know, so many of the other offerings, either from the public high providers, some of the new startups, that we should know. >> Yeah. I think that's an interesting question, right? I think all Google traders start with it's complete open source and, you know, we are a complete open source company. So there is no proprietary software that we put into Open Shift. Open Shift, basically, even though it has, you know, OC command, it basically has CPR. So you can actually use native Google networks as you choose on any Google network offering that you have be it GKE, EKS or any of the other things that are out there. So that's why I think there are such things with google networks and providers and Red Hat does not believe in open provider. It completely believes in open source. We have everything that we is open source. From an it standpoint, the value prop for Red Hat has always been the value of the subscription, but we actually make sure that, you know, Google network is taken from an upstream product. It's basically completed productized and available for the enterprise to consume. But that right, when we have the managed offering, we provide a lot more benefits to it, right? The benefits are right. We actually have customer zero for Open Shift. So what does that mean? Right. We will not release Open Shift if we can't run open Shift dedicated or any of their (indistinct) out Open Shift for them is under that Open Shift. Really really well. So you won't get a software version out there. The second thing is we actually run a lot of workloads, but then Red Hat that are dependent on our managed or open shift off. So for example, our billing systems, all of those internal things that are important for Red Hat run on managed Open Shift, for example, managed Open Shift. So those are the important services for Red Hat and we have to make sure that those things are running really, really well. So we provide that second layer of enterprise today. Then having put Open Shift online, out that in public. We have 4 million applications and a million developers that use them. So that means, I've been putting it out there in the internet and, you know, there's security hosts that are constantly being booked that are being plugged in. So that's another benefit that you get from having a product that's a managed service, but it also is something that enterprises can now use it. From an Open Shift standpoint, the real difference is we add a lot of other things on top of google network without compromising the google network safety. That basically helps customers not have to worry about how they're going to get the CIC pipeline or how they have to do a bunch of in Cobra Net as an outside as the inside. Then you have technologies like Store Street Metrics kind of really help customers not to obstruct the way the containerization led from that. So those are some of the benefits that we provide with Open Shift. >> Yeah. So, so, so Sathish, as it's said, there's lots of options when it comes to Kubernetes, even from a Red Hat offering, you've got different competing models there. If I look inside your portfolio, if it's something that I want to put on my infrastructure, if I haven't read the Open Shift container platform, is that significantly different from the managed platform. Maybe give us a little compare contrast, you know. What do I have to do as a customer? Is the code base the same? Can I do, you know, hybrid environments between them and you know, what does that mean? >> It's a smart questions. It's a really, really good question that you asked. So we actually, you know, as I've said, we add a lot of things on top of google network to make it really fast, but do you want to use the cast, you can use the desktop. So one of the things we've found, but you know, what we've done with our managed offering is we actually take Open Shift container platform and we manage that. So we make sure that you get like a completely managed source, you know. They'll be managed, the patching of the worker nodes and other things, which is, again, another difference that we have with the native Cobra Net of services. We actually give plush that admin functionality to customers that basically allows them to choose all the options that they need from an Open Shift container platform. So from a core base, it's exactly the same thing. The only thing is, it's a little bit opinionated. It to start off when we deploy the cluster for the customer and then the customer, if they want, they can choose how to customize it. So what this really does is it takes away any of the challenges the customer may have with like how to install and provision a cluster, which we've already simplified a lot of the open shift, but with the managed the Open Shift, it's actually just a click of it. >> Great. Sathish Well, I've got the trillion dollar question for you. One of the things we've been looking at for years of course, is, you know, what do I keep in my data center? What do I move to the cloud? How do I modernize it? We understand it's a complex and nuanced solution, but you talk to a lot of customers. So I, you know, here in 2020, what's the trends? What are some of the pieces that you're seeing some change and movement that, you know, might not have been the case a year ago? >> I think, you know, this is an interesting question and it's an evolving question, right? And it's something that if you ask like 10 people you'll get real answers, but I'm trying to generalize what I've seen just from all the customer conversations I've been involved. I think one thing is very clear, right? I think that the world is right as much as anybody may want to say that I'm going to go to a single cloud or I'm going to just be on prem. It is inevitable that you're going to basically end up with multiple infrastructure footprint. It's either multicloud or it's on Prem versus a single cloud or on prem versus multiple cloud. So the main thing is that, we've been noticing as, what customers are saying in a whole. How do I make sure that my developers are not confused by all these difference than one? How do I give them a consistent way to develop and build their applications? Not really worry about, what is the infrastructure. What is the footprint that they're actually servicing? So that's kind of really, really important. And in terms of, you know, things that, you know, we've seen customers, you know, I think you always start with compliance requirements and data regulations. Back there you got to figure it out. What compliance do I need? And as the infrastructure or the platform that I'm going to go to meet the compliance requirements that I have, and what are the data regulations? You know, what is the data I'm going to be setting? Is it going to meet the data submitted rules that my country or my geo has? I got to make sure I worry about that. And then I got to figure out if I'm going to basically more to the cloud from the data center or from one cloud to another cloud. I might just be doing a lift or shift. Am I doing a transformation? What is it that I really worry about? In addition to the transformation, they got to figure it out, or I need to do that. Do I not need to do that? And then, you know, we've got to figure out what your data going to set? What your database going to look in? And do you need to connect to some legacy system that you have on prem? Or how do you go? How do you have to figure that out and give them all of these complexities? This is really, really common for any large enterprise that has like an enterprise ID for that multi-cloud. That's basically in multiple geographies, servicing millions of customers. So that has a lot of experience doing all these things. We have open innovation labs, which are really, really awesome experience for customers. Whether they take a small project, they figured out how to change things. Not only learn how to change things from a technology standpoint, but also learn how to culturally change things, because a lot of these things. So it's not just moving from one infrastructure to another, but also learning how to do things differently. Then we have things like the container adoption programmer, which is like, how do you take a big legacy monolith application? How do you containerize it? How do you make it micro services? How do you make sure that you're leveraging the real benefits that you're going to get out of moving to the cloud or moving to a container platform? And then we have a bunch of other things like, how do you get started with Open Shift and all of that? So we've had a lot of experience with like our 2,400 plus customers doing this kind of really heavy workload migration and lifting. So the customers really get the benefits that they see out of Open Shift. >> Yeah. So Sathish, if I think about Google, specifically talking about Google cloud, one of the main reasons we hear customers using Google is to have access to the data services. They have the AI services they have. So how does that tie into what we were just talking about? If I, if I use Open Shift and you know. I'm living in Google cloud, can, can I access all of those cloud native services? Are there any nuances things I need to think about to be able to really unleash that innovation of the platform that I'm tying into? >> Yeah, absolutely not. Right. I think it's a great question. And I think customers are always wondering about. Hey, if I use Open Shift, am I going to be locked out of using the cloud services? And if anything run out as antilock. We want to make sure that you can use the best services that you need for your enterprise, like the strategy as well as for applications. So with that, right. And we've developed the operator framework, which I think Google has been a very early supporter of. They've built a lot of operators around their services. So you can develop those operators to monitor the life cycle of these services, right from Open Shift. So you can actually connect to an AI service if you want. That's absolutely fine. You can connect the database services as well. And you can leverage all of those things while your application runs on Open Shift from Google cloud. Also I think that done us right. We recognize that, when you're talking about the open hybrid cloud, you got to make sure that customers can actually leverage services that are the same across different clouds. So when you can actually leverage the Google services from On Prem as well, if you choose to have localized services. We have a large catalog of operators that we have in our operator hub, as well as in the Red Hat marketplace that you can actually go and leverage from third party, third party ISV, so that you're basically having the same consistent experience if you choose to. But based on the consistent experience, that's not tied to a cloud. You can do that as well. But we would like for customers to use any service that they want, right from Open Shift without any restrictions. >> Yeah. One of the other things we've heard a lot from Google over the last year or so has been, you know, just helping customers, especially for those mission, critical business, critical applications, things like SAP. You talked a bit about databases. What advice would you give customers these days? They're, they're looking at, you know, increasing or moving forward in their cloud journeys. >> I think it sounds as an interesting question because I think customers really have to look at, you know, what is the ID and technology strategy? What are the different initiatives to have? Is it digital transformation? Is it cloud native development? Is it just containerization or they have an overarching theme over? They've got to really figure that out and I'm sure they're looking at it. They know which one is the higher priority when all of them are interrelated and in some ways. They also got to figure out how they going to expand to new business. Because I think as we said, right, ID is basically what is driving personal software is eating the load. Software services are editing them. So you got to figure out, what are your business needs? Do you need to be more agile? Do you need to enter new businesses? You know, those are kind of important things. For example, BMW is a great example, they use Open Shift container platform as well as they use Open Shift dedicated, you know. They are like a hundred hundred plus year old car, guess, you know what they're trying to do. They're actually now becoming connected car infrastructure. That's the main thing that they're trying to build so that they can actually service the cars in any job. So in one shoe, they came from a car manufacturing company to now focus on being a SAS, an Edge and IOT company. If you really look at the cars as like the internet of things on an edge computer and what does that use case require? That use case cannot anymore have just one data center in Munich, they have to basically build a global platform of data centers or they can really easily go to the cloud. And then they need to make sure that that application double close when they're starting to run on multiple clouds, multiple geographies, they have the same abstraction layer so that they can actually apply things fast. Develop fast. They don't have to worry about the infrastructure frequently. And that's basically why they started using Open Shift. And don't know why they're big supporters of Open Shift. And then I think it's the right mission for their use. So I think it really depends on, you know, what the customer is looking for, but irrespective of what they're looking for, I think Open Shift nicely fits in because what it does, is it provides you that commonality across all infrastructure footprints. It gives you all the productivity gains and it allows you to connect to any service that you want anywhere because we are agnostic to that and as well as we bring a whole lot of services from Red Hat marketplace so you can actually leverage your status. >> Well, Sathish Balakrishnan, thank you so much for the updates. Great to hear about the progress you've got with your customers. And thank you for joining us on the Google cloud Next On Air Event. >> Thank you Stu. It's been great talking to you and look forward to seeing you in person one day. >> Alright. I'm Stu Miniman. And thank you as always for watching the Cube. (upbeat music) (upbeat music)

>>From around the globe covering Google cloud next. >>Hi, I'm Stu middleman and this is the cube coverage of Google cloud. Next, happy to welcome back to the program. One of our cube alumni, Clayton Coleman, he's the architect for Kubernetes and OpenShift with red hat Clayton. Thanks for joining us again. Great to see you. Good to see you. All right. So of course, one of the challenges in 2020 is we love to be able to get unity together. And while we can't do it physically, we do get to do it through all of the virtual events and online forum. Of course, you know, we had the cubit red hat summit cube con, uh, for the European show and now Google cloud. So, you know, give us kind of your, your state of the state 2020 Kubernetes. Of course it was Google, uh, taking the technology from Borg, a few people working on it, and, you know, just that this project that has just had massive impact on it. So, you know, where are with the community in Kubernetes today? >>So, uh, you know, 2020 has been a crazy year for a lot of folks. Um, a lot of what I've been spending my time on is, um, you know, taking feedback from people who, you know, in this time of, you know, change and concern and worry and huge shift to the cloud, um, working with them to make sure that we have a really good, um, you know, foundation in Kubernetes and that the ecosystem is healthy and the things are moving forward there. So there's a ton of exciting projects. I will say, you know, the, the pandemics had a, an impact on, um, you know, the community. And so in many places we've reacted by slowing down our schedules or focusing more on the things that people are really worried about, like quality and bugs and making sure that the stuff just works. Uh, I will say this year has been a really interesting one and open source. >>There's been much more focus, I think, on how we start to tie this stuff together. Um, and new use cases and new challenges coming into, um, what maybe, you know, the original Kubernetes was very focused on helping you bring stuff together, bring your applications together and giving you common abstractions for working with them. Um, we went through a phase where we made it easy to extend Kubernetes, which brought a whole bunch of new abstractions. And, and I think now we're starting to see the challenges and the needs of organizations and companies and individuals that are getting out of, um, not just in Kubernetes, but across multiple locations across placement edge has been huge in the last few years. And so the projects in and around Kubernetes are kind of reacting to that. They're starting to, um, bridge, um, many of these, um, you know, disparate locations, different clouds, multicloud hybrid cloud, um, connecting enterprises to data centers are connecting data centers to the cloud, helping workloads be a little bit more portable in of themselves, but helping workloads move. >>And then I think, you know, we're, we're really starting to ask those next big questions about what comes, what comes next for making applications really come alive in the cloud, um, where you're not as focused on the hardware. You're not focused on the details, which are focused on abstractions, like, um, you know, reliability and availability, not just in one cluster, but in multiple. So that's been a really exciting, uh, transition in many of the projects that I've been following. You know, certainly projects like Istio I've been dealing with, um, spanning clusters and connecting existing workloads in and, uh, you know, each step along the way, I see people sort of broaden their scope about what they want, uh, open source to help themselves. >>Yeah, I it's, it's, it's been fascinating to watch just the, the breadth of the projects that can tie in and leverage Kubernetes. Uh, you brought up edge computing and want to get into some of the future pieces, but before we do, you know, let's look at Kubernetes itself. Uh, one dot 19 is kind of where we are at. Uh, um, I already see some, some red stalking about one dot 20. Can you just talk about the, the, the base project itself contributions to it, how the upstream, uh, works and you know, how, how should customers think about, you know, their Kubernetes environment, obviously, you know, red hat with open shifts had a very strong position. You've got thousands of customers now using it, all of the cloud providers have their, uh, Kubernetes flavor, but also you partner with them. So walk us through a little bit about, you know, the open source, the project and those dynamics. >>The project is really healthy. I think we've got through a couple of big transitions over the last few years. We've moved from the original, um, you know, I was on the bootstrap steering committee trying to help the governance model. The full bootstrap committee committee has handed off responsibility to, um, new participants. There's been a lot of growth in the project governance and community governance. Um, I think there's huge credit to the folks on the steering committee today. Folks, part of contributor experience and standardizing and formalizing Kubernetes as its own thing. I think we've really moved into being a community managed project. Um, we've developed a lot of maturity around that and Kubernetes and the folks involved in helping Kubernetes be successful, have actually been able to help others within the CNCF ecosystem and other open source projects outside of CNCF be successful. So that angle is going phenomenally well. >>Uh, contribution is up. I think one of the tension points that we've talked about is, um, Kubernetes is maturing one 19, spent a lot of time on stability. And while there's definitely lots of interesting new things in a few areas like storage, and we have fee to an ingress fee too, coming up on the horizon dual stack, support's been hotly anticipated by a lot of on premise folks looking to make the transition to IPV six. I think we've been a little bit less focused on chasing features and more focused on just making sure that Kubernetes is maturing responsibly. Now that we have a really successful ecosystem of integrators and vendors and, um, you know, unification, the conformance efforts in Kubernetes. Um, there've been some great work. I happened to be involved in the, um, in the architecture conformance definition group, and there's been some amazing participation from, um, uh, from that group of people who've made real strides in growing the testing efforts so that, you know, not only can you look at, um, two different Kubernetes vendors, but you can compare them in meaningful ways. >>That's actually helped us with our test coverage and Kubernetes, there's been a lot of focus on, um, really spending time on making sure that upgrades work well, that we've reduced the flakiness of our test suites and that when a contributor comes into Kubernetes, they're not presented with a confusing, massive instructions, but they have a really clear path to make their first contribution and their next contribution. And then the one after that. So from a project maturity standpoint, I think 2020 has been a great great year for the project. And I want to see that continue. >>Yeah. One of the things we talked quite a bit about, uh, at both red hat summit, as well as, uh, the CubeCon cloud native con Europe, uh, was operators. And, you know, maybe I believe there was some updates also about how operators can work with Google cloud. So can you give us that update? >>Sure. There's been a lot of, um, there's been a lot of growth in both the client tooling and the libraries and the frameworks that make it easy to integrate with Kubernetes. Um, and those integrations are about patterns that, um, make operations teams more productive, but it takes time to develop the domain expertise in, uh, operationalizing large groups of software. So over the last year, um, know the controller runtime project, uh, which is an outgrowth of the Kubernetes Siggy lb machinery. So it's kind of a, an outshoot that's intended to standardize and make it easier to write integrations to Kubernetes that next step of, um, you know, going then pass that red hat's worked, uh, with, um, others in the community around, um, the operator SDK, uh, which unifying that project and trying to get it aligned with others in the ecosystem. Um, almost all of the cloud providers, um, have written operators. >>Google has been an early adopter of the controller and operator pattern, uh, and have continued to put time and effort into helping make the community be successful. And, um, we're really appreciative of everyone who's come together to take some of those ideas from Kubernetes to extend them into, um, whether it's running databases and service on top of Kubernetes or whether it's integrating directly with cloud. Um, most of that work or almost all of that work benefits everybody in the ecosystem. Um, I think there's some future work that we'd like to see around, um, you know, uh, folks, uh, from, um, a number of places have gone even further and tried to boil Kubernetes down into simpler mechanisms, um, that you can integrate with. So a little bit more of a, a beginner's approach or a simplification, a domain specific, uh, operator kind of idea that, um, actually really does accelerate people getting up to speed with, um, you know, building these sorts of integrations, but at the end of the day, um, one of the things that I really see is the increasing integration between the public clouds and their Kubernetes on top of those clouds through capabilities that make everybody better off. >>So whether you're using a managed service, um, you know, on a particular cloud or whether you're running, um, the elements of that managed open source software using an open source operator on top of Kubernetes, um, there's a lot of abstractions that are really productive for admins. You might use the managed service for your production instances, but you want to use, um, throw away, um, database instances for developers. Um, and there's a lot of experimentation going on. So it's almost, it's almost really difficult to say what the most interesting part is. Um, operators is really more of an enabling technology. I'm really excited to see that increasing glue that makes automation and makes, um, you know, dev ops teams, um, more productive just because they can rely increasingly on open source or managed services offerings from, you know, the large cloud providers to work well together. >>Yeah. You had mentioned that we're seeing all the other projects that are tying into Coobernetti's, we're seeing Kubernetes going into broader use cases, things like edge computing, what, from an architectural standpoint, you know, needs to be done to make sure that, uh, Kubernetes can be used, you know, meets the performance, the simplicity, um, in these various use cases. >>That's a, that's a good question. There's a lot of complexity in some areas of what you might do in a large application deployment that don't make sense in edge deployments, but you get advantages from having a reasonably consistent environment. I think one of the challenges everybody is going through is what is that reasonable consistency? What are the tools? You know, one of the challenges obviously is as we have more and more clusters, a lot of the approaches around edge involve, you know, whether it's a single cluster on a single machine and, um, you know, in a fairly beefy, but, uh, remote, uh, computer, uh, that you still need to keep in sync with your application deployment. Um, you might have a different life cycle for, uh, the types of hardware that you're rolling out, you know, whether it's regional or whether it's tied to, whether someone can go out to that particular site that you've been update the software. Sometimes it's connected, sometimes it isn't. So I think a need that is becoming really clear is there's a lot of abstractions missing above Coopernetties. Uh, and everyone's approaching this differently. We've got a get ops and centralized config management. Um, we have, uh, architectures where, you know, you, you boot up and you go check some remote cloud location for what you should be running. Um, I think there's some, some productive obstructions that are >>That, or haven't been, um, >>It haven't been explored sufficiently yet that over the next couple of years, how do you treat a whole bunch of clusters as a pool of compute where you're not really focused on the details of where a cluster is, or how can you define applications that can easily move from your data center out to the edge or back up to the cloud, but get those benefits of Kubernetes, all those places. And >>That >>This is for so early, that what I see in open source and what I see with people deploying this is everyone is approaching this subtly differently, but you can start to see some of those patterns emerge where, um, you need reproducible bundles of applications, things that help can do REL, or you can do with just very simply with Kubernetes. Um, not every edge location needs, um, uh, an ingress controller or a way to move traffic onto that cluster because their job is to generate traffic and send it somewhere else. But then that puts more pressure on, well, you need those where you're feeding that data to your API APIs, whether that's a cloud or something within your something within a private data center, you need, um, enough of commonalities across those clusters and across your applications that you could reason about what's going on. So >>There's a huge amount >>Out of a space here. And I don't think it's just going to be Kubernetes. In fact, I, I want to say, I think we're starting to move to that phase where Kubernetes is just part of the platform that people are building or need to build. And what can we do to build those tools that help you stitch together computer across a lot of footprints, um, parts of applications across a lot of footprints. And there's, there's a bunch of open source projects that are trying to drive to that today. Um, projects like I guess the O and K natives, um, with the work being done with the venting in K native, and obviously the venting is a hugely, um, you know, we talk about edge, we'd almost be remiss, not talk about moving data. And you talk about moving data. Well, you want streams of data and you want to be reacted to data with compute and K native and Istio are both great examples of technologies within the QB ecosystem that are starting to broaden, um, you know, outside of the, well, this is just about one cube cluster to, um, we really need to stitch together a mindset of development, even if we have a reasonably consistent Kubernetes across all those footprints. >>Yeah. Well, Clayton so important. There's so many technologies out there it's becoming about that technology. And it's just a given, it's an underlying piece of it. You know, we don't talk about the internet. We don't talk, you know, as much about Linux anymore. Cause it's just in the fabric of everything we do. And it sounds like we're saying that's where we're getting with Kubernetes. Uh, I'd love to pull on that thread. You mentioned that you're hearing some patterns starting to emerge out there. So when you're talking to enterprises, especially if you're talking 2020, uh, lots of companies, all of a sudden have to really accelerate, uh, you know, those transformational projects that they were doing so that they can move faster and keep up with the pace of change. Uh, so, you know, what should enterprise be, be working on? What feedback are you hearing from customers, but what are some of those themes that you can share and w what, what should everybody else be getting ready for that? >>The most common pattern I think, is that many people still find a need to build, uh, platforms or, um, standardization of how they do application development across fairly large footprints. Um, I think what they're missing, and this is what everyone's kind of building on their own today, that, um, is a real opportunity within the community is, uh, abstract abstractions around a location, not really about clusters or machines, but something broader than that, whether it's, um, folks who need to be resilient across clouds, and whether it's folks who are looking to bring together disparate footprints to accelerate their boot to the cloud, or to modernize their on premise stack. They're looking for abstractions that are, um, productive to say, I don't really want to worry too much about the details of clusters or machines or applications, but I'm talking about services and where they run and that I need to stitch those into. >>Um, I need to stitch those deeply into some environments, but not others. So that pattern, um, has been something that we've been exploring for a long time within the community. So the open service broker project, um, you know, has been a long running effort of trying to genericize one type of interface operators and some of the obstructions and Kubernetes for extending Kubernetes and new dimensions is another. What I'm seeing is that people are building layers on top through continuous deployment, continuous integration, building their own API is building their own services that really hide these details. I think there's a really rich opportunity within open to observe what's going on and to offer some supporting technologies that bridge clouds, bridge locations, what you deal with computed a little bit more of an abstract level, um, and really doubled down on making services run. Well, I think we're kind of ready to make the transition to say officially, it's not just about applications, which is what we've been saying for a long time. >>You know, I've got these applications and I'm moving them, but to flip it around and say, we want to be service focused and services, have a couple of characteristics, the details of where they run are more about the guarantees that you're providing for your customers. Um, we lack a lot of open source tools that make it easier to build and run services, not just to consume as dependencies or run open source software, but what are the things that make our applications more resilient in and of themselves? I think Kubernetes was a good start. Um, I really see organizations struggling with that today. You're going to have multiple locations. You're going to have, um, the need to dramatically move workloads. What are the tools that the whole ecosystem, the open source ecosystem, um, can collaborate on and help accelerate that transition? >>Well, Clayton, you teed up on my last thing. I want to ask you, you know, we're, we're here at the Google cloud show and when you talk about ecosystem, you talk about community, you know, Google and red hat, both very active participants in this community. So, you know, you, you peer you collaborate with a lot of people from Google I'm sure. So give our audience a little bit of insight as to, you know, Google's participation. What, what you've been seeing from them the last couple of years at Google has been a great partner, >>Crazy ecosystem for red hat. Um, we worked really closely with them on Istio and K native and a number of other projects. Um, I, you know, as always, um, I'm continually impressed by the ability of the folks that I've worked with from Google to really take a community focus and to concentrate on actually solving use cases. I think the, you know, there's always the desire to create drama around technology or strategy or business and open source. You know, we're all coming together to work on common goals. I really want to, um, you know, thank the folks that I've worked with at Google over the years. Who've been key participants. They've believed very strongly in enabling users. Um, you know, regardless of, um, you know, business or technology, it's about making sure that we're improving software for everyone. And one of the beauties of working on an open source project like Kubernetes is everyone can get some benefit out of it. And those are really, um, you know, the sum of all of the individual contributions is much larger than what the simple math would apply. And I think that's, um, you know, Kubernetes has been a huge success. I want to see more successes like that. Um, you know, working with Google and others in the open source ecosystem around infrastructure as a service and, you know, this broadening >>Domain of places where we can collaborate to make it easier for developers and operations teams and dev ops and sec ops to just get their jobs done. Um, you know, there's a lot more to do and I think open source is the best way to do that. All right. Well, Clayton Coleman, thank you so much for the update. It's really great to catch up. It was a pleasure. All right. Stay tuned for lots more coverage. The Google cloud next 2020 virtually I'm Stu Miniman. Thank you for watching the cube.

>> Announcer: Live from San Francisco, it's theCUBE, covering Google Cloud Next '19. Brought to you by Google Cloud, and its ecosystem partners. >> We're back at Google Cloud Next, at the new, improved Moscone Center. This is day two of theCUBE's coverage of Google's big Cloud show. theCUBE is a leader in live tech coverage, my name is Dave Vellante, I'm here with my co-host Stu Miniman. John Furrier is walking the floor, checking out the booth space. Ranga Rangachari is here, he's the Vice President and General Manager of Cloud Storage and hyper-converged infrastructure at Red Hat. Ranga, good to see you again. >> Hi Dave, hi Stu, good to see you again too. >> Thanks for coming on, this show it's, it's growing nicely, good thing Moscone is new and improved. How's the show going for you? >> Show's going really good. I just had a chance to walk around the booths and a lot of interesting conversations and, the Red Hat booth too, there've been a lot of interesting conversations with customers. >> A lot of tailwinds these days for Red Hat. We talk about that a lot on theCUBE, this whole notion of hybrid cloud, you guys have been on that since the early days. >> Yeah. >> Multi-cloud, omni-cloud, hyper-converged infrastructure, it's in your title. It's like that all the moons are lining up for you guys, you know is it just luck, skill, great predictions powers, what's your take? >> Well, I mean, I think it's a combination of those, but more importantly, it's about listening to our customers. I think that's what gives us, today, the permission to talk to our customers about some of these things they're doing, because when we talk to them, it's not just about solving today's problems, but also where they're headed, and anticipating where they're going, and the ability to meet their needs. So is, I think. >> So the Google partnership, we were talking earlier, it started 10 years ago with the hypervisor. >> Yup. >> And it's really evolved. Where is it today, from your perspective? >> Well, I think it continues to, it continues to cooperate in the technical community very well, and a couple of data points, one is on Kubernetes, that started four, five years ago, and that's going really strong. But more importantly, as the industry matures, there are, what I would call, special interest groups that are starting to emerge in the Kubernetes community. One thing that we are paying very close attention to is the storage SIG, which is the ability to federate storage across multiple clouds, and how do you do it seamlessly within the framework of Kubernetes, as opposed to trying to create a hack, or a one-off that some vendors attempted to do. So we try to take a very wholistic view of it, and make sure, I mean the industry we are in is trying to drive volumes, and volumes drives standards, so I think we pay very, very close attention-- >> And the objective there is leave the data in place if possible, provide secure access and fast access, provide high-speed data movement if necessary, protect the data in motion. That is a complex problem. >> It is, and that's why I think it's very important that the community together solves the problem, not just one vendor. But it's about how do you facilitate, the holy grail is how do you facilitate data portability and application portability across these hybrid clouds. And a lot of the things that you talked about are part and parcel of that, but what users don't wanna do is stitch them together. They want a simple, easy way. And most common example that we often get asked is can I migrate my data from one cloud to the other, from on-prem to a public cloud beta based on certain policies. That's a prototypical example of how federated storage and other things can help with that. >> Ranga, bring us inside some of those customer conversations, 'cause we talk on theCUBE, we go back to, customers always say I want multi-vendor, yes, I don't want lock-in, portability is a good thing, but at the end of the day, some of these things, if it's some science experiment or if it's difficult, well, sometimes it's easier just to kind of stick on a similar environment. We know the core of Red Hat, it's if I build on top of rail, then I know it can work lots of places, so where are customers at, how does that fit in to this whole discussion of multi-cloud. >> So, what I can kind of give you a perspective of the hybrid cloud, the product strategy that we've been on for better part of a decade now, is around facilitating the hybrid cloud. So if you look at the open, or the storage nature of the data nature of the conversations, it's almost two sides of the same coin. Which is, the developers want storage to be invisible. They don't wanna be in the business of stitching their lungs and their zone masking all that stuff. But yet at the same time they want storage to be ubiquitous. So, they want it to be invisible, they want it to be ubiquitous. So that's one of the key themes that we are in from our customer. >> Come on, Ranga, you guys are announcing storage list this year, right? >> Yeah, (laughs) exactly. (laughs) So that's a great point. The other part that we are also seeing from our customer conversations is, I think, let me give you, kind of the Red Hat inside out perspective. Is any products, any thing that we release to the market, the first filter that we run through is will it help our customers with our open hybrid cloud journey? So that kind of becomes the filter for any new features we add, any go-to-market motion, so that there is a tremendous amount of impedance match if you will. Between where we're going and how customers can succeed with their open hybrid cloud journey. >> So, in thinking about some of the discussions you're having with customers on their hybrid cloud strategy, specifically, what are those conversations like, what are the challenges that they're having? It's a maturity spectrum, obviously, but what are you seeing at each level of the spectrum, and where are some of those execution, formulation and execution challenges? >> So, as the industry evolves and the technology matures, the conversation change, and 12, 24 months ago it was a dramatically different conversation. It was an all around help me get there. Now the conversation is people really understand, and most of our conversations that we see, and even the other industry players are seeing this, is the conversation starts with on-prem looking out, as opposed to a cloud looking in. So, customers say look I've invested a tremendous amount of assets, intellectual horsepower into building my on-prem infrastructure and make it solid, now give me the degree of freedom for me to move certain workloads to one or many of these public clouds. So that's kind of a huge shift in the conversations we have with the customers. If you click one or a couple of levels below, the conversation talks about things like security as you pointed out. How do you ensure that if I move my workload my overall corporate compliance stuff aren't anywhere compromised. So that's one aspect. The other aspect is manageability. Can it really manage this infrastructure from a proverbial single pane of glass. So now the conversations are less about more theoretical, it's more about I've started the journey help me make this journey successful. >> So when you talk about the perspective of, I've built up this on-prem infrastructure, I've invested a ton it in, and now help me connect, I can see a mindset that would say think cloud first. Of course, the practical reality says I've got all this tactical debt. So how much of that is gonna be a potential pitfall down the road for some of these companies, in your view? >> Well, I think it's not so much of a technical debt. In one way you could call it a technical debt, but the other aspect is how do you really leverage the investment that you've made without having to just say well I'm gonna do things differently. So, that's why I think the conversations we have with our customers are mutually beneficial, because we can help them, but the same token they can help us understand where some of the road blocks are. And through our products, through our services, we can help them circumvent or mitigate some of those-- >> And those assets aren't depreciated on the books, they've gotta get a return on them, right? >> So, Ranga, we know that one of the areas that Red Hat and Google end up working a lot together is in the Cloud Native Computing Foundation. >> Yep. >> Bring us up to speed as to where we are with that storage discussion, 'cause I think back to when Docker launched it was oh, it's gonna be wonderful and everything, but we all live through virtualization, and we had to fix networking and storage challenges here, and networking seemed to go a little further along and there's been a few different viewpoints as to how storage should be looked at in the containerized and the Kubernetes SDO world that we're moving towards today. >> So one example that illustrates storage being the center of this is there is a project called Rook.io. If you're familiar with this, think of it as kind of sitting between the storage infrastructure and Kubernetes. And that is taking on a tremendous amount of traction, not just in the community, but even within the CNCF. I could be wrong here, but my understanding it's a project that's in incubation phase right now. So we are seeing a lot of industry commitment to that Rook project, and you're gonna see real, live use cases where customers are now able to fulfill the vision of data portability and storage portability across these multiple hybrid clouds. >> So Kubernetes is obviously taking off, although again, it's a maturity level. Some customers are diving in, and others maybe not so much. What are you seeing is some of the potential blockers, how are people getting started? Can you just download the code and go? What are you seeing there? >> That's a very interesting question, because we look at it as projects versus products. And, Kubernetes is a project. Phenomenal amount of velocity, phenomenal amount of innovation. But once you deploy it in your production environment, things like security, things like life cycle management, all those things have to be in place before somebody deploys it. That's why, in OpenShift you've seen the tremendous amount of market acceptance we've have with OpenShift is a proof point that it is kind of the best Kubernetes out there, because it's enterprise ready, people can deploy it, people can use it, people can scale with it, and not be worried about things like life cycle management, things like security, all the things that come into play when you deal with an upstream project. So, what we've seen from a customer basis, people start to dabble, and they'll look at Kubernetes, what's going on, and understand where the areas of innovation are. But once they start to say look I've got it deployed for some serious workloads, they look at a vendor who can provide all the necessary ingredients for them to be successful. >> We're having a good discussion earlier about customer's perspectives, I wanna get as much out of that asset as I possibly can. You said something that interested me. I wanna go back to it. Is customers want options to be able to migrate to various clouds. My question is do you sense that that's because they wanna manage their risk, they want an exit strategy? Or, are they actively moving more than once. Maybe they wanna go once and then run in the cloud. Or are you seeing a lot of active movement of that data? >> I think the first order of bit in those discussions that are about the workloads, What workload do they wanna run? And once they decide this is the, for instance, with the Google Cloud, with the MLAI type of workloads, lend themselves very well to the Google Cloud infrastructure. So when a customer says look this is the workload I wanna run on-prem, but I want the elastic capability for me to run on one of these public clouds, often the decision criteria seems to be what workload it is and where's the best place to run it in. And then, you know, the rest of the stuff comes into play. >> So, Ranga, let's step back for a second. I come out of this show, Google Cloud this year, and I'm hearing open, multi-cloud, reminds me of words I've heard going to Red Hat, some every year. Help us to kind of squint through a little bit as to where Red Hat sits in the customer. If I'm the c-suite of an enterprise customer day, where Red Hat fits in the partnership with customers, and where the partners fit into that overall story. >> So, our view is let's look at it customer end. And practically every customer that we talk to wants to embark on an open hybrid cloud storage. And I wanna kind of stress on the open part of it, because it's the easier way to say okay let me go build a hybrid cloud. The more difficult part is how do you facilitate it through open hybrid cloud story. And that's the march, if you will, that we've been on for the last five plus years. And, that business strategy and the technology strategy has not, we've been unwavering in that. And, the partners are and they say we truly believe that for us to be successful, for our customers to be successful, we need an ecosystem of partners. And the cloud providers are absolutely a critical ingredient and a critical component of the overall strategy, and I think together, with our partners, and our core technology, and our go-to-market routes, we think we can really solve our customers, we are solving them today, and we think we can continue to solve them over time. >> You talk about open, open has a lot of different definitions. And again it's suspected UNIX used to be open. (laughs) I see that potentially as one, real solid differentiator of Red Hat. I mean, your philosophy on open. What do you see as your differentiators in the marketplace? >> Well, I think the first is obviously open like you said, the second part is, I think I hinted upon it earlier, which is, projects are good. I think they are almost a fountain and of ideas and things, but I think where we spend a tremendous amount of hours of energy is to transform it from the upstream project into a product. And if you go back, Red Hat Linux, I think we've shown that Linux was in the same kind of state of vibe in other ways, 10, 20 years ago. And I think what we've shown to the industry is by being solely committed and focused on make these projects enterprise ready, I think we've shown the market leading the way, and making it successful. So I think for us, the next wave, whether it's Kubernetes, whether it's other things, it's a very similar recipe book, nothing dramatically different, but fundamentally what we want to do is help our customers take advantage of those innovations, but yet not compromise on what they need in their enterprise data centers. >> The recipe book is similar, but you've gotta make bets. You've made some pretty good bets over the years. >> Yep. >> We could debate about OpenStack, but I mean, even there. But that's not an easy thing for an open source company to do. 'Cause you've gotta pick your poison, you have to provide committers, what's the secret sauce there? >> Well, I think, first off, I think the number one secret sauce from our perspective is add more technical and intellectual horsepower to these communities. And, not so much for the sake of community, it's about does it solve a real business problem for our customers? That's the way we go about it because in the open source community, I don't even know, hundreds of thousands of open source projects are out there. And we pay, and our office of the CTO pays very close attention to all the projects out there, identify the ones that have promise, not just from our perspective but from customers' perspective, and invest in those areas. And a lot of them have succeeded, so we think we'll do well in that. >> Alright, so, Ranga, one of the biggest announcements this week is Anthos from Google. Wanna get your viewpoint as to where that fits. >> I think it's a good announcement, I haven't read through all the details, but part of it is I think it validates, to a certain extent, what Red Hat has been talking about for the last five, seven years. Which is you need a unified way to deploy, manage, provision your infrastructure, not just on public clouds, but a seamless way to connect to the on-prem. And I think Anthos is a validation of how we've been thinking about the work. So we think it's great. We think it's really good. >> Ranga Rangachari thanks so much for coming back on theCUBE >> Thank you, David! >> It's always a pleasure. >> Thank you again, Stu. >> Have a great Red Hat summit coming up in early May, theCUBE will be there, Stu will be co-hosting. You're watching theCUBE, day two of Google Cloud Next 2019 from Moscone. We'll be right back. (upbeat music)

>> reply from San Francisco. It's the Cube covering Google Club next nineteen Tio by Google Cloud and its ecosystem partners. >> We're back at Google Cloud next twenty nineteen. You're watching the Cube, the leader in live tech coverage on Dave a lot with my co host to minimum John Farriers. Also here this day. Two of our coverage. Hash tag. Google Next nineteen. Mike Evans is here. He's the vice president of technical business development at Red Hat. Mike, good to see you. Thanks for coming back in the Cube. >> Right to be here. >> So, you know, we're talking hybrid cloud multi cloud. You guys have been on this open shift for half a decade. You know, there were a lot of deniers, and now it's a real tail one for you in the whole world is jumping on. That bandwagon is gonna make you feel good. >> Yeah. No, it's nice to see everybody echoing a similar message, which we believe is what the customers demand and interest is. So that's a great validation. >> So how does that tie into what's happening here? What's going on with the show? It's >> interesting. And let me take a step back for us because I've been working with Google on their cloud efforts for almost ten years now. And it started back when Google, when they were about to get in the cloud business, they had to decide where they're going to use caveat present as their hyper visor. And that was a time when we had just switched to made a big bet on K V M because of its alignment with the Lenox Colonel. But it was controversial and and we help them do that. And I look back on my email recently and that was two thousand nine. That was ten years ago, and that was that was early stages on DH then, since that time, you know, it's just, you know, cloud market is obviously boomed. I again I was sort of looking back ahead of this discussion and saying, you know, in two thousand six and two thousand seven is when we started working with Amazon with rail on their cloud and back when everyone thought there's no way of booksellers goingto make an impact in the world, etcetera. And as I just play sort of forward to today and looking at thirty thousand people here on DH you know what sort of evolved? Just fascinated by, you know, sort of that open sources now obviously fully mainstream. And there's no more doubters. And it's the engine for everything. >> Like maybe, you know, bring us inside. So you know KK Veum Thie underpinning we know well is, you know, core to the multi clouds tragedy Red hat. And there's a lot that you've built on top of it. Speak, speak a little bit of some of the engineering relationships going on joint customers that you have. Ah, and kind of the value of supposed to, you know, write Hatton. General is your agnostic toe where lives, but there's got to be special work that gets done in a lot of places. >> Ralph has a Google. Yeah, yeah, yeah. >> Through the years, >> we've really done a lot of work to make sure that relative foundation works really well on G C P. So that's been a that's been a really consistent effort and whether it's around optimization for performance security element so that that provides a nice base for anybody who wants to move any work loader application from on crime over there from another cloud. And that's been great. And then the other maid, You know, we've also worked with them. Obviously, the upstream community dynamics have been really productive between Red Hat and Google, and Google has been one of the most productive and positive contributors and participants and open source. And so we worked together on probably ten or fifteen different projects, and it's a constant interaction between our upstream developers where we share ideas. And do you agree with this kind of >> S O Obviously, Cooper Netease is a big one. You know, when you see the list, it's it's Google and Red Hat right there. Give us a couple of examples of some of the other ones. I >> mean again, it's K B M is also a foundation on one that people kind of forget about that these days. But it still is a very pervasive technology and continuing to gain ground. You know, there's all there's the native stuff. There's the studio stuff in the AML, which is a whole fascinating category in my mind as well. >> I like history of kind of a real student of industry history, and so I like that you talk to folks who have been there and try to get it right. But there was a sort of this gestation period from two thousand six to two thousand nine and cloud Yeah, well, like you said, it's a book seller. And then even in the down turn, a lot of CFO said, Hey, cap backstop ex boom! And then come out of the downturn. And it was shadow I t around that two thousand nine time frame. But it was like, you say, a hyper visor discussion, you know, we're going to put VM where in in In our cloud and homogeneity had a lot of a lot of traditional companies fumbling with their cloud strategies. And and And he had the big data craze. And obviously open source was a huge part of that. And then containers, which, of course, have been around since Lennox. Yeah, yeah, and I guess Doctor Boom started go crazy. And now it's like this curve is reshaping with a I and sort of a new era of data thoughts on sort of the accuracy of that little historical narrative and and why that big uptick with containers? >> Well, a couple of things there won the data, the whole data evolution and this is a fascinating one. For many, many years. I'm gonna be there right after nineteen years. So I've seen a lot of the elements of that history and one of the constant questions we would always get sometimes from investor. Why don't you guys buy a database company? You know, years ago and we would, you know, we didn't always look at it. Or why aren't you guys doing a dupe distribution When that became more spark, etcetera. And we always looked at it and said, You know, we're a platform company and if we were to pick anyone database, it would only cover some percentage and there's so many, and then it just kind of upsets the other. So we've we've decided we're going to focus, not on the data layer. We're going to focus on the infrastructure and the application layer and work down from it and support the things underneath. So it's consistent now with the AML explosion, which, you know, we're who was a pioneer of AML. They've got some of the best services and then we've been doing a lot of work within video in the last two years to make sure that all the GP use wherever they're run. Hybrid private cloud on multiple clouds that those air enabled and Raylan enabled in open shift. Because what we see happening and in video does also is right now all the applications being developed by free mlr are written by extremely technical people. When you write to tense airflow and things like that, you kind of got to be able to write a C compiler level, but so were working with them to bring open shift to become the sort of more mass mainstream tool to develop. A I aml enable app because the value of having rail underneath open shift and is every piece of hardware in the world is supported right for when that every cloud And then when we had that GPU enablement open shift and middleware and our storage, everything inherits it. So that's the That's the most valuable to me. That's the most valuable piece of ah, real estate that we own in the industry is actually Ralph and then everything build upon that and >> its interest. What you said about the database, Of course, we're a long discussion about that this morning. You're right, though. Mike, you either have to be, like, really good at one thing, like a data stacks or Cassandra or a mongo. And there's a zillion others that I'm not mentioning or you got to do everything you know, like the cloud guys were doing out there. You know, every one of them's an operational, you know, uh, analytics already of s no sequel. I mean, one of each, you know, and then you have to partner with them. So I would imagine you looked at that as well. I said, How're we going to do all that >> right? And there's only, you know, there's so many competitive dynamics coming at us and, you know, for we've always been in the mode where we've been the little guy battling against the big guys, whoever, maybe whether it was or, you know, son, IBM and HP. Unix is in the early days. Oracle was our friend for a while. Then they became. Then they became a nen ime, you know, are not enemy but a competitor on the Lennox side. And the Amazon was early friend, and then, though they did their own limits. So there's a competitive, so that's that's normal operating model for us to us to have this, you know, big competitive dynamic with a partnering >> dynamic. You gotta win it in the marketplace that the customers say. Come on, guys. >> Right. We'Ll figure it out >> together, Figured out we talked earlier about hybrid cloud. We talked about multi cloud and some people those of the same thing. But I think they actually you know, different. Yeah, hybrid. You think of, you know, on prim and public and and hopefully some kind of level of integration and common data. Plain and control plan and multi cloud is sort of evolved from multi vendor. How do you guys look at it? Is multi cloud a strategy? How do you look at hybrid? >> Yeah, I mean, it's it's it's a simple It's simple in my mind, but I know the words. The terms get used by a lot of different people in different ways. You know, hybrid Cloud to me is just is just that straightforward. Being able to run something on premise have been able to run something in any in a public cloud and have it be somewhat consistent or share a bowl or movable and then multi cloud has been able to do that same thing with with multiple public clouds. And then there's a third variation on that is, you know, wanting to do an application that runs in both and shares information, which I think the world's you know, You saw that in the Google Antos announcement, where they're talking about their service running on the other two major public cloud. That's the first of any sizable company. I think that's going to be the norm because it's become more normal wherever the infrastructure is that a customer's using. If Google has a great service, they want to be able to tell the user toe, run it on their data there at there of choice. So, >> yeah, so, like you brought up Antos and at the core, it's it's g k. So it's the community's we've been talking about and, he said, worked with eight of us work for danger. But it's geeky on top of those public clouds. Maybe give us a little bit of, you know, compare contrast of that open shift. Does open ship lives in all of these environments, too, But they're not fully compatible. And how does that work? So are >> you and those which was announced yesterday. Two high level comments. I guess one is as we talked about the beginning. It's a validation of what our message has been. Its hybrid cloud is a value multi clouds of values. That's a productive element of that to help promote that vision And that concept also macro. We talked about all of it. It it puts us in a competitive environment more with Google than it was yesterday or two days ago. But again, that's that's our normal world way partnered with IBM and HP and competed against them on unit. We partner with that was partnered with Microsoft and compete with them, So that's normal. That said, you know, we believe are with open shift, having five plus years in market and over a thousand customers and very wide deployments and already been running in Google, Amazon and Microsoft Cloud already already there and solid and people doing really things with that. Plus being from a position of an independent software vendor, we think is a more valuable position for multi cloud than a single cloud vendor. So that's, you know, we welcome to the party in the sense, you know, going on prom, I say, Welcome to the jungle For all these public called companies going on from its, you know, it's It's a lot of complexity when you have to deal with, You know, American Express is Infrastructure, Bank of Hong Kong's infrastructure, Ford Motors infrastructure and it's a it's a >> right right here. You know Google before only had to run on Google servers in Google Data Center. Everything's very clean environment, one temperature on >> DH Enterprise customers have it a little different demands in terms of version ality and when the upgrade and and how long they let things like there's a lot of differences. >> But actually, there was one of the things Cory Quinn will. It was doing some analysis with us on there. And Google, for the most part, is if we decide to pull something, you've got kind of a one year window to do, you know? How does Red Hot look at that? >> I mean, and >> I explained, My >> guess is they'LL evolve over time as they get deeper in it. Or maybe they won't. Maybe they have a model where they think they will gain enough share and theirs. But I mean, we were built on on enterprise DNA on DH. We've evolved to cloud and hybrid multi cloud, DNA way love again like we love when people say I'm going to the cloud because when they say they're going to the cloud, it means they're doing new APs or they're modifying old apse. And we have a great shot of landing that business when they say we're doing something new >> Well, right, right. Even whether it's on Prem or in the public cloud, right? They're saying when they say we'LL go to the club, they talk about the cloud experience, right? And that's really what your strategy is to bring that cloud experience to wherever your data lives. Exactly. So talking about that multi cloud or a Romney cloud when we sort of look at the horses on the track and you say Okay, you got a V M. We're going after that. You've got you know, IBM and Red Hat going after that Now, Google sort of huge cloud provider, you know, doing that wherever you look. There's red hat now. Course I know you can't talk much about the IBM, you know, certainly integration, but IBM Executive once said to me still that we're like a recovering alcoholic. We learned our lesson from mainframe. We are open. We're committed to open, so we'LL see. But Red hat is everywhere, and your strategy presumably has to stay that sort of open new tia going last year >> I give to a couple examples of long ago. I mean, probably five. Six years ago when the college stuff was still more early. I had a to seo conference calls in one day, and one was with a big graphics, you know, Hollywood Graphics company, the CEO. After we explained all of our cloud stuff, you know, we had nine people on the call explaining all our cloud, and the guy said, Okay, because let me just tell you, right, that guy, something the biggest value bring to me is having relish my single point of sanity that I can move this stuff wherever I want. I just attach all my applications. I attached third party APS and everything, and then I could move it wherever we want. So realize that you're big, and I still think that's true. And then there was another large gaming company who was trying to decide to move forty thousand observers, from from their own cloud to a public cloud and how they were going to do it. And they had. They had to Do you know, the head of servers, a head of security, the head of databases, the head of network in the head of nine different functions there. And they're all in disagreement at the end. And the CEO said at the end of day, said, Mike, I've got like, a headache. I need some vodka and Tylenol now. So give me one simple piece of advice. How do I navigate this? I said, if you just write every app Terrell, Andrzej, boss. And this was before open shift. No matter >> where you want >> to run him, Raylan J. Boss will be there, and he said, Excellent advice. That's what we're doing. So there's something really beautiful about the simplicity of that that a lot of people overlooked, with all the hand waving of uber Netease and containers and fifty versions of Cooper Netease certified and you know, etcetera. It's it's ah, it's so I think there's something really beautiful about that. We see a lot of value in that single point of sanity and allowing people flexibility at you know, it's a pretty low cost to use. Relish your foundation >> over. Source. Hybrid Cloud Multi Cloud Omni Cloud All tail wins for Red Hat Mike will give you the final world where bumper sticker on Google Cloud next or any other final thoughts. >> To me, it's It's great to see thirty thousand people at this event. It's great to see Google getting more and more invested in the cloud and more and more invested in the enterprise about. I think they've had great success in a lot of non enterprise accounts, probably more so than the other clowns. And now they're coming this way. They've got great technology. We've our engineers love working with their engineers, and now we've got a more competitive dynamic. And like I said, welcome to the jungle. >> We got Red Hat Summit coming up stew. Writerly May is >> absolutely back in Beantown data. >> It's nice. Okay, I'll be in London there, >> right at Summit in Boston And May >> could deal. Mike, Thanks very much for coming. Thank you. It's great to see you. >> Good to see you. >> All right, everybody keep right there. Stew and I would back John Furry is also in the house watching the cube Google Cloud next twenty nineteen we'LL be right back

(upbeat electronic music) >> Narrator: Live from San Francisco, it's The Cube, covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hey, welcome back, everyone. We are here live, The Cube in San Francisco, Moscone West for the Red Hat Summit 2018 exclusive coverage. I'm John Furrier, the cohost of The Cube. I'm here with my cohost, John Troyer, who is the co-founder of Tech Reckoning, an advisory and community development firm. Our next guest is Jonathan Donaldson, Technical Director, Office of the CTO, Google Cloud. Former Cube Alumni. Formerly was Intel, been on before, now at Google Cloud for almost two years. Welcome back, good to see you. >> Good to see you too, it's great to be back. >> So, had a great time last week with the Google Cloud folks at KubeCon in Denmark. Kubernetes, rocking the world. Really, when I hear the word de facto standard and abstraction layers, I start to get, my bells go off, let me look at that. Some interesting stuff. You guys have been part of that from the beginning, with the CNCF, Google, Intel, among others. Really created a movement, congratulations. >> Yeah, thank you. It really comes down to the fact that we've been running containers for almost a dozen years. Four billion a week, we launch and collapse. And we know that at some point, as Docker and containers really started to take over the new way of developing things, that everyone is going to run into that scalability wall that we had run into years and years and years ago. And so Craig and the team at Google, again, I wasn't at Google at this time, but they had a really, let's take what we know from internally here and let's take those patterns and let's put them out there for the world to use, and that became Kubernetes. And so I think that's really the massive growth there, is that people are like, "Wow, you've solved a problem, "but not from a science project. "It's actually from something "that's been running for a decade." >> Internally, that's called bore. That's tools that Google used, that their SRE cyber lab engineers used to massively provision manage. And they're all software engineers, so it's not like they're operators. They're all Google engineers. But I want to take a minute, if you can, to explain. 'Cause you're new to Google Cloud. You're in the industry, you've been around, you helped form the CNCF, which is the Cloud Native Foundation. You know cloud, you know tech. Google's changed a lot, and Google Cloud specifically has a narrative of, they're one big cloud and they have an application called Google stuff and enterprises are different. You've been there now for almost a year or more. >> Jonathan: Little over a year, yeah. >> What's Google Cloud like right now? Break the myths down around Google Cloud. What's the current status? I know personally, a lot of cloud DNA is coming in from the industry. They've been hiring, making some great progress. Take a minute to explain the Google Cloud. >> Yeah, so it's really interesting. So again, it comes back from where you started from. So Google itself started from a scale consumer SAS type of business. And so that, they understood really well. And we still understand, obviously, uptime and scalability really, really well. And I would say if you backtrack several years ago, as the enterprise really started to look at public clouds and Google Cloud itself started to spin up, that was probably not, they probably didn't understand exactly all of the things that an enterprise would need. Really, at that point in time, no one cloud understood any of the enterprise specifically. And so what they did is they started hiring in people like myself and others that are in the group that I'm in. They're former CIOs of large enterprise companies or former VPs of engineering, and really our job in the Office of the CTO for Google Cloud is to help with the product teams, to help them build the products that enterprises need to be able to use the public cloud. And then also work with some of those top enterprise customers to help them adopt those technologies. And so I think now that if you look at Google Cloud, they understand enterprise really, really well, certainly from the product and the technology perspective. And I think it's just going to get better. >> I interviewed Jennifer Lynn, I had a one-on-one with her. I didn't publish it, it was more of a briefing. She runs Product Management, all on security side. >> Jonathan: Yeah, she's fantastic. >> So she's checking the boxes. So the table stakes are set for Google. I know you got to do some basic things to catch up to get in the cloud. But also you have partnerships. Google Next is coming up, The Cube will be there. Red Hat's a partner. Talk about that relationship with Red Hat and partners. So you're very partner-centric with Google Cloud. >> Jonathan: We are. >> And that's important in the enterprise, but so what-- >> Well, there tends to be two main ares that we focus on, from what we consider the right way to do cloud. One of them is open source. So having, which again, aligns perfectly with Red Hat, is putting the technologies that we want customers to use and that we think customers should use in open source. Kubernetes is an example, there's Istio and others that we've put out that are examples of those. A lot of the open source projects that we all take for granted today were started from white papers that we had put out at one point in time, explaining how we did those things. Red Hat, from a partner perspective, I think that that follows along. We think that the way that customers are going to consume these technologies, certainly enterprise customers are, through those partners that they know and trust. And so having a good, flourishing ecosystem of partners that surround Google Cloud is absolutely key to what we do. >> And they love multicloud too. >> They love multicloud. >> Can't go wrong with it. >> And we do too. The idea is that we want customers to come to Google Cloud and stay there because they want to stay there, because they like us for who we are and for what we offer them, not because they're locked into a specific service or technology. And things like Kubernetes, things like containers, being open sourced allows them to take their tool chains all the way from their laptop to their own cloud inside their own data center to any cloud provider they want. And we think hopefully they'll naturally gravitate towards us over time. >> One of the things I like about the cloud is that there's a flywheel, if you will, of expertise. Like I look at Amazon, for instance. They're getting a lot of metadata of the kinds of workloads that are on their cloud, so they can learn from that and turn that into an advantage for them, or not, or for their customers, and how they could do that. That's their business decision. Google has a lot of flywheel action going on. A lot of Android devices connected in the Google system. You have a lot of services that you can bring to bear in the cloud. How are you guys looking at, say, from a security standpoint alone, that would be a very valuable service to have. I can tap into all the security goodness of Google around what spear phishing is out there, things of that nature. So are you guys thinking like that, in terms of services for customers? How does that play out? >> So where we, we're very consistent on what we consider is, privacy is number one for our customers, whether they're consumer customers or whether they're enterprise customers. Where we would use data, you had mentioned a lot of things, but where we would use some data across customer bases are typically for security things, so where we would see some sort of security impact or an attack or something like that that started to impact many customers. And we would then aggregate that information. It's not really customer information. It's just like you said, metadata, themes, or trends. >> John Furrier: You're not monetizing it. >> Yeah, we're not monetizing it, but we're actually using it to protect customers. But when a customer actually uses Google Cloud, that instance is their hermetically sealed environment. In fact, I think we just came out recently with even the transparency aspects of it, where it's almost like the two key type of access, for if our engineers have to help the customer with a troubleshooting ticket, that ticket actually has to be opened. That kind of unlocks one door. The customer has to say, "Yes," that unlocks the other door. And then they can go in there and help the customer do things to solve whatever the problem is. And each one of those is transparently and permanently logged. And then the customer can, at any point in time, go in and see those things. So we are taking customer privacy from an enterprise perspective-- >> And you guys are also a whole building from Google proper, like it's a completely different campus. So that's important to note. >> It is. And a lot of it just chains on from Google proper itself. If you understood just how crazy and fanatical they are about keeping things inside and secret and proprietary. Not proprietary, but not allowing that customer data out, even on the consumer side, it would give a whole-- >> Well, you got to amplify that, I understand. But what I also see, a good side of that, which is there's a lot of resources you're bringing to bear or learnings. >> Yeah, absolutely. >> The SRE concept, for instance, is to me, really powerful, because Google had to build that out themselves. This is now a paradigm, we're seeing a cloud scale here, with the Cloud Native market bringing in all-new capabilities at scale. Horizontally scalable, fully synchronous, microservices architecture. This future is a complete game-changer on functionality at the different scale points. So there's no longer the operator's room, provisioning storage here. >> And this is what we've been doing for years and years and years. That's how all of Google itself, that's how search and ads and Gmail and everything runs, in containers all orchestrated by Borg, which is our version of Kubernetes. And so we're really just bringing those leanings into the Google Cloud, or learnings into Google Cloud and to our customers. >> Jonathan, machine learning and AI have been the big topic this week on OpenShift. Obviously that's a big strength of Google Cloud as well. Can you drill down on that story, and talk about what Google Cloud is bringing on, and machine learning on OpenShift in general? Give us a little picture of what's running. >> Yeah, so I think they showed some of the service broker stuff. And I think, did they show some of the Kubeflow stuff, which is taking some machine learning and Kubernetes underneath OpenShift. I think those are very, very interesting for people that want to start getting into using AutoML, which is kind of roll-your-own machine learning, or even the voice or vision APIs to enhance their products. And I think that those are going to be keys. Easing the adoption of those, making them really, really easy to consume, is what's going to drive the significant ramp on using those types of technologies. >> One of the key touchpoints here has been the fact that this stuff is real-world and production-ready. The fact that the enterprise architecture now rolling out apps within days or weeks. One of those things that's now real is ML. And even in the opening keynote, they talked about using a little bit of it to optimize the scheduling and what sessions were in which rooms. As you talk to enterprises, it does seem like this stuff is being baked into real enterprise apps today. Can you talk a little bit about that? >> Sure, so I certainly can't give any specific examples, because what I think what you're saying is that a lot of enterprises or a lot of companies are looking at that like, "Oh, this is our new secret sauce." It always used to be like they had some interesting feature before, that a competitor would have to keep up with or catch up with. But I think they're looking at machine learning as a way to enhance that customer experience, so that it's a much more intimate experience. It feels much more tailored to whomever is using their product. And I think that you're seeing a lot of those types of things that people are starting to bake into their products. We've, again, this is one of these things where we've been using machine learning for almost 10 years inside Google. Things like for Gmail, even in the early days, like spam filtering, something just mundane like that. Or we even used it, turned it on in our data centers, 'cause it does a really good job of lowering the PUE, which is the power efficiency in data centers. And those are very mundane things. But we have a lot of experience with that. And we're exposing that through these products. And we're starting to see people, customers gravitate to grab onto those. Instead of having to hard code something that is a one to many kind of thing, I may get it right or I may have to tweak it over time, but I'm still kind of generalizing what the use cases are that my customers want to see, once they turn on machine learning inside their applications, it feels much more tailored to the customer's use cases. >> Machine learning as a service seems to be a big hot button that's coming out. How are you guys looking at the technical direction from the cloud within the enterprise? 'Cause you have three classes of enterprise. You have the early adopters, the power, front, cutting-edge. Then you have the fast followers, then you have everybody else. The everybody else and fast followers, they know about Kubernetes, some might not even, "What is Kubernetes?" So you have kind of-- >> Jonathan: "What containers?" >> A level of progress where people are. How are you guys looking at addressing those three areas, because you could blow them away with TensorFlow as a service. "Whoa, wowee, I'm just trying to get my storage LUNs "moving to a cloud operation system." There's different parts of this journey. Is there a technical direction that addresses these? What are you guys doing? >> So typically we'll work with those customers to help them chart the path through all those things, and making it easy for them to use and consume. Machine learning is still, unless you are a stats major or you're a math major, a lot of the algorithms and understanding linear algebra and things like that are still very complex topics. But then again, so is networking and BGP and things like OSPF back a few years ago. So technology always evolves, and the thing that you can do is you can just help pull people along the continuum there, by making it easy for them to use and to provide a lot of education. And so we work with customers on all ends of the spectrum. Even if it's just like, "How do I modernize my applications, "or how do I even just put them into the cloud?" We have teams that can help do that or can educate on that. If there are customers that are like, "I really want to go do something special "with maybe refactoring my applications. "I really want to get the Cloud Native experience." We help with that. And those customers that say, "I really want to find out this machine learning thing. "How can I actually make that an impactful portion of my company's portfolio?" We can certainly help with that. And there's no one, and typically you'll find in any large enterprise, because there'll be some people on each one of those camps. >> Yeah, and they'll also want to put their toe in the water here and there. The question I have for you guys is you got a lot of goodness going on. You're not trying to match Amazon speed for speed, feature for feature, you guys are picking your shots. That is core to Google, that's clear. Is there a use case or a set of building blocks that are highly adopted with you guys now, in that as Google gets out there and gets some penetration in the enterprise, what's the use, what are the key things you see with successes for you guys, out of the gate? Is there a basic building? Amazon's got EC2 and S3. What are you guys seeing as the core building blocks of Google Cloud, from a product standpoint, that's getting the most traction today? >> So I think we're seeing the same types of building blocks that the other cloud providers are, I think. Some of the differences is we look at security differently, because of, again, where we grew up. We do things like live migration of virtual machines, if you're using virtual machines, because we've had to do that internally. So I think there are some differences on just even some of the basic block and tackling type of things. But I do think that if you look at just moving to the cloud, in and of itself is not enough. That's a stepping stone. We truly believe that artificial intelligence and machine learning, Cloud Native style of applications, containers, things like service meshes, those things that reduce the operational burdens and improve the rate of new feature introduction, as well as the machine learning things, I think that that's what people tend to come to Google for. And we think that that's a lot of what people are going to stay with us for. >> I overheard a quote I want to get your reaction to. I wrote it down, it says, "I need to get away from VPNs and firewalls. "I need user and application layer security "with un-phishable access, otherwise I'm never safe." So this is kind of a user perspective or customer perspective. Also with cloud there's no perimeters, so you got phishing problems. Spear phishing's one big problem. Security, you mentioned that. And then another quote I had was, "Kubernetes is about running frameworks, "and it's about changing the way "applications are going to be built over time." That's where, I think, SRE and Istio is very interesting, and Kubeflow. This is a modern architecture for-- >> There's even KubeVirt out there, where you can run a VM inside a container, which is actually what we do internally too. So there's a lot of different ways to slice and dice. >> Yeah, how relevant is that, those concepts? Because are you hearing that as well on the customers? 'Cause that's pain point, but also the new modern software development's future way to do things. So there's pain point, I need some aspirin for that. And then I need some growth with the new applications being built and hiring talent. Is that consistent with how you guys see it? >> So which one should I tackle? So you're talking about. >> John Furrier: VPN, do the VPNs first. >> The VPNs first, okay. >> John Furrier: That's my favorite one. >> So one of the most, kind of to give you the backstory, so one of the most interesting things when I came to Google, having come from other large enterprise vendors before this, was there's no VPNs. We don't even have it on our laptop. They have this thing called BeyondCorp, which is essentially now productized as the Identity-Aware Proxy. Which is, it actually takes, we trust no one or nothing with anything. It's not the walled garden style of approach of firewall-type VPN security. What we do is, based upon the resource you're going to request access for, and are you on a trusted machine? So on one that corporate has given you? And do you have two-factor authentication that corporate, not only your, so what you have and what you know. And so they take all of those things into awareness. Is this the laptop that's registered to you? Do you have your two-factor authentication? Have you authenticated to it and it's a trusted platform? Boom, then I can gain access to the resources. But they will also look for things like if all of a sudden you were sitting here and I'm in San Francisco, but something from some country in Asia pops up with my credentials on it, they're going to slam the door shut, going, "There's no way that you can be in two places at one time." And so that's what the Identity-Aware Proxy or BeyondCorp does, kind of in a nutshell. And so we use that everywhere, internally, externally. And so that's one of the ways that we do security differently is without VPNs. And that's actually in front of a lot of the GCP technologies today, that you can actually leverage that. So I would say we take-- >> Just rethinking security. >> It's rethinking security, again, based upon a long history. And not only that, but what we use internally, from our corporate perspective. And now to get to the second question, yeah. >> Istio, Kubeflow, is more of the way software gets run. One quote from one of the ex-Googlers who left Google then went out to another company, she goes, she was blown away, "This is the way you people ship software?" Like she was a fish out of water. She was like, "Oh my god, where's Borg?" "We do Waterfall." So there's a new approach that opens doors between these, and people expect. That's this notion of Kubeflow and orchestration. So that's kind of a modern, it requires training and commitment. That's the upside. Fix the aspirin, so Identity Proxy, cool. Future of software development architecture. >> I think one of the strong things that you're going to see in software development is I think the days of people running it differently in development, and then sandbox and testing, QA, and then in prod, are over. They want to basically have that same experience, no matter where they are. They want to not have to do the crossing your fingers if it, remember, now it gets reddited or you got slash-dotted way back in the past and things would collapse. Those days of people being able to put up with those types of issues are over. And so I think that you're going to continue to see the development and the style of microservices, containers, orchestrated by something that can do auto scaling and healing, like Kubernetes. You're going to see them then start to use that base layer to add new capabilities on top, which is where we see Kubeflow, which is like, hey, how can I go put scalable machine learning on top of containers and on top of Kubernetes? And you even see, like I said, you see people saying, "Well, I don't really want to run "two different data planes and do the inception model. "If I can lay down a base layer "of Kubernetes and containers, then I can run "bare metal workloads against the bare metal. "If I need to launch a virtual machine, "I'll just launch that inside the container." And that's what KubeVirt's doing. So we're seeing a lot of this very interesting stuff pop. >> John Furrier: Yeah, creativity. >> Creativity. >> Great, talk about your role in the Office of the CTO. I know we got a couple of minutes left. I want to get out there, what is the role of the CTO? Bryan Stevens, formerly a Red Hat executive. >> Yeah, Bryan's our CTO. He used to run a big chunk of the engineering for Google Cloud, absolutely. >> And so what is the office's charter? You mentioned some CIOs, former CIOs are in there. Is it the think tank? Is it the command and control ivory tower? What's the role of the office? >> So I think a couple of years ago, Diane Greene and Bryan Stevens and other executives decided if we want to really understand what the enterprise needs from us, from a cloud perspective, we really need to have some people that have walked in those shoes, and they can't just be Diane or can't just be Bryan, who also had a big breadth of experience there. But two people can't do that for every customer for every product. And so they instituted the Office of the CTO. They tapped Will Grannis, again, had been in Boeing before, been in the military, and so tapped him to build this thing. And they went and they looked for people that had experience. Former VPs of Engineering, former CIOs. We have people from GE Oil and Gas, we have people from Boeing, we have people from Pixar. You name it, across each of the different verticals. Healthcare, we have those in the Office of the CTO. And about, probably, I think 25 to 30 of us now. I can't remember the exact numbers. And really, what our day to day life is like is working significantly with the product managers and the engineering teams to help facilitate more and more enterprise-focused engineering into the products. And then working with enterprise customers, kind of the big enterprise customers that we want to see successful, and helping drive their success as they consume Google Cloud. So being the conduit, directly into engineering. >> So in market with customers, big, known customers, getting requirements, helping facilitate product management function as well. >> Yeah, and from an engineering perspective. So we actually sit in the engineering organization. >> John Furrier: Making sure you're making the good bets. >> Jonathan: Yes, exactly. >> Great, well thanks for coming on The Cube. Thanks for sharing the insight. >> Jonathan: Thanks for having me again. >> Great to have you on, great insight, again. Google, always great technology, great enterprise mojo going on right now. Of course, The Cube will be at Google Next this July, so we'll be having live coverage from Google Next here in San Francisco at that time. Thanks for coming on, Jonathan. Really appreciate it, looking forward to more coverage. Stay with us for more of day three, as we start to wrap up our live coverage of Red Hat Summit 2018. We'll be back after this short break. (upbeat electronic music)

>> Announcer: Live, from Boston, Massachusetts, it's the Cube. Covering Red Hat Summit 2017. Brought to you by Red Hat. (futuristic tone) >> Welcome back to the Cube's coverage of the Red Hat Summit here in Boston, Massachusetts. I'm your host, Rebecca Knight, along with my co-host Stu Miniman. We are welcoming right now Sam Ramji. He is the Vice President of Product Management Google Cloud Platforms. Thanks so much for joining us. >> Thank you, Rebecca, really appreciate it. And Stu good to see you again. >> So in your keynote, you talked about how this is the age of the developer. You said this is the best time in history to be a developer. We have more veneration, more cred in the industry. People get us, people respect us. And yet you also talked about how it is also the most challenging time to be a developer. Can you unpack that a little bit for our viewers? >> Yeah, absolutely. So I think there's two parts that make it really difficult. One is just the velocity of all the different pieces, how fast they're moving, right? How do you stay on top of all the different latest technology, right? How do you unpack all of the new buzzwords? How do you say this is a cloud, that's not a cloud? So you're constantly racing to keep up, but you're also maintaining all of your old systems, which is the other part that makes it so complex. Many old systems weren't built for modernization. They were just kind of like hey, this is a really cool thing, and they were built without any sense of the history, or the future that they'd be used in. So imagine the modern enterprise developer who's got a ship software at high rates of speed, support new business initiatives, they've got to deliver innovation, and they have to bridge the very new with the very old. Because if your mobile app doesn't talk to your mainframe, you are not going to move money. It's that simple. There's layers of technology architecture. In fact, you could think of it as technology archeology, as I mentioned in the keynote, right, this we don't want to create a new genre of people called programmer archeologists, who have to go-- >> I'm picturing them just chipping away. >> Sam: I don't think it'll be as exciting as Indiana Jones. >> No. >> Digging through layers of the stack is not really what people want to be doing with their time. >> Sam: Temple of the lost kernel. >> I love it. >> So Sam, it's interesting to kind of see, I was at the Google Cloud event a couple months ago, and here you bring up the term open cloud, which part of me wants to poke a hole in that and be like, come on, everybody has their cloud. Come on, you want to lock everybody in, you've got the best technology, therefore why isn't it just being open because it's great to say open and maybe people will trust you. Help explain that. >> Puppies, freedom, apple pie, motherhood, right. >> Stu: Yeah, yeah. (laughs) >> So there's a couple sides to that. One, we think the cloud is just a spectacular opportunity. We think about 1.2 trillion dollars in current spend will end up in cloud. And the cloud market depending on how you measure it is in the mid 20 billions today. So there's just unbounded upside. So we don't have to be a aspirational monopolist in order to be a successful business. And in fact, if you wind the clock forward, you will see that every market ends up breaking down into a closed system and a closed company, and an open platform. And the open platforms tend to grow more slowly, sort of exponential versus logarithmic, is how we think about it. So it's a pragmatic business strategy. Think about Linux in '97. Think about Linux in 2002. Think about Linux in 2007. Think about Linux in 2012. Think about Linux today. Look at that rate. It's the only thing that you're going to use. So open is very pragmatic that way. It's pragmatic in another direction which is customer choice. Customers are going to come for things that give them more options. Because your job is to future proof your business, to create what in the financial community call optionality. So how do you get that? In 2011, about eight other people and I created a nonprofit called the Open Cloud Initiative. And the Initiative is long since dead, we didn't fund it right, we kind of got these ideas baked, and then moved on. >> Stu: There's another OCI now. >> That's right, it's the Open Container Initiative. But we had three really crisp concepts there. We said number one, an open cloud will be based on open source. There won't be stuff that you can't get, can't replicate, can't build yourself. Second, we said, it'll have open access. There'll be no barriers to entry or exit. There won't be any discrimination on which users can or can't come in, and there won't be any blockers to being able to take your stuff out. 'Cause we felt that without open access, the cloud would be unsafe at any speed, to borrow a quote from Ralph Nader. And then third, built on an open ecosystem. So if you are assuming that you have to be able to be open to tens of thousands of different ideas, tens of thousands of different software applications, which are maybe database infrastructure, things that as a cloud provider, you might want to be a first party provider of. Well those things have to compete, or trade off or enrich each other in a consistent way, in a way that's fair, which is kind of what we mean when we say open ecosystem, but being able to be pulled through is going to give you that rate of change that you need to be exponential rather than logarithmic. So it's based on some fairly durable concepts, but I welcome you to poke holes in it. >> So we did an event with MIT a little while back. We had Marshall Van Alstyne, professor at BU who I know you know. He's an advisor at Cloud Foundry, and he talked about those platforms and it was interesting, you know, with the phone system you had Apple who got lots of the money, smaller market share as opposed to Android, which of course comes out of Google, has all of the adoption but less revenue. So, not sure it's this, yeah. >> Interestingly, we've run those curves, and you kind of see that same logarithmic versus exponential shift happening in Android. So we've seen, I don't have the latest numbers on the top of my head, but that is generating billions of dollars of third party revenue now. So share does shift over time in favor of openness and faster innovation. >> So let's bring it back to Red Hat here, because if I talk to all the big public cloud guys, Microsoft has embraced open source. >> And they're not just guys, actually, there's lots of women. >> Rebecca: Yes, thank you. >> Stu: I apologize. >> Sorry, I'm in a little bit of a jam here, where I'm trying to tell people the collective noun for technologists is not guys. >> Stu: Okay. >> It could be people, it could be folks, internally we use squirrels from time to time, just to invite people in. >> So, when I talk to the cloud squirrels, Microsoft has embraced open source. Amazon has an interesting relationship. >> I was there when that happened. >> You and I both know the people that they've brought in who have very good credibility in the open source community that are helping out Amazon there. Is it Kubernetes that makes you open because I look at what Red Hat's doing, we say okay, if I want to be able to live across many clouds or in my own data centers, Kubernetes is a layer to do that. It comes back to some of the things like Cloud Foundry. Is that what makes it open because I have choice, or is there more to it that you want to cover from an open cloud standpoint, from a Google standpoint? >> Open and choice effectively is a spectrum of effort. If it's incredibly difficult, it's the same as not having a choice. If it's incredibly easy, then you're saying actually, you really are free to come and go. So Kubernetes is kind of the brightest star in the solar system of open cloud. There's a lot of other technologies, new things that are coming out, like istio and pluri. I don't want to lose you in word soup. Linker D, container D, a lot of other things, because this is a whole new field, a whole fabric that has to come to bear, that just like the internet, can layer on top of your existing data centers or your existing clouds, that you can have other applications or other capabilities layered on top of it. So this permission-less innovation idea is getting reborn in the cloud era, not on top of TCP/IP, we take that for granted, but on top of Kubernetes and all of the linked projects. So yeah, that's a big part of it. >> I want to continue on with that idea of permission-less innovation and talk about the culture of open source, particularly because of what you were saying in the keynote about how it's not about the code, it's about the community. And you were using words like empathy and trust, and things that we don't necessarily think of as synonymous with engineers. >> Sam: Isn't it? >> So, can you just talk a little bit about how you've seen the culture change, particularly since your days at Microsoft, and now being at Google, in terms of how people are working together? >> Absolutely, so the first thing is why did it change? It became an economic imperative. Let's look at software industry competition back in the 90s. In general, the biggest got the mostest. If you could assemble the largest number of very intelligent engineers, and put them all on the same project, you would overwhelm your competition. So we saw that play out again and again. Then this new form of collaboration came around, not just birthed by Linux, but also Apache and a number of other things, where it's like oh, we don't have to work for the same company in order to collaborate. And all of a sudden we started seeing those masses grow as big as the number of engineers who went a single company. Ten thousand people, ten thousand engineers, share the copyright to the Linux kernel. At no point have they worked at the same company. At no point could a company have afforded to get all of them together. So this economic imperative that marks what I think of as the first half of the thirty years of open source that we've been in. The second half has been more us all waking up, and realizing open source has got to be inclusive. A diverse world needs diverse solutions built by diverse people. How do we increase our empathy? How do we increase our understanding so that we can collaborate? Because if we think each other is a jerk, if we get turned off of building our great ideas into software because some community member has said something that's just fundamentally not cool, or deeply hurtful, we are human beings and we do take our toys away, and say I'm not going to be there. >> That's the crux of it too. >> It's absolutely a cutthroat industry, but I think one of the things I'm seeing, I've been in Silicon Valley for 22 years, less three years for a stint at Microsoft, I've actually started to see the community become more self-reflective and like, if we can have cutthroat competition in corporations, we don't have to make that personal. 'Cause every likelihood of open source projects is you're employed as a professional engineer at a company, and that employment agreement might change. Especially in containers, right? Great container developers you'll see they move from one company to another, whether it's a giant company like Google, or whether it's a big startup like Docker, or any range of companies. Or Red Hat. So, this sort of general sense that there is a community is starting to help us make better open source, and you can't be effective in a community if you don't have empathy and you don't start focusing on understanding code of conduct community norms. >> Sam, I'm curious how you look at this spectrum of with this complexity out there, how much will your average customer, and you can segment it anywhere you want, but they say, okay I'm going to engage with this, do open source, get involved, and what spectrum of customers are going to be like, well, let me just run it on Google because you've got a great platform, I'm not going to have Google engineers and you guys have lots of smart people that can do that in any of the platform. How do you see that spectrum of customer, is it by what their business IT needs are, is it the size of the customer, is there a decision tree that you guys have worked out yet to try to help end users with what do they own, what do they outsource? It's in clouds more than outsourcing these days. The deal of outsourcing was your mess for less, and this should be somewhat more transformational and hopefully more business value, right? >> Yeah, Urs Hölzle, who's our SVP of Technical Infrastructure, says, the cloud is not a co-location facility. It is different, it is not your server that you shipped up and you know, ran. It's an integrated set of services that should make it incredibly easy to do computing. And we have tons of very intelligent women and men operating our cloud. We think about things like how do you balance velocity and reliability? We have a discipline called site reliability engineering. We've published a book on it, a community is growing up around that, it's sort of the mainstream version of dev ops. So there are a bunch of components that any company at any size can adopt, as long as you need both velocity and reliability. This has always been the tyranny of the or. If I can move fast I can break things, but even Mark Zuckerberg recently said you know, move fast and break fewer things. Kind of a shift, 'cause you don't want to break a lot of people's experience. How do you do that, while making sure that you have high reliability? It really defies simple classification. We have seen companies from startups to mom and pop shops, all the way to giant enterprises adopting cloud, adopting Google cloud platform. One of the big draws is of course, data analytics. Google is a deeply data intensive business, and we've taken that to eleven basically with machine learning, which is why it was so important to explain tense or flow, offer that as open source, and be able to move AI forward. Any company, at any size that wants to do high speed, high scale data analytics, is coming to GCP. We've seen it basically break down into, what's the business value, how close is it to the decision maker, and how motivated is an engineer to learn something different and give cloud a try. >> Because the engineer has to get better at working with the data, understanding the data, and deriving the right insights from the data. >> You're exactly right. Engineers are people, and people need to learn, and they need to be motivated to change. >> Sam, last question I have for you is, you've been involved in many different projects. We look at from the outside and say, okay, how much should be company driven, how much does a foundation get involved? We've seen certain foundations that have done very well, and others that have struggled. It's very interesting to watch Google. We'd give you good as we've talked on the Cube so far. Kubernetes seems to be going well. Great adoption. Google participates, but not too much, and Red Hat I think would agree with that. So congratulations on that piece. >> Sam: Thank you. >> What's your learnings that you've had as you've been involved in some of these various initiatives, couple foundations. We interviewed you when you were back at the Cloud Foundry, and things like that, so, what have you learned that you might want to say, hey, here's some guidelines. >> Yeah, so I think the first guideline is the core of a foundation is, the core purpose of a foundation is bootstrapping trust. So where trust is missing, then you will need that in order to create better contribution and higher velocity in the project. If there's trust there, if there's a benevolent dictator and everyone says that person's fine or that company's fine, then you won't necessarily need a foundation. You've seen a lot of changes in open source startups, dot coms that are also a dot org, shifting to models where you say well, this thing is actually so big it needs to not be owned by any one company. And therefore, to get the next level of contribution, we need to be able to bring in giant companies, then we create trust at that next level. So foundations are really there for trust. It's really important to be strong enough to get something off the ground, and this is the challenge we had at Cloud Foundry, it was a VMware project and then a Pivotal project, and many people believe this is great open source, but it's not an open community, but the technology had to keep working really well. So we how do we have a majority contributor, and start opening up, in a thoughtful process and bringing people in, until you can say what our target is to have the main contributor be less than 50% of the code commits. 'Cause then the majority is really coming from the community. Other projects that have been around for longer, maybe they started out with no majority. Those organizations, those projects tend to be self-organizing, and what they need is just a foundation to build a place that people can contribute money to, so the community can have events. So there's two very different types of organizations. One's almost like a charity, to say I really care about this popular open source project, and I want to be able to give something back, and others are more like a trade association, which is like, we need to enable very complex coordination between big companies that have a lot at stake, in which case you'll create a different class of foundation. >> Great, well Sam Ramji, thank you so much for being with us here on the Cube. I'm Rebecca Knight, and for your host Stu Miniman, please join us back in a bit. (futuristic tone)

>>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. This is the cubes coverage. Fourth year of Q Khan Cloud native Khan, 2019 Here in San Diego. I am still Minutemen like co host for this afternoon is Justin Warrant and happy to welcome to the program A first time guests, but was on the keynote stage yesterday Sougou Super Marine, who is the co founder and CEO of Planet Scale and also one of the, uh, we're gonna be talking about the test which graduated, announced on the stage. They didn't put a cap and gown or roll everything out, which they did a couple of years ago. But first, thanks so much for joining us. And congratulations. Thank you. All right, so, Sougou, bring us back. You know, we're talking about a cloud native database and we'll dig into that and everything, but bring us back to what you were working on. And you know why of what we now call >>so the When we started with us, we were really not thinking of cloud native itself. for say, it was kind of a sequence of events that kind of forced with us to become cloud native long before cloud native was actually born as even the term was born. Which was when we had to move the test from YouTube on print into Google's board, which use the predecessor off Cooper natives. Um, the reason why the test is kind of one of the leading storage projects in Cloud Native was because it was probably the first project that remained open source, even though we managed to ram it with >>work. Yeah, you know what? One of things we've been talking about at the show here is you know, in the early days, you know, we were very much talking about infrastructure, but we know the reason we have infrastructure is to run applications, and one of the most important applications is databases, and I talk to customers. It's not just one database. Often they have many different databases on, and that is one of the big challenges today. So, you know, you kind of look at that landscape, help us understand how this fits into that. That overall picture. >>Yeah, so that kind of goes back in tow, Google's history and how that can influence kubernetes itself. So if you look at Google's board, most off its features are meant for running stateless application. So within Google, people who wrote applications when they wanted to store state they just called out into a service that was semi part of board but wasn't itself run by board as if you would run your application. So many of those properties were inherited by Cooper natives. So which is the reason why? Um, right from the beginning, it was hard to make storage work for cover natives on Dhe. For that reason, even a zoo recently as early this year, If you look at the tweets from Kelsey Hightower, don't just move your database into communities. You're going to regret it. People still say that, but at the same time, because we test way, we're able to figure out howto make storage work under the stringent rules that Borg had, which was mainly to support stateless applications. In other words, we actually land because, as if it was a stateless application, while still managing while still making state state will not survive this stateless behavior, which is actually why we just managed to be launched within communities as soon as it was born. Ah, but it has been a struggle for other people because they didn't have the luxury of preparing for it without even knowing. Uh so I think that more effort needs to be made on both sides, both from people who are writing storage to make them work with communities as well as kubernetes itself, trying to meet them halfway, trying to add features to help the storage developers. >>It has been a real struggle. I remember from even the very first show I came to four years ago in Seattle looking at the set. My media thing is an ex storage guy and has a backup guy was to go and look at things and say OK, this is lovely for stateless applications, you said. But riel applications have data in them and they need to maintain state. Where's the state looking at all of the group in any type of things, like there were no state full sets with another thing that has changed a lot in four years, and people have come to the party and we need to be able to manage state. But now that you we have a database like a test, isn't that just taking things to the point where I as an app developer, I can just write my stateless application and then my data can live inside a data management service like a test? So I don't actually need to deal with any of that state management problem myself. >>That's what it amounts to. Uh, the the one property of the test is that it can run both in communities and outside. So there are people who run tests on Prem and they have their own orchestration layer. So that has given some challenge where we just cannot depend on communities. You cannot call into communities a p I s o. The way we have the architect of the test is that it knows when it runs within a orchestrated environment, how to interact with it, but it doesn't assume that it exists. So >>why have you provided that functionality? Is that because customers said that I actually want to be able to run the test, But I don't wanna have to deal with kubernetes >>exactly like so not everyone has migrated to communities. It is surprising that everybody wants to migrate communities. But then many of them are saying, I don't know how many years out it is on. Then for them, we just solved a different problem, which is the problem of sheer massive scale ability on dhe for them. They want to be able to still run with us on print s. So for that reason, that is actually a small gap between communities and the test itself. On dhe, we're filling that gap with health charts in the open source on Dhe Planet Scale, which is the company that I founded has built an operator that we're also going to open source so that people can use that to launch community >>before we talk about planet scale You. No, no, no, no. Absolutely. In the keynote you had some customer stories on might might help illustrate some what we're talking about, you know, the scalability of the environment, everything. So you know, I'll let you choose that kind of a short example. You know, the slack One you know, is one that I think president in the audience there. But >>I would choose slack. Ah, Jerry's always obviously enormous, but I will choose slack and nozzle because they represent two very different but really genuine needs in the industry. Slack once not just massive scale, but they want flexibility with manipulating data on DDE. That is something that is manipulating data really, really hard. Onda. We believe that we found the secret sauce to make that work with tests, and that is the reason you saw those statements from Slack. They're so passionate and with so much conviction, that is because they were fascinated by what we could do with their data. So that is one example and slack does not run on communities. They don't run on cloud. They run on AWS, but they don't they run it like they their own claim. They have very fixed I p addresses fixed instance names, but they're on it like a cloud. Sometimes I would say they are more coordinated behavior than some applications that run on kubernetes like they treat everything as disposable. When something goes away, they don't try to recover it or anything destroyed out. Replace it with something new, which is property off cloud native behavior. And on the other hand, a company like nozzle because they're they're actually a startup on dhe. It is surprising that why would the start of one to use? Ah, something that is Mento scale. Massively. That's when we realized that the cloud native nature of it does fills a gap that currently is not filled by many people, which is I want to run everything in Cooper natives all in one. And we didn't realize until they showed us what they did with it, which is, like, completely migrate from one cloud to another. They're a super amazing. And I heard it on dhe. They did that without even telling me are telling anybody in the community because one day I talked to them. They say they are on a key s on. A few days later, I still assumed that they are Nikki s and they know of your booty. Jakey, when did you do this? Oh, we did that last month because we got some really good deal with them, super exciting, >>and that that is a surprising, exactly affected. That's surprising. It is a bit of a concern to me because we hear a lot of talk about multi cloud and the idea of applications being being mobile between different clouds. Data movement is really hot. Exactly. So the fact that someone has actually managed to do that and haven't moved from one community service across to another one is that we find that remarkable because we know it's such a hard problem. But that's one of the great things I think about kubernetes, which is possibly under appreciated, is that it's not that it makes everything easy, but it makes what What used to be hard is now >>possible. Yes, yes, yes, that is very true. Yeah, it's, um uh, like it took It took us a while to, uh, think to make this mind shit, because some of these things, even though they're like it looks, looks looks very obvious. But for the longest time, we were, you're saying, tested for massive scale ability. It's for It's what this and that and even two years ago, up sport came and said, We're going to use the tests for communities orchestration. Weird, but okay, feel free. We don't have a problem with it. And then nozzle came out, and now suddenly you see Oh, this is this is why. And this Saul's really, really difficult problem on. They all did especially hot Spot. Did a lot of work in with tests to actually make it easier. But now we see Now we see the light. >>So Sougou Planet scales the company. Help us understand Vitesse planet scale. How that fits together. What's kind of the business model for your company? >>Yeah. So, um uh, so the test was originally developed at YouTube by you, too. There was one thing That was some pressure. We were beginning to feel when we developed it. We didn't mean for anybody to use it. Really. It was open source, more for academic reasons to show that we can do these things on. But it was interesting when people started adopting it. You're adopting this system. Okay, so we'll see what we can do to help you. But after a while, when the community started growing, some of them were contributing. But definitely storage is a difficult software to write, too. It's not like a pitiful software. Any anybody can understand the cord and start writing. It was obvious that the number of people wanting to use with death and wanting peaches from it are also people that we're not really capable of. writing those features because they're really hard features, too. Right on DDE. That pressure was going and they were saying all I wish you two could do this for me. You know, YouTube is a video company. They're not in the We just did this for ourselves. There's no reason for us to spend so many person years they've left in the future for you. And that time it became obvious that we need to start a company to support this community where there's this huge growing demand, Which is kind of what motivated towards us, uh, thinking about starting planet scale and one requirement waas It cannot remain a YouTube project at that point. So which is why we work it out that way, will actually move it to see NCF. And then I ended up leaving. You do have to start planet scale with my co founder. Then >>so is just from a business standpoint, is that service is on their customers ask for things and fun that that that gets contributed upskirt stream. >>So that was initially what we thought we will do. Initially we thought it was just get out laptops and start helping people that that was our initial thinking. But what we realized was at the same time the industry has shifted towards this new business model which is to actually run everything as a service. And we realized, Oh, my God, years All we have to do is we know how to run with us. You've done it at YouTube. You help people deployed with testing various companies. You know exactly what it takes to run with us. All we have to do is take this. I'm does the service. And that's exactly what people want. Because otherwise, because of the fact that we tested this flexible, it is also extremely complex, too confident because it can run on frame. Then you have to sit all these flags. You runnin carbonate is you said all these flags. So all this has to be managed and we realized, OK, we can manage this and we know exactly how to make it work. And we actually just announced two days ago that our planet scale CNDP Cloud native database is available for people to come in use. >>Well, congratulations on the progress of the business as well as the test graduation and thank you. So much for joining us here on the Cube. Thank you. Alright for Justin Warren. I'm stupid Men. We will be back with more of our day. Two of three days. Whoa! Wall coverage here from San Diego. Thank you for watching the Cube.

>>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 >>Welcome back. This is the cubes. Fourth year of coverage at Q. Khan Cloud, Native Con. We're here in San Diego. It's 2019. I'm stewed. Minutemen, my host for this afternoon is Justin Warren and happy to welcome to guests from the newly minted platinum member of the CNC F Net Up. Sitting to my right is that Baldwin, who is the director of Cloud Native and Communities Engineering and sitting to his right is Rob Bhaskar, who's the product product strategy for Kubernetes. And it's also a board member on the CME CF, thank you both for joining us. Thank you. All right, s O, you know, maybe start with you. You know, uh, you know, companies that No, I've got plenty of history with net up there. What I've been hearing from that up last few years is you know, the Corvette has always been software, and it is a multi cloud world. I've been hearing this message before. Kind of the cloud native Trinity's piece was going, Of course, there's been some acquisitions and met up continuing to go through its transformations if you will s o help us understand kind of net ops positioning in this ecosystem >>in communities. Yes. Okay, so what we're doing is we're building a product that large manage cloud native workloads on top of community. So we've solved the infrastructure problem. And that's kind of the old problem. We're bored to death. Talking about that problem, but we try to do is try to provide a single painting class to manage on premise. Workloads and off permits were close. So that's what we're trying to do. We're trying to say it's now more about the AP taxonomy in communities. And then what type of tooling do you build to manage that that application and communities and says what we're building right now? That's where we're headed with hybrid. >>There's a piece of it, though, that does draw from the historical strength of map, Of course. So we're building way have, essentially already in marketing capability that allows you to deploy communities an agnostic way, using pure, open unmodified kubernetes on all of the major public clouds, but also on trump. But over time and some of this is already evident. You'll see it married to the storage and data management capabilities that we draw from the historical NetApp and that we're starting to deploy into those public clouds >>with the idea that you should be able to take a project. So project being the name space, new space, having a certain application in it. So you have multiple deployments. I should be able to protect that name space or that project. I feel to move that and the data goes with it. So they were very data where that's what we're trying to do with our. Our software is, you know, make it very data. Where have that aligned with APS inside of communities, >>So maybe step back for a second. What? One of the one of things we've heard a few times at this show before and was talking about the keynote this morning is it is project over company when it comes to the C N C F Project Project over company. So it's about the ecosystem. The C in C F tries not to be opinionated, so it's okay for multiple projects to fitness face not moving up to a platinum a sponsor level. You know, participant here, Ned. It's got lots of history's in participating and driving standards, helping move where the industry's going. Where doesn't it up? See its position in, you know, the participating in the foundation and participating in this ecosystem? >>Yeah, So great question, actually. Love it. It's for my favorite topic. So I think the way we look at it is oftentimes, project to the extent they become ubiquitous, define a standard a de facto standard, so not necessarily ratified by some standards body. And so we're very interested in making sure that in a scenario where you would employ the standard from a technology integration perspective, our capabilities can can operate as an implementation behind the standard. So you get the distinguishing qualities of our capabilities. Our products in our service is Visa VI or in the context of the standard. We're not trying to take you down a walled garden path in a proprietary, uh, journey, if you will weigh, would rather actually compel you to work with us on the basis of the value, not necessarily operating off a proprietary set of interface. Kubernetes broadly perceive it as a defacto standard at this point, there's still some work to be done on running out the edges a lot of underway this week. It's definitely the case that there's a new appeal to making this more off herbal by pardon the expression mere mortals way. Think we can offer Cem, Cem, Cem help in that respect as well? >>Yeah, for us, its usability, right? I mean, that's the reason I started stacking. Cloud was that there was usability problem with kubernetes. I had a usability problem. That's what we're trying. That's how I'm looking at the landscape. And I look at kind of all the projects inside the C N c f. And I look at my role is our role is to How do we tie these together? How do we make these? So they're very, very usable to the users. How were engaging with the community is to try to like a line like this, basically pure upstream projects, and create a usability layer on top of that. But we're not gonna we don't want ever say we're gonna fork into these projects what we're gonna contribute back into these. >>That's one concern that I have heard from. Customers were speaking with some of them yesterday. One of the concerns I had was that when you add that manageability onto the base kubernetes layer, that often very spenders become rather opinionated about which way we think this is a good way to do that. And when you're trying to maintain that compatibility across the ecosystem. So some customers saying, Well, I actually don't want to have to be too closely welded to anyone. Vendor was part of the benefit of Kubernetes. I can move my workloads around. So how do you navigate What? What is the right level of opinion? Tohave and which part should actually just be part of a common sense >>should be along the lines of best practices is how we do it. So like, Let's take a number policy, for example, like applying a sane default network policy to every name space defying a saying default pod security policy. You know, building a cluster in the best practices fashion with security turned on hardening done where you would have done this already as a user. So we're not looking you in any way there, so that's we're not trying. I'm not trying to carry any type of opinion in the product we're trying to do is urbanize your experience across all of this ecosystem so that you don't ever have to think about time now building a cluster on top of Amazon. So I gotta worry about how do I manage this on Amazon? I don't want you to think about those providers anymore, right? And then on top of those on top of that infrastructure, I wanna have a way that you're thinking about managing the applications on those environments in the exact same way. So I'm scaling protecting an application on premise in the identical way I'm doing it in the cloud. >>So if it's the same everywhere, what's the value that you're providing? That means that I should choose your option than something else. >>So wait, do have This is where we have controllers and live inside of the clusters that manage this stuff for the user's so you could rebuild what we're doing, But you would have to roll it all by hands, but you could, you know, we don't stand in the way of your operations either. So, like if we go down, you don't go down that idea, but we do have controllers we have. We're using charities. And so, like our management technology, our controllers are just watching for workload to come into the environment. And then we show that in the interface. But you could just walk away as well if you wanted to. >>There's also a constellation of other service is that we're building around this experience, you know, they do draw again from some of the storage and management capabilities. So staple sets your traditional workloads that want to interact with or transact data against a block or a shared file system. We're providing capabilities for sophisticated qualities of persistence that can be can exist in all of those same public clouds. But moreover, over time, we're gonna be in on premises. Well, we're gonna be able to actually move migrate, place, cash her policy. Your put your persistent data with your workload as you move migrate scale burst would repatriate whatever the model is as you move across in between clouds. >>Okay, How how far down that pathway do you think we are? Because 11 criticism of proven it is is that a lot of the tooling that were used to from more traditional ways of operating this kind of infrastructure isn't really there yet. Hence into the question about we actually need to make this easy to use. How far down that pathway away? >>Why would argue that tooling that I've built has already solved some of those problems. So I think we're pretty far down. The people ride down the path. Now what we haven't done is open sourced. You know all my tools, right? To make it easier on everybody else. >>Get up, Scott. Strong partnerships across the cloud platforms. I had a chance to interview George at the Google Cloud event. New partner of the year. I believe some of the stuff help us understand how you know something about the team building. Interact with the public cloud. You look at anthems and azure Arkin. Of course, Amazon has many different ways. You can do your container and management piece there, you know, to talk a little bit of that relationship and how both with those partners and then across those partners, you know, work. >>Yeah, it's a wow. So how much time we have? So so there's certainly a lot of facets to to that, But drawing from the Google experience. We just announced the general availability of cloud volumes on top. So the ability to stand up and manage your own on top instance and Google's cloud. Likewise, we've announced the general availability of the cloud volume service, which gives you manage put fun as a service experience of shared file system on demand. Google, I believe, is either today or yesterday in London. I guess maybe I'll blame that on the time zone covers, not knowing what what day it was. But the point is that's now generally available. Some of those capabilities are going to be able to be connected to our ability from an ks to deploy, uh on demand kubernetes cluster and deploy applications from a market marketplace experience in a common way, not just with Google, but has your with Amazon. And so, you know, frankly, the story doesn't differ a little bit from one cloud to the next, but the the Endeavour is to provide common capabilities across all of them. It's also the case that we do have people that are very opinionated about I want to live only in the Google or that Microsoft of the Amazon, because we're trying to deliver a rich experience for those folks as well, even if you don't value the agnostic multi cloud expert. >>Yeah and Matt, You know, I'm sure you have a viewpoint on this, but you know, it's that skill set that that's really challenging. And I was at the Microsoft show and you've got people you know. It's not just about dot net, there's all that. They're they're embracing and opened all of these environment. But people tend to have the environment that you used to and for multi cloud to be a reality, it needs to be a little bit easier for me to go between them, but it's still we're still we're making progress. But there's work to do. Yeah, s so I just, you know, you know, I know you're building tools and everything, but what what more do we didn't need to do? What were some of the areas that you know you're hopeful for about a >>year before I need to go for the supreme? It's down. It's coming down to the data side like I need to be able to say that on when I turn on data service is inside of kubernetes. I need be able to have that work would go anywhere, right? And because it is a developer. So I have I'm running a production. I'm running an Amazon. But maybe I'm doing test locally on my bare metal environments. Right? I need I want to be able to maybe sink down some of my data. I'm working with a production down to my test environment. That stuff's missing. There's no one doing that right now, and that's where we're headed. That's the path that's where we're headed. >>Yeah. I'm glad you brought that up, actually, because one of the things that I feel like I heard a little bit last year, but it is violated more this year is we're talking a little bit more to the application to the application developer because, you know, communities is a piece of the infrastructure, But it's about the Colonel. Yeah, yeah, yeah. It's the colonel there. So, you know, how do we make sure you know, we're standing between what the APP developer needs and still making sure that, you know, infrastructure is taken care of because storage and networking they're still hard. >>It is. Yeah. Yeah. I mean, I'm I'm approaching. I'm thinking more along the lines of I'm trying to work about app developers personally than infrastructure This point on for me, you know, like so I have I give you a cluster in three minutes, right? So I don't really have to worry about that problem, you know, way also put Theo on top of the clusters. So it's like we're trying to create this whole narrative that you can manage that environment on day one day, two versions. But and that's for like, an I T manager, right? And society instead of our product. How I'm addressing this is you have personas and so you have this concept. You have an I T manager. They do these things that could set limits for the developer who's building the applications or the service's and pushing those up into the environment. They need to have a sense of freedom, right? And said on that side of the house, you know, I'm trying not to break them out of their tooling. So, like wait part of our product ties in to get s o. We have CD, you know? So you just get push, get commit to a branch and weaken target multiple clusters, Right? But no point to the developer, actually, drafty animal or anything. We make way basically create the container for you. Read the deployment, bring it online. And I feel like there's these lines and that I t guys need to be able to say I need to create the guard rails for the Debs. I don't want to make it seem like I'm creating guardrails for the deaths caused the deaths. Don't like that. That's how I'm balancing it. >>Okay, Because that has always been the tension and that there's a lot of talk about Dev ops, but you don't talkto application developers, and they don't wanna have anything to do with infrastructure. They just want a program to an A p I and get things done. They would like this infrastructure to be seamless. Yeah, >>and what we did, like also what I'm giving them is like service dashboards. Because as a developer, you know, because now you're in charge of your cue, eh? You're writing your tests you're pushing. If your c I is going to ct you on your service in production, right? And so we're delivering dashboards as well for service Is that the developers are running, so they dig in and say, Oh, here's an issue or here's where the issue is probably gonna be at I'm gonna go fix this. Yeah, and we're trying to create that type of like scenario for developer and for an I T manager, >>slightly different angle on it, by understanding that question correctly is part of the complexity of infrastructure is something we're also turned Friday deterministic sort of easy button capability, for perhaps you're familiar with them. That's nice. And a C I product, which we we kind of expand that as hybrid cloud infrastructure. If the intention is to make it a simple private cloud capability and indeed are not, a community service operates directly off of it. It's a big part of actually how we deliver Cloud Service is from it. The point is, is that if you're that application developer, if you want the effective and CASS on prom thing, Endeavor with are not a PhD. I product is to give you that sort of easy button extremes because you didn't really want to be a storage admin network at you didn't want to get into the be mired in the details of infra. So So you know, that's obviously work in progress. But we think we're definitely headed down the right direction >>for him. >>Yeah, it just seemed that a lot of enterprises wanna have the cloud like experience, but they want to be able to bring it home that we're seeing a lot more. Yeah. >>So this is like, this turn cheon from this turnkey cloud on premise and played with think has weaken like the same auto scaling. So take so take the dynamic nature of opportunities. Right. So I have a base cluster size of four worker notes, right? But my work, let's gonna maybe maybe need to have more notes. So my out of scale is gonna increase the size my cluster and decrease the size right Pretty much everybody only do that in the public cloud. I could do that in public and on premise now and so that's That's what we're trying to deliver. And that's nickel stuff. I think >>that there's a lot of advantages thio enterprises operating in that way because I have I people that here I can I can go and buy them, hire them and say way, need you to operate this gear and you, you've already done elsewhere. You can do it in cloud. You can do it on side. I could know run my operations the same across no matter where my applications leave, Which saves me a lot of money on training costs on development costs on generally makes for a much more smooth and seamless experience. So, Rob, if you could just love >>your takeaway on, you know, kind of net up participation here at the event and what you want people to take away off from the show this year. >>So it's certainly the case that we're doing a lot of great work. We, like people toe become aware of it. Not up, of course, is not. I think we talked about this and perhaps other context, not strictly a storage and data management company. Only way do draw from the strength of that as we're providing full stack capabilities in a way that are interconnected with public cloud things like are not a Cuban. Any service is really the foundational glue in many ways how we deliver the application run time, but over time will build a consolation of data centric capabilities around that as well. >>I would just love to get your viewpoint Is someone that you know built a company in this ecosystem. There's so many start ups here. Give us kind of that founder viewpoint of being in. They're so sort of ecosystem of the >>ecosystem. So this is how I came into the ecosystem at the beginning. I would have to say that it does feel different. Att This point, I'm gonna speak as Matt, not as now. And so my my thinking has always been It feels a lot like kind of your really your big fan of that rock bands, right? And you go to a local club way all get to know each other at that local club. There's, like maybe 500 of us or 1000 of us. And then that band gets signed a Warner Brothers and goes to the top it. Now there's 20,000 people or 12,000 people. That's how it feels to me right now, I think. But what I like about it is that just shows the power of the community is now at a point where is drawing in like cities now, not just a small collection of a tribe of people, right? And I think that's a very powerful thing with this community. And like all the where they called the kubernetes summits that they're doing way, didn't have any of those back when we first got going. I mean, it was tough to fill the room, you know, Now, now we can fill the room and it's amazing. And what I like seeing is is people moving past the problem with kubernetes itself and moving into, like, what other problems can I solve on top of kubernetes, you know? So you're starting to see that all these really exciting startups doing really need things, you know, and I really likes it like this vendor hall I really like, you know, because you get to see all the new guys. But there's a lot of stuff going on, and I'm excited to see where the community goes in the next five years. But it's we've gone from 0 to 60 insanely because you guys were at the original coupon. I think, Well, >>it's our fourth year doing the Cube at this show, but absolutely we've watched the early days, You know, I'm not supposed to mention open stack of this show, but we remember talking T o J j. And some of the early people there and wait interviewed Chris McCloskey back into Google days, right? So, yeah, we've been fortunate to be on here, really? Day zero here and definitely great energy. So much. Congrats. So much on the progress. Really appreciate the updates, Everything going. As you said, right, we've reached a certain estate and just adding more value on top of this whole >>environment. We're now like we're in, like, Junior high now. Right on were in grade school for a few years. >>All right, Matt. Rob, Thank you so much for the update. Hopefully not an awkward dance tonight for the junior people. For Justin Warren. I'm stupid and back with more coverage here from Q Khan Cloud native 2019. Diego, Thank you for watching Cute

>>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 >>Welcome back, toe Gorgeous. SAN Diego, California This is Q Khan Cloud Native Khan. 29 years. I'm still minimum. My co host is John Troyer, and this is the end of three days water wall coverage over 12,000 and 10 d Having a welcome to the program. Cassie, Who's the executive director at the national headquarters for v. American Red Cross. Matt. Thank you, American Red Cross. And thank you so much for joining us. >>Yeah. Thanks for having me. Uh, it's been a great conference so far. Uh, you know, we're here to share our story where as an end user on our journey with Cloud native with kubernetes Andi how that helps Red Cross do what we do, which is help people in need a cz best we can every day. >>Eso no matter what industry I talked to, everybody's dealing with change. There's always more things happening. American Red Cross. I mean, you know, it feels like I hear American Red Cross mentioned Maur a cz Time goes on because you know everything from, you know, things related to climate through, you know, global events and the like. So maybe before we get into some of the tech, just give us, you know, you know your role there and how kind of the changing world impact your organization. >>Sure. So my role is to support a few different business units. One is biomedical marketing. We try to recruit blood donors, too. Give blood at Red Cross Blood Dot or GE and other channels. That's obviously a significant part of what we d'oh were major player in the blood supply market in the US we provide service is to the armed forces, you know, in that regard as well. So that's part of it. Part of it is I work with humanitarian service is group as well to recruit financial donors on recruit volunteers. That's primarily through Red Cross. That or GE a T least as faras my group goes on, then corporate brand marketing and chapter related marketing and communications. So all that happens through Red Cross that Oregon Red Cross blood dot organ some related platforms on those our flagship brand products. >>Okay, And what led to the American Red Cross being part of this cloud. Native computing, Yeah, system. >>Our journey is a lot like, you know, a lot of other folks. We had a very, you know, monolithic type of architecture. We had all of these different business units with the different priorities, different timelines, different needs wrapped up into one big monster of a platform that, you know, kind of bundled up risk for everybody in this one platform. And, uh, you know, we'd always have collisions of priorities, mostly not to mention the resource issues of who's gonna work, you know, on what? At what time. And so a few years ago, we started talking about breaking that down. And, um, we've been lucky to have some technical leaders that are very aware of and welcoming to new cloud native technologies. We decided at that time to pursue, you know, a cloud native architecture. And what we have today in a few years later, is two years worth of being in production with a platform that runs on Amazon. We take advantage of a lot of the native orchestration tools there for running our clusters. And we've been able to service, you know, those different needs in a much more nimble way. We can release something for a Red Cross blood dot or without risking much on the financial donation side or on the volunteer recruitment side. And likewise, you know, for those other groups, we can kind of separate out the risks for each of those groups. And that's that's been a great, great benefit. >>You've been on the the vendor side. The for profit side is I t very different at the non profit. If you're looking, people are looking down, you get >>higher. Yeah, You know, I have been doing it a long time, a lot of different perspectives. But I think you know what I tried to do. And I would. I think I've seen work best is when I t is not the ticket taker, you know, integrated with the business. I'm very fortunate to have some business partners at Red Cross that collaborate. You know, every day we're having conversations every day. We have some people on our team that feel as though they're accountable for business outcomes, not just, you know, doing cool technology things, you know, For example, you know, multiyear evolution of process related to being more agile. We've got so much more integration and communication with business teams have gone from, you know, something like one release every five months now due to a weak, you know, and I think we could do more. It's just we don't have the need to do more. Um, and that's a huge, huge, big lift. You know, there's a lot of conversations that need to happen. Should make that work. >>Yeah, it's all a journey, right? We're all we're all improved. Continuous improvement, but so follow up there. So as a 90 leader for a very large organization, you know, they're one of the things people are saying this year. Wow. The conference is big. So many new technologies. So many new company somebody open source projects. You know, you're in the middle of this journey. You can't screw it up, right? That would be disastrous. So how do you How do you How did you and your organization look at new technologies and pick out which do technologies to try and incorporate them into your stack and your portfolio? >>Right. So we wanted to be a cloud native. We wanted a do, um, you know, focus on projects that where we knew there were skills in the marketplace, uh, that we could acquire at our price point. You know, we try to be good stewards of donor dollars at the end of the day, you know, all the money we have comes from folks like you and you guys who support Red Cross, you know, and thank you very much for all that generous support. And so we try to spend that money, uh, you know, very carefully. Way have some people who are, uh, you know, employees on our team made about 25 or so. But one of the great things we've been able to do with some of these technologies now is we have a program called Code for Good. It's a volunteer work force where we're here recruiting volunteers with the skill set that you know, they have a day job, but they have an interest in supporting Red Cross. Uh, maybe not financially. Maybe not with their blood, but they can give us some time on their skills, and we run it like an open source project. We set out a road map of features for six months or so. We have planning sessions, we say. Listen, you know if you can sign up for a feature that because you have two hours this week to work. Great. You have six hours. Great. You just had a baby, and you're not available for three months. Fine. You know, we we wanna have a, you know, a bench of people that can self select based on their time commitment, what to work on. And somehow it's been been working Great. You know, we started this in June. We have about 30 volunteers now on. We've already delivered an app for slack. That is kind of a workplace app where you can, you know, if your organization works with us, you can donate right from slack. You can give a schedule of blood donation, appointment, do things like that. >>I love that model. It's something that, you know we've looked at years ago. That kind of micro participation, if you will. You know, You think it's like, you know, Wikipedia wouldn't have been built if it wasn't for everybody. Just spending a little bit of time on it. Uh, I'm curious. Does something like participating with you know, this ecosystem I have generalized tools that people know and can plug in with, as opposed to, you know, having to know your direct stack Is that helpful To kind of be able to recruit people into that environment? What? What are the kind of most needed skills on dhe usages that you're recruiting? >>It is. You are learning. Curve at this point is much smaller than it was on our previous platform Because of the fact that we're using technologies people are familiar with, um, you know, things like Docker we use a lot. We just started evaluating Prometheus, another C N C F project for monitoring some non proud systems. Hopefully that'll graduate into production systems. So from a technology standpoint, yes, yes, we find that, you know, the people we talked with can walk in and be productive sooner. You know, there's still the Red Cross specific things they need to know about how we do business. But, um, you know, at least at this point, is that and not some proprietary system that they also have to learn >>any learnings that you've had participating in the c m. D. F. With the rollout of the technologies that you share with your peers, >>you know, I love the sea. NCF is very maintainer driven, You know, uh, and and user driven. I heard today at one of the analyst panels. I did. I think maybe 30% of people here are end users. >>That's a pretty >>large number. Um, you know, the fact that we can come here and learn about technologies meet people, meat vendors meet some of the people contributing code. Um, it's a lot different than you know, maybe some some summit sponsored by a for profit vendor that wants to, uh, you know, generate leads and sell you things. It feels much more community driven here and open to lots of different perspectives. >>So now what you looking forward to in the next few years? Both in terms of your stack and maybe coming back >>to Cuba? Yeah, way. It's funny. We've started to see other parts of Red Cross come to us toe, learn about kubernetes because the vendors they work with are mentioning these things. And and we have been early adopters, as far as you know, where across goes our group. Um and I think it's great if we can expand usage of, um, cloud native technologies to other parts of the organization on really get some economies of scale. So that's part of what we're trying to do is kind of internal, uh, consulting knowledge sharing collaboration on then, as far as what we're doing on our team way. Just really want to focus on. We're on a stable point in the platform, and then we want to do some things around monitoring and alerting that. Reduce those incident outages, too. Nothing. Hopefully, um, and work on that. >>You're working on a few projects that are that are being worked on here for That >>s So you have this Prometheus project. Like I said, we're piloting that, uh, you know, I would say in four or five months time, we'll know if that's going to be something we can, you know, put some more investment into >>All right, that want to give you the final word. Red cross dot org's code for good. I believe. The web. >>Yes, yes. >>What else? >>Your code for the number four. Good on. You know, if you're interested in volunteering, we need technical skills. We need team leadership skills, product owner skills, eh? So it's not just about you know, developing features and ops engineers as well. So thanks for your time. I want to say hi to my daughter, Peyton. It's late on the East Coast, so go to bed now, but thanks, folks. >>All right. What? Well, Matt, and actually, that is the final word for our day one of coverage for John Troyer. I'm stupid. And be sure to join us tomorrow. We've got two more days water wall coverage here. Lots of great speakers. Really appreciate. We've got the end users on. And, Matt, thank you so much. And, you know, great mission. The code for good. We definitely hope that the community here, you know, reaches out in connection Participates s Oh, that's it for today. Fixes all for watching.

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