Learn about cloud resource governance.
- [Instructor] So let's talk about resource governance. Again, resources are typically going to be coarse-grained Cloud resources such as storage database services, compute services, virtual services, perhaps cues, things like that, things that are major players within the infrastructure as a service provider that we're basically governing. So when you think about resources and resource management, this is about allocating, managing resources while they're allocated, and de-allocating resources as we need them. What's interesting about this is that you can certainly do that within the Cloud provider and we've provided several demos here as to how you're going to do that, but this is about putting another layer of abstraction on top of the Cloud provider and perhaps including additional Cloud providers and being able to provision resources through a single pane of glass or a single interface.
And so when we talk about governing resources, we're typically going to be talking about Cloud management platforms or tools that are really designed to run and manage these resources through an abstraction layer across different cloud providers. And we'll see a demo of that in this course. So resource governance is bound to Cloud governance. It's the two basic kinds of governance, being resource and services, and we have other things that are part of the framework as well, but these are probably the most important aspects of Cloud governance you need to understand.
Resource governance being dealing with coarse grain, service governance dealing with fine grain. Such as API's and web services, where resources are going to be storage, compute systems, things like that. So this is a breakdown of the chart we saw in the previous video. So Cloud governance technology, resource governance, and we have active, automated, and passive. So there are two kinds of tools out there. One is a passive tool which is basically able to do planning and implement things, but it's not actively dealing with the underlying resources, which is a bit of a disadvantage since it's for going to allocate resources, you don't want to enter that into places, you want that recorded in the particular tool versus a design time tool, which is going to help you somewhat but it's really not going to do anything actively managing and governing the system.
Where active is automated. So in other words, I'm able to leverage resource governance and I'm able to deal with the source and target systems through this automated mechanism. So anything I deal with in the resource governance layer is able to carry that on in the backend automatically. So we have operations-oriented. In other words, I'm dealing with operating the Cloud. And we have development-oriented, both flavors of resource management. So development-oriented would be dealing with servers to run applications and servers to run dev-ops operations, things like that. Operations-oriented would be just dealing with operational types of things, such as allocating servers for the accounting department, for the end of your planning processes, things like that.
Things in the normal course of operations where development would be more net new stuff, building things, ad hoc kinds of operations.
- Cloud governance basics
- Cloud resource governance
- How cloud security and governance are linked
- Defining governance policies
- Cloud management platform basics
- Reviewing service governance tools
- Cloud governance costs
- Understanding your requirements
- Finding the right tools
- Testing cloud governance
- How operations deals with governance