 Good morning, good afternoon, and good evening. I am Kevin Dewick with HPE GreenLake Cloud Services and welcome to the HPE GreenLake for private cloud session. I am joined today by Raj Mistry and Steve Schoewalter who will walk us through today's presentation and demonstration. We'd like to keep this session interactive so please submit your questions in the chat window. We have subject matter experts on the line to answer your questions. So with that I'll hand over to Raj. Cool, thanks Kevin. So the cloud is now fast becoming a reality. We see as HPE and what our customers say to us that it's not an expectation anymore, it's an absolute necessity. So the research and the stats that you see on the screen just kind of like prove that over the last five to six years organizations, enterprises are adopting cloud, be it in the data center with the hyperscalers or a mixture of both. But the interesting thing that we see now is a moving investment to basically increase private cloud capability. And in that vein what we've done with GreenLake Cloud Services is create a rich portfolio that delivers that cloud-like experience either at the edge in your data center co-location that actually matches and actually embraces the work that you do with the hyperscalers. What we're doing here is we're providing self-service capability, elasticity in the means in the way that you would use this and the way that you would flex things up and down. More importantly, all of this is one and operated for you, which comes true to what we say in terms of delivering that cloud experience within those locations be they the edge, the data center or the co-loc. GreenLake for private cloud was initially launched in summer 2020. It was the first iteration of what we call the GreenLake platforms. What we're trying to do with this element of the GreenLake Cloud Services portfolio is for things which is eliminate the complexity of building things that live, breed, behave and act like in a cloud-like manner in the data center because this is hard. The visibility around the way that you would manage and understand and run and operate certain elements of that cloud. The governance and the compliance piece, which is important, especially when it comes to things like applying policies, etc. that you would have and then the skills gap that we do from a managed services perspective that takes things off. From an infrastructure standpoint, beginning at the left, world-class HPE compute storage network switches embracing the virtualization and the software defined networking layer together with a pretty rich cloud automation and orchestration portal, all wrapped up for you, pre-built, pre-architected, removing complexity, increasing time to value and the actual delivery time scales. If we move to the actual experience, all of this is actually embracing the way that you would access these solutions. In through GreenLake Central, that's where your as-a-service experience begins with HPE. It's your entry point into the world of as-a-service. From here onwards, you would actually access that service. From a private cloud standpoint, this is where you would initiate the cloud management portal and then you would begin either working in that and the roles of either administrator, consumer, etc. Lastly, pushing buttons and provisioning stuff is really easy, but a lot of our focus is in the post-provisioning processes of understanding as it turned on, as it off. How much is it costing me? Am I getting the most efficiency out of it? Am I running out of capacity to deliver services to my users? All of this is finally wrapped up with the managed platform capability, which means you now have to understand and treat Hewlett-Packard Enterprise as an MSP and a cloud provider within your data center. We take care of the infrastructure, the software, and the experience. Your entry point is at the cloud management layer. That's how we get you going. Hey, Raj, I know we made some announcements earlier today about a new scalable form factor, where you know private cloud. I was wondering if maybe you could talk about how that extends the value proposition for customers. Good question, Steve. What the scalable form factor is really is us looking at market feedback, understanding what our customers are, and bringing this as an entry point into the smaller and the more medium enterprise who are looking to deliver private cloud capabilities, making it easier for them to embrace it and then scale. The other difference is the way that we actually have flexibility in the way that that cloud solution now grows. Different options are available to customers in terms of what they want to do. We typically talk as a team and to our customers about different roles. We have a notion of the cloud administrator or the cloud operator. This is more of your classic administrative role. This is where our customers would come in right at the cloud management layer and begin configuring their environment, networking, services, etc. From here onwards, it's the cloud consumer, so applications, application developers, lines of business, etc. They're presented with a self-service catalog for them to come and provision stuff. Could be normal VMs, it could be applications, depending on what the administrators or the operators have chosen to present to them. Lastly, it's around how do I understand what's going on in the environment, so the focus, as I mentioned beforehand, visibility to then understand what's happening to then optimize later, so addressing the needs of lines of business or IT leaders and business leaders within our customer base. All of this then begins from our central point of access, which is Green Lake Central. From here, services and solutions that customers subscribe to are presented. Depending on who you are, your privileges, your role within the actual environment, you get different options. A cloud administrator may see different things in central because they require administrative functions within the cloud environment. A consumer such as me may have limited views in central access or service, but I can basically only read or provision set things that are done for me. From a lines of business or from an IT leadership perspective, it's about providing predictive billing, visibility, and to cast understanding from a planning standpoint and allowing people to optimize at ease and speed. Central is where your journey begins, and then from within there, you launch the necessary service that you've subscribed to. Today's focus is the private cloud. Who was the solution built for Arash? Initially, we started off at the large enterprise level, Kevin, but what we've done as we do as HPE is listen to our customers. We've introduced on the launching today the scalable form factor to address the needs of a multitude of clients, both large and small, enable people to have different kind of like deployment types, so remote office branch office with a larger customers. For those smaller enterprises wanting to begin their private cloud journey, a great way for them to do that with HPE. All right. Thank you. How does a customer access the private cloud environment? Via Greenlake Central, Kevin, great question. That's our entry point for any of the services. Easier to see later on in the demo that Steve's going to walk through. It's where customers come in and depending on role, access, privilege, rights, etc., you are presented with your services, and from within there, you access the service depending on the role that's been assigned to you. Steve, why don't you show us a little bit about what a cloud administrator or cloud operator can do within the environment? Sure. Happy to, Raj. As we talk to these personas or use cases, our experience, as Raj mentioned, will always start in Greenlake Central. The role or persona I'm taking on here is that of an administrator of this private cloud environment. Again, I start off by logging in to Greenlake Central once the services stood up and available. Within my data center, I see the Greenlake for private cloud tile, which gives me an overview of services I'm consuming and some of the things that might be running in that environment. Clicking on the tile takes me to the cloud management platform dashboard. This is where I, as an administrator, can configure and control lots of things in the environment on behalf of my end users. So a couple of examples of things I might want to do first off. There's an important notion of grouping that we use for access control within the environment. So I may want to organize my users in the groups to control what they can see, what they can do, what sort of policies I can apply to them. Next, I probably want to configure the underlying software defined network that Raj talked about. So again, we deliver a software defined networking capability from within the software defined network. This is where I can create things like underlying networks, underlying distributed V switches, IP address pools. I can also configure and manage software defined routers, firewall rules, and some of those sorts of things within the environment. Any IP address pools I have that I want to make available to some of those underlying networks, I could manage from within here as well. We also feature software defined load balancing capabilities. So again, if I expect my developers or my end users to be able to provision resources that require some load balancing, I can create those load balancers to find the types of load balancing I want to make available to those end users from within here as well. Finally, I can manage keys and certificates. So if I have things like key pairs or SSL certificates, again, that I want to make available to my end users, I could manage all that from within here. And then one of the final things I might want to do is start to manage an automation library. So a library of virtual images that I want to make available for my end users. Because the private cloud solution is based on VMware, I might want to just pull in some existing VMware images I have, or I might want to create some new custom images. But really, I have a central place to be able to manage that library of images, and then decide who has access to which images and how I want to make those available to end users to be able to provision and lifecycle manage. So that's a quick overview of some of the administrative capabilities. Kevin, any questions at this point about that capability? I got one for you. Can customers bring their own tooling to the private cloud? Oh, yeah. So that's a great question. So, you know, almost every customer I talk to nowadays has made a large investment typically in some sort of automation tooling. And one of the things that we want to provide is the ability to surface that tooling and kind of allow customers to be able to reuse that tooling within our private cloud environment. So within the private cloud platform as an administrator, I can create all sorts of scripts and maybe some basic capabilities I want to define for scripts. But I also have the ability to integrate automation platforms. So we can see in this particular environment, I've onboarded a set of Ansible playbooks that exist in a Git repo. I really just point the cloud management platform to that repo. It scrapes all the playbooks that it finds there. And those become available as tasks and workflows that I can use after a provision VM. So again, I can reuse that investment that I've made in automating things like application provisioning, application configuration for my end users within my environment. Okay, I've got another one for you. How do customers improve control and governance of their private cloud? Yeah. So there are a couple of different ways to do that. So, you know, we'll talk specifically one of the capabilities I have within the cloud management platform is the ability to create policies. Policies are really a way I can provide my users with, you know, self-service access to kind of go do the things that they need to do, but provide some control around what they can do. So there's all sorts of policies I can create. So policies around things like if I've got certain group of users that I want to require to get provision approval, anytime they have provisioned something, I want an administrator to approve it. I can also limit the things that maybe a group of consumers can consume within my environment. Maybe I want to define a certain host name rule. So rather than create your own host names, I have a rule I want applied. If tagging and showback is important, I might want to force some tags within my environment. Say, hey, anybody who provisions something needs to provide me a value for this tag, and then I can define how that applies within the environment. So hopefully that answers some questions and gives you a feel of how these cloud administrators would work within the environment to be able to manage the overall environment itself. Perfect. Thanks, Steve. So what we've just described and seen is the ability for a cloud administrator to, hey, do day one tasks, set things up, set some services up, and more importantly, apply some rules controls and governance. So it keeps users safe and it keeps IT happy really. So let's say I'm Raj, I'm the head of applications, and I've got a team of developers. So I'm now going to come in as a consumer. Can you show me what I can do as a consumer, please, sir? Sure, Raj. So again, just like with the administrative use case we talked about as a cloud consumer, my experience starts in GreenLake Central. So once I'm logged into GreenLake Central, if I've been provided access to the environment by my administrators, I see the GreenLake for private cloud tile, and I click on it to get to the cloud management platform, just like the administrator use. Now, I probably see a lot less because I probably have a lot less capabilities here, but one of the first places I probably want to go is take a look at what instances have been provisioned and maybe provision an instance on my own. So instance provisioning is very simple. Really, it's just a few clicks and answer a few questions. So in this case, if I have access to multiple groups, so kind of that logical separation that I talked about, I'd first pick which group is this a part of. Again, in my particular case, I can provide a free form name because that's the policy that's been set up for me. I've got a forced tag, so I have to provide a tag or a label that tells me what area this is a part of. And as I continue to drill down, now I get to a point where I can select my image based on the images that have been made available to me. I can choose a size of a VM, so we have sort of some pre-provision sizes that my administrators have made available to me. And in some cases, I can customize some things within those sizes or maybe I can't, again, just depending on how this was created. Select the network that I want to connect to and provide a few other options. One of the things I do want to talk about is this notion of tagging. Tagging is very important from a showback perspective and we'll talk about when we get to cost analysis, how we can use any tags that get applied here to be able to do some showback reporting later. So if I want to provide a tag for an owner to make sure I can always write a report that says show me everything Steve has consumed, I've got the ability to provide those tags here. And again, through a policy, I can make those tags required. A couple other choices I have, any of that available automation that maybe my administrators have made available, I can run here. I can select some scaling of my application, maybe go ahead and auto select a backup schedule, manage some life cycle actions if maybe this VM only needs to run during weekdays and I don't need it on the weekends. I can have it automatically shut down, start up. And at the end, just click on complete and my VM is often being built. And then once my VMs are up and running, I've got access to be able to manage those VMs on a running basis. So if I have a VM that's running and I want to be able to manage it, very simple again from within the cloud management platform to go take a look at maybe how this VM is performing. Maybe I want to log into the console. Maybe I want to take a look at the log stash, the log error messages that this VM has created, or maybe I just want to stop it, start it, create an image from it, or maybe after I've provisioned it, run some of those workflows on it. As an end user, I've got the capability to kind of fully manage and fully control those VMs once I have them up and running. So that's a quick overview of that cloud consumer use case. Kevin, do you have any questions right now about that use case? Yeah, I do. Cloud consumers today want more than a VM. So how can a private cloud deliver more value for cloud consumers? Yeah, so that's a great question. So we talked a little bit about the cloud management platform's ability to integrate with existing automation for things like application installation and configuration. But one thing I didn't talk about is kind of an alternate way we can use that. And that's through this notion of blueprints. So within the cloud management platform, I as a developer or as an administrator can set up blueprints, which are really very complex applications. These could be multi-node, multi-tier applications where each tier may have a different application installed. They may be load balanced, all those sorts of things. And I can stitch all those together and make them available as a catalog item. It's just kind of one simple catalog item for an end user to consume. So they don't have to understand all the complexity or all the multiple nodes or all the workflows required on the back end to provide that service. I've already done all that hard work. I advertise it to them, and they don't have to know, again, in this particular case, I've got a web tier made up of a couple VMs, a database tier made up of a couple VMs. There's some automation running maybe through those Ansible playbooks in the back end to make all those things happen. Really as an end user, I just say, hey, I want one of these applications. I may need to answer a few questions, depending on how the application or the blueprint is built. And then I could push that out as an entire application. And again, I don't have to understand all the complexities that make up that multi node, multi tier application in the background. Steve, that's really cool. So line phase as good as it can be. So right. So we've pushed some buttons, we've set some stuff for, we've provisioned some stuff. So right at the beginning, you know, we spoke about the post provisioning stuff. So how do we actually manage the costs and also look at the usage within the environment, which is also important to our customers? Yeah. So it's a great question, Raj. So, you know, obviously customers want to understand what their overall green link consumption is, what their bill is, how all those things relate together. And then they probably want to do much more detailed cost analysis as well. So the good news here, we provide all this tooling and all this is available right through GreenLake Central. So a couple of the tiles that you'll see in GreenLake Central tie into the private cloud solution, just like they would any other GreenLake solution. So if I want to see overall what I've consumed within my private cloud as a GreenLake resource, I can drill down to understand, hey, what was actually metered as what I consumed, how did that relate to my GreenLake rate card? How did that create the number that appeared on my GreenLake bill for this particular service at the end of the month? I've also got the tools to do capacity planning. Again, just like every other GreenLake environment, we want to be able to show kind of that capacity planning view. So customers can understand kind of what they're consuming, what direction that's trending, and when we may need to add some more additional capacity. So again, when a customer needs more, it's already there and ready to go. They just start to consume it and pay for it as a part of their GreenLake bill. So GreenLake customers have a dedicated account team that kind of works with them to keep an eye on that capacity. And again, make sure we're working with customers to make the right decisions about when is the right time to add additional capacity to the environment. And then finally, our customers also get access to consumption analytics for much more detailed cost reporting. So within consumption analytics, I can take advantage of those tags that I talked about previously. So here's a report I created where I want to see my private cloud consumption and use really broken down by cost center and by the VMs that my users within each of those cost centers is consuming. So I wrote a report to do some showback costing based on those tags. So in this particular case, I can tell, for example, the Colo engineer cost center that, hey, over the last month, you've consumed 32 elements within the private cloud environment. Your total cost for that was $860. And I can give them the ability to, if they want, drill down on this. So now they'll see every individual VM that was provisioned, where it ran, when it ran. And in this particular case, I've broken down the cost between compute and storage because I really wanted to see those separately as separate line items. But really give customers the ability to do whatever showback or chargeback reporting makes sense within their organization, based on the tags they want to apply and how they want to be able to show and consume those costs. So Kevin, any questions about sort of this cost analysis use case? Yeah, is there a way to proactively monitor consumption of the private cloud environment? Yeah, so we actually provide a couple different ways to do that. One right within consumption analytics that we talked about, one of the capabilities I have is the ability to set a budget. So in this particular case, I've set a budget again, kind of by that cost center, that I can take a look at, hey, what are all these cost centers consuming within this private cloud environment? And how does that relate to what maybe an amount that I've given them to be able to use? So I can take a look at and see, hey, in the current period, I've got one cost center that's over budget to that are under budget, and take a look at their historical use as well. Going back to the cloud management platform, I also have more of a hard way to be able to set those consumption boundaries by using a policy. So again, if I want to create a policy that says, hey, Steve can only have 20 VMs. Once he's provisioned those 20 VMs, he can't have any more. He's got to come back and ask for more. And again, when I create this policy, I could apply it to a group or an individual user, just kind of based on how I want to put those guardrails around that environment and sort of do that around that environment. So there's kind of a way to do this in more of a soft way based on cost to understand budgets and get notifications when I get close to my budget limits, or more of a hard way to actually be able to limit resources that customers can consume within the environment itself. So with that, Raj, I'll throw it back to you. Cool. Thanks, Steve. So just to wrap up really, Steve and Kevin, thank you for the great demonstration in the chat really. A few things for the audience and our customers to understand. What we're now doing with Green Lane for Private Cloud and other platform solutions is helping you to get started really, really quickly, allowing you to begin your journey with us at the right level. And then you can scale depending on how you're actually managing your transformation being from an infrastructure standpoint, application standpoint, and you're looking to basically just modernize the way that you deliver services back out to your internal users. The other side of it is the important fact that we now act and behave very much like a cloud. So because we run those environments for you, we eliminate the complexity of feeding and watering, all the infrastructure, the configuration and the updates of the software layer, it leaves you free to basically deliver the services like Steve has just shown. The other side of it, final point is it's all usage based. So again, lowering kind of like the initial investment risk for you guys, allowing you to benefit from the way that we've actually integrated these solutions and technologies so you can just embrace them and take advantage of them. Excellent. Thank you, Raj. So I would like to thank you all for attending today. Thank you Raj and Steve for a brilliant demonstration. If you would like more information or like to speak to someone directly, then please fill out the poll by clicking on the poll option at the top of the chat box. So in closing, if you are interested in HPE GreenLake for private cloud, then please start a trial. It's easy. Thank you. Thank you all and goodbye for now.