A management method and management system for automated operation and maintenance deployment linkage work order tasks

Abstract

A management method and management system for automated operation and maintenance deployment linkage work order tasks, which relate to the field of automated operation and maintenance deployment of mainstream software systems. To solve the defects of the existing system upgrade and deployment that require manual deployment, lack deployment management approval, cannot retain online records, and cannot match complex deployment scenarios, an upgrade package of the program is imported, the upgrade content in the upgrade package is automatically parsed, archived and managed, and presented in a form; according to the upgrade content, combined with the work order task and approval status, automatically download and call relevant interfaces of the server or cloud platform to complete relevant backups and upgrades on the specified target server or database; archive, save and display the execution process and results of the backup and upgrade in the system, and form a written report. The present invention is mainly used for the automated operation and maintenance deployment of system upgrades.

Description

Technical Field

[0001] The present invention relates to the field of mainstream software system operation and maintenance deployment automation, and in particular to a management method and a management system for automated operation and maintenance deployment linkage work order tasks. Background Art

[0002] With the continuous development of SaaS business, the speed of business iteration and upgrading is getting faster and faster. In addition, the current information system construction tends to adopt the "middle platform + microservice" model. The high frequency of system upgrades brings huge pressure to daily operation and maintenance, which is mainly reflected in the following aspects:

[0003] a. Low deployment efficiency: Traditional deployment usually requires manual execution of a series of complex tasks, including configuring the environment, installing software, setting parameters, etc. These tasks are not only time-consuming but also prone to errors, resulting in low deployment efficiency.

[0004] b. The deployment process is prone to errors: Since traditional deployment involves a lot of manual operations, it is prone to configuration errors, missing steps, etc. These errors may cause system instability, malfunction, and even security risks.

[0005] c. Poor maintainability: Although traditionally deployed systems provide deployment specifications and documentation records, statistics and traceability are not convenient, and the comparison during subsequent maintenance and upgrades is poor, which increases maintenance costs.

[0006] d. A lot of repetitive work: Traditional deployment is strictly carried out according to deployment specifications, and many steps and operations need to be repeated every time deployment is carried out, which adds extra unnecessary workload and time cost.

[0007] The current mainstream solution is to apply the technical concept of DevOps, and most of them use the gitlab+jenkins model. It lacks a management approval process, cannot retain online records, and does not meet the needs of business scenarios. Although pure work order management systems can retain online approval records, they cannot match the needs of complex automated operation and maintenance deployment scenarios, and cannot implement a process line that matches the test environment and formal environment of the business scenario with multiple release process solutions.

[0008] Therefore, there is a need for a management method and management system for automated operation and maintenance deployment that can integrate work order management with automated operation and maintenance deployment and realize full process control and archiving auditing. Summary of the invention

[0009] In order to solve the defects of the existing system upgrade deployment that requires manual deployment, lacks deployment management approval, cannot retain online records, and cannot match complex deployment scenarios, the present invention provides a management method and management system for automated operation and maintenance deployment linked work order tasks that can integrate work order management with automated operation and maintenance deployment and realize full process control and archiving audit.

[0010] The present invention provides a method for managing automated operation and maintenance deployment linked work order tasks, comprising the following steps:

[0011] S1. Import the upgrade package of the program, automatically parse the upgrade content in the upgrade package, archive and manage it, and display it in a form;

[0012] S2. According to the upgrade content, combined with the work order tasks and approval status, automatically download and call the server or cloud platform related interface to complete the relevant backup and upgrade on the designated target server or database; archive and display the execution process and results of the backup and upgrade in the system, and form a written report.

[0013] Furthermore: Before S1, it is necessary to create a maintenance plan and create multiple small batches according to different modules, with multiple versions bound to each small batch.

[0014] Further: in S2, the work order task includes associated small batches, and each of the associated small batches is associated with multiple different versions according to the corresponding module.

[0015] Further: in S2, the approval status includes approving the associated small batch and retaining and archiving the approval information, and the approval status includes the approval process, approval opinion and / or approver.

[0016] Furthermore: in S2, it also includes releasing the approved small batches to the test environment for testing, completing the test by maintaining the corresponding test items, and generating a test report.

[0017] Further: if the test of the test environment passes, the maintenance plan is submitted for approval; if the test of the test environment fails, the calibration replacement upgrade package is released and a new upgrade package is re-imported.

[0018] Furthermore: if the maintenance plan is approved, it will be released to the official environment for secondary testing; if the maintenance plan is not approved, the release will be suspended.

[0019] Furthermore: If the test of the formal environment passes, the relevant backup and upgrade are completed, and the execution process and results of the backup and upgrade are archived, stored and displayed in the system, and a written report is formed; if the test of the formal environment fails, the version is rolled back.

[0020] The management system of the automated operation and maintenance deployment linkage work order task described in the present invention comprises an upgrade package import module, a maintenance plan creation module, a small batch creation module, a version binding module, an approval module, a release module, a test module and a report generation module;

[0021] The upgrade package import module is used to import the upgrade package and automatically parse the content in the upgrade package, and display the information in a form for subsequent release and upgrade of the release module;

[0022] The maintenance plan creation module is used to maintain the entire process and generate the final maintenance report;

[0023] The small batch creation module is used to associate a maintenance plan with multiple small batches, and associate each small batch with multiple versions, thereby realizing maintenance management of tasks;

[0024] The version binding module is used to bind the version to a small batch to facilitate the use of subsequent release modules;

[0025] The approval module is used to approve each upgrade operation according to business needs;

[0026] The release module is used for version release;

[0027] The test module is used to test the released small batch and generate a test report;

[0028] The report generation module is used to generate test reports and maintenance reports to facilitate later review and audit.

[0029] The beneficial effects of the present invention are:

[0030] The management method and management system of the automated operation and maintenance deployment-linked work order tasks described in the present invention can achieve full-process control and archiving auditing by integrating work order management with automated operation and maintenance deployment, further upgrade and practice the CI / CD concept in DevOps, and combine the work content to be upgraded, deployed and released in the system with actual business management and approval, so as to realize the digitalization, standardization and process-based creation of all business scenarios of system operation and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 It is a flow chart of the automated operation and maintenance deployment method of the present invention;

[0032] Figure 2 It is a schematic diagram of the technical architecture of the present invention;

[0033] Figure 3 This is a schematic diagram of importing the upgrade package for a business expansion case;

[0034] Figure 4This is a schematic diagram of the basic version information after the upgrade package is parsed;

[0035] Figure 5 This is the interface diagram of the micro-application TAR package;

[0036] Figure 6 It is the interface diagram of the microservice image;

[0037] Figure 7 This is the interface diagram of the SQL script;

[0038] Figure 8 It is a schematic diagram of the small batch related maintenance plan;

[0039] Fig. 9 is to create a maintenance plan diagram;

[0040] Fig.10 is to create a small batch of schematic diagrams;

[0041] Fig.11 It is a small batch binding maintenance plan;

[0042] Fig.12 is a schematic diagram of associating versions and mini-batches;

[0043] Fig.13 It is a schematic diagram of small batch approval records;

[0044] Fig.14 It is a small batch approval flow chart;

[0045] Fig.15 It is a one-click publishing schematic diagram;

[0046] Fig.16 This is the interface diagram of the release log;

[0047] Fig.17 It is a test report maintenance diagram;

[0048] Fig.18 It is a schematic diagram of maintenance test items;

[0049] Fig.19 It is a test report approval diagram;

[0050] Fig. 20 It is a schematic diagram for maintenance plan approval;

[0051] Fig.21 It is a schematic diagram for exporting maintenance reports. DETAILED DESCRIPTION

[0052] The following are only preferred specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a technician familiar with the technical field within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. The embodiments described below are only used to explain the present invention and cannot be interpreted as limitations on the present invention. The protection scope of the present invention should be based on the protection scope of the claims. The embodiments of the present invention are described in detail below. In order to facilitate the description of the present invention and simplify the description, the technical terms used in the specification of the present invention should be interpreted in a broad sense, including but not limited to conventional replacement schemes not mentioned in this application, and also including direct implementation methods and indirect implementation methods.

[0053] Example 1

[0054] Combination Figure 1 and Figure 2 This embodiment describes a method for managing automated operation and maintenance deployment linkage work order tasks, including the following steps:

[0055] S1. Reference Figure 3 , manually import the version upgrade package used to parse different business modules, automatically parse the content in the archived upgrade package, extract the required key information for integration, and divide the content into: microservices, microapplications, SQL scripts and other information, and display them in the form of a form; if the upgrade package lacks corresponding information, the corresponding microservice, microapplication and / or SQL script form will be left blank; through the relevant management approval of the business verification environment, including but not limited to version management, release management and approval management, after approval, conduct electricity fee calculation environment testing, and maintain archived test reports and problems encountered in the test and their solutions.

[0056] In the production environment, the version that has passed the test in the test environment is released with one click, including front-end files, report files, microservices, etc. After the release is completed, it will pass the final round of testing and approval confirmation to ensure the normal service of the production environment. All approval and release operations can be associated with mobile application notifications, including: SMS notifications, email notifications, DingTalk notifications, WeChat notifications, etc. The entire process digitizes, standardizes and automates the work links through the work order process.

[0057] The entire work process is digitally standardized and automated through the work order process, including version upgrade content, upgrade targets, personnel, business organization, approval control, release control, and archiving audit. It also incorporates the characteristics of domestic e-government, OA and other business types, and has the function of managing activities and activity time limits for multiple work calendars. The visual process modeling tool is integrated in the UEP-STUDIO development environment, providing a drag-and-drop business process definition tool.

[0058] Reference Figure 3 The first step to implement the fully automatic operation and maintenance deployment management method includes: importing the upgrade packages of different business modules in Version Control → Version Management. In the case, the business expansion (hereinafter referred to as business expansion) module is selected as an implementation case example. After the upgrade zip package is imported, refer to Figure 4 , you can see that the key contents contained in the upgrade package, such as detailed information, microservice information, microapplication information, SQL scripts, etc., have been parsed into the system (in order to ensure data security, the upgrade package used in this case is a confidential test package).

[0059] Table 1 Original table of upgrade package

[0060]

[0061] For comparison, refer to Table 1. Figure 5 , Figure 6 and Figure 7 Calibration, parsed information can be manually maintained and modified to ensure accuracy, and after the imported information is saved, it can still be viewed through the upgraded content tag. Microservices is a software architecture style, micro-applications are a form of mobile applications, and SQL scripts are scripting languages ​​used for database operations.

[0062] The upgrade package import includes different types of compressed packages such as zip and rar. The content in the automatic parsing archive upgrade package includes but is not limited to version number, business application name, release environment, version type, release range, urgency, previous version, etc. The form display includes modification and archiving of the displayed content. The version number is used to determine the binding relationship of small batches, and determine the upgrade version based on the version number. The module name is used to distinguish different small batches, the release environment is used to determine whether it is released to the test or production environment, the version type is used to indicate whether the service version is an iterative version or a newly added initialization version, the release range is used to indicate the network province of the release, the urgency is used to indicate the urgency of this version release, if the urgency is high, it will be expedited for approval and release, and the previous version is used to verify version dependencies. If the current online version is less than the dependent version, a prompt will be given before release.

[0063] S2. Automatically download and call the cloud platform interface to perform service backup and upgrade based on the microservice and microapplication addresses obtained through analysis, and display the results in the system and form a written report; specifically, it includes:

[0064] The approval status includes approving the associated small batch and retaining and archiving the approval information. The approval status includes the approval process, approval opinions and / or approvers.

[0065] It also includes releasing approved small batches to the test environment for testing, completing the testing by maintaining the corresponding test items, and generating a test report.

[0066] If the test environment passes the test, the maintenance plan is submitted for approval; if the test environment fails the test, the upgrade package is replaced by issuing a calibration, and a new upgrade package is re-imported. The issuing calibration means using the issuing calibration module to send the information that the current upgrade package has a test failure to the demander, and instruct the demander to replace the new upgrade package for upgrading.

[0067] If the maintenance plan is approved, it will be released to the official environment for secondary testing; if the maintenance plan is not approved, the release will be suspended.

[0068] If the test of the formal environment passes, the relevant backup and upgrade will be completed, and the execution process and results of the backup and upgrade will be archived, stored and displayed in the system, and a written report will be formed; if the test of the formal environment fails, the version will be rolled back.

[0069] Parse the word file and Excel file in the upgrade package, obtain the corresponding image address, tar package address, SQL script, service configuration information, download the image to the local computer, re-tag the modified image and upload it to the cloud image warehouse for release; after the tar package is downloaded to the local computer, the old version will be backed up, and then the new version will be released to the server. The SQL script will be executed in the corresponding library and the execution result will be returned. The service configuration information will be modified based on the original file. Version rollback refers to the process of restoring the software, database or system to a previous stable version or state. Rollback is to roll back the service configuration by calling the cloud platform interface. The tar package is a file format generated by a common file compression and packaging tool in Linux and Unix-like systems. The suffix of the tar package file is usually ".tar", which can be used in combination with different compression algorithms to generate files in formats such as ".tar.gz" or ".tar.bz2".

[0070] The process module is used to maintain and manage the work order process and task management. At the same time, it incorporates the characteristic requirements of domestic e-government, OA and other business types. It has the function of managing the activities and activity time limits of multiple work calendars and supports various process events. The visual process modeling tool is integrated in the development environment (such as the UEP-Studio development environment, that is, an integrated development environment or operating platform), which provides a drag-and-drop business process definition tool. Specifically, it includes:

[0071] The version submission process binds the version in the upgrade package to the process and then approves it. The approval process can be customized through the process module. The test report process maintains the status of related test items after the test environment is released, and integrates and archives them into a test report for approval. The approval process can be customized through the process module. The maintenance plan process submits the maintenance plan for approval after the test environment test is completed and approved. The maintenance plan mainly includes the version number, test environment test results and the person in charge. The approval process can be customized through the process module.

[0072] Reference Figure 8 The version management and maintenance method described in this embodiment maintains multiple small batches through maintenance plans (i.e. large batches), and maintains multiple versions under small batches. The version is the smallest unit in management. In the release process, multiple versions are released in batches automatically by releasing small batches, and the entire release process is displayed in the echo log. The release status of each version can also be viewed through the release log later, and the release information of all versions will be archived and retained in the system.

[0073] Reference Fig. 9 , in Automation Deployment → Maintenance Plan, create a maintenance plan named Patent Test (large batch) according to the form information, refer to Fig.10 , in Automatic Deployment → Version Submission, find the maintenance plan (large batch) you just created. According to the form content, add a small batch named Patent Test Business Expansion Batch below. After selecting a module for each small batch, only the version of the corresponding module can be bound below. Multiple small batches can be maintained under one maintenance plan (large batch). Refer to Fig.11 , mini-batches of 3 different modules are created.

[0074] After clicking the version information, associate the version of the corresponding module with the small batch. Each small batch can be associated with multiple different versions. Fig.12 , associated 4 different versions to the small batch, and then submitted the small batch for approval, refer to Fig.13 and Fig.14 All approval processes, approval opinions, and approvers will be archived in the system.

[0075] Reference Fig.15 When the approval status of a small batch is archived, you can publish it with one click. The published content is all versions under the current small batch. Release it according to the small batch. Even if there are other small batches under the large batch that have not been submitted for approval, they will not affect the release of other approved small batches. This release did not test the environment. Find the small batch that has passed the approval under the corresponding maintenance plan (large batch) in Automatic Deployment → One-click Release → One-click Release, and click Release to publish all versions under the small batch with one click. Refer to Fig.16, display the version release log, or click the release log to view the release information of all content.

[0076] Reference Fig.17 , find the corresponding maintenance plan (large batch) in Automation Deployment → Test Report → Test Report Maintenance, and you can see the small batches that have been released. Fig.18 , by maintaining the test items, manually selecting a new mandatory checklist or a new version checklist, and maintaining the test results in the system; refer to Fig.19 The operator checks the test results of all test items, manually maintains the test item content, and submits the test items for approval. After approval, click Test Pass to complete the test phase. After completion, the test report can be exported.

[0077] Reference Fig. 20 After the test phase is completed, go to Automated Deployment → Maintenance Plan, find the corresponding maintenance plan, and click Close Submission. This means that this maintenance plan (large batch) has passed the verification of the test environment and is sealed. You can no longer add any small batches or versions to this maintenance plan (large batch). Note that if there are unreleased or untested small batches in the maintenance plan (large batch), this large batch cannot be closed.

[0078] After the maintenance plan (large batch) is closed and submitted, it needs to be submitted for approval. The approval here means the official start of the process of releasing to the formal environment. All verified versions in the test environment are released to the formal environment with one click. After passing the approval, click Release to release the maintenance plan (large batch) to the formal environment.

[0079] Reference Fig.21 The approval process, test reports, test items and maintenance reports of all processes will be archived in the system for subsequent sorting, statistics and review.

[0080] Example 2

[0081] The present embodiment is explained in conjunction with Example 1. The present embodiment discloses a management system for automated operation and maintenance deployment and linkage work order tasks. Based on an integrated cloud platform and work scenarios, the project system is divided into four layers: a front-end web layer, a business service layer, a PaaS (Platform as a Service), and an IaaS (Infrastructure as a Service), with reference to the Pace-Layered Application Strategy architecture system. The front end is the entrance for user interaction, while the business service layer is the core for processing user requests and business logic; the front end realizes interaction with the back-end data by calling the API or interface of the business service layer; the business service layer is located between the front end and the back end, and is responsible for processing specific business logic and data operations; the PaaS layer is above the IaaS layer, and provides developers with a complete application development and deployment environment; the IaaS layer is the basic layer of cloud computing services, which provides virtualization services for basic IT resources such as computing, storage, network, and security.

[0082] The fully automatic operation and maintenance deployment management system integrates elements such as security protection, operation and maintenance monitoring, application construction, and management requirements to jointly realize the method architecture of automated operation and maintenance deployment and work order management, and supports the technical implementation of applications and data. The fully automatic operation and maintenance deployment management system is divided into 4 modules:

[0083] Among them, the overall operation and maintenance overview module is a quantitative display of automated operation and maintenance deployment and work order management methods, which displays automated release, management, approval and other functions and release results in a transparent, digital and standardized manner;

[0084] The release management module is the main implementation module of the method. It parses the contents of the upgrade package to obtain the required key information, and then calls the cloud platform interface to achieve automatic one-click release, upgrade, and backup.

[0085] The operation and maintenance management module is the embodiment of method work order management, which unifies the digital and standardized management of the processes, approvals, reports and other contents generated in release management;

[0086] The basic information maintenance module is the basic organizational information for ensuring the automatic operation and maintenance deployment management method.

[0087] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention.

Claims

1. A management method for automated operation and maintenance deployment linkage work order tasks, characterized in that: The steps include: S1. Import the upgrade package of the program, automatically parse the upgrade content in the upgrade package, archive and manage it, and display it in a form; before S1, it is also necessary to create a maintenance plan, that is, a large batch, and create multiple small batches according to different modules; S2. According to the upgrade content, combined with the work order task and approval status, automatically download and call the server or cloud platform related interface to complete the relevant backup and upgrade on the designated target server or database; archive and display the execution process and results of the backup and upgrade in the system, and form a written report; The approval status includes submitting the maintenance plan for approval and retaining the approval information for archiving; If the maintenance plan is approved, the official environment will be released for testing; If the maintenance plan is not approved, the release will be suspended; If the test of the formal environment passes, the relevant backup and upgrade will be completed, and the execution process and results of the backup and upgrade will be archived, stored and displayed in the system, and a written report will be formed; if the test of the formal environment fails, the version will be rolled back.

2. A method for managing automated operation and maintenance deployment linked work order tasks according to claim 1, characterized in that: Multiple versions are bundled under each small batch.

3. A method for managing automated operation and maintenance deployment linked work order tasks according to claim 1, characterized in that: In S2, the work order task includes associated small batches, and each of the associated small batches is associated with multiple different versions according to the corresponding module.

4. A management method for automated operation and maintenance deployment linkage work order tasks according to claim 3, characterized in that: In S2, the approval status includes the approval process, approval opinion and / or approver.

5. A method for managing automated operation and maintenance deployment linkage work order tasks according to claim 2, characterized in that: In S2, it also includes releasing the approved small batches to the test environment for testing, completing the test by maintaining the corresponding test items, and generating a test report.

6. A method for managing automated operation and maintenance deployment linked work order tasks according to claim 5, characterized in that: If the test of the test environment passes, the maintenance plan is submitted for approval; if the test of the test environment fails, the calibration replacement upgrade package is released and a new upgrade package is re-imported.

7. A management system based on the management method of the automated operation and maintenance deployment linkage work order task according to any one of claims 1 to 6, characterized in that: It includes upgrade package import module, maintenance plan creation module, small batch creation module, version binding module, approval module, release module, test module and report generation module; The upgrade package import module is used to import the upgrade package and automatically parse the content in the upgrade package, and display the information in a form for subsequent release and upgrade of the release module; The maintenance plan creation module is used to maintain the entire process and generate the final maintenance report; The small batch creation module is used to associate a maintenance plan with multiple small batches, and associate each small batch with multiple versions, thereby realizing maintenance management of tasks; The version binding module is used to bind the version to a small batch to facilitate the use of subsequent release modules; The approval module is used to approve each upgrade operation according to business needs; The release module is used for version release; The test module is used to test the released small batch and generate a test report; The report generation module is used to generate test reports and maintenance reports to facilitate later review and audit.

Images