(intro tune) >> Welcome back to HPE Discover 2021, the virtual version. My name is Dave Vellante and you're watching theCUBE's continuous coverage of the event. John Gromala is here. He's the Senior Director of Product Management for HPE GreenLake Lighthouse, new offering from HPE. We're going to talk about that. We're going to talk about Cloud Native. Hey, John, welcome to theCUBE. Good to see you again. >> Awesome. Great to be with you again. >> All right. What is GreenLake Lighthouse? >> Yes, very excited. Another new offering and innovation from HPE to support our broader GreenLake strategy and plans. It's really a brand new purpose built Cloud Native platform that we've developed and created that pulls together all of our infrastructure leadership with our platform software leadership into a single integrated system, built to run GreenLake Cloud Services. So think of it as, you know, fully integrated, deploy at any place you want on your premises, at a co-location provider or at the edge, wherever you need, they'll all inter-operate and work together, sharing data, you know, running apps together, great capability for people to bring the Cloud where they want. As we talk about with GreenLake, it's the Cloud that comes to you. >> So, should we think of this as a management platform? Is it also sort of a quasi development platform? Kind of where does it fit in that spectrum? >> Well, it's really more of a integrated system with all of the integrated control planes needed to run it, you know, in a distributed fashion. So it's a true distributed Cloud intended to run at any client location it's needed, connects back to GreenLake central and our GreenLake Cloud operations teams to go ahead and run any Cloud services that they want. So you get the benefit of running those workloads wherever you need, but that, you know, centralized control that people want in terms of how they run their Clouds. >> OK so, we think of these, these things like, for instance, how is it different from AWS outposts or things like, you know, as your stack or as your hub? >> Yeah. Very simply, you know, this is because it's a distributed Cloud intended to make it so you could run it wherever you need. You don't need to be tethered to any of the public Clouds or the various public Clouds out there. So people can now run their systems wherever they want, however they need without that required tethering that much of those other vendors require. So you can really sort of own your own Cloud or have that Cloud come to wherever you need it within your overall IT. >> Can I tether to a public Cloud if I want to? >> Yeah. The Cloud services, like many other Cloud services can interconnect together. So no issue if you want to run or even do fail over between public Cloud or on premises, it's all how you want to set it up. But that connection to public Cloud again, through GreenLake is done at that Cloud services level. You know, where you would connect one of these Greenlake Lighthouse systems to the public Cloud through services. >> OK so, maybe you could talk a little bit about the use cases in a minute, but how flexible is this? How do I configure Lighthouse? You know, what comes standard? What are my options? >> Yeah, so we've designed it in a very modular fashion so that people can really configure it to whatever their needs are at any given location. So there's a basic set of modules that aligned to a lot of the compute and storage instances that people are familiar with from all of the Cloud providers. You simply tell us which workloads you want to be running on it, and how much capacity you want. And that'll get configured in deploy to that given sight. In terms of the different types, we have what we're calling two series, or a set of series that are available for this to meet different sets of needs. One being more mainstream for, you know, broad use cases that people need, you know, virtualized container, any other type of enterprise workloads, and another more technically focused with higher performance networking for higher performance deployments. You can choose which of those fits your needs for those given areas. >> So maybe you could talk a little bit more about the workloads and what specifically is supported and how they get deployed. >> Yeah. Again, all of it is managed and run through GreenLake Central. That's our one location where people can go to watch these things, manage them. You can run, you know, container as a service, VM as a service, as needed on these different platforms. You can actually mix and match those as well. So one of these platforms can run multiple of those and you can vary the mix of those as your business needs change over time. So think of it as a very flexible way to manage this, which is really what Cloud Native is all about. Having that flexibility to run those workloads wherever and however you need. In addition, we can build a more advanced type of solutions on top of those sort of foundational capabilities with things like HPC as a service and Ops as a service to better enable clients to deploy any other given enterprise workloads. >> John, what about the security model for Lighthouse? That's obviously a big deal. Everybody's talking about these days. You can't open the news without seeing some kind of hack. How does lighthouse operate in a secure environment? >> Well, you know, first of all, that there's sort of a new standard that was established, you know, within these Cloud operating models. And HPE was leading in terms of infrastructure innovation with our Silicon Root of Trust, where we came out with the world's most secure infrastructure a few years ago. And what we're doing now, since this is a full platform and integrated system, we'll be extending that capability beyond just, you know, how we, you know, create a root of trust in our manufacturing facilities to ensure that it's secure, running it within the infrastructure itself. We'll be extending that vertically up into the software stacks of containers and VMs sort of using that route of trust up to make sure everything's secure in that sense and then eventually up to the workloads themselves. So by being able to go back to that root of trust it really makes a big difference in how people can run things in an enterprise secure way. Great innovations continued. And one of our big focus areas throughout this year. >> So where does it fit in the portfolio, John? I mean, how is it compliment or how is it different from, you know, the typical HPE systems, the hardware and software that we're used to? >> You might think of this as sort of a best of, bringing together all the great innovations of HPE. You know, we've got awesome infrastructure that we've led for many, many years. We've got, you know, great more Cloud Native software that's being developed. We've got great partnerships that we've got with a lot of the leading vendors out there. This allows us to bring all of those things together into a integrated platform that is really intended to run these Cloud Native services. So it builds on top of that leadership, fits in that sense with the portfolio, but it's ultimately about how it allows us to run and extend our GreenLake capabilities as we know them to make them more, more consumable, if you want to call it for a lot of our enterprise clients at whatever location that they. >> So when would I use Lighthouse and when would I use sort of a traditional HPE system? >> Yeah, again, it's a matter of which level of integration people want. You know, Cloud is really also in terms of experience about simplifying what people are purchasing and making it easier for them to consume, easier for them to roll out a lot of these things. That's when you'd want to purchase a Lighthouse versus our other infrastructure products. We'll always have those leading infrastructure products where people can put together everything in exactly the way that they want and go through the qualification and certification of a lot of those workloads. Or they can go ahead and select this GreenLake Lighthouse, where they have a lot of these things available in a catalog. We do validation of the workloads, and platform systems, so that it's all sort of ready for people to roll out at a much more secure, tested and agile fashion. >> So if I have a Cloud first strategy, but I don't want to put it in the public Cloud, but I want that Cloud experience. And I want to go fast. It sounds like Lighthouse, I'm the perfect customer for Lighthouse. >> Precisely, you know, this is taking that Cloud experience that people are wanting, the simplicity of those deployments and making it where it can come to them in whichever location that they want, you know, running it on a consumption basis. So that it's a lot easier way for them to go ahead and manage and deploy those things. Without a lot of the internal qualification and certifications that they've had to do over years. >> Versus OK, but and, or if I want to customize it maybe I want to, maybe I'm a channel partner. I want to bring some of my own value. I got a specific use case, that's not covered by something like Lighthouse. That's where I would go with a more traditional infrastructure. >> Correct. Yeah, if anyone wants to do customization, we've got a great set of products for that. We really want to use a Lighthouse as a mechanism for us to standardize and focus on more enabling these broader Cloud capabilities for clients. >> And lighthouse, talk a little bit more about the automation that I get that, you know, things like patching and software updates, that's sort of included in this integrated system, is that correct? >> Yeah. >> Absolutely. You know, when people think about you know, managing workloads in the Cloud, they don't worry about taking care of firmware updating and a lot of those things. That's all taken care of by the provider. So in that same experience, Lighthouse comes with all of the firmware updating, all of the software updating all included, all managed through our GreenLake managed services teams. So that's just part of how the system takes care of itself. You know, that's a new level of capability and experience that's consistent with all of the Cloud providers out there. >> And that's, OK so, that's something that is a managed service. So let's say I have a Lighthouse on prem, you're going to, that manage services doing all the patching and the releases, and the updates and that, that lives in the Cloud, that lives in HPE, that lives in my prem. >> Well, yeah, ultimately it all goes through GreenLake central and gets managed. You know, all of those deployments are automated in nature so that, you know, people don't have to worry about them. There's multiple ways that that can get delivered to them. We have some, you know, automation and control plane technology that brings that all together for them. You know, it can vary based on the client, on, you know, their degree of how they want to manage some of that, but it's all taken care of for them. >> And, you know, you've got GreenLake in the name, am I to infer from that that it sort of dovetails in, is one of the puzzles in the GreenLake mosaic. >> Yeah, exactly. So think of, think of GreenLake as our broader initiative for everything Cloud. And how do we start enabling not only these Cloud services, but make it easier for people to deploy those and consume them wherever they need. And this is the enablement piece. This is that portion of Greenlake that helps them enable that connected degree like central, where they can manage everything centrally. And then we've got that broad catalog of services available. >> And when can I get it, when's it go GA? >> Yeah. So it'll, July is when our first set of shipments and availability are there. So just a very, you know, few days after, you know, discover here and we'll expand the portfolio over time with more of a mainstream version, early, more technical or performance oriented ones available soon thereafter. And we've got plans even for edge type offerings, more in the future as well. So a case where we'll continue to build and expand more targeting these platforms to folks needs. Whether they're enterprise or maybe there are vertical offerings that they want, in terms of how they, you know, move all these things together. Think of Telco is a great case where people want this. Healthcare is another area where we can have the value of these integrated systems in a very purpose-built way. >> Can I ask you like, what's inside? You know, what can I get in terms of you know, basic infrastructure, compute, storage, networking? What are my options? >> All of the above, you know, what we'll do is we'll go through the basic selection of all of that greatest hits within our complete portfolio, pull them together, give you a few simple choices. You know, you think about it as, you want general purpose compute modules. You might want compute optimized or memory optimized modules. Each of those are simple choices that you'll make that come together. Underlying all that are the great infrastructure pieces that you've known for years. But we take care of simplifying that for you. So you don't have to worry about those details. >> Great. Well, John, congratulations on the new product, and thank you for sharing the update with theCUBE. >> Thank you very much. Great to talk to you. >> All right, thank you for watching theCUBE's coverage of HPE Discover 2021. My name is Dave Vellante. Keep it right there. We're right back with more coverage right after this short break. (outro tune)

>>Welcome back to HP discover 2021 the virtual version my name is Dave valentin. You're watching the cubes continuous coverage of the event, john Ramallah is here. He's the senior director of product management for HP. Green Lake Lighthouse. New offering from HP. We're gonna talk about that. We're gonna talk about cloud native. Hey john, welcome to the cube. Good to see you again. >>Awesome. Great to be with you again. >>All right. So what is Green Lake Lighthouse? >>Yeah, it's very excited. Another new offering and innovation from H P E to support our broader Green Lake strategy and plans. It's really a brand new, purpose built cloud native platform that we've developed and created. That pulls together all of our infrastructure leadership with our platform software leadership into a single integrated system built to run green light cloud services. So think of it as you know, fully integrated, deploy it any place you want on your premises at a co location provider or at the edge wherever you need. Um, they'll inter operate, work together sharing data, you know, running apps together. Great capability for people to bring the cloud where they want as we talk about what Green like it's the cloud that comes to you. >>So should we think of this as a as a management platform? Is it also sort of a quasi development platform kind of, where does it fit in that spectrum? >>Well, it's really more of an integrated system with all of the integrated control planes needed to run it in a distributed fashion. So it's a it's a true distributed cloud intended to run at any client location that's needed, connects back to Green Lake Central and our Green Light cloud operations teams to go ahead and run any cloud services that they want. So you get the benefit of running those workloads wherever you need but that, you know, uh centralized control that people want in terms of how they run their class. >>Okay so we think of these things like for instance how is it different from a WS outposts or things like you know as your stack or as your hub? >>Yeah, very simply this is because it's a distributed cloud intended to make it so you can run it wherever you need. You don't need to be tethered to any of the public cause or the various public clouds out there so people can now run their systems wherever they want however they need without that required tethering that much of those other vendors require. So you can really sort of own your own cloud or have that cloud come to wherever you need it within your overall. I. T. >>Can I tether to a public cloud if I want to. >>Yes. The cloud services like many other cloud services can interconnect together, so no issue, if you want to run or even do fail over between public cloud or on premises, it's all how you want to set it up. But that connection to public cut again through Green Lake is done at that cloud services level. Uh you know where you would connect one of the screen, like lighthouse systems to the public cloud three services. >>Okay, so maybe we talk a little bit about the use cases in a minute, but but how flexible is this? How do I configure Lighthouse? You know what what comes standard? What what what what are my options? >>Yes, so we've designed it in a very modular fashion so that people can really configure it to whatever their needs are at any given location. So there's a basic set of modules that align to a lot of the compute and storage instances that people are familiar with from all of the cloud providers, you simply tell us which workloads you want to be running on it and how much capacity you want and that will get configured and deployed to that given site. In terms of the different types, we have what we're calling to series or a set of series that are available for this to meet different sets of needs, one being more mainstream for broad use cases that people need virtualized container, any other type of enterprise workloads and another more technically focused with higher performance networking. For higher performance deployments, you can choose which of those fits your needs for those given areas. >>So maybe you could talk a little bit more about the workloads and what specifically is uh supported and how they get deployed. >>Again, all of it is managed and run through Green Lake Central. That's our one location where people can go to watch these things manage them. You can run container as a service VM as a service as needed on these different platforms. You can actually mix and match those as well. So one of these platforms can run multiple of those and you can vary the mix of those as your business needs change over time. So think of it as a very flexible way to manage this, which is really what cloud native is all about, having that flexibility to run those workloads wherever and however you need. In addition, we can build more advanced type of solutions on top of those sort of foundational capabilities with things like HPC is a service and collapses a service to better enable clients to deploy any of their given enterprise workloads. >>John what about the security model for lighthouse? Um, that's obviously a big deal. Everybody's talking about these days. It can't open the, the news without seeing some kind of, you know, hack de jure, how does Lighthouse operate in the, you know, secure environment? >>Well, you know, first of all, there's sort of a new standard that was established, um, you know, within these cloud operating models and HPV was leading in terms of infrastructure innovation with our Silicon Root of Trust, where we came out with the world's most secure infrastructure a few years ago. And what we're doing now, since this is a full platform and integrated system will be extending that capability beyond just how we create a root of trust in our manufacturing facilities to ensure that it's secure. Running it within the infrastructure itself, will be extending that vertically up into the software stacks of containers and VMS sort of using that root of trust up to make sure everything's secure in that sense. And then eventually up to the workloads themselves. So by being able to go back to that root of trust, it really makes a big difference in how people can run things in an enterprise secure way. Great innovations continued and one of our big focus areas throughout this year. >>So where does it fit in the portfolio, john I mean, how is it uh, compliment or how is it different from, you know, the typical HP systems, the hardware and software that we're used to? >>You might think of this as sort of a best of bringing together all the great innovations of H P D. You know, we we've got awesome infrastructure that we lead for many, many years. We've got, you know, great more cloud native software that's being developed. We've got great partnerships that we've got with a lot of the leading vendors out there. This allows us to bring all of those things together into an integrated platform that is really intended to run these cloud native services. So uh it builds on top of that leadership fits uh in that sense with the portfolio, but it's ultimately about how it allows us to run and extend our green light capabilities as we know them, to make them more uh more consumable if you want to call it for a lot of our enterprise clients and whatever location. So >>when would I when would I use Lighthouse? And when would I use sort of a traditional H P E system? >>Again, it's a matter of which level of integration people want. Cloud is really also in terms of experience about simplifying what people are purchasing and making it easier for them to consume easier for them to roll out a lot of these things. That's when you'd want to purchase a Lighthouse versus our other infrastructure products, we'll always have those leading infrastructure products where people can put together everything exactly the way that they want and go through the qualification and certification of a lot of those workloads or they can go ahead and select this green like Lighthouse, where they have a lot of these things available in a catalog. We do validation of, of the workloads and, and uh, platform systems so that it's all sort of ready for people to roll out in a much more secure, tested and agile fashion. >>So if I have a cloud first strategy, but I don't want to put it in the public cloud, but I want that cloud experience. Uh, and I want to go fast. It sounds like Lighthouse is that I'm the perfect customer for for Lighthouse, >>precisely. You know, this is taking that cloud experience that people are wanting the simplicity of those deployments and making it where it can come to them in whichever location that they want. You know, running it on a consumption basis so that it's a lot easier wait for them to go ahead and manage and deploy those things with out a lot of the internal qualifications and certifications that they had to do over the years >>versus okay. But or, and or if I want to customize it, maybe I want to, maybe I'm a channel partner. I want to bring some of my own value. I got a specific use case that's not covered by something like Lighthouse. That's where I would go with the more traditional infrastructure, >>correct? Yes. If anyone wants to do customization, we've got a great set of products for that. We really want to use Lighthouses, a mechanism for us to standardize and focus on more enabling these broader cloud capabilities for crime >>and Lighthouse. Uh Talk a little bit more about the automation that that I get, you know, things like patching and software updates that's sort of included in this integrated system. >>Is that correct? Absolutely. You know, when, when when people think about, you know, managing workloads in the cloud, they don't worry about taking care of from we're updating and a lot of those things that's all taken care of by the provider. So uh in that same experience, Lighthouse comes with all of the firmware, updating, all of the software, updating all included, all managed through our Green Lake managed services teams. So that's just part of how the system takes care of itself. Um You know, that's a new level of capability and experience that's consistent with all other cloud providers >>and that's that's okay, so that's that's something that is a managed service. Um So let's say I have a lighthouse on prem, you're gonna you're gonna that managed services doing all the patching and the releases and the updates and that lives that lives in the cloud, that lives in hp, that lives in my prem. >>Well, yeah, ultimately it all goes through Green Lake Central and it's managed. Um you know, all of those deployments are are automated in nature so that people don't have to worry about them. Um There's multiple ways that that can get delivered to them. We have some automation and control plane technology that brings that all together for them. Um You know, it can vary based on the client on their degree of of how they want to manage some of that, but it's all taken care of for them. >>And you've got Green Lake in the name and my to infer from that that it's sort of dovetails in is one of the puzzles in the Green Lake mosaic. >>Yeah, exactly. So think of think of Green Lake as our broader initiative for everything cloud and how do we start enabling not only these cloud services, but make it easier for people to deploy those and consume them, consume them wherever they need. And this is the enablement piece. This is that portion of green light that helps them enable that connected to green like Central where they can manage everything centrally. And then we've got that broad catalog of services available. >>And when can I get it? When you go G. A. >>Yes. So it'll july is when our first set of shipments and availability are there. So just a very few days after you discover here, and we'll expand the portfolio over time with more of a mainstream version early, more technical or performance oriented ones available soon thereafter. And we've got plans even for edge type offerings, uh more in the, in the future as well. So a case where we'll continue to build and expand more targeting these platforms to folks needs whether their enterprise or maybe there are vertical offerings that they want in terms of how they move all these things together. Think of Telco is a great case where people want this. Healthcare is another area where we can add the value of these integrated systems in a very purpose built way. >>Can I ask you what, like what's inside, you know, what, what can I get in terms of, you know, basic infrastructure, compute storage, networking, what are my options, >>all of the above. You know, what we'll do is we'll we'll go through the basic selection of all of that greatest hits uh within our complete portfolio. Pulling together, give you a few simple choices, you know, you think about it as you want, general purpose compute modules you might want compute optimized or memory optimized modules. Each of those are simple choices that you'll make that come together underlying all that are the great infrastructure pieces that you've known for years, but we take care of simplifying that for you so you don't have to worry about those details. >>Great well, john, congratulations on the new new product and uh and thank you for sharing the the the update with the cube. >>Thank you very much appreciate. >>All right, thank you for watching the cubes coverage of HP discover 2021. My name is Dave Volonte. Keep it right there right back with more coverage. Right after this short break. >>Yeah. Mhm.