Cloud management platforms (CMPs)

- [Instructor] All right let's talk about cloud management platforms and their importance to cloud communing governance. So what's important here is that these are resource governance tools. They're probably the primary example of a resource governance tool. So they typically don't deal with services. They deal with core cloud computing services, such as storage compute, things like that. So these tools allow you to deal with single or multi clouds, and typically they're deployed in a multi cloud world because ultimately if you're leveraging more than one cloud, things get confusing quickly. Things get complex quickly. What we're trying to do is remove us from that complexity using multi clouds as really kind of a layer of abstraction and automation between the person who's managing the cloud and governing the cloud, and the different multi clouds out there. Whatever brands you're able to leverage, and most people are doing cloud with multi cloud these days. So they are different, but morphing in the same direction. So everybody out there has their own take on what a cloud management platform is. However, the patterns and the way in which they're morphing or evolving are pretty much the same. So cloud management platforms are really the ability to abstract yourself away from the complexities of the underlying cloud computing architecture. So you may have multi cloud, you may have private cloud, you may have legacy systems that are all difficult to manage if you're using the common native features of each of those platforms. And cloud management platforms allow you to, in essence, sit at a higher level in the abstraction chain and manage these things in very similar ways. Storage is managed the same as storage on AWS, storage on Microsoft, storage on Google. So the single pane of glass approach you'll hear a lot out in the governance world, and what it really means is abstraction. Your ability, to an essence, monitor, have dashboards. Common ways of looking at very complex systems, and in essence hiding the cloud needed features away from you so you're not dealing with the underlying clouds. So we're able to deal with policies, we're able to set up pre-programed ways in which we access the resources. Such as we can have a cloud A, cloud B, cloud C. And keep in mind that cloud A, cloud, B, and cloud C can be any number of types of clouds, and also numbers of brands of clouds. Cloud A could be an OpenStack private cloud. Cloud B could be Amazon Web Services, and cloud C could be Microsoft. So on the cloud A we have services, security, data, and services, security, applications, and data under cloud B. Then cloud C may have services, security, applications, and data as well. Keep in mind that we're getting to these various underlying resources such as security in cloud B, or services on cloud C by using the single interface. Ultimately we're looking at these clouds through a single lens. Through the ability to, in essence, deal with them the same no matter what the native differences are and the particular cloud providers we have.