>>mhm. Hello and welcome to the cubes Ducker con coverage. I'm John Ferry, host of the Cube. We've got a great segment here with slim dot AI CEO John Amaral. Stealth mode, SAS Company. Start up in the devops space with tools today and open source around. Supply chain security with containers closed beta with developers. John, Thanks for coming on. Congratulations for being platinum sponsor here, Dr Khan. Thanks for coming on The Cube. >>Thanks so much on my pleasure. >>You know, container analysis, management optimisation. You know, that's super important. But security is at the centre of all the action we're seeing with containers. We've been talking shift left on a lot of cube conversations. What that means? Is it an outcome? Is that the product software supply chain? You seek them? A secure where malware. All these things are part of now the new normal in cloud Native. You guys at the centre of this, the surface areas change. All these things are important. Take a minute to explain what you guys are doing as a as a tools and open source. Some of the things you're doing, I know you got a stealth mode product. You probably can't talk about. But you gotta close, Beta. Can you give us a little bit of a teaser? What slim dot ai about >>sure. So someday I is about helping developers build secure containers fast, and that really plays to a few trends in the marketplace that are really apparent and important right now in a federal mandate and a bunch of really highly publicised breaches that have all been caused by software supply, chain risks and security and software supply, chain security has become a really top of mind concept for people who secure things and people who develop software and runs. SAS so slim that AI has built a bunch of capabilities and tools that allow software developers at their desks to better understand and build secure containers that really reduce software supply. Chain risk as you think about containers being run in production. And we do three things to help developers one, as we help them know everything about their software. It's a kind of a core concept of suffering supply chain security. Just know what software is in your containers to. Another core concept is only ship to production. What you need to run. That's all about risk surface and the ability for you to easily make a container small that has as much a software reduction in it as possible. And three, it's removed as many vulnerabilities as possible to Slim Toolset. Both are open source and our SAS data platform make that easy for developers to do >>so. Basically, you have a nice, clean, secure environment. Know what's in there. Don't only put in production was needed and make sure it's tight and it's trimmed down perfectly. So you're kind of teasing out this concept of slimming, which is in the name of the company. But it really is about surface area of attack around containers and super important as it becomes more and more prominent in the environment these days. What is container slimming and why is it important for supply chain security? >>Sure. So in the in the in the realm of software supply chain security, best practises right, there are three core concepts. One is the idea of an S bahn that you should know the inventory of all the software that runs in your world to its security posture, signing containers, making sure that the authenticity of the software that you use and production is well understood. And the third is, well, managing exactly what shopper you ship. The first two things I said are simply just inventory and basics about knowing what software you have. But no one answers the question. What software do I need? So I run a container and say, It's a gig and it's got all these packages in. It comes from the operating system from note, etcetera. It's got all this stuff in it. I know the parts that I write my code to. But all that other stuff, what is it? Why is it there? What's the risk in it? That slimming part is all about managing the list of things you actually shipped to the absolute minimum and with confidence that you know that that code will actually work when it gets production but be as small as possible. That's what slimming is all about, and it really reduces supply chain risk by lowering the attack surface in your container, but also trimming your supply chain to only the minimum pieces you need, which really causes a lot of improvements in in the operational overhead of having software supply chain security >>It's interesting as you get more more volume and velocity around containers, uh, and automation kicks in. Sometimes things are turning on and off you don't even know. And shift left has been a great trend for getting in the CI CD pipeline for developer productivity. Really cool. What are some of the consequences that's going on with this? Because then you start to get into some of these areas like some stuff happens that the developers have to come shift back and can take care of stuff. So, you know, C. Tus and CSOs are really worried about this container dynamic. What's the What's the new thing that's causing the problems here? What's the issue around the management that CDOs and CDOs care about? >>Sure. And I'll talk about the shift left implications as well for that exact point. So as you start to worry about software supply, chain security and get a handle on all the software you ship to prod well, part of that is knowledge is power. But it's also, um, risk and work as soon as I know about problems with my containers or the risk surface, and I got to do something about it so we're really getting into the age where everyone has to know about the software they ship. As soon as you know about that, say there's a vulnerability or a package that's a little risky or some surface area you don't really understand. The only place that can be evaded is by going back to the developers and asking them. What is that? How do I remove it? Please do that work. So the software supply chain security knowledge turns into developer security work. Now the problem is, is that historically, the knowledge was imperfect, and the developer, you know, involvement in that was, I'd say, at Hawk, meaning that developers had best practises that did the best they could. But the scrutiny we have now on minimising this kind of risk is really high. The beautiful part about containers is their portable, and it's an easily transferrable piece of software. So you have a lot of producers and a lot of consumers of containers. Consumers of containers that care about supply chain risk are now starting to push back on, producers saying, Take those vulnerabilities out, move those packages, make this thing more secure, lower the risk profile this works its way all the way back to the developers who don't really have the tools, capabilities and automation is to do the work I just described easily, and that's an opportunity that Slim is really addressing, making it easy for developers to remove risk. >>And that's really the consequences of shifting left without having the slimming. Because what you're saying is your shift left and that's kind of annulled out because you've got to go back and fix it. The work comes, >>that's right. And yeah, and it's not an easy task for a developer to understand the code that they didn't intentionally put in the container. It's like, Okay, there's a package in that operating system. What does it do? I don't know. Do I even use it? I don't know. So there's like tonnes of analytic and I would say even optimisation questions and work to be done, but they're just not equipped to, because the tooling for that is really immature Slims on a mission to make that really easy for them and do it automatically so they don't have to think about it. We just automatically remove stuff you don't use and voila! You've got this like perfectly pre optimised capability. >>You know, this suffer supply chain is huge, and I remember when open source started when I remember when I was breaking into the business. Now it's such a height in such an escalation of new developers. This it's a real issue that that's going to be resolved. It has to be because supply chain is part of open source, right? As more code comes in, you got to verify. You gotta make sure it's it's slimming where it needs to be slim and optimised. There needs to be optimised, huge trend. Um and so I just love this area. I think it's really innovative and needed. So congratulations on that, you know, have one more question for you before we get into to close out. Um, you guys are part of the Docker Extensions launch and your partner, >>Why >>is this important to participate in this programme and and what do you guys hope to hope it does for slim dot ai, >>First of all, doctors, the ubiquitous platform, their hub has millions and millions of containers. We've got millions and millions of developers using Docker desktop to actually build and work on containers. It's like literally the sandbox for all local work for building containers. It's a fair statement. So inclusion in Dr Khan and the relationship we're building with Docker is really important for developers and that we're bringing these capabilities to the place where developers work and live every day. It's where all the containers live in the world. So we want to have our technology be easy to use with docker tools. We want to keep developers workflows and systems and and tools of record be the same. We just want to help them use those tools better and optimist outputs. From that we've we've worked since our inception to make our tools really, really friendly for darker and darker environments to, um, we are building a doctor extension. Uh, they have, uh, in this darker con. They're launching their doctor extensions programme to the worldwide audience. We have been one of the lucky Cos that's been selected to build one of the early Dr desktop plug ins. It's derived from our capabilities and our Saas platform and an open source, and it's it's effectively an MRI machine, an awesome analytic tool that allows any developer to really understand the composition, security and profile of any container they work with. So it's giving the sight to the blind, so to speak, that it's this new tool to make container analysis easy. >>Well, John, you guys got a great opportunity. Container analysis, management, optimisation key to security, enabling it and maintaining and sustaining it. And it's changing. I know you guys. Your co founder also did a doctor Slim. So you guys are deep in the open source. I Congratulations on that. We'll see a Q. Khan for the remaining time. We have give a plug for the company, obviously in stealth mode price going to come out later this year. You got a developer preview? What's What's the company all about? What's the most important story here? Dr. Khan? >>Sure, just to playback. So we help developers do three important things. Know everything about the software in their containers to only ship stuff to production that you need, and and and three remove as many vulnerabilities as possible. That's really about managing and understanding the risk surface. It ties right back to software supply chain security, and any developer can use these tools today to emit and build containers that are more secure and better production grade containers, and it's easy to do. We have an open source project called Dioxin. Go check it out. Uh, it's not. It's on git Hub. It's easy to find if you go to w w w dot slim that ai you can find access to that. We have tens of thousands of developers, 500,000 plus downloads. We have developers everywhere using those tools today and open source to do the objectives. I just said You can also easily sign up for our data for our Saas platform, you can use the doctor extension, go ahead and do that and really get on your journey to make those outcomes reality for you. And really kind of make those SEC ops people downstream not have to shift anything left. It's super easy for you to be a great participant in software slash insecurity. >>All right. John Amaral, CEO slim dot ai Stealth. Most thanks for coming The Cube Cube coverage of Dr Khan. Thanks for watching. I'm John Kerry hosted the Cube back to more Dr Khan after the short break. Mhm mhm

>>mhm. What the special cube conversation here in Palo alto, I'm john Kerry host of the cube. We're here talking about kubernetes Cloud native and all things Cloud, cloud enterprise amir Sure VP of product and morgan Stanley is with me and we are great to have you on the cube. Thanks for coming on. I appreciate you taking the time, >>appreciate it, john good to be here. You >>know, cloud Native obviously super hot right now as the edges around the corner, you're seeing people looking at five G looking at amazon's wavelength outposts you've got as you got a lot of cloud companies really pushing distributed computing and I think one of the things that people really are getting into is okay, how do I take the cloud and re factor my business and then that's one business side then, the technical side. Okay, How do I do it? Like it's not that easy. Right. So it sounds, it sounds really easy to just go to move to the cloud. This is something that's been a big problem. So I know you guys in the center of all this uh and you've got, you know, microservices, kubernetes at the core of this, take a minute to introduce the company, what you guys do then I want to get into some specific questions. >>Mhm, of course. Well, bob Sani is a startup? Silicon Valley startup and what we do is automate system configuration that's typically worked at an engineer does and take lengthy and if done incorrectly at least to a lot of errors and cost overruns and the user experience problems. We completely automate that using an Ai and ml back end so that the engineering can focus on writing code and not worry about having to tune the little pieces working together. >>You know, I love the, I was talking to a V. C on our last uh startup showcase, cloud startup showcase and uh really prominent VC and he was talking about down stack up stack benefits and he says if you're going to be a down stack um, provider, you got to solve a problem. It has to be a big problem that people don't want to deal with. So, and you start getting into some of the systems configuration when you have automation at the center of this as a table stakes item problems are cropping up as new use cases are emerging. Can you talk about some of the problems that you guys see that you solve for developers and companies, >>of course. So they're basically, they're, the problem expresses itself in a number of domains. The first one is that he who pays the bills is separate from he who consumes the resources. It's the engineers that consume the resources and the incentives are to deliver code rapidly and deliver code that works well, but they don't really care about paying the bills. And then the CFO office sees the bills and there's a disparity between the two. The reason that creates a problem, a business problem is that the developers uh, will over provision stuff, uh to make sure that everything works and uh, they don't want to get caught in the middle of the night. You know, the bill comes due at the end of the month or into the quarter and then the CFO has smoke coming out of his ears because there's been clawed overruns. Then the reaction happens to all right, let's cut costs. And then, you know, there's an edict that comes down that says everything, reduce everything by 30%. So people go across and give a haircut to everything. So what happens next to systems out of balance? There's allocation resource misallocation and uh, systems start uh, suffering. So the customers become unhappy. And ironically, if you're not provisioned correctly, Not ironically, but maybe understandably, customers start suffering and that leads to a revenue problem down the line if you have too many problems unhappy. So you have to be very careful about how you cut costs and how you apportion resources. So both the revenue side is happy and it costs are happy because it all comes down to product experience and what the customers consume. You >>know, that's something that everyone who's done. Cloud development knows, you know, whose fault is it? You know, it's this fall. But now you can actually see the services you leave a switch open or, you know, I'm oversimplifying it. But, you know, you experiment services, you can the bills can just have massive, you know, overruns and then, and then you got to call the cloud company and you gotta call the engineers and say why did you do this? You got to get a refund or or the bad one. Bad apple could ruin it for everyone as you, as you highlighted over the bigger companies. So I have to ask you mean everyone lives this. How do companies have cost overruns? Is their patterns that you see that you guys wrote software 4-1, automate the obvious ones. Is there is there are certain things that you know always happen. Are there areas that have some indications? So why do, first of all, why do companies have cloud cost overruns? >>That's a great question. And let's start with a bit of history where we came from a pre cloud world, you built your own data centers, which means that you have an upfront Capex cost and you spend the money and you were forced to live within the needs that your data center provided. You really couldn't spend anymore. That provided kind of a predictable expenditure bottle it came in big chunks. But you know what, your budget was going to be four years from now, three years from now. And you built for that with the cloud computing, Your consumption is now on on demand basis and it's api enabled. So the developer can just ask for more resources. So without any kind of tools that tell the developer here is x amount of CPU or X amount of memory that you need for this particular service, that for it to deliver the right uh, performance that for the customer. The developers incentivized to basically give it a lot more than the application needs. Why? Because the developer doesn't want to pick up service tickets. He's incentivizing delivering functionality quickly and moving on to next project, not in optimizing costs. So that creates kind of uh an agency problem that the guy that actually controls how research are consumed is not incentivized to control the consumption of these resources. And we see that across the board in every company, engineers, engineering organization is a separate organization than the financial organization. So the control place is different. The consumption place and it breaks down the patterns are over provisions. And what we want to do is give engineers the tools to consume precisely the right amount of resources for the service level objectives that they have, given that you want a transaction rate of X and the literacy rate of Why here's how you configure your cloud infrastructure. So the application delivers according to the sls with the least possible resources consumed. >>So on this tool you guys have in the software you guys have, how how do you guys go to mark with that, you target the business buyer or the developer themselves and and how do you handle the developers say, I don't want anyone looking over my shoulder. I'm gonna go, I'm gonna have a blank check to do whatever it takes, um how do you guys roll that out because actually the business benefits are significant controlling the budget, I get that. Um how do you guys rolling this out? How do people engage with you? What's your strategy? >>Right. Are there, is the application owner, is the guy that owns the PML for the application? It tends to be a VP level or a senior director person that owns a SAAS platform and he or she is responsible for delivering good products to the market and delivering good financial results to the CFO So in that person of everything is rolled up, but that person will always favor the revenue site, which means consume more resources than you need in order to maximize customer happiness, therefore faster growth and uh they do that while sacrificing the cost side. So by giving the product owner the optimization tools autonomous of optimization tools that Sandy has, we allow him or her to deliver the right experience to the customer, with the right sufficient resources and address both the performance and the cost side of equation simultaneously, >>awesome. Can you talk about the impact c I C D s having in the cloud native computing on the optimization cycle? Um Obviously, you know, shifting left for security, we hear a lot of that, you're hearing a lot of more microservices being spun up, spun down automatically. Uh I'll see kubernetes clusters are going mainstream, you start to see a lot more dynamic uh activity if you if you in these new workflows, what is the impact of these new CSC D cloud? Native computing on the optimization cycle? >>C i c D is there to enable a fast delivery of software features basically. Uh So, you know, we have a combination of get get ups where you can just pull down repositories, libraries, open source projects from left and right. And using glue code, developers can deliver functionality really quick. In fact, microservices are there in service of that capability, deliver functionality quickly by being able to build functional blocks and then through a piece you put everything together. So ci cd is just accelerates the software delivery code. Between the time the boss says, give me an application until the application team plus the devops team plus SRE team puts it out in production. Now we can do this really quickly. The problem is though, nobody optimizes in the process. So when we deliver 1.0 in six months or less, we've done zero in terms of optimization and at one point, oh, becomes a way that we go through QA in many cases, unfortunately. And it also becomes a way that we go through the optimization. The customer screams that you eyes Laghi, you know, the throughput is really slow and we tinker and tinker and tinker and by the time it typically goes through a 12 month cycle of maturation, we get that system stability in the right performance with a I and machine learning that a person has enabled. We can deliver that, we can shrink that time out considerably. In fact, uh you know what we're going to announce in q khan is something that be called Kite storm is the ability to uh install our product and kubernetes environment in roughly 20 minutes and within two days you get the results. So before you have this optimization cycle that was going on for a very long time now that it's frank down and because of Ci Cd, you know, you don't have the luxury of waiting and the system itself can become part of the way of contributing system. The system being the uh ai ml service, that the presiding deliveries can be uh part and parcel of the Ci cd pipeline, that optimizes the code and gives you the right configuration and you get to go. So >>you guys are really getting down and injecting in some uh instrumentation for metadata around key areas. That right. Is that kind of how it's working? Are you getting in there with codes going to watch? Um how was it working under the hood? Can you just give me a quick example of, you know, how this would play out and what people might expect, how it would handle, >>of course. So what the way we optimize application performance is we have to have a metric against which we measure performance. That metric is an S L O service level, objective and in a kubernetes environment, we typically tap into Prometheus, which is the metrics gathering place metrics database for kubernetes workloads and we really focus on red metrics, the rate of transactions, the error rate and the for delay or latency. So we focus on these three metrics and what we have to do is inject a small container, it's an open source container into the application work space that we call that a container. Servo. Servo interacts with Prometheus to get the metrics and then it talks to our back end to tell the M L engine what's happening and then L engine and does this analysis and comes back with a new configuration which then servo implements in a canary instance. So the Canary instances where we run our experiments and we compare it against the main line, Which the application is doing after roughly 20 generations or so. The Bellingen Learns what part of the problem space to focus on in order to optimize to deliver optimal results. And then it very quickly comes to the right set of solutions to try and it tries those inside uh inside the canary instance and when it finds the optimal solution, it gives the recommendation back to the application team or alternatively, when you have enough trust in the tiny you can ought to promote it into mainline that >>gets the learning in there is a great example of some cloud native action. I want to get into some examples with your customer, but before we get there, I want to ask you, since I have you here, if you don't mind, what is cloud native mean these days, because you know, cloud native become kind of much cloud computing, um which essentially go move to the cloud, but as people start developing in the cloud where there's real new benefits, people talk about the word cloud native, could you take a quick minute to define? What is cloud Native, Does that even mean? What does cloud native mean? >>I'll try to give you my understanding government, we could get into a bit of philosophy. Uh Yeah, that's good. But basically cloud Native means it's, your application is built for the cloud and it takes advantages of the inherent benefits that a cloud environment can give you, which means that you can grow and shrink resources on the fly, if you built your application correctly, that you can scale up and scale down, you're a number of instances very quickly and uh, everything has taken advantage of a P I S so initially that was kind of done inside of the environment. Uh AWS Ec two is a perfect example of that. Kubernetes shifted cloud native to container its workload because it allows for rapid, more, rapid deployment and even enables or it takes advantage of a more rapid development cycle as we look forward. Cloud Native is more likely to be a surplus environment where you write functions and the backend systems of the cloud service provider, just give you that capability and you don't have to worry about maintaining and managing a fleet of any sort, whether it's VMS or containers, that's where it's gonna go. Currently we are to contain our space >>so as you start getting into the service molly good land, which we've been playing with, loves that as you get into that, that's going to accelerate more data. So I gotta ask you as you get into more of this this month, I will say monitoring or observe ability, how we want to look at it. You gotta get at the data. This becomes a critical part of solving a lot of problems and also making sure the machine learning is learning the right thing. How do you view that you guys over there? Because I think everyone is like getting that cloud native and it's not hard sell to say that's all good, but we can go back, you know, the expression ships created ships and then you have shipwrecks, you know, there's always a double edged sword here. So what's the downside? If you don't get the data right? >>Uh well, so the for us, the problem is not too much data, it's lack of data. So if you don't get data right is you don't have enough data. And the places where optimization cannot be automated is where the transaction rates are slow, where you don't have enough fruit. But coming into the application and it really becomes difficult to optimize that application with any kind of speed. You have to be able to profile the application long enough to know what moves its needle and in order for you to hit the S. L. O. Targets. So it's not too much data, it's not enough data. That seems to be the problem. And there are a lot of applications that are expensive to run but have a low throughput. And I would uh in all cases actually in every customer environment that have been in, where that's been the case if the application is just over provision, if you have a low throughput environment and it's costing too much, don't use ml to solve it. That's a wrong application of the technology. Just take a sledgehammer and back your resources by 50%, see what happens. And if that thing breaks back it again, until you find the baggage point. >>Exactly for you over prison, you bang it back down again. It's like the old school now with the cloud. Take me through some examples when you guys had some success, obviously you guys are in the right area right now, you're seeing a lot of people looking at this area to do that in some cases like changing the whole data center and respect of their business. But as you get it with customers with the app side, what some successes can you share some of the use cases, what you guys are being successful, your customers can get some examples. >>Yeah. So well known financial software for midsize businesses that that does accounting. It's uh there are customer during a large fleet and this product has been around for a while. It's not a container ice product. This product runs on VMS. Angela is a large component of that. So the problem for this particular vendor has been that they run on heterogeneous fleet that the application has been a along around for a very long time. And as new instance types on AWS have come in, developers have used those. So the fleet itself is quite heterogeneous and depending on the time of the day and what kind of reports are being run by organisations, they, the mix of resources that the applications need are different. So uh when we started analyzing the stack, we started we started looking at three different tiers, we looked at the database level, we looked at the job of mid tier and we looked at the web front end. And uh one of the things that became counterproductive is that m L. Discovered that using for the mid tier using larger instances but fear of a lot for better performance and lower cost and uh typically your gut feel is to go with smaller instances and more of a larger fleet if you would. But in this case, what the ML produced was completely counter intuitive And the net result for the customer was 78% cost reduction while agency went down by 10%. So think about it that you're, the response time is less, uh 10% less but your costs are down almost 80% 78% in this case. And the other are the fact that happened in the job of mitt here is that we improve garbage collection significantly and because whenever garbage collection happens on a JV M it takes a pause and that from a customer perspective it reflects as downtime because the machines are not responding so by tuning garbage collection Andrzej VMS across this very large fleet we were able to recover over 5000 minutes and month across the entire fleet. So uh, these are some substantial savings and this is what the right application of machine learning on a large fleet can do for assess business. >>And so talk about this fleet dynamic, You mentioned several lists. How do you see the future evolving for you guys? Where are you skating to where the puck is? As the expression goes? Um obviously with server list is going to have essentially unlimited fleets potentially That's gonna put a lot of power in the hands of developers. Okay. And people building experiences, What's the next five years look like for you guys? >>So I'm looking at the product from a product perspective, the service market depends on the mercy of the cloud service provider and typically the algorithms that they use. Uh basically they keep very few instances warm for you until you're the rate of api calls goes up and they start they start uh start turning on VMS are containers for you and then the system becomes more responsive over time. One place that we can optimize the service environment is give predictability of what the cyclicality of load is. So we can pre provision those instances and warm up the engine before the loads come into the system always stays responsive. You may have noticed that some of your apps on your phone that when you start them up, they may have a start up like a minute or two. Especially if it's a it's a terror gap. What's happening in those cases that you're starting an api calls goes in containers being started up for you to start up that instance, not enough of our warm to give you that rapid response. And that can lead to customer churn. So by by analyzing what the load on the overall load of the system is and pre provision the system. We can prevent the downtime uh prevent the lag to start up black on the downside. Which when you know when the usage goes down, it doesn't make sense to keep that many instances up. So we can talk to the back in infrastructure and the commission of those VMS in order to make to prevent cost creeps basically. So that's one place that we're thinking about extending our technology. >>So it's like, it's like the classic example where people say, oh during black monday everyone searches to do e commerce. You guys are thinking about it on A level that's a user centric kind of use case where you look at the application and be smart about what the expectation is on any given situation and then flex the resources on that. Is that right? That by getting right? So if it's your example, the app is a good one. If I wanted to load fast, that's the expectation. It better load fast. >>Yes, that's exactly but more romantic. So I use valentine's day and flowers my example. But you know, it doesn't have to be annual cycles. It can be daily cycles or hourly cycles. And all those patterns are learning about by an Ml back in. >>Alright, so I gotta ask you love the, this, this this new concept because most people think auto scaling right? Because that's a server concept. Can auto scale or database. Okay. On a scale up, you're getting down to the point where, okay, we'll keep the engines warm, getting more detailed. How do you explain this versus a concept like auto scaling. Is it the same as a cousins? >>They're they're basically the way they're expressed, it's the same technology but their way there expressed is different. So uh in a cooper native environment, the H. B A is your auto scaler basically in response to the need, response more instances and you get more containers going on. What happens as services? Less environment is you're unaware of the underpinnings that do that scale up for you. But there is an auto Scaler in place that does that scale up for you. So the question becomes that we're in a stack from a customer's perspective, are you talking about if you imagine your instances we're dealing with the H. B. A. If you're managing at the functional level we have to have api calls on the service provider's infrastructure to pre warm up the engine before the load comes. >>I love I love this under the hood is kind of love new dynamics kind of the same wine, new bottle but still computer science, still coding, still cool and relevant to make these experiences great. Thanks for coming on this cube conversation. I really appreciate it. Take a minute to put a plug in for the company. What are you guys doing in terms of status funding scale employees, what are you looking for? And if someone's watching this and there should be a customer of you guys, what what's, what's, what's going on in their world? What tells them that they need to be calling you? >>Yeah, so we're serious. Dave we've had the privilege of uh, our we've been privileged by having a very good success with large enterprises. Uh, if you go to our website, you'll see the logos of who we have, we will be at Q khan and there were going to be actively targeting the mid market or smaller kubernetes instances, as I mentioned, it's gonna take about 20 minutes to get started and we'll show the results in two hours. And our goal is for our customers to deliver the best user experience in terms of performance, reliability. Uh, so that they, they delight their customers in return and they do so without breaking the bank. So deliver excellent products, do it at the most efficient way possible, deliver a good financial results for your stakeholders. This is what we do. So we encourage anybody who is running a SAS company to come and take a look at us because we think we can help them and we can accelerate there. The growth at the lower cost >>and the last thing people need is have someone coming breathing down their necks saying, hey, we're getting overcharged. Why are you guys screwing up when they're not? They're trying to make a great experience. And I think this is kind of where people really want to do push the envelope and not have to go back and revisit the cost overruns, which if it's actually a good sign if you get some cost overruns here and there because you're experimenting. But again, you don't want to get out of control. >>You don't want to be a visual like the U. S. Debt. >>Exactly. I'm here. Thank you for coming on. Great. We'll see a coupe con. The key will be there in person is a hybrid event. So uh, coupon is gonna be awesome and thanks for coming on the key. Appreciate it. >>John is a pleasure. Thank you for having me on. >>Okay. I'm john fryer with acute here in Palo alto California remote interview with upsetting hot startup series. I'm sure they're gonna do well in the right spot in the market. Really well poisoned cloud Native. Thanks for watching. Yeah.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America. 2020. Virtual Brought to You by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners. Hey, welcome back, everybody. Jeffrey here with the Cube coming to you from our Palo Alto studios with our ongoing coverage of Q. Khan Cloud, Native Con 2020 North America. Of course, it's virtual like everything else is in 2020 but we're excited to be back. It's a terrific show, and we're excited our next guest. So let's introduce him. And we've got Sam Warner, the VP of offering manager and business line executive for storage for IBM. Sam. Great to see you. >>Great to be here. >>And also joining us is Brent Compton. He's a senior director of data services for Redhead. Great. See you, Brent. >>Thank you. >>So let's let's jump into it. Cloud Native. Everything's about cloud native. Everything's about containers. Everything is about kind of container ization and flexibility. But then there's this thing in the back and called storage. We actually have toe keep this stuff and record this stuff and have data protection for this stuff in business resiliency love to jump into it, so lets you know where does storage fit within a container world? And how is the growth of containers and the adoption containers really had you rethink the way that you think about storage and how clients you think about stories saying, Let's start with you >>e mean, it's a great question. And first off, I'm really excited about another cube con. Uh, we did Europe now, uh, doing North America so very excited to be, you know, seeing all the you know, all the news and all the people talking about the advancements around kubernetes. And we're very excited about it now. You asked a very good question. Important question. We're seeing an acceleration of digital transformation, and the people that are going through this digital transformation are using containers to now modernize the rest of their infrastructure. The interesting thing about it, though, is those initiatives are being driven out of the application teams. The business lines in an organization, and a lot of them don't understand that there's a lot of complexity to this storage piece here. So the storage teams I talked to are all of a sudden getting these initiatives thrown on them or a kind of halfway their strategy. And they're scratching their heads, trying to figure out now how they can support these applications with persistent storage. Because that's not where containers started. They started with micro services, and now now they're in a quandary. They have to deliver a certain S L. A to their customers, and they're trying to figure out how they do it in this new environment, which in a lot of cases, has been designed outside of their scope. So they're seeing issues with data protection. Some of the kind of core things that they've been dealing with for years are now. They're now having to solve all over again. So that's what we're working on helping them with reinventing how storage is deployed to help them deliver the same level of security, availability and everything they have in the past. Uh, in these new environments, >>right? So, yeah, e say you've been involved in this for a long time. You know, you've worked in hyper converge. You've worked in big data. You know, the evolution of big data continues to change, as ultimately we want to get people the information to make good decisions, but we've gone through a lot of integrations over the years. So how is it different? You know? Now how is it different with containers? What can we finally do you as a as an architect that we couldn't do before? >>Infrastructure is code. That's, I think, one of the fundamental differences of the storage admin of yesteryear versus storage admin of today today, Azaz Sam mentioned As people are developing and deploying applications, those applications need to dynamically provisioned the infrastructure dynamically provisioned what they need from compute dynamically provisioned what they need from storage dynamically provisioned network paths and so that that that element of infrastructure is code. A dynamically provisioned infrastructure is very different from well from yesterday, when applications or teams needed to. Well, when they needed storage, they would you know, they would file a ticket and typically wait. Now they make an a p A. Now they make an A p. I call and storage is dynamically provisioned and provided to their application. >>But what what I think hard to understand for the layman. And maybe it's just me, right? I It's very easy to understand dynamic infrastructure around, um compute right, I'm Pepsi. I'm running it out for the Super Bowl. I need I know how much people are gonna hit by hit my site and it's kind of easy to understand. Dynamic provisioning around networking again for the same example. What's less easy to understand its dynamic provisioning for storage? It's one thing to say, you know, there's a there's a pool of storage resource is that I'm going to dynamically provisioned for this particular after this particular moment. But one of the whole things about the dynamic is not only is it available when you need it, but I could make it big, and conversely, I could make it smaller go away. I get that for servers, and I kind of get that for networking, supporting an application and that example I just talked about. But we can't It doesn't go away a lot of the time for storage, right? That's important data that's maybe feeding another process. There's all kinds of rules and regulations, So when you talk about dynamic infrastructure for storage, it makes a lot of sense for grabbing some to provision for some new application. But it's >>hard to >>understand in terms of true dynamics in terms of either scaling down or scaling up or turning off when I don't particularly need that much capacity or even that application right now, how does it work within storage versus No, just servers or I'm grabbing them and then I'm putting it back in the pool. >>Let me start on this one, and then I'm gonna hand it off to Brent. Um, you know, let's not forget, by the way, that enterprises have very significant investments in infrastructure and they're able to deliver six nines of availability on their storage. And they have d are worked out in all of their security, encryption, everything. It's already in place, and they're sure that they can deliver on their SLS. So they want to start with that. You have to leverage that investment. So first of all, you have to figure out how to automate that into the environment, that existing sand, and that's where things like uh, a P I s the container storage interface CS I drivers come in. IBM provides that across your entire portfolio, allowing you to integrate your storage into a kubernetes environment into an open shipped environment so that it can be automated, but you have to go beyond that and be able to extend that environment, then into other infrastructure, for example, into a public cloud. So with the IBM flash system, family with our spectrum virtualized software were actually able to deploy that storage layer not only on Prem on our award winning a race, but we can also do it in the cloud. So we allow you to take your existing infrastructure investments and integrate that into your communities environment and using things like danceable, fully automated environment. I'll get into data protection before we're done talking. But I do want Brent to talk a bit about how container native storage comes into that next as well. On how you can start building out new environments for, uh, for your applications. >>Yeah, What the two of you are alluding to is effectively kubernetes services layer, which is not storage. It consumes storage from the infrastructure, Assam said. Just because people deploy Kubernetes cluster doesn't mean that they go out and get an entirely new infrastructure for that. If they're deploying their kubernetes cluster on premises, they have servers. If they're deploying their kubernetes cluster on AWS or an azure on G C P. They have infrastructure there. Uh, what the two of you are alluding to is that services layer, which is independent of storage that can dynamically provisioned, provide data protection services. As I mentioned, we have good stuff to talk about their relative to data protection services for kubernetes clusters. But that's it's the abstraction layer or data services layer that sits on top of storage, which is different. So the basics of storage underneath in the infrastructure, you know, remain the same, Jeff. But the how that storage is provisioned and this abstraction layer of services which sits on top of the storage storage might be IBM flash system array storage, maybe E m c sand storage, maybe a W S E B s. That's the storage infrastructure. But this abstraction layer that sits on top this data services layer is what allows for the dynamic interaction of applications with the underlying storage infrastructure. >>And then again, just for people that aren't completely tuned in, Then what's the benefit to the application developer provider distributor with that type of an infrastructure behind And what can they do that they just couldn't do before? >>Well, I mean Look, we're, uh, e I mean, we're trying to solve the same problem over and over again, right? It's always about helping application developers build applications more quickly helps them be more agile. I t is always trying to keep up with the application developer and always struggles to. In fact, that's where the emergency cloud really came from. Just trying to keep up with the developer eso by giving them that automation. It gives them the ability to provision storage in real time, of course, without having open a ticket like friends said. But really, the Holy Grail here is getting to a developed once and deploy anywhere model. That's what they're trying to get to. So having an automated storage layer allows them to do that and ensure that they have access to storage and data, no matter where their application gets it >>right, Right, that pesky little detail. When I have to develop that up, it does have to sit somewhere and and I don't think storage really has gotten enough of of the bright light, really in kind of this app centric, developer centric world, we talk all the time about having compute available and and software defined networking. But you know, having this software defined storage that lives comfortably in this container world is pretty is pretty interesting. In a great development, I want to shift gears a >>little bit. Just one thing. Go >>ahead, >>plus one to Sam's comments. There all the application developer wants, they want an A P I and they want the same a p I to provision the storage regardless of where their app is running. The rest of the details they usually don't care about. Sure. They wanted to perform what not give him an A p I and make it the same regardless of where they're running the app. >>Because not only do they want to perform, they probably just presume performance, right? I mean, that's the other thing is that the best in class quickly becomes presumed baseline in a very short short period of time. So you've got to just you just got to just deliver the goods, right? They're gonna get frustrated and not be productive. But I wanted to shift gears up a little bit and talk about some of the macro trends. Right? We're here towards the end of 2020. Obviously, Cove It had a huge impact on business and a lot of different ways. And it's really evolved from March, this light switch moment. Everybody work from home, too. Now, this kind of extended time, that's probably gonna go on for a while. I'm just curious some of the things that you've seen with your customers not so much at the beginning, because that was that was a special and short period of time. But mawr, as we've extended and and are looking to, um, probably extended this for a while, you know, What is the impact of this increased work from home increase attack surface? You know, some of these macro things that we're seeing that cove it has caused and any other kind of macro trends beyond just this container ization that you guys were seeing impacting your world. Start with you, Sam. >>You know, I don't think it's actually changed what people were going to do or the strategy. What I've seen it do is accelerate things and maybe changed the way they're getting their, uh and so they're actually a lot of enterprises were running into challenges more quickly than they thought they would. And so they're coming to us and asking us to help them. Saw them, for example, backing up their data and these container environments as you move mission critical applications that maybe we're gonna move more slowly. They're realizing that as they've moved them, they can't get the level of data protection they need. And that's why actually we just announced it at the end of October. Updates to our modern data protection portfolio. It now is containerized. It could be deployed very easily in an automated fashion, but on top of that, it integrates down into the A P. I layer down into CSE drivers and allows you to do container where snapshots of your applications so you could do operational recovery. If there's some sort of an event you can recover from that you can do D R. And you can even use it for data migration. So we're helping them accelerate. So the biggest I think requests I'm getting from our customers, and how can you help us accelerate? And how can you help us fix these problems that we went running into as we tried to accelerate our digital transformation? >>Brent, Anyone that you wanna highlight? >>Mm. Okay. Ironically, one of my team was just speaking with one of the cruise lines, um, two days ago. We all know what's happened them. So if we just use them as an example, I'm clearly our customers need to do things differently now. So plus one to Sam's statement about acceleration on I would add another word to that which is agility, you know, frankly, they're having to do things in ways they never envisioned 10 months ago. So there need to cut cycle times to deploy effectively new ways of how they transact business has resulted in accelerated poll for these types of infrastructure is code technologies. >>That's great. The one that jumped in my mind. Sam, is you were talking. We've we've had a lot of conversations. Obvious security always comes up on baking security and is is a theme. But ransomware as a specific type of security threat and the fact that these guys not only wanna lock up your data, but they want to go in and find the backup copies and and you know and really mess you up so it sounds like that's even more important to have the safe. And we're hearing, you know, all these conversations about air gaps and dynamic air gaps and, you know, can we get air gaps and some of these infrastructure set up so that we can, you know, put put those backups? Um, and recovery data sets in a safe place so that if we have a ransomware issue, getting back online is a really, really important thing, and it seems to just be increasing every day. We're seeing things, you know, if you can actually break the law sometimes if you if you pay the ransom because where these people operate, there's all kind of weird stuff that's coming out of. Ransomware is a very specific, you know, kind of type of security threat that even elevates, you know, kind of business continuity and resiliency on a whole nother level for this one particular risk factor. When if you're seeing some of that as well, >>it's a great point. In fact, it's clearly an industry that was resilient to a pandemic because we've seen it increase things. Is organized crime at this point, right? This isn't the old days of hackers, you know, playing around this is organized crime and it is accelerating. And that's one thing. I'm really glad you brought up. It's an area we've been really focused on across our whole portfolio. Of course, IBM tape offers the best most of the actual riel air gapping, physical air gapping We could take a cartridge offline. But beyond that we offer you the ability to dio you know, different types of logical air gaps, whether it's to a cloud we support. In fact, we just announced Now the spectrum protect. We have support for Google Cloud. We already supported AWS Azure IBM Cloud. So we give you the ability to do logical air gapping off to those different cloud environments. We give you the ability to use worm capability so you can put your backups in a vault that can't be changed. So we give you lots of different ways to do it. In our high end enterprise storage, we offer something called Safeguarded copy where we'll actually take data off line that could be recovered almost instantly. Something very unique to our storage that gives you, for the most mission critical applications. The fastest path recovery. One of things we've seen is some of our customers have done a great job creating a copy. But when the event actually happens, they find is gonna take too long to recover the data and they end up having to pay the ransom anyway. So you really have to think through an Indian strategy on we're able to help customers do a kind of health checks of their environment and figure out the right strategy. We have some offerings to help come in and do that for our customers. >>Shift gears a little bit, uh, were unanswerable fest earlier this year and a lot of talk about automation. Obviously, answer was part of the Red Hat family, which is part of the IBM family. But, you know, we're seeing Mawr and Mawr conversations about automation about, you know, moving the mundane and the air prone and all the things that we shouldn't be doing as people and letting people doom or high value stuff. When if you could talk a little bit about the role of automation, that the kind of development of automation and how you're seeing that, you know, impact your deployments, >>right? You want to take that one first? >>Yeah, sure. Um, s o the first is, um when you think about individual kubernetes clusters. There's a level of automation that's required there. I mean, that's the fundamental. I mean, back to the infrastructure is code that's inherently. That's automation. To effectively declare the state of what you want your application, your cluster to be, and that's the essence of kubernetes. You declare what the state is, and then you pass that declaration to kubernetes, and it makes it so. So there's the kubernetes level automation. But then there's, You know what happens for larger enterprises when you have, you know, tens or hundreds of kubernetes clusters. Eso That's an area of Jeff you mentioned answerable. Now that's an area of with, you know, the work, the red hats doing the community for multi cluster management, actually in the community and together with IBM for automating the management of multiple clusters. And last thing I'll touch on here is that's particularly important as you go to the edge. I mean, this is all well and good when you're talking about, you know, safe raised floor data center environments. But what happens when you're tens or hundreds or even thousands of kubernetes clusters are running in an oil field somewhere? Automation becomes not only nice to have, but it's fundamental to the operation. >>Yeah, but let me just add onto that real quick. You know, it's funny, because actually, in this cove it era, you're starting to see that same requirement in the data center in the core data center. In fact, I would say that because there's less bodies now in the data center, more people working remotely. The automation in need for automation is actually actually accelerating as well. So I think what you said is actually true for the core data center now as well, >>right? So I wanna give you guys the last word before before we close the segment. Um, I'm gonna start with you, Brent. Really, From a perspective of big data and you've been involved again in big data for a long time. As you look back, it kind of the data warehouse era. And then we had kind of this whole rage with the Hadoop era, and, you know, we just continue to get more and more sophisticated with big data processes and applications. But at the end of the day, still about getting the right data to the right person at the right time to do something about it. I wonder if if you can, you know, kind of reflect over that journey and where we are now in terms of this mission of getting, you know, the right data to the right person at the right time so they could make the right decision. >>I think I'll close with accessibility. Um, that Z these days, we you know, the data scientists and data engineers that we work with. The key problem that they have is is accessibility and sharing of data. I mean, this has been wonderfully manifest. In fact, we did some work with the province of Ontario. You could look that stop hashtag house my flattening eso the work with them to get a pool of data. Scientists in the community in the province of Ontario, Canada, toe work together toe understand how to track co vid cases s such so that government could make intelligent responses and policy based on based on the fax so that that need highlights the accessibility that's required from today's, you know, yesteryear. It was maybe, uh, smaller groups of individual data scientists working in silos. Now it's people across industry as manifest by that That need accessibility as well as agility. They need to be able to spin up an environment that will allow them to in this case, um, to develop and deploy inference models using shared data sets without going through years of design. So accessibility on back to the back to the the acceleration and agility that Sam talked about. So I'll close with those words >>That's great. And the consistent with the democratization of two is another word that we're here, you know, over and over again in terms of, you know, getting it out of the hands of the data scientists and getting it into the hands of the people who are making frontline business decisions every day. And Sam for you, for your clothes. I love for you Thio reflect on kind of the changing environment in terms of your requirements for the types of workloads that you now are, you know, looking to support. So it's not just taking care of the data center and relatively straightforward stuff. But you've got hybrid. You've got multi cloud, not to mention all the media, the developments in the media between tape and obviously flash, um, spinning, spinning drives. But you know, really, We've seen this huge thing with flash. But now, with cloud and the increased kind of autumn autonomy ization of of units to be able to apply big batches in small batches to particular workloads across all these different requirements. When if you could just share a little bit about how you guys are thinking about, you know, modernizing storage and moving storage forward. What are some of your what are some of your your priorities? What are you looking forward to, uh, to be able to deliver, You know, basically the stuff underneath all these other applications. I mean, applications basically is data whether you I and some in some computer on top. You guys something underneath the whole package? >>Yeah. Yeah. You know, first of all, you know, back toe what Brent was saying, Uh, data could be the most valuable asset of an enterprise. You could give an enterprising, incredible, uh, competitive advantage as an incumbent if you could take advantage of that data using modern analytics and a I. So it could be your greatest asset. And it can also be the biggest inhibitor to digital transformation. If you don't figure out how to build a new type of modern infrastructure to support access to that data and support these new deployment models of your application. So you have to think that through. And that's not just for your big data, which the big data, of course, is extremely important and growing at incredible pace. All this unstructured data, You also have to think about your mission critical applications. We see a lot of people going through their transformation and modernization of S a p with move toe s four Hana. They have to think about how that fits into a multi cloud environment. They need to think about the life cycle of their data is they go into these new modern environments. And, yes, tape is still a very vibrant part of that deployment. So what we're working on an IBM has always been a leader in software defined storage. We have an incredible portfolio of capabilities. We're working on modernizing that software to help you automate your infrastructure. And sure, you can deliver enterprise class sls. There's no nobody's going to alleviate the requirements of having, you know, near perfect availability. You don't because you're moving into a kubernetes environment. Get a break on your downtime. So we're able to give that riel enterprise class support for doing that. One of the things we just announced that the end of October was we've containerized our spectrum scale client, allowing you now toe automate the deployment of your cluster file system through communities. So you'll see more and more of that. We're offering you leading modern native protection for kubernetes will be the first to integrate with OCP and open ship container storage for data protection. And our flashes from family will continue to be on the leading edge of the curve around answerable automation and C s I integration with who are already so we'll continue to focus on that and ensure that you could take advantage of our world class storage products in your new modern environment. And, of course, giving you that portability between on from in any cloud that you choose to run in >>exciting times. No, no shortage of job security for you, gentlemen, that's for sure. All right, Well, Brent, Sam, thanks for taking a few minutes and, uh, is great to catch up. And again. Congratulations on the success. Thank you. Thank you. Thank you. Alrighty, Sammy's Brent. I'm Jeff, You're watching the cubes. Continuing coverage of Q. Khan Cloud, Native Con North America 2020. Thanks for watching. We'll see you next time.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud Native Computing Foundation and Ecosystem >>Partners Everyone welcome back to the cubes. Coverage of Coop con Cloud, native con North America 2020. Normally the Cuba's in person. But like the EU event, this is gonna be a remote virtual event. This is the Cube virtual. We are the Cube Virtual. This is a keynote and show review with our analysts and hosts Lisa Martin, GOP Scar and myself. Guys, welcome to the program. Lisa, Great to see you. You great to see you remotely. Thanks for coming on. >>Always great to be part of the Cuban acute virtual keeping us connected. >>So Coop Con Cloud Native cons November and I remember in 2016 the first Coop Con. That's when Hillary Clinton got defeated by Trump. And now this year the election's passed this time and, uh, Biden the winner. So, you know, election more good vibes this year in the community because everyone was kind of sad last time. So if you remember the first Cube con, it was in Seattle during that time, so that was important to kinda reminisce on. That other thing I want to bring up to you guys is the somber news of the passing of Dan Con who was the executive director of C N C F. He passed a few weeks ago on his home. It was illness and great legend. So we're gonna call that out, and there are thoughts and prayers. Go with the families. Condolences to his wife and kids. So what? I'm say, Dan. Godspeed. Funny dance story, Lisa. Yo, piece that I always always pronounce his name wrong on the queue was like, John, it's con, not Cohen. Okay. All right, Dan, Good to see you. Sorry, but a great guy friend to everyone And super great human being. So rest in peace. Okay. Que con, I >>think the big thing. >>This you wanna get your thoughts, you have to start with you, C and C F. What are they up to? Obviously remote. It's been a terrible year with the pandemic and all the disruptions on DCI change your thoughts on where they are now, this year. >>So you know, it's funny, even though it's remote. Even though reaching people, it's become harder. Uh, you know, we all have to deal with this from our you know, our living room, our office at home. But still, the C in C F is doing what it's been doing for a little while now. So instead of focusing on the technology part of RT world, there are focusing on you know, the community side of it. So they're fighting for inclusivity. They're fighting for diversity, for resilience in terms off their community. And they are really working on making the open source community more accessible, both for end user companies. A swell as offer developers thio enter the space, have their contribution and, you know, make sure that everyone can reap the full benefits off these open source products. >>You know, we talked to Priyanka Sharma and Stephen Augustus, and this was a big theme. There's there's been there's been a lot of engagement online, obviously, even though they have a remote platform, some people are thrilled with it. Some aren't. No one's ever happy these days. It's on the Web. It's always difficult, but the community been activated and a lot more diversity. I covered the big story around. You know, Master slave. The terminology now is gonna go main, you know, terminology and how that's gonna be safer. Also for diversity stem women in tech, This >>has been >>a big theme. I'd love to get your thoughts on that, because I think that's been a very positive thing. Uh, Lisa, you and I have been talking about this for years on the Cube around this diversity peace. What's your thoughts as well, like to get both your reactions on where this directions going. >>Yeah. You know, I think there's a number of things that have been catalyzed this year by the challenges that we've been through and the diversity pushed into the spotlight again. The spotlight is different, and it's really causing change for good. I think it's opening people's minds and perspective, as is, I think, this entire time, you know, it's for events like Yukon and all the other events that were normally getting a lot of airline miles for John and you were not getting. We're sitting at home with our in home studios, but at the same time, the engagement is increasing in every event, I imagine that the great Q. Khan and cognitive community that Dan Cohen has built is on Lee getting bigger and stronger, even though folks are physically separated. That's been just been my observation and something I felt from everything show I've covered every interview I've done that diversity is being raised now to a visibility level that we haven't seen in terms of a catalyzing action. >>You your reaction, Thio. >>No, I completely agree. And I want to add to that where you know, just like Lisa said. You know, we used to fly to these events. We were privileged and lucky to to be there to have the opportunity. But because everything is now digital and virtual, it opens the community up to so many other people who, for whatever reason, weren't able to join in person but are able to join virtually indigenously. So I think you know, even though there's a lot of downsides Thio to this pandemic, this is one of the, you know, the small nuggets of off seeing the sea NCF community opening up to a broader audience. >>Yeah, and that's a great point. You know, we aren't getting the airline miles we're getting Certainly the zoom and the cube mileage remote Lisa, because what's interesting you're saying is is that you know, we're getting more action with him coming in, doing some or hosting yourself, um, Eliana Gesu as well, Others. But we can get people more because remember, the people aren't we're not trying, but so aren't other people that were coming the big names, but also the fresh voices, the new names, names? We don't know yet. I think that's what we're seeing with the remote interviews is that it's one click away from being on the Cube now. So cute. Virtual is 24 73 65 we're gonna continue to do that. I think this is gonna change the makeup of the engagement in the conversation because you're gonna have mawr participation that's going to be highly accelerated. But also, these new voices are gonna bring a positive change. It might upset the hierarchy a little bit in the working groups at the top you, But you know they're open. I mean, I talked with Stephen Augustus. He's totally cool with this Chris, and I check is the same way he's like, Hey, bring on more people. This is the >>This is >>the vibe of the of the Lennox foundations always been. >>It's always been that way. And, you know, going back Teoh to the early open source events in Europe that I went to you. I started doing that as a teenager 15 years ago, and the vibe, you know, hasn't necessarily changed. The makeup of the audience certainly has changed right from it, being dominated by white males. It's totally opened up. And, you know, if we see that happening with the C N C F now as well, I think that's for you know, for the better. I think, um, our community, the i t community in the open source community need that resilience. Need all of those different perspectives from all of you know, different kinds of people from different walks of life with different histories. And I think that only makes the community stronger and more viable in the long run. I >>agree it's that >>open source needs. >>Sorry, it's not thought diversity that I think we're seeing even more now again. Just my perspective is just that the light that this challenging time is shining on, exposing things that are really opportunities and it's I think it's imperative to look at it in that way. But that thought diversity just opens up so many more opportunities that folks that are maybe a little bit more tunnel visioned aren't thinking of. But for businesses, thio and people Thio thrive and move forward and learn from this we need to be able Thio, take into consideration other concepts, other perspectives as we learn and grow. >>Yeah, that's a good point. You know, It was giving a a shout out to Dan Conn. And when I heard the news, I put a clip. One of my favorite clips over the interviews was really me kind of congratulating him on the success of C and C. I think it was, like two years ago or maybe last year. I forget, Um, but I >>was a >>critic of it ever initially, and I was publicly on the record on the Cube. Lisa, you remember, uh, with Stew, who's now having a great new career? Red hat Still and I were arguing, and I was saying, Stew, I think this is gonna fail, because if c. N. C F doesn't balance the end user peace with the logos that we're coming because remember, you about four years ago. It was like a NASCAR logo. Farmers like you know, it's like, you know, everything was like sponsored by Google this and then Amazon came in. You look at the sponsor list. It was like It's the who's who and cloud and now cloud native. It was the industry the entire industry was like, stacked up against reinvent. This is before Amazon made their move. I mean, uh, as your maid, they're moving for Google. Cloud kind of got their footing. So is essentially coop con against a W s. And I said, That's gonna fail, and I had to eat my words, and I did. It was rightfully so, But the balance, the balance between end user projects and vendor was very successful. And that's still plays out today. Lisa. This is important now because you said pandemic de ecosystem still needs to thrive, but there's no face to face anymore. >>What's the >>challenge? What's the opportunity there? I wanna put you on the spot. >>Sure. No, I think I think it's both challenging and opportunistic. I tend to look at it more from an opportunistic view. I think that it forced a lot of us, Even people like myself who worked from home a lot before, when I wasn't traveling for my marketing company or the Cube. You can really have very personal interactions. The people on Zoom and I found that it's connecting people in a deeper way than you even would get in the office. That's something that I actually really appreciate, how it has been an opportunity to really kind of expand relationships or toe open new doors that wouldn't be there if we were able to be studying together physically in person. And it's obviously changing. You know, all the vendors that we work with. It's very different to engage an audience when you are on Lee on camera, and it's something that, as we know, is we work with folks who haven't done it before. That's one of the things that I think a lot of the C suite I talked to Mrs is that opportunity Thio. You know, be on a stage and and be able to show your body language and your energy with your customers and your partners and your employees. But I actually do think that there is what we're doing through Zoom and and all these virtual platforms like the Cube virtual is well, we're opening up doors for a more intimate way that I think the conversations are more authentic. You know, people are have, like, three year old Discover occurs and they're running in the room when they're screaming behind that. That's how things are today. We're learning toe work with that, but we're also seeing people in a more human >>way. Containers Mitch, mainstream and shifting, left the role of security this year. What's your >>take? So I mean, if we're talking about security and nothing else, I think we're at a point where you know, the C N C. F has become mainstream. Its most popular products have become mainstream. Um, because if we're talking about security, there's, you know, not a lot left. And I say that with, you know, a little bit of sarcasm. I don't mean to offend anyone, but if I did, uh, I do apologize, but, you know, security. Even though it is super important again, it means that we have, you know, moved on from talking about kubernetes and and container Management, or we've moved on from storage. Um, it means that the technology part of the C N. C. F. Like the hard work has been done for 80%. We're now into the 20% where we're kind of, you know, dotting the I's and and making sure that we cover all of the bases. And so one of the news sandbox sandbox projects that has been accepted, I think, today even eyes certain Manager Thio to manage certificates Uh, you know, at scale, um, in an automated fashion. And I think that's, you know, 11 prime example of how security is becoming the theme and kind of the conversation at Yukon this year where, you know, we're again seeing that maturity come into play with even with sandbox projects now being able to help customers help end users with, you know, certificates which is, you know, in in the the macro picture a very specific, a very niche thing to be able to solve with open source software. But for every company, this is one of those vital, you know, kind of boilerplate security measures so that the, um the customer and all of their infrastructure remains safe. >>I think you what You're kind of really articulate, and there is the evolution of CNC off much to John Surprises. You said you thought in the very beginning that this wasn't gonna take off. It has. Clearly, Dan Cohen's left a great legacy there. But we're seeing the evolution of that. I do know John. Wanna ask because you did a lot of the interviews here. We've been talking for, what, nine months now on the Cube Virtual about the acceleration of transformation, of every business to go from that. Okay, how do we do this work in this in this weird environment? Keep the lights on. How do we actually be successful and actually become a thriving business? As things go forward, what are some of the things that you heard from the guests regarding? Kobe has an accelerator. >>Well, I think I think a couple of things. Good. Good question. I think it ranges. Right. So the new They had some news that they're trying to announce. Obviously, new survey certifications, K a security certification, new new tech radar support, diversity stats. You know, the normal stuff they do in the event, they gotta get the word out. So that was one thing I heard, but on the overall macro trend. You know, we saw the covert impact, and no >>one's >>afraid of it there. I mean, I think, you know, part of the legacy of these tech communities is they've been online. They're they're used to being online. So it's not a new thing. So I don't think that the work environment has been that much of a disruption to the people in the in the core community. Linux Foundation, for instance, had a great shot with Chris and a sticker on this. He's the CTO. He's been the CEO, brought a senior roles. Um, in fact, they're they're creating a template around C N C f. And then they're announced The Finn Finn Ops Foundation. Uh, Jr store meant, um, is an executive director. That's part of the new foundation. It's a practitioner community. So I think, um, teasing out the conversation is you're gonna see a template model of the C N. C f. Where you're going to see how groups work together. I think what cove? It has definitely shown in some of the things that you guys were saying around how people are gonna be more engaged, more diversity, more access. I >>think you're >>gonna start to see new social constructs emerge around distinct user groups. And I think this Finn ops Foundation is a tell sign around how groups of people going to start together, whether they're cube host coming together on Cube fans and cube alumni. I mean, let me think about the alumni that have been on the Cube. Lisa, you know Tim Hopkins, Sarah Novotny. Chelsie Hightower. Um, Dan Burns, Craig MK Lucky. I mean, we've had everybody on that's now Captain of the industry. So, um, way had capital one we've had, uh, you know, lift on. I mean, it's becoming a really tight knit. Everyone knows each other, and I think now they realize that they have a lot of, uh, power to infect change. And so when you're trying to affect change, um, that's a good thing, and people are pumped about. So I think the big focus was, um, CNC have a successful again. It's there's there's a somber note around Dan cons passing, but I think he had already moved on to a new position. So he was already passed the baton to management, But he did leave a mark, but I think there's Priyanka Sharma. She's doing a great job. People are upbeat and I think the theme is kubernetes. It happened. It's went next level, then it's going next level again and I think that's kind of what people really aren't saying is kind of the public secret, which is okay, this thing's going mainstream. Now you're gonna start to see it in, in, In commercial deployments. You're gonna start to see it scale into organizations. And that's not the cool kids or the Emerging Dev ops crowd. That's I t. So you know you know it's gonna happen is like, Hey, you know, I'm a nice guy, our developer. What is this? It has toe work. Well, that's the big I think I think people weren't talking about That's the most important story. >>I think another element to that John is the cultural shift. You know, we were talking when we talk about Dev ops who was think about speed and I talked to some folks who said, You know, it's it has to be the I T. Cultures on the business cultures coming together in a meaningful way to collaborate in a very new way. Thankfully, we have the technology to enable us to collaborate. But I think that's been another underlying thing that I've heard a lot through recent times. Is that that facilitator of of cultural change, which is always hard to dio? And there's a bit of a catalyst here for organizations to not just keep the lights on. But to be successful, going forward and and and find new ways of delighting their customers, >>we'll get the final word. I just want to say my big take away to the show is and we'll go down the line. I'll start Lisa in Europe, you could go is the usage of cloud and multi cloud is here. Everyone sees that. I think there's a financial aspect going on with security. You're gonna be tied in. I think you see new sets of services coming built on the foundation of the C N C F. But cloud and multi cloud is here. Multi cloud meeting edges. Well, that is definitely on everyone's radar. That was a big theme throughout the interview, so we'll see more of that. Lisa, your takeaways. >>Yeah, I would agree with that. And I think one of the biggest things that I hear consistently is the opportunities that have been uncovered, the the collaboration becoming tighter and folks having the opportunity to engage more with events like Coop Con and C and C F. Because of this virtual shift, I think there's only ah lot of positive things that we're going to stay to come. >>Yep. Yeah, my point of view is I mean, open source is validated completely right? It's a viable model to build around software. On the one hand, on the other hand, the C and C s role in making that open source community broadly accessible and inclusive is, I think, the biggest win Thio look back at at the last year. >>Well, I'm super excited for moving on to the next event. It's been great pleasure. Lisa. You you guys are great co host Virtual Cube. Thanks for participating. And we'll see you next time. Thank you. Okay, that's the cubes. Coverage of Coop con 2020 cloud Native con Virtual This the cube Virtual. We are the cube. Virtual. Thanks 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 >>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 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.

>>from New York. It's the Q covering Escape. 19. >>Welcome back to the Cube coverage here in New York City for the first inaugural multi cloud conference called Escape, where in New York City was staying in New York, were not escaping from New York were in New York. It's all about multi Cloud, and we're here. Lisa Marie Nancy, developer advocate for Port Works, and Eric Conn, vice president of Products Works. Welcome back. Q. >>Thank you, John. Good to see >>you guys. So, um, whenever the first inaugural of anything, we want to get into it and find out why. Multi clouds certainly been kicked around. People have multiple clouds, but is there really multi clouding going on? So this seems to be the theme here about setting the foundation, architecture and data of the two kind of consistent themes. What shared guys take Eric, What's your take on this multi cloud trend? Yeah, >>I think it's something we've all been actively watching for a couple years, and suddenly it is becoming the thing right? So every we just had ah, customer event back in Europe last week, and every customer there is already running multi cloud. It's always something on their consideration. So there's definitely it's not just a discussion topic. It's now becoming a practical reality. So this event's been perfect because it's both the sense of what are people doing, What are they trying to achieve and also the business sense. So it's definitely something that is not necessarily mainstream, but it's becoming much more how they're thinking about building all their applications. Going forward, >>you know, you have almost two camps in the world. Want to get your thoughts on this guy's Because, like you have cloud native and people that are cloud native, they love it. They born the cloud that get it. Everything's cracking along. The developers air on Micro Service's They're agile train with their own micro service's. Then you got the hybrid I t. Trying to be hybrid developer, right? So you kind of have to markets coming together. So to me, I see multi cloud as kind of a combination of old legacy Data center types of I t with cloud native, not just ops and dead. But how about like trying to build developer teams inside enterprises? This seems to be a big trend, and multi club fits into that because now the reality is that I got azure. I got Amazon. Well, let's take a step back and think about the architecture. What's the foundation? So that to me, is more my opinion. But I want to get your thoughts and reactions that because if it's true, that means some new thinking has to come around around. What's the architecture? What are you trying to do? What's the workloads behavior outcome look like? What's the work flows? So there's a whole nother set of conversations that happened. >>I agree. I think the thing that the fight out there right now that we want to make mainstream is that it's a platform choice, and that's the best way to go forward. So it's still an active debate. But the idea could be I want to do multi club, but I'm gonna lock myself into the Cloud Service is if that's the intent or that's the design architecture pattern. You're really not gonna achieve the goals we all set out to do right, So in some ways we have to design ourselves or have the architecture that will let us achieve the business schools that were really going for and that really means from our perspective or from a port works perspective. There's a platform team. That platform team should run all the applications and do so in a multi cloud first design pattern. And so from that perspective, that's what we're doing from a data plan perspective. And that's what we do with Kubernetes etcetera. So from that idea going forward, what we're seeing is that customers do want to build a platform team, have that as the architecture pattern, and that's what we think is going to be the winning strategy. >>Thank you. Also, when you have the definition of cod you have to incorporate, just like with hybrid I t the legacy applications. And we saw that you throughout the years those crucial applications, as we call them People don't always want them to refer to his legacy. But those are crucial applications, and our customers were definitely thinking about how we're gonna run those and where is the right places it on Prem. We're seeing that a lot too. So I think when we talk about multi cloud, we also talk about what What is in your legacy? What is it? Yeah, I >>like I mean I use legacy. I think it's a great word because I think it really puts nail in the coffin of that old way because remember, if you think about some of the large enterprises, these legacy applications, they've been optimized for hardware and optimize their full stack. They've been build up from the ground up, so they're cool. They're running stuff, but it doesn't always translate to see a new platform designed point. So how do you mean Containers is great fit for their Cooper names. Obviously, you know is the answer. We you guys see that as well, but okay, I can keep that and still get this design point. So I guess what I want to ask you guys, as you guys are digging into some of the customer facing conversations, what are they talking about? The day talking about? The platform? Specifically? Certainly, on the security side, we're seeing everyone running away from buying tools to thinking about platforms. What's the conversation like on the cloud side >>way? Did a talk are multiplied for real talk at Barcelona? Q. Khan put your X three on Sudden. Andrew named it for reals of Izzy, but we really wanted to talk about multiplied in the real world. And when we said show of hands in Barcelona, who's running multi cloud? It was very, very few. And this was in, what, five months? Four months ago? Whereas maybe our customers are just really super advanced because of our 100 plus customers. At four words, we Eric is right. A lot of them are already running multi cloud or if not their plan, in the planning stage right now. So even in the last +56 months, this has become a reality. And we're big fans of communities. I don't know if you know Eric was the first product manager for Pernetti. Hey, he's too shy to say it on Dhe. So yeah, and we think, you know, and criminal justice to be the answer to making all They caught a reality right now. >>Well, I want to get back into G, K, E and Cooper. Very notable historic moment. So congratulations, But to your point about multi cloud, it's interesting because, you know, having multiple clouds means things, right? So, for instance, if I upgrade to office 3 65 and I kill my exchange server, I'm essentially running azure by their definition. If I'm building it, stack on AWS. I'm a native, this customer. Let's just say I want to do some tensorflow or play with big table or spanner on Google. Now >>we have three >>clouds now they're not. So they have work clothes, specific objectives. I am totally no problem. I see that like for the progressive customers, some legacy be to be people who like maybe they put their toe in the cloud. But anyone doing meaningful cloud probably has multiple clouds. But that's workload driven when you get into tying them together and is interesting. And I think that's where I think you guys have a great opportunity in this community because if open source convene the gateway to minimize the lock in and when I say lock and I mean like locking them propriety respect if his value their great use it. But if I want to move my data out of the Amazon, >>you brought up so many good points. So let me go through a few and Lisa jumping. I feel like locking. People don't wanna be locked >>in at the infrastructure level. So, like you said, if >>there's value at the higher levels of Stack, and it helps me do my business faster. That's an okay thing to exchange, but it is just locked in and it's not doing anything. They're that's not equal exchange, right, So there's definitely a move from infrastructure up the platform. So locking in >>infrastructure is what people are trying to move away from. >>From what we see from the perspective of legacy, there is a lot of things happening in industry that's pretty exciting of how legacy will also start to running containers. And I'm sure you've seen that. But containers being the basis you could run a BM as well. And so that will mean a lot for in terms of how V EMS can start >>to be matched by orchestrators like kubernetes. So that is another movement for legacy, and I wanted to acknowledge that point >>now, in terms of the patterns, there are definitely applications, like a hybrid pattern where connect the car has to upload all its data once it docks into its location and move it to the data center. So there are patterns where the workflow does move the ups are the application data between on Prem into a public cloud, for instance, and then coming back from that your trip with Lisa. There is also examples where regulations require companies to enterprise is to be able to move to another cloud in a reasonable time frame. So there's definitely a notion of Multi Cloud is both an architectural design pattern. But it's also a sourcing strategy, and that sourcing strategy is more regulation type o. R. In terms of not being locked in. And that's where I'm saying it's all those things. I'd >>love to get your thoughts on this because I like where you're going with this because it kind of takes it to a level of okay, standardization, kubernetes nights, containers, everyone knows what that is. But then you start talking about a P I gateways, for instance, right? So if I'm a car and I have five different gateways on my device, I ot devices or I have multiple vendors dealing with control playing data that could be problematic. I gotta do something like that. So I'm starting. Envision them? I just made that news case up, but my point is is that you need some standards. So on the a p I side was seeing some trends there. One saying, Okay, here's my stuff. I'll just pass parameters with FBI State and stateless are two dynamics. What do you make of that? What, What? What has to happen next to get to that next level of happiness and goodness? Because Bernays, who's got it, got it there, >>right? I feel that next level. I feel like in Lisa, Please jump. And I feel like from automation perspective, Kubernetes has done that from a P I gateway. And what has to happen next. There's still a lot of easy use that isn't solved right. There's probably tons of opportunities out there to build a much better user experience, both from the operations point of view and from what I'm trying to do is an intense because what people aren't gonna automate right now is the intent. They automate a lot of the infrastructure manual tasks, and that's goodness. But from how I docked my application, how the application did it gets moved. We're still at the point of making policy driven, easy to use, and I think there's a lot of opportunities for everyone to get better there. That's like low priority loving fruitcake manual stuff >>and communities was really good at the local food. That's a really use case that you brought up. Really. People were looking at the data now and when you're talking about persistent mean kun is his great for stateless, but for state full really crucial data. So that's where we really come in. And a number of other companies in the cloud native storage ecosystem come in and have really fought through this problem and that data management problem. That's where this platform that Aaron was talking to that >>state problem. Talk about your company. I want to go back to to, um, Google Days. Um, many war stories around kubernetes will have the same fate as map reduce. Yeah, the debates internally at Google. What do we do with it? You guys made the good call. Congratulations on doing that. What was it like to be early on? Because you already had large scale. You were already had. Borg already had all these things in place. Um, it wasn't like there was what was, >>Well, a few things l say one is It was intense, right? It was intense in the sense that amazing amount of intelligence amazing amount of intent, and right back then a lot of things were still undecided, right? We're still looking at how containers or package we're still looking at how infrastructure kit run and a lot of service is were still being rolled out. So what it really meant is howto build something that people want to build, something that people want to run with you and how to build an ecosystem community. A lot of that the community got was done very well, right? You have to give credit to things like the Sig. A lot of things like how people like advocates like Lisa had gone out and made it part of what they're doing. And that's important, right? Every ecosystem needs to have those advocates, and that's what's going well, a cz ah flip side. I think there's a lot of things where way always look back, in which we could have done a few things differently. But that's a different story for different. Today >>I will come back in the studio Palop of that. I gotta ask you now that you're outside. Google was a culture shock. Oh my God! People actually provisioning software provisioning data center culture shock when there's a little >>bit of culture shock. One thing is, and the funny thing is coming full circle in communities now, is that the idea of an application? Right? The idea of what is an application eyes, something that feels very comfortable to a lot of legacy traditional. I wanna use traditional applications, but the moment you're you've spent so much time incriminates and you say, What's the application? It became a very hard thing, and I used to have a lot of academic debates. Where is saying there is no application? It's It's a soup of resources and such. So that was a hard thing. But funny thing is covered, as is now coming out with definitions around application, and Microsoft announced a few things in that area to so there are things that are coming full circle, but that just shows how the movement has changed and how things are becoming in some ways meeting each other halfway. >>Talk about the company, what you guys are doing. Take a moment. Explain in context to multi cloud. We're here. Port works. What's the platform? It's a product. What's the value proposition? What's the state of the company. >>So the companies? Uh well, well, it's grown from early days when Lisa and I joined where we're probably a handful now. We're in four or five cities. Geography ease over 100 people over 150 customers and there. It's been a lot of enterprises that are saying, like, How do I take this pattern of doing containers and micro service is And how do I run it with my mission? Critical business crinkle workloads. And at that point, there is no mission critical business critical workload that isn't stable so suddenly they're trying to say, How do I run These applications and containers and data have different life cycles. So what they're really looking for is a data plane that works with the control planes and how controlled planes are changing the behavior. So a lot of our technology and a lot of our product innovation has been around both the data plane but a storage control plane that integrates with a computer controlled plane. So I know we like to talk about one control plane. There's actually multiple control planes, and you mentioned security, right? If I look at how applications are running way after now securely access for applications, and it's no longer have access to the data. Before I get to use it, you have to now start to do things like J W. T. Or much higher level bearer tokens to say, I know how to access this application for this life cycle for this use case and get that kind of resiliency. So it's really around having that storage. More complexity absolutely need abstraction >>layers, and you got compute. Look, leading work there. But you gotta have >>software to do it from a poor works perspective. Our products entirely software right down loans and runs using kubernetes. And so the point here is we make remarries able to run all the staple workloads out of the box using the same comment control plane, which is communities. So that's the experiences that we really want to make it so that Dev Ops teams can run anywhere close. And that's that's in some ways been part of the mix. Lisa, >>we've been covering Dev up, going back to 2010. Remember when I first was hanging around San Francisco 2008 joint was coming out the woodwork and all that early days and you look at the journey of how infrastructures code We talked about that in 2008 and now we'll get 11 years later. Look at the advancements you've been through this now The tipping point. It's just seems like this wave is big and people are on it. The developers air getting it. It's a modern renaissance of application developers, and the enterprises it's happening in the enterprise is not just like the nerds Tier one, the Alfa Geeks or >>the Cloud native. It's happening in the >>everyone's on board this time, and you and I have been in the trenches in the early stages of many open source projects. And I think with with kubernetes Arab reference of community earlier, I'm super proud to be running the world's largest CNC F for user group. And it's a great community, a diverse community, super smart people. One of my favorite things about working for works is we have some really smart engineers that have figured out what companies want, how to solve problems, and then we'll go creative. It'll open source projects. We created a project called autopilot, really largely because one of our customers, every who's in the G s space and who's running just incredible application. You can google it and see what the work they're doing. It's all there publicly, Onda We built, you know, we built an open source project for them to help them get the most out of kubernetes. We can say so. There's a lot of people in the community system doing that. How can we make communities better halfway make commitments, enterprise grade and not take years to do that? Like some of the other open source projects that we worked on, it took. So it's a super exciting time to be here, >>and open source is growing so fast now. I mean, just think about how these projects being structured. Maur and Maur projects are coming online and user price, but a lot more vendor driven projects to use be mostly and used, but now you have a lot of vendors who are users. So the line is blurring between Bender User in Open source is really fascinating. >>Well, you look at the look of the landscape on the C N. C f. You know the website. I mean, it's what 400 that are already on board. It's really important. >>They don't have enough speaking slasher with >>right. I know, and it's just it. It is users and vendors. Everybody's in this community together. It's one of things that makes it super exciting. And it it's how we know this is This was the right choice for us to base this on communities because that's what everybody, you guys >>are practically neighbors. So we're looking for seeing the studio. Palo Alto Eric, I want to ask you one final question on the product side. Road map. What you guys thinking As Kubernetes goes, the next level state, a lot of micro service is observe abilities becoming a key part of it, Obviously, automation, configuration management things are developing fast. State. What's the What's the road map for you guys? >>For us, it's been always about howto handle the mission critical and make that application run seamlessly. And then now we've done a lot of portability. So disaster recovery has been one of the biggest things for us is that customers are saying, How do I do a hybrid pattern back to your earlier question of running on Prem and in Public Cloud and do a d. R. Pale over into some of the things at least, is pointing out that we're announcing soon is non series autopilot in the idea, automatically managing applications scale from a volume capacity. And then we're actually going to start moving a lot more into some of the what you do with data after the life cycle in terms of backup and retention. So those are the things that everyone's been pushing us and the customers are all asking for. You >>know, I think data they were back in recovery is interesting. I think that's going to change radically. And I think we look at the trend of how yeah, data backup and recovery was built. It was built because of disruption of business, floods, our gains, data center failure. But I think the biggest disruptions ransomware that malware. So security is now a active disruptor. So it's not like it after the hey, if we ever have, ah, fire, we can always roll back. So you're infected and you're just rolling back infected code. That's a ransomware dream. That's what's going on. So I think data protection it needs to be >>redefined. What do you think? Absolutely. I think there's a notion of How do I get last week's data last month? And then oftentimes customers will say, If I have a piece of data volume and I suddenly have to delete it, I still need to have some record of that action for a long time, right? So those are the kinds of things that are happening and his crew bearnaise and everything. It gets changed. Suddenly. The important part is not what was just that one pot it becomes. How do I reconstruct everything? What action is not one thing. It's everywhere. That's right and protected all through the platform. If it was a platform decision, it's not some the cattlemen on the side. You can't be a single lap. It has to be entire solution. And it has to handle things like, Where do you come from? Where is it allowed to go? And you guys have that philosophy. We absolutely, and it's based on the enterprises that are adopting port works and saying, Hey, this is my romance. I'm basing it on Kubernetes. You're my date a partner. We make it happen. >>This speaks to your point of why the enterprise is in. The vendors jumped in this is what people care about Security. How do you solve this last mile problem? Storage. Networking. How do you plug those holes in Kubernetes? Because that is crucial to our >>personal private moment. Victory moment for me personally, was been a big fan of Cuban is absolutely, you know, for years. Then there were created, talked about one. The moments that got me that was really kind of a personal, heartfelt moment was enterprise buyer. And, you know, the whole mindset in the Enterprise has always been You gotta kill the old to bring in the new. And so there's always been that tension of a you know, the shiny new toy from Silicon Valley or whatever. You know, I'm not gonna just trash this and have a migration za paying that. But for I t, they don't want that to do that. They hate doing migrations, but with containers and kubernetes that could actually they don't to end of life to bring in the new project. They can do it on their own timetable or keep it around. So that took a lot of air out of the tension in on the I t. Side because they say great I can deal with the lifecycle management, my app on my own terms and go play with Cloud native and said to me, that's like that was to be like, Okay, there it is. That was validation. That means this Israel because now they can innovate without compromising. >>I think so. And I think some of that has been how the ecosystems embrace it, right. So now it's becoming all the vendors are saying my internal stack is also based on community. So even if you as an application owner or not realizing it, you're gonna take a B M next year and you're gonna run it and it's gonna be back by something like awesome. Lisa >>Marie Nappy Eric on Thank you for coming on Port Works Hot start of multiple cities Kubernetes big developer Project Open Source. Talking about multi cloud here at the inaugural Multi cloud conference in New York City. It's the Cube Courage of escape. 2019. I'm John Period. Thanks for watching

>>from New York. It's the Q covering escape. 19. Hey, welcome back to the Cube coverage here in New York City for the first inaugural multi cloud conference called Escape. We're in New York City. Was staying in New York, were not escapee from New York were in New York. So about Multi Cloud. And we're here. Lisa Marie Nancy, developer advocate for report works, and Eric Conn, vice president of products. Welcome back with you. >>Thank you, John. >>Good to see you guys. So whenever the first inaugural of anything, we want to get into it and find out why. Multiplied certainly been kicked around. People have multiple clouds, but is there really multi clouding going on? So this seems to be the theme here about setting the foundation, architecture and data to kind of consistent themes. What's your guys take? Eric, What's your take on this multi cloud trend? >>Yeah, I think it's something we've all been actively watching for a couple years, and suddenly it is becoming the thing right? So every we just had a customer event back in Europe last week, and every customer there is already running multi cloud. It's always something on their consideration. So there's definitely it's not just a discussion topic. It's now becoming a practical reality. So this event's been perfect because it's both the sense of what are people doing, What are they trying to achieve and also the business sense. So it's definitely something that is not necessarily mainstream, but it's becoming much more how they're thinking about building all their applications Going forward. >>You know, you have almost two camps in the world to get your thoughts on this guy's because like you have a cloud native people that are cloud needed, they love it. They're born in the cloud that get it. Everything's bringing along. The developers are on micro service's They're agile train with their own micro service is when you got the hybrid. I t trying to be hybrid developer, right? So you kind of have to markets coming together. So to me, Essie multi Cloud as a combination of old legacy Data Center types of I t with cloud native not just optioned. It was all about trying to build developer teams inside enterprises. This seems to be a big trend, and multi cloud fits into them because now the reality is that I got azure, I got Amazon. Well, let's take a step back and think about the architecture. What's the foundation? So that to me, is more my opinion. But I want to get your thoughts and reactions that because if it's true, that means some new thinking has to come around around. What's the architecture, What we're trying to do? What's the workloads behavior outcome look like? What's the workflow? So there's a whole nother set of conversations. >>Yeah, that happened. I agree. I think the thing that the fight out there right now that we want to make mainstream is that it's a platform choice, and that's the best way to go forward. So it's still an active debate. But the idea could be I want to do multi club, but I'm gonna lock myself into the Cloud Service is if that's the intent or that's the design architecture pattern. You're really not gonna achieve the goals we all set out to do right, So in some ways we have to design ourselves or have the architecture that will let us achieve the business schools that were really going for and that really means from our perspective or from a port Works perspective. There's a platform team. That platform team should run all the applications and do so in a multi cloud first design pattern. And so from that perspective, that's what we're doing from a data plane perspective. And that's what we do with Kubernetes etcetera. So from that idea going forward, what we're seeing is that customers do want to build a platform team, have that as the architecture pattern, and that's what we think is going to be the winning strategy. >>Thank you. Also, when you have the death definition of cod, you have to incorporate, just like with hybrid a teeny the legacy applications. And we saw that you throughout the years those crucial applications, as we call them. People don't always want them to refer to his legacy. But those are crucial applications, and our customers were definitely thinking about how we're gonna run those and where is the right places it on Prem. We're seeing that a lot, too. So I think when we talk about multi cloud, we also talk about what what is in your legacy? What is your name? I mean, I >>like you use legacy. I think it's a great word because I think it really nail the coffin of that old way because remember, if you think about some of the large enterprises these legacy applications didn't optimized for harden optimize their full stack builds up from the ground up. So they're cool. They're running stuff, but it doesn't translate to see a new platform design point. So how do you continue? This is a great fit for that, cos obviously is the answer. You guys see that? Well, okay, I can keep that and still get this design point. So I guess what I want to ask you guys, as you guys are digging into some of the customer facing conversations, what are they talking about? The day talking about? The platform? Specifically? Certainly on the security side, we're seeing everyone running away from buying tools were thinking about platform. What's the conversation like on the outside >>before your way? Did a talk are multiplied for real talk at Barcelona. Q. Khan put your X three on son. Andrew named it for reals of busy, but we really wanted to talk about multiplied in the real world. And when we said show of hands in Barcelona, who's running multi pod. It was very, very few. And this was in, what, five months? Four months ago? Whereas maybe our customers are just really super advanced because of our 100 plus customers. At four words, we Eric is right. A lot of them are already running multi cloud or if not their plan, in the planning stage right now. So even in the last +56 months, this has become a reality. And we're big fans of your vanities. I don't know if you know, Eric was the first product manager for Pernetti. T o k. He's too shy to say it on dhe. So yeah, and we think, you know, And when it does seem to be the answer to making all they caught a reality right now. >>Well, I want to get back into G k e. And Cooper was very notable historical. So congratulations. But your point about multi cloud is interesting because, you know, having multiple clouds means things, right? So, for instance, if I upgrade to office 3 65 and I killed my exchange server, I'm essentially running azure by their definition. If I'm building a stack I need of us, I'm a Navy best customer. Let's just say I want to do some tensorflow or play with big table. Are spanner on Google now? I have three clouds. No, they're not saying they have worked low specific objectives. I am totally no problem. I see that all the progressive customers, some legacy. I need to be people like maybe they put their tone a file. But anyone doing meaningful cloud probably has multiple clouds, but that's workload driven when you get into tying them together. It's interesting. I think that's where I think you guys have a great opportunity in this community because it open source convene the gateway to minimize the locket. What locket? I mean, like locking the surprise respect if its value, their great use it. But if I want to move my data out of the Amazon, >>you brought up so many good points. So let me go through a few and Lisa jumping. I feel like locking. People don't wanna be locked in at the infrastructure level. So, like you said, if there's value at the higher levels of Stack and it helps me do my business faster, that's an okay thing to exchange. But if it's just locked in and it's not doing anything. They're that's not equal exchange, right? So there's definitely a move from infrastructure up the platform. So locking in infrastructure is what people are trying to move away from. From what we see from the perspective of legacy, there is a lot of things happening in industry that's pretty exciting. How legacy will also start to run in containers, and I'm sure you've seen that. But containers being the basis you could run a BM as well. And so that will mean a lot for in terms of how VM skin start to be matched by orchestrators like kubernetes. So that is another movement for legacy, and I wanted to acknowledge that point now, in terms of the patterns, there are definitely applications, like a hybrid pattern where connect the car has to upload all its data once it docks into its location and move it to the data center. So there are patterns where the workflow does move the ups are the application data between on Prem into a public cloud, for instance, and then coming back from that your trip with Lisa. There is also examples where regulations require companies to enterprise is to be able to move to another cloud in a reasonable time frame. So there's definitely a notion of Multi Cloud is both an architectural design pattern. But it's also a sourcing strategy and that sourcing strategies Maura regulation type o. R in terms of not being locked in. And that's where I'm saying it's all those things. >>You love to get your thoughts on this because I like where you're going with this because it kind of takes it to a level of Okay, standardization kubernetes nights containing one does that. But then you're something about FBI gateways, for instance. Right? So if I'm a car, have five different gig weighs on my device devices or I have multiple vendors dealing with control playing data that could be problematic. I gotta do something. So I started envisioned. I just made that this case up. But my point is, is that you need some standards. So on the A p I side was seeing some trends there once saying, Okay, here's my stuff. I'll just pass Paramus with FBI, you know, state and stateless are two dynamics. What do you make of that? What? What what has to happen next to get to that next level of happiness and goodness because Ruben is has got it, got it there, >>right? I feel like next level. I feel like in Lisa. Please jump. And I feel like from automation perspective, Kubernetes has done that from a P I gateway. And what has to happen next. There's still a lot of easy use that isn't solved right. There's probably tons of opportunities out there to build a much better user experience, both from operations point of view and from what I'm trying to do is an intense because what people aren't gonna automate right now is the intent to automate a lot of the infrastructure manual tasks, and that's goodness. But from how I docked my application, how the application did, it gets moved. We're still at the point of making policy driven, easy to use, and I think there's a lot of opportunities for everyone to get better there. >>That's like Logan is priority looking fruity manual stuff >>and communities was really good at the food. That's a really use case that you brought up really. People were looking at the data now, and when you're talking about persistent mean Cooney's is great for stateless, but for St Paul's really crucial data. So that's where we really come in. And a number of other companies in the cloud native storage ecosystem come in and have really fought through this problem and that data management problem. That's where this platform that Aaron was talking about >>We'll get to that state problem. Talk about your company. I wanna get back Thio, Google Days, um, many war stories around kubernetes. We'll have the same fate as map reduce. You know, the debates internally and Google. What do we do with it? You guys made a good call. Congratulations doing that. What was it like to be early on? Because you already had large scale. You already had. Borg already had all these things in place. Was it like there was >>a few things I'll say One is. It was intense, right? It was intense in the sense that amazing amount of intelligence, amazing amount of intent, and right back then a lot of things were still undecided, right? We're still looking at how containers are package. We're still looking at how infrastructure Kate run and a lot of the service's were still being rolled out. So what it really meant is howto build something that people want to build, something that people want to run with you and how to build an ecosystem community. A lot of that the community got was done very well, right? You have to give credit to things like the Sig. A lot of things like how people like advocates like Lisa had gone out and made it part of what they're doing. And that's important, right? Every ecosystem needs to have those advocates, and that's what's going well, a cz ah flip side. I think there's a lot of things where way always look back, in which we could have done a few things differently. But that's a different story for different >>will. Come back and get in the studio fellow that I gotta ask you now that you're outside. Google was a culture shock. Oh my God. People actually provisioning software. Yeah, I was in a data center. Cultures. There's a little >>bit of culture shock. One thing is, and the funny thing is coming full circle in communities now, is that the idea of an application, right? The idea of what is an application eyes something that feels very comfortable to a lot of legacy traditional. I wanna use traditional applications, but the moment you're you've spent so much time incriminates and you say, What's the application? It became a very hard thing, and I used to have a lot of academic debates wise saying there is no application. It's it's a soup of resources and such. So that was a hard thing. But funny thing is covered, as is now coming out with definitions around application, and Microsoft announced a few things in that area to so there are things that are coming full circle, but that just shows how the movement has changed and how things are becoming in some ways meeting each other halfway. >>Talk about the company. What you guys are doing. Taking moments explaining contacts. Multi Cloud were here. Put worse. What's the platform? It's a product. What's the value proposition? What's the state of the company? >>Yes. So the companies? Uh well, well, it's grown from early days when Lisa and I joined where we're probably a handful now. We're in four or five cities. Geography is over 100 people over 150 customers and there. It's been a lot of enterprises that are saying, like, How do I take this pattern? Doing containers and micro service is, and how do I run it with my mission? Critical business crinkle workloads And at that point, there is no mission critical business critical workload that isn't stable so suddenly they're trying to say, How do I run These applications and containers and data have different life cycles. So what they're really looking for is a data plane that works with the control planes and how controlled planes are changing the behavior. So a lot of our technology and a lot of our product innovation has been around both the data plane but a storage control plane that integrates with a computer controlled plane. So I know we like to talk about one control plane. There's actually multiple control planes, and you mentioned security, right? If I look at how applications are running way, acting now securely access for applications and it's no longer have access to the data. Before I get to use it, you have to now start to do things like J W. T. Or much higher level bear tokens to say I know how to access this application for this life cycle for this use case and get that kind of resiliency. So it's really around having that >>storage. More complexity, absolutely needing abstraction layers and you compute. Luckily, work there. But you gotta have software to do it >>from a poor box perspective. Our products entirely software right down loans and runs using kubernetes. And so the point here is we make remarries able to run all the staple workloads out of the box using the same comment control plane, which is communities. So that's the experiences that we really want to make it so that Dev Ops teams can run anywhere close. And that's that's in some ways been part of the mix. >>Lisa, we've been covering Jeff up. Go back to 2010. Remember when I first I was hanging around? San Francisco? Doesn't eight Joint was coming out the woodwork and all that early days. You look at the journey of how infrastructures code. We'll talk about that in 2008 and now we'll get 11 years later. Look at the advancements you've been through this now the tipping point just seems like this wave is big and people are on developers air getting it. It's a modern renaissance of application developers, and the enterprise it's happening in the enterprise is not just like the energy. You're one Apple geeks or the foundation. It's happening in >>everyone's on board this time, and you and I have been in the trenches in the early stages of many open source projects. And I think with kubernetes Arab reference of community earlier, I'm super proud to be running the world's largest CNC F for user group. And it's a great community, a diverse community, super smart people. One of my favorite things about working poor works is we have some really smart engineers that have figured out what companies want, how to solve problems, and then we'll go credible open source projects. We created a project called autopilot, really largely because one of our customers, every who's in the G s space and who's running just incredible application, you can google it and see what the work they're doing. It's all out there publicly. Onda we built, you know, we've built an open source project for them to help them get the most out of kubernetes we can say so there's a lot of people in the community system doing that. How can we make communities better? Half We make competitive enterprise grade and not take years to do that. Like some of the other open source projects that we worked on, it took. So it's a super exciting time to be here, >>and open source is growing so fast. Now just think about having project being structured. More and more projects are coming online and user profit a lot more. Vendor driven projects, too used mostly and used with. Now you have a lot of support vendors who are users, so the line is blurring between then their user in open source is really fast. >>Will you look at the look of the landscape on the C N. C. F? You know the website. I mean, it's what 400 that are already on board. It's really important. >>They don't have enough speaking slasher with >>right. I know, and it's just it. It is users and vendors. Everybody's in the community together. It's one of things that makes it super exciting, and it's how we know this is This was the right choice for us. Did they communities because that's what? Everybody? >>You guys are practically neighbors. We look for CNN Studio, Palo Alto. I wanna ask you one final question on the product side. Road map. What you guys thinking As Kubernetes goes, the next level state, a lot of micro service is observe. Ability is becoming a key part of it. The automation configuration management things are developing fast. State. What's the road for you guys? For >>us, it's been always about howto handle the mission critical and make that application run seamlessly. And then now we've done a lot of portability. So disaster recovery is one of the biggest things for us is that customers are saying, How do I do a hybrid pattern back to your earlier question of running on Prem and in Public Cloud and do a D. R fail over into a Some of the things, at least, is pointing out. That we're announcing soon is non Terry's autopilot in the idea of automatically managing applications scale from a volume capacity. And then we're actually going to start moving a lot more into some of what you do with data after the life cycle in terms of backup and retention. So those are the things that everyone's been pushing us, and the customers are all asking, >>You know, I think data that recovery is interesting. I think that's going to change radically. And I think we look at the trend of how yeah, data backup recovery was built. It was built because of disruption of business, floods, our games. That's right. It is in their failure. But I think the biggest disruptions ransomware that malware. So security is now a active disruptor, So it's not like it After today. If we hadn't have ah, fire, we can always roll back. So you're infected and you're just rolling back infected code. That's a ransomware dream. That's what's going on. So I think data protection needs to redefine. >>What do you think? Absolutely. I think there's a notion of how do I get last week's data last month and then oftentimes customers will say If I have a piece of data volume and I suddenly have to delete it, I still need to have some record of that action for a long time, right? So those are the kinds of things that are happening and his crew bearnaise and everything, it gets changed. Suddenly, the important part is not what was just that one pot it becomes. How do I reconstruct everything? Action >>is not one thing. It's everywhere That's right, protected all through the platform. It is a platform decision. It's not some cattlemen on the side. >>You can't be a single lap. It has to be entire solution. And it has to handle things like, Where do you come from? Where is it allowed to go? >>You guys have that philosophy? >>We absolutely. And it's based on the enterprises that are adopting port works and saying, Hey, this is my romance. I'm basing it on Kubernetes here, my data partner. How do you make it happen? >>This speaks to your point of why the enterprise is in the vendors jumped in. This is what people care about security. How do you solve this last mile problem? Storage, Networking. How do you plug those holes and kubernetes? Because that is crucial. >>One personal private moment. Victory moment for me personally, Waas been a big fan of Cuban, is actually, you know, for years in there when it was created, talked about one of moments that got me was personal. Heartfelt moment was enterprise buyer on. The whole mindset in the enterprise has always been You gotta kill the old to bring in the new. And so there's always been that tension of a you know, the shame, your toy from Silicon Valley or whatever. You know, I'm not gonna just trash this and have a migration is a pain in the butt fried. You don't want that to do that. They hate doing migrations, but with containers and kubernetes, they actually they don't end of life to bring in the new project they could do on their own or keep it around. So that took a lot of air out of the tension in on the I t. Side. Because it's a great I can deal with the life cycle of my app on my own terms and go play with Cloud native and said to me, I was like, That was to be like, Okay, there it is. That was validation. That means this is real because now they will be without compromising. >>I think so. And I think some of that has been how the ecosystems embraced it, right, So now it's becoming all the vendors are saying My internal stack is also based on company. So even if you as an application owner or not realizing it, you're gonna take a B M next year and you're gonna run it and it's gonna be back by something like >>the submarine and the aircon. Thank you for coming on court. Worse Hot started Multiple cities Kubernetes Big developer Project Open Source Talking about multi cloud here at the inaugural Multi Cloud Conference in New York City Secu Courage of Escape Plan 19 John Corey Thanks for watching.

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum, World 2019 brought to you by the M Wear and its ecosystem partners. >> Hey, welcome back, everyone. Live Cube coverage of the emerald 2019 were here in San Francisco, California Mosconi North Lobby. Two sets Our 10th year covering the emerald in our 20th year of Of of our seasons of covering Me to be enterprised Tech. I'm Jeffrey Day Volonte student Justin Warren breaking down day to Cube insights segment. Dave's Do You Do You're on Set Valley set this the meadow set because it's got the steamboat chirping birds behind us. Justin, you've been doing some interviews out on the floor as well. Checking the story's out. All the news is out. Day one was all the big corporate stuff. Today was the product technology news stew. I'll go to you first. What's the assessment on your take on the M, where obviously they're reinventing themselves? Jerry Chen, who we interviewed, said this is Act three of'em where they keep on adding more and more prostitute their core, your thoughts on what's going on. >> So the biggest whore I've seen is the discussion of Tom Zoo, which really talking those cloud native applications. And if you break down VM wear, it's like many companies that said, There's the, you know, core product of the company. It is vey sphere. It is the legacy for what we have and it's not going anywhere, and it's changing. But, you know, then there's the modernization project Pacific howto a bridge to the multi cloud world. How do I bridge Kubernetes is going to come into the sphere and do that? But then there's the application world into the thing I've been. You know, the existential threat to VM, where I've been talking about forever is if we sas if I and cloud If I and all the APS go away, the data centers disappear in Vienna, where dominant, the data center is left out in the cold. So, you know, Pivotal was driving down that that path. They've done a lot of acquisitions, so love directionally where towns who's going time will tell whether they can play in that market. This is not a developer conference. We go to plenty of developer events, so, you know, that's you know, some of the places. I see you know, and and still, you know, >> narrator conference. You're right. Exactly Right. And just I want to get your thoughts, too, because you've been blocking heavily on this topic as well. Dev Ops in general, commenting on the Cube. You know, the reality and the reality, Uh, and the reality of situation from the the announcement. That's a vapor. They're doing some demos. They're really product directions. So product directions is always with VM. Where does it? It's not something that their shameful love, that's what they do. That's what they put out. It's not bakery >> company. It's a statement, A statement of >> direction. We were talking hybrid cloud in 2012 when I asked Pet guess it was a halfway house. He blew a gasket. And now, five years later, the gestation period for hybrid was that. But the end was happy to have the data center back in the back. In the play here, your thoughts on >> Yeah. So this conference is is, I think, a refreshing return to form. So, Vienna, where is as you say, this is an operators conference in Vienna. Where is for operators? It's not Four Dev's. There was a period there where cloud was scary And it was all this cloud native stuff in Vienna where tried to appeal to this new market, I guess tried to dress up and as something that it really wasn't and it didn't pull it off and we didn't It didn't feel right. And now Veum Way has decided that Well, no, actually, this is what they and where is about. And no one could be more Veum where than VM wear. So it's returning to being its best self. And I think you >> can software. They know software >> they know. So flick. So the addition of putting predict Enzo in and having communities in there, and it's to operate the software. So it's it's going to be in there an actual run on it, and they wanna have kubernetes baked into the sphere. So that now, yeah, we'll have new a new absent. Yeah, there might be SAS eps for the people who are consuming them, but they're gonna run somewhere. And now we could run them on van. Wait. Whether it's on Silent at the edge could be in the cloud your Veum wear on eight of us. >> David David so I want to get your thoughts just don't want to jump into because, you know, I love pivotal what they've done. I've always felt as a standalone company they probably couldn't compete with Amazon to scale what's going on in the other things. But bring it back in the fold in VM, where you mentioned this a couple of our interviews yesterday, Dave, and still you illuminate to to the fact of the cloud native world coming together. It's better inside VM wear because they can package pivotal and not have to bet the ranch on the outcome in the marketplace where this highly competitive statements out there so you get the business value of Pivotal. The upside now can be managed. Do your thoughts first, then go to date >> about Pivotal. Yeah, as >> an integrated, integrated is better for the industry than trying to bet the ranch on a pier play >> right? So, John, yesterday we had a little discussion about hybrid and multi cloud and still early about there, but the conversation of past five years ago was very different from the discussion. Today, Docker had a ripple effect with Containers and Veum. Where is addressing that and it made sense for Pivotal Cut to come home, if you will. They still have the Pivotal Labs group that can work with customers going through that transformation and a number of other pieces toe put together. But you ve m where is doing a good enough job to give customers the comfort that we can move you forward to the cloud. You don't have to abandon us and especially all those people that do VM Where is they don't have to be frozen where they are >> a business value. >> Well, I think you've got to start with the transaction and provide a historical context. So this goes back to what I used to call the misfit toys. The Federation. David Golden's taking bits and pieces of of of Dragon Pearl of assets in side of E, M. C and V M wear and then creating Pivotal out of whole cloth. They need an I P O. Michael Dell maintained 70% ownership of the company and 96% voting shares floated. The stock stock didn't do well, bought it back on 50 cents on the dollar. A so what the AIPO price was and then took a of Got a Brit, brought back a $4 billion asset inside of the M wear and paid $900 million for it. So it's just the brilliant financial transaction now, having said all that, what is the business value of this? You know, when I come to these shows, I'd liketo compare what they say in the messaging and the keynotes to what practitioners are saying in the practitioners last night were saying a couple of things. First of all, they're concerned about all the salmon. A like one. Practitioners said to me, Look, if it weren't for all these acquisitions that they announced last minute, what would we be hearing about here? It would have been NSX and V san again, so there's sort of a little concerns there. Some of the practitioners I talked to were really concerned about integration. They've done a good job with Nasasira, but some of the other acquisitions that they may have taken longer to integrate and customers are concerned, and we've seen this movie before. We saw the DMC. We certainly saw the tell. We're seeing it again now, at the end where Veum where? Well, they're very good at integrating companies. Sometimes that catches up to you. The last thing I'll say is we've been pushing You just mentioned it, Justin. On Dev's not a deaf show. Pivotal gives VM where the opportunity to whether it's a different show are an event within the event to actually attract the depths. But I would say in the multi cloud world, VM wears sitting in a good position. With the exception of developers pivotal, I think it's designed to solve that problem. Just tell >> your thoughts. >> Do you think that Veum, where is, is at risk of becoming a portfolio company just like a M A. M. C. Watts? Because it certainly looks at the moment to me like we look at all the different names for things, and I just look at the brand architecture of stuff. There are too many brands. There are too many product names, it's too confusing, and there's gonna have to be a culottes some point just to make it understandable for customers. Otherwise, we're just gonna end up with this endless sprawl, and we saw what the damage that did it. At present, I am saying >> it's a great point and Joseph Joe to cheese used to say that overlap is better than gaps, and I and I agree with him to appoint, you know better until it's not. And then Michael Dell came in and Bar came and said, Look, if we're gonna compete with Amazon's cost structure, we have to clean this mess up and that's what they've been doing it a lot of hard work on that. And so, yeah, they do risk that. I think if they don't do that integration, it's hard to do that. Integration, as you know, it takes time. Um, and so I have Right now. All looks good, right? Right down the middle. As you say, John, are >> multi cloud. Big topic gestation period is going to take five years to seven years. When the reality multi cloud a debate on Twitter last night, someone saying, I'm doing multi cloud today. I mean, we had Gelsinger's layout, the definition of multi cloud. >> Well, he laid out his definition definition. Everyone likes to define its. It's funny how, and we mentioned this is a stew and I earlier on the other set, cloud were still arguing about what cloud means exit always at multi cloud, which kind of multi cloud is a hybrid bowl over. And then you compare that to EJ computing, which computing was always going on. And then someone just came along and gave it a name and everyone just went, huh? OK, and go on with their lives. And so why is cloud so different and difficult for people to agree on what the thing is? >> There's a lot of money being made and lost, That's why >> right day the thing I've said is for multi cloud to be a real thing, it needs to be more valuable to a customer than the sum of its pieces on. And, you know, we know we're gonna be an Amazon reinvent later this year we will be talking, you know? Well, they will not be talking multi cloud. We might be talking about it, but >> they'll be hinting to hybrid cloud may or may not say >> that, you know, hybrid is okay in their world with outpost and everything they're doing in there partnering with VM wear. But you know, the point I've been looking at here is you know, management of multi vendor was atrocious. And, you know, why do we think we're going to any better. David, who hired me nine years ago. It was like I could spend my entire career saying, Management stinks and security needs to be, >> you know, So I want to share lawyers definition. They published in Wicked Bon on Multiply Multi Cloud Hybrid Cloudy, Putting together True Hybrid Cloud Multiply Any application application service can run on any node of the hybrid cloud without rewriting, re compiling or retesting. True hybrid cloud architectures have a consistent set of hardware. Software service is a P I is with integrated network security data and control planes that are native to and display the characteristics of public cloud infrastructure is a service. These attributes could be identically resident on other hybrid nodes independent of location, for example, including on public clouds on Prem or at the edge. That ain't happening. It's just not unless you have considered outposts cloud a customer azure stack. Okay, and you're gonna have collections of those. So that vision that he laid out, I just I think it's gonna >> be David. It's interesting because, you know, David and I have some good debates on this. I said, Tell me a company that has been better at than VM wear about taking a stack and letting it live on multiple hardware's. You know, I've got some of those cars are at a big piece last weekend talking about, you know, when we had to check the bios of everything and when blade Service rolled out getting Veum whereto work 15 years ago was really tough. Getting Veum were to work today, but the >> problem is you're gonna have outposts. You're gonna have project dimensions installed. You're gonna have azure stacks installed. You're gonna have roll your own out there. And so yeah, VM where is gonna work on all >> those? And it's not gonna be a static situation because, you know, when I talk to customers and if they're using V M where cloud on AWS, it's not a lift and shift and leave it there, Gonna modernize their things that could start using service is from the public cloud and they might migrate some of these off of the VM where environment, which I think, is the thing that I am talking to customers and hearing about that It's, you know, none of these situations are Oh, I just put it there and it's gonna live there for years. It's constantly moving and changing, and that is a major threat to VM wears multi clouds, >> Traffic pushes. Is it technically feasible without just insanely high degrees of homogeneity? That's that's the question. >> I I don't think it is and or not. I don't think it's a reasonable thing to expect anyway, because any enterprise you have any M and a activity, and all of a sudden you've got more than one that's always been true, and it will always be true. So if someone else makes a different choice and you buy them, then we'll have both. >> So maybe that's not a fair definition, but that's kind of what what? One could infer that. I think the industry is implying that that is hybrid multi club because that's the nirvana that everybody wants. >> Yeah, the only situation I can see where that could maybe come true would be in something like communities where you're running things on as an abstraction on top off everything else, and that that is a common abstraction that everyone agrees on and builds upon. But we're already seeing how that works out in real life. If >> I'm >> using and Google Antos. I can't easily move it to P. K s or open shift. There's English Kubernetes, as Joe Beta says, is not a magic layer, and everybody builds. On top of >> it, is it? Turns out it's actually not that easy. >> Well, and plus people are taken open source code, and then they're forking it and it building their own proprietary systems and saying, Hey, here's our greatest thing. >> Well, the to the to the credit of CNC, if Kubernetes. Does have a kind of standardized, agreed to get away away from that particular issue. So that's where it stands a better chance and say unfortunately, open stack. So because we saw a bit of that change of way, want to go this way? And we want to go that way. So there's a lot of seeing and zagging, at least with communities. You have a kind of common framework. But even just the implementation of that writing it, >> I love Cooper. I think I've been a big fan of committed from Day one. I think it's a great industry initiative. Having it the way it's rolling out is looking very good. I like it a lot. The comments that we heard on the Cube of Support. Some of my things that I'm looking at is for C N C s Q. Khan Come coop con Coming up is what happened with Kay, native and SDO because that's what I get to see the battleground for above Goober Netease. You see, that's what differentiates again. That's where that the vendors are gonna start to differentiate who they are. So I think carbonates. It could be a great thing. And I think what I learned here was virtualization underneath Kubernetes. It doesn't matter if you want to run a lot. Of'em Furat scale No big deal run Cooper's on top. You want to run in that bare metal? God bless you, >> Go for it. I think this use cases for both. >> That's why I particularly like Tenzer is because for those customers who wanna have a bit of this, cupidity is I don't want to run it myself. It's too hard. But if I trust Vienna where to be able to run that in to upgrade it and give me all of the goodness about operating it in the same way that I do the end where again we're in and I'll show. So now I can have stuff I already know in love, and I can answer incriminating on top of it. >> All right, But who's gonna mess up Multi clouds do. Who's the vendor? I'm not >> even saying it s so you can't mess up something that >> who's gonna think vision, this vision of multi cloud that the entire industry is putting forth who's gonna throw a monkey? The rich? Which vendor? Well, screw it. So >> you know, licensing usually can cause issues. You know, our friend Corey Crane with a nice article about Microsoft's licensing changes there. You know, there are >> lots of Amazon's plays. Oh, yeah. Okay. Amazon is gonna make it. >> A multi clock is not in the mob, >> but yet how could you do multi cloud without Amazon? >> They play with >> control. My the chessboard on my line has been Amazon is in every multi cloud because if you've got multiple clouds, there's a much greater than likely chance >> I haven't been. You know, my feeling is in looking at the history of how multi vendor of all from the I T industry from proprietary network operating systems, many computers toe open systems, D c P I P Web, etcetera. What's going on now is very interesting, and I think the sea so ce of the canary in the coal mine, not Cee Io's because they like multi vendor. They want multiple clouds. They're comfortable that they got staff for that si sos have pressure, security. They're the canary in the coal mine and all the seasons lights, while two are all saying multi clouds b s because they're building stacks internally and they want to create their own technology for security reasons and then build a P eyes and make a P. I's the supplier relationship and saying, Hey, supplier, if you want to work with me, me support my stack I think that is an interesting indication. What that means is that the entire multi cloud thing means we're pick one clown build on, have a backup. We'll deal with multiple clouds if there's workloads in there but primary one cloud, we'll be there. And I think that's gonna be the model. Yes, still be multiple clouds and you got azure and get office 3 65 That's technically multi cloud, >> but I want to make a point. And when pats on we joke about The cul de sac is hybrid cloud a cul de sac, and you've been very respectful and basically saying Yap had okay, But But But you were right, Really. What's hybrid would show me a hybrid cloud. It's taken all this time to gestate you where you see Federated Applications. It's happening. You have on prim workloads, and you have a company that has public cloud workloads. But they're not. Hybrid is >> the region. Some we'll talk about it, even multi. It is an application per cloud or a couple of clouds that you do it, but it's right. Did he follow the sun thing? That we might get there 15 years ago? Is >> no. You're gonna have to insist that this >> data moving around, consistent >> security, governance and all the organizational edicts across all those platforms >> the one place, like all week for that eventually and this is a long way off would be if you go with Serverless where it's all functions and now it's about service composition and I don't care where it lives. I'm just consuming a service because I have some data that I want to go on process and Google happens to have the best machine learning that I need to do it on that data. Also use that service. And then when I actually want to run the workload and host it somewhere else, I drop it into a CD in with an application that happens to run in AWS. >> Guys wrapping up day to buy It's just gonna ask, What is that animal? It must be an influence because hasn't said a word. >> Thistles. The famous blue cow She travels everywhere with me, >> has an INSTAGRAM account. >> She used to have an instagram. She now she doesn't. She just uses my Twitter account just in time to time. >> I learned a lot about you right now. Thanks for sharing. Great to have you. Great as always, Great commentary. Thanks for coming with Bay three tomorrow. Tomorrow. I want to dig into what's in this for Del Technologies. What's the play there when I unpacked, that is tomorrow on day three million. If there's no multi cloud and there's a big tam out there, what's in it for Michael Dell and BM where it's Crown Jewel as the main ingredient guys, thanks for coming stupid in Manchester words, David Want them? John, Thanks for watching day, too. Inside coverage here are wrap up. Thanks for watching

>> fly from San Francisco. It's the Cube covering Google Cloud next nineteen Tio by Google Cloud and its ecosystem partners. >> Run. Welcome to the Cube here, live in San Francisco on Mosconi South were on the floor at Google. Next twenty nineteen. Hashtag Google Next nineteen. I'm John for my co host this week for three days and wall to wall coverage of Google's cloud conference is with Dave. Alonso Has too many men. Guys day one of three days of wall to wall coverage. We got Thomas Curry in the new CEO on the job for ten weeks. Took the realm from Diane Green. Thirty five thousand attendees. It's packed. It's definitely a developer crowd. It feels a lot like a WS, not a corporate show like Microsoft or IBM or others or Oracle. It's really more about developers. We just heard the Kino. Google's making some moves. The new CEO is gonna put on a show. He saw two customers you see in the positioning. Soon DARPA Kai, the CEO of Google, came out really kind of. Ah, interesting keynote Feels like Thomas's that's gonna shake that Oracle off, but he's guns blaring. Some new announcements. Guys, let's do a round upon the keynote. >> Yeah. So, John, as you said, a great energy here that this place is bustling sitting here where we are, we could see everybody is going through the Expo Hall. As you said. Is Google serious about this? This whole cloud activity? Absolutely. There's no better way than to have your CEO up. There we go, The Amazon show. You don't see Jeff Bezos there into the Microsoft shows? You know, you don't usually see you know their CEO. There you have the Cloud Group does the cloud thing, but absolutely. Cloud is a critical piece of what Google is doing. And it's interesting because I actually didn't feel as geeky and his developer focused as I would expect to see at a Google show. Maybe they've heard that feedback for years that, you know, Google makes great stuff, but they're too smart in there, too geeky When you go to the Amazon show, they're announcing all of the different, you know, puting storage pieces and everybody's hooting and hollering. Here it was a little bit more business. It was high level. They had all these partners out on stage and customers out on stage. Many of them, you know, you talk about retail and health care and all these other ones where you say, Okay, Amazons, a major competitor there. So, you know, can Google stake their claim as to how they're going to move up from the number three position and gain more market share? You know, as they fit into the multi cloud, which we know we're going to spend a lot of time on, wears their position in this cloud space today. >> What your thoughts. >> Well, first of all, there's a big show. I mean, it's we're here at IBM thick in February. This feels like a much, much larger event, Number one Stew said. It's really much more developer heavy, I think. John, there's no question people don't question Googles Global Cloud Presence. Soon Dar talked about two hundred countries, ninety cloud regions fifty eight plus two new data centers. So no question there. But there are questions as to whether or not Google could move beyond search and maps and Gmail and really be a big cloud player for Enterprise Cloud that really is to the elephant in the room. Can Google innovate and attractive CEOs? They showed a number of customers, not nearly, of course, as many as what Amazon or even Microsoft would show. They're talking about ecosystem. To me, that ecosystem slide. It's got a cord truthful this year to really show some progress. But you've got new leadership as we talked about last year, John and love to get your thoughts on this. Google's playing the long game. They've got the best tech and you know they've got great data. Great. Aye, aye. I want to take >> into the new rebranding of the Google Cloud platform, which is now called Antos, which is a Greek word for flour. We kind of had visibility into This would kind of start coming. But before we get into that, I want to just kind of point out something that we've reported on looking angle, some that we've been saying on Twitter on DH about Diane Greene. It's been reported that she was fired from Google for missing on red hat. All these rumors, but interesting Thomas Koreans first words, a CEO on stage. It was a direct shout out to Diane Greene. I think this validates our reporting and our analysis that Diane Green absolutely helped hire curry and work with the boy workers Sundar And essentially, because she was the architect of rebuilding Google Clouds Enterprise chops the team there that she recruited we've been following and covering. Diane Green built that foundation. She passed the torch. Thomas Curry. This was not a Diane Green firing, so I think I think Thomas Carrion nice gesture on Diane Green kind of sets the table and validates and preserves her legacy as the rebuilder re architect of Google Cloud. >> Pretty interesting. Yeah. I mean, you know, I think this where there's some smoke, there's fire that don't think Diana Corning court fired. I think you know that she was under a lot of pressure. She was here for seven years. I think they probably felt like Okay, now it's time to really bring somebody in. Who wants to take this to the next level? And I'll die unnecessarily had the stomach for that >> John Really great points there. But it does talk about you know what is the culture of Google? You know, the elephant The room is what is Google? Google makes you know most of their money on advertising. That's not what Google Cloud is. It doesn't fit into the additional model. You know, Google's culture is not geared for the enterprise. As you know that the critique on Google for years has been We make really great stuff and you need to be Google E. And you need to do things the way we do Thomas Koreans out there. We need to meet customers where they are today. That's very much what we hear in the Enterprise. That that's what you hear. You know when you talk about Amazon or Microsoft, they're listening to their customers. They're meeting them at their business applications there, helping them build new environment. So, you know, will Google be a little less googly on DH? Therefore, you know, meet customers and help work them, and that leads to the multi clouding the anthros discussed. >> We heard a lot about that today. I mean, John, you've pointed out many, many times that Cooper Netease is the linchpin to Google strategy. It's really you know, that was the kind of like a Hail Mary relative Tae Ws and that's what we heard today. Multi cloud, multi cloud, multi cloud, where is with a W s. And certainly to a lesser extent, Oracle. It's Unit Cloud Multi Cloud is more expensive is what they tell us. Multi cloud is less secure. A multi cloud is more complex. Google's messaging is exactly the opposite of >> that. So, Dave, just to poke it that a little bit, is great to see Sanjay *** Inn up on stage with VM wear. But where we last cvm were to cloud show. It's an Amazon. They've got a deep partnership here. Cooper Netease is not a differentiator for Google. Everybody's doing it. Even Amazon is being, you know, forced to be involved in it. Cisco was up on stage. This guy's got a deep partnership with Amazon and a ks. So you know, Cooper Netease is not a magic layers. Good job, Ada said on the Cube. Q. Khan. It is something that you know Google, that management layer and how I live in a multi cloud environment. Yes, Google might be further along with multi cloud messaging, then say Amazon is, But you know, Amazons, the leader in this space and everybody that has multiple clouds, Amazons, one of them, even the keynote >> This morning aboard Air Force right eight, I was forced into Cooper days you're not CNW s run demos that show, you know, a target of the Google clouded the Microsoft. You saw that today from Google >> while we see how the Amazon demos with our oracle. But that's the result. Let's let's hold off on the partisan saying, Let's go through the Kino So the Diane Green comment also AOL came out. Who runs VP of Engineer. He's the architect. One. This Antos product. Last year, they announced on G. C. P s basically a hybrid solution G a general availability of Antos, which has security built in out of the box. Multi cloud security integrated for continues integration, confused development, CCD pipeline ing very key news and that was really interesting. This is such a their new platform that they've rebranded called Antos. This is a way for them to essentially start posturing from just hybrid to multi cloud. This is the shift of of Google. They want to be the on premise cloud solution and on any cloud, your thoughts. >> You know, the demo said it all. The ability to take V m movement two containers and move them anywhere right once and move anywhere and that, I think, is is the key differentiator right now. Relative to certainly eight of us. Lesser extent Microsoft, IBM right there with red hat. That's to me The interesting angle >> Here. Look, Google has a strong history with Ken Containers. If you if you scroll back to the early days of doctor twenty fourteen, twenty, fifty, Google's out there as to how many you know, it just so many containers that they're building up and tearing down. However you go to the Microsoft. So you go to the Amazon show. We're starting to talk a lot more about server list. We're gonna have the product lead for surveillance on today. I'm excited to dig into that because on a little bit concerned that Google is so deep in the containers and how you Burnett eases, they're looking for, like a native to connect the pieces, but that they are a little bit behind in some of the next generation architectures built on journalists for death. >> I want to make a point here if you're not the leader in cloud which, you know in Enterprise Cloud, which Google is not, you know, IBM is not or, you know, Oracle is not okay, fine, but if you don't have a cloud like Cisco or Dell or VM, where you have to go after multi cloud. Amazon's not in a rush to go after multi cloud. There's no reason down the road. Amazon can't go after that opportunity. To the extent that it's a real tam, it's There's a long way to go. Talk about early innings were like having started the game of Outpost >> hasn't even been spect out. Yes, sir, there has not been relieved. So we're seeing what Amazon's got knowing they are the clouds. So they're the incumbent. Interesting enough on Jennifer Lin. You mention the demo. Jennifer Lin Cube alumni. We gonna interview her later. She introduced on those migrate Kind of reminds me of some of the best shows we have the migration tools and that migrates work clothes from PM wears into containers running in containers. As you mentioned. A. This is an end and no modified co changes. That's a big deal, >> John. Exactly on Twitter, people are going. Is this the next emotion? You know, those of us who've been in the industry while remember how powerful that was able to seamlessly migrate? You know, the EMS and containers at, You know, I shouldn't have to think about Colin building it where it lives. That was the promise of has for all those years and absolutely things like uber Netease what Google's doing, chipping away at that. They're partnering with Cisco, there partner with pivotal parting with lots of companies so that that portability of code isa lot of >> Master Jack is a cloud of emotion. I mean, we know what the motion did in the Enterprise. >> To me, that's the star. The keynote is actually the rebranding associate positioning thing. But the star of the show is the Jennifer Lin demo, because if anthems migrate actually works, that's going to tell. Sign to me on how fast Google can take territory now. What's interesting also with the announcements, was, I want to get you guys thoughts on this because we cover ecosystems, we cover how Cloud and Enterprise have been pardoning over the years. Enterprise is not that easy. Google has found out the hard way Microsoft is done really well. They've installed base. Google had stand this up from the beginning again. Diane Greene did a great job, but now it's hard. It's a hard nut to crack. So you see Cisco on stage. Cisco has huge enterprise. Cloud the em Where comes on stage? David Gettler Gettler, the VP of engineering of Cisco, one of their top executives on stage. And he has Sanjay *** and keep alumni came on. Sanjay had more time. Francisco. So you have two companies who kind of compete? NSX. We have suffered a fine Cisco both on stage. Cisco, absolutely integrating into We covered on silicon angle dot com just posted it live where Cisco is actually laying down their container platform and integrating directly into Google's container platform to offer a program ability End to end. I think that's something that didn't get teased out on the keynotes doing, because this allows for Google to quickly move into the enterprise and offer true program ability of infrastructure. This is the nirvana of infrastructure is code. This is what Dev Ops has been waiting for. Still your thoughts on this because this could be a game changer. Hydro, what's an A C I. This could put pressure on VM, where with the containers running in platform and the Cisco relationship your thoughts. >> So John Cisco has a broad portfolio. When you talk about multi cloud, it's not just the networking components, it's the eyes, absolutely apiece. But that multi cloud management, uh, is a layer that Cisco has, you know, been adding two and working on for a lot of years, and they've got very key partnerships. So making sure, you know, seeing right seeing David vehicular onstage here. Proof, Cisco, lot of enterprise customers him where, Of course, six hundred thousand customers. They're So Google wants to get into these accounts. You look at, you know, Microsoft strength of their enterprise agreements that they have. So how will Google get into some of these big accounts? Get into the procurement, get into the environment? And there's lots of different methods and partnerships We said our credit >> David vehicular undersold the opportunity here. I mean, when it comes to he did at working Inter Cloud. Sisko is in the poll possession position to basically say we got the best network, the highest performance networks, the most secure networks, and we're in a position to connect all these clouds. And to me, that didn't come out today. So when you think about multi cloud, each of these companies is coming at it from a position of strength. Cisco. Very clearly dominant networking VM wear in virtual ization and I think that came through. And Sanjay *** ins, you know, keynote. I think again Gettler undersold it, but it's a great opportunity for Cisco and Google. >> Well, I think Google has a huge opportunity. It Cisco because if they have a go to market joint sales together, that could really catapult Google sails again. If I get really was kind of copy, we're we're Cisco. But Cisco look, a bm was on stage with them. I thought that was going to be a Hail Mary for for Sisko to kind of have bring that back. But then watching Sanjay Putin come on saying, Hey, we're okay, it's going to be a V m World And Pat Kelsey has been on the record saying, Coo Burnett eases the dial tone of the Internet stew. This is an interesting matchup between Cisco and BM, where your thoughts >> Yeah, so so right. There's so many pieces here, a cz to where their play way. No, there's competitive competition and, you know, partnerships. In a lot of these environments, Google actually has a long history of partnering. You know, I can't even think how many years ago, the Google and GM or Partnership and Cisco. If I can't actually, Dave, there's There's something I know you've got a strong viewpoint on. You know, Thomas Kurian left Oracle and it was before he had this job. Every he says, you know, is T. K going to come in here and bring, you know, oracles, you know, sales methodology into Google. You know, What does he bring? What's his skill set on? You know >> what exact community? I think it's the opposite, right? I think that's why you left Oracle because he didn't want every database to run in the Oracle, Cloudy realised is a huge opportunity out there. I think the messaging that I heard today is again it's completely I saw something on Twitter like, Oh, this is just like organ. It's nothing like Oracle. It's the It's the polar opposite opposite of what Oracle is doing. >> I think I think curry and can really define his career. This could be a nice swan song for him. As he takes Google with Diane Greene did builds it out, does the right deals if he can build on ecosystem and bring the tech chops in with a clear go to market. He's not going to hire the salespeople and the SCS fast enough. In my opinion, that's gonna be a really slow boat. Teo promised land. He's got to do some deals. He's gotta put Some Corp Devin Place has gotta make some acquisitions will be very in the sin. DARPA Kai, the CEO, said. We are investing heavily in cloud. If I'm Amazon, I'm worried about Google. I think they are dark horse. They have a lot of they have a clean sheet of paper. Microsoft, although has legacy install base. Google's got, I think, a lot more powder, if you will. Dave, >> what One little sign? I agree without John, I think you're absolutely right. The clean sheet of paper and deep pockets, you know, and the long game in the great tech. Uh, you have a son should be worried about Google. One little side note, it's still you. And I talked about this. Did you hear? Uh uh, Thomas asked Sanjay Putin about Dell, Dell Technologies, and Sunday is an executive. Dell was talking about the whole Del Technologies portfolio. I thought it was a very interesting nuance that we had previously seen from VM wear when they were owned by himself. >> Dave, you know, we see Delon Veum where are almost the same company these days that they're working together? But John, as you said, I actually like that. You know, we didn't have some big announcement today on an acquisition. Thomas Kurian says. He's got a big pocket book. He's going to be inquisitive, and it'LL be interesting to see, do they? By some company that has a big enterprise sales force. It can't just be old legacy sales trying to go into the cloud market. That won't work, but absolutely the lot of opportunities for them to go out. They didn't get get, huh? They didn't get red hat. So who will? Google Page? You >> guys are right on man. Sales Force is still a big question mark, And how can they hire that fast? That's a >> And again, he's only been on the job for ten weeks. I think is going to get his sea legs. I think it's him. He's going to come in. He's gonna ingratiating with culture. It'Ll be a quick decision. I think Google culture will accept or reject Thomas Curry and based upon his first year in operations, he's going to get into the team, and I think the Wall Street Journal kind of comment on that. Will he bring that Oracle? I thought that was kind of not a fair assessment, but I think he's got the engineering chops toe hang with Google. He kind of gets the enterprise mark one hundred percent been there, done that. So I think he's got a good shot. I think you could make the right moves. Of course we're here making the moves on the Cube here live for day, one of three days of wall to wall coverage. I'm sorry, David. Lock These two minute men here in Google, next in Mosconi in San Francisco Live will be back with more coverage after this short break.