>>The cube presents HPE discover 2022 brought to you by HPE. >>Hi everybody. Welcome back to the Cube's coverage of HPE. Discover 2022 from the Venetian convention center, formerly the sand convention center in Las Vegas, Dave ante, with John furrier. We're here with Brad parks. Who's the chief product officer at morphia data and Brian Thompson. Who's the vice president of GreenLake cloud product management at Hewlett Packard enterprise gentlemen. Great to see you first time on the queue first time. Wow. I just assumed we've known each other for, so >>We've been around a long time now. I'm happy to be here and thanks for, thanks for making the >>Time. Yeah, you've put a lot of people on the queue, but Morpheus data, when we, you know, we first met, I mean, with your new role here several years ago, tell, give us the update what's Morpheus do, why are you, so why does people, why do people need Morpheus? Think >>People need Morpheus, cuz it is messy, right? Technology promise, you know, simple, better, faster, but it's only gotten more complex, more heterogeneous over the last decade. We are a unified orchestration and automation platform that makes kind of the, the messy labyrinth that is enterprise. It kind of simpler to navigate primary use case. Self-service for developers who wanna push a button, get a database and an abstract deployed into their on-prem or their public cloud without having to wait on it. >>So you've, you've, you've been through the hyper-converged world. You've seen all that hardware come together. The VMware Nutanix of the world's kind of hardware. Now you got this software abstraction where you got operations, you've got AI, you got all kinds of ops AI ops dev ops data ops ops machine, >>You >>Know, they're all there. And so you got developer environments, you got operating environments. It's just getting more complicated at scale. Yep. This is a huge challenge. You guys are tackling this and then by the way, throw in automation in there too. Right? So, so all that's kind of coming together. How does self-service work put all that complication? >>Well, so I was just talking about Robert Christiansen. I know he's probably think he's been on the Q he's on S team and the ven diagram that we see in hundreds of enterprises we talk to is there's a need for central platform engineering at an enterprise to enable developers, to hit a button, get their database, run an I API line, you know, get their app stack deployed. They also wanna do the same thing with Kubernetes, right? Micro clusters deployed, you know, at a service, same thing with Terraform and Ansible. And they're just there aren't enough skilled operators who have moved up that stack. So you have to automate and canonize that knowledge and, and make it easy. >>Brian, one of the sort of pillars of GreenLake is, and as a service is data and we see a change in the way data is data platforms are being architected, data organizations. And one of the things that is a critical principle of sort of what we see as the new data era is self-service infrastructure where the operation of the technical details are an operational detail, not the be all end, all, you have to go beg and get data out. Okay. So you guys are building out, I think, consistent with that principle self-service infrastructure. That's right. So where does Morpheus fit in, in terms of that objective, what's your relationship like and, and help us understand >>That. Yeah. Within GreenLake, specifically think of this as a broad portfolio of different as a service offerings. Part of that key is meeting customers where they are and where they want to be. So we have that array of things which are fully self-service if you will, but serving an it admin type of persona. So it's where as a enterprise, I still have those resources. I want that granular of control all the way through, how do we deliver some of our more advanced cloud services, really trying to serve the end user to your point, how do I empower application owners, developers to, to bring in and, and work with those services? This is key in, in some of those cloud services, we're delivering more of VSC is a key component that we work as we bring to again, provide those interfaces. How do I provide everything from API CLI through a gooey experience that can span across multiple form factors, bring together that more of a homogenous experience? >>What, what options are out there to solve this problem today? I mean, what are the best practices? Is it do it yourself? Is it, you know, a little bit of VMware here, a little bit of, you know, other tooling there, what, what do you see out there in the marketplace? >>I'll give kinda my perspective kind of yeah. Outside the, the tools that we see when we walk into an enterprise, you've got a company that's got a lot of VMware, maybe a little Nutanix, we've got some AWS, they wanna use OpenShift for their clusters. They got Terraform Ansible, and they got service now. And there's a, there's a poor it ops team in the middle, trying to wire all that together. And each of those domains have tried to go up this hill, right. VMware's done with vRealize automation, you know? Yeah. OpenShift will say no where the way, and you use cube vert to >>Do your virtual service now will say the same thing. Right? >>So our goal is, you know, we started in the middle right. Middle out, right. We started unifying that for self-service for developers and finance teams. And we're we're agnostic. We don't have a dog in the fight, right. We don't have a hypervisor business, a hardware business, an ITSM business. We're all about bringing the pieces together. But that said, we work with partners like HP, you have a footprint of thousands of customers who are solving that same problem and need to need to move up stack. So it's been a good win-win. So >>You're not trying to be the cloud operating system per se. I mean, right. The way, the way a VMware wants to be, or you could even argue, well, I guess open, you >>Got, you got the hyperscalers coming down, you got VMware moving up. But again, they all at the end of the day are trying to control their cash cow, right. Their hardcore business. We wanna make them all transparent. So >>Your bet is it's gonna be all of the above. Yeah. That's not gonna change. Right. That's the complexity is, is that right? Or do you think they're gonna consolidate? >>No, I think there's definitely something to that. I also think there's enough. Disparate. Technology's not gonna be one size fits all or one to rule them all. In fact, I think that's part of the examples in the past, like private cloud is we announced yesterday private cloud for enterprise. It's not a new term. People are doing that for quite a while now, but they are typically fairly brittle hand rolled disparate technologies, some poor it team trying to hold it together. So where we can provide that kind of life cycle management in a cloud operating model, remove that complexity and provide that stability. And in that experience across what will be interchangeable parts at times, I think that's really that direction in, >>Yeah. You guys talk about this whole starting in the middle. I like that because there's a skills gap as well. Right. Not only is there for a challenge on it that transforms, there's not enough. People actually know how to manage a Kubernetes cluster spin one up. Yeah. So there's been a rise of managed services. We're seeing come outta the woodwork almost in all areas where it's complex. Yeah. How does that fit into the makeup of as customers, engineer or rearchitect or, or just evolve to edge on premises and public cloud? Yeah. In a cloud operating way, because if I got managed service, do they just plug in, I mean, new orchestrating services, managed services all the above, take us through this dynamic because we're seeing more and more customers saying, just gimme the service. Yeah. >>I, I know manage perspective. This, this kinda goes back to that portfolio of meeting customers where they are. There are some that, that have that expertise in house they're opinionated. They just want a different consumption model. But on the other side of that, it's difficult to attract and retain that type of talent. And if I have limited resources, am I gonna focus on the care and feeding of that underlying infrastructure? Or am I gonna try to up level and focus on things more strategic to the business? So that's where we've certainly been focusing. And I think this type of management capability is what feeds into that. Right? >>Talk about the trust aspect, because if I'm gonna go manage service, it better work. I need to trust it. It's not a zero trust environment. It's actually a trust and verified, but you're seeing the software supply chain is a big discussion point. Developers don't wanna have to get back off their CDC pipeline to go in and manage stuff. So a managed service has to be verified. Yeah. There's a huge trust factor in there. How does what's the status of this now? Is it real? >>I think one of the, one of the pieces we see in terms of trust organizationally, I mean, people in process is always harder than the tech usually. And, and a lot of the trust is just internal. You get, you know, developers don't trust the ops team, right? Security doesn't trust anybody, you know, finance doesn't trust, you know, who's billing them. Part of what we do as a stack is we give each of those stakeholder groups, the ability to get their core needs met without getting each other's way. And from a delivery perspective where we partner with HPE is we are, you know, we're a platform framework, we're a technology provider we're inside, you know, products like the private cloud. We work their GMs team, the manage services team. If they wanna take on more of that operational concern, right. They use us or if the customer wants to manage it themselves. So we we're all about enabling them at the end of the day. And, and HP brings >>And how hard bread is it to unify? UN unification is a great word. I love let's unify everybody. Right. So how, how hard is that? Can you scope that problem statement for us? What does that mean? >>I'll separate it from a technology perspective and then the people process. So a lot of the traditional people that have played in that space that do it yourself, you mention right. Scripting it all together is hard, right? And if you change from cloud a to cloud B, you're set back six months, like why we exist is we wanna very quickly pull the pieces together. We can usually get a POC up and running in about two hours, right? That's a, self-service VMware private cloud, right? That doesn't mean you've solved the organizational inertia. You know, that's, that takes time, weeks, months. And that's where people are like Accenture GreenLake, other SI other channel partners bring that together to, to help make that change happen. >>How mature is the platform? Where are you in terms of determining product market fit? Are you, are you scaling at this point? >>Well, the, the great part about our origin story, right? We got our start as an internal tool set inside a two and a half billion dollar private equity firm that was transforming it at dozens of companies. So we were built for the use case product market fit happened, cuz a bunch of guys needed to get their jobs done. So we've been an outbound since 2015, right? We were top of the stack ranking, you know, all the MQs, all the quadrants, all the analysis. So we think we're their product market fit. The nice thing is customers have actually moved to where we are. Right? Five years ago, cloud management meant cleaning up the lift and shift mess. Now it's automation platform engineering. So it it's a fun time. >>It's it's operational. Yeah. It's they're operationalizing it. >>What's your go to market model. Maybe you could double click on those through >>Partners. So honestly through HP is a big one. We're small, right? We want to be the best unified platform we can be. Our go to market is via technology partners like HPE, right? The other systems integrators, other channel partners globally. So, so yeah. It's >>So then you've got kind of a tiger team overly. Yep. Salesforce is that, that >>Yeah, we've got teams globally. So we've got about 700,000 workloads under management around the world. About 70% of those are OnPrem VMware Nutanix. The rest are up in the public cloud. So we work with partners, solution providers, services, engines to, to help deliver that to >>Customers. What do you make of the 61 billion acquisition of VMware from Broadcom? >>We're, you know, I think your analysis was spot on. It is gonna be a, a war of, you know, what is the, the most profitable to that new Broadcom business and things like vRealize automation, some of these fringe products that are core at a customer use cases, but may not be driving a lot of bottom revenue for VMware, I think are gonna be gonna be on the bubble. And we've seen more interest in the last few weeks from people who just want to hedge their bets. Right. They want to be able to switch from hypervisor a to hypervisor B or cloud a to cloud B without being locked into anyone's stack. And that is, that is why we exist. Mm. >>You wanna comment on that? >>I mean, it's, you know, for HP and from a GreenLake and even just historically, right. It's about customer choice. Mm. We have a strong relationship with VMware. Sure. We have, I don't know how many bajillions of servers out there running VMware that we, we support with. So, you know, it's, it's, it's all just looking at that ecosystem and helping deliver those customer solutions and outcomes is our focus. Yeah. >>Thank >>You. Brian. Talk about the GreenLake success with partners. We're seeing ecosystem is a big part of that and we know the formula for ecosystems create value. What is the pitch that green lakes making to the marketplace right now to attract more folks to build and or integrate into the >>Platform? Yeah. I mean, GreenLake started with a, a vehicle of how do I start to deliver an OPEX model, a consumption model for traditional infrastructure that we've been providing more and more as the services and solutions really have emerged and evolved. It's gone from, how do I just give you kit and a consumption model for it to now looking at embedded solutions with third party ISV software building or wrapping those services around it, really delivering outcomes and solutions you're seeing. And hopefully you'll solve just from announcement more and more of that, where we have kind of turnkey solutions with key partners, how do we bring a marketplace ecosystem together? How do we help enable those kind of full solutions? Because we're not gonna build it all ourselves, right. We wanna make sure that we can deliver those outcomes. >>So marketing is often and should be ahead of the actual product, early days of GreenLake. It was really a, you know, financial model. Sure. Right. Where do, where do you see GreenLake today? How far is it matured? We saw some of the, the announcements yesterday. We saw some demos. Where are we at? >>Yeah. So this actually, I think really the exciting part is you might have heard Antonio refer to as that journey to one each of our different businesses within green or within HPE, they've all been building these cloud services in GreenLake enabled services. But as you saw Alma share the path to the HPE GreenLake cloud platform that really is bringing these services together into a functional platform, right? Common identity, common telemetry services, bringing these together as now, integrable interoperable services. Like you're starting to see that come together and you can really see the Chrome trail of, of where we're going with a very powerful hybrid cloud experience, right? Spanning private public on-prem colo and a, and a full solution set within there. So it that's, that's the exciting part >>For me and Brad Morpheus will be a capability inside of GreenLake that a customer can consume. Do you have to write to GreenLake APIs to enable that? Or is it, is it more just certify that you work inside a GreenLake? What has to get done? I'll say a lot >>Of what they've done is actually written into, into our APIs. Like we've normalized hybrid it. We have a, a database model of every load balance or a cloud endpoint automation tool. So we are, we're all about making it easier to consume it. And the vision that Alma and HP has around GreenLake fits very well with why we exist. So they're able to extract metering data from our, you know, from our API, we know who provisioned what, where how much they spent. So we're a good repository and platform partner for them to, to build on. It's >>Great for that console that you guys have. Yeah. >>You got the, you got the open APIs, you publish those, you guys take advantage of 'em and then sure. Boom. Then you can consume. Got it. All right, guys. Hey, great to see you again, red. Thanks for, for >>Coming on. Thanks. Thanks for having us on >>Our pleasure. Great stuff. Congratulations. Okay. Keep it right there. This is Dave Valante for John furrier. Are you watching the cubes coverage of HPE discover 2022 from Las Vegas? We'll be right back.