Updated on 2023-12-12 GMT+08:00

Overview

Information Technology Infrastructure Library (ITIL) implements infrastructure-oriented management, facing problems such as data isolation and information inconsistency between O&M services. CMDB centrally manages resource objects and applications, and provides accurate, consistent resource configuration data in time for AOM, LTS, and APM. It also provides data configuration interfaces for maintaining third-party systems.

Function Description

Table 1 Function description

Category

Description

Homepage

On the homepage, search for resources (such as applications and hosts) by keyword or name.

Application Management

Manage the relationships between cloud service objects and applications. The "application + sub-application (optional) + component + environment" model is used.

Resource Management

Centrally manage your cloud services. You can view the association relationships between global cloud service resource objects and applications, including cloud resources that have not been bound to applications, facilitating resource analysis and management.

Environment Tags

Add tags to created application environments so that you can quickly filter environments with the same attributes.

Enterprise Project

An enterprise project can contain one or more applications.

Basic Concepts

CMDB is used to manage application structure information and related configurations. It involves the following concepts:

  • Enterprise project: An enterprise project can contain one or more applications.
  • Application management: Manage the relationships between resource objects and applications. CMDB uses the "application + sub-application (optional) + component + environment" model.
  • Application: basic object of CMDB and root node of the resource management model. An application represents a logical unit, which can be a project, product, or service. After an application is created, you can view the same application topology information in all regions.
  • Sub-application (optional): A maximum of three layers of sub-applications can be created for an application. A sub-application can be regarded as a service, which is a group of components or microservices.
  • Component: minimum unit of an application. It can be regarded as a middleware component on which an application depends, such as Relational Database Service (RDS) and Distributed Message Service (DMS). Generally, a component is used together with environments. It can contain one or more environments. For example, an order application includes the function test environment, pressure test environment, pre-release environment, and live network environment.
  • Environment: Components or programs with different configurations form different environments. Each environment has its own region attribute. You can filter environments by region. You can also add one or more tags when creating an environment, and filter environments by tag. For example, environments can be classified into the formal or test environment by environment type, CN East or CN South environment by region, or Alpha, Beta, Gamma, or Product environment by DevOps pipeline phase.
  • Environment tag: attribute set for an environment. Multiple environments may have the same tag. You can filter required environments by tag. A tag can be added only to different environments of the same application.
  • Resource bind: You can bind a resource object to an environment of an application. A resource object instance of an application can belong to multiple environments.
  • Resource unbind: If the component or environment changes and the resource is not required, you can unbind the resource from the original application.
  • Resource transfer: If the component or environment to which a resource is bound changes, transfer the resource to the target node.