A hybrid cloud automated operation and maintenance publishing system and operation method thereof

Abstract

The present invention discloses a hybrid cloud automated operation and maintenance publishing system, including: a main management center, which selects a regional data center as the main management center; service and business modules, which create automated publishing execution program files for various services and business modules; a configuration center, a deployment object storage space and a database platform, which establish a unified configuration center, a deployment object storage space and a database platform, create service configuration items in the configuration center, establish a classification directory in the object storage, and create a database connection in the database platform for executing SQL statements; and create roles and user accounts in the configuration center and the database platform. The present invention reduces the occurrence of manual memory commands and manual execution errors, and the system service management method also supports the startup of services in parallel, significantly improving the startup efficiency. In the face of business expansion and module addition, only the corresponding configuration and publishing files need to be added to achieve dynamic upgrades.

Description

Technical Field

[0001] The present invention relates to the field of automated operation and maintenance technology, and in particular to a hybrid cloud automated operation and maintenance publishing system and an operation method thereof. Background Art

[0002] With the rapid development of IT technologies such as cloud computing, big data, and artificial intelligence, and the rapid growth and change of enterprise business needs, the pressure and challenges of operation and maintenance management are also increasing. Effectively ensuring the construction of the operation and maintenance platform system and improving the operation and maintenance support capabilities are important issues that the operation and maintenance department needs to solve. With the advancement of operation and maintenance technology and the improvement of the operation and maintenance service system, automated operation and maintenance, as a dynamic direction, is also facing new challenges and changes with the changes in scale and scenarios.

[0003] Release and upgrade are an inevitable and indispensable part of daily operation and maintenance work. In the early stage of business development, the service architecture is small and the number of servers is limited. Traditional manual deployment and automated batch tools can fully meet the existing needs. As the business scale grows and the number of servers increases dramatically, the business architecture will become more and more complicated. When dealing with the same deployment work, manual deployment requires operation and maintenance personnel to repeat the same operations. The huge number of servers brings a huge workload. Although automated tools can perform batch operations at the same time, when facing complex architectures and business modules, different deployment processes still need to be manually run according to the type of business module, which will also generate a lot of repetitive work and prone to human errors;

[0004] At the same time, the current public cloud / private cloud hybrid cloud platforms and cross-regional or even cross-national private cloud hybrid cloud platforms may involve the deployment of online business systems across countries or even across continents. General manual deployment and automation tools cannot meet the efficient and stable operation and maintenance work, resulting in inflated operation and maintenance costs. Summary of the invention

[0005] The purpose of the present invention is to provide a hybrid cloud automated operation and maintenance publishing system and its operation method, so as to solve the problem raised in the above background technology that most of the current servers are deployed based on public cloud / private cloud platforms, involving multiple public cloud vendors or private cloud platform technical standards, and hybrid deployment of multiple data centers across regions / countries / continents, which makes the situation of each data center server different; and with the development of business, the service architecture is constantly changing, and the original manual and automated tool deployment cannot cope with the problems of regional isolation, unified operation and maintenance standards, and platform continuity and reuse.

[0006] To achieve the above object, the present invention provides the following technical solution: a hybrid cloud automated operation and maintenance publishing system, comprising:

[0007] Main management center: select a regional data center as the main management center;

[0008] Service and business modules: Create automated release execution program files for various services and business modules. The file content includes but is not limited to release environment detection, systematized service registration, configuration file and deployment package verification, configuration loading, deployment package acquisition, service start and stop. Customized content is written based on the service type, configuration file format, and startup parameters of the business module. The same business module uses the same release file regardless of region.

[0009] Configuration center, object storage space and database platform: Establish a unified configuration center, deploy object storage space and database platform, create service configuration items in the configuration center, establish a classification directory in the object storage, and create a database connection on the database platform for executing SQL statements;

[0010] Create roles and user accounts in the configuration center and database platform.

[0011] Preferably, in addition to business functions, the main management center is also used to undertake automated tool management, automated release file management, release package backup management and operation and maintenance functions.

[0012] Preferably, when the main management center automatically publishes file updates, other regional computer rooms will automatically obtain the latest published files and execute publishing tasks according to the latest file contents when publishing. Files can be increased or decreased according to business adjustments to achieve dynamic management.

[0013] Preferably, the roles and user accounts are used to set up personnel groups, and different permissions for the configuration center and database platform are allocated to them, so as to achieve management with separate rights and responsibilities.

[0014] An operating method of a hybrid cloud automated operation and maintenance publishing system comprises the following steps:

[0015] Step 1: When releasing for the first time, you need to create service configuration items in the configuration center. They are uniformly named after the service module, and different regions are distinguished by regional labels. When releasing versions on a daily basis, relevant development or configuration personnel will make corresponding configuration modifications, and operation and maintenance personnel will review and release them;

[0016] Step 2: Establish the corresponding database connection of the service on the database platform, create users and assign different permissions. When publishing, the relevant developers submit the SQL to be executed, and the operation and maintenance personnel review and execute the SQL;

[0017] Step 3: When publishing for the first time, you need to create an execution management file for the corresponding service in the main management computer room. You can use it directly in subsequent releases or modify it accordingly according to your needs.

[0018] Step 4: Upload the corresponding service module deployment package to the object storage. When releasing a version, the deployment package of the same service only needs to be backed up and uploaded once. Servers in all regions can access and download the service deployment package in an encrypted manner, saving storage space.

[0019] Step 5: Use automation tools to batch execute release commands on the management server. After receiving the command, the target server will automatically complete a series of operations such as comparing configurations, loading new configurations, comparing deployment package versions, downloading and replacing new version packages, and stopping and restarting services according to the contents of the execution file.

[0020] Step 6: During the deployment process, the monitoring system will continuously detect the service. If any problem occurs during the release process, an alarm will be prompted to notify the corresponding operation and maintenance personnel to handle it;

[0021] Step 7: Verify whether the service release is successful and submit the result.

[0022] The hybrid cloud automated operation and maintenance publishing system and its operation method proposed by the present invention have the following beneficial effects:

[0023] 1. The present invention uses a unified system service management for service management. Before the service is started, all software services and module services are uniformly registered as system services, and their own command startup mode is abandoned. Whether it is starting, stopping, checking service status, etc., unified system commands are used to perform operations, making operation and maintenance management more standardized. At the same time, deployment operations are unified, reducing the occurrence of manual memory commands and manual execution errors. In addition, the system service management mode also supports the startup of services in parallel, which significantly improves the startup efficiency;

[0024] 2. In terms of release management, the present invention performs automated process storage for the release process. When releasing, all release actions can be completed by executing the corresponding automated release file. The storage process includes a series of operations such as release environment monitoring, system service registration, configuration file and deployment package verification, downloading new configuration files and deployment packages, replacing new versions, and restarting services. Even if the command is executed incorrectly at ordinary times, the new configuration and deployment package are not detected in the verification step, and the service restart operation will not be triggered, thereby improving security. At the same time, in the face of business expansion and module addition, only the corresponding configuration and release files need to be added to achieve dynamic upgrades;

[0025] 3. The present invention unifies the configuration centers, object storage, and database execution platforms between data centers / across countries and continents, uses regional labels for differentiation, ensures data consistency of the same modules in different regions, saves deployment resources in different regions, and unifies operations during the deployment process to reduce repetitive work. In the case of multiple regional data centers and hybrid clouds, only one set of configuration center, object storage, and database execution platform needs to be deployed. All regional data centers will pull configuration and deployment packages from the same configuration center and object storage. When the regional data center is dynamically expanded, only the configuration of the newly added region needs to be added to the configuration center, and the changes are very flexible.

[0026] 4. During the publishing process, the present invention uses a combination mode in which the management server sends commands in batches and the target server automatically pulls and executes tasks. During the initial deployment, the target server will cache the automated deployment execution program files locally, and the management server only sends execution commands. The target service executes the deployment program files and automatically obtains the latest files from the configuration center and object storage, alleviating the operating pressure of the management server. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 The present invention is an automated publishing flow chart. DETAILED DESCRIPTION

[0028] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0029] For examples, see Figure 1The present invention provides a technical solution: a hybrid cloud automated operation and maintenance publishing system, including: a main management center, service and business modules, a configuration center, an object storage space and a database platform. A regional data center is selected as the main management center. In addition to business functions, the main management center is also used to undertake automated tool management, automated release file management, release package backup management and operation and maintenance functions, create automated release execution program files for various services and business modules, and the file content includes but is not limited to release environment detection, service system registration, configuration file and deployment package verification, configuration loading, deployment package acquisition, service start and stop, and write individual files according to the service type, configuration file format, and startup parameters of the business module. Personalized content, the same business module uses the same release file regardless of the region. When the main management center automatically releases file updates, other regional computer rooms will automatically obtain the latest release file and execute the release task according to the latest file content. Files can be increased or decreased according to business adjustments to achieve dynamic management; establish a unified configuration center, deploy object storage space, and database platform, create service configuration items in the configuration center, establish a classification directory in the object storage, and create a database connection on the database platform for executing SQL statements; create roles and user accounts in the configuration center and database platform, set up personnel groups, and assign different permissions to the configuration center and database platform to achieve decentralized management.

[0030] An operating method of a hybrid cloud automated operation and maintenance publishing system comprises the following steps:

[0031] Step 1: When releasing for the first time, you need to create service configuration items in the configuration center. They are uniformly named after the service module, and different regions are distinguished by regional labels. When releasing versions on a daily basis, relevant development or configuration personnel will make corresponding configuration modifications, and operation and maintenance personnel will review and release them;

[0032] Step 2: Establish the corresponding database connection of the service on the database platform, create users and assign different permissions. When publishing, the relevant developers submit the SQL to be executed, and the operation and maintenance personnel review and execute the SQL;

[0033] Step 3: When publishing for the first time, you need to create an execution management file for the corresponding service in the main management computer room. You can use it directly in subsequent releases or modify it accordingly according to your needs.

[0034] Step 4: Upload the corresponding service module deployment package to the object storage. When releasing a version, the deployment package of the same service only needs to be backed up and uploaded once. Servers in all regions can access and download the service deployment package in an encrypted manner, saving storage space.

[0035] Step 5: Use automation tools to batch execute release commands on the management server. After receiving the command, the target server will automatically complete a series of operations such as comparing configurations, loading new configurations, comparing deployment package versions, downloading and replacing new version packages, and stopping and restarting services according to the contents of the execution file.

[0036] Step 6: During the deployment process, the monitoring system will continuously detect the service. If any problem occurs during the release process, an alarm will be prompted to notify the corresponding operation and maintenance personnel to handle it;

[0037] Step 7: Verify whether the service release is successful and submit the result.

[0038] The present invention is based on a configuration center, a database platform, and object storage, combined with automation tools such as batch operations and process storage, and is applicable to real business scenarios in multiple regions and different public clouds / private clouds. It simplifies manual operations, realizes an operation and maintenance platform with automated deployment, and realizes operation and maintenance standardization and dynamic expansion.

[0039] The multi-region data centers use the same configuration center, database platform, and object storage to ensure data consistency. The configuration center has unified configuration management and uses regional labels as a distinction. All services pull configurations from the configuration center without having to modify them individually. The database platform is managed by decentralized authority and rules, and there is no need to log in to the database to operate, which makes the database security more secure. Object storage is used to manage release packages. Deployment packages of the same service in different regions do not need to be backed up repeatedly, which reduces manual work and saves storage resources.

[0040] The release process of each service is pre-stored in the execution file. When releasing, running the execution file can automatically implement a series of operations such as stopping the service, replacing the version package, loading the configuration, restarting the service, etc. The release process is automatic, unified, and standardized. Batch tools are used when deploying multiple servers. At the same time, the "push&pull" combination mode is used to reduce the performance pressure of the management host.

[0041] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A hybrid cloud automated operation and maintenance publishing system, characterized in that: include: Main management center: select a regional data center as the main management center; Service and business modules: Create automated release execution program files for various services and business modules. The file content includes release environment detection, systematized service registration, configuration file and deployment package verification, configuration loading, deployment package acquisition, service start and stop. Customized content is written based on the service type, configuration file format, and startup parameters of the business module. The same business module uses the same release file regardless of region. Configuration center, object storage space and database platform: Establish a unified configuration center, deploy object storage space and database platform, create service configuration items in the configuration center, establish a classification directory in the object storage, and create a database connection on the database platform for executing SQL statements; Creating roles and user accounts in the configuration center and database platform; In addition to business functions, the main management center is also used to undertake automation tool management, automation release file management, release package backup management and maintenance operations; When the main management center automatically publishes file updates, other regional computer rooms will automatically obtain the latest release files and execute release tasks according to the latest file content. Files are increased or decreased according to business adjustments to achieve dynamic management; The roles and user accounts are used to set up personnel groups, assign different permissions to the configuration center and database platform, and manage them in a decentralized manner. Step 1: When releasing for the first time, you need to create service configuration items in the configuration center. They are uniformly named after the service module, and different regions are distinguished by regional labels. When releasing versions on a daily basis, relevant development or configuration personnel will make corresponding configuration modifications, and operation and maintenance personnel will review and release them; Step 2: Establish the corresponding database connection of the service on the database platform, create users and assign different permissions. When publishing, the relevant developers submit the SQL to be executed, and the operation and maintenance personnel review and execute the SQL; Step 3: When publishing for the first time, you need to create an execution management file for the corresponding service in the main management computer room. You can use it directly in subsequent releases or modify it accordingly according to your needs. Step 4: Upload the corresponding service module deployment package to the object storage. When releasing a version, the deployment package of the same service only needs to be backed up and uploaded once. Servers in all regions access and download the service deployment package in an encrypted manner, saving storage space. Step 5: Use automation tools to batch execute release commands on the management server. After receiving the command, the target server will automatically complete a series of operations such as comparing configurations, loading new configurations, comparing deployment package versions, downloading and replacing new version packages, and stopping and restarting services according to the contents of the execution file. Step 6: During the deployment process, the monitoring system will continuously detect the service. If any problem occurs during the release process, an alarm will be prompted to notify the corresponding operation and maintenance personnel to handle it; Step 7: Verify whether the service release is successful and submit the result.

Images