Two-state operation and maintenance of superior cloud: service-oriented CMDB driven by business scenario

In recent years, domestic and foreign CMDB failure cases abound, few successes, some questioned the CMDB is dead? but a variety of business scenarios show that the current data center operations, the CMDB is still an indispensable part, it carries the foundation of operation and maintenance, mastering the lifeblood of operations.

Analysis of past failure cases, quietly think about, failure is nothing more than two points:

First, The CMDB itself is not built enough to adapt to the new situation in the current data center and cloud environment. The current data center is characterized by agile, dynamic and continuous development. Even when the storm comes, the data center environment is changing rapidly. The traditional CMDB cannot keep up with the rhythm and can only feel powerless and deal with various problems frequently.

Second, non-scene-driven, unable to support business needs. The purpose of the CMDB construction is to satisfy the needs of the business, to ensure the continuous and efficient operation of the business, but in many cases, we just use the CMDB as a static configuration management library, not closely related to the business.

If you want to put the business system on the path of agile operations, it is bound to the traditional CMDB make an innovation to realize the change of ideas and ideas. Will shift from a simple static configuration repository to the ability to provide continuous operations for business systems, to provide actuarial operational capabilities for assets, and to provide agile automation capabilities for the technical architecture. Build a service-oriented CMDB driven by business scenarios under cloud computing .

Below, we analyze how to build a CMDB to ensure the agile operation of the business system through a common business scenario, from business system requirements to internal IT resource coordination, on-line deployment, monitoring and operation, to daily operations.

(a) The system first embedded a business system on-line approval process, the steps are as follows:

1, the business unit to the System architecture Group proposed business system construction SLA (Service level agreement) requirements;

2, the system architecture group according to the requirements of the SLA, analysis of the most basic architecture unit;

3, operation and maintenance department according to the Basic Architecture Unit deployment implementation.

(ii) from the system implementation of two forms: deployment patterns and operational patterns

Deployment patterns

1, after the end of the process, the business system, SLA requirements, deployment details into the CMDB;

2, according to the established deployment process, start the process (the system pre-built deployment process);

3, matching automation script (or call API);

4, automatically create the operating environment, deployment system;

5, update the CMDB.

Operating pattern

1, monitoring tools from the CMDB acquisition strategy;

2, the monitoring tool receives the instruction, immediately implements the monitoring;

3, monitoring tools real-time feedback service system SLA indicators to the CMDB;

4, the CMDB will be real-time feedback and the original set of comparison and trend analysis, judge the status of Operation;

5~8, once the current operating conditions do not meet the requirements, the CMDB triggers an automated process to expand the operating environment in real-time elastic capacity.

As can be seen from the above, the CMDB has been transformed into automation, which is driven by services to make the operation of business systems more agile. Therefore, the construction of a continuous, efficient, agile operation, service-type CMDB is more important.

Service Type CMDB construction needs from 2 aspects to start:

1. Service Awareness

The traditional CMDB, the service object is the operation and maintenance personnel, mostly passively accept some instructions. However, the service objects of the CMDB under cloud computing are more business policies, processes, automation tools. From passive mode to active mode, it is necessary to proactively identify problems and solve problems.

2. Service Framework

Provide a complete API system, build services around the upper layer of the business, fully integrate external applications, to extend the convenience of the application.

If you want to build a robust CMDB, the above two pointcuts are only the beginning, and a solid basic function is essential :

1. Modeling capability

A flexible underlying data model can be established to expand resources at any time to meet the consumption needs of different scenarios.

2. Automatic discovery Capability

Discover the infrastructure, virtual applications, and intricate relationships between data centers and cloud environments with polling, APM capture, API calls, and more.

3. Clear Performance Ability

Demonstrate the architecture of your entire data center clearly and in a multidimensional, multi-perspective way.

4, the management of granularity

Establish authorization management mechanisms between infrastructure and application models to determine the depth and granularity of management based on business needs.

5. Capacity analysis capability

Evaluate data centers, integrate metrics analysis, control operations family property and posture, and continuously promote the improvement and promotion of operations and maintenance capabilities.

6. Impact Analysis

Through the impact analysis function, quickly analyze the scope and extent of the failure, identify the root cause of failure, and ensure the efficient operation of the business.

In this idealized scenario, the CMDB provides SLA service requirements for the business system, providing the drive for building and expanding the system architecture. No CMDB can be used out of the box, each enterprise has a different management perspective and management granularity. We have to do the CMDB's own service, tamping the foundation, flexible expansion, the upper layer can be based on business on-demand implementation. The construction of the CMDB is not overnight, but driven by the business scene, slowly run-in, the CMDB construction of the road is a long way!

Introduction: Zhou, the current gifted cloud software products Wang, Yun-Engineering lion One, half legs into the vast world of operations, the goal is to become a little bit of the product Wang, on the sauce.

Two-state operation and maintenance of superior cloud: service-oriented CMDB driven by business scenario