CN110620695B - Data processing method and related equipment - Google Patents
Data processing method and related equipment Download PDFInfo
- Publication number
- CN110620695B CN110620695B CN201910937430.9A CN201910937430A CN110620695B CN 110620695 B CN110620695 B CN 110620695B CN 201910937430 A CN201910937430 A CN 201910937430A CN 110620695 B CN110620695 B CN 110620695B
- Authority
- CN
- China
- Prior art keywords
- node
- configuration information
- management
- agent
- shared
- 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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0889—Techniques to speed-up the configuration process
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the application discloses a data processing method and related equipment, wherein the method is applied to the technical field of block chains and comprises the following steps: the management node in the Sawtoth network can receive and store the unique configuration information of the corresponding node sent by each node agent, send a first starting instruction to the first node agent, and receive and store the shared configuration information sent by the first node agent, so that the first node agent can obtain the shared configuration information and the unique configuration information of the first node from the management node to start the first node; and sending a second starting instruction to the second node agent, wherein the second starting instruction is used for instructing the second node agent to acquire the shared configuration information and the unique configuration information of the second node from the management node so as to start the second node. By adopting the mode, the construction efficiency of the Sawtoth network is improved.
Description
Technical Field
The present application relates to the field of block chaining technologies, and in particular, to a data processing method and related devices.
Background
Sawtoth is an enterprise-level blockchain project hatched by a super ledger and an Intel together, and aims to provide a safer, more efficient and more easily-extensible blockchain solution for an enterprise. The bottom layer of the system is realized by using Python and Rust languages, and the system provides multiple development languages SDK and intelligent contract support such as Go, rust, python, JS and Java. Meanwhile, the method supports pluggable consensus algorithms such as PoET, raft and PBFT, and enterprises can construct alliance chains, private chains and even public chains according to needs.
Sawtooth provides friendly support for distributed application developers, such as multi-language SDKs, multi-language intelligent contracts and the like. However, the sawteeth network building, network management, configuration management are not friendly.
In order to build the sawteeth network, a network administrator has to log in a server of each node of the sawteeth network, input different complex commands through a command line, initialize configuration information on a created block chain and edit related configuration information under the chain, so that the operation is complex, and the building efficiency of the sawteeth network is low.
Disclosure of Invention
The embodiment of the application provides a data processing method and related equipment, and is beneficial to improving the building efficiency of a Sawtoth network.
In a first aspect, an embodiment of the present application provides a data processing method, which is applied to a sawteeth network, where the sawteeth network includes a management node, at least one node, and a corresponding node agent, and the method includes:
the management node receives and stores the unique configuration information of the corresponding node sent by each node agent;
the management node sends a first starting instruction to a first node agent, wherein the first starting instruction is used for indicating a first node to generate shared configuration information, and the first node is a created node;
the management node receives and stores the shared configuration information sent by the first node agent, so that the first node agent acquires the shared configuration information and the unique configuration information of the first node from the management node to start the first node;
the management node sends a second start instruction to a second node agent, the second start instruction is used for instructing the second node agent to acquire the shared configuration information and the unique configuration information of the second node from the management node so as to start the second node, and the second node is a non-created node.
In one embodiment, before the management node sends the first start instruction to the first node agent, the management node may further display a node management list, where the node management list includes node identifiers of each node in the at least one node; and determining a first node corresponding to the node identification as an emerging node according to the node identification selected from the node list.
In an embodiment, the management node may further receive node state information of each corresponding node sent by each node agent, where the node state information includes one or more of a node running state, central processing unit information, memory information, network information, disk information, and an application log; and the management node displays the node state information of the corresponding node sent by each node agent.
In one embodiment, the management node may further detect a management operation input for a node to be managed in the node management list; the management node determines a node corresponding to the management operation as a node to be managed; and the management node sends a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed, wherein the management instruction is used for indicating the node agent corresponding to the node to be managed to perform node management on the node to be managed, and the node management comprises at least one of starting the node to be managed, restarting the node to be managed, stopping the node to be managed and deleting the node to be managed.
In an embodiment, the management operation is a deletion operation for instructing to delete the node to be managed, and before the management instruction corresponding to the management operation is sent to the node agent corresponding to the node to be managed, the management node may further obtain a consensus member list from the shared configuration information; and the management node verifies the management operation based on the consensus member list, and if the verification is passed, the step of sending a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed is triggered and executed.
In an embodiment, the management node may further receive and store unique configuration information of a new node corresponding to a new node sent by a new node agent; the management node displays the unique configuration information of the newly added node; if the management node receives a confirmation instruction aiming at the newly added node, a newly added node starting instruction is sent to the newly added node agent so as to instruct the newly added node agent to acquire the shared configuration information and the unique configuration information of the newly added node from the management node so as to start the newly added node.
In an embodiment, the management node may further obtain configuration information to be updated, where the configuration information includes the shared configuration information and/or unique configuration information of a target node, and the target node is any node in the at least one node; and the management node verifies the configuration information to be updated, and if the verification is passed, the shared configuration information and/or the unique configuration information of the target node are/is updated by adopting the configuration information to be updated.
In an embodiment, the configuration information to be updated includes unique configuration information of the target node, and after updating the unique configuration information of the target node with the configuration information to be updated if the configuration information to be updated passes the verification, the management node may further send a restart instruction to a node agent corresponding to the target node to instruct the node agent corresponding to the target node to acquire the shared configuration information and the updated unique configuration information of the target node from the management node to restart the target node.
In a second aspect, the present application provides a data processing apparatus including means for performing the method of the first aspect.
In a third aspect, an embodiment of the present application provides a server, which includes a processor, a communication interface, and a memory, where the processor, the communication interface, and the memory are connected to each other, where the communication interface is controlled by the processor to send and receive messages, the memory is used to store a computer program that supports the server to execute the foregoing method, and the computer program includes program instructions, and the processor is configured to call the program instructions to execute the foregoing method according to the first aspect.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program, the computer program comprising program instructions that, when executed by a processor, cause the processor to perform the method of the first aspect.
In this embodiment of the application, the management node may receive and store the unique configuration information of the corresponding node sent by each node agent, and send a first start instruction to the first node agent, where the first start instruction is used to instruct the first node to generate shared configuration information. Further, the management node may further send a second start instruction to the second node agent, the second start instruction being used to instruct the second node agent to acquire the shared configuration information and the unique configuration information of the second node from the management node to start the second node. By adopting the mode, the related information of the Sawtoth network can be managed in an auxiliary mode through the management node, and the commands (such as the first starting command, the second starting command and the like) of the management node are executed through the node agent, so that the user does not need to independently log in a server deployed by each node in the Sawtoth network to edit configuration files (such as unique configuration information, shared configuration information and the like) for building and starting the Sawtoth network, the workload of a Sawtoth network administrator is greatly saved, and the building efficiency of the Sawtoth network is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are 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 is a schematic structural diagram of a Sawtooth network according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a data processing method according to an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram of another data processing method provided in the embodiments of the present application;
fig. 4 is a schematic block diagram of a data processing apparatus provided in an embodiment of the present application;
fig. 5 is a schematic block diagram of a server according to an embodiment of the present application.
Detailed Description
The data processing method provided by the embodiment of the application is applied to a Sawtoth network, and referring to a structural schematic diagram of the Sawtoth network shown in FIG. 1, the Sawtoth network comprises a management node 10 and at least one network node 11, each network node 11 comprises a Sawtoth node 110 and a corresponding node agent 111, wherein the management node can be independently deployed and also can be deployed on a certain network node, and the management node can assist an administrator to set up the Sawtoth network, maintain the configuration on a link and under the link of the Sawtoth network, monitor the operation state of the Sawtoth network, and check a network node adding request; each node agent in each network node is used for reporting the node running state, the synchronous network configuration and the like of the corresponding sawteeth node, and each node agent and the corresponding sawteeth node are deployed on the same server (namely, the network node 11).
The management node 10 includes an interface display module, a background service module, and a storage module, and the management node may be a server for providing data processing related services, and the server is connected to a display device, or the management node may also be some intelligent terminals with rich software and hardware resources, such as some personal computers.
In one embodiment, the interface presentation module provides a human-machine interaction interface for the management node, and may be configured to: a. and displaying node state information, such as: one or more of the running state of the Sawtoth node, CPU information of a central processing unit, memory information, network information, disk information and an application log; b. managing the network, such as: starting, restarting, adding and deleting the Sawtoth node; c. on-chain configuration management, such as: configuring a consensus algorithm, namely a white list and a black list of an administrator, and a white list and a black list of an intelligent contract; d. under-chain configuration management, such as: the sawteeth network runtime shares configuration (i.e., configuration for shared configuration information), and the sawteeth node runtime has unique configuration (i.e., configuration for unique configuration information).
In the embodiment of the application, on one hand, configuration information (shared configuration information and/or unique configuration information) can be changed quickly and efficiently through the interface display module, and a user does not need to log in a server deployed by each node in a Sawtoth network in sequence to manually change the configuration and restart the Sawtoth node, so that the configuration is effective; on the other hand, the join request of the Sawtoth node can be received in real time, the join request is examined and approved through the interface display module, a user does not need to log in a server, and the operation is carried out through a command line; in another aspect, the running state of each of the sawteeth nodes can be displayed through the interface display module, so that each of the sawteeth nodes can be monitored, users can conveniently process or delete abnormal sawteeth nodes in time, users do not need to log in each server, and the difficulty in maintaining the sawteeth network is reduced by operating through a command line.
In one embodiment, the background service module may be configured to provide a background service to the outside. The interface display module can realize the inquiry of node state information, the configuration of the Sawtoth node information and the management of the Sawtoth node by sending an instruction to the background service module; meanwhile, the node agent can send the collected node state information of the Sawtoth node to the management node, and the node state information is displayed to a display screen by the interface display module after being processed by the background service module; secondly, the node agent can also receive commands from the management node, so as to start, restart, delete and the like on the Sawtoth node.
In one embodiment, when the management node is a server, the storage module may be a database; when the management node is an intelligent terminal, the storage module may be a storage device (e.g., a memory bank, a hard disk, etc.), and the storage module is configured to store data of the entire Sawtooth network, such as: node state information, on-chain configuration, off-chain configuration, node joining requests, operation logs or node logs and the like, and the problems of decentralized configuration and storage, inconsistent configuration information, decentralized log storage and the like are solved.
Referring to fig. 2, fig. 2 is a schematic flowchart of a data processing method provided in this embodiment, and is applied to a Sawtooth network, where the Sawtooth network includes a management node, at least one node, and a corresponding node proxy, and this embodiment may be executed by the management node, and as shown in the drawing, the data processing method may include:
s201: and the management node receives and stores the unique configuration information of the corresponding node sent by each node agent. The node agent may be the node agents 111 shown in fig. 1, each node agent 111 corresponds to a node, and the node may be the sawteeth node 110 shown in fig. 1. The unique configuration information includes public access connection information, a node public key, a node name, and the like of a corresponding node of each node agent, and the public access connection information may be 192.168.56.101, 8800, for example.
In one embodiment, the management node includes an interface presentation module, a background service module, and a storage module, and may pre-configure connection information (e.g., an Internet Protocol Address (IP) and a port, etc.) of the management node for communicating with the node agent, for example: 192.168.56.100:6060. When the management node detects a management node starting instruction, the interface display module, the background service module and the storage module can be started automatically.
Further, for the configuration of each node agent, not only the connection information of the management node needs to be configured for connecting the management node, but also unique configuration information of the corresponding node of each node agent needs to be configured. Further, after the configuration is completed, each node agent may be automatically connected to the management node according to the connection information of the configured management node, while transmitting unique configuration information of the corresponding node to the management node. After receiving the unique configuration information of the corresponding node sent by each node agent, the management node may store the unique configuration information of each node in the storage module.
In one embodiment, before the management node stores the unique configuration information of any one of the nodes in the storage module, it may further verify whether the configuration format of the unique configuration information meets the requirement, and if it is detected that the configuration format of the unique configuration information meets the requirement, the unique configuration information of any one of the nodes is stored in the storage module. In another embodiment, if it is detected that the configuration format of the unique configuration information does not meet the requirement (for example, the number of bits of the public access connection information is not equal to the preset number of bits, the format of the public key of the node is incorrect, etc.), an alarm message for the unique configuration information is output to the node agent corresponding to the any node, so as to prompt that the any node is wrong with the format of the user unique configuration information.
S202: the management node sends a first starting instruction to the first node agent, wherein the first starting instruction is used for indicating the first node to generate the shared configuration information, and the first node is a creation node. The shared configuration information comprises a network communication encryption public and private key, a pbft common identification member list, a network address addressing list and the like.
S203: the management node receives and stores the shared configuration information sent by the first node agent, so that the first node agent obtains the shared configuration information and the unique configuration information of the first node from the management node to start the first node.
In an embodiment, the management node may present a node management list, where the node management list includes a node identifier of each node in the at least one node, and further, the management node may determine, according to the node identifier selected from the node list, a first node corresponding to the node identifier as an ancestor node.
Illustratively, the management node may display the node identifiers of the nodes in a form of a list in a display screen, and the user may select any one of the node identifiers and input an ancestor node selection operation for the any one of the node identifiers. For this case, the management node may determine a node corresponding to any node identifier as an ancestor node. The input mode of the creature node selection operation can be voice, pressing, clicking, sliding and the like. For example, the node identifier of one node shown in the node management list is "01", the user inputs a voice "select 01 node as a founder node" (i.e., a founder node selection operation), the management node can recognize the voice, and the node corresponding to the node identifier of 01 is determined as a founder node in the node management list.
Further, after determining the created node (i.e., the first node), the management node may send a first start instruction to a node agent (i.e., the first node agent) corresponding to the created node. The first node agent may generate shared configuration information according to the first start instruction and upload the shared configuration information to the management node, and the management node may store the shared configuration information in the storage module after receiving the shared configuration information. Further, the first node agent may acquire configuration information required for startup of the founder node from the management node (the configuration information required for startup includes unique configuration information of the first node itself and shared configuration information) to generate a configuration file, and the node agent may start the founder node according to the configuration file.
The unique configuration information and the shared configuration information are all obtained from the management node in a unified mode, so that the configuration information and the shared configuration information of the creation node can be guaranteed not to be modified locally and manually, and the configuration consistency is guaranteed.
In an embodiment, before the management node stores the shared configuration information in the storage module, it may further verify whether the configuration format of the shared configuration information meets the requirement, and if it is detected that the configuration format of the shared configuration information meets the requirement, the shared configuration information is stored in the storage module. In another embodiment, if it is detected that the configuration format of the shared configuration information does not meet the requirement, an alarm message for the shared configuration information is output to the first node agent, so as to prompt that the first node is wrong in the user shared configuration information format, and thus, the user can conveniently reconfigure the correct shared configuration information.
Illustratively, the shared configuration information includes a list of consensus members, assuming that the correct list of consensus members is configured to: "abcedfg", "uuenske", "sswerqk", "surfer" ], in a manual configuration manner, the network administrator needs to ensure that the configuration format of the common member list must be correct, if the administrator carelessly inputs a double quotation mark less, so that after the wrong configuration format data is linked up, a component depending on the wrong configuration format data is crashed, and after the component is crashed, the sawthoth network cannot process new data, and due to the characteristic that the blockchain cannot be tampered with, the network administrator cannot restore the configuration, thereby causing the whole network to fail permanently. For this situation, if the management node detects that the number of the double quotations of the common member list in the shared configuration information sent by the first proxy node is not equal to the preset threshold value (e.g. 4), it may determine that the configuration format of the common member list is incorrect and not compliant, and further determine that the configuration format of the shared configuration information is incorrect. Further, an alarm message for the shared configuration information may be sent to the first proxy node, so as to prompt that the first node has an error in the configuration format of the user consensus member list, thereby facilitating the user to reconfigure the correct consensus member list.
S204: and the management node sends a second starting instruction to the second node agent, wherein the second starting instruction is used for indicating the second node agent to acquire the shared configuration information and the unique configuration information of the second node from the management node so as to start the second node, and the second node is a non-invasive node.
And the second node agent is a node agent corresponding to any non-generative node. In an embodiment, for a newly built Sawtooth network, after detecting that an authored node is started, a management node may automatically send a second start instruction to a node proxy (i.e., a second node proxy) corresponding to a non-authored node, and after receiving the second start instruction, the second node proxy may obtain configuration information (the configuration information includes unique configuration information and shared configuration information of the second node) required for starting the corresponding second node from the management node to generate a configuration file corresponding to the second node, and the second node proxy starts the corresponding second node according to the configuration file.
After all the second nodes are started, the establishment of the Sawtoth network is completed. It can be seen that, in this way, the management node can assist in managing relevant information (for example, unique configuration information, shared configuration information, and the like) of the sawteeth network, and the node agent executes commands (for example, a first start instruction, a second start instruction, and the like) of the management node, so that a network administrator does not need to separately log in a server deployed by each node in the sawteeth network to edit a configuration file (for example, unique configuration information, shared configuration information, and the like), build and start the node, which not only greatly saves the workload of the sawteeth network administrator, but also is beneficial to improving the building efficiency of the sawteeth network.
In one embodiment, the user may manage the nodes through the node management list. In this case, the management node may detect a management operation input for the node to be managed in the node management list, determine the node corresponding to the management operation as the node to be managed, and send a management instruction corresponding to the management operation to the node agent corresponding to the node to be managed, where the management is used to instruct the node agent corresponding to the node to be managed to perform node management on the node to be managed, and the node management includes at least one of starting the node to be managed, restarting the node to be managed, stopping the node to be managed, and deleting the node to be managed. The input mode of the management operation may be voice, sliding, clicking, pressing, and the like.
Illustratively, the management operation may include a combination of a selection operation on any node identifier and a selection operation on a target management option, where the target management option is any one of a plurality of management options presented on a corresponding display page of the node management list, and the plurality of management options include "start", "restart", "stop", and "delete". After the user clicks the node identifier of any one node in the node management list (i.e., the selection operation is input to the node identifier of any one node), the management node may display a plurality of management options on a display page of the node management list, and the user inputs the selection operation for a target management option. In this case, the management node may determine any node as a node to be managed, and send a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed, where the management instruction is used to instruct the node agent corresponding to the node to be managed to perform node management on the node to be managed, where the node management is matched with the target management option. For example, if the target management option selected by the user is "stop", the management instruction is used to instruct the node agent corresponding to the node to be managed to stop starting the node to be managed; for another example, if the target management option selected by the user is "delete", the management instruction is used to instruct the node agent corresponding to the node to be managed to delete the node to be managed.
In an embodiment, it is assumed that the management operation is a deletion operation for instructing to delete the node to be managed, in this case, before the management node sends a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed, a consensus member list may be obtained from the shared configuration information, the management node verifies the management operation based on the consensus member list, and if the verification passes, the step of sending the management instruction corresponding to the management operation to the node agent corresponding to the node to be managed is triggered and executed.
In one embodiment, when the number of the common member lists in the modified shared configuration information is less than the preset threshold number of the common member lists, a component dependent on the shared configuration information crashes, and after the component crashes, the sawteeth network cannot process new data. Due to the fact that the blockchain cannot be tampered with, an administrator cannot restore the configuration, and therefore the whole network is permanently disabled. In order to solve the above problem, the management node may verify the deletion operation based on the consensus member list, specifically, if the management node predicts that the to-be-managed node corresponding to the deletion operation is deleted in response to the deletion operation, and then the number of the consensus member list is smaller than the threshold of the number of the preset consensus member list, it is determined that the deletion operation is not verified, and accordingly, the deletion operation is not responded, that is, the step of sending the management instruction corresponding to the management operation to the node agent corresponding to the to-be-managed node is not triggered.
On the contrary, if the management node predicts that the number of the consensus member list is not less than the preset threshold of the number of the consensus member list after deleting the to-be-managed node corresponding to the deletion operation in response to the deletion operation, it is determined that the deletion operation is verified, and accordingly, the deletion operation may be responded, that is, a step of triggering execution of a management instruction corresponding to the management operation to be sent to a node agent corresponding to the to-be-managed node is performed.
In this embodiment of the application, the management node may receive and store the unique configuration information of the corresponding node sent by each node agent, and send a first start instruction to the first node agent, where the first start instruction is used to instruct the first node to generate shared configuration information. Further, the management node may further send a second start instruction to the second node agent, where the second start instruction is used to instruct the second node agent to obtain the shared configuration information and the unique configuration information of the second node from the management node to start the second node. By adopting the mode, the related information of the Sawtoth network can be managed in an auxiliary mode through the management node, and the commands (such as the first starting command, the second starting command and the like) of the management node are executed through the node agent, so that a user does not need to log in a server deployed by each node in the Sawtoth network to edit configuration files (such as unique configuration information, shared configuration information and the like) for building and starting the node aiming at the building of the Sawtoth network, the workload of a Sawtoth network administrator is greatly saved, and the building efficiency of the Sawtoth network is improved.
Referring to fig. 3, fig. 3 is a schematic flowchart of another data processing method provided in this embodiment, which is applied to a Sawtooth network, where the Sawtooth network includes a management node and at least one node and a corresponding node agent, and this embodiment may be executed by the management node, and as shown in the drawing, the data processing method may include:
s301: and the management node receives and stores the unique configuration information of the corresponding node sent by each node agent.
S302: the management node sends a first starting instruction to the first node agent, wherein the first starting instruction is used for indicating the first node to generate the shared configuration information, and the first node is a creation node.
S303: the management node receives and stores the shared configuration information sent by the first node agent, so that the first node agent acquires the shared configuration information and the unique configuration information of the first node from the management node to start the first node.
S304: and the management node sends a second starting instruction to the second node agent, wherein the second starting instruction is used for indicating the second node agent to acquire the shared configuration information and the unique configuration information of the second node from the management node so as to start the second node, and the second node is a non-invasive node. For specific implementation of steps S301 to S304, reference may be made to the relevant description of steps S201 to S204 in the foregoing embodiment, and details are not described here again.
S305: the management node receives node state information of each corresponding node sent by each node agent, wherein the node state information comprises one or more of node running state, central processing unit information, memory information, network information, disk information and application logs. The node operating state is a node operating state of a node corresponding to each node agent, and the central processing unit information, the memory information, the network information and the disk information may be related information of a server deployed by the node agent.
S306: and the management node displays the node state information of the corresponding node sent by each node agent.
In one embodiment, the management node may show the node status information of the respective corresponding node sent by each node agent through the display device. For example, the management node may present the node status information in a node management list, where each node identifier corresponds to one node status information. By adopting the mode, a user can uniformly monitor the running state of each node, not only can timely process network faults, but also can timely manage the nodes according to the running state of each node, wherein the management comprises at least one of starting the nodes to be managed, restarting the nodes to be managed, stopping the nodes to be managed and deleting the nodes to be managed, and the nodes to be managed are any nodes which are selected by the user and need to be managed.
In one embodiment, the management node may receive and store unique configuration information of the new node corresponding to the new node sent by the new node agent, and display the unique configuration information of each new node, and if the management node receives a confirmation instruction for the new node, send a new node start instruction to the new node agent to instruct the new node agent to obtain the shared configuration information and the unique configuration information of the new node from the management node to start the new node.
In one embodiment, when a node agent (i.e., a newly added node agent) and a node corresponding to the node agent (i.e., a newly added node) are newly built in the sawteeth network, configuration of the newly added node agent is required, where the configuration includes connection information for configuring a management node, unique configuration information for connecting the management node, and unique configuration information for configuring the newly added node. Further, after the agent of the newly added node is successfully started, the newly added node can be automatically connected with the management node, the unique configuration information corresponding to the newly added node is sent to the management node, and the management node stores the received unique configuration information of the newly added node in the storage module.
Further, the management node may display the unique configuration information of the newly added node, the user may check the unique configuration information of the newly added node, and if the user agrees that the newly added node joins the sawteeth network, a confirmation instruction is input. And the management node sends a new node starting instruction to the new node agent after receiving the confirmation instruction aiming at the new node, and the new node agent can acquire the shared configuration information and the unique configuration information of the new node from the management node to generate a configuration file required by starting the new node and further start the new node based on the configuration file.
In one embodiment, after receiving the confirmation instruction for the newly added node, the management node automatically verifies and updates the unique configuration of the newly added node without manually updating the unique configuration information of the newly added node by the user. In specific implementation, the management node can automatically verify whether the unique configuration information of the newly added node is legal or not, and if so, the unique configuration information of the newly added node is stored in the storage module to update the unique configuration information of the newly added node; and if the new node is illegal, the unique configuration information of the new node is not stored, and alarm information aiming at the unique configuration information of the new node is output to the new node agent and used for prompting that the unique configuration information of the new node is illegal.
Illustratively, the unique configuration information includes a public key of the newly added node, the management node may verify whether the public key of the newly added node is in a black-and-white list, if the public key of the newly added node is in the white list, it is determined that the public key of the newly added node is legal, and if the public key of the newly added node is in the black list, it is determined that the public key of the newly added node is illegal, that is, it may be determined that the unique configuration information of the newly added node is illegal.
In one embodiment, the management node may obtain configuration information to be updated, the configuration information including shared configuration information and/or unique configuration information of a target node, the target node being any one of the at least one node. Further, the management node checks the configuration information to be updated, and if the check is passed, the shared configuration information and/or the unique configuration information of the target node are/is updated by using the configuration information to be updated.
In one embodiment, the user may update the relevant configuration information through a management interface of the management node. For example, if the user updates the unique configuration information of the target node through the management interface, the management node may obtain the unique configuration information of the target node updated by the user (hereinafter referred to as the unique configuration information to be updated), check the format of the unique configuration information to be updated, and if the format meets the format requirement of the unique configuration information, determine that the check on the unique configuration information to be updated is passed, and update the pre-stored unique configuration information of the target node with the unique configuration information to be updated.
Or, if the user updates the shared configuration information through the management interface, the management node may acquire shared configuration information (hereinafter, referred to as shared configuration information to be updated) updated by the user, check the format of the shared configuration information to be updated, and if the format meets the format requirement of the shared configuration information, determine that the shared configuration information to be updated passes the check, and update the pre-stored shared configuration information by using the shared configuration information to be updated.
Because some of the Sawtoth networks are configured with strict requirements, in order to avoid network failure caused by artificial mismatch, the management node can automatically check the legality of the configuration information to be updated, and illegal configuration information is avoided. For example, assuming that the shared configuration information includes a consensus member list, the consensus member list currently stored by the management node is configured to: and the user updates the list of the consensus members through a management interface, and the user inputs one double quotation mark less in the updating process. For such a situation, the management node may obtain an updated consensus member list (hereinafter referred to as an to-be-updated consensus member list) input by the user, detect the format of the to-be-updated consensus member list, and determine that the number 3 of double quotations in the to-be-updated consensus member list is not equal to the preset double quotation number threshold 4, that the to-be-updated consensus member list does not meet the format requirement of the consensus member list, and further determine that the check on the to-be-updated consensus member list does not pass.
Alternatively, during the update process, the user enters a correctly formatted list of consensus members. In this case, if the management node determines that the consensus member list to be updated meets the format requirement of the consensus member list, the pre-stored consensus member list may be updated through the consensus member list to be updated.
For this situation, in an embodiment, the configuration information to be updated includes the unique configuration information of the target node, and after the management node updates the unique configuration information of the target node by using the configuration information to be updated, the management node may send a restart instruction to the node proxy corresponding to the target node to instruct the node proxy corresponding to the target node to acquire the shared configuration information and the updated unique configuration information of the target node from the management node to restart the target node.
It can be seen that, in the embodiment of the application, on one hand, a user can quickly and efficiently change the relevant configuration information through the management interface without sequentially logging in servers deployed by each node in the sawteeth network to manually change the configuration, so that the updating efficiency of the configuration information can be improved; on the other hand, after the unique configuration information of the target node is updated, the target node can be automatically restarted to enable the updated unique configuration information to take effect, and the effectiveness efficiency of the updated unique configuration information is improved.
In this embodiment of the application, the management node may receive and store the unique configuration information of the corresponding node sent by each node agent, and send a first start instruction to the first node agent, where the first start instruction is used to instruct the first node to generate shared configuration information. Further, the management node may further send a second start instruction to the second node agent, the second start instruction being used to instruct the second node agent to acquire the shared configuration information and the unique configuration information of the second node from the management node to start the second node. Furthermore, the management node can receive and display the node state information of each corresponding node sent by each node agent, and by adopting the mode, a user can uniformly monitor the operation state of each node, so that not only can network faults be processed in time, but also the nodes can be managed in time according to the operation state of each node.
Embodiments of the present application further provide a computer storage medium, in which program instructions are stored, and when executed, the program instructions are used to implement the corresponding method described in the foregoing embodiments.
An embodiment of the present application further provides a data processing apparatus, which includes a module configured to execute the method described in fig. 2 or fig. 3, and is configured to a management node in a Sawtooth network. Specifically, referring to fig. 4, a schematic block diagram of a data processing apparatus provided in an embodiment of the present application is shown. The data processing apparatus of the present embodiment includes:
a communication module 40, configured to receive unique configuration information of a corresponding node sent by each node agent;
a storage module 41, configured to store unique configuration information of a corresponding node sent by each node agent;
the communication module 40 is further configured to send a first start instruction to a first node agent, where the first start instruction is used to instruct a first node to generate shared configuration information, and the first node is an creature node;
the communication module 40 is further configured to receive shared configuration information sent by the first node agent;
the storage module 41 is further configured to store the shared configuration information sent by the first node agent, so that the first node agent obtains the shared configuration information and the unique configuration information of the first node from the management node to start the first node;
the communication module 40 is further configured to send a second start instruction to a second node agent, where the second start instruction is used to instruct the second node agent to obtain the shared configuration information and the unique configuration information of a second node from the management node to start the second node, and the second node is a non-created node.
In one embodiment, the apparatus further comprises an output module 42 and a processing module 43, wherein: the output module 42 is configured to display a node management list, where the node management list includes a node identifier of each node in the at least one node; the processing module 43 is configured to determine, according to the node identifier selected from the node list, a first node corresponding to the node identifier as an ancestor node.
In an embodiment, the communication module 40 is further configured to receive node state information of each corresponding node sent by each node agent, where the node state information includes one or more of a node running state, central processing unit information, memory information, network information, disk information, and an application log; the output module 42 is further configured to display node state information of each corresponding node sent by each node agent.
In one embodiment, the apparatus further comprises a detection module, wherein: the detection module is used for detecting the management operation input aiming at the node to be managed in the node management list; the processing module 43 is further configured to determine a node corresponding to the management operation as a node to be managed; the communication module 40 is further configured to send a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed, where the management instruction is used to instruct the node agent corresponding to the node to be managed to perform node management on the node to be managed, and the node management includes at least one of starting the node to be managed, restarting the node to be managed, stopping the node to be managed, adding the node to be managed, and deleting the node to be managed.
In an embodiment, the management operation is a deletion operation for instructing to delete the node to be managed, and the processing module 43 is further configured to obtain a consensus member list from the shared configuration information; and the management node verifies the management operation based on the consensus member list, and if the verification is passed, the communication module 40 is triggered to execute the management instruction corresponding to the management operation sent to the node agent corresponding to the node to be managed.
In one embodiment, the communication module 40 is further configured to receive unique configuration information of a new node corresponding to a new node sent by a new node agent; a storage module 41, further configured to store unique configuration information of the newly added node agent corresponding to the newly added node; the output module 42 is further configured to display the unique configuration information of the newly added node; the communication module 40 is further configured to, if a confirmation instruction for the new node is received through the detection module, send a new node start instruction to the new node agent to instruct the new node agent to acquire the shared configuration information and the unique configuration information of the new node from the management node to start the new node.
In an embodiment, the processing module 43 is further configured to obtain configuration information to be updated, where the configuration information includes the shared configuration information and/or unique configuration information of a target node, the target node is any node in the at least one node, the management node verifies the configuration information to be updated, and if the verification passes, the shared configuration information and/or the unique configuration information of the target node is updated by using the configuration information to be updated.
In an embodiment, the configuration information to be updated includes unique configuration information of the target node, and the communication module 40 is further configured to send a restart instruction to a node agent corresponding to the target node to instruct the node agent corresponding to the target node to acquire the shared configuration information and the updated unique configuration information of the target node from the management node to restart the target node.
It should be noted that the functions of the functional modules of the data processing apparatus described in the embodiment of the present application may be specifically implemented according to the method in the method embodiment described in the foregoing fig. 2 or fig. 3, and a specific implementation process thereof may refer to the related description of the method embodiment in fig. 2 or fig. 3, which is not described herein again.
Referring to fig. 5, fig. 5 is a schematic block diagram of a server according to an embodiment of the present disclosure, and as shown in fig. 5, the server is connected with a display device and is deployed in a Sawtooth network, the Sawtooth network further includes at least one node and a node agent corresponding to each node, and the server includes a processor 501, a memory 502, and a communication interface 503. The processor 501, the memory 502 and the communication interface 503 may be connected by a bus or other means, and in fig. 5 shown in the embodiment of the present application, the bus connection is taken as an example. Wherein the communication interface 503 is controlled by the processor for transceiving messages, the memory 502 is for storing a computer program comprising program instructions, and the processor 501 is for executing the program instructions stored by the memory 502. Wherein, the processor 501 is configured to call the program instruction to execute: receiving unique configuration information of the corresponding node transmitted by each node agent through the communication interface 503, and storing the unique configuration information to the memory 502; sending a first start instruction to a first node agent through a communication interface 503, where the first start instruction is used to instruct a first node to generate shared configuration information, and the first node is an ancestor node;
receiving the shared configuration information sent by the first node agent through the communication interface 503 and storing the shared configuration information to the memory 502, so that the first node agent acquires the shared configuration information and the unique configuration information of the first node from the management node to start the first node; sending a second start instruction to a second node agent through the communication interface 503, where the second start instruction is used to instruct the second node agent to obtain the shared configuration information and the unique configuration information of a second node from the management node to start the second node, where the second node is a non-created node.
In an embodiment, the processor 501 is further configured to display a node management list through a display device, where the node management list includes a node identifier of each node in the at least one node; the processor 501 is configured to determine, according to a node identifier selected from the node list, a first node corresponding to the node identifier as an created node.
In an embodiment, the processor 501 is further configured to receive, through the communication interface 503, node state information of each corresponding node sent by each node agent, where the node state information includes one or more of a node running state, central processing unit information, memory information, network information, disk information, and an application log; the processor 501 is further configured to display, through a display device, node state information of each corresponding node sent by each node agent.
In one embodiment, the processor 501 is further configured to detect, through a display device, a management operation input for a node to be managed in the node management list; the processor 501 is further configured to determine a node corresponding to the management operation as a node to be managed, and send a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed through a communication interface 503, where the management instruction is used to instruct the node agent corresponding to the node to be managed to perform node management on the node to be managed, and the node management includes at least one of starting the node to be managed, restarting the node to be managed, stopping the node to be managed, adding the node to be managed, and deleting the node to be managed.
In an embodiment, the management operation is a deletion operation for instructing to delete the node to be managed, and the processor 501 is further configured to obtain a consensus member list from the shared configuration information; the management node verifies the management operation based on the consensus member list, and if the verification is passed, the management node triggers the communication interface 503 to execute a management instruction corresponding to the management operation sent to the node agent corresponding to the node to be managed.
In one embodiment, the processor 501 is further configured to receive, through the communication interface 503, unique configuration information of a new node corresponding to a new node sent by a new node agent, and store, through the memory 502, the unique configuration information of the new node corresponding to the new node agent; displaying the unique configuration information of the newly added node through a display device; and is further configured to send an additional node start instruction to the additional node agent through the communication interface 503 if a confirmation instruction for the additional node is received through the display device, so as to instruct the additional node agent to acquire the shared configuration information and the unique configuration information of the additional node from the management node to start the additional node.
In an embodiment, the processor 501 is further configured to obtain configuration information to be updated, where the configuration information includes the shared configuration information and/or unique configuration information of a target node, the target node is any node of the at least one node, the management node verifies the configuration information to be updated, and if the verification passes, the shared configuration information and/or the unique configuration information of the target node is updated by using the configuration information to be updated.
In an embodiment, the configuration information to be updated includes unique configuration information of the target node, and the processor 501 is further configured to send a restart instruction to a node proxy corresponding to the target node through the communication interface 503, so as to instruct the node proxy corresponding to the target node to acquire the shared configuration information and the updated unique configuration information of the target node from the management node to restart the target node.
It should be understood that, in the embodiment of the present Application, the Processor 501 may be a Central Processing Unit (CPU), and the Processor 501 may also be other general-purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 502 may include both read-only memory and random access memory, and provides instructions and data to the processor 501. A portion of memory 502 may also include non-volatile random access memory. For example, the memory 502 may also store device type information.
In a specific implementation, the processor 501, the memory 502, and the communication interface 503 described in this embodiment of the present application may execute the implementation described in the method embodiment described in fig. 2 or fig. 3 provided in this embodiment of the present application, and may also execute the implementation of the data processing apparatus described in this embodiment of the present application, which is not described herein again.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
While only some embodiments have been described in detail herein, it will be understood that all modifications and equivalents may be resorted to, falling within the scope of the invention.
Claims (8)
1. A data processing method applied to a sawteeth network including a management node and at least one node and corresponding node agent, the method comprising:
the management node receives and stores the unique configuration information of the corresponding node sent by each node agent;
the management node displays a node management list, wherein the node management list comprises node identifiers of all nodes in the at least one node;
the management node determines a first node corresponding to the node identification as an established node according to the node identification selected from the node management list;
the management node sends a first starting instruction to a first node agent, wherein the first starting instruction is used for indicating a first node to generate shared configuration information, and the first node is a created node;
the management node receives shared configuration information sent by the first node agent, and detects whether the configuration format of the shared configuration information meets the requirement;
if yes, the management node stores the shared configuration information sent by the first node agent, so that the first node agent can acquire the shared configuration information and the unique configuration information of the first node from the management node to start the first node;
if not, outputting alarm information aiming at the shared configuration information to the first node agent, wherein the alarm information is used for prompting that the format of the shared configuration information is wrong;
the management node sends a second starting instruction to a second node agent, wherein the second starting instruction is used for instructing the second node agent to acquire the shared configuration information and the unique configuration information of a second node from the management node so as to start the second node, and the second node is a non-created node;
the management node acquires configuration information to be updated, wherein the configuration information comprises the shared configuration information and/or unique configuration information of a target node, and the target node is any one of the at least one node;
and the management node verifies the configuration information to be updated, and if the verification is passed, the shared configuration information and/or the unique configuration information of the target node are/is updated by adopting the configuration information to be updated.
2. The method of claim 1, further comprising:
the management node receives node state information of each corresponding node sent by each node agent, wherein the node state information comprises one or more of node running state, central processing unit information, memory information, network information, disk information and application logs;
and the management node displays the node state information.
3. The method of claim 1, further comprising:
the management node detects management operation input aiming at the node to be managed in the node management list;
and the management node sends a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed, wherein the management instruction is used for indicating the node agent corresponding to the node to be managed to perform node management on the node to be managed, and the node management comprises at least one of starting the node to be managed, restarting the node to be managed, stopping the node to be managed and deleting the node to be managed.
4. The method according to claim 3, wherein the management operation is a deletion operation for instructing deletion of the node to be managed, and before the management instruction corresponding to the management operation is sent to the node agent corresponding to the node to be managed, the method further comprises:
the management node acquires a consensus member list from the shared configuration information;
and the management node verifies the management operation based on the consensus member list, and if the verification is passed, the step of sending a management instruction corresponding to the management operation to a node agent corresponding to the node to be managed is triggered and executed.
5. The method of claim 1, further comprising:
the management node receives and stores the unique configuration information of the newly added node corresponding to the newly added node sent by the newly added node agent;
the management node displays the unique configuration information of the newly added node;
if the management node receives a confirmation instruction aiming at the newly added node, a newly added node starting instruction is sent to the newly added node agent so as to instruct the newly added node agent to acquire the shared configuration information and the unique configuration information of the newly added node from the management node so as to start the newly added node.
6. The method of claim 1, wherein the configuration information to be updated comprises unique configuration information of the target node, and wherein after updating the unique configuration information of the target node with the configuration information to be updated, the method further comprises:
and the management node sends a restart instruction to a node proxy corresponding to the target node to instruct the node proxy corresponding to the target node to acquire the shared configuration information and the updated unique configuration information of the target node from the management node so as to restart the target node.
7. A data processing apparatus, wherein the apparatus is applied to a management node in a sawteeth network, the sawteeth network further including at least one node and a corresponding node agent, the apparatus comprising:
the communication module is used for receiving the unique configuration information of the corresponding node sent by each node agent;
the storage module is used for storing the unique configuration information of the corresponding node sent by each node agent;
an output module, configured to display a node management list, where the node management list includes a node identifier of each node in the at least one node;
the processing module is used for determining a first node corresponding to the node identification as an founding node according to the node identification selected from the node management list; the node configuration information updating system is further configured to obtain configuration information to be updated, where the configuration information includes shared configuration information and/or unique configuration information of a target node, and the target node is any one of the at least one node; verifying the configuration information to be updated, and if the configuration information to be updated passes the verification, updating the shared configuration information and/or the unique configuration information of the target node by adopting the configuration information to be updated;
the detection module is used for detecting whether the configuration format of the shared configuration information sent by the first node agent meets the requirement, if so, the shared configuration information is stored in the storage module, and if not, the alarm information aiming at the shared configuration information is output to the first node agent through the output module; the alarm information is used for prompting that the format of the shared configuration information is wrong;
the communication module is further configured to send a first start instruction to a first node agent, where the first start instruction is used to instruct the first node to generate shared configuration information, and the first node is an established node;
the communication module is further configured to receive shared configuration information sent by the first node agent;
the storage module is further configured to store the shared configuration information sent by the first node agent, so that the first node agent obtains the shared configuration information and the unique configuration information of the first node from the management node to start the first node;
the communication module is further configured to send a second start instruction to a second node proxy, where the second start instruction is used to instruct the second node proxy to acquire the shared configuration information and unique configuration information of a second node from the management node to start the second node, and the second node is a non-invasive node.
8. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which is executed by a processor to implement the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910937430.9A CN110620695B (en) | 2019-09-29 | 2019-09-29 | Data processing method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910937430.9A CN110620695B (en) | 2019-09-29 | 2019-09-29 | Data processing method and related equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110620695A CN110620695A (en) | 2019-12-27 |
| CN110620695B true CN110620695B (en) | 2022-11-15 |
Family
ID=68925047
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910937430.9A Active CN110620695B (en) | 2019-09-29 | 2019-09-29 | Data processing method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110620695B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113125764B (en) * | 2019-12-30 | 2023-08-25 | 深圳迈瑞生物医疗电子股份有限公司 | Sample analyzer, automatic maintenance method thereof and readable storage medium |
| CN111654532B (en) * | 2020-05-08 | 2023-08-01 | 国云科技股份有限公司 | Centralized management system, method and device for configuration files |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332701A (en) * | 2017-06-26 | 2017-11-07 | 中国人民银行数字货币研究所 | The method and system of management node |
| CN109246179A (en) * | 2018-06-30 | 2019-01-18 | 华为技术有限公司 | Safeguard method and apparatus, server and the computer readable storage medium of block chain |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170346639A1 (en) * | 2016-05-24 | 2017-11-30 | Business Information Exchange System Corp. | Public Key Infrastructure based on the Public Certificates Ledger |
| CN109728954B (en) * | 2019-01-04 | 2022-03-04 | 深圳壹账通智能科技有限公司 | Federation node point management system and method |
| CN110138586A (en) * | 2019-04-04 | 2019-08-16 | 平安科技（深圳）有限公司 | Block chain node administration method, electronic device, system and readable storage medium storing program for executing |
-
2019
- 2019-09-29 CN CN201910937430.9A patent/CN110620695B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332701A (en) * | 2017-06-26 | 2017-11-07 | 中国人民银行数字货币研究所 | The method and system of management node |
| CN109246179A (en) * | 2018-06-30 | 2019-01-18 | 华为技术有限公司 | Safeguard method and apparatus, server and the computer readable storage medium of block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110620695A (en) | 2019-12-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020140667A1 (en) | Consortium blockchain node management system and method | |
| CN107241315B (en) | Access method and device of bank gateway interface and computer readable storage medium | |
| US20060195820A1 (en) | Method and system for version negotiation of distributed objects | |
| JP2003099410A (en) | Multiple device management method and system | |
| US20220237295A1 (en) | Remote Attestation Method and Device for Composite Device | |
| US11044156B2 (en) | Secure mechanism to manage network device configuration and audit with a blockchain | |
| CN110620695B (en) | Data processing method and related equipment | |
| CN111984561B (en) | IPMI command processing method, system, device and medium for BMC | |
| US9292355B2 (en) | Broker system for a plurality of brokers, clients and servers in a heterogeneous network | |
| CN112714158A (en) | Transaction processing method, relay network, cross-link gateway, system, medium, and device | |
| CN112583630B (en) | Device management method, device, system, device and storage medium | |
| WO2020220938A1 (en) | Data acquisition method, apparatus, device, and computer readable storage medium | |
| CN109189403B (en) | Operating system OS batch installation method and device and network equipment | |
| CN107301053B (en) | Picture configuration method and device and electronic terminal | |
| CN111488163B (en) | Firmware updating method and device, electronic equipment and storage medium | |
| CN112130889A (en) | Resource management method and device, storage medium and electronic device | |
| CN104104701A (en) | Online service configuration updating method and system | |
| CN112291081A (en) | Method, system and storage medium for auditing controller cluster data by cloud management platform | |
| CN110930110A (en) | Distributed flow monitoring method and device, storage medium and electronic equipment | |
| WO2020037607A1 (en) | Data transmission method and apparatus | |
| JP2006113754A (en) | Software update device and method | |
| US7568194B2 (en) | Method and system for availability checking on distributed objects | |
| US11379434B2 (en) | Efficient and automatic database patching using elevated privileges | |
| Cisco | 9.0.03 Version Software Release Notes Cisco StrataView Plus for AIX | |
| CN111858100A (en) | BMC message transmission method and related 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 |