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

Abstract

The embodiment of the invention provides an operation and maintenance management method and device, equipment and a computer readable storage medium. The method comprises the following steps: constructing a topology view for a software system based on application service information and resource information in the software system; based on the topology view, processing an operation work order service for the software system, the operation work order service indicating execution of configuration and management on an application service in the software system; and based on the topology view, processing an operation and maintenance work order service for the software system, the operation and maintenance work order service indicating configuration and management of resources in the software system. According to the scheme disclosed by the invention, various dependencies in a software system are cleared by constructing the topology view. Besides, work order businesses related to technicians and operation and maintenance personnel are unified in one system to process problems, so that the operation process of the work order businesses is simplified, and the operation and maintenance convenience is improved.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computer technology, and more specifically, to a method, apparatus, device, and computer-readable storage medium for operation and maintenance management. Background Art

[0002] In modern software systems, various software entities such as application services and resources need to be managed.

[0003] In related technologies, it is usually necessary to switch different systems to manage application services and resources and handle related affairs respectively, and there is no direct connection between resources and application services. When the resource or application service configuration changes, it is difficult to quickly determine whether these changes affect other application services or resources in the software system. This leads to the inability to respond to potential risks and problems in a timely manner.

[0004] Therefore, a more efficient operation and maintenance management solution is needed to deal with these problems. Summary of the invention

[0005] In a first aspect of the present disclosure, a method for operation and maintenance management is provided. The method includes: constructing a topology view for the software system based on application service information and resource information in the software system; processing an operation work order business for the software system based on the topology view, the operation work order business indicating configuration and management of application services in the software system; and processing an operation and maintenance work order business for the software system based on the topology view, the operation and maintenance work order business indicating configuration and management of resources in the software system.

[0006] In a second aspect of the present disclosure, an operation and maintenance management device is provided. The device includes: a topology module configured to construct a topology view for a software system based on application service information and resource information in the software system; an operation work order module configured to process an operation work order business for the software system based on the topology view, the operation work order business indicating configuration and management of application services in the software system; and an operation and maintenance work order module configured to process an operation and maintenance work order business for the software system based on the topology view, the operation and maintenance work order business indicating configuration and management of resources in the software system.

[0007] In a third aspect of the present disclosure, an electronic device is provided. The electronic device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit, and when the instructions are executed by the at least one processing unit, the electronic device executes the method of the first aspect of the present disclosure.

[0008] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to perform the method according to the first aspect of the present disclosure.

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

[0010] In the following, in conjunction with the accompanying drawings and with reference to the following detailed description, the above and other features, advantages and aspects of various implementations of the present disclosure will become more apparent. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0011] Figure 1 A schematic diagram showing an example environment in which embodiments of the present disclosure can be implemented;

[0012] Figure 2 A flowchart showing a process of operation and maintenance management according to some embodiments of the present disclosure is shown;

[0013] Figure 3A A schematic diagram showing a service upstream and downstream topology according to some embodiments of the present disclosure is shown;

[0014] Figure 3B A schematic diagram showing a service resource topology according to some embodiments of the present disclosure is shown;

[0015] Figure 3C A schematic diagram showing a middleware topology according to some embodiments of the present disclosure;

[0016] Figure 3D A flowchart showing a process of processing an online work order according to some embodiments of the present disclosure is shown;

[0017] Figure 3E A flowchart showing a process of processing a test work order according to some embodiments of the present disclosure is shown;

[0018] Figure 3F A flowchart showing a process of processing an operation and maintenance work order according to some embodiments of the present disclosure is shown;

[0019] Figure 4 A block diagram showing an apparatus for operation and maintenance management according to some embodiments of the present disclosure; and

[0020] Figure 5 A block diagram of an electronic device is shown in which one or more embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION

[0021] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0022] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0023] It should be noted that the acquisition, storage and application of user personal information involved in the technical solution of the present disclosure are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0024] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0025] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information, so that the user can independently choose whether to provide personal information to software or hardware such as electronic devices, applications, servers or storage media that execute operations of the technical solution of the present disclosure based on the prompt message.

[0026] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information is sent to the user in a manner such as a pop-up window, in which the prompt information can be presented in text form. In addition, the pop-up window can also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0027] As briefly mentioned above, in modern software systems, especially in complex distributed systems and microservice architectures, there are various software entities (such as various application services, database resources, host resources, domain name resources, etc.). There are also a large number of calls and dependencies between software entities. Therefore, it is necessary to operate and manage various application services and resources in the software system to handle related business. In related technologies, operation and maintenance personnel and technical personnel operate and maintain data in different systems respectively. There is no direct correlation between resource data and application service data.

[0028] Operation and maintenance personnel and R&D personnel need to log in to different systems to handle related matters, and then switch between the two systems to complete related operations. This multi-system operation increases manpower consumption. Processing a transaction requires multiple steps and coordination between systems, which reduces maintenance efficiency and increases communication costs. As the complexity of the system increases, operation and maintenance personnel and technical personnel need to handle and follow up on the same transaction, but due to the use of different systems, the problems of information asymmetry and poor communication become more prominent.

[0029] Furthermore, when the configuration of an application service or resource changes, it is difficult to quickly determine whether these changes affect other application services and resources in the software system, and which application services and resources are affected. This makes it impossible to timely assess and respond to potential risks and issues.

[0030] Therefore, if related businesses can be handled within one system from both the technical and operation and maintenance perspectives, the convenience and collaboration efficiency of operation and maintenance can be significantly improved, and communication costs can be reduced.

[0031] In view of this, an improved scheme for operation and maintenance management is proposed in the embodiments of the present disclosure. According to the embodiments of the present disclosure, a topology view for the software system is constructed based on the application service information and resource information in the software system; based on the topology view, the operation work order business for the software system is processed, and the operation work order business indicates the configuration and management of the application services in the software system; and based on the topology view, the operation and maintenance work order business for the software system is processed, and the operation and maintenance work order business indicates the configuration and management of the resources in the software system. Thus, by constructing a topology view, various dependencies in the software system are clarified. And it is possible to integrate the configuration and management of application services and resources from the technical perspective and the operation and maintenance perspective into one system, thereby improving the overall operation and maintenance efficiency, reducing communication costs, and ensuring the efficient operation of systems and services. In addition, when a failure or configuration change occurs, the impact of the failure or change on other parts of the system can be quickly understood, so that timely and effective decisions can be made.

[0032] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0033] Figure 11 is a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Figure 1 In the environment 100, the electronic device 110 can build a topology view 140 for the software system based on the application service information 120 and the resource information 130 in the software system. Based on the topology view 140, the electronic device 110 can process an operation work order service 150 for the software system. In some embodiments, the operation work order service 150 indicates the configuration and management of the application service in the software system. Based on the topology view 140, the electronic device 110 can also process an operation and maintenance work order service 160 for the software system. In some embodiments, the operation and maintenance work order service 160 indicates the configuration and management of the resources in the software system.

[0034] exist Figure 1 In the embodiment, the electronic device 110 may include any computing system with computing capabilities, such as various computing devices / systems, terminal devices, servers, etc. The terminal device may involve any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. The server includes but is not limited to a mainframe, an edge computing node, a computing device in a cloud environment, and the like.

[0035] It should be understood that Figure 1 The components and arrangements in the environment 100 shown are merely examples, and a computing system suitable for implementing the exemplary implementation described in the present disclosure may include one or more different components, other components, and / or different arrangements. The implementation of the present disclosure is not limited in this respect.

[0036] Figure 2 A flowchart of a process 200 of operation and maintenance management according to some embodiments of the present disclosure is shown. The process 200 may be implemented in the environment 100 , for example, the process 200 may be implemented at the electronic device 110 .

[0037] In block 210 , the electronic device 110 constructs a topology view for the software system based on application service information and resource information in the software system.

[0038] In some embodiments, application service information may include a name or ID for identifying an application service; configuration parameters required for the application service to run (e.g., port number, environment variables, etc.); the calling relationship between the application service and other services; the current running state of the service (e.g., start, stop, abnormal, etc.); and information such as resources associated with the service. Resource information may include a name or ID for identifying an application service; configuration parameters of resources (e.g., central processing unit (CPU), memory, storage capacity, etc.); the current running state of resources (e.g., available, unavailable, abnormal, etc.); the dependency relationship between resources and application services; resource usage, and other information.

[0039] In some embodiments, the topology view for the software system includes at least one of the following: service upstream and downstream topology, which is used to display the calling relationship between various application services; service resource topology, which is used to display the resources associated with each application service; and middleware topology, which is used to display the application services associated with each middleware.

[0040] The service upstream and downstream topology shows the calling relationship between various application services. The service upstream and downstream topology is used to reveal the dependency relationship between services, that is, which services are called and which services call other services. Through the service upstream and downstream topology, you can clearly understand the interaction between various services in the system, help locate problems and optimize performance.

[0041] The service resource topology shows the resources associated with each application service. The service resource topology helps you understand the resources used by each service and the scope of the impact of resources on business data. This can help better manage and optimize system resources.

[0042] The middleware topology shows the relationship between each middleware and application service. Middleware resources are a specific type of resource in the software system that can coordinate the communication, data transmission, and state management between different parts. For example, middleware resources can include message queue systems, database management systems, cache systems, etc. Middleware resources play an important role in the system architecture and are usually shared and relied upon by multiple application services. Therefore, it is also very important to understand the dependency relationship between middleware resources and application services.

[0043] In some embodiments, the calling relationship between services can be represented by arrows in the topology view, and the arrows point to the called services, reflecting the direction of the calling relationship. Figure 3A , Figure 3A FIG. 1 is a schematic diagram showing an example service upstream and downstream topology according to some embodiments of the present disclosure. Figure 3AAs shown, application service A calls application service B, and application service B calls application service C and application service D. In this case, the node corresponding to application service B (also called node B) is the downstream node of the node corresponding to application service A (also called node A), and node A is the upstream node of node B. Similarly, the node corresponding to application service C (also called node C) and the node corresponding to application service D (also called node D) are both downstream nodes of node B, and node B is the upstream node of node C and node D. In the upstream and downstream service topology corresponding to application service B, node A is the starting node, node B is the destination node of node A, and node C and node D are the destination nodes of node B. In the topology view, there will be arrows pointing from node A to node B and from node B to node C and node D to indicate the calling relationship between them. Of course, for the purpose of explanation, in Figure 3A A simple example of the upstream and downstream topology of services is shown in FIG. 1 , but in actual applications, the topology may include more nodes and more complex calling relationships.

[0044] For example, please refer to Figure 3B , Figure 3B FIG. 1 is a schematic diagram showing a service resource topology according to some embodiments of the present disclosure. Figure 3B As shown, the software system includes application service C, and the resources that application service C depends on include resource 1, resource 2, resource 3, middleware a and middleware b. Then the electronic device 110 can construct the service resource topology by taking the node corresponding to application service C as the starting node and taking the nodes corresponding to all resources associated with the service, resource 1, resource 2, resource 3, middleware a and middleware b as the destination nodes. Of course, for the purpose of explanation, Figure 3B A simple example of a service resource topology is shown in FIG. 1 , but in actual applications the topology may include more nodes and more complex call relationships.

[0045] For example, please refer to Figure 3C , Figure 3C A schematic diagram of a middleware topology according to some embodiments of the present disclosure is shown. In the software system, application services A, B, and D all need to use middleware resource a. Therefore, the node corresponding to middleware a can be used as the starting node, and the nodes corresponding to application services A, B, and D can be used as the destination node to construct the middleware topology. Of course, for the purpose of explanation, Figure 3C A simple example of a middleware topology is shown in FIG. 1 , but in actual applications the topology may include more nodes and more complex call relationships.

[0046] In some embodiments, the electronic device 110 can configure and manage application service information in a service management database (SMDB). For example, view and manage the application service list; add and modify application service information, etc. The electronic device 110 can also view resource information in a configuration management database (CMDB). In addition, the electronic device 110 can synchronize resource information from the cloud platform to the configuration management database at regular intervals.

[0047] In some embodiments, the electronic device 110 may associate the SMDB and the CMDB through the constructed topology view.

[0048] As an example, each application service runs on a specific host or server when deployed and has its specific host Internet Protocol Address (IP) address (also called host IP). For example, in the application service information recorded in the SMDB, application service A runs on host IP1. In the resource information recorded in the CMDB, the application services that depend on host IP1 include application service A. Therefore, the application service information in the SMDB can be associated with the resource information in the CMDB by building a topology view. And the jump view from application service to resource can be realized through the service resource topology in the topology view, and the jump view from resource to its associated application service can be realized through the middleware topology in the topology view.

[0049] Continue to refer Figure 2 In box 220, the electronic device 110 processes the operation work order business for the software system based on the topology view.

[0050] In some embodiments, running a work order service indicates performing configuration and management on an application service in a software system to ensure normal development, testing, and launch of the application service.

[0051] In some embodiments, running a work order service includes at least one of the following: an online work order, a test work order.

[0052] The launch ticket indicates that the first application service is deployed to the software system. The launch ticket refers to a task ticket used to manage and record the launch of the application service (deployment to the production environment) during the development and operation process. The launch ticket can contain detailed information and steps in the launch process to ensure that the application service can be deployed to the production environment smoothly and without error.

[0053] The test work order indicates that a test operation is performed on the second application service. A test work order refers to a work order used to manage and record tasks for submitting application services for testing during the development and operation and maintenance process. The test work order can ensure that all functions and modules that need to be tested are strictly verified. Among them, performing a test operation on the second application service can refer to performing a test operation on the first application service that needs to be launched, or performing a test operation on other application services that need to be tested in the software system.

[0054] For example, please refer to Figure 3D , Figure 3D A flowchart of processing an on-line work order 300A according to some embodiments of the present disclosure is shown.

[0055] In block 311 , the electronic device 110 determines a first application service to be launched as indicated by the launch work order.

[0056] In some embodiments, the electronic device can create an online work order based on the application service information in the software system. As an example, the online work order can specifically include the following contents: Create an online work order: create a new work order to record and manage the upcoming online operation; Select online service: select the application service that needs to be launched; Select service tag: select the version or tag of the application service to ensure the specific version of the online; Online check items: list the items that need to be checked before going online to ensure the smooth progress of the online operation; Configure relevant personnel: including technical personnel, approval personnel, etc. related to the online work order, so that effective collaboration and communication can be carried out during the online process.

[0057] In some embodiments, through the online work order, the electronic device 110 can determine the first application service that needs to be deployed to the production environment.

[0058] In block 312 , the electronic device 110 may determine a first impact scope of the launch of the first application service on other application services and resources in the software system based on the service upstream and downstream topology and the service resource topology in the topology view.

[0059] In some embodiments, when a new application service is to be launched, it is necessary to evaluate the impact of this operation on the entire system, such as potential system performance issues, dependency conflicts, and resource competition.

[0060] Through the service upstream and downstream topology, the electronic device 110 can identify which other application services the first application service that is online has dependencies on. Understanding these dependencies helps determine which services may be affected. For example, the online service A may affect the service C that depends on it. Through the service resource topology, the electronic device 110 can identify which resources the online service has dependencies on. Understanding these resource dependencies helps determine which resources may be affected by increased load, configuration changes, etc. For example, the online service A may increase the load on the database resources it depends on and there may be resource competition issues.

[0061] In block 313 , the electronic device 110 may determine an approval result for the online work order based on the first impact scope.

[0062] In some embodiments, the approval result indicates whether the application service is allowed to go online. For example, if the online launch of the application service does not affect other application services and resources in the system or the impact on other application services and resources in the system is within a controllable range based on the first impact scope, and sufficient countermeasures are in place, the approval result will show that it is allowed to go online. If the online launch of the application service has too great an impact on important services or resources in the system based on the first impact scope, and it is difficult to take effective countermeasures, the approval result will show that it is not allowed to go online.

[0063] In some embodiments, the electronic device 110 can present the approval status of the online work order, specifically including: pending: the online work order has been created, but processing has not yet begun, waiting for the current user's approval or further operation; processed: the online work order has been approved by the current user; submitted: the online work order created and submitted by the current user, and the approval status of the online work order submitted by the current user can be viewed.

[0064] In some embodiments, the online work order can also include an emergency deployment work order, which is a simplified version of the online work order, used in emergency situations where the application service needs to be quickly launched. Only users with corresponding permissions can create and execute this work order. It simplifies the approval process to quickly respond to emergency needs.

[0065] In the disclosed embodiment, the application services that need to be launched are identified through the online work order, ensuring that the online process of a specific application service is managed. In addition, the dependencies between application services and between application services and resources are fully understood through the topology view, and the impact of the online operation on the entire system can be accurately evaluated. Based on the results of the impact range assessment, the online work order is approved to decide whether to allow the application service to go online, which improves the accuracy of risk assessment and the scientific nature of decision support, and ensures the security and reliability of the application service online process.

[0066] For example, please refer to Figure 3E, Figure 3E A flowchart of processing a test work order 300B according to some embodiments of the present disclosure is shown.

[0067] In block 321 , the electronic device 110 determines a second application service to be submitted for testing as indicated by the test work order.

[0068] In some embodiments, the electronic device 110 can create a test work order based on the application service information and resource information in the software system. As an example, the test work order may specifically include the following contents: Create a test work order: create a new work order to record and manage the upcoming test operations; Select a test service: select the application service to be tested; Priority selection: the priority of the test task indicated by the test work order; Test content: the functional module to be tested and the specific content description; Configure relevant personnel: including the person who submitted the test work order and the technical personnel and approval personnel related to the test work order.

[0069] In some embodiments, through the test work order, the electronic device 110 can determine the second application service that needs to be tested in the test environment.

[0070] In block 322 , the electronic device 110 determines a second impact scope of the submission test of the second application service on other application services and resources in the software system based on the service upstream and downstream topology and the service resource topology in the topology view.

[0071] In some embodiments, when testing a new application service, it is necessary to evaluate the impact of this operation on the entire system. For example, the test process may occupy a large amount of computing resources, storage resources or network bandwidth, thereby affecting other application services running at the same time. Or the application service being tested may have interactive interfaces with other services, and these interfaces may be triggered during the test, thereby affecting the normal operation of other services.

[0072] The service upstream and downstream topology and service resource topology can be used to display the dependencies between services and between services and resources, which can help identify other services or resources that may be affected by the application service submitted for testing.

[0073] In block 323 , the electronic device 110 may determine an approval result for the test work order based on the second impact scope.

[0074] In some embodiments, the approval result indicates whether the application service is allowed to submit the test. For example, the scope of influence is determined based on the information provided by the topology view, and the approval decision is made. If it is determined based on the second scope of influence that the resources occupied by the test operation are within the controllable range and do not affect the normal operation of other application services, the test work order is approved; if the test operation occupies key resources in the system, causing the key application service to be unable to operate normally, the approval result indicates that additional preventive measures need to be formulated or the test work order is rejected.

[0075] In some embodiments, the electronic device 110 can present the approval status of the test work order, specifically including: pending: the test work order has been created, but processing has not yet begun, waiting for the current user's approval or further operation; processed: the test work order has been approved by the current user; submitted: the test work order created and submitted by the current user, and the approval status of the test work order submitted by the current user can be viewed.

[0076] In the disclosed embodiment, the application service submitted for testing is clearly identified through the test work order, ensuring that the test work is clearly directed. The dependencies between application services and between application services and resources are fully understood through the topology view, and the impact of the test on other parts of the system is accurately evaluated. According to the results of the impact range assessment, the test work order is approved, the approval decision process is optimized, and system failures caused by tests that do not comprehensively consider the impact of the system are reduced.

[0077] Continue to refer Figure 2 In box 230, the electronic device 110 processes the operation and maintenance work order business for the software system based on the topology view.

[0078] In some embodiments, the operation and maintenance work order business instructions perform configuration and management on resources in the software system to ensure stable operation of the system and effective use of resources.

[0079] For example, please refer to Figure 3F , Figure 3F A flowchart of a process 300C for processing an operation and maintenance work order according to some embodiments of the present disclosure is shown.

[0080] In box 331, the electronic device 110 determines the resources for which change is requested as indicated in the operation and maintenance work order.

[0081] In some embodiments, the electronic device 110 can determine resource changes in the software system based on the operation and maintenance work order, such as adding, deleting, and modifying cloud resource configuration (such as computing resources, storage resources, and network configuration), application service configuration changes (such as modifying service parameters and updating middleware versions), etc.

[0082] In some embodiments, the electronic device 110 can create an operation and maintenance work order based on the application service information and resource information in the software system. As an example, the operation and maintenance work order may specifically include the following contents: Create an operation and maintenance work order: record the operation and maintenance operation to be performed; Change selection application: select the type of resource change operation, such as requesting to create or modify a user account, requesting to allocate or adjust the resources of the software system, requesting to grant or adjust system permissions, requesting to make specific configuration changes or adjustments to the system, etc.; Application reason description: describe in detail the reason for applying for resource change.

[0083] In block 332 , the electronic device 110 determines a third impact scope of the resource change on other application services and resources in the software system based on the service resource topology and the middleware topology in the topology view.

[0084] In some embodiments, when changing resources in the system, it is necessary to evaluate the scope of impact of this operation on the entire system. For example, resource changes may cause services that rely on these resources to be temporarily interrupted or unavailable; resource changes (such as adjusting the CPU and memory configuration) may affect the performance of the service; middleware or configuration changes may also cause compatibility issues; changes involving database or storage resources may affect data consistency.

[0085] Based on the service resource topology and middleware topology in the topology view, you can view the location of the changed resources in the topology map and which application services have direct dependencies. For example, if you upgrade the database version, you can view which services use the database. Through the topology map, you can further analyze other services associated with the directly dependent services and evaluate the indirect impact that the change may bring. For example, service A depends on middleware B, and middleware B affects service C and service D. Combine direct and indirect dependencies to determine the scope of impact and clarify all services and resources that may be affected by the change.

[0086] In box 333 , the electronic device 110 determines the approval result of the operation and maintenance work order based on the third impact scope.

[0087] In some embodiments, the approval result indicates whether the resource has been changed. For example, if the third impact scope indicates that the resource change operation only affects a small number of application services or resources in the system and the risk is controllable, the approval result may be to approve the operation and maintenance work order and allow the change operation to proceed. If the change involves important application services or widely affects multiple services or resources, the approval result may be to reject the operation and maintenance work order and prohibit the change operation from proceeding.

[0088] In some embodiments, the electronic device 110 can present the approval status of the operation and maintenance work order, specifically including: pending: the operation and maintenance work order has been created, but processing has not yet begun, waiting for the current user's approval or further operation; processed: the operation and maintenance work order has been approved by the current user; submitted: the operation and maintenance work order created and submitted by the current user, and the approval status of the operation and maintenance work order submitted by the current user can be viewed.

[0089] In the disclosed embodiment, the operation and maintenance work order is used to manage and record the various operations and change processes of the system resources that the operation and maintenance personnel need to perform. In addition, the impact range of the resource change operation is evaluated through the topology view, so that the risks and potential problems that may be caused by the change can be more accurately identified, thereby reducing the risk of system failures and service interruptions and improving operation and maintenance efficiency.

[0090] In some embodiments, the electronic device 110 can record the operation work order business and the impact of the operation work order business on other application services and resources in the software system. The electronic device 110 can also record the operation and maintenance work order business and the impact of the operation and maintenance work order business on other application services and resources in the software system.

[0091] In some embodiments, the electronic device 110 records the application service launch, test, resource change operations indicated by the launch work order, test work order, and operation and maintenance work order, as well as the results and impacts of these operations. The electronic device 110 can also record and analyze the recorded operations, including the time of occurrence of the work order operation, the content of the operation, the executor, the approver, and other information, for subsequent tracing and analysis.

[0092] In the disclosed embodiment, the electronic device 110 records the work order business operations and the scope of impact on the system to better identify and manage potential risks, more effectively plan and optimize the use of resources, reduce the possibility of system failures and service interruptions, and help improve the team's operation and maintenance efficiency and system stability.

[0093] Figure 4 1 is a block diagram of an apparatus 400 for operation and maintenance management according to some embodiments of the present disclosure. The apparatus 400 may be implemented as or included in the electronic device 110. An apparatus.

[0094] The device 400 includes a topology module 410, which is configured to construct a topology view for the software system based on the application service information and resource information in the software system; an operation work order module 420, which is configured to process the operation work order business for the software system based on the topology view, and the operation work order business indicates the execution of configuration and management of application services in the software system; and an operation and maintenance work order module 430, which is configured to process the operation and maintenance work order business for the software system based on the topology view, and the operation and maintenance work order business indicates the execution of configuration and management of resources in the software system.

[0095] In some embodiments, the topology view for the software system includes at least one of the following: service upstream and downstream topology, which is used to display the calling relationship between various application services; service resource topology, which is used to display the resources associated with each application service; and middleware topology, which is used to display the application services associated with each middleware.

[0096] In some embodiments, running a work order service includes at least one of the following: an online work order, the online work order instructs deployment of a first application service to a software system; and a test work order, the test work order instructs execution of a test operation on a second application service.

[0097] In some embodiments, the operation work order module 420 is further configured to: determine the first application service to be launched as indicated by the online work order; determine the first impact scope of the launch of the first application service on other application services and resources in the software system based on the service upstream and downstream topology and service resource topology in the topology view; and determine the approval result of the online work order based on the first impact scope, and the approval result indicates whether the application service is allowed to go online.

[0098] In some embodiments, the running work order module 420 is further configured to: determine the second application service to be submitted for testing indicated by the test work order; determine the second impact scope of the submitted test of the second application service on other application services and resources in the software system based on the service upstream and downstream topology and service resource topology in the topology view; and determine the approval result of the test work order based on the second impact scope, and the approval result indicates whether the application service is allowed to submit for testing.

[0099] In some embodiments, the operation and maintenance work order module 430 is further configured to: determine the resources for which change is requested as indicated in the operation and maintenance work order; determine a third impact scope of the resource change on other application services and resources in the software system based on the service resource topology and middleware topology in the topology view; and determine an approval result for the operation and maintenance work order based on the third impact scope, the approval result indicating whether the resource has been changed.

[0100] In some embodiments, the device 400 also includes a recording module 440, which is configured to record the operation of the work order business and the scope of impact of the operation of the work order business on other application services and resources in the software system; and to record the operation and maintenance work order business and the scope of impact of the operation and maintenance work order business on other application services and resources in the software system.

[0101] The modules included in the device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units in the device 400 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0102] Figure 5 1 shows a block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 5 The electronic device 500 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. The electronic device 500 may be implemented as or included in Figure 1 Electronic device 110 or Figure 4 In the device 400.

[0103] like Figure 5 As shown, the electronic device 500 is in the form of a general electronic device. The components of the electronic device 500 may include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 520. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 500.

[0104] The electronic device 500 typically includes a plurality of computer storage media. Such media may be any available media accessible to the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 may be a volatile memory (e.g., registers, caches, random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data and may be accessed within the electronic device 500.

[0105] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 5 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.

[0106] The communication unit 540 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented in a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 500 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0107] The input device 550 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 560 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 500 may also communicate with one or more external devices (not shown) through the communication unit 540 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 500, or communicate with any device that allows the electronic device 500 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0108] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which one or more computer instructions are stored, wherein the one or more computer instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0109] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0110] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0111] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0112] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0113] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the marketplace, or to enable other persons of ordinary skill in the art to understand the implementations disclosed herein.

Claims

1. An operation and maintenance management method, comprising: Based on the application service information and resource information in the software system, construct a topology view for the software system; Based on the topology view, processing an operation work order service for the software system, wherein the operation work order service indicates configuration and management of application services in the software system; as well as Based on the topology view, an operation and maintenance work order service for the software system is processed, wherein the operation and maintenance work order service indicates configuration and management of resources in the software system.

2. The method according to claim 1, wherein the topology view for the software system comprises at least one of the following: The service upstream and downstream topology is used to show the calling relationship between various application services. The service resource topology is used to display the resources associated with each application service. The middleware topology is used to display application services respectively associated with each middleware.

3. The method according to claim 1, wherein the running of the work order business comprises at least one of the following: an on-line work order, the on-line work order instructing to deploy the first application service to the software system; and A test work order, wherein the test work order instructs to perform a test operation on the second application service.

4. The method according to claim 3, wherein processing the operation work order business for the software system based on the topology view comprises: Determine the first application service to be put online as indicated by the online work order; Determine a first impact scope of the launch of the first application service on other application services and resources in the software system based on the service upstream and downstream topology and the service resource topology in the topology view; as well as Based on the first impact scope, an approval result of the online work order is determined, and the approval result indicates whether the application service is allowed to go online.

5. The method according to claim 3, wherein processing the operation work order business for the software system based on the topology view comprises: Determine the second application service to be submitted for testing indicated by the test work order; Determine, based on the service upstream and downstream topology and the service resource topology in the topology view, a second impact scope of the submission test of the second application service on other application services and resources in the software system; as well as Based on the second impact scope, an approval result of the test work order is determined, and the approval result indicates whether the application service is allowed to submit for testing.

6. The method according to claim 1, wherein processing the operation and maintenance work order business for the software system based on the topology view comprises: Determine the resources for which change is requested as indicated in the operation and maintenance work order; Determine, based on the service resource topology and the middleware topology in the topology view, a third impact scope of the resource change on other application services and resources in the software system; as well as Based on the third impact scope, an approval result of the operation and maintenance work order is determined, and the approval result indicates whether the resource is changed.

7. The method according to claim 1, further comprising: Record the operation of the work order business and the impact of the operation of the work order business on other application services and resources in the software system; as well as Record the operation and maintenance work order business and the impact of the operation and maintenance work order business on other application services and resources in the software system.

8. An operation and maintenance management device, comprising: A topology module, configured to construct a topology view for the software system based on application service information and resource information in the software system; An operation work order module is configured to process an operation work order service for the software system based on the topology view, wherein the operation work order service indicates configuration and management of application services in the software system; as well as The operation and maintenance work order module is configured to process the operation and maintenance work order business for the software system based on the topology view, and the operation and maintenance work order business indicates the configuration and management of resources in the software system.

9. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to execute the system according to any one of claims 1 to 7 when executed by the at least one processing unit.

10. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the system according to any one of claims 1 to 7.

Images