Operation and maintenance release management system, method, device and equipment and storage medium

Abstract

The invention discloses an operation and maintenance release management system, method, device and equipment and a storage medium. The system comprises a system application layer, an API adaptation layer, a tool layer and an instance layer. The system application layer is used for managing at least one management application system and issuing operation and maintenance release management tasks generated by the management application systems to the API adaptation layer; the API adaptation layer is used for determining tool execution instructions corresponding to the API execution instructions according to the task execution related information and issuing the task execution related information and the tool execution instructions to the tool layer; the tool layer is used for scheduling a task execution tool to execute a tool execution instruction, generating a machine execution script, determining an instance server according to task execution related information, and issuing the machine execution script to the instance server in the instance layer; and the instance layer is used for managing at least one instance server to execute a corresponding machine execution script, generating and feeding back a script execution result, and managing an operation and maintenance release state of the system instance according to the script execution result.

Description

Technical Field

[0001] The present invention relates to the field of system operation and maintenance release technology, and in particular to an operation and maintenance release management system, method, device, equipment and storage medium. Background Art

[0002] There are significant pain points in the current technical architecture of the operation and maintenance system: many operation and maintenance platforms operate in parallel, and the system management strategies and application scenarios adopted by each are completely different. This decentralization leads to barriers to interconnection between operation and maintenance systems, and it is impossible to achieve the unification of operation and maintenance management and release mechanisms, thereby greatly reducing the efficiency and reliability of operation and maintenance release management. Summary of the invention

[0003] The present invention provides an operation and maintenance release management system, method, device, equipment and storage medium to improve the efficiency and reliability of operation and maintenance release management.

[0004] According to one aspect of the present invention, an operation and maintenance release management system is provided, the system comprising: a system application layer, an API adaptation layer, a tool layer and an instance layer;

[0005] The system application layer is used to manage at least one management application system and send the operation and maintenance release management tasks generated by each management application system to the API adaptation layer;

[0006] The API adaptation layer is used to determine the tool execution instructions corresponding to each of the API execution instructions according to the task execution related information, and send the task execution related information and the tool execution instructions to the tool layer;

[0007] The tool layer is used to schedule the task execution tool to execute the tool execution instruction and generate a machine execution script, and determine the instance server according to the task execution related information, and send the machine execution script to the instance server in the instance layer;

[0008] The instance layer is used to manage at least one instance server to execute a corresponding machine execution script, generate and feedback a script execution result, and manage the operation and maintenance release status of the system instance according to the script execution result.

[0009] According to another aspect of the present invention, an operation and maintenance release management method is provided, which is applied to an API adaptation layer of an operation and maintenance release management system, wherein the operation and maintenance release management system further includes a system application layer, a tool layer, and an instance layer, and the method includes:

[0010] Obtaining an operation and maintenance publishing management task sent by a management application system in the system application layer; the operation and maintenance publishing management task includes task execution related information and at least one API execution instruction;

[0011] Determine, based on the task execution related information, tool execution instructions corresponding to each of the API execution instructions;

[0012] The task execution related information and the tool execution instruction are sent to the tool layer, so that the task execution tool in the tool layer executes the tool execution instruction and generates a machine execution script, and the target server is determined according to the task execution related information, and the machine execution script is sent to the target server, and the target server executes the machine execution script, generates and feeds back the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result.

[0013] According to another aspect of the present invention, an operation and maintenance release management device is provided, which is configured in an API adaptation layer of an operation and maintenance release management system, wherein the operation and maintenance release management system further includes a system application layer, a tool layer and an instance layer, and the device includes:

[0014] A task acquisition module, used to acquire an operation and maintenance release management task sent by a management application system in the system application layer; the operation and maintenance release management task includes task execution related information and at least one API execution instruction;

[0015] An instruction generation module, used for determining the tool execution instructions corresponding to each of the API execution instructions according to the task execution related information;

[0016] An instruction sending module is used to send the task execution related information and the tool execution instruction to the tool layer, so that the task execution tool in the tool layer executes the tool execution instruction and generates a machine execution script, and determines the target server according to the task execution related information, sends the machine execution script to the target server, and the target server executes the machine execution script, generates and feeds back the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result.

[0017] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0018] at least one processor; and

[0019] a memory communicatively connected to the at least one processor; wherein,

[0020] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the operation and maintenance release management method described in any embodiment of the present invention.

[0021] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the operation and maintenance release management method described in any embodiment of the present invention when executed.

[0022] The technical solution of this embodiment is achieved by having the system application layer manage at least one management application system, and sending the operation and maintenance release management tasks generated by each management application system to the API adaptation layer; the API adaptation layer determines the tool execution instructions corresponding to each API execution instruction based on the task execution related information, and sends the task execution related information and tool execution instructions to the tool layer; the tool layer schedules the task execution tool to execute the tool execution instruction and generate a machine execution script, and determines the instance server based on the task execution related information, and sends the machine execution script to the instance server in the instance layer; the instance layer manages at least one instance server to execute the corresponding machine execution script, generate and feedback the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result. The above technical solution enables seamless conversion between each management application system and each tool layer platform by uniformly arranging the instruction mapping relationship between API instructions and tool execution instructions, realizes effective decoupling between the operation and maintenance platform and the execution platform, and improves the efficiency, flexibility and reliability of operation and maintenance release management.

[0023] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 This is a schematic diagram of the structure of an operation and maintenance release management system provided according to Embodiment 1 of the present invention;

[0026] Figure 2 This is a flowchart of an operation and maintenance release management execution method provided according to Embodiment 2 of the present invention;

[0027] Figure 3 This is a schematic diagram of the structure of an operation and maintenance release management device provided according to Embodiment 3 of the present invention;

[0028] Figure 4It is a structural schematic diagram of an electronic device for implementing the operation and maintenance release management method of an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] Embodiment 1

[0032] Figure 1 A schematic diagram of the structure of an operation and maintenance release management system provided by the first embodiment of the present invention: system application layer, API (Application Programming Interface) adaptation layer, tool layer and instance layer.

[0033] Among them, the system application layer is used to manage at least one management application system, and send the operation and maintenance release management tasks generated by each management application system to the API adaptation layer; the API adaptation layer is used to determine the tool execution instructions corresponding to each API execution instruction according to the task execution related information, and send the task execution related information and tool execution instructions to the tool layer; the tool layer is used to schedule the task execution tool to execute the tool execution instruction and generate a machine execution script, and determine the instance server according to the task execution related information, and send the machine execution script to the instance server in the instance layer; the instance layer is used to manage at least one instance server to execute the corresponding machine execution script, generate and feedback the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result.

[0034] Among them, at least one management application system can be deployed in the system application layer, and each management application system can be an application system that implements different functions, such as an insurance policy system, an asset management system, or a financial advisory system. Each management application system can include corresponding subsystems; the subsystems can be microservice modules with independent functions. Each subsystem can correspond to a corresponding process or application instance and be deployed on different application servers.

[0035] For example, if the management application system is an insurance policy application system, its corresponding subsystem may be a login service subsystem. The subsystem includes at least one service process or application instance. For the login service, the same login service process may be deployed on different application servers, and each process is an application instance. The lowest level of operation and maintenance release in this embodiment is the release of an application instance or a process, that is, instance release.

[0036] Among them, the operation and maintenance release management task can be a task such as updating or releasing an application instance under a subsystem of the management application system. It can be understood that the operation and maintenance release of an application instance can usually be divided into four states: to be deployed, in place, ready, and running. That is, the application instance repeatedly switches between the four states.

[0037] The operation and maintenance release management task includes task execution related information and at least one API execution instruction. Among them, the task execution related information may include information related to the execution of this operation and maintenance release task, such as the operation and maintenance tools required to execute this operation and maintenance release task. The number of API execution instructions can be one or more, such as opening a service, closing a service, stopping an application (closing a process), and starting an application (starting a process).

[0038] In an optional embodiment, the system application layer is used to generate an operation and maintenance release management task. The specific operation and maintenance release management task is generated in the following manner: determining an operation and maintenance release management process; the operation and maintenance release management process includes at least one to-be-executed item with an execution order relationship; determining the API execution instructions corresponding to each to-be-executed item; and generating the operation and maintenance release management task according to the API execution instructions of each to-be-executed item.

[0039] The operation and maintenance release management process may be an operation and maintenance release process with an execution order, for example, the process may include starting services, detecting instances, and releasing configurations. Then starting services, detecting instances, and releasing configurations are pending items with an execution order relationship. Different pending items correspond to their own API execution instructions, and operation and maintenance release management tasks are generated according to the API execution instructions of each pending item.

[0040] Among them, at least one operation and maintenance tool (i.e., execution system) for operation and maintenance release management is deployed in the tool layer, and different operation and maintenance tools have different corresponding protocols. When the system application layer issues operation and maintenance release management tasks, due to the inconsistency of its API standards, it is necessary to convert the API standards separately, and only after the conversion can the operation and maintenance tool execute the corresponding operation and maintenance release tasks. In the whole process, the system application layer and the tool layer are highly coupled, and the operation standards of different operation and maintenance tools are inconsistent, and the flexibility is not high.

[0041] In summary, in order to realize the automation of the issuance and processing of operation and maintenance release management tasks, this embodiment decouples the system application layer and the tool layer, and performs unified and standardized processing on the issuance of operation and maintenance release management tasks, so that different operation and maintenance tools in the tool layer can perform task processing of operation and maintenance release management tasks based on their own standards, thereby improving flexibility and reliability.

[0042] Among them, the API adaptation layer is used to convert the API execution instructions received in the operation and maintenance release management tasks into tool execution instructions that can be recognized by each operation and maintenance tool in the tool layer, and send the converted tool execution instructions to the tool layer for execution by the corresponding operation and maintenance tool.

[0043] It should be noted that for all types of published operation and maintenance operations, specific operation instructions can be transformed into standard unified operation and maintenance operations, so that the operation and maintenance tools can perform the standardized unified operation and maintenance operations. The mapping relationship between tool execution instructions and API execution instructions of different operation and maintenance tools may be different, so the mapping relationship between tool execution instructions of different operation and maintenance tools and each API execution instruction can be pre-stored.

[0044] Specifically, the API execution instructions included in the operation and maintenance release task execution process include but are not limited to the following instructions:

[0045] (1) Open services (services are enabled to provide services to other applications);

[0046] (2) Shut down the service (the service shuts down the service to other applications);

[0047] (3) Stop the application (close the process);

[0048] (4) Start the application (start the process by starting the script);

[0049] (5) Detect the instance (for internal status, the detection script will detect the process to determine whether the instance is normal);

[0050] (6) Release configuration: startup configuration (configuration here refers to conf or yml sent to the configuration directory, such as the running configuration directory, to prepare for startup; for this type of configuration using nacos, it means updating the configuration on the relevant project);

[0051] (7) Release program: prepare the installation package to the installation directory;

[0052] (8) Delete configuration: (in the configuration directory) Delete configuration;

[0053] (9) Uninstall the program: delete the installation package (in the installation directory);

[0054] (10) Cold backup: back up the currently executed application to a specified backup directory (versions can be marked);

[0055] (11) Hot backup: In the startup state, the application under the current execution path is backed up to the specified backup directory (versions can be marked);

[0056] (12) Package acquisition: Get the release package to the specified directory (package temporary storage directory, not release directory);

[0057] (13) Enable the package (new package / old package): Place the specified remote application in the specified instance running directory (decompress it if necessary);

[0058] (14) Enable configuration: the startup configuration (the configuration here refers to conf or yml, which is sent to the configuration directory, such as the running configuration directory, to prepare for startup);

[0059] (15) Turn off traffic: turn off the traffic of the process;

[0060] (16) Injection configuration: specifically refers to using systems such as nacos to inject configuration into the corresponding project configuration server to take effect;

[0061] (17) Clean cache: clean cache or related files according to parameters;

[0062] (18) Configuration backup: Start configuration backup to the specified directory;

[0063] (19) Release preparation: A series of operations that need to be done before release, such as clearing cache, package verification or other operations mentioned above;

[0064] (20) Verify application: Verify the application instance of the publishing process;

[0065] (21) Empty: empty command.

[0066] In an optional embodiment, tool execution instructions corresponding to each API execution instruction are determined based on task execution related information, including: determining the tools required for task execution based on task execution related information; determining a tool instruction mapping relationship table corresponding to the tools required for task execution; and generating tool execution instructions corresponding to each API execution instruction based on the tool instruction mapping relationship table.

[0067] Decrypt the information related to task execution to obtain the operation and maintenance tool required to execute the task. Determine the tool instruction mapping relationship table corresponding to the operation and maintenance tool. According to the mapping relationship between API execution instructions and tool execution instructions in the tool instruction mapping relationship table, determine the tool execution instructions corresponding to each API execution instruction.

[0068] The tool instruction mapping relationship table between the tool execution instructions and API execution instructions of a certain operation and maintenance tool can be shown in Table 1:

[0069] Table 1

[0070]

[0071] The API adapter layer sends the generated tool execution instructions and task execution information to the tool layer, which schedules the operation and maintenance tools required to execute the task in the task execution information, executes the tool execution instructions, and generates a machine execution script. Based on the task execution related information, the instance server related to the task execution is determined.

[0072] Among them, at least one instance server is deployed in the instance layer, and each instance server runs one or more application instances (application processes) on one or more management application systems.

[0073] The machine executes the script issued by the operation and maintenance tool of the corresponding instance service self-tool layer and generates the script execution result. The script execution result can be the success or failure of the operation and maintenance release task. The instance server feeds back the script execution result to the system application layer layer by layer.

[0074] In an optional embodiment, the API adaptation layer obtains the tool instruction execution result generated by the tool layer based on the script execution result; generates the API instruction execution result according to the tool instruction execution result; and feeds back the API instruction execution result to the system application layer so that the system application layer can manage the operation and maintenance release status of the system instance based on the API instruction execution result.

[0075] The tool layer generates a tool instruction execution result based on the script execution result obtained from the instance layer. Specifically, if the script execution result is a successful operation and maintenance release, the tool instruction execution result is a successful tool instruction execution; if the script execution result is a failed operation and maintenance release, the tool instruction execution result is a failed tool instruction execution. The tool layer feeds back the tool instruction execution result to the API adaptation layer, and the API adaptation layer generates an API instruction execution result based on the tool execution result. Specifically, if the tool execution result is a successful tool instruction execution, the API instruction execution is successful; if the tool instruction execution fails, the API instruction execution fails. The API adaptation layer feeds back the API instruction execution result to the system application layer, and the system application layer can determine whether the operation and maintenance release management task of the system instance is successfully executed based on the API instruction execution result, thereby realizing the operation and maintenance release management of the system instance.

[0076] The technical solution of this embodiment is achieved by having the system application layer manage at least one management application system, and sending the operation and maintenance release management tasks generated by each management application system to the API adaptation layer; the API adaptation layer determines the tool execution instructions corresponding to each API execution instruction based on the task execution related information, and sends the task execution related information and tool execution instructions to the tool layer; the tool layer schedules the task execution tool to execute the tool execution instruction and generate a machine execution script, and determines the instance server based on the task execution related information, and sends the machine execution script to the instance server in the instance layer; the instance layer manages at least one instance server to execute the corresponding machine execution script, generate and feedback the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result. The above technical solution enables seamless conversion between each management application system and each tool layer platform by uniformly arranging the instruction mapping relationship between API instructions and tool execution instructions, realizes effective decoupling between the operation and maintenance platform and the execution platform, and improves the efficiency, flexibility and reliability of operation and maintenance release management.

[0077] Figure 2 A flowchart of an operation and maintenance release management method provided in Example 1 of the present invention. This embodiment can be applied to situations where operation and maintenance release management is performed on application instances of the same or different application systems. The method can be executed by an operation and maintenance release management device. The operation and maintenance release management device can be implemented in the form of hardware and / or software. The operation and maintenance release management device can be configured in an electronic device.

[0078] An operation and maintenance release management method of this embodiment can be applied to an operation and maintenance release management system, which includes a system application layer, an API adaptation layer, a tool layer and an instance layer. The method can be executed by the API adaptation layer, such as Figure 2 As shown, the method includes:

[0079] S210, obtaining an operation and maintenance release management task sent by a management application system in the system application layer; the operation and maintenance release management task includes task execution related information and at least one API execution instruction.

[0080] S220: Determine the tool execution instructions corresponding to the API execution instructions according to the task execution related information.

[0081] S230. Send the task execution related information and tool execution instructions to the tool layer, so that the task execution tool in the tool layer can execute the tool execution instructions and generate a machine execution script, and determine the target server based on the task execution related information, send the machine execution script to the target server, and have the target server execute the machine execution script, generate and feedback the script execution result, so as to manage the operation and maintenance release status of the system instance based on the script execution result.

[0082] Among them, the system application layer is used to manage at least one management application system, and send the operation and maintenance release management tasks generated by each management application system to the API adaptation layer; the API adaptation layer is used to determine the tool execution instructions corresponding to each API execution instruction according to the task execution related information, and send the task execution related information and tool execution instructions to the tool layer; the tool layer is used to schedule the task execution tool to execute the tool execution instruction and generate a machine execution script, and determine the instance server according to the task execution related information, and send the machine execution script to the instance server in the instance layer; the instance layer is used to manage at least one instance server to execute the corresponding machine execution script, generate and feedback the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result.

[0083] Among them, at least one management application system can be deployed in the system application layer, and each management application system can be an application system that implements different functions, such as an insurance policy system, an asset management system, or a financial advisory system. Each management application system can include corresponding subsystems; the subsystems can be microservice modules with independent functions. Each subsystem can correspond to a corresponding process or application instance and be deployed on different application servers.

[0084] For example, if the management application system is an insurance policy application system, its corresponding subsystem may be a login service subsystem. The subsystem includes at least one service process or application instance. For the login service, the same login service process may be deployed on different application servers, and each process is an application instance. The lowest level of operation and maintenance release in this embodiment is the release of an application instance or a process, that is, instance release.

[0085] Among them, the operation and maintenance release management task can be a task such as updating or releasing an application instance under a subsystem of the management application system. It can be understood that the operation and maintenance release of an application instance can usually be divided into four states: to be deployed, in place, ready, and running. That is, the application instance repeatedly switches between the four states.

[0086] The operation and maintenance release management task includes task execution related information and at least one API execution instruction. Among them, the task execution related information may include information related to the execution of this operation and maintenance release task, such as the operation and maintenance tools required to execute this operation and maintenance release task. The number of API execution instructions can be one or more, such as opening a service, closing a service, stopping an application (closing a process), and starting an application (starting a process).

[0087] In an optional embodiment, the system application layer is used to generate an operation and maintenance release management task. The specific operation and maintenance release management task is generated in the following manner: determining an operation and maintenance release management process; the operation and maintenance release management process includes at least one to-be-executed item with an execution order relationship; determining the API execution instructions corresponding to each to-be-executed item; and generating the operation and maintenance release management task according to the API execution instructions of each to-be-executed item.

[0088] The operation and maintenance release management process may be an operation and maintenance release process with an execution order, for example, the process may include starting services, detecting instances, and releasing configurations. Then starting services, detecting instances, and releasing configurations are pending items with an execution order relationship. Different pending items correspond to their own API execution instructions, and operation and maintenance release management tasks are generated according to the API execution instructions of each pending item.

[0089] Among them, at least one operation and maintenance tool (i.e., execution system) for operation and maintenance release management is deployed in the tool layer, and different operation and maintenance tools have different corresponding protocols. When the system application layer issues operation and maintenance release management tasks, due to the inconsistency of its API standards, it is necessary to convert the API standards separately, and only after the conversion can the operation and maintenance tool execute the corresponding operation and maintenance release tasks. In the whole process, the system application layer and the tool layer are highly coupled, and the operation standards of different operation and maintenance tools are inconsistent, and the flexibility is not high.

[0090] In summary, in order to realize the automation of the issuance and processing of operation and maintenance release management tasks, this embodiment decouples the system application layer and the tool layer, and performs unified and standardized processing on the issuance of operation and maintenance release management tasks, so that different operation and maintenance tools in the tool layer can perform task processing of operation and maintenance release management tasks based on their own standards, thereby improving flexibility and reliability.

[0091] Exemplarily, information related to task execution may be parsed to determine the operation and maintenance tools required to execute the operation and maintenance management task.

[0092] In an optional embodiment, tool execution instructions corresponding to each API execution instruction are determined based on task execution related information, including: determining the tools required for task execution based on task execution related information; determining a tool instruction mapping relationship table corresponding to the tools required for task execution; and generating tool execution instructions corresponding to each API execution instruction based on the tool instruction mapping relationship table.

[0093] Decrypt the information related to task execution to obtain the operation and maintenance tool required to execute the task. Determine the tool instruction mapping relationship table corresponding to the operation and maintenance tool. According to the mapping relationship between API execution instructions and tool execution instructions in the tool instruction mapping relationship table, determine the tool execution instructions corresponding to each API execution instruction.

[0094] The API adapter layer sends the generated tool execution instructions and task execution information to the tool layer, which schedules the operation and maintenance tools required to execute the task in the task execution information, executes the tool execution instructions, and generates a machine execution script. Based on the task execution related information, the instance server related to the task execution is determined.

[0095] Among them, at least one instance server is deployed in the instance layer, and each instance server runs one or more application instances (application processes) on one or more management application systems.

[0096] The machine executes the script issued by the operation and maintenance tool of the corresponding instance service self-tool layer and generates the script execution result. The script execution result can be the success or failure of the operation and maintenance release task. The instance server feeds back the script execution result to the system application layer layer by layer.

[0097] Optionally, obtain the tool instruction execution result generated by the tool layer based on the script execution result; generate the API instruction execution result according to the tool instruction execution result; feed back the API instruction execution result to the system application layer, so that the system application layer can manage the operation and maintenance release status of the system instance based on the API instruction execution result.

[0098] The tool layer generates a tool instruction execution result based on the script execution result obtained from the instance layer. Specifically, if the script execution result is a successful operation and maintenance release, the tool instruction execution result is a successful tool instruction execution; if the script execution result is a failed operation and maintenance release, the tool instruction execution result is a failed tool instruction execution. The tool layer feeds back the tool instruction execution result to the API adaptation layer, and the API adaptation layer generates an API instruction execution result based on the tool execution result. Specifically, if the tool execution result is a successful tool instruction execution, the API instruction execution is successful; if the tool instruction execution fails, the API instruction execution fails. The API adaptation layer feeds back the API instruction execution result to the system application layer, and the system application layer can determine whether the operation and maintenance release management task of the system instance is successfully executed based on the API instruction execution result, thereby realizing the operation and maintenance release management of the system instance.

[0099] The technical solution of this embodiment obtains the operation and maintenance release management task sent by the management application system in the system application layer, determines the tool execution instructions corresponding to each API execution instruction according to the task execution related information, sends the task execution related information and the tool execution instruction to the tool layer, so that the task execution tool in the tool layer can execute the tool execution instruction and generate a machine execution script, and determines the target server according to the task execution related information, sends the machine execution script to the target server, and the target server executes the machine execution script, generates and feeds back the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result. The above technical solution achieves seamless conversion between each management application system and each tool layer platform by uniformly arranging the instruction mapping relationship between API instructions and tool execution instructions, realizes effective decoupling between the operation and maintenance platform and the execution platform, and improves the efficiency, flexibility and reliability of operation and maintenance release management.

[0100] Embodiment 3

[0101] Figure 3 The structure diagram of an operation and maintenance release management device provided in the third embodiment of the present invention. The operation and maintenance release management device provided in the embodiment of the present invention can be applied to the case where the operation and maintenance release management is performed on the application instances of the same or different application systems. The operation and maintenance release management device can be implemented in the form of hardware and / or software, such as Figure 3 As shown, the device specifically includes: a task acquisition module 301, an instruction generation module 302 and an instruction delivery module 303. Among them,

[0102] The task acquisition module 301 is used to acquire the operation and maintenance release management task sent by the management application system in the system application layer; the operation and maintenance release management task includes task execution related information and at least one API execution instruction;

[0103] An instruction generation module 302 is used to determine the tool execution instructions corresponding to each of the API execution instructions according to the task execution related information;

[0104] The instruction sending module 303 is used to send the task execution related information and the tool execution instruction to the tool layer, so that the task execution tool in the tool layer executes the tool execution instruction and generates a machine execution script, and determines the target server according to the task execution related information, sends the machine execution script to the target server, and the target server executes the machine execution script, generates and feeds back the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result.

[0105] The technical solution of this embodiment obtains the operation and maintenance release management task sent by the management application system in the system application layer, determines the tool execution instructions corresponding to each API execution instruction according to the task execution related information, sends the task execution related information and the tool execution instruction to the tool layer, so that the task execution tool in the tool layer can execute the tool execution instruction and generate a machine execution script, and determines the target server according to the task execution related information, sends the machine execution script to the target server, and the target server executes the machine execution script, generates and feeds back the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result. The above technical solution achieves seamless conversion between each management application system and each tool layer platform by uniformly arranging the instruction mapping relationship between API instructions and tool execution instructions, realizes effective decoupling between the operation and maintenance platform and the execution platform, and improves the efficiency, flexibility and reliability of operation and maintenance release management.

[0106] Optionally, the instruction generation module 302 is specifically used to:

[0107] Determine the tools required for task execution based on the task execution related information;

[0108] Determine a tool instruction mapping relationship table corresponding to the tool required to perform the task;

[0109] According to the tool instruction mapping relationship table, tool execution instructions corresponding to each of the API execution instructions are generated.

[0110] Optionally, the device further comprises:

[0111] A tool execution result acquisition module, used to acquire the tool instruction execution result generated by the tool layer based on the script execution result;

[0112] An API execution result generation module, used to generate an API instruction execution result according to the tool instruction execution result;

[0113] The API execution result feedback module is used to feed back the API instruction execution result to the system application layer, so that the system application layer can manage the operation and maintenance release status of the system instance based on the API instruction execution result.

[0114] The operation and maintenance release management device provided in the embodiment of the present invention can execute the operation and maintenance release management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0115] Embodiment 4

[0116] Figure 4 A schematic diagram of an electronic device 40 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0117] like Figure 4 As shown, the electronic device 40 includes at least one processor 41, and a memory connected to the at least one processor 41, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 41 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 42 or the computer program loaded from the storage unit 48 to the random access memory (RAM) 43. In the RAM 43, various programs and data required for the operation of the electronic device 40 can also be stored. The processor 41, the ROM 42, and the RAM 43 are connected to each other through a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0118] A number of components in the electronic device 40 are connected to the I / O interface 45, including: an input unit 46, such as a keyboard, a mouse, etc.; an output unit 47, such as various types of displays, speakers, etc.; a storage unit 48, such as a disk, an optical disk, etc.; and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0119] The processor 41 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 41 executes the various methods and processes described above, such as the operation and maintenance release management method.

[0120] In some embodiments, the operation and maintenance release management method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 48. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 40 via the ROM 42 and / or the communication unit 49. When the computer program is loaded into the RAM 43 and executed by the processor 41, one or more steps of the operation and maintenance release management method described above may be performed. Alternatively, in other embodiments, the processor 44 may be configured to execute the operation and maintenance release management method in any other appropriate manner (e.g., by means of firmware).

[0121] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0122] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0123] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0124] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0125] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0126] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0127] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0128] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. An operation and maintenance release management system, characterized in that: Includes system application layer, API adaptation layer, tool layer and instance layer; The system application layer is used to manage at least one management application system and send the operation and maintenance release management tasks generated by each management application system to the API adaptation layer; The operation and maintenance release management task includes task execution related information and at least one API execution instruction; The API adaptation layer is used to determine the tool execution instructions corresponding to each of the API execution instructions according to the task execution related information, and send the task execution related information and the tool execution instructions to the tool layer; The tool layer is used to schedule the task execution tool to execute the tool execution instruction and generate a machine execution script, and determine the instance server according to the task execution related information, and send the machine execution script to the instance server in the instance layer; The instance layer is used to manage at least one instance server to execute a corresponding machine execution script, generate and feedback a script execution result, and manage the operation and maintenance release status of the system instance according to the script execution result.

2. The system according to claim 1, characterized in that Determining the tool execution instructions corresponding to the API execution instructions respectively according to the task execution related information includes: Determine the tools required for task execution based on the task execution related information; Determine a tool instruction mapping relationship table corresponding to the tool required to perform the task; According to the tool instruction mapping relationship table, tool execution instructions corresponding to each of the API execution instructions are generated.

3. The system according to claim 1, characterized in that The API adaptation layer is also used for: Obtaining a tool instruction execution result generated by the tool layer based on the script execution result; Generate an API instruction execution result according to the tool instruction execution result; The API instruction execution result is fed back to the system application layer, so that the system application layer can manage the operation and maintenance release status of the system instance based on the API instruction execution result.

4. The system according to claim 1, characterized in that The system application layer is also used for: Determine an operation and maintenance release management process; the operation and maintenance release management process includes at least one to-be-executed item having an execution order relationship; Determine the API execution instructions corresponding to each of the items to be executed; Generate an operation and maintenance release management task according to the API execution instructions of each of the items to be executed.

5. A method for operation and maintenance release management, characterized in that: The API adaptation layer applied to the operation and maintenance release management system, wherein the operation and maintenance release management system further includes a system application layer, a tool layer and an instance layer, and the method includes: Obtaining an operation and maintenance publishing management task sent by a management application system in the system application layer; the operation and maintenance publishing management task includes task execution related information and at least one API execution instruction; Determine, based on the task execution related information, tool execution instructions corresponding to each of the API execution instructions; The task execution related information and the tool execution instruction are sent to the tool layer, so that the task execution tool in the tool layer executes the tool execution instruction and generates a machine execution script, and the target server is determined according to the task execution related information, and the machine execution script is sent to the target server, and the target server executes the machine execution script, generates and feeds back the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result.

6. The method according to claim 5, characterized in that Determining the tool execution instructions corresponding to the API execution instructions respectively according to the task execution related information includes: Determine the tools required for task execution based on the task execution related information; Determine a tool instruction mapping relationship table corresponding to the tool required to perform the task; According to the tool instruction mapping relationship table, tool execution instructions corresponding to each of the API execution instructions are generated.

7. The method according to claim 5, characterized in that The method further comprises: Obtaining a tool instruction execution result generated by the tool layer based on the script execution result; Generate an API instruction execution result according to the tool instruction execution result; The API instruction execution result is fed back to the system application layer, so that the system application layer can manage the operation and maintenance release status of the system instance based on the API instruction execution result.

8. An operation and maintenance release management device, characterized in that: An API adaptation layer configured in an operation and maintenance release management system, wherein the operation and maintenance release management system further includes a system application layer, a tool layer, and an instance layer. The device includes: A task acquisition module, used to acquire an operation and maintenance release management task sent by a management application system in the system application layer; the operation and maintenance release management task includes task execution related information and at least one API execution instruction; An instruction generation module, used for determining the tool execution instructions corresponding to each of the API execution instructions according to the task execution related information; An instruction sending module is used to send the task execution related information and the tool execution instruction to the tool layer, so that the task execution tool in the tool layer executes the tool execution instruction and generates a machine execution script, and determines the target server according to the task execution related information, sends the machine execution script to the target server, and the target server executes the machine execution script, generates and feeds back the script execution result, so as to manage the operation and maintenance release status of the system instance according to the script execution result.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the operation and maintenance release management method described in any one of claims 5-6 when executed.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the computer program implements the operation and maintenance release management method according to any one of claims 5-6.

Images