CN111614702B - Edge calculation method and edge calculation system - Google Patents
Edge calculation method and edge calculation system Download PDFInfo
- Publication number
- CN111614702B CN111614702B CN201910133148.5A CN201910133148A CN111614702B CN 111614702 B CN111614702 B CN 111614702B CN 201910133148 A CN201910133148 A CN 201910133148A CN 111614702 B CN111614702 B CN 111614702B
- Authority
- CN
- China
- Prior art keywords
- edge
- metadata
- node
- edge node
- resource
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Abstract
The embodiment of the application discloses an edge computing method and an edge computing system, which are used for reducing the number of long connections between edge nodes and management nodes and saving edge resources. The method in the embodiment of the application comprises the following steps: the edge manager calls the k8s Master to create an edge node, and stores the creation information of the edge node in the metadata store, wherein the creation information is used for indicating that the edge node belongs to the k8s Master; the edge controller obtains the creation information of the edge node from the metadata storage; the edge controller establishes a long connection with the k8s Master according to the creation information; the edge controller monitors the resource metadata attributed to the edge node in the k8s Master according to the long connection; when the resource metadata changes, the edge controller sends a notification message to the edge node, wherein the notification message is used for indicating the changed data of the resource metadata; and the edge node performs corresponding calculation processing according to the change data.
Description
Technical Field
The present application relates to the field of cloud computing, and in particular, to an edge computing method and an edge computing system.
Background
The Internet of things is an important component of a new generation of information technology and is also an important development stage of the information era. The internet of things is a network which connects sensors, controllers, machines, personnel, objects and the like together in a new mode by utilizing communication technologies such as local networks or the internet and the like to form the connection between people and objects and between objects and realize informatization, remote management control and intellectualization. In the current mainstream internet of things technology, the basic operation idea is that the edge device sends the acquired data to a data center; then the data center carries out operation processing and analysis to obtain an operation instruction, and the operation instruction is issued to the edge device; and finally, the edge equipment executes the operation instruction to obtain the result required by the user. In the mode, the intelligence degree of the whole internet of things completely depends on the data center, and the edge equipment only has the functions of simple data acquisition, transmission, final instruction execution and the like. Once the network communication between the edge device and the data center is interrupted, the whole internet of things system may be in an unusable state. To solve this problem, intelligent edge computation is proposed. Intelligent edge computation proposes a new model: each edge device of the Internet of things is provided with data acquisition, analysis and calculation, communication and the most important intelligence. The intelligent edge computing also utilizes the cloud computing capability, utilizes the cloud computing to perform large-scale security configuration, deployment and management of the edge equipment, and can distribute the computing capability according to the equipment type and scene, so that the computing capability flows between the cloud and the edge, and the result of the two beauty is obtained.
The current intelligent edge computing typically employs kubernets technology. The Kubernetes is a distributed cluster and is composed of management nodes (Master-nodes) and nodes (nodes). The Master-node mainly runs core components such as an application programming interface server (api server), a scheduler (scheduler), a controller (controller), a memory (etcd), and the node mainly runs components such as a kubel. And the Master-node and the node perform interaction in a command declaration mode to complete the management of the resources. The kubel operated by the node establishes a plurality of long connections with the Master-node, respectively monitors (watch) resource changes of services, nodes, pod and the like, and correspondingly processes the resource changes.
In this mode, each node establishes multiple long connections with the Master-node, respectively, which is a resource consumption for the edge scene with limited resources.
Disclosure of Invention
The embodiment of the application provides an edge calculation method and device, which are used for reducing the number of long connections between edge nodes and management nodes, so that edge resources are saved.
In a first aspect, an embodiment of the present application provides an edge computing method, which is applied to an edge computing system, where the edge computing system includes an edge controller, an edge manager, a k8s Master, and a metadata store; the edge manager calls the k8s Master to create an edge node and stores the creation information of the edge node in the metadata store, wherein the creation information is used for indicating that the edge node belongs to the k8s Master; the edge controller obtains the creation information of the edge node from the metadata storage; after the edge controller acquires the creation information, the edge controller uses the creation information to proxy the edge node to establish a long connection with the k8s Master, and monitors resource metadata belonging to the edge node in the k8s Master through the long connection; when the resource metadata of the edge node changes, the edge controller sends a notification message to the edge node, wherein the notification message is used for indicating the change data of the resource metadata; and finally, the edge node performs corresponding calculation processing according to the changed data.
In the technical solution provided in the embodiment of the present application, an edge controller in the edge computing system proxies the edge node to establish a long connection with the k8s Master, and then the edge controller monitors resource metadata corresponding to the edge node in the k8s Master through the long connection; when the resource metadata changes, the edge controller notifies the edge node of the change data of the resource metadata, so that the edge node performs corresponding calculation processing according to the variable data. Therefore, the edge node reduces a plurality of connections with the k8s Master, and only one connection is established between the edge node and the edge controller for signaling interaction, so that resources in an edge scene are saved.
Optionally, the edge node may also store the change data.
Optionally, the edge node includes edge metadata management, edge metadata storage, and Kubelet;
the edge node storing the change data includes:
the edge metadata management receives the change data sent by the edge controller;
the edge metadata management synchronizing the change data to the edge metadata store;
the edge metadata store maintains the change data.
Meanwhile, the edge node may further store resource metadata allocated by the k8s Master to the edge node, and the specific operations are as follows: the edge metadata management receives resource metadata sent by the edge controller; the edge metadata management synchronizing the resource metadata to the edge metadata store; the edge metadata store stores the resource metadata.
On the basis, when the edge node is restarted offline, the Kubelet in the edge node acquires the resource metadata and the change data from the edge metadata storage; the edge node then resumes operation using the resource metadata and the change data and performs computational processing.
In the embodiment of the application, the edge node stores the resource metadata distributed by the k8s Master to the edge node and corresponding resource metadata change data in the running process, so that in the process of offline restart of the edge node, the edge node can directly acquire the resource metadata and the resource metadata change data to restore running. Therefore, the edge node does not need to acquire resource metadata by establishing connection with the k8s Master, and the self-running of the edge node is further realized.
In a second aspect, an embodiment of the present application provides an edge computing method, which is applied to an edge computing system, where the edge computing system includes an edge manager, a k8s Master, and a metadata store; the edge manager calls the k8s Master to create an edge node and stores the creation information of the edge node in the metadata store; the k8s Master allocates resource metadata for the edge node and sends the resource metadata to the edge node; the edge node saves the resource metadata; when the edge node is restarted off line, the edge node resumes running by using the resource metadata.
In this embodiment of the present application, the edge node stores the resource metadata allocated by the k8s Master to the edge node, so that in the process of offline restart of the edge node, the edge node may directly obtain the resource metadata to resume running. Therefore, the edge node does not need to acquire resource metadata by establishing connection with the k8s Master, and the self-running of the edge node is further realized.
Optionally, the edge computing system further includes an edge controller, where the edge controller obtains creation information of the edge node from the metadata storage, where the creation information is used to indicate that the edge node belongs to the k8s Master, and uses the creation information to proxy that the edge node establishes a long connection with the k8s Master, and the edge controller establishes a communication channel with the edge node; the edge controller monitors the resource metadata of the edge node in the k8s Master using the long connection; when the resource metadata changes, the edge controller sends a notification message to the edge node through the communication channel, wherein the notification message is used for indicating the changed data of the resource metadata; and the edge node performs corresponding calculation processing according to the change data.
In the technical solution provided in this embodiment, an edge controller in the edge computing system proxies the edge node to establish a long connection with the k8s Master, and then the edge controller monitors resource metadata corresponding to the edge node in the k8s Master through the long connection; when the resource metadata changes, the edge controller notifies the edge node of the change data of the resource metadata, so that the edge node performs corresponding calculation processing according to the variable data. Therefore, the edge node reduces a plurality of connections with the k8s Master, and only one connection is established between the edge node and the edge controller for signaling interaction, so that resources in an edge scene are saved.
Optionally, the edge node may also store the change data.
Optionally, the edge node includes edge metadata management, edge metadata storage, and Kubelet;
the edge node storing the change data includes:
the edge metadata management receives the change data sent by the edge controller;
the edge metadata management synchronizing the change data to the edge metadata store;
the edge metadata store maintains the change data.
Meanwhile, the edge node may further store resource metadata allocated by the k8s Master to the edge node, and the specific operations are as follows: the edge metadata management receives resource metadata sent by the edge controller; the edge metadata management synchronizing the resource metadata to the edge metadata store; the edge metadata store stores the resource metadata.
In a third aspect, an embodiment of the present application provides an edge computing system, including an edge controller, an edge manager, a k8s Master, and a metadata store and an edge node;
the edge manager is used for calling the k8s Master to create an edge node and storing the creation information of the edge node in the metadata storage, wherein the creation information is used for indicating that the edge node belongs to the k8s Master;
the edge controller is used for acquiring the creation information of the edge node from the metadata storage; establishing long connection with the k8s Master according to the creation information; monitoring the resource metadata of the edge nodes in the k8s Master according to the long connection; when the resource metadata changes, sending a notification message to the edge node, wherein the notification message is used for indicating the changed data of the resource metadata;
and the edge node is used for performing corresponding calculation processing according to the change data.
In a fourth aspect, an embodiment of the present application provides an edge computing system, including an edge manager, a k8s Master, and a metadata store; the edge manager calls the k8s Master to create an edge node, and stores the creation information of the edge node in the metadata store, wherein the creation information is used for indicating that the edge node belongs to the k8s Master; the k8s Master allocates resource metadata for the edge node and sends the resource metadata to the edge node; the edge node saves the resource metadata; when the edge node is restarted off line, the edge node resumes running by using the resource metadata.
In a fifth aspect, the present application provides a computer-readable storage medium, which includes instructions, when the instructions are executed on a computer, the computer performs the above-mentioned method.
In a sixth aspect, embodiments of the present application provide a computer program product comprising instructions, which when run on a computer, the computer performs the above method.
According to the technical scheme, the embodiment of the application has the following advantages: the edge controller establishes a long connection with the k8s Master by using the edge controller to proxy the edge node in the edge computing system, and then monitors the resource metadata corresponding to the edge node in the k8s Master through the long connection; when the resource metadata changes, the edge controller notifies the edge node of the change data of the resource metadata, so that the edge node performs corresponding calculation processing according to the variable data. Therefore, the edge node reduces a plurality of connections with the k8s Master, and only one connection is established between the edge node and the edge controller for signaling interaction, so that resources in an edge scene are saved.
Drawings
FIG. 1 is a system architecture diagram of mainstream edge computation;
FIG. 2 is a system architecture diagram of an edge computing system in an embodiment of the present application;
FIG. 3 is a schematic diagram of an embodiment of an edge calculation method in an embodiment of the present application;
FIG. 4 is a schematic diagram of another embodiment of an edge calculation method in the embodiment of the present application;
FIG. 5 is a schematic diagram of an embodiment of an edge computing system in an embodiment of the present application;
fig. 6 is a schematic diagram of another embodiment of an edge computing system in an embodiment of the present application.
Detailed Description
The embodiment of the application provides an edge calculation method and device, which are used for reducing the number of long connections between edge nodes and management nodes, so that edge resources are saved.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The internet of things is an important component of a new generation of information technology. In the current mainstream internet of things technology, a basic operation thought is shown in fig. 1, and edge equipment sends acquired data to a data center; then the data center carries out operation processing and analysis to obtain an operation instruction, and the operation instruction is issued to the edge device; and finally, the edge equipment executes the operation instruction to obtain the result required by the user. In the mode, the intelligence degree of the whole internet of things completely depends on the data center, and the edge equipment only has the functions of simple data acquisition, transmission, final instruction execution and the like. Once the network communication between the edge device and the data center is interrupted, the whole internet of things system may be in an unusable state. To solve this problem, intelligent edge computation is proposed. Intelligent edge computation proposes a new model: each edge device of the Internet of things is provided with data acquisition, analysis and calculation, communication and the most important intelligence. The intelligent edge computing also utilizes the cloud computing capability, utilizes the cloud computing to perform large-scale security configuration, deployment and management of the edge equipment, and can distribute the computing capability according to the equipment type and scene, so that the computing capability flows between the cloud and the edge, and the result of the two beauty is obtained.
The current intelligent edge computing typically employs kubernets technology. The Kubernetes is a distributed cluster and is composed of management nodes (Master-nodes) and nodes (nodes). The Master-node mainly runs core components such as an application programming interface server (api server), a scheduler (scheduler), a controller (controller), a memory (etcd), and the node mainly runs components such as a kubel. And the Master-node and the node perform interaction in a command declaration mode to complete the management of the resources. The kubel operated by the node establishes a plurality of long connections with the Master-node, respectively monitors (watch) resource changes of services, nodes, pod and the like, and correspondingly processes the resource changes. In this mode, each node establishes multiple long connections with the Master-node, respectively, which is a resource consumption for the edge scene with limited resources.
In order to solve this problem, an embodiment of the present application provides an edge computing method, which is applied in an edge computing system as shown in fig. 2, where the edge computing system includes an edge controller, an edge manager, a k8s Master, a metadata store, and an edge node; the edge manager calls the k8s Master to create an edge node and stores the creation information of the edge node in the metadata store; the edge controller obtains the creation information of the edge node from the metadata storage; after acquiring the creation information, the edge controller uses the creation information to proxy that the edge node establishes a long connection with the k8s Master, and monitors resource metadata about the edge node in the k8s Master through the long connection; when the resource metadata of the edge node changes, the edge controller sends a notification message to the edge node, wherein the notification message is used for indicating the change data of the resource metadata; and finally, the edge node performs corresponding calculation processing according to the changed data. It is understood that the edge node includes edge metadata management, edge metadata storage and Kubelet, wherein the edge metadata management is used for synchronizing data related to the edge node from metadata storage of a cloud end through an edge controller, and synchronizing state data and event data of the edge node to metadata storage of the cloud end; the edge metadata store is used for storing data such as resource metadata, state data, event data, trigger rules and the like of the edge node; the Kubelet is used to read resource metadata and change data from the edge metadata store and manage and store resources, as well as resource states, to the edge metadata store.
Specifically, referring to fig. 3, an embodiment of an edge calculation method in the embodiment of the present application includes:
301. the edge manager calls k8s Master to create an edge node.
When a user calls an edge manager creation application, the edge manager directly calls an interface of the k8s Master to create the edge node and generates creation information, wherein the creation information is used for indicating that the edge node belongs to the k8s Master.
302. The k8s Master assigns resource metadata to the edge node.
After the edge manager creates the edge node, the k8s Master assigns resource metadata to the edge node. Wherein, the resource metadata may also be included in the creation information of the edge node.
303. The metadata store holds creation information attributed to the edge node.
After the edge manager completes the creation of the edge node, creation information attributed to the edge node is stored in the metadata store, where the creation information is used to indicate that the edge node belongs to the k8s Master, and may also include information such as resource metadata, state data, and event data of the edge node.
304. The edge controller retrieves the creation information from the metadata store.
The edge controller reads the creation information attributed to the edge node from the metadata store.
305. The edge controller establishes a long connection with the k8s Master according to the creation information and establishes a communication channel with the edge node.
The edge controller establishes a long connection with the k8s Master by acting on the edge node according to the creation information, and simultaneously establishes a communication channel between the edge controller and the edge node. Thus, the edge controller can be used as a middle receiving and forwarding point to realize information interaction between the edge node and the k8s Master.
It is understood that the long connection includes an Event (Event), a monitoring service (watch services), a monitoring node (watch nodes), a monitoring application (watch pod), and the like. The communication channel may be a cloud communication channel, or may also be other wired or wireless communication channels, which is not limited herein.
306. The edge controller monitors the resource metadata attributed to the edge node within the k8s Master using the long connection.
The edge controller monitors the resource metadata attributed to the edge node within the watch nodes using the established long connection.
307. When the resource metadata changes, the edge controller sends a notification message by using the communication channel, wherein the notification message is used for indicating the change data of the resource metadata.
When the resource metadata belonging to the edge node changes, the edge controller sends a notification message by using a communication channel between the edge controller and the edge node, wherein the notification message is used for indicating the change data of the resource metadata.
It is to be understood that the alteration data of the resource metadata may be sent when a change threshold is met, for example, when the change of the resource metadata exceeds a preset threshold, the edge controller sends the notification message to the edge node. And when the change of the resource metadata is less than a preset threshold value, the edge controller does not send the notification message to the edge node.
308. And the edge node performs corresponding calculation processing by using the change data.
The edge node performs corresponding calculation processing by using the change data.
It will be appreciated that the edge node may perform the computational processing itself when it does not receive the change data. When the edge node receives the changed data sent by the edge controller, the edge node performs corresponding calculation processing according to the changed data.
In practical applications, the edge node may also save the change data, so that the edge node may directly obtain the change data from the local. When the edge node is not connected to the k8s Master, corresponding calculation processing may be performed according to the changed data. Meanwhile, the edge controller can also send the resource metadata to the edge node, and the edge node also saves the resource metadata, so that the edge node directly obtains the resource metadata from the edge node locally. When the edge node is restarted off line, the operation can be recovered directly according to the resource metadata and the change data.
In this embodiment, in the edge computing system, an edge controller proxies the edge node to establish a long connection with the k8s Master, and then the edge controller monitors resource metadata corresponding to the edge node in the k8s Master through the long connection; when the resource metadata changes, the edge controller notifies the edge node of the change data of the resource metadata, so that the edge node performs corresponding calculation processing according to the variable data. Therefore, the edge node reduces a plurality of connections with the k8s Master, and only one connection is established between the edge node and the edge controller for signaling interaction, so that resources in an edge scene are saved.
Specifically referring to fig. 4, another embodiment of the edge calculation method in the embodiment of the present application includes:
401. the edge manager calls k8s Master to create an edge node.
When a user calls an edge manager creation application, the edge manager directly calls an interface of the k8s Master to create the edge node and generates creation information, wherein the creation information is used for indicating that the edge node belongs to the k8s Master.
402. The k8s Master assigns resource metadata to the edge node.
After the edge manager creates the edge node, the k8s Master creates resource metadata for the edge node. Wherein, the resource metadata may also be included in the creation information of the edge node.
403. The metadata store maintains creation information attributed to the edge node, the creation information including resource metadata for the edge node.
After the edge manager completes the creation of the edge node, creation information attributed to the edge node is stored in the metadata store, where the creation information is used to indicate that the edge node belongs to the k8s Master, and may also include information such as resource metadata, state data, and event data of the edge node.
404. The edge node retrieves the creation information from the metadata store.
The edge node reads the creation information of the edge node from the metadata store.
Optionally, the edge node includes edge metadata management, edge metadata storage, and Kubelet. The specific process by which the edge node obtains the creation information from the metadata store may be as follows: the edge metadata management synchronizes the creation information of the edge node from the metadata store and synchronizes the state data and event data of the edge node to the metadata store.
It can be understood that, when the edge node monitors that the resource metadata attributed to the edge node in the k8s Master changes, the edge node acquires change data of the resource metadata and performs corresponding calculation processing by using the change data.
405. The edge node saves the creation information.
The edge node saves the creation information.
Optionally, after the edge metadata management synchronizes the creation information of the edge node from the metadata store, the edge metadata management synchronizes the creation information to the edge metadata store; the edge metadata store then saves the creation information.
Optionally, the edge node may also store the change data. The storage method is the same as the creation information, and is not described herein again.
406. When the edge node is restarted off line, the edge node resumes operation according to the creation information and performs corresponding calculation processing.
Because the edge node stores the resource metadata, when the edge node is restarted offline, the edge node can locally acquire the resource metadata, thereby recovering the operation and performing corresponding calculation processing.
Optionally, if the edge node further stores the changed data of the resource metadata in the running process, the edge node may further obtain the changed data in the running recovery process, and finally, the running recovery is performed according to the resource metadata and the changed data.
In this embodiment, the edge node stores the resource metadata allocated by the k8s Master to the edge node, so that the edge node can directly acquire the resource metadata to resume running during the offline restart of the edge node. Therefore, the edge node does not need to acquire resource metadata by establishing connection with the k8s Master, and the self-running of the edge node is further realized.
It is understood that, in the embodiment of the present application, the scheme shown in fig. 3 may be implemented independently from the scheme shown in fig. 4, or may be implemented in combination with the scheme shown in fig. 4, and the specific case is described by using the system shown in fig. 2:
when a user calls an edge manager creating application, the edge manager directly calls the interface of the k8s Master to create the edge node; after the edge manager creates the edge node, the k8s Master creates resource metadata for the edge node. The creation information is used for indicating that the edge node belongs to the k8s Master, and meanwhile, the creation information can also comprise the resource metadata; after the edge manager completes creation of the edge node, creation information of the edge node is stored in the metadata store, wherein the creation information may further include information such as resource metadata, state data, and event data of the edge node. The edge controller reads the creation information of the edge node from the metadata store. The edge controller establishes a long connection with the k8s Master by acting on the edge node according to the creation information, and simultaneously establishes a communication channel between the edge controller and the edge node. Thus, the edge controller can be used as a middle receiving and forwarding point to realize information interaction between the edge node and the k8s Master; the edge controller sends the creation information to the edge node through a communication channel. It is understood that the long connection includes an Event (Event), a monitoring service (watch services), a monitoring node (watch nodes), a monitoring application (watch pod), and the like. The communication channel may be a communication channel, or may also be other wired or wireless communication channels, and is not limited herein. The edge controller monitors the resource metadata attributed to the edge node within the watch nodes using the established long connection. When the resource metadata belonging to the edge node changes, the edge controller sends a notification message by using a communication channel between the edge controller and the edge node, wherein the notification message is used for indicating the change data of the resource metadata. It is to be understood that the alteration data of the resource metadata may be sent when a change threshold is met, for example, when the change of the resource metadata exceeds a preset threshold, the edge controller sends the notification message to the edge node. And when the change of the resource metadata is less than a preset threshold value, the edge controller does not send the notification message to the edge node. The edge node performs corresponding calculation processing by using the change data. It will be appreciated that the edge node may perform the computational processing itself when it does not receive the change data. When the edge node receives the changed data sent by the edge controller, the edge node performs corresponding calculation processing according to the changed data. Meanwhile, the edge node stores the creation information and change data attributed to the edge node, wherein the creation information may further include resource metadata. Optionally, the edge node includes edge metadata management, edge metadata storage, and Kubelet. Wherein the edge metadata management synchronizes creation information attributed to the edge node from the metadata store and synchronizes state data and event data of the edge node to the metadata store. After the edge metadata management synchronizes the creation information of the edge node from the metadata store, the edge metadata management synchronizes the creation information to the edge metadata store; the edge metadata store then saves the creation information. Optionally, the edge node may also store the change data. The storage method is the same as the creation information, and is not described herein again. Because the edge node stores the resource metadata attributed to the edge node, when the edge node is restarted offline, the edge node can locally acquire the resource metadata, thereby recovering the operation and performing corresponding calculation processing.
In the technical solution provided in this embodiment, an edge controller in the edge computing system establishes a long connection with the k8s Master in proxy of the edge node, and then the edge controller monitors resource metadata corresponding to the edge node in the k8s Master through the long connection; when the resource metadata changes, the edge controller notifies the edge node of the change data of the resource metadata, so that the edge node performs corresponding calculation processing according to the variable data. Therefore, the edge node reduces a plurality of connections with the k8s Master, and only one connection is established between the edge node and the edge controller for signaling interaction, so that resources in an edge scene are saved. And the edge node stores the resource metadata distributed by the k8s Master to the edge node, so that the edge node can directly acquire the resource metadata to restore the operation in the offline restart process of the edge node. Therefore, the edge node does not need to acquire resource metadata by establishing connection with the k8s Master, and the self-running of the edge node is further realized.
Referring to fig. 5, an embodiment of an edge computing system in an embodiment of the present application is described below, where:
the edge manager 501 is configured to invoke the k8s Master to create an edge node 505, and store creation information of the edge node 505 in the metadata store 504;
the edge controller 502 is configured to obtain creation information of the edge node 505 from the metadata storage 504, where the creation information is used to indicate that the edge node belongs to the k8s Master; establishing long connection with the k8s Master503 according to the creation information; monitoring resource metadata attributed to the edge node 505 in the k8s Master503 according to the long connection; when the resource metadata changes, sending a notification message to the edge node 505, where the notification message is used to indicate changed data of the resource metadata; the edge node 505 is configured to perform corresponding calculation processing according to the changed data.
Optionally, the edge node 505 is further configured to store the change data.
Optionally, referring specifically to fig. 6, the edge node 505 includes an edge metadata management 5051, an edge metadata store 5052, and a Kubelet 5053;
the edge metadata management 5051 is configured to receive the changed data sent by the edge controller 502;
the edge metadata management 5051, which synchronizes the change data to the edge metadata storage 5052;
the edge metadata store 5052 is used to store the changed data.
Optionally, the edge metadata management 5051 is further configured to receive resource metadata sent by the edge controller 502, where the resource metadata is distributed to the edge node 505 by the k8s Master 503;
the edge metadata management 5051, which is also used to synchronize the resource metadata to the edge metadata storage 5052;
the edge metadata store 5052 is also used to store the resource metadata.
Optionally, when the edge node 505 restarts offline, the Kubelet5053 is configured to obtain the resource metadata and the change data;
the edge node 505 is configured to resume operation using the resource metadata and the change data.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or 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 units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above 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; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (9)
1. An edge computing method applied to an edge computing system, wherein the edge computing system comprises an edge controller, an edge manager, a management node and a metadata storage, and the method is characterized by comprising the following steps:
the edge manager calls the management node to create an edge node, and stores creation information of the edge node in the metadata storage, wherein the creation information is used for indicating that the edge node belongs to the management node;
the edge controller acquires the creation information of the edge node from the metadata storage;
the edge controller establishes long connection with the management node according to the creation information;
the edge controller monitors resource metadata attributed to the edge node in the management node according to the long connection;
when the resource metadata changes, the edge controller sends a notification message to the edge node, wherein the notification message is used for indicating the change data of the resource metadata;
when the edge node is restarted offline, the Kubelet contained in the edge node acquires the resource metadata and the change data;
and the edge node recovers operation by using the resource metadata and the change data.
2. The method of claim 1, further comprising:
the edge node stores the change data.
3. The method of claim 2, wherein the edge nodes comprise edge metadata management, edge metadata storage, and Kubelet;
the edge node storing the change data includes:
the edge metadata management receives the change data sent by the edge controller;
the edge metadata management synchronizing the change data to the edge metadata store;
the edge metadata store maintains the change data.
4. The method of claim 3, further comprising:
the edge metadata management receives resource metadata sent by the edge controller, and the resource metadata is distributed to the edge nodes by the management nodes;
the edge metadata management synchronizing the resource metadata to the edge metadata store;
the edge metadata store stores the resource metadata.
5. An edge computing system comprising an edge controller, an edge manager, a management node, a metadata store, and an edge node;
the edge manager is used for calling the management node to create an edge node and storing creation information of the edge node in the metadata storage, wherein the creation information is used for indicating that the edge node belongs to the management node;
the edge controller is used for acquiring the creation information of the edge node from the metadata storage; establishing long connection with the management node according to the creation information; monitoring resource metadata attributed to the edge node in the management node according to the long connection; when the resource metadata changes, sending a notification message to the edge node, wherein the notification message is used for indicating the changed data of the resource metadata;
when the edge node is restarted offline, the Kubelet contained in the edge node acquires the resource metadata and the change data;
and the edge node recovers operation by using the resource metadata and the change data.
6. The edge computing system of claim 5 wherein the edge node is further configured to store the change data.
7. The edge computing system of claim 6, wherein the edge nodes include edge metadata management, edge metadata storage, and Kubelet;
the edge metadata management is used for receiving the change data sent by the edge controller;
the edge metadata management to synchronize the change data to the edge metadata store;
the edge metadata store is used for storing the change data.
8. The edge computing system of claim 7, wherein the edge metadata manager is further configured to receive resource metadata sent by the edge controller, the resource metadata being assigned to the edge node by the management node;
the edge metadata management further to synchronize the resource metadata to the edge metadata store;
the edge metadata store is further configured to store the resource metadata.
9. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910133148.5A CN111614702B (en) | 2019-02-22 | 2019-02-22 | Edge calculation method and edge calculation system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910133148.5A CN111614702B (en) | 2019-02-22 | 2019-02-22 | Edge calculation method and edge calculation system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111614702A CN111614702A (en) | 2020-09-01 |
| CN111614702B true CN111614702B (en) | 2022-03-25 |
Family
ID=72201901
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910133148.5A Active CN111614702B (en) | 2019-02-22 | 2019-02-22 | Edge calculation method and edge calculation system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111614702B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114884880B (en) * | 2022-04-06 | 2024-03-08 | 阿里巴巴（中国）有限公司 | Data transmission method and system |
| CN115225450A (en) * | 2022-09-20 | 2022-10-21 | 南京艾泰克物联网科技有限公司 | Multi-data machine room virtualization cluster management system based on edge computing |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102365634A (en) * | 2009-01-30 | 2012-02-29 | 伊斯曼柯达公司 | System for managing distributed assets and metadata |
| CN108737215A (en) * | 2018-05-29 | 2018-11-02 | 郑州云海信息技术有限公司 | A kind of method and apparatus of cloud data center Kubernetes clusters container health examination |
| CN108810013A (en) * | 2018-07-02 | 2018-11-13 | 山东汇贸电子口岸有限公司 | A kind of service access method based on container |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9946719B2 (en) * | 2015-07-27 | 2018-04-17 | Sas Institute Inc. | Distributed data set encryption and decryption |
-
2019
- 2019-02-22 CN CN201910133148.5A patent/CN111614702B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102365634A (en) * | 2009-01-30 | 2012-02-29 | 伊斯曼柯达公司 | System for managing distributed assets and metadata |
| CN108737215A (en) * | 2018-05-29 | 2018-11-02 | 郑州云海信息技术有限公司 | A kind of method and apparatus of cloud data center Kubernetes clusters container health examination |
| CN108810013A (en) * | 2018-07-02 | 2018-11-13 | 山东汇贸电子口岸有限公司 | A kind of service access method based on container |
Non-Patent Citations (4)
| Title |
|---|
| Edge computing in IoT context: Horizontal and vertical Linux container migration;Corentin Dupont等;《2017 Global Internet of Things Summit (GIoTS)》;20170609;全文 * |
| What is KubeEdge;KubeEdge;《KubeEdge https://kubeedge.io/ko/docs/kubeedge/ 》;20190128;正文第2页，图1 * |
| 推文：kubeEdge;kubeEdge;《推文：https://twitter.com/kubeedge/status/1091168556723490816》;20190201;全文 * |
| 边缘计算:现状与展望;施巍松等;《计算机研究与发展》;20181221;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111614702A (en) | 2020-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106331098B (en) | Server cluster system | |
| EP3125117B1 (en) | Update management system and update management method | |
| CN100426751C (en) | Method for ensuring accordant configuration information in cluster system | |
| CN106155811B (en) | Resource service device, resource scheduling method and device | |
| CN106656589B (en) | A kind of server dual-machine hot backup system | |
| CN110515748B (en) | Message processing method and related device | |
| CN104461752A (en) | Two-level fault-tolerant multimedia distributed task processing method | |
| CN106612312A (en) | Virtualized data center scheduling system and method | |
| CN103647830A (en) | Dynamic management method for multilevel configuration files in cluster management system | |
| CN103036719A (en) | Cross-regional service disaster method and device based on main cluster servers | |
| CN110581782A (en) | Disaster tolerance data processing method, device and system | |
| CN103530193A (en) | Method and device used for adjusting application process | |
| CN111614702B (en) | Edge calculation method and edge calculation system | |
| CN109324942B (en) | Double-activity processing method, device, system, equipment and storage medium for microservice | |
| CN102957623A (en) | Maintenance method and equipment of neighborhood of border gate protocol | |
| CN104468633A (en) | SDN southing security proxy product | |
| CN107682411A (en) | A kind of extensive SDN controllers cluster and network system | |
| CN105589756A (en) | Batch processing cluster system and method | |
| CN113778615B (en) | Rapid and stable network shooting range virtual machine construction system | |
| CN112087506B (en) | Cluster node management method and device and computer storage medium | |
| CN111078463A (en) | Data backup method, device and system | |
| CN116095145B (en) | Data control method and system of VPC cluster | |
| CN116257380A (en) | High availability method and system for Kubernetes federal management control plane across data centers | |
| CN113553194B (en) | Hardware resource management method, device and storage medium | |
| CN111008095A (en) | State snapshot generation and recovery method facing edge cloud |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220225 Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province Applicant after: Huawei Cloud Computing Technology Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Applicant before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |