Application operation and maintenance method and device, equipment, storage medium and program product

By building an application operation and maintenance view and executing operation and maintenance verification strategies, the problems of fault location and operation and maintenance management in data center operation and maintenance management are solved, rapid operation and maintenance and risk control are achieved, and predictability and automation of operation and maintenance management are improved. level.

CN119065794APending Publication Date: 2024-12-03CHINA CONSTRUCTION BANK +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411285976.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-13
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In data center operation and maintenance management with large data scale, many business scenarios and complex relationships between systems, it is difficult for existing technologies to quickly locate and deal with faults, the risk of operation and maintenance management is high, the barriers between automation tools are obvious, and the overall operation and maintenance view is lacking Unified operation and maintenance strategies.

Method used

By standardizing the target application objects and deployment objects based on the technology stack, building an application operation and maintenance view, executing operation and maintenance verification strategies for each stage before, during and after operation, updating operation and maintenance status information, and achieving rapid operation and maintenance and failures Disposal and improve the ability to manage and control risks in automated operation and maintenance.

Benefits of technology

It realizes layered sorting and operation and maintenance status information display starting from the target application object, quickly locate faults and operation and maintenance scenarios, optimizes application operation and maintenance views, improves the risk management capabilities of automated operation and maintenance and predictability of target applications, and realizes Safety and standardized automated operation and maintenance management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119065794A_ABST
    Figure CN119065794A_ABST
Patent Text Reader

Abstract

The invention provides an application operation and maintenance method and device, equipment, a storage medium and a program product, and can be applied to the technical field of computers. The method comprises the steps that based on a technical stack target application object and a deployment object associated with the target application object, an application operation and maintenance view of a target application is determined for standardization, technical stacks comprise a traditional virtual machine technical stack, a container technical stack and a container mixed technical stack, the target application object is used for identifying the target application, and the deployment object is used for deploying the target application; the application operation and maintenance view represents a hierarchical structure diagram formed by a physical logic relationship between a target application object and a plurality of deployment objects, and the target application object and the deployment objects are bound with operation and maintenance state information respectively; executing the operation and maintenance check strategies corresponding to the target application in the pre-operation stage, the middle operation stage and the post-operation stage to obtain operation and maintenance check results; and updating operation and maintenance state information in the application operation and maintenance view based on the operation and maintenance check result.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and more specifically, to an application operation and maintenance method and apparatus, equipment, storage medium, and program product. Background Art

[0002] With the development of the information age, technology is also changing rapidly. Large commercial banks are also facing increasing challenges in the changes in business and technology. The goal of data center operation and maintenance is to ensure business stability and operation. When an emergency occurs, the problem can be quickly located and the response to restore business can be handled as soon as possible. However, with the increasing scale of data, the increasing number of business scenarios, the increasing complexity of the connections and dependencies between systems, and the increasing diversity of technology stacks, data center operation and maintenance management is becoming more and more difficult.

[0003] In the process of realizing the concept of the present disclosure, the inventors found that there are at least the following problems in the related technology: the current operation and maintenance management based on the dimensions of infrastructure, platform, virtualization layer, etc. cannot quickly handle and locate, and the operation and maintenance control risk is relatively high. Summary of the invention

[0004] In view of this, the present disclosure provides an application operation and maintenance method and apparatus, equipment, storage medium and program product.

[0005] One aspect of the present disclosure provides an application operation and maintenance method, including: standardizing a target application object and a deployment object associated with the target application object based on a technology stack, and determining an application operation and maintenance view of the target application, wherein the technology stack includes a traditional virtual machine technology stack, a container technology stack, and a container hybrid technology stack, and the container hybrid technology stack performs object hybrid deployment based on an object mapping relationship between the traditional virtual machine technology stack and the container technology stack, the target application object is used to identify the target application, and the application operation and maintenance view represents a hierarchical structure diagram composed of a physical and logical relationship between the target application object and multiple deployment objects, and the target application object and the deployment object are each bound with operation and maintenance status information; executing the operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage, respectively, to obtain the operation and maintenance verification results; and updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance verification results.

[0006] According to an embodiment of the present disclosure, the operation and maintenance verification strategy corresponding to the post-operation stage includes a fault verification strategy, a business transaction verification strategy, and a log verification strategy; wherein, the operation and maintenance verification strategy corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage is executed, and the operation and maintenance verification results are obtained, including:

[0007] Execute the fault verification strategy to obtain the fault verification result; execute the business transaction verification strategy to obtain the transaction status verification result; execute the log verification strategy to obtain the log status verification result, among which the operation and maintenance verification result includes the fault verification result, the transaction status verification result, and the log status verification result.

[0008] According to an embodiment of the present disclosure, the fault verification result includes target fault scenario information, and the operation and maintenance status information includes operation and maintenance scenario information, transaction status information, log status information, and running status information; wherein, updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance verification result includes:

[0009] Based on the scenario mapping relationship, determine the target operation and maintenance scenario information corresponding to the target fault scenario information, wherein the scenario mapping relationship represents the correspondence between the fault scenario and the operation and maintenance scenario; in the application operation and maintenance view, determine the first deployment object corresponding to the target operation and maintenance scenario information; perform a fault handling operation on the first deployment object to obtain a handling result; update the running status information of the first deployment object according to the handling result; update the transaction status information and log status information corresponding to the target application object according to the transaction status check result and the log status check result.

[0010] According to an embodiment of the present disclosure, the deployment object includes a space object, an application system object, a deployment unit object, a container service object, a container collection object, and a container object; wherein, based on the technology stack, the target application object and the deployment object associated with the target application object are standardized to determine the application operation and maintenance view of the target application, including:

[0011] Based on the container technology stack, the target application objects, space objects, application system objects, deployment unit objects, container service objects, container collection objects, and container objects are standardized to determine the application operation and maintenance view of the target application.

[0012] According to an embodiment of the present disclosure, the target application object and the deployment object associated with the target application object are standardized based on the technology stack to determine the application operation and maintenance view of the target application, and further includes:

[0013] When the deployment objects include virtual operating system objects and application user objects, the target application objects, deployment unit objects, virtual operating system objects, and application user objects are standardized based on the traditional virtual machine technology stack to determine the application operation and maintenance view of the target application.

[0014] According to an embodiment of the present disclosure, the operation and maintenance check strategy corresponding to the pre-operation stage includes a system status check strategy and a test check strategy; wherein, the operation and maintenance check strategy corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage is executed to obtain the operation and maintenance check result, and also includes:

[0015] Execute the system status check strategy on the system where the target application is located to obtain the system status check result that indicates the check has passed, so that the target application can conduct business transactions; execute the test check strategy to obtain the test check result, where the operation and maintenance check result includes the system status check result and the test check result.

[0016] According to an embodiment of the present disclosure, the operation and maintenance status information also includes test status information; wherein, updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance check result also includes:

[0017] Based on the test verification results, determine the test objects that have not completed the test from the target application objects and deployment objects; test the test objects according to the test strategy and test function script to obtain the test results; based on the test results and the verification results that represent the completed tests in the test verification results, update the test status information corresponding to the target application objects and deployment objects.

[0018] According to an embodiment of the present disclosure, the operation and maintenance check strategy corresponding to the running stage includes a user authority check strategy and an execution status check strategy; wherein, the operation and maintenance check strategy corresponding to the target application in the pre-running stage, the running stage, and the post-running stage is executed to obtain the operation and maintenance check result, which also includes:

[0019] Execute the user authority check strategy to obtain the authority check result indicating that the check has passed, so that the application user object on the target application can perform transaction operations; execute the execution status check strategy to obtain the execution check result.

[0020] Another aspect of the present disclosure provides an application operation and maintenance device, including:

[0021] A determination module is used to standardize a target application object and a deployment object associated with the target application object based on a technology stack, and determine an application operation and maintenance view of the target application, wherein the technology stack includes a traditional virtual machine technology stack, a container technology stack, and a container hybrid technology stack, and the container hybrid technology stack performs object hybrid deployment based on an object mapping relationship between the traditional virtual machine technology stack and the container technology stack, and the target application object is used to identify the target application, and the application operation and maintenance view represents a hierarchical structure diagram composed of a physical and logical relationship between a target application object and a plurality of deployment objects, and the target application object and the deployment object are each bound with operation and maintenance status information;

[0022] An execution module is used to execute the operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage, and obtain the operation and maintenance verification results;

[0023] The update module is used to update the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance verification results.

[0024] Another aspect of the present disclosure provides an electronic device, comprising:

[0025] one or more processors;

[0026] a memory for storing one or more programs,

[0027] When one or more programs are executed by one or more processors, the one or more processors implement the above application operation and maintenance method.

[0028] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above application operation and maintenance method when executed.

[0029] Another aspect of the present disclosure provides a computer program product, which includes computer executable instructions, and the instructions are used to implement the above application operation and maintenance method when executed.

[0030] According to the application operation and maintenance method, device, equipment, storage medium and program product provided by the present disclosure, starting from the target application object as the basic perspective, an application operation and maintenance view with a hierarchical structure is constructed according to the deployment object associated with the target application object, and the operation and maintenance inspection strategies corresponding to the target application in the pre-operation stage, the operation stage and the post-operation stage are executed to obtain the operation and maintenance inspection results, and then the operation and maintenance status information in the application operation and maintenance view is updated. Starting from the target application object, the operation and maintenance status information associated with the target application object and each deployment object is displayed layer by layer through hierarchical combing, which can realize rapid operation and maintenance and jump processing such as fault or operation and maintenance scenarios. According to the operation and maintenance inspection results obtained by the target application at different operation stages, the operation and maintenance status information is updated, and the application operation and maintenance view is optimized, which improves the automated operation and maintenance risk management and control capabilities, ensures the predictability of the target application, and realizes safe and standardized automated operation and maintenance management of the target application. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0032] Figure 1 The application scenario of the application operation and maintenance method according to the embodiment of the present disclosure is schematically shown;

[0033] Figure 2 A flowchart of an application operation and maintenance method according to an embodiment of the present disclosure is schematically shown;

[0034] Figure 3 An example schematic diagram schematically shows an object mapping relationship according to an embodiment of the present disclosure;

[0035] Figure 4An example schematic diagram of container hybrid technology stack deployment according to an embodiment of the present disclosure is schematically shown;

[0036] Figure 5 A block diagram schematically shows an application operation and maintenance device according to an embodiment of the present disclosure; and

[0037] Figure 6 A block diagram of an electronic device suitable for implementing an application operation and maintenance method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0038] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0039] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0040] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0041] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0042] In the process of realizing the present disclosure, it is found that with the development of the information age, technology is also changing rapidly. Large commercial banks are also facing increasing challenges in the changes of business and technology. However, with the increasing scale of data, the increasing number of business scenarios, the increasing complexity of the association and dependence between systems, and the increasing diversity of technology stacks, the operation and maintenance management of data centers is becoming more and more difficult. Traditional operation and maintenance staff conduct on-site control, supplemented by automation tools, but still face many problems: there are barriers between automation tools, and the entire process of operation and maintenance from operation and maintenance strategy or script writing, testing to production is not connected, and most of them exist in text form. When a fault occurs, it is impossible to quickly locate the solution according to the test situation and then realize rapid disposal and positioning. At the same time, the root of data operation and maintenance is the application system, and the current operation and maintenance management is divided into dimensions such as infrastructure, platform, virtualization layer, network, storage, and application. There is no application perspective and no overall operation and maintenance view. The script or orchestration definition is standardized, the entry is not unified, the reuse rate is low, and the risk control of automated operation and maintenance needs to be improved.

[0043] In view of this, the embodiments of the present disclosure provide an application operation and maintenance method and apparatus, device, storage medium and program product. The method includes: standardizing the target application object and the deployment object associated with the target application object based on the technology stack, determining the application operation and maintenance view of the target application, wherein the target application object is used to identify the target application, and the application operation and maintenance view represents a hierarchical structure diagram composed of the physical logical relationship between the target application object and multiple deployment objects, and the target application object and the deployment object are each bound with operation and maintenance status information; executing the operation and maintenance inspection strategies corresponding to the target application in the pre-operation stage, the operation stage and the post-operation stage, respectively, to obtain the operation and maintenance inspection results; updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance inspection results.

[0044] It should be noted that the application operation and maintenance method and application operation and maintenance device determined in the present disclosure can be used in the financial field, and can also be used in any field other than the financial field. The application field of the application operation and maintenance method and device determined in the present disclosure is not limited.

[0045] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0046] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0047] Figure 1 The application scenario of the application operation and maintenance method according to the embodiment of the present disclosure is schematically shown.

[0048] like Figure 1 As shown, the system architecture 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104 and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0049] The user may use at least one of the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0050] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0051] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0052] It should be noted that the application operation and maintenance method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the application operation and maintenance device provided in the embodiment of the present disclosure can generally be set in the server 105. The application operation and maintenance method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105. Accordingly, the application operation and maintenance device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105.

[0053] Alternatively, the application operation and maintenance method provided in the embodiment of the present disclosure may also be executed by the first terminal device 101, the second terminal device 102, or the third terminal device 103, or may also be executed by other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103. Accordingly, the application operation and maintenance apparatus provided in the embodiment of the present disclosure may also be provided in the first terminal device 101, the second terminal device 102, or the third terminal device 103, or may be provided in other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103.

[0054] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0055] Figure 2 The flowchart of the application operation and maintenance method according to the embodiment of the present disclosure is schematically shown.

[0056] like Figure 2 As shown, the method 200 includes operations S210 to S230.

[0057] In operation S210 , the target application object and the deployment objects associated with the target application object are standardized based on the technology stack to determine an application operation and maintenance view of the target application.

[0058] According to an embodiment of the present disclosure, a target application is an application developed based on a running software program on a computer or mobile device. For example, the target application may be a front-end application, a back-end application, an intermediate component, a database, etc. The target application object is used to identify the target application and an entry point into the target application.

[0059] According to an embodiment of the present disclosure, the deployment object associated with the target application object represents the operation and maintenance objects corresponding to each link in the operation and maintenance environment that the target application is deployed in. For example, the deployment object may be a deployment unit object, a container object, and the like.

[0060] According to the embodiments of the present disclosure, the application operation and maintenance view represents a hierarchical structure diagram composed of the physical and logical relationships between the target application object and multiple deployment objects. With the target application object corresponding to each target application as the basic layer, the physical and logical relationships between the target application object and the deployment object and the physical and logical relationships between multiple deployment objects are sorted out layer by layer, and the structural layer corresponding to each deployment object is constructed, and the application operation and maintenance view is constructed based on the basic layer and the structural layer.

[0061] For example, taking target application A as an example, the application operation and maintenance view of target application A is a hierarchical structure diagram composed of the target application A object, the deployment object corresponding to the deployment unit where target application A is located, the deployment object corresponding to the container service under the deployment unit, the deployment object corresponding to the container group included in the container service, and the deployment object corresponding to the container included in the container group.

[0062] According to an embodiment of the present disclosure, the application operation and maintenance view can support the integrated management of the traditional virtual machine technology stack, the container hybrid technology stack, and the container technology stack. The traditional technology stack includes the traditional virtual machine technology stack, and the objects between the traditional virtual machine technology stack and the container technology stack correspond to an object mapping relationship, and then the container hybrid technology stack performs hybrid deployment of deployment objects based on the object mapping relationship between the traditional virtual machine technology stack and the container technology stack. The object mapping relationship represents the logical correspondence between the deployment objects defined in the container technology stack and the deployment objects defined in the traditional virtual machine technology stack.

[0063] According to an embodiment of the present disclosure, the target application object and the deployment object in the application operation and maintenance view are each bound with operation and maintenance status information. The operation and maintenance status information of the target application object represents the operating status information of the target application when performing business transaction services or operation and maintenance operations. For example, transaction success rate, number of deployment objects, number of operation and maintenance scenarios. The operation and maintenance status information of the deployment object represents the operating performance information of each deployment object when supporting the target application to carry out business transaction services or operation and maintenance operations. For example, container operation status, thread connection status.

[0064] In operation S220, operation and maintenance check strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage are executed to obtain operation and maintenance check results.

[0065] According to the embodiments of the present disclosure, policy definitions are performed for the target application in the pre-operation stage, the operation stage, and the post-operation stage, and the operation and maintenance inspection policies corresponding to the pre-operation stage, the operation stage, and the post-operation stage are obtained. Policy definitions include definition of orchestration, scripts, and application programming interfaces (APIs).

[0066] According to an embodiment of the present disclosure, the operation and maintenance verification strategy in the pre-operation stage may include the operation and maintenance operation strategy definition, operation and maintenance lifecycle strategy definition, current transaction status verification strategy definition, test status verification strategy definition, etc. of the target application before operation.

[0067] For example, the definition of operation and maintenance strategy includes defining operation scripts or application programming interfaces, and defining the orchestration of operation and maintenance operations in combination with scenarios. The orchestration of operation and maintenance operations includes hybrid orchestration, fallback orchestration, etc. The definition of operation and maintenance lifecycle strategy supports the implementation and guidance of standardization of the entire operation and maintenance lifecycle.

[0068] According to an embodiment of the present disclosure, the operation and maintenance check policy in the running stage may include execution status check policy definitions of the target application object and the deployment object, user authority status check policy definitions, etc.

[0069] According to an embodiment of the present disclosure, the operation and maintenance check strategy in the post-operation stage may include a fault check strategy definition, a feedback status check strategy definition, and the like.

[0070] According to an embodiment of the present disclosure, the server executes the operation and maintenance check strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage, and obtains the operation and maintenance check results corresponding to the pre-operation stage, the operation stage, and the post-operation stage. For example, the operation and maintenance check results in the pre-operation stage may include the result that both the target application object and the deployment object have passed the test.

[0071] In operation S230 , the operation and maintenance status information in the application operation and maintenance view is updated based on the operation and maintenance check result.

[0072] According to the embodiments of the present disclosure, the target application object and the deployment object may generate the latest operation and maintenance verification results in the pre-operation stage, the operation stage, and the post-operation stage, and update the operation and maintenance status information bound to each other according to the operation and maintenance verification results. For example, the updated operation and maintenance status information of the deployment object includes the tested information.

[0073] According to the embodiments of the present disclosure, starting from the target application object, the operation and maintenance status information associated with the target application object and each deployment object is displayed layer by layer through hierarchical combing. The application operation and maintenance view accelerates the integrated management of the traditional virtual machine technology stack, the virtual machine and container hybrid technology stack, and the container technology stack, and can achieve rapid operation and maintenance as well as jump processing such as fault or operation and maintenance scenarios. According to the operation and maintenance inspection results obtained by the target application at different operation stages, the operation and maintenance status information is updated, and the application operation and maintenance view is fed back to optimize, thereby improving the automated operation and maintenance risk management capability, ensuring the predictability of the target application, and realizing safe and standardized automated operation and maintenance management of the target application.

[0074] According to an embodiment of the present disclosure, the operation and maintenance check strategy corresponding to the pre-operation stage includes a system status check strategy and a test check strategy; wherein, the operation and maintenance check strategy corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage is executed to obtain the operation and maintenance check result, and also includes:

[0075] Execute the system status check strategy on the system where the target application is located to obtain the system status check result that indicates the check has passed, so that the target application can conduct business transactions; execute the test check strategy to obtain the test check result, where the operation and maintenance check result includes the system status check result and the test check result.

[0076] According to an embodiment of the present disclosure, the system status verification strategy includes an operation and maintenance verification strategy of a target application before running, an operation and maintenance life cycle verification strategy, a current transaction status verification strategy, and the like.

[0077] According to an embodiment of the present disclosure, the target application performs various application operation and maintenance operations according to the operation and maintenance operation verification strategy. The operation and maintenance operation verification strategy can define scripts according to the application operation and maintenance type in combination with the operation and maintenance scenario or the emergency plan corresponding to the combing scenario. The operation and maintenance operation verification strategy supports script writing recommendations and prompts.

[0078] Table 1 schematically shows an application operation type table according to an embodiment of the present disclosure.

[0079]

[0080] Table 1 includes the types of application operation and maintenance operations and the corresponding operation contents of each application operation and maintenance operation. Application operation and maintenance operation types include emergency operation, health check, application restart, version change, daily operation, green light test, data backup, etc. In different operation and maintenance scenarios, the operation and maintenance operation check strategy is executed as needed to perform application operation and maintenance operations.

[0081] According to the embodiments of the present disclosure, the current transaction status verification strategy includes verifying the transaction time, transaction volume, and the range of devices involved in the transaction, and executing the system status verification strategy on the system where the target application is located to obtain the system status verification result. For example, if the current transaction time is not during the peak period of business transactions, a system status verification result indicating that the verification has passed can be obtained.

[0082] According to an embodiment of the present disclosure, the test verification strategy includes strategies such as detecting the test status of the target application, container, application user, etc., the specific test process, and arranging the reference and synchronization of the test results in the application operation and maintenance view.

[0083] According to an embodiment of the present disclosure, a test verification strategy is executed to obtain a test verification result, which may include a tested result, an untested result, test process information, and the like.

[0084] According to an embodiment of the present disclosure, the operation and maintenance status information also includes test status information; wherein, updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance check result also includes:

[0085] Based on the test verification results, determine the test objects that have not completed the test from the target application objects and deployment objects; test the test objects according to the test strategy and test function script to obtain the test results; based on the test results and the verification results that represent the completed tests in the test verification results, update the test status information corresponding to the target application objects and deployment objects.

[0086] According to an embodiment of the present disclosure, the test verification result may include a tested result and an untested result, and objects to be tested for which the test has not been completed are determined from the target application objects and the deployed objects according to the untested results.

[0087] According to the embodiments of the present disclosure, the operation and maintenance of the test object is shifted left, and the test strategy, test function script (orchestration or API), etc. are pre-placed in the test phase for test verification. If there are any problems with the test, adjustments are made. If there are no problems with the test, the test results are recorded. The operation and maintenance is shifted left to the test environment to achieve online information sharing and integrated operation and maintenance of the target application.

[0088] According to an embodiment of the present disclosure, the test strategy is a test rule. For example, the test strategy may be a batch restart test or a single restart test. The test function script may support testing the function of the object to be tested. For example, compatibility testing, performance testing, etc.

[0089] According to the embodiment of the present disclosure, after the test is completed, the test process information and the test results are released to production for use at the same time. The test status information corresponding to the target application object and the deployment object is updated according to the test results and the test verification results that represent the completed test.

[0090] According to an embodiment of the present disclosure, the operation and maintenance check strategy corresponding to the running stage includes a user authority check strategy and an execution status check strategy; wherein, the operation and maintenance check strategy corresponding to the target application in the pre-running stage, the running stage, and the post-running stage is executed to obtain the operation and maintenance check result, which also includes:

[0091] Execute the user authority check strategy to obtain the authority check result indicating that the check has passed, so that the application user object on the target application can perform transaction operations; execute the execution status check strategy to obtain the execution check result.

[0092] According to an embodiment of the present disclosure, the user authority check policy may include an approval check policy, an executor clicks on a menu and views data authority check policy, a secondary authorization authority check policy, a high-risk command authority check policy, and the like.

[0093] According to the embodiments of the present disclosure, a user permission check strategy is executed to obtain a permission check result indicating that the check has passed. At the same time, permission check results such as prompts for high-risk commands can be detected to facilitate secure transaction operations by application user objects on the target application.

[0094] According to the embodiments of the present disclosure, the execution status verification strategy can support the display of the execution status and historical execution status of the target application object and the deployment object, as well as the setting of the detection and maintenance period, to obtain the execution verification results, and then update the test status information corresponding to the target application object and the deployment object according to the execution verification results, connect the test and executed information, and prompt risks and applicability.

[0095] According to an embodiment of the present disclosure, the operation and maintenance verification strategy corresponding to the post-operation stage includes a fault verification strategy, a business transaction verification strategy, and a log verification strategy; wherein, the operation and maintenance verification strategy corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage is executed, and the operation and maintenance verification results are obtained, including:

[0096] Execute the fault verification strategy to obtain the fault verification result; execute the business transaction verification strategy to obtain the transaction status verification result; execute the log verification strategy to obtain the log status verification result, among which the operation and maintenance verification result includes the fault verification result, the transaction status verification result, and the log status verification result.

[0097] According to an embodiment of the present disclosure, the fault detection strategy is used to detect the fault type, fault scenario, etc. when a fault occurs. The fault detection strategy is executed to obtain a fault detection result. The fault detection result may include a fault scenario, a fault type, etc.

[0098] According to an embodiment of the present disclosure, a business transaction verification strategy is used to detect the completion status of a business transaction, such as transaction duration and transaction success rate. The business transaction verification strategy is executed to obtain a transaction status verification result. For example, the transaction status verification result may include a transaction success rate of 90%.

[0099] According to an embodiment of the present disclosure, the log check strategy is used to detect abnormal log status, such as log connection thread status, etc. The log check strategy is executed to obtain a log status check result. For example, the log status check result may include a normal log connection result.

[0100] According to an embodiment of the present disclosure, the fault verification result includes target fault scenario information, and the operation and maintenance status information includes operation and maintenance scenario information, transaction status information, log status information, and running status information; wherein, updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance verification result includes:

[0101] Based on the scenario mapping relationship, determine the target operation and maintenance scenario information corresponding to the target fault scenario information, wherein the scenario mapping relationship represents the correspondence between the fault scenario and the operation and maintenance scenario; in the application operation and maintenance view, determine the first deployment object corresponding to the target operation and maintenance scenario information; perform a fault handling operation on the first deployment object to obtain a handling result; update the running status information of the first deployment object according to the handling result; update the transaction status information and log status information corresponding to the target application object according to the transaction status check result and the log status check result.

[0102] According to an embodiment of the present disclosure, a scenario mapping relationship between a fault scenario and an operation and maintenance scenario is defined, and the target operation and maintenance scenario information can be quickly locked according to the target fault scenario information and the scenario mapping relationship. For example, the target operation and maintenance scenario information is defined as a scenario mapping relationship between a production node query timeout scenario and an operation and maintenance scenario as an application production class.

[0103] According to an embodiment of the present disclosure, the operation and maintenance status information associated with the deployment object includes operation and maintenance scenario information. In the application operation and maintenance view, the first deployment object corresponding to the target operation and maintenance scenario information is determined. For example, the target operation and maintenance scenario information is the application production class, and then the first deployment object is determined to be the container 1 object.

[0104] For example, if the first deployment object is container 1, and a fault occurs on container 1, container 1 can be isolated to obtain a processing result indicating that isolation is complete, and then the running status information of container 1 is updated to an unexecuted state according to the processing result.

[0105] According to an embodiment of the present disclosure, transaction status information corresponding to the target application object is updated according to the transaction status check result, and log status information corresponding to the target application object is updated according to the log status check result.

[0106] According to the embodiments of the present disclosure, the target operation and maintenance scenario information can be quickly locked according to the target fault scenario information and the scenario mapping relationship. The operation and maintenance status information in the application operation and maintenance view includes the target operation and maintenance scenario information, so that the fault location can be quickly locked. If the fault occurs on container 1, container 1 can be isolated and processed to timely feed back the scenario construction. The operation and maintenance inspection strategy corresponding to the pre-operation stage is executed, and then it is executed according to the demand based on the operation and maintenance inspection results and the operation and maintenance scenario. After execution, the linkage monitoring is carried out to conduct a phased analysis of the operation and maintenance inspection results, and a certain object is quickly cut into for disposal, and then the overall view is fed back, which improves the average fault recovery time of the target application and realizes the safe and standardized automated operation and maintenance management of the target application.

[0107] According to an embodiment of the present disclosure, the deployment object includes a space object, an application system object, a deployment unit object, a container service object, a container collection object, and a container object; wherein, based on the technology stack, the target application object and the deployment object associated with the target application object are standardized to determine the application operation and maintenance view of the target application, including:

[0108] Based on the container technology stack, the target application objects, space objects, application system objects, deployment unit objects, container service objects, container collection objects, and container objects are standardized to determine the application operation and maintenance view of the target application.

[0109] According to an embodiment of the present disclosure, the space corresponding to the deployment object space object contains all projects and parameter settings of the current workspace. The application system corresponding to the application system object is the system where the target application is located, and the deployment unit corresponding to the deployment unit object is a logically different and independent software unit, which can be independently deployed, versioned and managed in the application. The container service corresponding to the container service object is the service environment, which includes containers, storage addresses, network interfaces, container configurations, etc. The container set Pod corresponding to the container collection object is a collection of multiple containers. The container container of the container object is the container in the container collection. A container collection Pod encapsulates an application container and may include multiple containers.

[0110] According to an embodiment of the present disclosure, the logical-physical relationship between deployment objects may be that the application system includes the container service, the container service includes the container set, and the container set includes the container.

[0111] According to the embodiments of the present disclosure, a unified definition of target application objects, space objects, application system objects, deployment unit objects, container service objects, container collection objects, and container objects are performed based on the container technology stack. Starting from the target application object, the display is expanded layer by layer, and the operation and maintenance status information is associated to determine the application operation and maintenance view of the target application.

[0112] Figure 3 An example schematic diagram of an object mapping relationship according to an embodiment of the present disclosure is schematically shown.

[0113] like Figure 3 As shown in the figure, there is a corresponding mapping relationship between the objects of the traditional technology stack and the container technology stack, which facilitates the mixed deployment of objects. The deployment objects defined in the traditional technology stack are traditional application operation and maintenance objects, which include logical subsystem objects, physical subsystem objects, deployment unit objects, host objects, user objects, and process objects. The deployment unit object corresponds to the application function deployment module, the host object corresponds to the actual physical machine or virtual machine, the user object corresponds to the application user or other users such as weblogic users, and the process object corresponds to the line management process running on the host.

[0114] According to the embodiments of the present disclosure, the deployment objects defined in the container technology stack are container application operation and maintenance objects, which include target application objects, space objects, application system objects, deployment unit objects, container service objects, container collection objects, and container objects. The application system corresponds to the physical subsystem, the container collection corresponds to the host, and the container corresponds to the user.

[0115] According to an embodiment of the present disclosure, the target application object and the deployment object associated with the target application object are standardized based on the technology stack to determine the application operation and maintenance view of the target application, and further includes:

[0116] When the deployment objects include virtual operating system objects and application user objects, the target application objects, deployment unit objects, virtual operating system objects, and application user objects are standardized based on the traditional virtual machine technology stack to determine the application operation and maintenance view of the target application.

[0117] According to an embodiment of the present disclosure, the deployment objects defined in the traditional virtual machine technology stack include virtual operating system objects and application user objects. The virtual operating system objects correspond to host objects. Based on the technology stack, the target application objects, deployment unit objects, virtual operating system objects, and application user objects are uniformly defined to determine the application operation and maintenance view of the target application.

[0118] According to an embodiment of the present disclosure, the virtual operating system (OS) corresponding to the virtual operating system object can be divided into a desktop operating system, a mobile operating system, a server operating system, an embedded operating system, etc. The virtual operating system is deployed on a virtual machine.

[0119] Figure 4 An example schematic diagram of container hybrid technology stack deployment according to an embodiment of the present disclosure is schematically shown.

[0120] like Figure 4As shown, the target application object of target application A is hierarchically organized into a deployment structure for overall display, and the corresponding operation and maintenance scenario numbers are marked on the target application object and each deployment object. Click the number to display the operation and maintenance status information associated with the operation and maintenance scenario, such as test process information and test result information. The container hybrid technology stack deployment includes the hybrid deployment of the traditional virtual machine technology stack and the container technology stack. In the traditional virtual machine technology stack deployment, the application operation and maintenance view starts with the target application A, and expands layer by layer to include deployment unit A, virtual operating system OS1, virtual operating system OS2, and virtual operating system OS3. The virtual operating system OS1 is further expanded to include application users and weblogic users. The above can all be abstracted as objects to identify the corresponding deployment objects. The traditional virtual machine technology stack uniformly defines the above deployment objects. The number of user operations corresponding to the application user is 5.

[0121] According to the embodiments of the present disclosure, in the deployment of the container technology stack, the deployment space is expanded based on the target application A in the application operation and maintenance view, and the deployment space is further expanded into deployment unit A and deployment unit B. Deployment unit A is expanded into a container service such as nginx service, and the container service is expanded into container set pod1, container set pod2, and container set pod3. Container set pod1 is further expanded to include container container1 and container container2, all of which can be abstracted into objects for identifying corresponding deployment objects. The container technology stack uniformly defines the above deployment objects. The operation and maintenance status information associated with container set pod2 includes 3 operation and maintenance scenarios, including 1 daily inspection category and 2 application production categories.

[0122] According to an embodiment of the present disclosure, the operation and maintenance status information associated with the target application A may include 8 operation and maintenance scenarios, 3 container categories, all of which have been fed back and executed, and 5 virtual machine application user operations, 2 of which have completed test verification, and the rest have not executed the operation and maintenance verification strategy.

[0123] According to the embodiments of the present disclosure, the application operation and maintenance view accelerates the integrated management of traditional virtual machine technology stacks, virtual machine and container hybrid technology stacks, and container technology stacks. According to the defined test information and scripts, APIs, orchestration, and combined with the deployment architecture, the traditional infrastructure, platform, virtualization layer, network, storage, application and other dimensional scattered modes are systematically integrated and sorted out. This mode stands from the perspective of the target application, can fully reflect the overall situation of operation and maintenance, and is also convenient for quickly cutting into a certain object for disposal when a fault occurs, thereby realizing rapid operation and maintenance or disposal jump.

[0124] Based on the above application operation and maintenance method, the present disclosure also provides an application operation and maintenance device. Figure 5 The device is described in detail.

[0125] Figure 5A structural block diagram of an application operation and maintenance device according to an embodiment of the present disclosure is shown.

[0126] like Figure 5 As shown, the application operation and maintenance device 500 of this embodiment includes a determination module 510 , an execution module 520 and an update module 530 .

[0127] The determination module 510 is used to standardize the target application object and the deployment object associated with the target application object based on the technology stack, and determine the application operation and maintenance view of the target application, wherein the technology stack includes the traditional virtual machine technology stack, the container technology stack and the container hybrid technology stack, and the container hybrid technology stack performs object hybrid deployment based on the object mapping relationship between the traditional virtual machine technology stack and the container technology stack, and the target application object is used to identify the target application. The application operation and maintenance view represents a hierarchical structure diagram composed of the physical and logical relationships between the target application object and multiple deployment objects, and the target application object and the deployment object are each bound with operation and maintenance status information. In one embodiment, the determination module 510 can be used to perform the operation S210 described above, which will not be repeated here.

[0128] The execution module 520 is used to execute the operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage, and obtain the operation and maintenance verification results. In one embodiment, the execution module 520 can be used to execute the operation S220 described above, which will not be repeated here.

[0129] The updating module 530 is used to update the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance check result. In one embodiment, the updating module 530 can be used to perform the operation S230 described above, which will not be described in detail here.

[0130] According to an embodiment of the present disclosure, the execution module 520 includes a first execution submodule, a second execution submodule and a third execution submodule.

[0131] The first execution submodule is used to execute the fault detection strategy to obtain the fault detection result.

[0132] The second execution submodule is used to execute the business transaction verification strategy and obtain the transaction status verification result.

[0133] The third execution submodule is used to execute the log verification strategy and obtain the log status verification result, wherein the operation and maintenance verification result includes the fault verification result, the transaction status verification result, and the log status verification result.

[0134] According to an embodiment of the present disclosure, the update module 530 includes a first update submodule, a second update submodule, a third update submodule, a fourth update submodule, and a fifth update submodule.

[0135] The first updating submodule is used to determine the target operation and maintenance scenario information corresponding to the target fault scenario information based on the scenario mapping relationship, wherein the scenario mapping relationship represents the correspondence between the fault scenario and the operation and maintenance scenario.

[0136] The second updating submodule is used to determine, in the application operation and maintenance view, a first deployment object corresponding to the target operation and maintenance scenario information.

[0137] The third updating submodule is used to perform a fault handling operation on the first deployment object to obtain a handling result.

[0138] The fourth updating submodule is used to update the running status information of the first deployment object according to the processing result.

[0139] The fifth updating submodule is used to update the transaction status information and log status information corresponding to the target application object according to the transaction status check result and the log status check result.

[0140] According to an embodiment of the present disclosure, the determination module 510 includes a first determination submodule.

[0141] The first determination submodule is used to standardize the target application object, space object, application system object, deployment unit object, container service object, container collection object, and container object based on the container technology stack to determine the application operation and maintenance view of the target application.

[0142] According to an embodiment of the present disclosure, the determination module 510 further includes a second determination submodule.

[0143] The second determination submodule is used to standardize the target application object, deployment unit object, virtual operating system object, and application user object based on the traditional virtual machine technology stack to determine the application operation and maintenance view of the target application when the deployment object includes a virtual operating system object and an application user object.

[0144] According to an embodiment of the present disclosure, the execution module 520 further includes a fourth execution submodule and a fifth execution submodule.

[0145] The fourth execution submodule is used to execute the system status check strategy on the system where the target application is located, and obtain the system status check result indicating that the check has passed, so that the target application can perform business transactions.

[0146] The fifth execution submodule is used to execute the test verification strategy to obtain the test verification result, wherein the operation and maintenance verification result includes the system status verification result and the test verification result.

[0147] According to an embodiment of the present disclosure, the update module 530 further includes a sixth update submodule, a seventh update submodule and an eighth update submodule.

[0148] The sixth updating submodule is used to determine the objects to be tested that have not completed the test from the target application objects and the deployment objects based on the test verification result.

[0149] The seventh updating submodule is used to test the test object according to the test strategy and the test function script to obtain the test result.

[0150] The eighth updating submodule is used to update the test status information corresponding to the target application object and the deployment object respectively according to the test result and the verification result representing the completed test in the test verification result.

[0151] According to an embodiment of the present disclosure, the execution module 520 further includes a sixth execution submodule and a seventh execution submodule.

[0152] The sixth execution submodule is used to execute the user authority check strategy and obtain an authority check result indicating that the check has passed, so that the application user object on the target application can perform transaction operations.

[0153] The seventh execution submodule is used to execute the execution status check strategy and obtain the execution check result.

[0154] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging circuits, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

[0155] For example, any multiple of the determination module 510, the execution module 520, and the update module 530 can be combined in one module / unit / sub-unit for implementation, or any one of the modules / units / sub-units can be split into multiple modules / units / sub-units. Alternatively, at least part of the functions of one or more of these modules / units / sub-units can be combined with at least part of the functions of other modules / units / sub-units and implemented in one module / unit / sub-unit. According to an embodiment of the present disclosure, at least one of the determination module 510, the execution module 520, and the update module 530 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware or in a suitable combination of any of them. Alternatively, at least one of the determination module 510, the execution module 520, and the update module 530 may be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function may be performed.

[0156] Figure 6 A block diagram of an electronic device suitable for implementing an application operation and maintenance method according to an embodiment of the present invention is shown.

[0157] Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0158] like Figure 6 As shown, a computer electronic device 600 according to an embodiment of the present invention includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include an onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present invention.

[0159] In RAM 603, various programs and data required for the operation of electronic device 600 are stored. Processor 601, ROM 602 and RAM 603 are connected to each other via bus 604. Processor 601 performs various operations of the method flow according to the embodiment of the present invention by executing the programs in ROM 602 and / or RAM 603. It should be noted that the program can also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 can also perform various operations of the method flow according to the embodiment of the present invention by executing the programs stored in one or more memories.

[0160] Optionally, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to the bus 604. The electronic device 600 may further include one or more of the following components connected to the input / output (I / O) interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 608 including a hard disk, etc.; and a communication portion 609 including a network interface card such as a LAN card, a modem, etc. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the input / output (I / O) interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage portion 608 as needed.

[0161] Optionally, the method flow according to the embodiment of the present invention can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, the above-mentioned functions defined in the system of the embodiment of the present invention are executed. Optionally, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0162] The present invention also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiment; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the application operation and maintenance method according to the embodiment of the present invention is implemented.

[0163] Optionally, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

[0164] For example, optionally, the computer-readable storage medium may include the ROM 602 and / or the RAM 603 described above and / or one or more memories other than the ROM 602 and the RAM 603 .

[0165] An embodiment of the present invention also includes a computer program product, which includes a computer program, which contains program code for executing the method provided by the embodiment of the present invention. When the computer program product runs on an electronic device, the program code is used to enable the electronic device to implement the application operation and maintenance method provided by the embodiment of the present invention.

[0166] When the computer program is executed by the processor 601, the above functions defined in the system / device of the embodiment of the present invention are performed. Optionally, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0167] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 609, and / or installed from a removable medium 611. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0168] Optionally, the program code for executing the computer program provided by the embodiment of the present invention can be written in any combination of one or more programming languages, specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, such as Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0169] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It can be understood by those skilled in the art that the features recorded in the various embodiments of the present disclosure can be combined and / or combined in a variety of ways, even if such a combination or combination is not explicitly recorded in the present disclosure. In particular, without departing from the spirit and teaching of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0170] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. An application operation and maintenance method, characterized in that: The method comprises: Based on the technology stack, the target application object and the deployment object associated with the target application object are standardized to determine the application operation and maintenance view of the target application, wherein the technology stack includes a traditional virtual machine technology stack, a container technology stack and a container hybrid technology stack, and the container hybrid technology stack performs object hybrid deployment based on the object mapping relationship between the traditional virtual machine technology stack and the container technology stack, the target application object is used to identify the target application, and the application operation and maintenance view represents a hierarchical structure diagram composed of physical and logical relationships between the target application object and multiple deployment objects, and the target application object and the deployment object are each bound with operation and maintenance status information; Execute the operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage, respectively, to obtain the operation and maintenance verification results; The operation and maintenance status information in the application operation and maintenance view is updated based on the operation and maintenance check result.

2. The method according to claim 1, characterized in that The operation and maintenance verification strategy corresponding to the post-operation stage includes a fault verification strategy, a business transaction verification strategy, and a log verification strategy; The operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage are executed to obtain the operation and maintenance verification results, including: Executing the fault detection strategy to obtain a fault detection result; Execute the business transaction verification strategy to obtain a transaction status verification result; The log verification strategy is executed to obtain a log status verification result, wherein the operation and maintenance verification result includes the fault verification result, the transaction status verification result, and the log status verification result.

3. The method according to claim 2, characterized in that The fault detection result includes target fault scenario information, and the operation and maintenance status information includes operation and maintenance scenario information, transaction status information, log status information, and operation status information; Wherein, updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance check result includes: Based on the scenario mapping relationship, determine the target operation and maintenance scenario information corresponding to the target fault scenario information, wherein the scenario mapping relationship represents the correspondence between the fault scenario and the operation and maintenance scenario; In the application operation and maintenance view, determining a first deployment object corresponding to the target operation and maintenance scenario information; Performing a fault handling operation on the first deployment object to obtain a handling result; Update the running status information of the first deployment object according to the processing result; The transaction status information and the log status information corresponding to the target application object are updated according to the transaction status check result and the log status check result.

4. The method according to claim 1, characterized in that: The deployment objects include space objects, application system objects, deployment unit objects, container service objects, container collection objects, and container objects; The target application object and the deployment object associated with the target application object are standardized based on the technology stack to determine the application operation and maintenance view of the target application, including: Based on the container technology stack, the target application object, the space object, the application system object, the deployment unit object, the container service object, the container collection object, and the container object are standardized to determine an application operation and maintenance view of the target application.

5. The method according to claim 4, characterized in that The target application object and the deployment object associated with the target application object are standardized based on the technology stack to determine the application operation and maintenance view of the target application, further comprising: In the case where the deployment object includes a virtual operating system object and an application user object, the target application object, the deployment unit object, the virtual operating system object, and the application user object are standardized based on the traditional virtual machine technology stack to determine the application operation and maintenance view of the target application.

6. The method according to claim 1, characterized in that The operation and maintenance verification strategy corresponding to the pre-operation stage includes a system status verification strategy and a test verification strategy; The step of executing the operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage to obtain the operation and maintenance verification results also includes: Executing the system status check strategy on the system where the target application is located to obtain a system status check result indicating that the check has passed, so that the target application can perform business transactions; The test verification strategy is executed to obtain a test verification result, wherein the operation and maintenance verification result includes the system status verification result and the test verification result.

7. The method according to claim 6, characterized in that The operation and maintenance status information also includes test status information; Wherein, updating the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance check result further includes: Based on the test verification result, determining the to-be-tested object that has not completed the test from the target application object and the deployment object; Testing the object to be tested according to the test strategy and the test function script to obtain the test result; The test status information corresponding to the target application object and the deployment object is updated according to the test result and the verification result indicative of the completed test in the test verification result.

8. The method according to claim 1, characterized in that The operation and maintenance verification strategy corresponding to the running stage includes a user authority verification strategy and an execution status verification strategy; The step of executing the operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage to obtain the operation and maintenance verification results also includes: Executing the user authority check strategy to obtain an authority check result indicating that the check has passed, so that the application user object on the target application can perform transaction operations; The execution status check strategy is executed to obtain an execution check result.

9. An application operation and maintenance device, characterized in that: The device comprises: A determination module, configured to standardize a target application object and a deployment object associated with the target application object based on a technology stack, and determine an application operation and maintenance view of the target application, wherein the technology stack includes a traditional virtual machine technology stack, a container technology stack, and a container hybrid technology stack, and the container hybrid technology stack performs object hybrid deployment based on an object mapping relationship between the traditional virtual machine technology stack and the container technology stack, the target application object is used to identify the target application, and the application operation and maintenance view represents a hierarchical structure diagram consisting of a physical and logical relationship between the target application object and a plurality of the deployment objects, and the target application object and the deployment object are each bound with operation and maintenance status information; An execution module, used to execute the operation and maintenance verification strategies corresponding to the target application in the pre-operation stage, the operation stage, and the post-operation stage, respectively, to obtain the operation and maintenance verification results; An updating module is used to update the operation and maintenance status information in the application operation and maintenance view based on the operation and maintenance check result.

10. An electronic device, comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the method according to any one of claims 1 to 8.

12. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 8.