>>Hi lisa martin here with the cubes coverage of demon 2021. I've got to alumni joining me. Please welcome back to the cube Danny. Alan beam's ceo Danny. It's great to see you. >>I am delighted to be here lisa. >>Excellent brian Schwartz is here as well. Google director outbound product management brian welcome back to the program. Uh >>thanks for having me again. Excited to be >>here. Excited to be here. Yes, definitely. We're gonna be talking all about what Demon google are doing today. But let's go ahead and start Danny with you. Seems vision is to be the number one trusted provider of backup and recovery solutions for the, for for modern data protection. Unpack that for me, trust is absolutely critical. But when you're talking about modern data protection to your customers, what does that mean? >>Yeah. So I always, I always tell our customers there's three things in there that are really important. Trust is obviously number one and google knows this. You've been the most trusted search provider uh, forever. And, and so we have 400,000 customers. We need to make sure that our products work. We need to make sure they do data protection, but we need to do it in a modern way. And so it's not just back up and recovery, that's clearly important. It's also all of the automation and orchestration to move workloads across infrastructures, move it from on premises to the google cloud, for example, it also includes things like governance and compliance because we're faced with ransomware, malware and security threats. And so modern data protection is far more than just back up. It's the automation, it's the monitoring, it's a governance and compliance. It's the ability to move workloads. Um, but everything that we look at within our platform, we focus on all of those different characteristics and to make sure that it works for our customers. >>One of the things that we've seen in the last year, Danny big optic in ransom were obviously the one that everyone is the most familiar with right now. The colonial pipeline. Talk to me about some of the things that the team has seen, what your 400,000 customers have seen in the last 12 months of such a dynamic market, a massive shift to work from home and to supporting SAS for clothes and things like that. What have you seen? >>Well, certainly the employees working from home, there's a massive increase in the attack surface for organizations because now, instead of having three offices, they have, you know, hundreds of locations for their end users. And so it's all about protecting their data at the same time as well. There's been this explosion in malware and ransomware attacks. So we really see customers focusing on three different areas. The first is making sure that when they take a copy of their data, that it is actually secure and we can get into, you know, a mutability and keeping things offline. But really taking the data, making sure it's secure. The second thing that we see customers doing is monitoring their environment. So this is both inspection of the compute environment and of the data itself. Because when ransomware hits, for example, you'll see change rates on data explode. So secure your data monitor the environment. And then lastly make sure that you can recover intelligently is let us say because the last thing that you want to do if you're hit by ransomware is to bring the ransomware back online from a backup. So we call this security cover re secure, restore. We really see customers focusing on those three areas >>And that restoration is critical there because as we know these days, it's not if we get hit with ransomware, it's really a matter of when. Let's go ahead now and go into the google partnership, jenny talked to me about it from your perspective, the history of the strength of the partnership, all that good stuff. >>Yeah. So we have a very deep and long and lengthy relationship with google um, on a number of different areas. So for example, we have 400,000 customers. Where do they send their backups? Most customers don't want to continue to invest in storage solutions on their premises. And so they'll send their data from on premises and tear it into google cloud storage. So that's one integration point. The second is when the running workloads within the clouds. So this is now cloud native. If you're running on top of the google cloud platform, we are inside the google America place and we can protect those workloads. A third area is around the google vm ware engine, there's customers that have a hybrid model where they have some capacity on premises and some in google using the VM ware infrastructure and we support that as well. That's a third area and then 1/4 and perhaps the longest running um, google is synonymous with containers and especially kubernetes, they were very instrumental in the foundations of kubernetes and so r K 10 product which does data protection for kubernetes is also in the google America place. So a very long and deep relationship with them and it's to the benefit of our customers. >>Absolutely. And I think I just saw the other day that google celebrated the search engine. It's 15th birthday. I thought what, what did we do 16 years ago when we couldn't just find anything we wanted brian talked to me about it from Google's perspective of being partnership. >>Yeah, so as Danny mentioned, it's really multifaceted, um it really starts with a hybrid scenario, you know, there's still a lot of customers that are on their journey into the cloud and protecting those on premises workloads and in some senses, even using beams capabilities to move data to help migrate into the cloud is I'd say a great color of the relationship. Um but as Danny mentioned increasingly, more and more primary applications are running in the cloud and you know, the ability to protect those and have, you know, the great features and capabilities, uh you know, that being provides, whether it be for GCB er VM where you know, capability and google cloud or things like G k e R kubernetes offering, which has mentioned, you know, we've been deep and wide in kubernetes, we really birthed it many, many years ago um and have a huge successful business in, in the managing and hosting containers, that having the capabilities to add to those. It really adds to our ecosystem. So we're super excited about the partnership, we're happy to have this great foundation to build together with them into the future. >>And Danny Wien launched, just been in february a couple of months ago, being backup for google cloud platform. Talk to us about that technology and what you're announcing at them on this year. >>Yeah, sure. So back in february we released the first version of the VM backup for G C p product in the marketplace and that's really intended to protect of course, i as infrastructure as a service workloads running on top of G C p and it's been very, very successful. It has integration with the core platform and what I mean by that is if you do a backup in G C P, you can do you can copy that back up on premises and vice versa. So it has a light integration at the data level. What we're about to release later on this summer is version two of that product that has a deep integration with the VM platform via what we call the uh team service platform, a PS themselves. And that allows a rich bidirectional uh interaction between the two products that you can do not just day one operations, but also day to operations. So you can update the software, you can harmonize schedules between on premises and in the cloud. It really allows customers to be more successful in a hybrid model where they're moving from on premises to the cloud. >>And that seems to be really critically important. As we talk about hybrid club all the time, customers are in hybrid. They're living in the hybrid cloud for many reasons, whether it's acquisition or you know, just the nature of lines of business leveraging their cloud vendor of choice. So being able to support the hybrid cloud environment for customers and ensure that that data is recoverable is table stakes these days. Does that give them an advantage over your competition Danny? >>It does. Absolutely. So customers want the hybrid cloud experience. What we find over time is they do trend towards the cloud. There's no question. So if you have the hybrid experience, if they're sending their data there, for example, a step one, step two, of course, is just to move the workload into the cloud and then step three, they really start to be able to unleash their data. If you think about what google is known for, they have incredible capabilities around machine learning and artificial intelligence and they've been doing that for a very long time. So you can imagine customers after they start putting their data there, they start putting their workloads here, they want to unlock it into leverage the insights from the data that they're storing and that's really exciting about where we're going. It's, they were early days for most customers. They're still kind of moving and transitioning into the cloud. But if you think of the capabilities that are unlocked with that massive platform in google, it just opens up the ability to address big challenges of today, like climate change and sustainability and you know, all the health care challenges that we're faced with it. It really is an exciting time to be partnered with Google >>Ryan. Let's dig into the infrastructure in the architecture from your perspective, help us unpack that and what customers are coming to you for help with. >>Yeah. So Danny mentioned, you know the prowess that google has with data and analytics and, and a, I I think we're pretty well known for that. Uh, there's a tremendous opportunity for people in the future. Um, the thing that people get just right out of the box is the access to the technology that we built to build google cloud itself. Just the scale and, and technology, it's, you know, it's, it's a, you know, just incredible. You know, it's a fact that we have eight products here at google that have a billion users and when you have, you know, most people know the search and maps and gmail and all these things. When you have that kind of infrastructure, you build a platform like google cloud platform and you know, the network as a perfect example, the network endpoints, they're actually close to your house. There's a reason our technology is so fast because you get onto the google private network, someplace really close to where you actually live. We have thousands and thousands of points of presence spread around the world and from that point forward you're riding on our internal network, you get better quality of service. Uh the other thing I like to mention is, you know, the google cloud storage, that team is built on our object storage. It's uh it's the same technology that underpins Youtube and other things that most people are familiar with and you just think about that for a minute, you can find the most obscure Youtube video and it's gonna load really fast. You know, you're not going to sit there waiting for like two minutes waiting for something to load and that same under underlying technology underpins GCS So when you're going to go and you know, go back to an old restore, you know, to do a restore, it's gonna load fast even if you're on one of the more inexpensive storage classes. So it's a really nice experience for data protection. It has this global network properties you can restore to a different region if there was ever a disaster, there's just the scale of our foundation of infrastructure and also, you know, Danny mentioned if we're super proud about the investments that google has made for sustainability, You know, our cloud runs on 100% renewable energy at the cloud at our scale. That's a lot of, that's a lot of green energy. We're happy to be one of the largest consumers of green energy out there and make continued investments in sustainability. So, you know, we think we have some of the greenest data centers in the world and it's just one more benefit that people have when they come to run on Google Cloud. >>I don't know what any of us would do without google google cloud platform or google cloud storage. I mean you just mentioned all of the enterprise things as well as the at home. I've got to find this really crazy, obscure youtube video but as demanding customers as we are, we want things asAP not the same thing. If you know, an employee can't find a file or calendar has been deleted or whatnot. Let's go in to finish our time here with some joint customer use case examples. Let's talk about backing up on prem workloads to google cloud storage using existing VM licensing Danny. Tell us about that. >>Yeah. So one of the things that we've introduced at beam is this beam, universal licensing and it's completely portable license, you can be running your workloads on premises now and on a physical system and then you can, you know, make that portable to go to a virtual system and then if you want to go to the cloud, you can send that data up to the work load up to the cloud. One of the neat things about this transition for customers from a storage perspective, we don't charge for that. If you're backing up a physical system and sending your your back up on premises, you know, we don't charge for that. If you want to move to the cloud, we don't charge for that. And so as they go through this, there's a predictability and and customers want that predictability so much um that it's a big differentiating factor for us. They don't want to be surprised by a bill. And so we just make it simple and seamless. They have a single licensing model and its future proof as they move forward on the cloud journey. They don't have to change anything. >>Tell me what you mean by future proof as a marketer. I know that term very well, but it doesn't mean different things to different people. So for means customers in the context of the expansion of partnership with google the opportunities, the choices that you're giving customers to your customers, what does future proof actually delivered to them? >>It means that they're not locked into where they are today. If you think about a customer right now that's running a workload on premises maybe because they have to um they need to be close to the data that's being generated or feeding into that application system. Maybe they're locked into that on premises model. Now they have one of two choices when their hardware gets to the end of life. They can either buy more hardware which locks them into where they are today for the next three years in the next four years Or they can say, you know what, I don't want to lock into that. I want to model the license that is portable that maybe 12 months from now, 18 months from now, I can move to the cloud and so it future proof some, it doesn't give them another reason to stay on premises. It allows them the flexibility that licensing is taken off the table because it moves with you that there's zero thought or consideration and that locks you into where you are today. And that's exciting because it unlocks the capabilities of the cloud without being handicapped if you will by what you have on premises. >>Excellent. Let's go to the second uh use case lift and shift in that portability brian. Talk to us about it from your perspective. >>Yeah, so we obviously constantly in discussions with our customers about moving more applications to the cloud and there's really two different kind of approach is the lift and shift and modernization. You know, do you want to change and run on kubernetes when you come to the cloud as you move it in? In some cases people want to do that or they're gonna obviously build a new application in the cloud. But increasingly we see a lot of customers wanting to do lift and shift, they want to move into the cloud relatively quickly. As Danny said, there's like compelling events on like refreshes and in many cases we've had a number of customers come to us and say look we're going to exit our data centers. We did a big announcement Nokia, they're gonna exit 50 data centers in the coming years around the world and just move that into the cloud. In many cases you want to lift and shift that application to do the migration with his little change as possible. And that's one of the reasons we've really invested in a lot of enterprise, more classic enterprise support type technologies. And also we're super excited to have a really wide set of partners and ecosystem like the folks here at Wien. So the customers can really preserve those technologies, preserve that operational experience that they're already familiar with on prem and use that in the cloud. It just makes it easier for them to move to the cloud faster without having to rebuild as much stuff on the way in. >>And that's critical. Let's talk about one more use case and that is native protection of workloads that run on g c p Danny. What are you enabling customers to do there? >>Well? So we actually merged the capabilities of two different things. One is we leverage the native Api is of G C p to take a snapshot and we merge that with our ability to put it in a portable data format. Now. Why is that important? Because you want to use the native capabilities of G CPU want to leverage those native snapshots. The fastest way to recover a file or the fastest way to recover of'em is from the G C p snapshot. However, if you want to take a copy of that and move it into another locale or you want to pull it back on premises for compliance reasons or put it in a long term storage format, you probably want to put it in GCS or in our portable storage format. And so we merge those two capabilities, the snapshot and back up into a single product. And in addition to that, one of the things that we do, again, I talked about predictability. We tell customers what that policy is going to cost them because if for example a customer said, well I like the idea of doing my backups in the cloud, but I want to store it on premises. We'll tell them, well if you're copying that data continually, you know what the network charges look like, What the CPU and compute charges look like, What do the storage costs looks like. So we give them the forecast of what the cost model looks like even before they do a single backup. >>That forecasting has got to be key, as you said with so much unpredicted things that we can't predict going on in this world the last year has taught us that with a massive shift, the acceleration of digital business and digital transformation, it's really critical that customers have an idea of what their costs are going to be so that they can make adjustments and be agile as they need the technology to be. Last question Bryant is for you, give us a view uh, and all the V mon attendees, what can we expect from the partnership in the next 12 >>months? You know, we're excited about the foundation of the partnership across hybrid and in cloud for both VMS and containers. I think this is the real beginning of a long standing relationship. Um, and it's really about a marriage of technology. You think about all the great data protection and orchestration, all the things that Danny mentioned married with the cloud foundation that we have at scale this tremendous network. You know, we just signed a deal with SpaceX in the last couple of days to hook their satellite network up to the google cloud network, you know, chosen again because we just have this foundational capability to push large amounts of data around the world. And that's you know, for Youtube. We signed a deal with Univision, same type of thing, just massive media uh, you know, being pushed around the world. And if you think about it that that same foundation is used for data protection. Data protection. There's a lot of data and moving large sets of data is hard. You know, we have just this incredible prowess and we're excited about the future of how our technology and beans. Technology is going to evolve over time >>theme and google a marriage of technology Guys, thank you so much for joining me, sharing what's new? The opportunities that demand google are joined me delivering to your joint customers. Lots of great step. We appreciate your time. >>Thanks lisa >>For Danielle in and Brian Schwartz. I'm Lisa Martin. You're watching the cubes coverage of Lehman 2021.

>>Hey, welcome to the Cubes coverage of Red Hat Summit 2021, the virtual experience, I'm lisa martin, I have two guests joining me. One is a cube alum kamal Shah is back, he's now the VP of cloud platforms at Brent had come on, it's great to have you back on the program. You're in a new role, we're going to talk about that. Thank you. And Kirsten newcomer is here as well. She's the Director of cloud and Death stickups strategy at Red Hat, Kirsten, Welcome and thank you for bringing the red hat vibe to the segment. >>Absolutely, very happy to be here. >>So looking forward to this conversation that we're going to be having in the next 20 minutes or so. We're gonna be talking about the last time come on, you were on, you were the ceo of stack rocks In January of 2021. The announcement that red hat plans to acquire stack rocks, it wouldn't be talking all about that. But I'd like to start with Kirsten, give us your perspective from red hats perspective, why is red hat a good fit for stack rocks? >>You know, there are so many reasons first of all as as you know, right? Red hat has been working with product Izing kubernetes since kubernetes one dato. Right, so so open shift three dato shipped with kubernetes one dot Oh, so we've been working with kubernetes for a long time, stack rocks embraces kind of is kubernetes native security embraces the declarative nature of kubernetes and brings that to security. Red hats, Custer's red hat enterprise customers, we have a great set across different verticals that are very security conscious and and during my five years at red hat, that's where I spend the majority of my time is talking with our customers about container and kubernetes security. And while there's a great deal of security built in to open shift as it goes to market out of the box, customers need the additional capabilities that stack rock springs. Historically, we've met those needs with our security partners. We have a great ecosystem of security partners. And with the stack rocks acquisition, we're now in a position to offer additional choice. Right. If a customer wants those capabilities from Red hat tightly integrated with open shift, we'll have those available and we continue to support and work with our broad ecosystem of security partners. >>Excellent customers always want choice. Come on. Give me your perspective. You were at the helm the ceo of stack rocks as you were last time you were on the cube. Talk to me about the redhead acquisition from your seat. >>Yeah. So as as Kirsten mentioned, we were partners of red hat. You're part of the red hat partner ecosystem. And uh, what we found is that was both a great strategic fit and a great cultural fit between our two companies. Right? And so the discussions that we had were how do we go and quickly enable our customers to accelerate their digital transformation initiatives to move workloads to the cloud, to containerized them, to manage them through kubernetes and make sure that we seamlessly addressed their security concerns. Right? Because it continues to be the number one concern for large enterprises and medium sized enterprises and frankly any enterprise that uh, you know, uh, working out today. So, so that was kind of the impetus behind it. And I must say that so far the the acquisition has been going on very smoothly. So we had two months in roughly and everybody and has been very welcoming, very collaborative, very supportive. And we are already working hand in hand to to integrate our companies and to make sure that we are working closely together to make our customers successful. >>Excellent. We're gonna talk about that integration in a second. But I can imagine challenging going through an acquisition during a global pandemic. Um but that is one of the things that I think lends itself to the cultural alignment. Kamal that you talked about, Kirsten. I want to get your perspective. We know we talk about corporate culture and corporate culture has changed a lot in the last year with everybody or so many of us being remote. Talk to me about kind of the core values that red hat and stack rocks share >>actually, you know, that's been one of the great joys doing during the acquisition process in particular, Kamal and and ali shared kind of their key values and how they um how they talked to talk with their team And some of the overlap was just so resonated so much for all of us. In particular the sense of transparency, uh, that the, that the team the stack rocks executive team brings and approaches. That's a that's a clear value for red hat um strongly maintained. Uh, that was one of the key things the interest in um uh, containers and kubernetes. Right. So the technology alignment was very clear. We probably wouldn't have proceeded without that. But again, um and I think the investment in people and the independence and the and the strong drive of the individuals and supporting the individuals as they contribute to the offering so that it really creates that sense of community um and collaboration that is key. Uh and and it's just really strong overlap in in cultural values and we so appreciated that >>community and collaboration couldn't be more important these days. And ultimately the winner is the customers. So let's dig in. Let's talk about what stack rocks brings to open shift Kirsten take it away >>man. So as I said earlier, um so I think we we really believe in continuous security at red hat and in defense and depth. And so when we look at an enterprise kubernetes distribution that involves security at the real core os layer security and kubernetes adding the things into the distribution, making sure they're there by default, that any distribution needs to be secured to be hardened, auditing, logging, identity, access management, just a wealth of things. And Red hat has historically focused on infrastructure and platform security, building those capabilities into what we bring to market stack rocks enhances what we already have and really adds workload protection, which is really when it comes down to it. Especially if you're looking at hybrid cloud, multi cloud, how you secure, not just the platform, but how you secure your workloads changes. And we're moving from a world where, you know, you're deploying anti virus or malware scanners on your VMS and your host operating system to a world where those work clothes may be very short lived. And if they aren't secured from the get go, you miss your opportunity to secure them right? You can't rely on, you know, you do need controls in the infrastructure but they need to be kubernetes native controls and you need to shift that security left. Right? You never patch a running container. You always have to rebuild and redeploy if you patch the running container the next time that container images deployed, you've missed, you've lost that patch. And so the whole ethos the whole shift left. The Deb sec ops capabilities that stack rock springs really adds such value. Right? You can't just do DEF SEc or set cops. You need to do a full infinity loop to really have def SEc ops and stack rocks. I'm gonna let Kamal tell you about it, but they have so many capabilities that that really drive that shift left and enable that closed loop. We're just so excited that they're part of our offerings. >>So can you take us through that? How does stack rocks facilitate the shift left? >>Yeah, absolutely. So stack rocks, which we we announced at summit is now being rebranded as red hat. Advanced cluster security was really purpose built to help our customers address the use cases across the entire application lifecycle. Right? So from bill to deploy to run time. So this is the infinite loop that Kirsten mentioned earlier and one of our foundations was to be kubernetes native to ensure that security is really built into the application is supposed to bolt it on. So specifically, we help our customers shift left by securing the supply chain and we're making sure that we identifying vulnerabilities early during the build process before they make it to a production environment. We helped them secure the infrastructure by preventing miS configurations again early in the process because as we all know, MIS configurations often lead to breaches at at runtime. Right? We help them address uh compliance requirements by ensuring that we can check for CS benchmarks are regulatory requirements around the C I P C I, hip hop and this and and that's uh you know, just focusing on shift left, doesn't really mean that you ignore the right side or ignore the controls you need uh when your applications are running in production. So we help them secure that at runtime by identifying preventing breaches the threat detection, prevention and incident response. >>That built in security is you both mentioned that built in versus bolt on Kirsten? Talk to me about that, that as really kind of a door opener. We talked a lot about security issues, especially in the last year. I don't know how many times we've talked about miS configurations leading to breaches that we've seen so many security challenges present in the last year. We talked to me a little bit Kirsten about >>what >>customers appetites are for going. All right now, I've got cloud native security, I'm going to be able to, I'm going to feel more comfortable with rolling out production deployments. >>It's, it's a great place to go. So there are a number of elements to think about. And if I could, I could, I could start with by building on the example that Kamal said, Right, So when we think about um I need to build security into my pipeline so that when I deliver my containerized workloads, they're secure. What if I miss a step or what if a new vulnerability is discovered after the fact? Right. So one of the things that stack rocks or redhead a CS offers is it has built in policy checks to see whether a container or running image has something like a package manager in it. Well, a package manager can be used to load software that is not delivered with the container. And so the idea of ensuring that you are including workload, built in workload, protect locks with policies that are written for you. So you can focus on building your applications. You don't necessarily have to learn everything there is to know about the new attack vectors that are really just it it's new packaging, it's new technology. It's not so much there are some new attack vectors, but mostly it's a new way of delivering and running your applications. That requires some changes to how you implement your security policies. And so ensuring that you have the tools and the technology that you're running on have those capabilities built in. So that when we have conversations with our security conscious customers, we can talk with them about the attack vectors they care about. We can illustrate how we are addressing those particular concerns. Right? One of them being malware in a container, we can look for stack. Rocks can look for a package manager that could be used to pull in, you know, code that could be exploited and you can stop a running container. Um, we can do deeper data collection with stack rocks. Again, one of the challenges when you're looking at moving your security capabilities from a traditional application environment is containers come and go all the time. In a kubernetes cluster nodes, your servers can come and go in a cloud native kubernetes cluster, right? If you're running on on cloud public cloud infrastructure, um, those things are the nodes are ephemeral to, they're designed to be shut down and brought back up. So you've got a lot more data that you need to collect and that you need to analyze and you need to correlate the information between these. Right? I no longer have one application stack running on one or more VMS, it's just things are things are moving fast so you want the right type of data collection and the right correlation to have good visibility into your environment. >>And if I can just build on that a little bit. The whole idea here is that these policies really serve as god rails right for the developers. So the it allows developers to move quickly to accelerate the speed of development without having to worry about hundreds of potential security issues because there are guardrails that will notify that with concrete recommendations early in the process. And the analogy I often use is that you know the reason we have breaks in our cars, it's not to slow us down but to allow us to go faster because we know we can slow down when we need to write. So similarly these policies are really it's really designed to accelerate the speed of development and accelerate digital transformation initiatives that our customers are embarking on >>and come on. I want to stick with you on the digital transformation front. We've talked so much about how accelerated that has been in the last year with everything going on in such a dynamic market. Talk to me Kamal about some of the feedback that you've gotten from stack rocks customers about the acquisition and how it is that maybe that facilitator of the many pivots that businesses have had to do in the last year to go from survival mode to thriving business. >>Yeah. Yes, absolutely. The feedback from all of our customers bar none has been very very positive. So it's been it's allowed us to invest more in the business and you know, we publicly stated that we are going to invest more in adding more capabilities. We are more than doubling the size of our teams as an example. And really working hand in hand with our uh the broader team at Red had to uh further accelerate the speed of development and digital transformation initiatives. So it's been extremely positive because we're adding more resources, We're investing more. We're accelerating the product roadmap uh based on uh compared to what we could do as a, as a start up as you can imagine. And and the feedback has been nothing but positive. So that's kind of where we are today. And what we're doing with the summit is rolling out a new bundle called open shift uh, Open shift platform plus, which includes not just Red hat A CS which used to be Stock rocks, but also red hat open shift hybrid cloud platform as well as Red hat advanced uh container cluster management, ACM capabilities as well as create the container registry. So we're making it easier for our customers to get all the capabilities that they need to for the drive digital transformation initiatives to get. It goes back to this whole customer centric city team that red hat has, that was also core value of stack rocks and and the winner and all of this, we believe ultimately is our, our our customers because that's where we exist to serve them, >>right. And I really like that if I could chime in kind of on top of that a little bit. Um so, so I think that one of the things we've seen with the pandemic is more of the red Hat customers are accelerating their move to public cloud and away from on premises data centers. Uh and and you know, that's just part partly because of so many people working remotely. Um it just has really pushed things. And so with Hybrid cloud becoming even more key to our joint customer base and by hybrid cloud, I mean that they have some environments that are on premises as they're making this transition. Some of those environments may stay that footprint may stay on premises, but it might be smaller, they may not have settled on a single public cloud. They could, in fact, they often are picking a public cloud based on where their development focuses. Google is very popular for ai and ml workloads. Amazon of course is just used, you know, by pretty much everybody. Um and then Azzurri is popular with um a subset of customers as well. And so we see our customers investing in all of these environments and stack rocks red hat A CS like open shift runs in all these environments. So with open shift platform plus you get a complete solution that helps with multi cluster management with a C. M with security across all of these environments, right? You can take one approach to how you secure your cluster, how you secure your workloads, how you manage configurations, You get one approach no matter where you're running your containers and kubernetes platform when you're doing this with open shift platform plus. So you also get portability. If today you want to be running an amazon maybe tomorrow you need to spin up a cluster in google, you can do that if you're working with the K s or G K E, you can or a Ks, you can do that with red hat a CS as well. So we really give you everything you need to be successful in this move and we give you back to that choice word, right? We give you the opportunity to choose and to migrate at the speed that works for you. >>So that's simplicity. That streamlining. I gotta ask you the last question here in our last couple of minutes. Come on, what's the integration process been like? as we said the acquisition just a couple of months in. But talk to me about that integration process. What that's been like? >>Yeah, absolutely. So as I mentioned earlier, the process has been very smooth so far, so two months in and it's largely driven by the common set of culture and core values that exists between our two companies. And so uh you know, from a product standpoint, we've been working hand in hand because I mentioned earlier, we were partners are working hand in hand on accelerating the road map the joint roadmap that we have here uh from a go to market perspective teams are well integrated. We are going to be rolling out the rolling out the bundle and we're gonna be rolling out additional uh options for our customers. We've also publicly announced that will be open sourcing uh red hat A. C. S. Uh formerly known as Stock Rock. So stay tuned for further news and that announcement. And, and so you know, uh, again two months and everybody's been super collaborative. Super helpful, super welcoming. And the team is the well settled and we're looking forward to now focusing on our primary objective is just to make sure that our customers are successful. >>Absolutely. That customer focus is absolutely critical. But also so is the employee experience. And it sounds like we both talked about the ethos and the and the core value alignment. They're probably being pretty critical to doing an integration during a very challenging time globally. I appreciate both of you joining me on the program today, sharing what's going on stack rocks now asks the opportunities for customers to have that built in cuBA and the security. Thanks so much for your time. >>Thank you. Thank >>you for Camel shaw and Kirsten newcomer. I'm lisa martin. You're watching the cubes coverage of Red Hat Summit, The virtual experience. Mhm

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

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019. Brought to you by VM Wear and its ecosystem partners. >> Welcome back to two cubes. Live coverage in San Francisco, California for VM World 2019. I'm John Ferrier, Postal Cuba David Lattin, My Coast, Dave. 10 years covering the BM World Paul Maritz laid out the stack early on. We saw that and watch it go through Its motions now >> remain from the marketing people got a hold of >> that mainframe turned into cloud Now hybrid cloud seven years after we first started about 2012 has been great Our next guest, Paul Falsone, S V. P and general manager of the Cloud Native APS. This is a business unit within VM where that is going to the next level. This is the Act three is Jerry Chen said any of you I talked earlier for VM wears a company. I won't say moving up the staff because there is no stack. It's cloud, right? So its applications on top of operating infrastructure Dev ops going enterprise scale is about developers building APS operating them in scale. This is a big focus of what you're doing. >> It is a dead end of the day. One of my close friend of mine, who's in front of customers all the time, reminds our team constantly that our customers applications matter of the most cause. That's what they used to get in front of their customers with the Dillman teams and the tools they're building the user. Japs come second cause that's what supports the abs. And then the infrastructure comes third zone away. There is that stacks it, but never forget you were at the bottom of the pecking order, if you will, when it comes to ultimately bringing full customer value to our company, our customers, businesses. >> And it's one of the things we've been looking back at our 10 years covering VM where I think you're 13 15 of'em world is that the virtual ization of all very quickly around really optimizing server virtualization really kind of change. The game of one kind of knows that our knows the history there, but it did it without any code changes, too, APs and I think that was a very innovative thing. Now we looking containers and what Kubernetes is bringing to the table. You're starting to get some clear visibility into what's happening and what's possible. Could >> you >> share your vision on what that visibility is that you guys are eyeing for the marketplace in four of'em, where, >> sure, the APP development methodologies are changing, changing more today than they have in the last 20 years. We're seeing ah lot of new concepts and approaches that right now really only accessible to a small percentage of application developers worldwide. We want to try to bring those application development methodologies, practices tools to the mainstream so we can. We can touch the 13 or $14 million.1,000,000 enterprise developers around the world and help the CEOs in their line of business counterparts at our customers get a CZ much productivity out of their development teams as possible. At the end of the day, those APS we're gonna power the next decade of those organizations success or failures with their customers, and so that's becoming a real competitive asset. I've had a number of customer discussions here this week where the primary theme is how me help my developers move faster at enterprise scale, but in a regulated environment in an environment where compliance is is front center >> to big things going on in your world that we covered extensively, honestly, pretty impactful to the Vienna, where portfolio one as open source and hefty oh, acquisition half a billion dollars almost a year ago, about a year left in less than a year, probably was that we close in December last year. So yes, ovary. Just recently we know those guys all people. I mean, I've been covering that for a while, and then I'll see the pivotal acquisition. Just announced a drink from the fire hose. There be doing tons of press briefings, those to impact points, kind of leaving a mark. >> So we've been we've been building up to this. I joined AA Drink them were in 2012 through the Sierra acquisition, but I moved into this role about just about three years ago, and one of the things that we identified early on was, ah, close partnership with Pivotal was going to be essential inside of the Del Technologies umbrella for us to exist in thrive together. And so that's where the idea for P Cass was born. So the combination of V. M. R. R and D with pivotal RND focused on delivering our first community service to our enterprise. Customers we brought helped you in last year. Once they saw what we were doing and thought about the possibility of what would happen if we actually took some of the concepts of communities and p ks and embed them into V sphere, That was, I think, the real ah ha moment for for us and the happier team coming together in the power of what that could enable. But all along the way, we always believed that that was just covering the infrastructure side of the equation. You still needed to get through the making the APP developers productive and efficient in this new infrastructure world and so on to be able to do so on any cloud. And that's where the pivotal piece finally came together last just last month. July Pivotal put out a lot of information in the market around how they're evolving their portfolio to be very cool, bernetti centric, moving forward. And that was a big part about getting all the pieces lined up so that the M word could deliver what we announced this week. The in the town's a portfolio with the component tree for building running in managing modern applications on any club, >> we've kind of come full circle here, predates, and I Sarah, But you guys talking about the stack? Yeah. Paul Moretz. I used to have the whole stack. Ed actually applications up here with Simba. Spring sources around. Exactly. And then you had these when I used to call the misfit toys. Have you had some assets in the M. C as coming in Vienna, where Paul Maritz, Joe Tucci decided, create pivotal as the The platform developed next generation applications. Now it's all come full circle there. So my question is related to that stack and particularly the death part of that stack. This audience is not Deb's not, but increasingly, you've gotta attract that audience. So what's what's your thoughts there? And so >> I think pivotals done a very nice job over the years through the Con Foundry Foundation. The work they've done there through the spring community Spring is at this stage is is arguably the most popular modern Java development environment on the planet. So, you know, we're seeing a tremendous amount of leverage of that of that framework and so between the events of pimples is actively involved in Leeds and their ability to help customers, um teach their enterprise developers how to get the most out of this modern tool kit. We think that there is some wonderful ingredients to a recipe to really scale this thing up in a big way. We way. I also believe that Veum we're still has a lot to learn about what it means to best support enterprise developers and their organizations. And so we are quite a bit in learning mode right now. We're gonna take a lot of lessons from the pivotal team as we as we move forward towards the close and learn a lot more about the team in the culture and their customer engagements. But one of the things I think is is front and center to what pivotal has for customers today is their transformation Service's customers. You've got different groups inside a customer summer looking to build the newest applications. Some of them are just trying to get more operational efficiency out of what they have today. Some of these customers have 12,000 applications in their environments. Um, pivotal has ah set of service is that come in and they help them take their existing monolithic applications and just modernize key components of them so they can operate them more efficiently and reclaim a lot of resources to go do other things. That, I think is probably the lowest hanging fruit for enterprise organizations today. And I'm very, very excited about the service is that pimple has to make available the customers on that front. >> Assad and Jerry Chen, earlier than the other set I was mentioning earlier is a VC now, Greylock, big time to your one. We see former VM Where, uh, guy from 22,003. He also worked on cloud foundries in sight. We ask about the white spaces where starts to thrive in one of the transit is kind of pointing to was have some cummings going public. Some are being bought at sizable numbers, but we rift on. The idea of monitoring was a boring category right now. Observe ability, which is just be monitoring 2.0, you got I pose. You got acquisitions. I mean, major action happening in this observe ability space. I bring this up because that's an area you think, Oh, it's a white space Data opportunities for companies to build service is really points to this cloud. 2.0 application Renaissance And I want to get your thoughts on that environment. What needs to be in place to make that happen? Honestly, pivotals keep for you guys. I get that on Vienna. Where side, but for the ecosystem and for the marketplace, people trying to make careers and or do things What is that cloud 2.0, complexity that need to be abstracted away or >> so The Pepto team had a great Craig and Joe had this great, uh, one liner on kubernetes is all about where the people structure meets the infrastructure. When you think about that, our enterprise organizations have thousands if not tens of thousands of developers all trying to do similar. But a lot of cases different things at the same time, across lots of different cloud infrastructures. On the infrastructure team side, you've got private cloud, you've got hybrid cloud. You've got public cloud environments that you have to get your arms around, monitor, manage, secure and get visibility into. We believe that Carini sits at that perfect layer between the two domains on. This is a big part of why we developed Tom's a mission control. It's just that that perfect layer between the two domains, too, access the company's later and give you full visibility into what all of your developers were doing on every piece of your infrastructure. And we also think that's gonna be a very interesting place for third parties to plug into to gain access to all of the community's clusters that we're helping. Our customers managed across their app landscape to do very interesting things. And so we're really excited about the ecosystem that that project will open up. >> You think this opportunity to start ups in there? >> I do. I do. I think there's a ton of other I mean, think about it just really basic math. Ah, VM based application. When it gets containerized, it has just on the compute side alone. Never mind the networking in the storage site. There are 10 times as many moving parts. A typical containerized EPA's 10 times as many moving parts as avian bay Step. If you think about that applied to the networking layer, you think about that applied to the storage layer, the security layer. You've got 10 times as many points to secure. Now, how do you get your head around that level of complexity As a an operations person, you can't do it. Humans can't do it anywhere. You can't write down your actions. Control this on a pad of paper and know what's what's accessing what anymore, >> Dave. One more question, if I may, on the on the VM container thing, there's a debate or are architectural kind of conversation, and customers are having around when to do containers in three days on bare metal or with V EMS. How do you guys talk to that house? The >> steam going because that was my question. So there was a snarky tweets yesterday. I want to get your reaction to it. And the tweet was during yesterday's keynote. I thought we we launched pivotal so that we didn't have to run containers on V EMS. Now the reality to your point is that people are running containers on bare metal. They're running him on vehement the EMS. I don't have any data, but I wonder if you could comment on that >> so way Probably have a couple of snarky comments of our own on this three share one of the things that put up on stage. Yes, I'll start at the kind of a little little. And I worked my way up at the base layer. The testing we're doing with Project Pacific, which is something we announced this week, which is effectively bringing kubernetes into the heart of the sphere. We're actually using combinations to make the sphere better. We're also going to expose communities to our customers through V sphere, just like we exposed the EMS today. This is a pretty exciting project for the for the company in our early testing of this project, based on the advanced scheduling capabilities of the SX hyper visor take advantage of modern hardware. We're seeing an 8% better performance in a certain test sweet versus what you'd see on bare metal so are ready at the early stages. We're seeing some benefits now take that a step further. The big public college for writers out there if you look at service is like G K on Google. If you look at a ks, uh, recast on Amazon, a cast on his door, every single one of their community service is is run against a virtualized environment, not on a bare metal environment. Why is that? Well, because their customers are using containers in VM, side by side, the flexibility you get out of that virtualization layer. Whether you're a big public cloud provider or your ah smaller enterprise shop running your own data centers, the benefits are proportionate, rather equal on dso >> the narratives off a little bit. What you're saying. What I hear you saying is people use virtualization for a lot of efficiency and scale reasons that's independent of what happens with bearnaise decisions. So if you decide you want to run Cubans on bare metal, go >> to go to town. We think >> if you want to do that, >> you want to do that. But we don't. We actually see a lot of customers who have started down that path. When they go to get to that operational stage, they're realizing they're now dealing with firm where again, they're dealing with Nick drivers again. They're dealing with stuff, and they can easily take that and turn it over to their ops team that's already managing a huge virtualized state and operated with the same tool. >> That's a really a layer thing around round scale. You do the virtual ization for Ryan reasons, and then cos sits on top of it for a whole another reason. >> And the I'd say its operations scale these operations teams need to, you know, just look at the number of announcements we made this week. For an ops team to get their head around all of these new technologies simultaneously is impossible to bring them in one new capability of time into the thing that they're already operating for. That organization is very >> positive. If I understood yesterday, you're claiming better before 8% better performance relative to bare metal. I know that's apples to apples. Or what kind of juicing you're doing on the benchmark >> sex schedule that it chooses it right there. >> I want to ask you about integration and look at it as a quasi. His story of the the industry. You go back to see A with all the acquisitions, right? Historical force it with fusion. Different layer of the stack. I know. Certainly Del did a lot of acquisitions. Some of them work. Some of them didn t m c. Same thing pretty successful. Actually. VM were great engineering. Um, very strong. Go to market on really good acquisitions. My question is on integration with the nice Sarah background, I wonder. I mean, nice. Sarah seems to be very well integrated into the VM. Where platform How is integration The state of integration today within V. M. Where is it a lot easier today because we're living in this AP I economy. What about VM? Wears sort of integration ethos. One of the challenges. I wonder if you could comment and that long. So >> I've been through, uh, to significant integrations of'em where the 1st 1 was with this nice era on. I was on the I was on the incoming side, not the receiving side. The next was with hep Theo. I was on the receiving side, not the incoming side. And so, as coming into this year, back in 2012 Pat was extremely supportive and asked his entire team to be very supportive of getting us integrated quickly and productive. A CZ fastest possible. We were on campus on the via more campus from the next era office within days of the deal closing. That's how efficient Veum work. That's like that's the mindset hammerhead coming into. We were in a building. We were co located with the other networking engineers and product managers. Within the first week on, we were off to the races. That was about 100 20 person company. Hep Ko is about 100% company, Um, about the same efficiency we were consolidating. Offices were bringing them over again, mostly distributed team, but they had a center of gravity. In Seattle. We had a center of gravity in Bellevue. We brought the team's over within within a couple of months in about three months. In three and 1/2 months in, we had the team fully integrated. The organizational design done all the tools in a greater we're all in the same systems. So what happens very quickly now, an organization that's much bigger like like pivotal 3000 employees. Public company takes a little bit longer to get from Deal announced the deal close because it's too public entities. It'll take a little bit longer to do all the integration, but we're already thinking thinking about we know them so well and they know us so well. We already know where the potential landmines are, where the potential rough spots are. Pat prides himself and, uh, this pushes down into the rest of them were on well, welcoming new team members in new groups into the company. And so we try to do that really were very culturally sensitive way optimized for the right tool kit s O that we take, we take some learning like cloud health. When they came in, they had a lot of expertise around. SAS drooling and support of customers were adopting all of that, right. Were jettisoned some of our older tools in favor of some of the things that >> we're gonna win the modernization. So I want to get your thoughts on the last question for the second congratulations, your your your area. We love what you're doing. We think it's super important. Would be covering it like a blanket this year and going forward. But Pakistan came on was wrapped. Talking about 10 years and doing the riffing on the Cube are 10 years covering it. We have some 10 years forward, which waves to be on. They highlighted on the past 10 years in this ear acquisition as a critical moment to bring VM. We're into the S T D C kind of concept started networking up, so we know the history they're sti n and then going forward, he says. If you're not a networking and security in the next wave and Kubernetes is Number one, you're really gonna be missing out. So we highlighted networking, security and kubernetes. But networking. It's nice here on both sides of that 10 year spectrum. You're part of that. >> Why is that? Why is that wise >> watching people know that networking is the most important piece of the wave here? What's the relevance of what he's saying? Share their thoughts on >> Think about the increasing complexity of what at modernization drives into the infrastructure. You're getting smaller and smaller moving parts that that need to operate together at scale in a comprehensive, logical way. But at any point in time, if you're if you're an enterprise organization, if you've got if you've got compliance requirements, audit ability, requirements. If you want to protect, you hear about the number of of small towns that get blackmailed on a daily basis because someone's secured an encrypted There, there, there count taxpayer data and they're there, their victims. All right, this is this >> is some say, cyber warfare. >> It is something. So if you think about in orderto help, our customers get the most out of their developers, these tools that open up I think the potential of a lot more avenues of attack get a lot more complex. And so we think that these two have to progress hand in hand. One. We do want to help developers go as fast as possible. We won't help enterprises get the most out of those developers. That's a big part of why we brought them were into into the damn warfare. We're bringing a pivotal into the VM. We're family, but at the same time, we recognize that the infrastructure has to progress. Every bit is fast, and the network is the thing that ties all these parts together. Whether it's a layer three year layer for networking today or level layer several networking layer seven AP I based networking in the future >> all. I mean, I'm not gonna bring up I ot or industrial i ot to takeovers of physical devices, whether it's a self driving bus off a cliff or taking over towns and cities warfare, I mean the service areas of enormous networks, Internet connectivity applications over the cloud native. Anyway, we know that, right? So a lot to talk about. Thanks for coming on. The Cube Sharing your insight. Senior Vice President, General manager, The Cloud Native APS Group. This is really the key instrument with envy em where to take kubernetes and the advancement of cloud to 0.0 to the next level. I'm John for a day. Volante, be back after this short break.

>> from our studios in the heart of Silicon Valley, Palo Alto, California It is a cute conversation >> universe. And welcome to another cube conversation from our wonderful Palo Alta Studios in beautiful Palo Alto, California. As we do with every cute conversation, we're gonna talk about an important topic with smart people that can provide some good clues and guidance as to how the industry's gonna be forward. We're gonna do that today, too. Specifically, what we're gonna talk about is that there has been an enormous amount of interest in kubernetes is a technology for making possible the whole micro service's approached application development. But one of the challenges that kubernetes has been specifically built to be stateless, which means that it's not necessarily aware of its underlying data. Now that is okay for certain classes of application. But the typical enterprise does want to ensure that its data can remain state full. That does have a level of protection required, et cetera, which creates a new need within the industry for how do we marry state full capabilities, staple storage capabilities with kubernetes and have that conversation? We've got great guests here. Part of Ayatollah is a co founder and C t o of robin dot io and radish men on is the CMO Robin. I owe partner Radish. Welcome to the Cube. >> Great to be here. >> All right, so, reddish one, we start with you. Why don't you give us a quick update on Robin Donna? >> Sure. Robin. Daughter, You, as you were alluding to, is addressing super important problem that is in front of us, which is that you've got cloud. Native technologies, especially containers. And community is becoming the default way in which enterprises are choosing to innovate. But at the same time, there's a >> whole swath >> of applications which were architected just five years ago, which all need to get the same benefits off agility, portability and efficiency of cloud native technologies. Robin helps bridge that, and I hope to talk more about that. >> Excellent. So part of let's start with you and talk about this problem this impedance mismatch between applications that require some state full assurance about the data and kubernetes, which tends to be stateless. How does that How does that impact the way applications get built and deployed? >> Sure. So if you look at me as you mentioned that communities is a platform that has started our originated for stateless workloads, and people have adopted the fastest growing open source project. We know about that, but when you look at a stateless work lord, it actually depends on state from somewhere. It's basically computing something right. It's computing state that's coming either, for the network ordered. Is computing on state that store brother inside, big data data, data leak or inside a database? Now, if you look at the problem itself, developers have gotten used to the agility benefits that communities has to offer the mostly infrastructure as a court kind of construct centered offers, however, the agility is not complete if you do not bring the state full workload workloads also into the communities for so as an example, think about somebody who's trying to build on entire pipeline right across the in. Just process so visualized by plane. If you're saying that you know what, in order to put this entire stock together, our entire pipeline together are to still do something that is non agile by going out sorry communities and then marry that with something inside communities. That's not true, actually. So more and more we're seeing developers and the develops teams basically saying that. Okay, I want to have the entire stock developed on deployed on a child platform, like open these. And of course, that comes with a bunch of challenges that need to be addressed and hoping you talk about that today. >> Well, if we have a zoo said the state has to be maintained somewhere, state may be maintained somewhere up in the cloud, But there are gonna be circumstances where because of data locality issues on, you know you want local control. You have ah, Leighton. See, considerations a number of other issues that you want to be ableto locate state in the closer close to the kubernetes. Is that really what we're talking about here? >> That's one aspect of it which is essentially around the performance and maybe you in governance reasons why you want to call a Kate State and stateless, Right? But the other reason I was saying is, if you want to deploy a stack, stack is comprised of many too many competent, stateless as well estate full. And you're talking about the birth of an entire application that the developer is gonna push under this platform right, so there. It's not about just the data locality and all that. It's also that just enabling the entire stock to be deployed in one shot. >> So you just you just you want a simpler, more manageable stats at all, right? So what's the solution? What people, what people have to do to get access to both those performance more more performance state Full application. Cubans clusters that record, have some degree of day locality concerns or to sustain that dream of increasingly simple stacks. What has to happen differently? >> Sure, and there are two aspects to this. The 1st 1 I would say, is that a the platform that is going to offer this on top of communities has to guarantee the persistency needs, whether it is in terms of reliability, dumps of performances. Selous, it has to guarantee does so you have to get those onto the platform first. But beyond that, if you look at other issues talking about many, there are many, many data platforms or data applications of workloads that predict board docker and communities. Now, if you don't really bring them into the Ford, you really are not solving the real business challenges that people have today, right? So beyond just providing persistency layer to communities pods, you need to have a way in which you can take complex platforms such as Mongol, Cassandra Elastic, such article rack. Cloudera these kind of workload and bring them onto a platform that has architected for Microsoft. Just communities, right? Because these platforms are not. These workers are not designed for micro service's workloads. So how do you marry them onto a platform such as communities that is designed as a micro service's platform? So you go to solve that, and that is exactly what Robin has done. So we have taken this approach where you can take complex workloads, rear platforms and then make them run on on a Microsoft this platform like abilities, starting with the storage subsystem, which is where one of our course fences. >> So I could conceivably imagine an Oracle database being rendered as a container with inside a cougar and he's cluster and position as a service have been orchestrated by by that kubernetes instance. What >> if I could jump in? You don't have to imagine we have customers in production there. They have Oracle Rack as a service offered on robin right now. One thing I want to contextualize is that our roots are in problem solving this hard problem off applications that I haven't been designed for containers contain arising them and being able to manage that gracefully in carbonated right. It just gave the example off Oracle Rack as a service. Or we also have customers with, let's say, multiple petabytes of data with her new bastard service, um, covering big large enterprises as well. Now from that lineage. Now, what've you also offering is that there is a set of customers who, already picked, Committed is already right might be open shift. It might be P K, as it might be g k to do its customers. We also have an offering called Robbins Storage, which brings powerful data management capabilities right. So to offering the platform offering, which is communities plus storage plus networking. Bless application bundles for some of the demanding workloads. But we just talked about, and then Robin Storage is a new offering which can add the magic of data management and advanced data management capabilities to any community. Is that you? >> Well, let's talk about that just for one second the uh, when I think of data management capabilities, I'm thinking not just a Iot being written back and forth between some media and some application. I'm thinking in terms of, oh, data protection and security. So are there Give us a sense of the scope of the service? Is that our part off this solution that you're talking? >> Yeah, I'll start in part like and chime in as well. So the first context you need to have is that all these data management capabilities are in the context of a hybrid being the normed implementation, right? Nine or 10 customers are looking at implementing on Prem with Public Cloud, right? So in that context, any of the cable release that we're talking about being being able to take snapshots or being able to take, you know, move that snap short to be offer as a back up in the cloud or ability, the clone and rehydrate applications, these air own capabilities that need to operate in a hybrid cloud context, that's number one. The second thing is, rather than just solve the storage level problem off taking snapshots, being able to bring application and data together is a big game changer in partner. Can you add a little bit more on the apple is data? >> Absolutely. Because, I mean, if you look at the the dinner service is the radish doctor board snapshots and clones and things living backups. Those constructs have existed in the storage industries for almost three decades. So there's nothing new about dark, right? But if you look at applying them for work Lord that are running in communities, you gotta uplevel that, because when you look at a story little snapshot, it is still a volume orelon level snapshot. But what a developer develops team needs is the ability to take an entire workload. That's a Mongo TB cluster and the only snap, short and dark cluster. I want to keep different states, even if the topology of the application is changing. Correct. And that is something that Robin has innovated on because we recognized. And I come from a storage bag when I was a distinguishing. Jenna very does have Bean fortunate to be building many data platforms there on be recognized that just leaving that storage does not deliver the promise of agility that communities offers. They were uplevel it into applications and for the very first time. In fact, we're introducing concepts such as you go to a Mongo classroom. You say I want to go snapshot this cluster. We understand the apology that this cluster has. How many shards depositor for offering these things. The service is under Langston the volumes and we dark forms a snapshot. That's an application. Little snapshot of the benefit of application will snap Shirt is that if another developer wants to go clone and run queries on that, you don't have to go Dr Storage Admin inside. Just give me clones of these large volumes. They'll say, Just clone this Mongol Devi cluster on. Then within minutes, you have an up and running long body be cluster fully functional. You can start readies life. Exactly. Other thing would be draw the stock double portability. So you have this snapshot taken periodic snapshots. So let's say that you run out of capacity nor deer center, and you would like to go bust into a different cloud. That's your on premises, and you want to go and run a clone in geeky because that's where the capacities, our snapshots and the baby, a implemented and architect of this allow you to port an entire application along with topology? Medea on data so that he can go and stand up Fully functional, ready to use. That's among Would he be cluster and geeky in the club? >> Now you talk about UK a Google kubernetes engine on G C P Google Cloud Platform. Obviously, that's when you think about kubernetes. That's kind of the mother ship. When you come right down to it. How does your platform and G K E G. C P work together? >> So the first thing is >> that we have, ah, partnership, which is led by engineering to engineering engagement, that >> part eyes front, ending around a standard set of AP eyes whereby the advanced data management capabilities that we're talking about can be brought into communities world itself and, of course, geeky as the implementation footprint. Right? So that's one area that we've been collaborating on. The second is from, ah, Google perspective. The preferred storage for running enterprise workloads or state full workloads or the data intensive work clothes that be talking about is Robin Storage and that's ah that we definitely are pretty excited by the fact that through rigorous technical evaluation, after rigorous technical evaluation, Google is chosen Robyn stories as the preferred storage for these demanding workloads. So from both these standpoints off moving the state of the art of what does it mean to provide data management capabilities to communities, to providing a solution that works today for customers who are embracing G K both on Prem in in the cloud to be able to bring state full workloads? We're working with Google and pretty excited about that part. Anyone add further color on the engineering partnership? >> He absolutely, I think, as a radish mentioned. So Google perform. We are the purport storage solution for that. Now can we just rewind back a little bit there? About 25 30 different stories? When does providing stories for communities? Right. So what is this? I think that this move is something special that let us tow this thing at this point, right. We took a very fundamentally different approach when we when we saw this problem for G k r for communities you could have started with several open source story solutions, are there and build on top of that. When their companies that take barter effects, for example, pity orifice and build on that. The companies that takes seven belong there, right? Be formally said that. Listen, if you want to elevate the experience from storage onto applications, that the example that I took earlier off taking a snatcher, a mongo migrating and if your story, it's stackers underwear off the application, which means that the stories track is unaware of the topology of the application. Can you really do application consistent snapshots? You can't. All he can do is begin to snapshot individual Williams. Correct. Now, if the stories stock is not a rare off the application to polish, can you actually the application level quality? Also, this. If you can't do that, can you really guarantee noisy neighbor elimination? You had to >> do all >> those things right? If you really wanna run data platforms, those are the core things that you need to do right and Soviet took an approach is that it doesn't know it will not cut it if you build a story. Stack on top of border defense, for example, are on set, so we do a ground up approach and he said, Look, if you wanna build a story, started this cloud native communities native. How would that look like? And how would the perimeters exposed so that it can deliver the entire experienced applications? So architectural leave yard very superior compared to the other players out there, it's proof is that we've got picked. Now that's one aspect. The other aspect is the approach that were taken to expose these primitives, their own snapshots and backup on a portability and all that was very clean. Right on. Very pragmatic how it works with both the born in the cloud as well as the the prior boatloads right on. Because of that, we're also collaborating with the Google engineers is to come up with a set off a P eyes that were planning to standardize right around community so that you could have a very standard set off a p I through which you can trigger these data management calls. Right? So that's that's other like no other stock Borden engineering to engineering collaboration. So that's the other thing that we're collaborating on to create the stana riser of FBI's based on the knowledge that we have had, because we have have we have feel deployments off like rubbish. Talked about right article rack. We have field the Prime Minster. People are deploying multiple petabytes off starting in the single communities. Robin, cluster. Right? So all that learning all the experience that we have had its contributed towards this joint Engineering to engineering. Afford that you're going to create the standardized data management. >> So we've got Robin. I owe has delivered a piece of technology for handling state full kubernetes clusters that has been validated by Google I o. Today or you know, so that can be used now. And is the basis for further engineering work to move this Maur into the mainstream for the future? That's good. Very exciting stuff, Partha. Right, Dash. Thanks very much for being here in the Cube. Thank you. Thank you. And once again, I want to thank part uh Chautala, Who is the co founder and CEO of Robin I owe and radish men on Who's the CMO Robin don I owe once again. I'm Peter Bursts. Thanks very much for watching this cube conversation until next time