CN112506659A

CN112506659A - Management method of edge device and related device

Info

Publication number: CN112506659A
Application number: CN202011434823.7A
Authority: CN
Inventors: 胡伟煌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-12-10
Filing date: 2020-12-10
Publication date: 2021-03-16
Anticipated expiration: 2040-12-10
Also published as: CN112506659B

Abstract

The application discloses a management method and a related device of edge equipment, which are applied to the technical field of cloud. Determining a meta-cluster deployed on a cloud platform in response to a target instruction, wherein the meta-cluster comprises a central control device and at least one associated managed cluster, the central control device is used for issuing the target instruction to the managed cluster, and at least one control component is configured in the managed cluster; then obtaining the edge equipment to be deployed; and associating the edge device with the control component to deploy the edge service corresponding to the target instruction at the edge device. Therefore, the process of rapidly expanding and managing the edge device is realized, the edge device is managed through the control component in the hosting cluster, the upper-layer meta-cluster framework does not need to be re-deployed in the cluster expanding process, and the expanding efficiency of the edge device is improved.

Description

Management method of edge device and related device

Technical Field

The present application relates to the field of computer technologies, and in particular, to a management method for edge devices and a related apparatus.

Background

The edge computing refers to an open platform which is close to one side of an object or a data source and integrates network, computing, storage and application core capabilities. The network edge side can be any functional entity from a data source to the cloud computing center, and the entities carry an edge computing platform with the core capabilities of network fusion, computing, storage and application, so that real-time, dynamic and intelligent service computing is provided for end users.

Generally, edge computing is managed in a cluster manner, a single cluster can only manage equipment of a certain size due to performance limitation, and if the number of the equipment exceeds the upper limit of the size, one or more clusters need to be created to meet the larger size of the edge equipment.

However, creating a cluster requires preparing a machine of a cluster control surface and then deploying the cluster, that is, deploying from the perspective of the overall architecture of the cluster, which is tedious in deployment process and high in cost, and affects the expansion efficiency of the edge device.

Disclosure of Invention

In view of this, the present application provides a method for managing an edge device, which can effectively improve the expansion efficiency of the edge device.

A first aspect of the present application provides a method for managing an edge device, which can be applied to a system or a program that includes a management function of the edge device in a terminal device, and specifically includes:

determining a meta-cluster deployed on a cloud platform in response to a target instruction, wherein the meta-cluster comprises a central control device and at least one associated managed cluster, the central control device is used for issuing the target instruction to the managed cluster, and at least one control component is configured in the managed cluster;

acquiring edge equipment to be deployed;

associating the edge device with the control component according to a deployment rule so that the edge device accesses to the corresponding hosted cluster, wherein the hosted cluster is used for deploying the edge service corresponding to the target instruction at the edge device, and the deployment rule is determined based on the position information or the business information corresponding to the edge service.

Optionally, in some possible implementations of the present application, the determining a meta-cluster deployed in the cloud platform in response to the target instruction includes:

setting an area label for a node unit in an initial cluster in response to the target instruction;

calling a target service within the range of the area label to determine a target interface in the node unit;

creating the control component in the node unit based on the target interface to determine as the hosted cluster;

determining the central control device associated with the hosted cluster to determine the meta-cluster.

Optionally, in some possible implementations of the present application, the creating the control component in the node unit based on the target interface to determine as the hosted cluster includes:

creating the control component in the node unit based on the target interface, and calling up a detection process;

and if the detection process indicates that the control component normally serves on the node unit, determining that the control component is the hosting cluster.

Optionally, in some possible implementation manners of the present application, the acquiring the edge device to be deployed includes:

determining a plurality of candidate edge devices;

calling a node registration interface of a cloud platform to acquire registration parameters of the candidate edge devices;

determining the edge device to be deployed based on the registration parameters.

Optionally, in some possible implementation manners of the present application, the determining the edge device to be deployed based on the registration parameter includes:

the registration parameters determine location information of the candidate edge devices;

determining the corresponding hosted cluster based on the location information;

and performing node registration in the managed cluster to determine the edge device to be deployed.

Optionally, in some possible implementation manners of the present application, the registering nodes in the hosted cluster to determine that the edge device is to be deployed includes:

acquiring load information of the hosting cluster;

and if the load information meets a preset condition, performing node registration in the hosting cluster to determine the edge device to be deployed.

Optionally, in some possible implementations of the present application, the method further includes:

if the load information does not meet the preset condition, creating a candidate hosting cluster based on the edge device to be deployed.

Optionally, in some possible implementations of the present application, the associating the edge device with the control component according to a deployment rule includes:

associating the edge equipment with the control component according to a deployment rule, and uploading a mirror image service corresponding to the edge service to a mirror image warehouse;

deploying the mirroring service in the mirroring repository;

and deploying the edge service corresponding to the target instruction at the edge equipment based on the mirror image service.

Optionally, in some possible implementations of the present application, the deploying the mirroring service in the mirroring repository includes:

determining deployment parameters corresponding to the mirror image service;

and determining a deployment space according to the deployment parameters so as to deploy in the mirror image warehouse.

initiating a deployment test instruction;

testing the edge service in the edge device based on the deployment test instruction to obtain a test result;

and if the test result meets the test condition, finishing the deployment of the edge service in the edge equipment.

Optionally, in some possible implementations of the present application, the meta-cluster and the hosted cluster are managed through kubernets, and the target instruction is used to expand the number of the edge devices managed by the cloud platform.

Optionally, in some possible implementation manners of the present application, the management method of the edge device is applied to a block chain device, where the block chain device is a node in a block chain.

A second aspect of the present application provides an apparatus for managing an edge device, including:

the cloud platform comprises a determining unit, a processing unit and a processing unit, wherein the determining unit is used for responding to a target instruction to determine a meta-cluster deployed on a cloud platform, the meta-cluster comprises a central control device and at least one associated managed cluster, the central control device is used for issuing the target instruction to the managed cluster, and at least one control component is configured in the managed cluster;

the device comprises an acquisition unit, a deployment unit and a deployment unit, wherein the acquisition unit is used for acquiring edge equipment to be deployed;

the management unit is used for associating the edge device with the control component according to a deployment rule so that the edge device accesses to the corresponding hosted cluster, the hosted cluster is used for deploying the edge service corresponding to the target instruction at the edge device, and the deployment rule is determined based on the position information or the business information corresponding to the edge service.

Optionally, in some possible implementations of the present application, the determining unit is specifically configured to set an area label for a node unit in an initial cluster in response to the target instruction;

the determining unit is specifically configured to invoke a target service within the range of the area tag to determine a target interface in the node unit;

the determining unit is specifically configured to create the control component in the node unit based on the target interface to determine that the control component is the hosted cluster;

the determining unit is specifically configured to determine the central control device associated with the hosted cluster to determine the meta-cluster.

Optionally, in some possible implementations of the present application, the determining unit is specifically configured to create the control component in the node unit based on the target interface, and invoke a detection process;

the determining unit is specifically configured to determine that the control component is the hosted cluster if the detecting process indicates that the control component is normally served on the node unit.

Optionally, in some possible implementation manners of the present application, the obtaining unit is specifically configured to determine a plurality of candidate edge devices;

the acquisition unit is specifically configured to call a node registration interface of a cloud platform to acquire registration parameters of the candidate edge device;

the obtaining unit is specifically configured to determine the edge device to be deployed based on the registration parameter.

Optionally, in some possible implementation manners of the present application, the obtaining unit is specifically configured to determine, by the registration parameter, location information of the candidate edge device;

the acquiring unit is specifically configured to determine the corresponding hosting cluster based on the location information;

the obtaining unit is specifically configured to perform node registration in the hosted cluster to determine the edge device to be deployed.

Optionally, in some possible implementation manners of the present application, the obtaining unit is specifically configured to obtain load information of the managed cluster;

the obtaining unit is specifically configured to perform node registration in the hosting cluster if the load information meets a preset condition, so as to determine the edge device to be deployed.

Optionally, in some possible implementation manners of the present application, the obtaining unit is specifically configured to create a candidate hosting cluster based on the edge device to be deployed if the load information does not satisfy the preset condition.

Optionally, in some possible implementation manners of the present application, the management unit is specifically configured to associate the edge device with the control component according to a deployment rule, and upload a mirror service corresponding to the edge service to a mirror warehouse;

the management unit is specifically configured to deploy the mirroring service in the mirroring warehouse;

the management unit is specifically configured to deploy, at the edge device, an edge service corresponding to the target instruction based on the mirroring service.

Optionally, in some possible implementation manners of the present application, the management unit is specifically configured to determine a deployment parameter corresponding to the mirroring service;

the management unit is specifically configured to determine a deployment space according to the deployment parameter, so as to perform deployment in the mirror image warehouse.

Optionally, in some possible implementation manners of the present application, the management unit is specifically configured to initiate a deployment test instruction;

the management unit is specifically configured to test the edge service in the edge device based on the deployment test instruction to obtain a test result;

the management unit is specifically configured to complete deployment of the edge service in the edge device if a test result meets a test condition.

A third aspect of the present application provides a computer device comprising: a memory, a processor, and a bus system; the memory is used for storing program codes; the processor is configured to execute the method for managing an edge device according to any one of the first aspect and the first aspect according to instructions in the program code.

A fourth aspect of the present application provides a computer-readable storage medium having stored therein instructions, which, when executed on a computer, cause the computer to execute the method for managing an edge device according to any one of the first aspect or the first aspect.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method for managing an edge device provided in the first aspect or the various alternative implementations of the first aspect.

According to the technical scheme, the embodiment of the application has the following advantages:

determining a meta-cluster deployed on a cloud platform in response to a target instruction, wherein the meta-cluster comprises a central control device and at least one associated managed cluster, the central control device is used for issuing the target instruction to the managed cluster, and at least one control component is configured in the managed cluster; then obtaining the edge equipment to be deployed; and associating the edge device with the control component to deploy the edge service corresponding to the target instruction at the edge device. Therefore, the process of rapidly expanding and managing the edge device is realized, the edge device is managed through the control component in the hosting cluster, the upper-layer meta-cluster framework does not need to be re-deployed in the cluster expanding process, and the expanding efficiency of the edge device is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a system architecture diagram illustrating operation of a management system of an edge device according to an embodiment of the present disclosure;

fig. 2 is a flowchart of a management method of an edge device according to an embodiment of the present disclosure;

fig. 3 is a flowchart of another management method for an edge device according to an embodiment of the present application;

fig. 4 is a flowchart of another management method for an edge device according to an embodiment of the present application;

fig. 5 is a flowchart of another management method for an edge device according to an embodiment of the present application;

fig. 6 is a system architecture diagram illustrating operation of another management system of an edge device according to an embodiment of the present application;

fig. 7 is a flowchart of another management method for an edge device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a management apparatus of an edge device according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 10A is a data sharing system according to an embodiment of the present application;

fig. 10B is a block chain composition according to an embodiment of the present disclosure;

fig. 10C is a schematic diagram of input information of a block link point according to an embodiment of the present disclosure.

Detailed Description

The embodiment of the application provides a management method and a related device of edge equipment, which can be applied to a system or a program containing a management function of the edge equipment in terminal equipment, wherein a meta-cluster deployed on a cloud platform is determined by responding to a target instruction, the meta-cluster comprises a central control device and at least one associated hosting cluster, the central control device is used for issuing the target instruction to the hosting cluster, and at least one control component is configured in the hosting cluster; then obtaining the edge equipment to be deployed; and associating the edge device with the control component to deploy the edge service corresponding to the target instruction at the edge device. Therefore, the process of rapidly expanding and managing the edge device is realized, the edge device is managed through the control component in the hosting cluster, the upper-layer meta-cluster framework does not need to be re-deployed in the cluster expanding process, and the expanding efficiency of the edge device is improved.

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 is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "corresponding" 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.

First, some nouns that may appear in the embodiments of the present application are explained.

kubernets: also called k8s, is a distributed cluster management system, and an execution program (worker) is run on each node (node) to manage the life cycle of the container, and the execution program is kubel.

kubelet: the main function is to periodically obtain the expected state of the microservice process on the node (what container is run, the number of copies run, how the network or storage is configured, etc.) from a certain place, and call the corresponding container platform interface to achieve the state.

Pod: the minimum/simplest basic unit for creation or deployment of kubernets, one Pod represents one micro service process running on a cluster, and one micro service process encapsulates one edge container (or multiple edge containers) providing micro service applications, storage resources, an independent network IP and policy options for managing and controlling the operation mode of the container.

kube-proxy: an interface proxy for managing Service object (Service) access portals, the proxy object comprising intra-cluster microservice process-to-Service object access and extra-cluster access Service objects.

In order to solve the above problem, the present application provides a management method for an edge device, where the method is applied to a system framework for managing the edge device shown in fig. 1, and as shown in fig. 1, the system framework for managing the edge device provided in the embodiment of the present application is specifically divided into a partition management process of a control surface component (central control device master) in a cloud to a cluster and an access deployment process of the edge device at an edge end. The present application mainly uses container technology docker and container arrangement tool technology kubernets (hereinafter referred to as k8 s). The cloud end is mainly used for deploying master related components of kubernets, and control surface components of the cloud end are divided into meta clusters and hosting clusters.

Specifically, the meta-cluster is a complete independent k8s cluster, including k8s master nodes and k8s node nodes. The node of k8s can be added with horizontal fast expansion. The node runs a master component hosting a k8s cluster, wherein the node can be a physical host or a virtual machine.

The managed cluster is a node used by the managed k8s cluster to register and manage the edge device, and the managed k8s cluster mainly deploys components of the master part, including components of kube-apiserver, kube-controller-manager, kube-scheduler, etcd, and the like. The master hosting the cluster runs on the node nodes of the meta-cluster in containers (pod).

The command is issued through the central control device of the cloud, so that managed k8s service clusters (namely a way of managing on kube) are created and managed through a k8s meta-cluster, the number of managed k8s service clusters can be increased rapidly to increase cloud control nodes, edge devices are registered in the managed service cluster control nodes, and management of the edge devices by the cloud is achieved.

It can be understood that one hosting cluster control node can manage certain scale of edge devices, and when the hosting cluster control node is added, larger scale of edge devices can be managed quickly.

In this embodiment, the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, a big data and artificial intelligence platform, and the like. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The terminal and the server may be directly or indirectly connected through a wired or wireless communication manner, and the terminal and the server may be connected to form a block chain network, which is not limited herein.

It can be understood that the method provided by the present application may be a program written as a processing logic in a hardware system, or may be a management apparatus of an edge device, and the processing logic is implemented in an integrated or external manner. As an implementation manner, the management apparatus of the edge device determines a meta-cluster deployed on the cloud platform in response to a target instruction, where the meta-cluster includes a central control device and at least one associated hosting cluster, the central control device is configured to issue the target instruction to the hosting cluster, and at least one control component is configured in the hosting cluster; then obtaining the edge equipment to be deployed; and associating the edge device with the control component to deploy the edge service corresponding to the target instruction at the edge device. Therefore, the process of rapidly expanding and managing the edge device is realized, the edge device is managed through the control component in the hosting cluster, the upper-layer meta-cluster framework does not need to be re-deployed in the cluster expanding process, and the expanding efficiency of the edge device is improved.

The scheme provided by the embodiment of the application relates to a cloud technology, and is specifically explained by the following embodiment:

with reference to the above flow architecture, a management method for an edge device in the present application will be introduced below, please refer to fig. 2, where fig. 2 is a flow chart of a management method for an edge device provided in an embodiment of the present application, where the management method may be executed by a cloud device or a server, and the embodiment of the present application at least includes the following steps:

201. a meta-cluster deployed at the cloud platform is determined in response to the target instruction.

In this embodiment, the meta-cluster includes a central control device (control plane component) and at least one associated managed cluster, where the central control device is configured to issue a target instruction to the managed cluster, and the managed cluster is configured with at least one control component.

It can be understood that the application is described with one meta-cluster deployed in the cloud platform, and in an actual scenario, the cloud platform may include a plurality of meta-clusters connected in parallel.

Specifically, the target instruction may be an instruction for adding an edge device in the meta-cluster, an instruction for deleting an edge device, or a specific service instruction, which is not limited herein.

Compared with the mode of managing the edge device in the cloud cluster dimension in the prior art, the method is equivalent to dividing the cloud cluster, and adjusting the single-layer control of the control device on the node to include the hierarchical structure of the meta-cluster (control device control) and the hosting cluster (node control), so that the management of the edge device is facilitated, for example, in a k8s scenario, that is, adjusting the single-layer control of the k8s master on the node to the hierarchical structure of the meta-cluster and the hosting cluster (a master component is configured in the node).

In particular, the process of determining meta-clusters and their associated hosting clusters may be created. Firstly, responding to a target instruction to set an area label for a node unit in an initial cluster; then, calling a target service in the range of the area label to determine a target interface in the node unit, wherein the target service is an etcd service; then, a control component is created in the node unit based on the target interface so as to be determined as a hosting cluster; and further determining a central control device associated with the hosting cluster to determine a meta-cluster.

Wherein the etcd is a distributed system with distributed and reliable key-value storage. It is not only used for storage, but also provides shared configuration and service discovery. Service Discovery (Service Discovery) may find each other and establish connections among processes or services in the same distributed cluster.

Specifically, etcd uses a raft protocol to maintain the consistency of the states of the nodes in the cluster. The etcd service is a distributed system, a plurality of nodes communicate with each other to form an integral external service, each node stores complete data, and the data maintained by each node is ensured to be consistent through a raft protocol, namely, the data of the nodes corresponding to the hosting cluster is ensured to be consistent. In addition, each node in the etcd service maintains a state machine, and at most one active master node exists at any time. The master node processes all write operations from the client, and the changes of the write operations to the state machine are reliably synchronized to other nodes through a Raft protocol, so that the consistency of node data corresponding to the hosting cluster is ensured.

Optionally, in the process of creating a hosting cluster by a node based on a meta-cluster, a rechecking process may also be performed, that is, a control component is created in a node unit based on a target interface, and a detection process is invoked; and if the detection process indicates that the control component is normally served on the node unit, determining the node unit as a managed cluster. Thereby ensuring the credibility of the hosting cluster.

202. And acquiring the edge equipment to be deployed.

In this embodiment, the edge device to be deployed may be selected from a plurality of candidate edge devices, that is, only candidate edge devices that are successfully registered in the cloud platform may be deployed. Specifically, a plurality of candidate edge devices are determined first; then calling a node registration interface of the cloud platform to acquire registration parameters of the candidate edge devices; and then determining the edge device to be deployed based on the registration parameters. The registration parameters may include parameters of the edge device in terms of device performance, such as load state and service duration, or may include geographic parameters of the device distribution location and connection state.

Optionally, to facilitate the management of the edge devices by the hosting cluster, the edge devices may be selected to be closely located; firstly, determining the position information of candidate edge equipment according to registration parameters; then determining a corresponding hosting cluster based on the position information; and performing node registration in the managed cluster to determine the edge device to be deployed. By screening the position information, the timeliness of the managed cluster for managing the edge equipment is improved.

Optionally, since the meta-cluster associates multiple managed clusters, the load of the managed clusters, that is, the number of managed edge devices, may be considered when allocating the managed clusters to the edge devices. Specifically, firstly, load information of a hosting cluster is obtained; and if the load information meets the preset condition, performing node registration in the hosting cluster to determine the edge equipment to be deployed. For example, the preset condition is that the load rate is less than 60% or not fully loaded, and the specific value setting is determined by the actual scene.

Optionally, when the load information does not satisfy the preset condition, a candidate hosting cluster may be created based on the edge device to be deployed, where the candidate hosting cluster may be another hosting cluster associated with the meta cluster, or a hosting cluster is newly created in the meta cluster, so as to improve accuracy of edge device management.

203. The edge devices are associated with the control components according to deployment rules such that the edge devices access the corresponding hosted clusters.

In this embodiment, through the configuration of the meta-cluster and the hosting cluster, the edge device is associated with the corresponding hosting cluster, that is, the hosting cluster is used to deploy the edge service corresponding to the target instruction at the edge device, so that the edge service information in the meta-cluster can be obtained, the horizontal expansion of the cloud platform cluster scale is realized, which is also called horizontal expansion, and a larger number of requests are supported by more nodes; in addition, the deployment rule is a rule used for ensuring that the edge device can be fully utilized after accessing the hosting cluster, and specifically, the deployment rule may be determined based on the location information or the service information corresponding to the edge service; for example, if the edge service corresponds to the service a, determining edge devices adapted to the service a, and if the service a requires at least 4K of camera devices (the service information requirement) in the hosted cluster 1 (different hosted clusters can be set differently), screening resolution in the process of determining the edge devices; or the edge service corresponds to the service of the area B, associating the hosting cluster corresponding to the area B with the edge device of which the position information is close to the area B, thereby improving the response efficiency of the edge and the cloud; it is to be understood that the setting of the deployment rule may be a combination of one or more of the above examples, and may also be performed, without departing from the above examples, by using manual access of relevant personnel, that is, the deployment rule corresponds to manual access, or by using automatic access, that is, the deployment rule corresponds to free access, where the specific manner is determined by an actual scenario and is not limited herein.

Specifically, for the configuration process in which the edge service is issued to the edge device, the mirror image service corresponding to the edge service may be uploaded to a mirror image warehouse, where the mirror image warehouse is used to store Docker mirror images, the Docker mirror images are used to deploy container services, and each mirror image has a specific unique identifier, for example, the identifier is registration address + mirror image name + mirror image Tag of the mirror image; then deploying mirror image service in a mirror image warehouse; and then deploying the edge service corresponding to the target instruction on the edge device based on the mirror image service, thereby ensuring the traceability of the edge service and improving the stability of the edge service configuration.

In addition, in the process of mirror image service configuration, the deployment parameters corresponding to the mirror image service can be determined; and then determining a deployment space according to the deployment parameters so as to deploy in the mirror image warehouse. For example, the mirror services are classified to facilitate statistics of service conditions.

Optionally, after the edge service is deployed, a deployment test instruction may be initiated; then testing the edge service in the edge equipment based on the deployment test instruction to obtain a test result; and if the test result meets the test condition, completing the deployment of the edge service in the edge equipment, thereby ensuring the stability and reliability of the deployment of the edge service.

The cluster can be conveniently and rapidly deployed and expanded, and the number of the management edge devices is increased. Assuming 6 central devices with 48 cores and 64G resources, a maximum of 6000 edge devices can be managed in the case of the prior art solution. And with the present application, the 6 devices can manage 12 thousand edge devices. Under the condition of the same central control equipment resource, the equipment scale managed by the method is 20 times that of the prior art. Compared with the prior art, the cluster expansion efficiency of the application technology is high in expansibility, the cluster expansion efficiency is calculated according to the second level, and the cluster expansion efficiency of the prior art is calculated according to the hour or day.

With reference to the foregoing embodiments, a meta-cluster deployed in a cloud platform is determined in response to a target instruction, where the meta-cluster includes a central control device and at least one associated managed cluster, the central control device is configured to issue the target instruction to the managed cluster, and at least one control component is configured in the managed cluster; then obtaining the edge equipment to be deployed; and associating the edge device with the control component to deploy the edge service corresponding to the target instruction at the edge device. Therefore, the process of rapidly expanding and managing the edge device is realized, the edge device is managed through the control component in the hosting cluster, the upper-layer meta-cluster framework does not need to be re-deployed in the cluster expanding process, and the expanding efficiency of the edge device is improved.

The foregoing embodiment describes a deployment process of an edge node on a cloud platform, and a description is given below of a pre-configuration of the cloud platform. The pre-configuration of the cloud platform comprises deployment of a k8s meta-cluster and a service hosting cluster; three steps of registering and checking edge nodes and deploying and checking edge services are respectively described below.

For the process of deploying the k8s meta cluster and hosting cluster, referring to fig. 3, fig. 3 is a flowchart of another management method for edge devices according to an embodiment of the present application, including the following steps:

301. and deploying the meta-cluster.

In this embodiment, the meta cluster is a k8s meta cluster, and includes a k8s master node and a k8s node; wherein, the node of k8s can be added by horizontal quick expansion, and a master component for hosting the k8s cluster is run on the node, and the master component is used for the management of the edge device.

Specifically, the deployment of the meta-cluster may be set according to all node nodes associated with the current k8s master node, or may select some of them, for example: and initiating resource detection on the node to acquire the working information (load state, availability and the like) of the node, so as to select the node with the state meeting the condition for deployment.

302. And marking the nodes of the meta-cluster with region labels.

In this embodiment, an area tag is set for a node of a meta-cluster, which is equivalent to an identifier set for a control component (master component) in a managed cluster.

Specifically, the setting of the area identifier may be division according to a specific service, for example, the control component responsible for the service a is marked with an identifier 1, the control component responsible for the service B is marked with an identifier 2, and a corresponding identifier is correspondingly set for the associated device on the service path responsible for the control component; the setting of the area identification can also be division according to the geographical range, and because the deployment of the edge equipment has regionality, the master component, namely the node, can be set at different geographical positions, thereby ensuring the convenience of the edge management process.

It can be understood that the area identifier may be used as a reference in the edge device management process, that is, the device deployment may also be performed without the area identifier in the actual edge device management process, so as to avoid device scheduling when a sudden device failure occurs.

303. A target service of the hosted cluster is created.

In this embodiment, the target service is an etcd service for creating managed k8s, the etcd is a distributed service system with distributed and reliable key-value storage, and the etcd service is not only used for storage, but also provides shared configuration and service discovery.

Specifically, the storage in the etcd service is a flat binary key space, and the key space has a lexicographic order index for keys (byte strings), so that the cost of range query is low. Where the key space maintains multiple revisions (versions), each atomic change operation (a transaction may consist of multiple sub-operations) will produce a new revision. The revisions are monotonically increasing throughout the life cycle of the cluster. Revisions also support indexing, so range scanning based on revisions is also efficient. The compression operation needs to specify a revision number, and revisions smaller than the revision number are removed, so that the compression accuracy is guaranteed.

304. A control component hosting a cluster is created on a node of the meta-cluster.

In this embodiment, the process of creating the control component of the hosted cluster is to deploy the master component on the node, so that the node has the capability of managing the edge device.

305. An access interface address of the hosting cluster is configured.

In this embodiment, after deploying the master component on the node, a plurality of edge devices may be managed, and in a possible scenario, one hosting cluster (including a plurality of node nodes on which the master component is deployed) may manage 5000 edge devices. Therefore, it is necessary to perform corresponding multi-interface configuration for the hosted cluster, and store the access interface address through the etcd service and associate the corresponding device, so as to ensure the independence of the service between master components.

306. It is checked whether the hosted cluster is available.

In this embodiment, the checking process may query the cluster health check interface by calling the etcd service, so as to check the interface and test the related service, so as to check whether the deployment of the hosted cluster is normal.

307. And returning service deployment failure and error reporting.

In this embodiment, if the check performed on the managed cluster in step 306 indicates that the managed cluster is not available, a service deployment failure and an error are returned, so as to facilitate deployment adjustment.

308. Creating a hosted cluster is complete.

In this embodiment, if the service is normal, an interface for deploying the hosted cluster is called, a k8s hosted cluster master service is deployed, and the hosted cluster master service runs on a node of a k8s meta cluster. Thereby configuring the access address of the managed k8s system interface (api), i.e. illustrating meta-cluster and managed cluster deployment completion.

As for the process of registering and checking edge nodes, as shown in fig. 4, fig. 4 is a flowchart of another management method for edge devices according to the embodiment of the present application, and includes the following steps:

401. one or more edge devices are registered.

In this embodiment, in order to ensure the reliability of the edge device, the edge device accessing the hosting cluster needs to be registered on the cloud platform.

402. Filling in edge device registration parameters.

In this embodiment, the registration parameters of the edge device include identification information (device number, authentication number, etc.) of the edge device, location information (IP address, home location, etc.), and function information (load capacity, available state, etc.).

403. It is checked whether the node satisfies the registration condition.

In this embodiment, the judgment of the registration condition may be performed according to the registration parameter, that is, one or more of the identification information, the location information, or the function information is verified, for example, the credibility of the authentication number is checked; the frequency of replacement of home locations; whether it is in an optimum load state, etc.

404. Returning the registration failure and reporting the error.

In this embodiment, if the registration information of the edge device does not satisfy the registration condition in step 403, a registration failure and a specific failure reason, that is, an error reporting process, are fed back to the cloud platform.

It will be appreciated that the recording of the respective edge device may be made after an error, with a reminder being made when the device registers again to further check for the dimension indicated by the error.

405. A hosting cluster is automatically selected.

In this embodiment, if the registration condition is satisfied, the hosted cluster is automatically selected, specifically, the automatic selection process may be performed based on the location information, for example, the hosted cluster belonging to the same area as the edge device is automatically selected; the process of automatic selection may be based on the service, for example, a process of automatically selecting a hosted cluster belonging to service a with the edge device, thereby saving subsequent grouping of edge devices.

406. And judging whether the number of the nodes of the hosting cluster reaches an upper limit.

In this embodiment, in consideration of the capacity of the hosting cluster and the efficiency of managing the edge devices, an upper limit device may be performed on the number of nodes (edge devices) managed in the hosting cluster, specifically, the upper limit may be a load upper limit, that is, the number of nodes accessed at most; the upper limit may also be a numerical value set by real-time resource load conditions of different hosting clusters, for example, the busy hour threshold is 80% of the upper limit of the load, the idle hour threshold is 60% of the upper limit of the load, and the specific numerical value setting is determined according to an actual scene, so that stability of the hosting cluster in managing the edge device is ensured.

407. A hosted cluster is created.

In this embodiment, if the upper limit is reached, a hosting cluster is created, specifically, the created hosting cluster may repeat the steps in the embodiment shown in fig. 3, or a hosting cluster that does not access the edge device in the steps in the embodiment shown in fig. 3 or a hosting cluster that does not reach the upper limit is selected.

It can be understood that, for the creation of a new hosted cluster, association is performed with the registered edge device during the creation process, that is, association is performed with the edge device immediately after the hosted cluster is created, so that the access efficiency of the edge device is improved.

408. It is checked whether the node has successfully registered.

In this embodiment, after the node corresponding to the edge device is associated with the hosting cluster, a second node verification needs to be performed, that is, the reliability of the contact between the edge device and the hosting cluster is ensured. Specifically, the checking may be performed through a process of sending the identification information, that is, the hosting cluster sends a checking instruction to the associated edge device, and the edge device may respond to the checking instruction and determine whether the check node is successfully registered according to a response condition.

409. And returning the node registration failure and error report.

In this embodiment, according to the response of the check instruction in step 408, if the hosting cluster does not receive the response of the edge device, it indicates that the registration of the edge device fails, and generates the relevant information of the edge device, so as to facilitate the inspection.

410. The edge node registration is successful.

In this embodiment, according to the response of the check instruction in step 408, if the hosted cluster receives the response of the edge device, it indicates that the edge device is successfully registered, and the edge device has been deployed as an edge node in the hosted cluster.

Further, for the process of deploying and checking the edge service, referring to fig. 5, fig. 5 is a flowchart of another management method for an edge device according to an embodiment of the present application, including the following steps:

501. uploading the edge service image to an image repository.

In this embodiment, the process of the edge service is a process of issuing the service through the cloud platform, and in order to ensure the consistency of the service, the edge service image may be uploaded to the image warehouse at first. Specifically, a mirror repository may contain multiple namespaces, that is, different namespaces for different edge services are configured, so as to implement parallel multi-service.

502. An edge mirroring service is deployed.

In this embodiment, the process of deploying the edge mirror service calls an edge service deployment interface, and deploys the edge service through the service mirror.

503. And filling out the deployment parameters of the edge service.

In this embodiment, the deployment parameter may include a resource parameter and a regional parameter of the demand, specifically, the resource parameter is a relevant parameter used for indicating hardware or software resources required by the edge service operation process, for example: the occupied resource amount, the required equipment number and the like; and the region parameter is used for indicating the object targeted by the edge service, and further selecting the edge equipment which is closer to the object.

504. And selecting the edge equipment meeting the deployment parameter condition.

In this embodiment, the satisfaction of the deployment parameter condition, that is, the satisfaction of the resource parameter or the regional parameter dimension, for example, the edge device whose operation capacity reaches 1G is selected, or the edge device within the range a is selected.

505. And the cloud platform automatically deploys the edge service to the corresponding edge device.

In this embodiment, the edge service can be rapidly deployed to the corresponding edge device by selecting the edge device by the hosting cluster and determining the corresponding interface.

506. It is checked whether the edge service deployment is successful.

In this embodiment, the checking of the deployment condition of the edge service may be performed by calling an edge service health check interface to check whether the edge service is successfully deployed.

507. And returning service deployment failure and error reporting.

In this embodiment, if the health check indicates an exception, a service deployment failure is returned, and a corresponding edge service is recorded, so as to facilitate checking.

508. And returning the deployment success.

In this embodiment, if the health check is normal, the edge service is deployed successfully.

After the configuration process of the cloud platform and the edge node is performed, a system architecture diagram as shown in fig. 6 may be obtained, where fig. 6 is a system architecture diagram of another management method for an edge device according to the embodiment of the present disclosure. The method mainly comprises a cloud platform (cloud) central control device (meta k8s master) and an edge device (node) of an edge terminal (edge). Three deployment cluster nodes 1-3(node1-3) are associated in the meta cluster (meta) corresponding to the central control device, four control components a-D (k8s master pod a-D) are configured in each deployment cluster through corresponding etcd services a-D, and each control component is associated with four edge devices at an edge end, and the specific number of the devices is determined by an actual scene, which is only an example here.

Specifically, the deployment process of the edge service in fig. 6 relates to a selection process of a control component and an edge device in a hosted cluster (node), and the hosted cluster is expressed as a node in the following embodiments.

In a possible scenario, the edge service includes 4 threads of sub-services, and at this time, the service needs to be issued, the central control device firstly traverses the load state of the nodes in the element cluster, and determines that the nodes 1-3 perform the distribution of the sub-services; next, the node traverses the load state of the control component managed by itself, and selects the control component satisfying the load condition to execute the sub-service, for example: a free component; as the load state of the node1 in the figure approaches saturation, only the control component A is called to carry out the load of the sub-service; the load state of the node 2 is free, so that the load of the sub-service is carried out by calling the control component B and the control component C; the load state of the node 3 is close to saturation, so that the control component D is called to carry out the load of the sub-service; based on the determination of the control component, the control component issues the sub-services according to the edge devices managed by the control component.

It can be understood that the control component issues the sub-service may be to issue the edge device within the target range, that is, to issue the sub-service by using the area tag in the edge device registration process, so as to improve the service issuing efficiency and accuracy.

It can be understood that the cloud central control device creates and manages a plurality of k8s hosting clusters by one k8s meta-cluster; the node nodes of the meta-cluster can be transversely expanded quickly, and the number of managed clusters can be established and expanded quickly; one hosted cluster can manage 5000 edge devices at most, so that the number of edge devices that can be taken over can be rapidly expanded by rapidly creating and managing multiple hosted clusters.

In a possible scenario, the method and the device can be applied to various edge computing scenarios, such as edge devices such as various cameras on a highway, video monitoring in a cell, edge devices such as various face recognition devices, various PCDN and CDN edge devices.

Next, a description is given with reference to a configuration scene of a camera on a highway, as shown in fig. 7, fig. 7 is a flowchart of another management method for edge devices according to an embodiment of the present application; including but not limited to the following steps:

701. and acquiring edge equipment corresponding to the newly added road.

In the embodiment, the method is applied to the extended scene of the road cameras, and as the number of the deployed road cameras is large and the deployment is wide, the method for managing the edge devices can be used for performing a rapid device extension process.

Specifically, the edge device corresponding to the newly added road is the camera device added in the newly added road, so that the camera device can be registered in the cloud for management, and the control component in the hosting cluster in the application is associated, wherein the hosting cluster can be set according to the area tag, for example, the hosting cluster configured for the road in the area a is used, and therefore the matching between the camera device and the hosting cluster in the cloud registration process is improved.

In this embodiment, the step of the embodiment shown in fig. 4 is referred to in the registration process of the edge device, and details are not described here.

702. And deploying the edge equipment based on the cloud platform.

In this embodiment, the process of deploying the edge device refers to an association process between the edge device and the control component in fig. 3 or fig. 5, which is not described herein again.

703. And deploying the task of the corresponding area of the newly added road to the edge equipment.

In this embodiment, because the newly added road and the edge device configured by the newly added road have certain geographical location characteristics, the hosting clusters in the corresponding area can be configured nearby for management, thereby improving the management efficiency.

On the other hand, task execution information, that is, camera information, of each hosted cluster may be obtained by the central control device corresponding to the meta cluster, for example: vehicle violation information; specifically, the vehicle violation information can be uploaded to the central control device after camera shooting information is collected and processed in the hosting cluster, namely the violation information collected by the central control device is a set of violation information of each area.

By the management method of the edge device, the cameras can be comprehensively accessed into a camera management system of the expressway, the overall management efficiency cannot be influenced by the number of the continuously increased cameras, the large-scale cameras can be conveniently accessed into a cloud platform, and the management process of corresponding tasks is carried out.

In order to better implement the above-mentioned aspects of the embodiments of the present application, the following also provides related apparatuses for implementing the above-mentioned aspects. Referring to fig. 8, fig. 8 is a schematic structural diagram of a management apparatus of an edge device according to an embodiment of the present application, where the management apparatus 800 includes:

a determining unit 801, configured to determine, in response to a target instruction, a meta-cluster deployed in a cloud platform, where the meta-cluster includes a central control device and at least one associated managed cluster, the central control device is configured to issue the target instruction to the managed cluster, and at least one control component is configured in the managed cluster;

an obtaining unit 802, configured to obtain an edge device to be deployed;

a management unit 803, configured to associate the edge device with the control component according to a deployment rule, so that the edge device accesses to the corresponding hosted cluster, where the hosted cluster is configured to deploy, at the edge device, an edge service corresponding to the target instruction, and the deployment rule is determined based on location information or business information corresponding to the edge service.

Optionally, in some possible implementations of the present application, the determining unit 801 is specifically configured to set an area label for a node unit in an initial cluster in response to the target instruction;

the determining unit 801 is specifically configured to invoke a target service within the range of the area tag to determine a target interface in the node unit;

the determining unit 801 is specifically configured to create the control component in the node unit based on the target interface to determine as the hosted cluster;

the determining unit 801 is specifically configured to determine the central control device associated with the hosted cluster to determine the meta-cluster.

Optionally, in some possible implementations of the present application, the determining unit 801 is specifically configured to create the control component in the node unit based on the target interface, and invoke a detection process;

the determining unit 801 is specifically configured to determine that the control component is the hosted cluster if the detection process indicates that the control component is normally served on the node unit.

Optionally, in some possible implementations of the present application, the obtaining unit 802 is specifically configured to determine a plurality of candidate edge devices;

the obtaining unit 802 is specifically configured to call a node registration interface of a cloud platform to obtain registration parameters of the candidate edge device;

the obtaining unit 802 is specifically configured to determine the edge device to be deployed based on the registration parameter.

Optionally, in some possible implementation manners of the present application, the obtaining unit 802 is specifically configured to determine the location information of the candidate edge device according to the registration parameter;

the obtaining unit 802 is specifically configured to determine the corresponding hosting cluster based on the location information;

the obtaining unit 802 is specifically configured to perform node registration in the hosted cluster to determine the edge device to be deployed.

Optionally, in some possible implementation manners of the present application, the obtaining unit 802 is specifically configured to obtain load information of the hosted cluster;

the obtaining unit 802 is specifically configured to perform node registration in the hosted cluster if the load information meets a preset condition, so as to determine the edge device to be deployed.

Optionally, in some possible implementation manners of the present application, the obtaining unit 802 is specifically configured to create a candidate hosting cluster based on the edge device to be deployed if the load information does not meet the preset condition.

Optionally, in some possible implementation manners of the present application, the management unit 803 is specifically configured to associate the edge device with the control component according to a deployment rule, and upload a mirror service corresponding to the edge service to a mirror repository;

the management unit 803 is specifically configured to deploy the mirroring service in the mirroring repository;

the management unit 803 is specifically configured to deploy, based on the mirroring service, an edge service corresponding to the target instruction at the edge device.

Optionally, in some possible implementation manners of the present application, the management unit 803 is specifically configured to determine a deployment parameter corresponding to the mirroring service;

the management unit 803 is specifically configured to determine a deployment space according to the deployment parameter, so as to perform deployment in the mirror image warehouse.

Optionally, in some possible implementation manners of the present application, the management unit 803 is specifically configured to initiate a deployment test instruction;

the management unit 803 is specifically configured to test the edge service in the edge device based on the deployment test instruction to obtain a test result;

the management unit 803 is specifically configured to complete the deployment of the edge service in the edge device if the test result meets the test condition.

Referring to fig. 9, fig. 9 is a schematic structural diagram of a server provided in this embodiment, where the server 900 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 922 (e.g., one or more processors) and a memory 932, and one or more storage media 930 (e.g., one or more mass storage devices) storing an application 942 or data 944. Memory 932 and storage media 930 can be, among other things, transient storage or persistent storage. The program stored on the storage medium 930 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, a central processor 922 may be provided in communication with the storage medium 930 to execute a series of instruction operations in the storage medium 930 on the server 900.

The server 900 may also include one or more power supplies 926, one or more wired or wireless network interfaces 950, one or more input-output interfaces 958, and/or one or more operating systems 941, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

The steps performed by the management apparatus in the above-described embodiment may be based on the server configuration shown in fig. 9.

An embodiment of the present application further provides a computer-readable storage medium, where management instructions of an edge device are stored in the computer-readable storage medium, and when the management instructions are executed on a computer, the computer is enabled to perform the steps performed by the management apparatus of the edge device in the method described in the foregoing embodiments shown in fig. 1 to 7.

Also provided in the embodiments of the present application is a computer program product including instructions for managing an edge device, which when run on a computer, causes the computer to perform the steps performed by the management apparatus of the edge device in the method described in the foregoing embodiments shown in fig. 1 to 7.

An embodiment of the present application further provides a management system of an edge device, where the management system of an edge device may include the management apparatus of an edge device in the embodiment described in fig. 8 or the server described in fig. 9.

In a possible scenario, the method for network resource management in the present application is applied to a blockchain device, that is, an authoritative DNS, an LDNS, or a terminal is a blockchain device, and the blockchain device is a node in a blockchain, which is described below with reference to the accompanying drawings; referring to the data sharing system shown in fig. 10A, the data sharing system 1000 refers to a system for performing data sharing between nodes, the data sharing system may include a plurality of nodes 1001, and the plurality of nodes 1001 may refer to respective clients in the data sharing system. Each node 1001 may receive input information while performing normal operations and maintain shared data within the data sharing system based on the received input information. In order to ensure information intercommunication in the data sharing system, information connection can exist between each node in the data sharing system, and information transmission can be carried out between the nodes through the information connection. For example, when an arbitrary node in the data sharing system receives input information, other nodes in the data sharing system acquire the input information according to a consensus algorithm, and store the input information as data in shared data, so that the data stored on all the nodes in the data sharing system are consistent.

Each node in the data sharing system has a node identifier corresponding thereto, and each node in the data sharing system may store a node identifier of another node in the data sharing system, so that the generated block is broadcast to the other node in the data sharing system according to the node identifier of the other node in the following. Each node may maintain a node identifier list as shown in the following table, and store the node name and the node identifier in the node identifier list correspondingly. The node identifier may be an IP (Internet Protocol) address and any other information that can be used to identify the node, and table 1 only illustrates the IP address as an example.

TABLE 1 correspondence of node names to node identifiers

Node name	Node identification
		Node1	117.114.151.174
Node 2	117.116.189.145
		…	…
Node N	119.123.789.258

Each node in the data sharing system stores one identical blockchain. The block chain is composed of a plurality of blocks, as shown in fig. 10B, the block chain is composed of a plurality of blocks, the starting block includes a block header and a block main body, the block header stores an input information characteristic value, a version number, a timestamp and a difficulty value, and the block main body stores input information; the next block of the starting block takes the starting block as a parent block, the next block also comprises a block head and a block main body, the block head stores the input information characteristic value of the current block, the block head characteristic value of the parent block, the version number, the timestamp and the difficulty value, and the like, so that the block data stored in each block in the block chain is associated with the block data stored in the parent block, and the safety of the input information in the block is ensured.

When each block in the block chain is generated, referring to fig. 10C, when the node where the block chain is located receives the input information, the input information is verified, after the verification is completed, the input information is stored in the memory pool, and the hash tree for recording the input information is updated; and then, updating the updating time stamp to the time when the input information is received, trying different random numbers, and calculating the characteristic value for multiple times, so that the calculated characteristic value can meet the following formula:

SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))＜TARGET

wherein, SHA256 is a characteristic value algorithm used for calculating a characteristic value; version is version information of the relevant block protocol in the block chain; prev _ hash is a block head characteristic value of a parent block of the current block; merkle _ root is a characteristic value of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, is a fixed value within a period of time, and is determined again after exceeding a fixed time period; x is a random number; TARGET is a feature threshold, which can be determined from nbits.

Therefore, when the random number meeting the formula is obtained through calculation, the information can be correspondingly stored, and the block head and the block main body are generated to obtain the current block. And then, the node where the block chain is located respectively sends the newly generated blocks to other nodes in the data sharing system where the newly generated blocks are located according to the node identifications of the other nodes in the data sharing system, the newly generated blocks are verified by the other nodes, and the newly generated blocks are added to the block chain stored in the newly generated blocks after the verification is completed.

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 embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a management apparatus of an edge device, 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: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

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

1. A method for managing an edge device, comprising:

acquiring edge equipment to be deployed;

2. The method of claim 1, wherein determining the meta-cluster deployed at the cloud platform in response to the target instruction comprises:

3. The method of claim 2, wherein creating the control component in the node unit based on the target interface to determine as the hosted cluster comprises:

4. The method of claim 1, wherein obtaining the edge device to be deployed comprises:

determining a plurality of candidate edge devices;

5. The method of claim 4, wherein the determining the edge device to be deployed based on the registration parameters comprises:

determining the corresponding hosted cluster based on the location information;

6. The method of claim 5, wherein the node registration in the hosted cluster to determine the edge device to be deployed comprises:

acquiring load information of the hosting cluster;

7. The method of claim 6, further comprising:

8. The method of claim 1, wherein associating the edge device with the control component according to a deployment rule comprises:

deploying the mirroring service in the mirroring repository;

9. The method of claim 8, wherein deploying the mirroring service in the mirroring repository comprises:

determining deployment parameters corresponding to the mirror image service;

10. The method according to any one of claims 1-9, further comprising:

initiating a deployment test instruction;

11. The method of claim 1, wherein the meta-cluster and the hosted cluster are managed through kubernets, and wherein the target instruction is used to expand the number of edge devices managed by the cloud platform.

12. The method according to claim 1, wherein the management method of the edge device is applied to a blockchain device, and the blockchain device is a node in a blockchain.

13. An apparatus for managing an edge device, comprising:

14. A computer device, the computer device comprising a processor and a memory:

the memory is used for storing program codes; the processor is configured to execute the method for managing an edge device according to any one of claims 1 to 12 according to instructions in the program code.

15. A computer-readable storage medium having stored therein instructions which, when run on a computer, cause the computer to execute the method of managing an edge device of any one of claims 1 to 12.