Layers of the anatomy of cloud computing
Several layers are responsible for carrying out cloud processes smoothly. Some of them are discussed below.
Service Catalog
The service catalog is critical to the definition of the cloud since it specifies the types of services that the cloud can provide and what they cost to the end-user. Architecture is the first thing that is drafted before a cloud. Before processing each request for a new resource, the service management layer consults the service catalog.
Cloud Life cycle Management Layer (CLM)
The CLM layer handles the coordination of all other layers in the cloud. All internal and external queries are directed to the CLM layer initially. Internally, CLM may send requests and actions to different layers for processing.
Provisioning and Configuration Module
It's the lowest cloud level, usually found on bare hardware (as firmware) or on top of the hypervisor layer. Its purpose is to hide the underlying hardware and provide a standard mechanism for spawning virtual machine instances on demand. It also manages the virtual machine's operating systems and applications post-configuration.
Monitoring and Optimization
This layer is in charge of cloud monitoring for all services, storage, networking, and application components. It could conduct routine activities based on the statistics to optimize the behavior of the infrastructure components and offer essential data to the cloud administrator so that the setup could be further optimized for optimal usage and performance.
Metering and Chargeback
This layer contains utilities for calculating cloud resource utilization. The metering module gathers all use data per domain and use. This module provides the cloud administrator with adequate information to regularly track ongoing resource usage and generate bills based on that usage.
Orchestration
Cloud operations rely heavily on orchestration. Requests from the service management layer, monitoring, and chargeback modules are converted to appropriate action items, then forwarded to the provisioning and configuration module for final closure. In the process of orchestration, the CMDB is updated.
Configuration Management Database (CMDB)
It is a central configuration repository that stores and updates all metadata and configuration for various modules and resources in real-time. Third-party software and integration components can then access the repository using standard protocols like SOAP. As requests are processed in the cloud, all updates in the CMDB happen in real-time.
Frequently Asked Questions
What is the limitation of Configuration Management Database (CMDB) in the anatomy of cloud computing?
Due to the linked dependencies and relationships in CMDB, deleting any configuration item (CI) is practically impossible.
What are some limitations of virtualization in cloud computing?
Some limitations of virtualization in cloud computing are that data can be at risk, learning new infrastructure, high initial investment, etc.
What is meant by orchestration in the anatomy of cloud computing?
The process of automating the procedures required to manage connections and operations of workloads on private and public clouds is known as cloud orchestration.
What is the difference between a server and a data center according to the anatomy of cloud computing?
The significant difference between the server and data center is that server runs on a single node with internalized data stores. In contrast, the data center runs on several nodes with externalized data stores.
What is the platform in the anatomy of cloud computing?
A server's operating system and hardware in an Internet-based data center are referred to as a cloud platform. It enables remote and large-scale coexistence of software and hardware devices.
Conclusion
In this article, we have extensively discussed the concepts of the anatomy of cloud computing. We started with introducing the anatomy of cloud computing; then, we explained the components of the anatomy of cloud computing then concluded with layers of the anatomy of cloud computing.