CN111343267B - Configuration management method and system - Google Patents
Configuration management method and systemDownload PDFInfo
- Publication number
- CN111343267B CN111343267BCN202010112581.3ACN202010112581ACN111343267BCN 111343267 BCN111343267 BCN 111343267BCN 202010112581 ACN202010112581 ACN 202010112581ACN 111343267 BCN111343267 BCN 111343267B
- Authority
- CN
- China
- Prior art keywords
- configuration file
- configuration
- hash value
- historical
- file
- 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
Images
Classifications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
- G06F16/137—Hash-based
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/184—Distributed file systems implemented as replicated file system
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
Technical Field
The present application relates to the field of computer configuration technologies, and in particular, to a configuration management method, system, terminal device, and computer-readable storage medium.
Background
With the development of network technology, computers are gradually clustered. However, because the number of computers in the computer cluster is huge, when performing operation maintenance, it is impossible to manually log in each device to perform command configuration.
In the conventional technology, the computer cluster is often divided into a plurality of nodes, and the management node sends the configuration to the child nodes in a centralized manner, so as to implement uniform configuration of the computer cluster. However, after the configuration is issued to the child node, it is inevitable that the configuration in the computer cluster is not consistent due to artificial modification or damage of the configuration command on the child node.
Disclosure of Invention
In view of this, embodiments of the present application provide a method and an apparatus for managing a configuration, which can solve the technical problem that configurations in a computer cluster cannot be kept consistent because artificial modification or damage to a configuration file on a child node cannot be avoided after the configuration is issued to the child node.
A first aspect of an embodiment of the present application provides a configuration management method, including:
calculating a first hash value of a current configuration file, wherein the current configuration file is a file formed by collecting configuration commands which are currently running;
acquiring a second hash value of a pre-stored historical configuration file, wherein the historical configuration file is a unified configuration file issued by a management node;
and if the first hash value and the second hash value are different, updating the current configuration file according to the historical configuration file.
A second aspect of an embodiment of the present application provides a configured management system, including:
the detection configuration module is used for detecting whether the current configuration file is the same as the unified configuration file or not;
the operating system module is used for acquiring a local Internet protocol address;
the management node database module is used for storing the historical configuration file;
and the child node database module is used for storing an update log of the configuration command set in the current configuration file.
A third aspect of embodiments of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor operates the computer program, the steps of the method of the first aspect are implemented.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, which stores a computer program that, when operated by a processor, implements the steps of the method of the first aspect.
Compared with the prior art, the embodiment of the application has the advantages that: in the application, a first hash value of a current configuration file is calculated; acquiring a second hash value of a pre-stored historical configuration file, wherein the historical configuration file is a unified configuration file issued by a management node or a configuration file obtained after the unified configuration file is updated; and if the first hash value and the second hash value are different, updating the current configuration file according to the historical configuration file. And judging whether the current configuration file is changed or not according to the second hash value of the historical configuration file, and further updating the current configuration file to ensure that the configuration commands in the computer cluster are kept consistent.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the related technical descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 shows a schematic flow chart of a method of managing a configuration provided herein;
FIG. 2 shows a detailed schematic flow chart of step 103 of a method for managing a configuration provided by the present application;
FIG. 3 shows a schematic flow chart of a management method of another configuration provided herein;
FIG. 4 shows a schematic flow chart of a management method of another configuration provided herein;
FIG. 5 shows a schematic flow chart of a management method of another configuration provided herein;
FIG. 6 shows a schematic flow chart of a management method of another configuration provided herein;
FIG. 7 is a schematic diagram illustrating a management system of one configuration provided herein;
FIG. 8 is a schematic diagram illustrating a detection configuration module in a configured management system provided by the present application;
fig. 9 shows a schematic diagram of a terminal device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing a relative importance or importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
With the development of network technology, computers are gradually clustered. However, because the number of computers in the computer cluster is huge, when performing operation maintenance, it is impossible to manually log in each device to perform command configuration.
In the conventional technology, the computer cluster is often divided into a plurality of nodes, and the management node sends the configuration to the child nodes in a centralized manner, so as to implement uniform configuration of the computer cluster. However, after the configuration is issued to the child node, it is inevitable that the configuration in the computer cluster is not consistent due to artificial modification or damage of the configuration command on the child node.
In view of this, embodiments of the present application provide a method, a system, a terminal device, and a computer-readable storage medium for managing a configuration, which can solve the technical problem that configurations in a computer cluster cannot be kept consistent because artificial modification or damage to a configuration file on a child node cannot be avoided after the configuration is issued to the child node.
Referring to fig. 1, fig. 1 shows a schematic flow chart of a management method for a configuration provided in the present application.
As shown in fig. 1, the management method may include the steps of:
step 101, calculating a first hash value of a current configuration file, wherein the current configuration file refers to a file formed by a set of currently running configuration commands.
The configuration command is an instruction for specifying a computer to perform a specific action, and includes a timed task (Crontab) command and the like.
Since the number of configuration commands contained in the local computer is large, if each configuration command is compared one by one, the calculation efficiency is low. Therefore, the present embodiment forms the current configuration file by aggregating a plurality of configuration commands. And then calculating a first hash value of the current configuration file, and determining whether to update the current configuration file according to the first hash value without comparing a plurality of configuration commands one by one.
The hash value is a value corresponding to the target file calculated by using a hash algorithm, and the hash algorithm maps a binary value with any length into a smaller binary value with a fixed length, wherein the binary value is the hash value. The Hash algorithms include Message Digest Algorithm second version (Message Digest Algorithm 2, MD2), Message Digest Algorithm fourth version (Message Digest Algorithm 4, MD4), Message Digest Algorithm fifth version (Message Digest Algorithm 5, MD5), and Hash function encryption Algorithm (Secure Hash Algorithm, SHA-1), among others. In the embodiment, the current configuration file is represented by the first hash value, so that the operation efficiency is greatly optimized.
And 102, acquiring a second hash value of a pre-stored historical configuration file, wherein the historical configuration file is a unified configuration file issued by a management node.
The historical configuration file may be a unified configuration file issued by the management node, may also be an updated configuration file, and may also be a configuration file with the same hash value. Wherein the historical configuration file is stored in a database. When the second hash value of the historical configuration file needs to be obtained, the second hash value of the pre-stored historical configuration file only needs to be obtained in the memory of the local computer, and the historical configuration file does not need to be obtained from the database.
As an embodiment of the application, when the second hash value of the historical configuration file needs to be obtained, the historical configuration file in the database may be directly obtained, and then the second hash value of the historical configuration file is calculated through a hash algorithm.
As another embodiment of the present application, when the second hash value of the historical configuration file needs to be obtained, the historical configuration file in the memory may be directly obtained, and then the second hash value of the historical configuration file is calculated through a hash algorithm.
As another embodiment of the present application, when the second hash value of the history configuration file needs to be obtained, the second hash value pre-stored in the database may be directly obtained.
And 103, if the first hash value and the second hash value are different, updating the current configuration file according to the historical configuration file.
And if the first hash value and the second hash value are different, indicating that one or more configuration commands in the current configuration file are changed. The current configuration file needs to be updated according to the historical configuration file so as to keep the configuration files in the computer cluster consistent.
Specifically, the updating the current configuration file according to the historical configuration file includes the following steps, please refer to fig. 2, and fig. 2 shows a specific schematic flowchart of step 103 in a management method for configuration provided by the present application.
Step 1031, traversing the first configuration command set in the history configuration file and the second configuration command set in the current configuration file.
Since the historical configuration file and the current configuration file both contain a plurality of configuration commands. Therefore, each configuration command of the historical configuration file and the current configuration file needs to be traversed.
Step 1032, updating the second configuration command set according to the first configuration command set to obtain the updated current configuration file.
And searching different and same configuration commands in the first configuration command set and the second configuration command set, and replacing the configuration commands in the second configuration command set with the corresponding configuration commands in the first configuration command set to obtain the updated current configuration file.
In the embodiment, a first hash value of the current configuration file is calculated; acquiring a second hash value of a pre-stored historical configuration file, wherein the historical configuration file is a unified configuration file issued by a management node or a configuration file obtained after the unified configuration file is updated; and if the first hash value and the second hash value are different, updating the current configuration file according to the historical configuration file. And judging whether the current configuration file is changed or not according to the second hash value of the historical configuration file, and further updating the current configuration file to ensure that the computer configuration in the computer cluster is kept consistent.
Optionally, on the basis of the embodiment shown in fig. 1, before the current configuration file is updated according to the historical configuration file, the following steps are further included, please refer to fig. 3, and fig. 3 shows a schematic flowchart of another configuration management method provided by the present application. In this embodiment, steps 301 to 302 are the same as steps 101 to 102 in the embodiment shown in fig. 1, and specific reference is made to the description related to steps 101 to 102 in the embodiment shown in fig. 1, which is not repeated herein.
Step 301, calculating a first hash value of a current configuration file, where the current configuration file is a file formed by a configuration command set currently running.
Step 302, obtaining a second hash value of a pre-stored historical configuration file, where the historical configuration file is a unified configuration file issued by a management node.
Step 303, if the first hash value and the second hash value are different, acquiring a local internet protocol address.
And when the historical configuration file is stored in a local database, directly acquiring the historical configuration file in the local database.
When the historical configuration file is stored in a non-local database (such as a management node database), the historical configuration file is obtained according to a local internet protocol address.
Step 304, obtaining the historical configuration file in a database according to the local internet protocol address.
Step 305, updating the current configuration file according to the historical configuration file.
In this embodiment, the historical configuration file is obtained in the database by obtaining a local internet protocol address and according to the local internet protocol address. And updating the current configuration file by acquiring the historical configuration file, so as to ensure that the configuration commands in the computer cluster are kept consistent.
Optionally, on the basis of the embodiment shown in fig. 1, the method further includes the following steps, please refer to fig. 4, and fig. 4 shows a schematic flowchart of a management method of another configuration provided in the present application. In this embodiment, steps 401 to 403 are the same as steps 101 to 103 in the embodiment shown in fig. 1, and specific reference is made to the related description of steps 101 to 103 in the embodiment shown in fig. 1, which is not repeated herein.
Step 401, calculating a first hash value of a current configuration file, where the current configuration file is a file formed by a configuration command set currently running.
Step 402, obtaining a second hash value of a pre-stored historical configuration file, where the historical configuration file is a unified configuration file issued by a management node.
Step 403, if the first hash value and the second hash value are different, updating the current configuration file according to the historical configuration file.
In step 404, a command to be executed and an execution log in a preset period are obtained.
In order to check whether the updated configuration command in the current configuration file can be executed normally. Therefore, after the current configuration file is updated, the command and the execution log which need to be executed in the preset period need to be acquired, so as to detect whether the configuration command in the updated current configuration file can be normally executed.
Step 405, if the command does not exist in the execution log, sending alarm information to an external device or a management node.
If the command exists in the execution log, it indicates that the updated configuration command in the current configuration file can be normally executed.
If the command does not exist in the execution log, it indicates that the updated configuration command in the current configuration file cannot be normally executed, and an alarm message needs to be sent to external equipment or a management node to remind a user of configuration updating.
In this embodiment, by obtaining a command to be executed and an execution log in a preset period, if the command does not exist in the execution log, sending alarm information to an external device or a management node. Whether the configuration command in the updated current configuration file is normally executed is determined through the method, so that an error configuration instruction is prevented from being generated after updating, and the accuracy of updating the configuration command is ensured.
Optionally, on the basis of the embodiment shown in fig. 1, the method further includes the following steps, please refer to fig. 5, and fig. 5 shows a schematic flowchart of a management method of another configuration provided in the present application. In this embodiment, steps 501 to 503 are the same as steps 101 to 103 in the embodiment shown in fig. 1, and specific reference is made to the description related to steps 101 to 104 in the embodiment shown in fig. 1, which is not repeated herein.
Step 501, calculating a first hash value of a current configuration file, where the current configuration file is a file formed by a configuration command set currently running.
Step 502, obtaining a second hash value of a pre-stored historical configuration file, where the historical configuration file is a unified configuration file issued by a management node.
Step 503, if the first hash value is different from the second hash value, updating the current configuration file according to the historical configuration file.
Step 504, repeatedly executing step 501 to step 503 every preset time.
In the present embodiment, steps 501 to 503 are repeatedly executed every preset time period. The method realizes the periodic update of the current configuration file, and ensures that the configuration commands in the computer cluster are kept consistent.
Optionally, on the basis of the embodiment shown in fig. 1, the method further includes the following steps, please refer to fig. 6, and fig. 6 shows a schematic flowchart of a management method of another configuration provided in the present application. In this embodiment, steps 601 to 603 are the same as steps 101 to 103 in the embodiment shown in fig. 1, and specific reference is made to the related description of steps 101 to 104 in the embodiment shown in fig. 1, which is not repeated herein.
Step 601, calculating a first hash value of a current configuration file, where the current configuration file is a file formed by a configuration command set currently running.
Step 602, obtaining a second hash value of a pre-stored historical configuration file, where the historical configuration file is a unified configuration file issued by a management node.
Step 603, if the first hash value and the second hash value are different, updating the current configuration file according to the historical configuration file, and sending alarm information to external equipment or a management node.
If the first hash value and the second hash value are different, the configuration command in the current configuration file is changed or damaged in the child node, the current configuration file needs to be updated according to the historical configuration file, and alarm information is sent to external equipment or a management node.
In this embodiment, when the first hash value and the second hash value are different, the current configuration file is updated according to the historical configuration file, and an alarm message is sent to an external device or a management node. Through the method, the user is prompted to carry out other measures, and the configuration command in the current configuration file is prevented from being changed or damaged.
Referring to fig. 7, fig. 7 is a schematic diagram illustrating a management system according to one configuration provided in the present application.
As shown in fig. 7, the management system 7 includes: the system comprises a detection configuration module, an operating system module, a management node database module and a child node database module.
And the detection configuration module is used for detecting whether the current configuration file is the same as the unified configuration file. And the operating system module is used for acquiring a local internet protocol address. And the management node database module is used for storing the historical configuration file. And the child node database module is used for storing an update log of the configuration command set in the current configuration file.
The processing flow of the management system 7 is as follows:
the operating system module sends a detection configuration instruction to a detection configuration module (which may be a detection configuration program or a script, etc.) according to a preset period. The detection configuration module sets a file exclusive lock in the current configuration file, calculates a first hash value of the current configuration file and a second hash value of the historical configuration file, and if the first hash value is different from the second hash value, calculates a second hash value of the historical configuration file. And the operating system module acquires a local IP address and acquires a historical configuration file in the management node database module according to the IP address. And the detection configuration module updates different configurations of the local configuration file according to the historical configuration file. The management node database module stores the updated local configuration file. The child node database module stores a configuration update log. And the detection configuration module takes the third hash value of the modified current configuration file as the second hash value of the historical configuration file.
Referring to fig. 8, fig. 8 is a schematic diagram illustrating a detection configuration module in a configured management system according to the present application.
Wherein, the detection configuration module 8 includes:
the calculatingunit 81 is configured to calculate a first hash value of a current configuration file, where the current configuration file is a file formed by a set of configuration commands currently running.
The obtainingunit 82 is configured to obtain a second hash value of a pre-stored historical configuration file, where the historical configuration file is a unified configuration file issued by the management node.
And the judgingunit 83 is configured to update the current configuration file according to the historical configuration file if the first hash value is different from the second hash value.
According to the management system for configuration, a first hash value of a current configuration file is calculated; acquiring a second hash value of a pre-stored historical configuration file, wherein the historical configuration file is a unified configuration file issued by a management node or a configuration file obtained after the unified configuration file is updated; and if the first hash value and the second hash value are different, updating the current configuration file according to the historical configuration file. And judging whether the current configuration file is changed or not according to the second hash value of the historical configuration file, and further updating the current configuration file to ensure that the configuration commands in the computer cluster are kept consistent.
Fig. 9 shows a schematic diagram of a terminal device according to an embodiment of the present application. As shown in fig. 9, aterminal device 9 of this embodiment includes: aprocessor 90, amemory 91, and acomputer program 92, such as a configured hypervisor, stored in thememory 91 and operable on theprocessor 90. Theprocessor 90, when executing thecomputer program 92, implements the steps in each of the above-described configured management method embodiments, such as the steps 101 to 103 shown in fig. 1. Alternatively, theprocessor 90, when executing thecomputer program 92, implements the functions of the modules in the above device embodiments, such as the modules shown in fig. 8.
Illustratively, thecomputer program 92 may be partitioned into one or more modules that are stored in thememory 91 and executed by theprocessor 90 to accomplish the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions for describing the execution of thecomputer program 92 in the oneterminal device 9. For example, thecomputer program 92 may be divided into modules with specific functions as follows:
the detection configuration module is used for detecting whether the current configuration file is the same as the unified configuration file or not;
the operating system module is used for acquiring a local Internet protocol address;
the management node database module is used for storing the historical configuration file;
and the child node database module is used for storing an update log of the configuration command set in the current configuration file.
Theterminal device 9 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, aprocessor 90, amemory 91. Those skilled in the art will appreciate that fig. 9 is merely an example of one type ofterminal device 9 and does not constitute a limitation of one type ofterminal device 9, and may include more or fewer components than shown, or combine certain components, or different components, e.g., the one type of terminal device may also include input-output devices, network access devices, buses, etc.
TheProcessor 90 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Thememory 91 may be an internal storage module of theterminal device 9, such as a hard disk or a memory of theterminal device 9. Thememory 91 may also be an external storage device of theterminal device 9, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) and the like provided on theterminal device 9. Further, thememory 91 may also include both an internal memory module and an external memory device of theterminal device 9. Thememory 91 is used for storing the computer program and other programs and data required by the kind of terminal equipment. Thememory 91 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned functional modules and modules are illustrated as examples, and in practical applications, the above-mentioned functional allocation may be performed by different functional modules and modules according to requirements, that is, the internal structure of the apparatus is divided into different functional modules or modules to perform all or part of the above-mentioned functions. In the embodiments, each functional module and each module may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module, and the integrated modules may be implemented in a form of hardware or a form of software functional modules. In addition, specific names of the functional modules and modules are only used for distinguishing the functional modules and the modules from each other, and are not used for limiting the protection scope of the present application. The modules and the specific working processes of the modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed terminal device and method may be implemented in other ways. For example, the above-described terminal device embodiments are merely illustrative, and for example, the modules or the division of the modules is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of modules or components may be combined or may be integrated into another system, or some features may be omitted or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (8)
1. A method for managing a configuration, the method comprising:
calculating a first hash value of a current configuration file, wherein the current configuration file is a file formed by collecting configuration commands which are currently running;
acquiring a second hash value of a pre-stored historical configuration file, wherein the historical configuration file is a unified configuration file issued by a management node;
and if the first hash value and the second hash value are different, traversing a first configuration command set in the historical configuration file and a second configuration command set in the current configuration file, and updating the second configuration command set according to the first configuration command set to obtain the updated current configuration file.
2. The method of managing as set forth in claim 1, wherein before said traversing a first set of configuration commands in the historical configuration file and a second set of configuration commands in the current configuration file, updating the second set of configuration commands based on the first set of configuration commands, and obtaining the updated current configuration file, further comprising:
acquiring a local internet protocol address;
and acquiring the historical configuration file in a database according to the local Internet protocol address.
3. The management method of claim 1, further comprising:
and repeatedly executing the step of calculating the first hash value of the current configuration file and the subsequent steps at intervals of preset time length.
4. The method for managing as set forth in claim 1, wherein after traversing a first configuration command set in the historical configuration file and a second configuration command set in the current configuration file if the first hash value and the second hash value are different, updating the second configuration command set according to the first configuration command set, and obtaining the updated current configuration file, the method further comprises:
acquiring a command to be executed and an execution log in a preset period;
and if the command does not exist in the execution log, sending alarm information to external equipment or a management node.
5. The management method of claim 1, further comprising:
and if the first hash value and the second hash value are different, sending alarm information to external equipment or a management node.
6. A management system for a configuration, the system comprising:
the detection configuration module is used for detecting whether the current configuration file is the same as the unified configuration file or not;
the operating system module is used for acquiring a local Internet protocol address;
the management node database module is used for storing historical configuration files;
the child node database module is used for storing an update log of a configuration command set in a current configuration file;
the detection configuration module comprises:
the device comprises a calculation unit and a control unit, wherein the calculation unit is used for calculating a first hash value of a current configuration file, and the current configuration file refers to a file formed by a configuration command set which is currently running;
the acquisition unit is used for acquiring a second hash value of a pre-stored historical configuration file, wherein the historical configuration file is a unified configuration file issued by a management node;
and the judging unit is used for traversing a first configuration command set in the historical configuration file and a second configuration command set in the current configuration file if the first hash value and the second hash value are different, and updating the second configuration command set according to the first configuration command set to obtain the updated current configuration file.
7. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 5 when operating the computer program.
8. A computer-readable storage medium, in which a computer program is stored which, when being operated by a processor, carries out the steps of the method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010112581.3ACN111343267B (en) | 2020-02-24 | 2020-02-24 | Configuration management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010112581.3ACN111343267B (en) | 2020-02-24 | 2020-02-24 | Configuration management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111343267A CN111343267A (en) | 2020-06-26 |
| CN111343267Btrue CN111343267B (en) | 2022-08-12 |
Family
ID=71187122
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010112581.3AActiveCN111343267B (en) | 2020-02-24 | 2020-02-24 | Configuration management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111343267B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112000363A (en)* | 2020-07-30 | 2020-11-27 | 苏州浪潮智能科技有限公司 | Method and system for managing big data assembly configuration file |
| CN113886267B (en)* | 2021-10-25 | 2025-05-06 | 锐凌无线有限责任公司 | A software system detection method, device, electronic device and storage medium |
| CN114090242B (en)* | 2021-11-08 | 2025-09-12 | 百果园技术(新加坡)有限公司 | Model training method, device, equipment, storage medium and program product |
| CN114428631A (en)* | 2022-01-18 | 2022-05-03 | 北京有竹居网络技术有限公司 | Configuration file management method, apparatus, computer readable medium and electronic device |
| CN114189437A (en)* | 2022-02-15 | 2022-03-15 | 北京搜狐新媒体信息技术有限公司 | Method and device for processing configuration information of network equipment |
| CN116032608A (en)* | 2022-12-29 | 2023-04-28 | 北京威努特技术有限公司 | A method for synchronizing industrial control firewall configuration |
| CN118132538B (en)* | 2024-05-06 | 2024-07-16 | 深圳九有数据库有限公司 | Database system replacement method and device, electronic equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106603281A (en)* | 2016-12-07 | 2017-04-26 | 乐视控股（北京）有限公司 | Configuration file management method and system |
| CN108600029A (en)* | 2018-05-09 | 2018-09-28 | 深圳壹账通智能科技有限公司 | A kind of configuration file update method, device, terminal device and storage medium |
| CN109325349A (en)* | 2018-08-15 | 2019-02-12 | 深圳市元征科技股份有限公司 | A kind of method for managing security, terminal device and computer readable storage medium |
| CN109614376A (en)* | 2018-12-04 | 2019-04-12 | 郑州云海信息技术有限公司 | NAS node configuration file update method and NAS configuration node controller |
| CN109669717A (en)* | 2018-09-25 | 2019-04-23 | 深圳壹账通智能科技有限公司 | Data processing method, device, equipment and storage medium based on deployment platform |
| CN109842530A (en)* | 2019-04-15 | 2019-06-04 | 网易（杭州）网络有限公司 | VNF configuration method, device, electronic equipment and computer-readable medium |
| CN110061838A (en)* | 2019-04-28 | 2019-07-26 | 广州大学 | A kind of the decentralization storage system and its realization, information retrieval method of DNS resource record |
| EP3537740A1 (en)* | 2018-03-06 | 2019-09-11 | Accenture Global Solutions Limited | Hash based device configuration management |
| CN110602251A (en)* | 2019-09-30 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Data processing method, device, apparatus and medium based on inter-node data sharing |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10944546B2 (en)* | 2017-07-07 | 2021-03-09 | Microsoft Technology Licensing, Llc | Blockchain object interface |
- 2020
- 2020-02-24CNCN202010112581.3Apatent/CN111343267B/enactiveActive
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106603281A (en)* | 2016-12-07 | 2017-04-26 | 乐视控股（北京）有限公司 | Configuration file management method and system |
| EP3537740A1 (en)* | 2018-03-06 | 2019-09-11 | Accenture Global Solutions Limited | Hash based device configuration management |
| CN108600029A (en)* | 2018-05-09 | 2018-09-28 | 深圳壹账通智能科技有限公司 | A kind of configuration file update method, device, terminal device and storage medium |
| CN109325349A (en)* | 2018-08-15 | 2019-02-12 | 深圳市元征科技股份有限公司 | A kind of method for managing security, terminal device and computer readable storage medium |
| CN109669717A (en)* | 2018-09-25 | 2019-04-23 | 深圳壹账通智能科技有限公司 | Data processing method, device, equipment and storage medium based on deployment platform |
| CN109614376A (en)* | 2018-12-04 | 2019-04-12 | 郑州云海信息技术有限公司 | NAS node configuration file update method and NAS configuration node controller |
| CN109842530A (en)* | 2019-04-15 | 2019-06-04 | 网易（杭州）网络有限公司 | VNF configuration method, device, electronic equipment and computer-readable medium |
| CN110061838A (en)* | 2019-04-28 | 2019-07-26 | 广州大学 | A kind of the decentralization storage system and its realization, information retrieval method of DNS resource record |
| CN110602251A (en)* | 2019-09-30 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Data processing method, device, apparatus and medium based on inter-node data sharing |
Non-Patent Citations (2)
| Title |
|---|
| 一种云存储环境下的安全存储系统;薛矛等;《计算机学报》;20151231(第05期);全文* |
| 基于RBAC技术的电力信息系统间授权差异智能检测工具研发;赵新建;《信息通信》;20170415(第04期);全文* |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111343267A (en) | 2020-06-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111343267B (en) | Configuration management method and system | |
| CN110737658A (en) | Data fragment storage method, device, terminal and readable storage medium | |
| CN109814524B (en) | Vehicle diagnosis method, device and system | |
| CN112163412B (en) | Data verification method and device, electronic equipment and storage medium | |
| CN115086047B (en) | Interface authentication method and device, electronic equipment and storage medium | |
| US20200364595A1 (en) | Configuration assessment based on inventory | |
| WO2021114025A1 (en) | Incremental data determination method, incremental data determination apparatus, server and terminal device | |
| CN110851339A (en) | Method and device for reporting buried point data, storage medium and terminal equipment | |
| CN118094450B (en) | Fault early warning method and related equipment | |
| CN111538651A (en) | Interface testing method, device, server and storage medium | |
| CN115033551A (en) | Database migration method and device, electronic equipment and storage medium | |
| CN113220342A (en) | Centralized configuration method and device, electronic equipment and storage medium | |
| CN112527780A (en) | Redis cluster creating and managing method, system, computer device and storage medium | |
| CN118132576A (en) | Method and device for updating dimension data | |
| CN118446779A (en) | Model loading method and device, electronic equipment and storage medium | |
| CN113726885B (en) | Flow quota adjusting method and device | |
| CN110879774A (en) | Network element performance data warning method and device | |
| CN116881081A (en) | Acquisition configuration updating method, device and system of monitoring system and storage medium | |
| CN116089131A (en) | Method and system for solving incorrect current value of alarm recovery data of monitoring system | |
| CN113127495B (en) | Database updating method and device | |
| CN110377665B (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN113656378A (en) | A server management method, device and medium | |
| CN110784479B (en) | Data verification method and device, electronic equipment and storage medium | |
| CN115022171A (en) | Optimization method, apparatus, electronic device and readable storage medium for updating interface | |
| CN109788054B (en) | Configuration method, server and medium for distributed application coordination service node |
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 | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address | Address after:518000 Room 01, 20th Floor, Cuilin Building, No. 10, Kaifeng Road, Maling Community, Meilin Street, Futian District, Shenzhen, Guangdong Patentee after:Shenzhen Handhui Technology Group Co.,Ltd. Address before:518000 2401e, 24 / F, Hainan Huanqing building, No. 24 Futian Road, Weizhen community, Futian street, Futian District, Shenzhen, Guangdong Patentee before:Shenzhen muchenglin Technology Co.,Ltd. |