Operation and maintenance strategy generation method and device, equipment, storage medium and program product

Abstract

The invention provides an operation and maintenance strategy generation method which can be applied to the technical field of big data. The operation and maintenance strategy generation method comprises the following steps: in response to an instruction for executing an operation and maintenance task, determining target to-be-operated and to-be-maintained software associated with the operation and maintenance task; determining at least one association link corresponding to the operation and maintenance task based on a pre-constructed software relationship library; determining a target associated component node from the at least one associated component node based on the associated link; reading a target software information set corresponding to the target to-be-operated and to-be-maintained software node from a software relationship library, and reading a target associated component information set corresponding to the target associated component node; and based on the target software information set and the target associated component information set, determining an operation and maintenance strategy for the target to-be-operated and to-be-maintained software. The invention further provides an operation and maintenance strategy generation device and equipment, a storage medium and a program product.

Description

Technical Field

[0001] The present disclosure relates to the field of big data technology, and more specifically to an operation and maintenance strategy generation method, device, equipment, storage medium and program product. Background Art

[0002] As the scale of enterprises expands and businesses continue to evolve, the interdependencies between software become increasingly complex, and the constant changes in software operation and maintenance requirements increase the difficulty of software operation and maintenance. The existing method of determining software operation and maintenance strategies is usually to determine the rules and processes of software operation and maintenance by reading pre-established software operation and maintenance documents.

[0003] In the process of realizing the concept of the present disclosure, the inventors found that there are at least the following problems in the related technology: (1) The software operation and maintenance documents prepared by different personnel may be different, resulting in the problem of non-standardization of software operation and maintenance documents, which in turn increases the difficulty for operation and maintenance personnel to determine the rules and processes of software operation and maintenance based on the software operation and maintenance documents. (2) The software operation and maintenance documents describe the rules and processes of software operation and maintenance in text form. This method of relying on text description to obtain rules and processes is inefficient, and due to different personal understandings of text, it is very easy to cause misunderstandings, which seriously hinders the development and maintenance personnel from accurately controlling the overall software system. (3) The software operation and maintenance documents lack information transmission methods such as numbers and codes, which greatly increases the difficulty of software installation, maintenance, migration and upgrading, and the information flow is not smooth, which is not conducive to tracking and analyzing the use of function points. Summary of the invention

[0004] In view of the above problems, the present disclosure provides a method, apparatus, device, storage medium and program product for generating an operation and maintenance strategy.

[0005] According to a first aspect of the present disclosure, a method for generating an operation and maintenance strategy is provided, comprising: in response to an instruction to execute an operation and maintenance task, determining a target software to be operated and maintained associated with the operation and maintenance task; based on a pre-built software relationship library, determining at least one association link corresponding to the operation and maintenance task, wherein the association link comprises: a target software to be operated and maintained node corresponding to the target software to be operated and maintained, and at least one association component node corresponding to at least one association component, and a dependency relationship exists between the association component and the target software to be operated and maintained; based on the association link, determining a target association component node from at least one association component node; reading a target software information set corresponding to the target software to be operated and maintained node from the software relationship library, and reading a target association component information set corresponding to the target association component node; and determining an operation and maintenance strategy for the target software to be operated and maintained based on the target software information set and the target association component information set.

[0006] According to an embodiment of the present disclosure, based on a target software information set and a target associated component information set, determining an operation and maintenance strategy for the target software to be operated and maintained includes: determining first operation and maintenance information related to the operation and maintenance task based on the target software information set; determining second operation and maintenance information related to the operation and maintenance task based on the target associated component information set; and determining an operation and maintenance strategy for the target software to be operated and maintained based on the first operation and maintenance information and the second operation and maintenance information.

[0007] According to an embodiment of the present disclosure, an associated component node includes a parent associated component node and a child associated component node; based on an associated link, determining a target associated component node from at least one associated component node includes: based on the associated link, determining a parent associated component node corresponding to the target software to be operated and maintained, and a child associated component node corresponding to the target software to be operated and maintained; based on the parent associated component node and the child associated component node, determining a target associated component node from at least one associated component node.

[0008] According to an embodiment of the present disclosure, the operation and maintenance strategy generation method also includes: determining multiple software to be operated and maintained, and components associated with each software to be operated and maintained, wherein the multiple software to be operated and maintained include target software to be operated and maintained; based on the multiple software to be operated and maintained, and components associated with each software to be operated and maintained, constructing a software relationship library.

[0009] According to an embodiment of the present disclosure, based on multiple software to be maintained and components associated with each software to be maintained, constructing a software relationship library includes: determining first variable configuration information corresponding to each software to be maintained; based on the first variable configuration information, determining first basic operation and maintenance information corresponding one-to-one to each software to be maintained, the first basic operation and maintenance information including at least one of the following: attribute information, access control information, software management configuration information and association relationship information of the software to be maintained; based on the first basic operation and maintenance information, generating a software information set corresponding one-to-one to each software to be maintained, the software information set including a target software information set.

[0010] According to an embodiment of the present disclosure, based on multiple software to be maintained and components associated with each software to be maintained, constructing a software relationship library also includes: determining second variable configuration information corresponding to each component; based on the second variable configuration information, determining second basic operation and maintenance information corresponding to the component; based on the second basic operation and maintenance information, generating an associated component information set corresponding to each component one by one, the associated component information set including a target associated component information set.

[0011] According to an embodiment of the present disclosure, based on multiple software to be maintained, building a software relationship library also includes: screening out multiple initial software to be maintained that have dependency relationships from the multiple software to be maintained; determining the dependency directions between the multiple initial software to be maintained; determining the dependency directions between components associated with each software to be maintained; and determining at least one association link based on the dependency directions between the multiple initial software to be maintained and the dependency directions between components associated with each software to be maintained.

[0012] The second aspect of the present disclosure provides an operation and maintenance strategy generation device, including: a first determination module, which is used to determine the target software to be operated and maintained associated with the operation and maintenance task in response to an instruction to execute the operation and maintenance task; a second determination module, which is used to determine at least one association link corresponding to the operation and maintenance task based on a pre-built software relationship library, wherein the association link includes: a target software node to be operated and maintained corresponding to the target software to be operated and maintained, and at least one association component node corresponding to at least one association component, and the association component has a dependency relationship with the target software to be operated and maintained; a third determination module, which is used to determine the target association component node from at least one association component node based on the association link; a reading module, which is used to read the target software information set corresponding to the target software node to be operated and maintained from the software relationship library, and read the target association component information set corresponding to the target association component node; a fourth determination module, which is used to determine the operation and maintenance strategy for the target software to be operated and maintained based on the target software information set and the target association component information set.

[0013] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0014] The fourth aspect of the present disclosure further provides a computer-readable storage medium having a computer program or instructions stored thereon, which implements the steps of the above method when the above computer program or instructions are executed by a processor.

[0015] The fifth aspect of the present disclosure further provides a computer program product, including a computer program or instructions, which implement the steps of the above method when the above computer program or instructions are executed by a processor.

[0016] According to the embodiments of the present disclosure, by directly reading the target software information set and the target associated component set from the software relationship library, it is possible to simply and accurately know which software will be affected by executing the operation and maintenance tasks, and to know the basic information of the target software to be operated and maintained, so that the operation and maintenance strategy can be accurately and efficiently determined based on the above information, without having to determine the rules and processes of software operation and maintenance by reading complex and non-standardized software operation and maintenance documents. This fundamentally eliminates the difficulty of operation and maintenance work caused by deviations in text understanding, reduces the workload of operation and maintenance personnel, improves software operation and maintenance efficiency, and improves the accuracy of operation and maintenance strategies. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] Figure 1 The application scenario diagram of the operation and maintenance strategy generation method, apparatus, device, medium and program product according to the embodiment of the present disclosure is schematically shown;

[0019] Figure 2 A flowchart of a method for generating an operation and maintenance strategy according to an embodiment of the present disclosure is schematically shown;

[0020] Figure 3 A schematic diagram schematically shows a software information set according to an embodiment of the present disclosure;

[0021] Figure 4 A schematic diagram schematically shows a software relationship library according to an embodiment of the present disclosure;

[0022] Figure 5 A schematic diagram schematically shows a database set according to an embodiment of the present disclosure;

[0023] Figure 6 A structural block diagram of an operation and maintenance strategy generating device according to an embodiment of the present disclosure is schematically shown; and

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

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

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

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

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

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

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

[0031] In the scenario of using personal information for automated decision-making, the methods, devices, and systems provided by the embodiments of the present disclosure provide users with corresponding operation portals for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered. The expression "automated decision-making" here refers to the activity of automatically analyzing and evaluating a person's behavioral habits, interests and hobbies, or economic, health, credit status, etc. through computer programs, and making decisions. The expression "expert decision-making" here refers to the activity of making decisions by people who specialize in a certain field, have specialized experience, knowledge and skills, and have reached a certain level of professionalism.

[0032] It should be noted that the operation and maintenance strategy generation method and device disclosed in the present invention can be used in the field of big data technology, and can also be used in any field other than the field of big data technology. The application field of the operation and maintenance strategy generation method and device disclosed in the present invention is not limited.

[0033] An embodiment of the present disclosure provides an operation and maintenance strategy generation method, comprising: in response to an instruction to execute an operation and maintenance task, determining a target software to be operated and maintained associated with the operation and maintenance task; based on a pre-built software relationship library, determining at least one association link corresponding to the operation and maintenance task, wherein the association link comprises: a target software to be operated and maintained node corresponding to the target software to be operated and maintained, and at least one association component node corresponding to at least one association component, and the association component has a dependency relationship with the target software to be operated and maintained; based on the association link, determining a target association component node from at least one association component node; reading a target software information set corresponding to the target software to be operated and maintained node from the software relationship library, and reading a target association component information set corresponding to the target association component node; based on the target software information set and the target association component information set, determining an operation and maintenance strategy for the target software to be operated and maintained.

[0034] Figure 1 The following schematically shows an application scenario diagram of the operation and maintenance strategy generation method, apparatus, device, medium, and program product according to an embodiment of the present disclosure. Figure 1 As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104 and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

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

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

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

[0038] For example, the user may initiate an instruction to perform an operation and maintenance task through any one of the first terminal device 101, the second terminal device 102, or the third terminal device 103 (for example, the first terminal device 101, but not limited thereto). In response to the above instruction, the server 105 may be used to execute the operation and maintenance strategy generation method of the embodiment of the present disclosure, including: in response to the instruction to perform the operation and maintenance task, determining the target software to be operated and maintained associated with the operation and maintenance task; based on the pre-built software relationship library, determining at least one association link corresponding to the operation and maintenance task, wherein the association link includes: a target software node to be operated and maintained corresponding to the target software to be operated and maintained, and at least one association component node corresponding to at least one association component, and the association component has a dependency relationship with the target software to be operated and maintained; based on the association link, determining the target association component node from at least one association component node; reading the target software information set corresponding to the target software node to be operated and maintained from the software relationship library, and reading the target association component information set corresponding to the target association component node; based on the target software information set and the target association component information set, determining the operation and maintenance strategy for the target software to be operated and maintained.

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

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

[0041] The following will be based on Figure 1 The scene described by Figure 2~Figure 5The operation and maintenance strategy generation method of the disclosed embodiment is described in detail.

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

[0043] like Figure 2 As shown, the operation and maintenance strategy generation method of this embodiment includes operations S210 to S250.

[0044] In operation S210 , in response to an instruction to execute an operation and maintenance task, target software to be operated and maintained associated with the operation and maintenance task is determined.

[0045] In operation S220, based on a pre-built software relationship library, at least one association link corresponding to the operation and maintenance task is determined, wherein the association link includes: a target software node corresponding to the target software to be operated and maintained, and at least one associated component node corresponding to at least one associated component, and there is a dependency relationship between the associated component and the target software to be operated and maintained.

[0046] In operation S230, a target associated component node is determined from at least one associated component node based on the associated link.

[0047] In operation S240, a target software information set corresponding to the target software node to be operated and maintained is read from the software relationship library, and a target associated component information set corresponding to the target associated component node is read.

[0048] In operation S250, an operation and maintenance strategy for the target software to be operated and maintained is determined based on the target software information set and the target associated component information set.

[0049] According to the embodiments of the present disclosure, most of the methods for determining operation and maintenance strategies require reading pre-established software operation and maintenance files to determine the rules and processes of software operation and maintenance, which results in the need to read a large number of software operation and maintenance files when determining operation and maintenance tasks, increasing the workload of operation and maintenance personnel, and may miss important content in the software operation and maintenance files; in addition, there is a problem of non-standardization in software operation and maintenance files, which increases the reading difficulty for operation and maintenance personnel; since software operation and maintenance files describe the rules and processes of software operation and maintenance in text form, operation and maintenance personnel have different understandings of text, resulting in deviations in the understanding of software operation and maintenance files, which in turn leads to inaccurate operation and maintenance strategies; in addition, software operation and maintenance files may also be lost and have a low degree of dataization, further increasing the difficulty of operation and maintenance. Therefore, in order to reduce the workload of operation and maintenance personnel and reduce the difficulty of operation and maintenance, a software relationship library can be constructed, and the relevant information of the software to be operated and maintained can be intuitively presented through the software relationship library, so that the operation and maintenance strategy can be determined simply and accurately.

[0050] According to an embodiment of the present disclosure, in operation S210, the operation and maintenance task may be to perform operations such as installation, maintenance, migration, and upgrade of software, and the operation and maintenance object of the operation and maintenance task is the software to be operated and maintained. The target software to be operated and maintained may be software corresponding to the operation and maintenance task. For example, the operation and maintenance task may be to upgrade software A. After receiving an instruction to upgrade software A, it may be determined that the target software to be operated and maintained associated with the operation and maintenance task is software A. According to actual business needs, the target software to be operated and maintained may include one or more.

[0051] According to an embodiment of the present disclosure, in operations S220 to S230, when an operation and maintenance task is performed on a certain software to be operated and maintained (for example, the target software to be operated and maintained), other components may be affected. For example, other components need to be called when the operation and maintenance task is performed on the target software to be operated and maintained; or, the configuration of other components needs to be changed when the operation and maintenance task is performed on the target software to be operated and maintained. For example: when the operation and maintenance task is performed on the target software to be operated and maintained, the database needs to be backed up. Correspondingly, when the operation and maintenance tasks are performed on other components, the target software to be operated and maintained may also be affected. For example, when upgrading a certain software, the configuration of the target software to be operated and maintained needs to be changed. Therefore, the existence of a dependency relationship can be that when the operation and maintenance tasks are performed on the software to be operated and maintained, other components will be affected, or when the operation and maintenance tasks are performed on other components, the software to be operated and maintained will be affected.

[0052] When performing an operation and maintenance task, it is necessary to determine which other components will be affected by the operation and maintenance task, so as to determine the operation and maintenance strategy. The components affected by the operation and maintenance task can be determined based on the associated links. Specifically, the pre-built software relationship library contains multiple associated links. Each associated link includes multiple nodes, and there are dependencies between the software to be operated and maintained corresponding to the multiple nodes and the components, and between the components. The associated links containing the target software to be operated and maintained nodes can be determined to obtain the associated links corresponding to the operation and maintenance task. In addition to the target software to be operated and maintained nodes, the associated links corresponding to the operation and maintenance task also include associated link nodes, and the components corresponding to the associated link nodes are the components that have a dependency relationship with the target software to be operated and maintained.

[0053] For the component corresponding to the associated link node, it may be the component affected when the operation and maintenance software to be operated and maintained performs the operation and maintenance task, or it may be the component that will affect the operation and maintenance software when it performs the operation and maintenance task. Therefore, it is necessary to further determine the node of the component affected when the operation and maintenance software to be operated and maintained performs the operation and maintenance task from the associated component node, and obtain the target associated component node, wherein the target associated component node corresponds to the target associated component. The target associated component may specifically include the component that needs to be called when the operation and maintenance task is performed on the target software to be operated and maintained, or the component that needs to change the configuration when the operation and maintenance task is performed on the target software to be operated and maintained.

[0054] According to an embodiment of the present disclosure, in operation S240, a software information set corresponding to a plurality of software is stored in the software relationship library, for example, a target software information set corresponding to the target software to be maintained may be stored. The target software information set includes basic information of the target software to be maintained, for example, the software type, version information, life cycle, etc. of the target software to be maintained.

[0055] Correspondingly, the software relationship library also stores an associated component information set corresponding to multiple associated components. The associated component set may include basic component information corresponding to the associated components, such as component type, version information, life cycle, etc. of the associated components. After determining the target associated component node, the target associated component information set corresponding to the target associated component node may be directly read from the software relationship library.

[0056] According to an embodiment of the present disclosure, in operation S250, when performing an operation and maintenance task, an operation and maintenance strategy needs to be determined based on the basic information of the target software to be operated and maintained, and the basic information of the target associated components. For example, it may be: the operation and maintenance strategy needs to be determined based on the current version, version update history, version control method, hardware configuration, access rights, and other information of the target software to be operated and maintained and the target associated components. The target software information set can be directly read from the software relationship library, and the basic information of the target software to be operated and maintained required for performing the operation and maintenance task can be directly read from the target software information set; and the target associated component information set can be directly read from the software relationship library, and the basic information of the target associated components required for performing the operation and maintenance task can be directly read from the target associated component information set, so as to determine the operation and maintenance strategy based on the basic information of the target software to be operated and maintained and the basic information of the target associated components.

[0057] According to the embodiment of the present disclosure, the association link corresponding to the operation and maintenance task is determined based on the pre-built software relationship library, and the target association component node is determined from the association component node based on the association link, so that the call relationship and configuration change relationship between the target software to be operated and maintained and other associated components can be fully considered, so that the operation and maintenance strategy is more accurate. In addition, the operation and maintenance personnel can intuitively and simply determine the operation and maintenance content they are responsible for from the software relationship library, and clarify which components need to be called or changed in configuration, thereby improving the work efficiency of the operation and maintenance personnel. By directly reading the target software information set and the target association component information set from the software relationship library, it is possible to simply and accurately know which software will be affected by the execution of the operation and maintenance task, and to know the basic information of the target software to be operated and maintained, so that the operation and maintenance strategy can be accurately and efficiently determined based on the above information, without having to determine the rules and processes of software operation and maintenance by reading complex and non-standardized software operation and maintenance files, eliminating the difficulty of operation and maintenance work caused by the deviation of text understanding, reducing the workload of operation and maintenance personnel, improving the efficiency of software operation and maintenance, and improving the accuracy of operation and maintenance strategies.

[0058] According to an embodiment of the present disclosure, specifically, based on a target software information set and a target associated component information set, determining an operation and maintenance strategy for the target software to be operated and maintained includes: determining first operation and maintenance information related to the operation and maintenance task based on the target software information set; determining second operation and maintenance information based on the target associated component information set; determining an operation and maintenance strategy for the target software to be operated and maintained based on the first operation and maintenance information and the second operation and maintenance information.

[0059] According to the embodiments of the present disclosure, a large amount of basic information of the target software to be operated and maintained is stored in the target software information set, but when performing the operation and maintenance task, only part of the basic information may be used to determine the operation and maintenance strategy, so the basic information related to the operation and maintenance task can be screened out from the target software information set, that is, the first operation and maintenance information. For example: when upgrading the software, it is usually only necessary to obtain the software version information, compatibility information, user permissions and other information, so the version information, compatibility information, user permissions and other information can be read from the target software information set to obtain the first operation and maintenance information.

[0060] Accordingly, when performing an operation and maintenance task, it is also possible to determine the operation and maintenance strategy using only part of the basic information of the target-related component, so the basic information of the target-related component related to the operation and maintenance task can be screened out from the target-related component information set, that is, the second operation and maintenance information. Furthermore, the operation and maintenance strategy can be accurately determined based on the first operation and maintenance information and the second operation and maintenance information.

[0061] According to an embodiment of the present disclosure, the associated component node includes a parent associated component node and a child associated component node. Based on the associated link, determining the target associated component node from at least one associated component node includes: based on the associated link, determining the parent associated component node corresponding to the operation and maintenance task and the child associated component node corresponding to the operation and maintenance task; based on the parent associated component node and the child associated component node, determining the target associated component node from at least one associated component node.

[0062] According to an embodiment of the present disclosure, for the target software to be maintained, the software that is affected when the maintenance task is performed on it is a child-associated component of the target software to be maintained, and the software that affects the target software to be maintained when the maintenance task is performed is the parent-associated component of the target software to be maintained.

[0063] According to the embodiments of the present disclosure, numbers can be set for the target software to be operated and maintained, the parent-associated component, and the child-associated component, and the numbers of the parent-associated component and the child-associated component can be stored in the target software information set, so that the parent-associated component and the child-associated component can be directly determined by reading the parent-associated component number and the child-associated component number in the target software information set. Further, the associated component to be called to perform the operation and maintenance task and the associated component to be changed in configuration can be determined from the child-associated component to obtain the target associated component, and the target associated component node corresponding to the target associated component can be determined.

[0064] For example: the target software to be operated and maintained is software B. The parent-associated components corresponding to software B include software A, and the child-associated components corresponding to software B include software C, software D, and software E. Through the parent-associated components and the child-associated components, it can be determined that when executing the operation and maintenance task for software B, the software that needs to be called is software C, software D, and software E, among which software B can call software C, and software C can call software D and software E. Software C, software D, and software E are target-associated components. The nodes corresponding to software C, software D, and software E can be determined to obtain the target-associated component nodes.

[0065] According to an embodiment of the present disclosure, the operation and maintenance strategy generation method further includes constructing a software relationship library. Constructing the software relationship library specifically includes: determining multiple software to be operated and maintained, and components associated with each software to be operated and maintained, wherein the multiple software to be operated and maintained include target software to be operated and maintained; based on the multiple software to be operated and maintained, and components associated with each software to be operated and maintained, constructing the software relationship library.

[0066] According to the embodiments of the present disclosure, the software to be maintained can be determined from the time dimension, for example, at least one software to be maintained within a predetermined time period can be determined to obtain the software to be maintained. The software to be maintained can also be determined from the business dimension, for example, at least one software to be maintained when executing a specific business can be determined to obtain the software to be maintained.

[0067] According to an embodiment of the present disclosure, the components associated with each software to be maintained may be, for example, components that have a dependency relationship with the software to be maintained. For example, the software to be maintained may be an APP. A virtual machine may call the APP, and the APP may call a corresponding standby APP, so the components associated with the APP may be the virtual machine and the standby APP.

[0068] According to the embodiments of the present disclosure, the software relationship library can be configured according to the actual application scenario. Different application scenarios can correspond to different business requirements. Specifically, the target business requirements can be determined, and the software to be operated and maintained and the components associated with each software to be operated and maintained involved in executing the business requirements can be determined, and the software relationship library can be constructed based on the software to be operated and maintained and the components associated with each software to be operated and maintained.

[0069] According to an embodiment of the present disclosure, specifically, based on a plurality of software to be operated and maintained, and components associated with each software to be operated and maintained, building a software relationship library includes operations 21 to 23.

[0070] Operation 21: Determine first variable configuration information corresponding to each software to be operated and maintained.

[0071] Operation 22: Determine first basic operation and maintenance information corresponding to each software to be operated and maintained based on the first variable configuration information, wherein the first basic operation and maintenance information includes at least one of the following: attribute information, access control information, software management configuration information, and association relationship information of the software to be operated and maintained.

[0072] Operation 23: Generate a software information set corresponding to each software to be operated and maintained based on the first basic operation and maintenance information, where the software information set includes a target software information set.

[0073] According to an embodiment of the present disclosure, in operation 21, when operating and maintaining the software, it may be necessary to change certain configurations of the software, but for the operation and maintenance personnel, not all configurations of the software can be changed. For example, for some office software, its page size, user account name, etc. can be changed, but some key system configuration parameters cannot be changed. The reason is that these configuration parameters are set in the initial configuration stage of the software. Therefore, when performing operation and maintenance tasks, there is no need to consider these unchangeable software configurations. Accordingly, when constructing a software relationship library, only the variable configuration information of each software to be operated and maintained needs to be considered, without considering the configuration information that cannot be changed.

[0074] For each software to be operated and maintained, the data generated by each software to be operated and maintained within a predetermined time interval can be obtained, and the data flow analysis, control flow analysis and transaction path analysis are performed on the above data, so as to determine the first variable configuration information corresponding to each software to be operated and maintained. Among them, the data flow analysis can be the analysis of the movement path of the data in the software to be operated and maintained, which can characterize the input, processing and output process of the data in the software to be operated and maintained; the control flow analysis is the sequence of instructions accepted by the software to be operated and maintained, which can characterize how the software to be operated and maintained executes different code paths according to conditions and logical branches; the transaction path analysis can be the analysis of the behavior path of users when they conduct transactions through the software to be operated and maintained.

[0075] Specifically, the first variable configuration information may include, for example, storage location, operating system version, an independent executable file in the software to be maintained, cache value of the software to be maintained, a software package corresponding to the software to be maintained, location of a water and electricity room, and other information.

[0076] According to an embodiment of the present disclosure, in operation 22, after determining the first variable configuration information, the first variable configuration information may be divided to obtain basic operation and maintenance information such as attribute information, access control information, software management configuration information, and association relationship information.

[0077] According to an embodiment of the present disclosure, specifically, the attribute information may include: the number of the software to be maintained, the name of the software to be maintained, the type of software to be maintained, the version number, the location of the water and electricity room, the role of the software to be maintained, etc., wherein the role of the software to be maintained is used to define what function the software to be maintained assumes on the transaction path; the access control information may include: the black and white lists corresponding to the software to be maintained, the network security policy, etc.; the software management configuration information may include: the effective version of the software to be maintained, the effective switch, the effective configuration, etc.; the association relationship information may include: the parent-associated component number and the child-associated component number corresponding to the software to be maintained, etc.

[0078] According to an embodiment of the present disclosure, in operation 23, a software information set corresponding to each software to be operated and maintained may be generated based on the first basic operation and maintenance information.

[0079] Figure 3 A schematic diagram schematically shows a software information set according to an embodiment of the present disclosure.

[0080] like Figure 3 As shown, for a software information set of a certain software, it may include various information about the software, such as the software number, the name of the software to be maintained, the type of software to be maintained, the version number, the effective version, the effective switch, the effective configuration, etc. It should be noted that Figure 3 The specific content of the software information set shown in is only an exemplary description. According to actual business needs, the software information set may also include other information related to the software to be maintained.

[0081] According to the embodiments of the present disclosure, only the variable configuration information of the software to be maintained is stored in the software information set, which can make the content of the software relationship library clearer and more concise. The maintenance personnel no longer need to filter out the configuration information that cannot be changed, thereby reducing the workload of the maintenance personnel.

[0082] According to an embodiment of the present disclosure, based on multiple software to be maintained and components associated with each software to be maintained, constructing a software relationship library also includes: determining second variable configuration information corresponding to each component; based on the second variable configuration information, determining second basic operation and maintenance information corresponding to the component; based on the second basic operation and maintenance information, generating an associated component information set corresponding to each component one by one, the associated component information set including a target associated component information set.

[0083] According to the embodiments of the present disclosure, for operation and maintenance personnel, not all configurations of associated components can be changed, so when performing operation and maintenance tasks, there is no need to consider these unchangeable software configurations. Accordingly, when building a software relationship library, only the variable configuration information of each software to be operated and maintained needs to be considered, without considering the configuration information that cannot be changed. The data generated by each associated component within a predetermined time interval can be obtained, and the data flow analysis, control flow analysis and transaction path analysis are performed on the above data to determine the second variable configuration information.

[0084] According to an embodiment of the present disclosure, after determining the second variable configuration information, the second variable configuration information can be divided to obtain second basic operation and maintenance information. The second basic operation and maintenance information may include basic operation and maintenance information such as attribute information of associated components, access control information, software management configuration information, association relationship information, etc.

[0085] According to an embodiment of the present disclosure, a set of associated component information corresponding one-to-one to each associated component may be generated based on the second basic operation and maintenance information.

[0086] According to an embodiment of the present disclosure, based on multiple software to be maintained, building a software relationship library also includes: screening out multiple initial software to be maintained that have dependency relationships from the multiple software to be maintained; determining the dependency directions between the multiple initial software to be maintained; determining the dependency directions between components associated with each software to be maintained; and determining at least one association link based on the dependency directions between the multiple initial software to be maintained and the dependency directions between components associated with each software to be maintained.

[0087] According to an embodiment of the present disclosure, for multiple software to be operated and maintained, there may or may not be dependencies between the software to be operated and maintained, and multiple initial software to be operated and maintained with dependencies can be screened out from the multiple software to be operated and maintained.

[0088] According to the embodiments of the present disclosure, the calling directions between the initial software to be operated and maintained can be determined, thereby obtaining the dependency directions between the multiple initial software to be operated and maintained. Correspondingly, the calling directions between the components associated with each software to be operated and maintained can be determined, thereby obtaining the dependency directions between the components associated with each software to be operated and maintained. After determining the dependency directions between the initial software to be operated and maintained and between the components, nodes corresponding to each initial software to be operated and maintained and each component can be generated to obtain the software to be operated and maintained nodes and the associated component nodes, and the above-mentioned software to be operated and maintained nodes and the associated component nodes together constitute an associated link.

[0089] Figure 4 A schematic diagram of a software relationship library according to an embodiment of the present disclosure is schematically shown.

[0090] like Figure 4As shown, the software relationship library may include multiple software information sets to be operated and maintained and multiple associated component information sets, for example, it may include a collection switch set, an access switch set, a virtual machine set, a database set, etc. There may be dependencies between the software to be operated and maintained and the associated components, and between multiple associated components. For example: a virtual machine can call a main APP and can also call database A. In addition, database A can call database B. The main APP can call the corresponding backup APP. A software information set can also be used as a software node to be operated and maintained, and an associated component information set can also be used as an associated component node.

[0091] It should be noted that Figure 4 The specific content of the software relationship library shown in is only an exemplary description, and the software relationship library may also include other information according to actual business needs.

[0092] According to the embodiments of the present disclosure, by constructing a software relationship library, the basic information of the operation and maintenance software and the dependency relationships between the components are abstracted. By determining the operation and maintenance strategy based on the software relationship library, the dependency relationships between the components can be directly obtained, effectively avoiding the problems of hidden software relationships, incomplete information, and low degree of dataization in the software operation and maintenance files. Determining the operation and maintenance strategy based on the software relationship library provides a highly integrated and automated management method, effectively reducing the problems of missing information and misunderstanding caused by reading software operation and maintenance files, ensuring the accuracy and efficiency of software operation and maintenance, bringing a clearer and controllable software management environment to large enterprise organizations, and providing data support and analysis tools for software operation and maintenance.

[0093] According to the embodiments of the present disclosure, when building a software relationship library, basic operation and maintenance information related to the software to be operated and maintained can be read from the database, for example, the cabinet location can be read from the environment library, the attribute information of the software to be operated and maintained can be read from the software device library, and the relevant information of the aggregation switch and the access switch can be read from the hardware relationship library. A database set can be built, and based on the database set, it can be known which databases need to be called when building the software relationship library.

[0094] Figure 5 A schematic diagram of a database collection according to an embodiment of the present disclosure is schematically shown.

[0095] like Figure 5 As shown, the database set may include multiple databases, for example, a hardware relationship library, a software device library, an environment library, etc. It should be noted that Figure 5 The specific content of the database set shown in is only an example. According to actual business needs, the database set may also include other types of databases.

[0096] Taking the rule simulation of prohibiting communication in different management areas in two computer rooms in different countries and regions as an example, the operation and maintenance strategy generation method of the embodiment of the present disclosure is schematically explained.

[0097] At first, various accesses between different management areas were interoperable. For safety reasons, the system was isolated, and physical and logical isolation gradually became strict access control. An operation and maintenance task can be defined. For example, the S area in the A region cannot normally access the 2 area in the B region, but communication is allowed after special approval. The target software to be operated and maintained associated with the above operation and maintenance task is software B. The association link corresponding to the above operation and maintenance task can be determined from the pre-built software relationship library, and the association link includes software A node, software B node, software C node, and software D node. Among them, software A can call software B, software B can change the configuration of software C, and software C can call software D. Based on the association link, the target association component node can be determined to be software C node and software D node. The software B information set corresponding to the software B node, as well as the software C information set and software D information set corresponding to the software C node and software D node respectively can be read from the software relationship library, and the operation and maintenance strategy is determined based on the software B information set, software C information set, and software D information set.

[0098] Based on the above operation and maintenance strategy generation method, the present disclosure also provides an operation and maintenance strategy generation device. Figure 6 The device is described in detail.

[0099] Figure 6 The structural block diagram of the operation and maintenance strategy generating device according to an embodiment of the present disclosure is schematically shown.

[0100] like Figure 6 As shown, the operation and maintenance strategy generating device 600 of this embodiment includes a first determining module 610 , a second determining module 620 , a third determining module 630 , a reading module 640 and a fourth determining module 650 .

[0101] The first determination module 610 is used to determine the target maintenance software associated with the maintenance task in response to the instruction to perform the maintenance task. In one embodiment, the first determination module 610 can be used to perform the operation S210 described above, which will not be described in detail here.

[0102] The second determination module 620 is used to determine at least one association link corresponding to the operation and maintenance task based on the pre-built software relationship library, wherein the association link includes: a target software node corresponding to the target software to be operated and maintained, and at least one associated component node corresponding to at least one associated component, and the associated component has a dependency relationship with the target software to be operated and maintained. In one embodiment, the first reading module 620 can be used to perform the operation S220 described above, which will not be repeated here.

[0103] The third determination module 630 is used to determine a target associated component node from at least one associated component node based on the associated link. In one embodiment, the second reading module 630 can be used to perform the operation S230 described above, which will not be described in detail here.

[0104] The reading module 640 is used to read the target software information set corresponding to the target software node to be operated and maintained from the software relationship library, and read the target associated component information set corresponding to the target associated component node. In one embodiment, the second determination module 640 can be used to perform the operation S240 described above, which will not be repeated here.

[0105] The fourth determination module 650 is used to determine the operation and maintenance strategy for the target software to be operated and maintained based on the target software information set and the target associated component information set. In one embodiment, the fourth determination module 650 can be used to perform the operation S250 described above, which will not be repeated here.

[0106] According to an embodiment of the present disclosure, the fourth determination module includes a first determination submodule, a second determination submodule and a third determination submodule.

[0107] The first determination submodule is used to determine the first operation and maintenance information related to the operation and maintenance task based on the target software information set; the second determination submodule is used to determine the second operation and maintenance information based on the target associated component information set; the third determination submodule is used to determine the operation and maintenance strategy for the target software to be operated and maintained based on the first operation and maintenance information and the second operation and maintenance information.

[0108] According to an embodiment of the present disclosure, the third determining module includes a fourth determining submodule and a fifth determining submodule.

[0109] The fourth determination submodule is used to determine the parent association component node corresponding to the target software to be operated and maintained, and the child association component node corresponding to the target software to be operated and maintained based on the association link; the fifth determination submodule is used to determine the target association component node from at least one association component node based on the parent association component node and the child association component node.

[0110] According to an embodiment of the present disclosure, the operation and maintenance strategy generating device further includes a fifth determining module and a building module.

[0111] The fifth determination module is used to determine multiple software to be maintained and components associated with each software to be maintained, wherein the multiple software to be maintained includes the target software to be maintained; the construction module is used to construct a software relationship library based on the multiple software to be maintained and components associated with each software to be maintained.

[0112] According to an embodiment of the present disclosure, the construction module includes a sixth determination submodule, a seventh determination submodule and a first generation submodule.

[0113] The sixth determination submodule is used to determine the first variable configuration information of each software to be operated and maintained; the fifth determination submodule is used to determine the first basic operation and maintenance information corresponding to each software to be operated and maintained based on the first variable configuration information of each software to be operated and maintained, and the first basic operation and maintenance information includes at least one of the following: attribute information, access control information, software management configuration information and association relationship information of the software to be operated and maintained; the first generation submodule is used to generate a software information set corresponding to each software to be operated and maintained based on the basic operation and maintenance information, and the software information set includes a target software information set.

[0114] According to an embodiment of the present disclosure, the construction module further includes an eighth determination submodule, a ninth determination submodule and a second generation submodule.

[0115] The eighth determination submodule is used to determine the second variable configuration information corresponding to each component; the ninth determination submodule is used to determine the second basic operation and maintenance information corresponding to the component based on the second variable configuration information; the second generation submodule is used to generate an associated component information set corresponding to each component one by one based on the second basic operation and maintenance information, and the associated component information set includes a target associated component information set.

[0116] According to an embodiment of the present disclosure, the construction module further includes a screening submodule, a tenth determining submodule, an eleventh determining submodule and a twelfth determining submodule.

[0117] The screening submodule is used to screen out multiple initial software to be maintained that have dependencies from multiple software to be maintained; the tenth determination submodule is used to determine the dependency direction between the multiple initial software to be maintained; the eleventh determination submodule is used to determine the dependency direction between the components associated with each software to be maintained; the twelfth determination submodule is used to determine the associated links based on the dependency direction between the multiple initial software to be maintained and the dependency direction between the components associated with each software to be maintained.

[0118] According to an embodiment of the present disclosure, any multiple modules of the first determination module 610, the second determination module 620, the third determination module 630, the reading module 640, and the fourth determination module 650 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first determination module 610, the second determination module 620, the third determination module 630, the reading module 640, and the fourth determination module 650 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, at least one of the first determination module 610 , the second determination module 620 , the third determination module 630 , the reading module 640 and the fourth determination module 650 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.

[0119] Figure 7 A block diagram of an electronic device suitable for implementing an operation and maintenance strategy generating method according to an embodiment of the present disclosure is schematically shown.

[0120] like Figure 7 As shown, the electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 to a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include an onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0121] In RAM 703, various programs and data required for the operation of electronic device 700 are stored. Processor 701, ROM 702 and RAM 703 are connected to each other via bus 704. Processor 701 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 702 and / or RAM 703. It should be noted that the program can also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.

[0122] According to an embodiment of the present disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to the bus 704. The electronic device 700 may further include one or more of the following components connected to the input / output (I / O) interface 705: an input portion 706 including a keyboard, a mouse, etc.; an output portion 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 708 including a hard disk, etc.; and a communication portion 709 including a network interface card such as a LAN card, a modem, etc. The communication portion 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the input / output (I / O) interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage portion 708 as needed.

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

[0124] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 702 and / or RAM 703 described above and / or one or more memories other than ROM 702 and RAM 703.

[0125] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the operation and maintenance strategy generation method provided by the embodiment of the present disclosure.

[0126] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 701. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

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

[0128] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

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

[0130] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0131] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

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

Claims

1. A method for generating an operation and maintenance strategy, characterized in that: The method comprises: In response to an instruction to execute an operation and maintenance task, determining a target to-be-operated and maintained software associated with the operation and maintenance task; Based on a pre-built software relationship library, at least one association link corresponding to the operation and maintenance task is determined, wherein the association link includes: a target software node corresponding to the target software to be operated and maintained, and at least one association component node corresponding to at least one association component, and the association component has a dependency relationship with the target software to be operated and maintained; Based on the association link, determining a target association component node from the at least one association component node; Reading a target software information set corresponding to the target software node to be operated and maintained from the software relationship library, and reading a target associated component information set corresponding to the target associated component node; Based on the target software information set and the target associated component information set, an operation and maintenance strategy for the target software to be operated and maintained is determined.

2. The method according to claim 1, characterized in that The determining of the operation and maintenance strategy for the target software to be operated and maintained based on the target software information set and the target associated component information set includes: Based on the target software information set, determining first operation and maintenance information related to the operation and maintenance task; Determining second operation and maintenance information related to the operation and maintenance task based on the target-associated component information set; An operation and maintenance strategy for the target software to be operated and maintained is determined based on the first operation and maintenance information and the second operation and maintenance information.

3. The method according to claim 1, characterized in that The associated component nodes include a parent associated component node and a child associated component node; The determining, based on the association link, a target association component node from the at least one association component node comprises: Based on the association link, determining a parent association component node corresponding to the operation and maintenance task, and a child association component node corresponding to the operation and maintenance task; Based on the parent association component node and the child association component node, a target association component node is determined from the at least one association component node.

4. The method according to claim 1, characterized in that The method further comprises: Determine a plurality of software to be operated and maintained, and components associated with each of the software to be operated and maintained, wherein the plurality of software to be operated and maintained includes a target software to be operated and maintained; The software relationship library is constructed based on the plurality of software to be maintained and the components associated with each of the software to be maintained.

5. The method according to claim 4, characterized in that The constructing the software relationship library based on the plurality of software to be operated and maintained and the components associated with each of the software to be operated and maintained includes: Determine the first variable configuration information corresponding to each of the software to be operated and maintained; Based on the first variable configuration information, determine the first basic operation and maintenance information corresponding to each of the software to be operated and maintained, wherein the first basic operation and maintenance information includes at least one of the following: attribute information, access control information, software management configuration information, and association relationship information of the software to be operated and maintained; Based on the first basic operation and maintenance information, a software information set corresponding to each of the software to be operated and maintained is generated, and the software information set includes a target software information set.

6. The method according to claim 5, characterized in that The step of constructing the software relationship library based on the plurality of software to be maintained and the components associated with each of the software to be maintained further includes: Determining second variable configuration information corresponding to each of the components; Determining second basic operation and maintenance information corresponding to the component based on the second variable configuration information; Based on the second basic operation and maintenance information, an associated component information set corresponding to each of the components is generated, and the associated component information set includes a target associated component information set.

7. The method according to claim 6, characterized in that The step of constructing the software relationship library based on the plurality of software to be maintained and the components associated with each of the software to be maintained further includes: Filtering out a plurality of initial software to be operated and maintained having a dependency relationship from the plurality of software to be operated and maintained; Determining the dependency direction between the plurality of initial software to be operated and maintained; Determine the dependency direction between components associated with each of the software to be maintained; At least one of the association links is determined based on the dependency directions between the multiple initial software to be operated and maintained and the dependency directions between components associated with each of the software to be operated and maintained.

8. An operation and maintenance strategy generating device, characterized in that: The device comprises: A first determination module, configured to determine, in response to an instruction to execute an operation and maintenance task, a target to-be-operated and maintained software associated with the operation and maintenance task; A second determination module is used to determine at least one association link corresponding to the operation and maintenance task based on a pre-built software relationship library, wherein the association link includes: a target software node corresponding to the target software to be operated and maintained, and at least one association component node corresponding to at least one association component, wherein the association component has a dependency relationship with the target software to be operated and maintained; A third determining module, configured to determine a target associated component node from the at least one associated component node based on the associated link; A reading module, used to read a target software information set corresponding to the target software node to be operated and maintained from the software relationship library, and to read a target associated component information set corresponding to the target associated component node; The fourth determination module is used to determine the operation and maintenance strategy for the target software to be operated and maintained based on the target software information set and the target associated component information set.

9. An electronic device, comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images