CN113076129B - Automatic checking and processing method for complex configuration dependency relationship - Google Patents
Automatic checking and processing method for complex configuration dependency relationship Download PDFInfo
- Publication number
- CN113076129B CN113076129B CN202110306547.4A CN202110306547A CN113076129B CN 113076129 B CN113076129 B CN 113076129B CN 202110306547 A CN202110306547 A CN 202110306547A CN 113076129 B CN113076129 B CN 113076129B
- Authority
- CN
- China
- Prior art keywords
- configuration
- new
- new configuration
- dependency
- issuing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 14
- 230000001419 dependent effect Effects 0.000 claims abstract description 32
- 238000000034 method Methods 0.000 claims description 17
- 230000001502 supplementing effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The automatic checking and processing method for the complex configuration dependency relationship comprises the following steps in sequence: creating a dependency graph; when a new configuration is issued, adding the new configuration into the dependency graph; checking whether all the dependences of the new configuration are satisfied, when the configuration A of all the dependences of the new configuration are not satisfied, setting the new configuration into a pending state, and prompting the configuration A of the missing dependences according to the dependency graph; when all the dependent configurations A of the new configuration are satisfied, issuing the new configuration; the invention establishes the dependency graph, sets the configuration which does not satisfy all the dependencies as the pending state, detects whether all the dependent configuration items of the configuration A which depends on the new configuration are satisfied when the new configuration is issued, and carries out corresponding operation, thereby solving the problem that issuing fails when the dependent configuration items which are configured when the current issuing configuration are not satisfied and the problem that the configuration needs to be checked one by one.
Description
Technical Field
The invention relates to the field of computer software configuration, in particular to an automatic checking and processing method for complex configuration dependency.
Background
With the development of computer applications, various applications have increasingly abundant functions, and the abundant functions bring about increasingly more diversity and complexity of configuration items; the reason is that the essential is that various dependency relationships among configurations are more and more complex, and the dependence is many-to-many, multi-level dependence and even many-to-many dependency relationships among layers;
in a computer software system, as the diversity and complexity of configuration items increase, configuration dependency relationships become more and more complex, and when any one of the dependencies involved in configuration is not satisfied, the configuration will fail, what needs to be checked step by step, and when dependency checking between multiple levels is encountered, the current process is not acceptable at all; complex configuration that fails to issue due to dependency missing before issuing again after the completion of the investigation; there is a need to address the problems associated with such complex configuration dependencies; so that we can put more effort on the business than on the investigation of configuration dependencies and the process of issuing the configuration.
Aiming at the current situation of the complex configuration dependency relationship, no related processing scheme exists at present, and the traditional processing thought is as follows: under the complex configuration dependency relationship, before any configuration is performed, all the dependent basic configuration is ensured to be satisfied, otherwise, if any one of the configuration dependency items is not satisfied, the configuration fails to be issued, and in many application designs, the lack of the dependency is not told at all; however, before the configuration, we do not know all the dependency items of the configuration, do not have clear knowledge on the dependency relationship, do not meet direct failure, and check and meet all the dependencies one by one, and manually re-issue the configuration which fails before the time, but when the configuration items of the configuration are many, the time and the effort are quite consumed again.
Disclosure of Invention
The invention aims at: the method comprises the steps of establishing a dependency graph, setting all the dependent configurations which are not satisfied as pending states, not issuing failure in the prior art, prompting missing dependent configuration items, detecting whether all the dependent configuration items of the configuration A which depends on the new configuration are satisfied or not when issuing the new configuration, and performing corresponding operation, thereby solving the problem that the issuing failure is caused when the dependent configuration items of the configuration are not satisfied when issuing the configuration at present, and checking one by one.
The technical scheme adopted by the invention is as follows:
the automatic checking and processing method for the complex configuration dependency relationship comprises the following steps in sequence:
step S1: creating a dependency graph;
step S2: when a new configuration is issued, adding the new configuration into the dependency graph;
step S3: checking whether all the dependences of the new configuration are satisfied, when the configuration A of all the dependences of the new configuration are not satisfied, setting the new configuration into a pending state, and prompting the configuration A of the missing dependences according to the dependency graph; when all the dependent configurations a of the new configuration are satisfied, the new configuration is issued.
To better implement the solution, further, the method further includes step S4: after the new configuration is issued, checking whether all the dependent configuration items of the configuration G in the pending state due to the new configuration are satisfied in the dependency graph, if all the dependent configuration items of the configuration G are satisfied, issuing the configuration G, and if all the dependent configuration items of the configuration G are not satisfied, continuing to maintain the pending state of the configuration G.
In order to better implement the solution, further, the configuration G in the pending state depending on the new configuration is a neighboring configuration node of the new configuration in the dependency graph.
In order to better implement the present solution, further, the pending state in step S3 is: and (3) not issuing unsatisfied configuration A1 in all the configuration A depending on the new configuration, and issuing the configuration A which is not affected by the configuration A1, wherein the new configuration is in a state of waiting for the issuing of the rest of configuration A.
In order to better implement the scheme, further, when the system is initialized, a unique category ID is allocated to each configuration according to the category of each configuration, and each configuration also has a unique name under the category ID, the unique identifier of each configuration is a combination of the category ID and the name, and the creation of the dependency graph in the step S1 is to create and record the dependency graph into the system according to the unique identifier of each configuration and the dependency relationship between the configurations during the system initialization.
In order to better implement the solution, further, the step of adding the new configuration to the dependency graph in step S2 specifically includes:
when a new configuration is issued, detecting whether a unique identifier of the new configuration is in the dependency graph, and if the unique identifier of the new configuration is in the dependency graph, issuing the new configuration according to the unique identifier of the new configuration; when the unique identifier of the new configuration is not in the dependency graph, supplementing the new configuration into the dependency graph according to the dependency of the new configuration, and issuing the new configuration.
In order to better realize the scheme, further, when the new configuration is issued in the step S2, if the new configuration is detected to have the unique identifier, whether the configuration corresponding to the unique identifier of the new configuration is issued is detected, and if the configuration is issued, no operation is performed; and if the configuration corresponding to the unique identifier of the new configuration is not issued, issuing the new configuration.
Because the configurations in the computer software system have complex and different dependency relationships, the issuing of one configuration X is required to satisfy all the dependent configurations a of the configuration, but the configuration X depends on other configurations B, so when the configuration a depended by one configuration X is not satisfied and cannot be issued, there may be various possibilities, in the prior art, the issuing process of the configuration X is directly performed, when all the dependent configurations a of the configuration X are not satisfied, the issuing failure of the configuration X directly occurs, and it is required to check which configuration a is not satisfied, and the configuration a is not satisfied, and because which configuration B depended on the configuration a is not satisfied, and it is also required to check, and after all the configuration B is issued, the configuration X is issued finally, the issuing process is time-consuming and laborious, and after the checking is completed, the configuration a, the configuration B, and the like are required to be issued sequentially, and the issuing process is wasted.
When the configuration is issued, a new configuration to be issued is searched in the dependency graph, when all the configuration items of the new configuration are met, the issuing of the new configuration is performed, and if all the dependencies of the new configuration are not met, the new configuration is set to be in a pending state, wherein the pending state can be set to be that the configuration A1 which is not met in all the configurations A of the new configuration dependency is not issued, the configuration A which is not influenced by the configuration A1 is issued, a part of the configuration A which is relied by the new configuration is issued, the new configuration is in a state waiting for the issuing of the rest of the configuration A, after the issuing of the rest of the configuration A, the new configuration is issued, and the time waste caused by the issuing failure and the need of the issuing again of the new configuration is avoided due to the fact that the issuing of the new configuration is not fully issued.
In summary, due to the adoption of the technical scheme, the beneficial effects of the invention are as follows:
1. the complex configuration dependency relationship automatic checking and processing method establishes a dependency relationship graph, sets the configuration which does not satisfy all dependencies as a pending state, detects whether all the dependent configuration items of the configuration A which depends on the new configuration are satisfied or not when the new configuration is issued, and carries out corresponding operation, thereby solving the problem that issuing fails when the dependent configuration items of the configuration are not satisfied when the configuration is issued at present and the problem that the configuration needs to be checked one by one;
2. the automatic checking and processing method for the complex configuration dependency relationship establishes a dependency relationship graph, sets the configuration which does not meet all the dependencies as a pending state, detects whether all the dependent configuration items of the configuration A which depends on the new configuration are met when the new configuration is issued, and performs corresponding operation.
Drawings
For a clearer description of the present solution, the drawings that are needed in the embodiments will be briefly described, it being understood that, without inventive effort, a person skilled in the art can obtain further relevant drawings from these drawings, in which:
FIG. 1 is a functional block diagram of embodiment 1 of the present invention;
fig. 2 is a functional block diagram of embodiment 2 of the present invention.
Detailed Description
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it should be understood that the described embodiments are only some embodiments of the present invention, but not all embodiments, and therefore should not be considered as limiting the scope of protection. All other embodiments, which are obtained by a worker of ordinary skill in the art without creative efforts, are within the protection scope of the present invention based on the embodiments of the present invention.
In the description of the present invention, it should be noted that, unless explicitly stated and limited otherwise, the terms "disposed," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; or may be directly connected, or may be indirectly connected through an intermediate medium, or may be communication between two elements. The specific meaning of the above terms in the present invention will be understood in specific cases by those of ordinary skill in the art.
The present invention will be described in detail with reference to fig. 1 to 2.
Example 1:
a complex configuration dependency automatic checking processing method, as shown in figure 1, comprises the following steps in sequence:
step S1: creating a dependency graph;
step S2: when a new configuration is issued, adding the new configuration into the dependency graph;
step S3: checking whether all the dependences of the new configuration are satisfied, when the configuration A of all the dependences of the new configuration are not satisfied, setting the new configuration into a pending state, and prompting the configuration A of the missing dependences according to the dependency graph; when all the dependent configurations a of the new configuration are satisfied, the new configuration is issued.
Working principle: because the configurations in the computer software system have complex and different dependency relationships, the issuing of one configuration X is required to satisfy all the dependent configurations a of the configuration, but the configuration X depends on other configurations B, so when the configuration a depended by one configuration X is not satisfied and cannot be issued, there may be various possibilities, in the prior art, the issuing process of the configuration X is directly performed, when all the dependent configurations a of the configuration X are not satisfied, the issuing failure of the configuration X directly occurs, and it is required to check which configuration a is not satisfied, and the configuration a is not satisfied, and because which configuration B depended on the configuration a is not satisfied, and it is also required to check, and after all the configuration B is issued, the configuration X is issued finally, the issuing process is time-consuming and laborious, and after the checking is completed, the configuration a, the configuration B, and the like are required to be issued sequentially, and the issuing process is wasted.
When the configuration is issued, a new configuration to be issued is searched for the dependency relationship in the dependency relationship graph, when all the configuration items of the new configuration are met, the issuing of the new configuration is performed, and if all the dependencies of the new configuration are not met, the new configuration is set to be in a pending state.
Example 2
When the system is initialized, a unique category ID is allocated to each configuration according to the category of each configuration, and each configuration also has a unique name under the category ID, wherein the unique identifier of each configuration is a combination of the category ID and the name, and the complex configuration dependency automatic checking processing method comprises the following steps in sequence as shown in fig. 2:
step S1: when the system is initialized, a dependency graph is created according to the unique identifier of each configuration and the dependency relationship among the configurations, and the dependency graph is recorded in the system.
Step S2: when a new configuration is issued, adding the new configuration into the dependency graph; the method comprises the following steps:
when a new configuration is issued, detecting whether a unique identifier of the new configuration is in the dependency graph, and if the unique identifier of the new configuration is in the dependency graph, issuing the new configuration according to the unique identifier of the new configuration; when the unique identifier of the new configuration is not in the dependency graph, supplementing the new configuration into the dependency graph according to the dependency of the new configuration, and issuing the new configuration.
When a new configuration is issued, if the new configuration is detected to have a unique identifier, detecting whether the configuration corresponding to the unique identifier of the new configuration is issued, and if so, not operating; and if the configuration corresponding to the unique identifier of the new configuration is not issued, issuing the new configuration.
Step S3: checking whether all the dependences of the new configuration are satisfied, when the configuration A of all the dependences of the new configuration are not satisfied, setting the new configuration into a pending state, and prompting the configuration A of the missing dependences according to the dependency graph; when all the dependent configurations a of the new configuration are satisfied, the new configuration is issued.
The undetermined state is as follows: and (3) not issuing unsatisfied configuration A1 in all the configuration A depending on the new configuration, and issuing the configuration A which is not affected by the configuration A1, wherein the new configuration is in a state of waiting for the issuing of the rest of configuration A.
Step S4: after the new configuration is issued, checking whether all the dependent configuration items of the configuration G in the pending state due to the new configuration are satisfied in the dependency graph, if all the dependent configuration items of the configuration G are satisfied, issuing the configuration G, and if all the dependent configuration items of the configuration G are not satisfied, continuing to maintain the pending state of the configuration G. Configuration G, which depends on the new configuration and is in a pending state, is a neighboring configuration node of the new configuration in the dependency graph.
Working principle: because the configurations in the computer software system have complex and different dependency relationships, the issuing of one configuration X is required to satisfy all the dependent configurations a of the configuration, but the configuration X depends on other configurations B, so when the configuration a depended by one configuration X is not satisfied and cannot be issued, there may be various possibilities, in the prior art, the issuing process of the configuration X is directly performed, when all the dependent configurations a of the configuration X are not satisfied, the issuing failure of the configuration X directly occurs, and it is required to check which configuration a is not satisfied, and the configuration a is not satisfied, and because which configuration B depended on the configuration a is not satisfied, and it is also required to check, and after all the configuration B is issued, the configuration X is issued finally, the issuing process is time-consuming and laborious, and after the checking is completed, the configuration a, the configuration B, and the like are required to be issued sequentially, and the issuing process is wasted.
When the configuration is issued, a new configuration to be issued is searched in the dependency graph, when all the configuration items of the new configuration are met, the issuing of the new configuration is performed, and if all the dependencies of the new configuration are not met, the new configuration is set to be in a pending state, wherein the pending state can be set to be that the configuration A1 which is not met in all the configurations A of the new configuration dependency is not issued, the configuration A which is not influenced by the configuration A1 is issued, a part of the configuration A which is relied by the new configuration is issued, the new configuration is in a state waiting for the issuing of the rest of the configuration A, after the issuing of the rest of the configuration A, the new configuration is issued, and the time waste caused by the issuing failure and the need of the issuing again of the new configuration is avoided due to the fact that the issuing of the new configuration is not fully issued.
And after the new configuration is issued, the scheme checks whether all the dependent configuration items of the configuration G in the pending state due to the new configuration are satisfied, and because the configuration G possibly depends on the new configuration is possibly only lack of the new configuration, after the new configuration is issued, all the dependent configurations of the configuration G can be satisfied, so that the configuration G can be issued. Here, in general, the configuration G that depends on the new configuration and is in the pending state is a neighboring configuration node of the new configuration in the dependency graph, that is, we only detect the configuration G that depends on the new configuration, detect the configuration H that depends on the configuration G after the configuration G is issued, and not detect the configuration H that depends indirectly on the new configuration due to the dependence on the configuration G after the new configuration is issued.
In addition, in the scheme, a unique identifier is created before the dependency graph is established, when the system is initialized, the system clearly knows what major classes of configuration (such as major classes including interface configuration and route configuration for a firewall product) are provided for the system, the ID is allocated to the configuration class, in the subsequent use process, a name is provided for a newly added configuration item in a certain class of configuration (such as a configuration item for configuring an ip for an interface is executed in the major class of interface configuration, or a configuration item for creating a route is executed in the major class of route configuration), and then the unique identifier of the configuration is "major class id+intra-class configuration item name". In the dependency graph, the unique identifier is used for referring to the configuration, the dependency between the configurations is clearly expressed, when the new configuration is issued, whether the unique identifier of the new configuration is in the dependency graph is detected, if the unique identifier of the new configuration is in the dependency graph, the new configuration is added to the corresponding position in the dependency graph according to the unique identifier of the new configuration and is ready for issuing; when the unique identifier of the new configuration is not in the dependency graph, supplementing the new configuration into the dependency graph according to the dependency of the new configuration, and preparing to issue the new configuration.
The foregoing description is only a preferred embodiment of the present invention, and is not intended to limit the present invention in any way, and any simple modification, equivalent variation, etc. of the above embodiment according to the technical matter of the present invention fall within the scope of the present invention.
Claims (5)
1. A complex configuration dependency automatic checking and processing method is characterized in that: the method comprises the following steps of:
step S1: creating a dependency graph;
step S2: when a new configuration is issued, adding the new configuration into the dependency graph;
step S3: checking whether all the dependences of the new configuration are satisfied, when the configuration A of all the dependences of the new configuration are not satisfied, setting the new configuration into a pending state, and prompting the configuration A of the missing dependences according to the dependency graph; when all the dependent configurations A of the new configuration are satisfied, issuing the new configuration;
when the system is initialized, a unique category ID is allocated to each configuration according to the category of each configuration, and each configuration also has a unique name under the category ID, wherein the unique identifier of each configuration is a combination of the category ID and the name, and the creation of the dependency graph in the step S1 is to create and record the dependency graph into the system according to the unique identifier of each configuration and the dependency between the configurations when the system is initialized;
the step of adding the new configuration to the dependency graph in the step S2 specifically includes:
when a new configuration is issued, detecting whether the unique identifier of the new configuration is in the dependency graph, and if the unique identifier of the new configuration is in the dependency graph, issuing the new configuration; when the unique identifier of the new configuration is not in the dependency graph, supplementing the new configuration into the dependency graph according to the dependency of the new configuration, and issuing the new configuration.
2. The automatic checking and processing method for complex configuration dependency according to claim 1, wherein: the method further comprises a step S4: after the new configuration is issued, checking whether all the dependent configuration items of the configuration G in the pending state due to the new configuration are satisfied in the dependency graph, if all the dependent configuration items of the configuration G are satisfied, issuing the configuration G, and if all the dependent configuration items of the configuration G are not satisfied, continuing to maintain the pending state of the configuration G.
3. The automatic checking and processing method for complex configuration dependency according to claim 2, wherein: the configuration G which depends on the new configuration and is in a pending state is a neighboring configuration node of the new configuration in the dependency graph.
4. The automatic checking and processing method for complex configuration dependency according to claim 1, wherein: the pending state in the step S3 is: and (3) not issuing unsatisfied configuration A1 in all the configuration A depending on the new configuration, and issuing the configuration A which is not affected by the configuration A1, wherein the new configuration is in a state of waiting for the issuing of the rest of configuration A.
5. The automatic checking and processing method for complex configuration dependency according to claim 1, wherein: when a new configuration is issued in the step S2, if the new configuration is detected to have a unique identifier, detecting whether the configuration corresponding to the unique identifier of the new configuration is issued or not, and if the configuration is issued, not performing operation; and if the configuration corresponding to the unique identifier of the new configuration is not issued, issuing the new configuration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110306547.4A CN113076129B (en) | 2021-03-23 | 2021-03-23 | Automatic checking and processing method for complex configuration dependency relationship |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110306547.4A CN113076129B (en) | 2021-03-23 | 2021-03-23 | Automatic checking and processing method for complex configuration dependency relationship |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113076129A CN113076129A (en) | 2021-07-06 |
| CN113076129B true CN113076129B (en) | 2023-11-28 |
Family
ID=76613291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110306547.4A Active CN113076129B (en) | 2021-03-23 | 2021-03-23 | Automatic checking and processing method for complex configuration dependency relationship |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113076129B (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008158759A (en) * | 2006-12-22 | 2008-07-10 | Toshiba Corp | Programming method, program processing method, processing program, and information processing device |
| CN103793217A (en) * | 2012-10-31 | 2014-05-14 | 国际商业机器公司 | Method and system for quick software configuration |
| CN106648859A (en) * | 2016-12-01 | 2017-05-10 | 北京奇虎科技有限公司 | Task scheduling method and device |
| CN106878061A (en) * | 2017-01-12 | 2017-06-20 | 烽火通信科技股份有限公司 | A kind of method and device for realizing that data communications equipment configuration is synchronous |
| CN107092491A (en) * | 2017-04-21 | 2017-08-25 | 网宿科技股份有限公司 | A kind of configuring load application method and system |
| CN108108878A (en) * | 2017-12-04 | 2018-06-01 | 上海电机学院 | Configurable workflow transactions model and its dynamic verification method based on target |
| CN108628751A (en) * | 2018-05-17 | 2018-10-09 | 北京三快在线科技有限公司 | A kind of useless dependence item detection method and device |
| CN109491571A (en) * | 2018-10-19 | 2019-03-19 | 珠海国津软件科技有限公司 | A kind of association of configuration item and its associated diagram methods of exhibiting and system |
| CN109598407A (en) * | 2018-10-26 | 2019-04-09 | 阿里巴巴集团控股有限公司 | A kind of execution method and device of operation flow |
| CN111338706A (en) * | 2020-02-13 | 2020-06-26 | 深信服科技股份有限公司 | Configuration file importing method, device, equipment and computer readable storage medium |
| CN111708599A (en) * | 2020-08-18 | 2020-09-25 | 江苏神彩科技股份有限公司 | Configuration diagram display method, device, equipment and storage medium |
| CN111813464A (en) * | 2020-08-31 | 2020-10-23 | 新华三半导体技术有限公司 | Chip configuration method, monitoring module and chip |
| CN112306850A (en) * | 2019-07-31 | 2021-02-02 | 腾讯科技(成都)有限公司 | Test case generation method and device and storage medium |
| CN112306471A (en) * | 2020-10-19 | 2021-02-02 | 北京金山云网络技术有限公司 | Task scheduling method and device |
| CN112783568A (en) * | 2021-01-12 | 2021-05-11 | 网易（杭州）网络有限公司 | Initialization method, device, equipment and storage medium of application program |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7039923B2 (en) * | 2002-04-19 | 2006-05-02 | Sun Microsystems, Inc. | Class dependency graph-based class loading and reloading |
| US9244880B2 (en) * | 2012-08-30 | 2016-01-26 | Netspeed Systems | Automatic construction of deadlock free interconnects |
| CN105099904B (en) * | 2014-04-30 | 2018-06-05 | 华为技术有限公司 | A kind of method, apparatus and system of definite intermediary routing node |
| CN104077140B (en) * | 2014-07-04 | 2017-11-07 | 用友网络科技股份有限公司 | Automation Compilation Method and compilation device for continuous integrating |
| WO2017212496A2 (en) * | 2016-06-08 | 2017-12-14 | Veriversion Labs Ltd. | Methods and systems of software testing, distribution, installation and deployment |
| US10355933B2 (en) * | 2017-03-31 | 2019-07-16 | Microsoft Technology Licensing, Llc | Dependency graph for coordination of device configuration |
| US10666507B2 (en) * | 2017-06-30 | 2020-05-26 | Microsoft Technology Licensing, Llc | Automatic reconfiguration of dependency graph for coordination of device configuration |
| CN110457260B (en) * | 2019-08-14 | 2024-07-02 | 深圳前海微众银行股份有限公司 | File processing method, device, equipment and computer readable storage medium |
-
2021
- 2021-03-23 CN CN202110306547.4A patent/CN113076129B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008158759A (en) * | 2006-12-22 | 2008-07-10 | Toshiba Corp | Programming method, program processing method, processing program, and information processing device |
| CN103793217A (en) * | 2012-10-31 | 2014-05-14 | 国际商业机器公司 | Method and system for quick software configuration |
| CN106648859A (en) * | 2016-12-01 | 2017-05-10 | 北京奇虎科技有限公司 | Task scheduling method and device |
| CN106878061A (en) * | 2017-01-12 | 2017-06-20 | 烽火通信科技股份有限公司 | A kind of method and device for realizing that data communications equipment configuration is synchronous |
| CN107092491A (en) * | 2017-04-21 | 2017-08-25 | 网宿科技股份有限公司 | A kind of configuring load application method and system |
| CN108108878A (en) * | 2017-12-04 | 2018-06-01 | 上海电机学院 | Configurable workflow transactions model and its dynamic verification method based on target |
| CN108628751A (en) * | 2018-05-17 | 2018-10-09 | 北京三快在线科技有限公司 | A kind of useless dependence item detection method and device |
| CN109491571A (en) * | 2018-10-19 | 2019-03-19 | 珠海国津软件科技有限公司 | A kind of association of configuration item and its associated diagram methods of exhibiting and system |
| CN109598407A (en) * | 2018-10-26 | 2019-04-09 | 阿里巴巴集团控股有限公司 | A kind of execution method and device of operation flow |
| CN112306850A (en) * | 2019-07-31 | 2021-02-02 | 腾讯科技(成都)有限公司 | Test case generation method and device and storage medium |
| CN111338706A (en) * | 2020-02-13 | 2020-06-26 | 深信服科技股份有限公司 | Configuration file importing method, device, equipment and computer readable storage medium |
| CN111708599A (en) * | 2020-08-18 | 2020-09-25 | 江苏神彩科技股份有限公司 | Configuration diagram display method, device, equipment and storage medium |
| CN111813464A (en) * | 2020-08-31 | 2020-10-23 | 新华三半导体技术有限公司 | Chip configuration method, monitoring module and chip |
| CN112306471A (en) * | 2020-10-19 | 2021-02-02 | 北京金山云网络技术有限公司 | Task scheduling method and device |
| CN112783568A (en) * | 2021-01-12 | 2021-05-11 | 网易（杭州）网络有限公司 | Initialization method, device, equipment and storage medium of application program |
Non-Patent Citations (6)
| Title |
|---|
| Build Predictor: More Accurate Missed Dependency Prediction in Build Configuration Files;Bo Zhou;《2014 IEEE 38th Annual Computer Software and Applications Conference》;1-10 * |
| Configuring the relationships of organizational goals based on ontology framework;Tengku Adil Tengku Izhar;《2017 IEEE SmartWorld, Ubiquitous Intelligence & Computing, Advanced & Trusted Computed, Scalable Computing & Communications, Cloud & Big Data Computing, Internet of People and Smart City Innovation (SmartWorld/SCALCOM/UIC/ATC/CBDCom/IOP/SCI)》;1-7 * |
| ForCES体系结构下的FE建模技术研究;高蕾;《计算机工程与科学》;1-4 * |
| 一种基于关联挖掘的服务一致化配置方法;王焘;《计算机研究与发展》;188-201 * |
| 基于多标签的内核配置图及其应用;侯朋朋;《智能软件研究中心(中国科学院软件研究所) 》;1-5 * |
| 大数据组件部署和管理平台的设计与实现;孙浩;《万方》;1-67 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113076129A (en) | 2021-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8924499B2 (en) | Operating system migration with minimal storage area network reconfiguration | |
| CN113475040B (en) | Learning by inference from brown deployments | |
| EP3373518A1 (en) | Service configuration method and device for network service | |
| CN108279947A (en) | The method and device of financial self-service equipment SP installation kits adaptation | |
| CN102123104A (en) | Network device configuration correcting method and network device | |
| CN111399828A (en) | Model-driven logic device modeling method and terminal | |
| CN104965729A (en) | Method for automatically setting BIOS default value of server | |
| CN113076129B (en) | Automatic checking and processing method for complex configuration dependency relationship | |
| CN106576260A (en) | Policy coordination method and apparatus in NFV system | |
| CN106603330A (en) | Cloud platform virtual machine connection state checking method | |
| CN108089968A (en) | A kind of method of host's machine monitoring virtual-machine data storehouse state | |
| CN108347362B (en) | Method for discovering new device, bridging device and device in system | |
| CN112311574A (en) | Method, device and equipment for checking network topology connection | |
| US10778550B2 (en) | Programmatically diagnosing a software defined network | |
| CN105247618A (en) | Method and device for hard disk drive to execute application code | |
| CN106610899B (en) | Test case generation method and device | |
| CN111259619A (en) | Control method and device for configuration object, storage medium and verification platform | |
| US12126496B2 (en) | Network topology mapping for correctly configuring clustered networks | |
| CN109324965A (en) | A kind of automated testing method that monitoring flock causes client to be collapsed | |
| CN115373916A (en) | Abnormality detection method, abnormality detection device, electronic apparatus, and computer-readable storage medium | |
| CN107590393A (en) | The BIOS adaptive approach and system of a kind of like products difference set meal | |
| CN106899432B (en) | Automatic configuration method of cloud terminal system based on DHCP server | |
| CN104182369A (en) | Method for searching terminal on upper computer and upper computer | |
| CN109491936A (en) | A kind of master slave mode judgment method, controller and the storage medium of dual controller | |
| CN112994787A (en) | Optical network fault judgment method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |