CN114301909A

CN114301909A - Edge distributed management and control system, method, equipment and storage medium

Info

Publication number: CN114301909A
Application number: CN202111460541.9A
Authority: CN
Inventors: 周晶
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2021-12-02
Filing date: 2021-12-02
Publication date: 2022-04-08
Anticipated expiration: 2041-12-02
Also published as: CN114301909B

Abstract

The embodiment of the application provides an edge distributed management and control system, method, device and storage medium. In the embodiment of the application, the edge nodes are managed by adopting the distributed clusters, in the distributed clusters, the edge management and control are layered from three dimensions of object arrangement, resource scheduling and object synchronization and resource management and control, namely, the object arrangement clusters of the first layer execute arrangement operation of application examples for tenants, tenant isolation can be realized, the resource scheduling and object synchronization clusters of the second layer undertake synchronization of the resource scheduling and the data related to the application examples, and the deployment of the application examples is completed by the node management and control clusters of the third layer, so that the availability, stability and convenience of management and control of services can be integrally improved, and real wide-coverage and large-scale cluster management and control services are provided for the tenants.

Description

Edge distributed management and control system, method, equipment and storage medium

Technical Field

The present application relates to the field of cloud computing technologies, and in particular, to a system, a method, a device, and a storage medium for edge distributed management and control.

Background

The edge cloud, namely edge cloud computing, is a distributed cloud computing platform constructed on an edge infrastructure based on the core and edge computing capability of a cloud computing technology, forms an elastic cloud platform with comprehensive computing, network, storage, safety and other capabilities at an edge position, forms an end-to-end technical framework of 'cloud edge end three-body cooperation' with a central cloud and an internet of things terminal, reduces response time delay, reduces cloud pressure, reduces bandwidth cost, and can provide cloud services such as whole network scheduling, computing power distribution and the like by putting network forwarding, storage, computing, intelligent data analysis and other works at the edge. The cloud computing platform provides Edge Node Service (ENS) to the outside based on edge nodes, the edge node service is constructed based on operator edge nodes and a network, and the cloud computing platform provides 'fusion, opening, linkage and elasticity' distributed computing resources in a one-stop mode, so that computing time delay and cost are effectively reduced.

With the development of edge technologies, the edge scale is larger and larger, the number of edge nodes is larger and larger, edge clouds appear, the service requirements of clients in different industries on low delay, large bandwidth and data nearby processing can be met, and particularly under the conditions that the 5G technology is gradually paved, national strategies and company strategies are gradually clear, infrastructure is continuously perfected, edge services and scenes are gradually enriched, edge computing has the characteristics of super-large-scale isomerism, fusion, miniaturization, wide coverage and the like. Therefore, it is becoming increasingly important how to provide more fluid, high quality, large-scale computing services at the edge.

In the process of handling edge large-scale, wide-coverage, miniaturization, heterogeneous integration and distributed multi-cloud cluster management, how to provide real wide-coverage for tenants is a great challenge for edge computing.

Disclosure of Invention

Aspects of the present disclosure provide a system, a method, a device, and a storage medium for edge distributed management and control, so as to improve stability of an edge distributed management and control system.

The embodiment of the present application provides an edge distributed management and control system, including: a plurality of edge nodes to be managed and controlled and a distributed management and control cluster, wherein the distributed management and control cluster comprises: a plurality of object arrangement clusters of a first layer, a resource scheduling and object synchronization cluster of a second layer and a plurality of node control clusters of a third layer; each object orchestration cluster is delivered to a tenant, forms a routing relation with at least one node management and control cluster, and is used for executing orchestration operation of an application instance aiming at the tenant to create the application instance; the resource scheduling and object synchronizing cluster is used for scheduling the application instance to target resource equipment based on a routing relation between a maintained object arranging cluster and a node control cluster when it is monitored that the application instance is created, and synchronizing a data deployment task related to the application instance to the target node control cluster, wherein the target node control cluster is a node control cluster which is responsible for managing edge nodes to which the target resource equipment belongs; each node management and control cluster is responsible for managing at least one edge node and is used for controlling target resource equipment to locally deploy the application instance according to the data deployment task related to the application instance under the condition that the node management and control cluster serves as a target node.

The embodiment of the present application further provides an application instance deployment method, which is applied to a resource scheduling and object synchronization cluster in an edge distributed management and control system, where the resource scheduling and object synchronization cluster is located in a second layer of the distributed management and control cluster, and the distributed management and control cluster further includes: the method comprises the following steps that a plurality of object arrangement clusters of a first layer and a plurality of node management and control clusters of a third layer are arranged, and the method comprises the following steps: the resource scheduling and object synchronization cluster monitors whether a plurality of object editing clusters execute the creation operation of the application instance or not so as to create the application instance; when it is monitored that an application instance is created, scheduling the application instance to target resource equipment based on a routing relation between the maintained object orchestration cluster and the node management and control cluster; synchronizing the data deployment tasks related to the application examples to a target node management and control cluster so that the target node management and control cluster can control target resource equipment to locally deploy the application examples; the target node control cluster is a node control cluster which is responsible for managing the edge nodes to which the target resource equipment belongs.

The embodiment of the present application further provides an application instance deployment method, which is applied to any node control cluster in an edge distributed control system, where the node control cluster is located at a third layer in the distributed control cluster, and the distributed control cluster further includes: a plurality of object orchestration clusters at a first level and resource scheduling and object synchronization clusters at a second level, the method comprising: receiving data related to the application instance of resource scheduling and object synchronization cluster synchronization, wherein the application instance is created by an object arrangement cluster corresponding to any node control cluster, the application instance needs to be deployed on target resource equipment, and the target resource equipment is determined from edge nodes which are responsible for management of any node control cluster based on the routing relation between the maintained object arrangement cluster and the node control cluster by the resource scheduling and object synchronization cluster; and controlling the target resource equipment to locally deploy the application instance according to the data related to the application instance.

The embodiment of the present application further provides a resource scheduling and object synchronization cluster, including: the application instance deployment method comprises a memory for storing a computer program and a processor coupled with the memory for executing the computer program to implement the steps in the application instance deployment method provided by the embodiment of the application.

An embodiment of the present application further provides a node management and control cluster, including: the application instance deployment method comprises a memory for storing a computer program and a processor coupled with the memory for executing the computer program to implement the steps in the application instance deployment method provided by the embodiment of the application.

An embodiment of the present application further provides a distributed management and control cluster, including: a plurality of object arrangement clusters of a first layer, a resource scheduling and object synchronization cluster of a second layer and a plurality of node control clusters of a third layer; each object orchestration cluster is delivered to a tenant, forms a routing relation with at least one node management and control cluster, and is used for executing orchestration operation of an application instance aiming at the tenant to create the application instance; the resource scheduling and object synchronizing cluster is used for scheduling the application instance to target resource equipment based on a routing relation between the maintained object scheduling cluster and the node control cluster when the application instance is monitored to be created, and synchronizing data related to the application instance to the target node control cluster, wherein the target node control cluster is a node control cluster which is responsible for managing the edge node to which the target resource equipment belongs; each node management and control cluster is responsible for managing at least one edge node and is used for controlling target resource equipment to locally deploy the application instance according to the data related to the application instance under the condition that the node management and control cluster serves as a target node.

Embodiments of the present application further provide a computer storage medium storing a computer program, which, when executed by a processor, causes the processor to implement the steps in the application instance deployment method provided in the embodiments of the present application.

In the embodiment of the application, the edge nodes are managed by adopting the distributed clusters, in the distributed clusters, the edge management and control are layered from three dimensions of object arrangement, resource scheduling and object synchronization and resource management and control, namely, the object arrangement clusters of the first layer execute arrangement operation of application examples for tenants, tenant isolation can be realized, the resource scheduling and object synchronization clusters of the second layer undertake synchronization of the resource scheduling and the data related to the application examples, and the deployment of the application examples is completed by the node management and control clusters of the third layer, so that the availability, stability and convenience of management and control of services can be integrally improved, and real wide-coverage and large-scale cluster management and control services are provided for the tenants.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a schematic structural diagram of an edge distributed management and control system according to an exemplary embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of another edge distributed management and control system according to an exemplary embodiment of the present application;

fig. 3 is a flowchart illustrating an application instance deployment method according to an exemplary embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating another application instance deployment method according to an exemplary embodiment of the present application;

FIG. 5 is a schematic structural diagram of a resource scheduling and object synchronization cluster according to an exemplary embodiment of the present application;

fig. 6 is a schematic structural diagram of a node management and control cluster according to an exemplary embodiment of the present application;

fig. 7 is a schematic structural diagram of a distributed management and control cluster according to an exemplary embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the embodiment of the application, the edge nodes are managed by adopting a distributed cluster, in the distributed cluster, the edge management and control are layered from three dimensions of object arrangement, resource scheduling and object synchronization and resource management and control, namely, the object arrangement cluster of the first layer executes arrangement operation of application instances for tenants, tenant isolation can be realized, the resource scheduling and object synchronization cluster of the second layer undertakes synchronization of the resource scheduling and the data related to the application instances, and the deployment of the application instances is completed by the node management and control cluster of the third layer, so that the usability, stability and convenience of the tenant management and control can be improved on the whole, and the true wide coverage and large-scale cluster management and control service is provided for the tenants.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

Fig. 1 is a schematic structural diagram of an edge distributed management and control system according to an exemplary embodiment of the present application. As shown in fig. 1, the edge distributed management and control system 100 includes: a distributed policing cluster 10 and a plurality of edge nodes 20 to be policed. Wherein, distributed management and control cluster 10 includes: a plurality of object orchestration clusters 101 at a first level, a resource scheduling and object synchronization cluster 102 at a second level, and a plurality of node management and control clusters 103 at a third level.

In this embodiment, the edge nodes 20 are dispersed in different area locations, the coverage network has a wide range, and has a characteristic of being closer to the terminal, and the resource scale of a single edge node 20 is smaller, but the number of edge nodes 20 is relatively large. The edge nodes 20 may all be deployed by the same Internet Service Provider (ISP), or may be implemented by non-ISP deployment, which is not limited to this.

In the present embodiment, each edge node 20 includes a series of edge infrastructures including, but not limited to: a distributed Data Center (DC), a wireless room or cluster, an edge device such as a communication network of an operator, a core network device, a base station, an edge gateway, a home gateway, a computing device and/or a storage device, a corresponding network environment, and so on. In some alternative embodiments, the edge node 20 may be implemented as an Internet Data Center (IDC) located at the edge, that is, one edge IDC is one edge node 20 in this embodiment; alternatively, the edge node 20 may be implemented as a machine room located at the edge, that is, one machine room is one edge node 20 in the embodiment of the present application. It is noted that the location, capabilities, and infrastructure involved of the various edge nodes 20 may or may not be the same. Based on these edge infrastructures, the edge node 20 may provide various resources to the outside, such as resources with certain computing capabilities, such as CPUs, GPUs, servers, and computing devices, resources with storage capabilities, such as memories and hard disks, and network resources, such as bandwidths. In this embodiment, the resource with certain computing capability in the edge node 20 is referred to as a resource device 201, and may be, for example, a server, a computing device, or the like, and each edge node 20 includes at least one resource device 201.

The edge distributed management and control system 100 of this embodiment may be applied to various application scenarios such as a Content Delivery Network (CDN), an e-commerce, a game, an audio/video, an internet of things, logistics, an industrial brain, and an urban brain, and provides cloud computing services for terminal users in various scenarios. Specifically, for each application scenario, an application (hereinafter, simply referred to as an application) that can provide cloud computing services in the application scenario may be deployed in the edge node 20 in the edge distributed management and control system 100, where deploying the application in the edge node 20 is actually a process of deploying the application on the resource device 201 in the edge node 20. For example, in an e-commerce scenario, an application that can provide an online shopping function, for example, a server that can be an online shopping application, can be deployed on the resource device 201 in the edge node 20, and the server interacts with a shopping terminal to provide the online shopping function for a shopping user; in a game scenario, an application that can provide an online game function, for example, a server that can be an online game application, may be deployed on the resource device 201 in the edge node 20, and the server interacts with a game terminal to provide an online game service for a game user; in the field of audio and video, applications that can provide audio and video functions, such as a live broadcast service terminal, an on-demand service terminal, or a video monitoring service terminal, may be deployed on the resource device 201 in the edge node 20, and these service terminals interact with the playing terminal to provide services such as live broadcast, on-demand, or monitoring for a viewing user.

In this embodiment, with the development of edge node technology, the edge scale is larger and larger, the number of edge nodes is larger and larger, and the appearance of edge clouds can meet the service requirements of clients in different industries on low delay, large bandwidth and data processing nearby, and especially under the conditions that 5G technology is gradually spread, national strategy and company strategy are gradually clear, infrastructure is continuously perfected, and edge services and scenes are gradually enriched, edge computing gradually has the characteristics of super-large scale isomerism, fusion, miniaturization, wide coverage and the like. Therefore, it is becoming increasingly important how to provide more fluid, high quality, large-scale computing services at the edge.

In this embodiment, a distributed management and control cluster is adopted to perform distributed management and control on the plurality of edge nodes 20. The distributed control cluster three-layer cluster architecture comprises the following components: a plurality of object orchestration clusters 101 at a first level, a resource scheduling and object synchronization cluster 102 at a second level, and a plurality of node management and control clusters 103 at a third level.

In order to realize tenant isolation and protect the security of tenant data, each tenant is delivered to an object orchestration cluster 101, and the object orchestration cluster 101 can provide a uniform interface for each tenant to access cluster resources of the edge distributed management and control system, so that tenant isolation is realized. The object orchestration cluster 101 may perform orchestration operations of an application instance for a tenant to create the application instance. The orchestration operation of the application instance includes at least one of: creation of application instances, elastic scaling, rolling updates, reconstruction, migration, shutdown, and the like.

The creating of the application instance refers to a process of creating an application instance meeting the requirement on the resource device 201 for the first time according to the cloud computing service requirement information submitted by the tenant. The rolling update of the application instance refers to a process of gradually updating the application instance in batches to ensure the availability of the service when the mirror version is updated, and finally realizing the update of all the application instances, which relates to a process of deleting an original application program and creating a new application instance. The reconstruction of the application instance refers to a process of recreating a new application instance and deleting an original application instance when the application instance is abnormal. The application instance exception includes an exception of the application instance itself, and also includes an exception caused by a failure of the resource device 201 where the application instance is located. Shutdown of an application instance refers to the process of closing the application instance. The migration of the application instance refers to a process of migrating the application instance running on one resource device 201 to another resource device 201 due to a requirement, which involves a reconstruction of the application instance on another resource device 201 and a deletion operation of the original application instance. In addition to the reconstruction process related to the application program in the first creation of the application instance, the rolling update of the application instance, the reconstruction of the application instance and the migration process of the application, the elastic scaling of the application instance also relates to the deletion of the existing application instance and the creation of new application instances, and the creation of the new application instances also belongs to the situation of performing an orchestration operation on the application instances to create the application instances.

Wherein, the elastic expansion of the application example comprises transverse elastic expansion and longitudinal elastic expansion; the horizontal elastic expansion refers to increasing the number of application examples (referred to as horizontal expansion for short) when the service demand increases according to the cloud computing service demand and the strategy so as to ensure the cloud computing capacity, and reducing the number of application examples (referred to as horizontal contraction for short) when the service demand decreases so as to save the cost; correspondingly, the longitudinal elastic expansion and contraction refers to performing resource expansion (referred to as longitudinal expansion) on the application instance under the condition that the resource utilization rate is high and performing resource contraction (referred to as longitudinal contraction) on the application instance under the condition that the resource utilization rate is low according to the resource utilization condition of the application instance. Alternatively, whether the resource utilization rate of the application instance is higher or lower may be determined by setting an upper usage rate limit and a lower usage rate limit; if the resource utilization rate of the application example is higher than the set utilization rate upper limit value, the resource utilization rate of the application example is considered to be higher; and if the resource utilization rate of the application example is lower than the set utilization rate lower limit value, the resource utilization rate of the application example is considered to be lower. The horizontal expansion of the application instance is specifically a process of creating a new application instance, and the horizontal expansion of the application instance is specifically a process of deleting an existing application instance; vertical expansion or vertical contraction of an application instance involves two operations, namely reconstruction of a new application instance and deletion of an original application instance.

In this embodiment, a routing relationship exists between the object orchestration cluster 101 and at least one node management cluster 103, and in the case of an application instance created by the object orchestration cluster 101, data related to the application instance may be synchronized to one or several node management clusters 103 pointed to by the routing relationship, and the one or several node management clusters 103 control resource devices in the edge nodes 20 managed by the node management cluster 103 to locally deploy the application instance. Wherein deploying an application instance is the process of generating an application instance.

In this embodiment, the resource scheduling and object synchronizing cluster 102 is configured to monitor whether an application instance is created, and when it is monitored that an application instance is created, schedule the application instance to a target resource device based on a routing relationship between the maintained object orchestration cluster 101 and the node management and control cluster 103, and synchronize data of the application instance to the target node management and control cluster. The target resource device is a resource device which meets the resource arrangement requirement of the tenant. The target node control cluster is a node control cluster which is responsible for managing the edge nodes to which the target resource devices belong. That is, the resource scheduling and object synchronization cluster 102 in this embodiment performs resource scheduling (referred to as a resource scheduling function) for the application instance on the one hand, and performs data synchronization for the application instance on the other hand. Further optionally, when the application instance depends on the data object, the resource scheduling and object synchronization cluster 102 further needs to synchronize, for the data object that the application instance depends on, data related to the data object to the node management and control cluster. In this embodiment, various data (for example, data including application instance data and data object on which the application instance depends) synchronized by the resource scheduling and object synchronization cluster 102 to the node managing cluster are collectively referred to as "objects", and a function of the resource scheduling and object synchronization cluster 102 to synchronize various data to the node managing cluster is also referred to as an object synchronization function.

In this embodiment, each node management and control cluster 103 is responsible for managing at least one edge node 20, and in the case of serving as a target node management and control cluster, the target resource device controls to locally deploy an application instance according to data related to the application instance synchronized with the object synchronization cluster 102 by resource scheduling.

In an optional embodiment, each object orchestration cluster may configure, in addition to creating an application instance, data objects on which the application instance depends, where the data objects are used to represent data objects related to the application instance, where the data objects may describe the running state of the application instance, such as which application instances are running, where the application instance is deployed, such as on which edge node the application instance is running, and where the resources that the application instance may use and some policies of the runtime, such as which resources that may be used by the application instance and whether some application instance runtimes support a restart policy, an upgrade policy, or a fault tolerance policy, etc. If the object orchestration cluster is implemented as a kubernets (K8s), the application instance may be implemented as a container, and accordingly, the data objects on which the application instance depends may include, but are not limited to: container set (Pod), Service (Service), Volume (Volume), configuration map (ConfigMap), and the like. The Pod is deployed on the resource device 201 of the edge node 20, the Pod includes a container group formed by one or more containers, the Pod is a minimum deployment unit of the K8s cluster, and can be created and scheduled, and the application instance can be deployed on the one or more pods. Service may provide a single stable name and access address for the Pod, based on which the K8s Service agent may assign the user's Service request to the Pod. Volume is a shared directory in a Pod that can be accessed by multiple containers. The user of the Pod can store the common configuration variables of the Pod through the ConfigMap, and when the Pod needs to be accessed, the Pod can be accessed through the ConfigMap.

In this embodiment, the object orchestration cluster 101 performs an orchestration operation of an application instance for a tenant, creates the application instance, and configures a data object on which the application instance depends; when it is monitored that an application instance is created, the resource scheduling and object synchronizing cluster 102 schedules the application instance and the data objects depending on the application instance to a target resource device based on the maintained routing relationship between the object scheduling cluster 101 and the node control cluster 103, and synchronizes the data related to the application instance and the data objects depending on the application instance to the target node control cluster. Correspondingly, the target node management and control cluster 103 controls the target resource device to locally deploy the application instance and the data object depending on the application instance.

In this embodiment, the object orchestration cluster 101 is responsible for identifying instance orchestration requirements in the edge distributed management and control system, and performing orchestration operation on application instances according to the application instance orchestration requirements, so as to create application instances. The embodiment of identifying instance orchestration requirements in the edge distributed management and control system is not limited. The following examples are given.

Embodiment X1:the object orchestration cluster 101 supports interaction with a tenant, for example, an interaction interface may be provided for the tenant, and in implementation, the interaction interface may be a web page or a command window, and the tenant may submit edge service requirement information to the object orchestration cluster 101 through the interaction interface, where the edge service requirement of the tenant generally relates to an orchestration operation on an application instance.

Optionally, according to the difference of the edge service requirement, the application instance arrangement requirement identifiable by the object arrangement cluster 101 according to the edge service requirement information may also be different. The following examples illustrate:

in the case a1, a tenant needs to deploy its own cloud computing service in the edge distributed management and control system 100, and may submit demand information of the cloud computing service to the object orchestration cluster 101, where the demand information includes an area location of the cloud computing service, a service quality requirement, and the like, and accordingly, the object orchestration cluster 101 may recognize that the tenant is required to create an application instance capable of providing the cloud computing service, and the creation of the application instance is a specific application instance orchestration requirement.

In case a2, during the use of the cloud computing service, the tenant submits service upgrade requirement information to the object orchestration cluster 101 for service upgrade, where the service upgrade requirement information may include a new version of image file or information pointing to the new version of image file, and may further include a rolling upgrade policy to request the object orchestration cluster 101 to perform rolling upgrade on its application instance. The rolling upgrading strategy comprises information such as batches to be upgraded in batches, the number of application instances needing to be upgraded in each batch or identification of the application instances needing to be upgraded in each batch. In view of this, in the case of receiving the service upgrade requirement information submitted by the tenant, the object orchestration cluster 101 may identify that the application instance needs to be subjected to rolling upgrade, which is a specific container orchestration requirement.

In the case a3, in the cloud computing service usage process, the tenant may know the resource usage of the application instance according to the state data of the application instance, and if the resource usage of the application instance is low, may submit the demand information of vertical contraction to the object orchestration cluster 101, where the demand information may include the amount of resources that need to be reduced or new resource information after reduction, so as to request the object orchestration cluster 101 to perform resource contraction on its application instance. In view of this, if the requirement information of vertical capacity reduction submitted by the tenant is received, it is determined that a container arrangement requirement for resource capacity reduction on the application instance is identified.

In case a4, in the cloud computing service usage process, the tenant may learn the resource usage of the application instance according to the state data of the application instance, and if the resource usage of the application instance is high, may submit the demand information for longitudinal capacity expansion to the object orchestration cluster 101, where the demand information may include the amount of resources that need to be increased or new resource information after the increase, so as to request the object orchestration cluster 101 to perform resource capacity expansion on its application instance. In view of this, if the requirement information of longitudinal capacity expansion submitted by the tenant is received, it is determined that a container arrangement requirement for resource capacity expansion of the application instance is identified.

In case a5, in the cloud computing service usage process, a tenant submits requirement information of horizontal expansion to the object orchestration cluster 101 because a service requirement increases, where the requirement information may include an increase amount of the service requirement, where the increase amount has a corresponding relationship with the number of application instances, or may directly include the number of application instances that need to be expanded, so as to request the object orchestration cluster 101 to expand the number of application instances thereof. In view of this, if the requirement information of horizontal expansion submitted by the tenant is received, it is determined that a container arrangement requirement for quantity expansion of the application instances is identified.

In case a6, in the cloud computing service usage process, the tenant submits requirement information of horizontal contraction to the object orchestration cluster 101 because the service requirement decreases, where the requirement information may include a reduction amount of the service requirement, where the reduction amount has a corresponding relationship with the number of application instances, or may directly include the number of application instances that need to be reduced, so as to request the object orchestration cluster 101 to perform quantity contraction on its application instances. In view of this, if the requirement information of the horizontal capacity reduction submitted by the tenant is received, it is determined that a container arrangement requirement for performing quantity capacity reduction on the application instances is identified.

In case a7, in the process of using the cloud computing service, the tenant may know the running state of the application instance according to the state data of the application instance, and if the running of the application instance is found to be abnormal, in order to ensure the availability of the service, may submit application instance migration requirement information to the object orchestration cluster 101 to request the object orchestration cluster 101 to migrate its application instance. In view of this, if application instance migration requirement information submitted by a tenant is received, it is determined that a container orchestration requirement for migrating an application instance is identified.

Embodiment X2:the object orchestration cluster 101 may monitor the running state of the application instance existing in each edge node 20, or the node management and control cluster 103 monitors the running state of the application instance existing in each edge node 20, and reports the monitored running state of the application instance existing in each edge node 20 to the object orchestration cluster 101, and regardless of the above manner, after the object orchestration cluster 101 acquires the running state of the application instance existing in each edge node 20, it may determine whether to perform some kind or some kinds of orchestration operations, such as reconstruction and migration, on the application instance according to the monitored running state of each application instance, so as to identify the application instance orchestration requirement in the edge distributed management and control system 100.

Optionally, according to the different running states of the application instances, the application instance arrangement requirements recognizable by the object arrangement cluster 101 according to the running states of the application instances may also be different. The following examples illustrate:

in case B1, object orchestration cluster 101 may monitor the load of the application instances in each edge node 20; and when the load of the application example is monitored to be higher than the set upper limit value of the load, determining and identifying the arrangement requirement of the application example for quantity expansion of the application example.

In case B2, object orchestration cluster 101 may monitor the load of the application instances in each edge node 20; and when the load of the application example is monitored to be lower than the set lower load limit value, determining and identifying the arrangement requirement of the application example for quantity capacity reduction of the application example.

In case B3, object orchestration cluster 101 may monitor the running state of the application instances in each edge node 20; and when the abnormal operation of the application instance is monitored, determining and identifying the arrangement requirement of the application instance for migrating the application instance.

In case B4, the tenant may also authorize management of the image file to the object orchestration cluster 101, where the object orchestration cluster 101 is responsible for various management of saving, version upgrading, maintaining, and the like of the image file. Thus, when the image file of the new version is monitored, the arrangement requirement of the application instance for performing rolling upgrade on the application instance is determined and identified.

In the case B5, the object orchestration cluster 101 may monitor resource usage of the application instances in each edge node 20, and determine that an application instance orchestration requirement for resource expansion of the application instances is identified when it is monitored that the resource usage of the application instances is higher than the set upper limit of the usage.

In the case B6, the object orchestration cluster 101 may monitor resource usage of the application instances in each edge node 20, and determine that an application instance orchestration requirement for performing resource reduction on the application instances is identified when it is monitored that the resource usage of the application instances is lower than a set lower usage limit.

For the above embodiments X1 and X2, the case a1 relates to the first creation of an application instance, the cases a2, a7 and B3-B4 relate to the reconstruction of an application instance, the cases a4-a, B1 and B5 relate to the new creation of an application instance, and the first creation, reconstruction and new creation of the application instance all belong to the case of performing an orchestration operation on an application instance to create an application instance.

In an optional embodiment, the object arrangement cluster, the resource scheduling and object synchronization cluster, and the node control cluster in the distributed control cluster cooperate with each other to implement uniform and global arrangement and management of application instances among the edge nodes 20, which solves the problem of cluster control, but does not limit the specific implementation of the object arrangement cluster, the resource scheduling and object synchronization cluster, and the node control cluster, and all the ways that can implement the functional logic described in the above embodiments are applicable to the embodiments of the present application. For example, in some optional embodiments, the object orchestration cluster, the resource scheduling and object synchronization cluster, and the node management cluster may be implemented based on a kubernets (K8s) technology, that is, a cluster management engine implemented based on a K8s technology is respectively deployed on the object orchestration cluster, the resource scheduling and object synchronization cluster, and the node management cluster, as shown in fig. 2. In fig. 2, the number of the object orchestration cluster, the node management cluster, and the edge node is 1 for example, but not limited thereto.

Wherein, the K8s architecture mainly comprises a Master Node and a Work Node; the main node comprises a control-Manager Server, an interaction module (API Server), a storage module (Cluster state store) and a scheduling module (Scheduler). The management and control module is mainly used to maintain the state of the edge distributed management and control system 100, for example, fault detection, automatic expansion, rolling update, and the like. The interaction module is an API interface exposed to the outside by the main node and is an interface for interaction between the outside and the main node, and the tenant can submit edge service demand information to the main node through the interaction module. In addition, the interaction module may provide authentication, authorization, access control, API registration, and discovery functions. The storage module is mainly used for storing state information of each node in the edge distributed management and control system 100. The scheduling module is used for scheduling resources, and scheduling the resources for the edge nodes according to the resource use information of the edge nodes and the network service quality of the user areas served by the edge nodes.

In this embodiment, the object orchestration cluster, the resource scheduling and object synchronization cluster, and the node management and control cluster may be implemented based on the K8s technology. The functions that focus on when different clusters are implemented based on the K8s technique are not the same. As described in detail below.

Embodiment Y1:each object orchestration cluster 101 may be implemented as a K8s cluster, with object orchestration cluster 101 primarily focusing on the functionality of the interaction module, storage module, and management module that implement the K8s technique. Further, the object orchestration Cluster 101 may be implemented as a K8s Virtual Cluster (Virtual Cluster), and the K8s architecture implements isolation of multiple tenants based on a namespace, which may result in that data of some tenants is no longer isolated because each combination shares an interaction module (API Server). In the K8s architecture adopted in this embodiment, each tenant is delivered to one virtual cluster, that is, the object orchestration cluster 101, and multi-tenant isolation is realized by the object orchestration cluster 101.

Wherein the object orchestration cluster 101 comprises: a first API service node 101a, as shown in fig. 2. The first API service node provides a unified interface for cluster resource operations, and controls the operation of the resource devices by communicating with the kubel component on each resource device. In addition, the first API service node also provides functions of authentication, authorization, access control, API registration, discovery and the like. The first API service node may be implemented as an interaction module (API Server) in K8s, and the first API service node may determine, in response to the edge service requirement information submitted by the tenant, an application instance orchestration requirement corresponding to the tenant, and execute an orchestration operation of the application instance according to the application instance orchestration requirement to create the application instance. The edge service requirement information submitted by the tenant can be directly submitted to an object arrangement cluster corresponding to the tenant, specifically, the edge service requirement information is submitted to a main node in the object arrangement cluster, an interaction module (API Server) in the main node receives the edge service requirement information, the application instance arrangement requirement corresponding to the tenant is determined according to the edge service requirement information, and the arrangement operation of the application instance is executed according to the application instance arrangement requirement so as to create the application instance. Or, the first API service node may determine an application instance orchestration requirement corresponding to the tenant according to the running state of the existing application instance of the tenant, and execute an orchestration operation of the application instance according to the application instance orchestration requirement to create the application instance. Or, the first API service node may respond to the edge service requirement information submitted by the tenant and determine an application instance orchestration requirement corresponding to the tenant according to the running state of the existing application instance of the tenant, and execute an orchestration operation of the application instance according to the application instance orchestration requirement to create the application instance.

Wherein, the object orchestration cluster 101 further includes, in addition to the first API service node 101 a: distributed storage node 101b, as shown in FIG. 2, may be implemented as a storage module in the K8s technology. The at least one node control cluster 103 corresponding to the object orchestration cluster 101 is configured to monitor an operation state of an existing application instance of a tenant, and report the operation state to the object orchestration cluster 101, for example, the node control cluster 103 reports the operation state of the existing application instance of the tenant to a first API service node, and the first API service node provides the received operation state of the existing application instance to a distributed storage node. The distributed storage node stores the running state of the existing application instance of the tenant.

Further, the object orchestration cluster 101 includes, in addition to the first API service node 101a and the distributed storage node 101 b: cluster management node 101c, as shown in fig. 2. The cluster management node may be implemented as a policing module in the K8s architecture. Further may be implemented as a Virtual Cluster-manager (Virtual Cluster-manager) in the Virtual Cluster. The cluster management node is configured to manage a lifecycle of the object orchestration cluster 101 to which the object orchestration cluster belongs, for example, in a case that an edge service needs to be provided for a new tenant, the new tenant is delivered to one object orchestration cluster 101, and the cluster management node in the object orchestration cluster 101 creates a first API service node and a distributed storage node for the object orchestration cluster 101 to which the tenant belongs. For another example, in a case where a tenant does not need to deploy an application instance, the object orchestration cluster 101 corresponding to the tenant is shutdown.

Embodiment Y2:resource schedulingThe resource scheduling and object synchronization cluster 102 may also be implemented based on K8s, and includes: the resource delivery executor 102 a. The resource delivery executor is used for monitoring whether the tenant creates the application instance through the object orchestration cluster, for example, whether the first API service node creates the application instance may be monitored, or after the first API service node creates the application instance, a notification message may be sent to the resource delivery executor. In addition, the resource delivery executor is further configured to schedule the application instance, and schedule the application instance to the corresponding resource device according to a predetermined scheduling policy, and specifically, when it is monitored that the application instance is created and has not been scheduled to any resource device, the resource delivery executor schedules the application instance to the target resource device based on a routing relationship between the maintained object orchestration cluster and the node management and control cluster. For example, the resource delivery executor monitors that an application instance is created and needs to start 100 Pod to run the application instance, and the resource delivery executor determines, according to load information of each resource device in the edge node, on which resource device on which edge node the 100 Pod is deployed.

Besides the resource delivery executor, the resource scheduling and object synchronization cluster further includes: example synchronizer 102 b. The instance synchronizer may monitor a state of the application instance, and synchronize data related to the application instance to the target node management and control cluster in a case that the application instance is scheduled to the target resource device, so that the target node management and control cluster controls the target resource device to locally deploy the application instance. The target resource device can control the cluster through the node corresponding to the edge node to which the target resource device belongs, the deployment state of the application instance is synchronized to the instance synchronizer, and the instance synchronizer synchronizes the deployment state of the application instance to the corresponding object arrangement cluster 101 so that the object arrangement cluster can be presented to the corresponding tenant.

Further, the resource scheduling and object synchronization cluster includes, in addition to the resource delivery executor and the instance synchronizer: a resource planner 102 c. The resource planner may establish an association relationship between the node management and control cluster and the edge node or a routing relationship between the node management and control cluster and the object orchestration cluster. In an optional embodiment, the resource planner may determine, according to attribute information of a plurality of edge nodes, at least one edge node that each node manages and controls a cluster, and establish an association relationship between the node management and control cluster and the edge node. The attribute information of the edge node includes but is not limited to: the scale attribute refers to the resource amount of the edge node, for example, resources with storage capacity such as a memory and a hard disk, and network resources such as bandwidth. In another optional embodiment, the resource planner may determine, according to edge service requirement information of a tenant corresponding to each object orchestration cluster, at least one node control cluster that is usable by each object orchestration cluster, for example, the edge service requirement information includes an operator, an area location, or a service quality requirement for cloud computing service, and the resource planner may select, according to the edge service requirement information, an edge node that meets the edge service requirement information from a plurality of edge nodes, and use the at least one node control cluster corresponding to the edge node that meets the edge service requirement information as the at least one node control cluster that is usable by each object orchestration cluster. After determining at least one node management cluster usable by each object orchestration cluster, a routing relationship between the object orchestration cluster and the node management cluster may be established.

Embodiment Y3:the node control cluster 103 may also be implemented based on the K8s technology, and each node control cluster 103 includes: a second API service node 103a, as shown in fig. 2. The second API service node may be implemented as an interaction module (API Server) in the K8s architecture. The second API service node may receive data related to the application instance synchronized by the resource scheduling and object synchronization cluster, and send the data related to the application instance to the target resource device, so that the target resource device deploys the application instance locally.

Besides the second API service node, the node management and control cluster further includes: an instance management node 103b deployed on a resource device in each edge node, as shown in fig. 2. The instance management node can maintain the life cycle of the application instance on the resource device to which the instance management node belongs, and report the running state of the corresponding application instance to each object editing cluster. In the process of reporting the running state of the corresponding application instance to each object orchestration cluster, the instance management node provides the running state of the corresponding application instance to the second API service node, the second API service node provides the running state of the corresponding application instance to the instance synchronizer, the instance synchronizer provides the running state of the application instance to the first API service node of the object orchestration cluster corresponding to the node management and control cluster to which the instance synchronizer belongs according to the routing relationship between the node management and control cluster and the object orchestration cluster, and the first API service node presents the running state of the corresponding application instance to the corresponding tenant.

The edge distributed management and control system provided by the embodiment of the application has the following advantages:

1. the resource level of the edge node can be transversely expanded through the horizontal expansion of the node control cluster, and the edge resource management target of managing million edge node and million resource devices is really achieved;

2. the cloud edge only needs to synchronize the application examples and the related data objects thereof, so that on one hand, the data bottleneck limitation of the central cluster can be removed, the resource scheduling and object synchronization cluster only stores the routing relation from the object arrangement cluster to the node control cluster, on the other hand, the data related to the application examples are synchronized to the node control cluster based on the routing relation, the synchronous data volume is small, and the stability and the usability of the edge distributed control system are greatly improved in the cloud edge weak network environment;

3. a single distributed control cluster can control and distribute edge nodes in the whole domain to a large extent;

4. the object arrangement cluster can provide multi-tenant control isolation, and does not take the roles of storage and data synchronization of more application examples and various data objects related to the application examples, and the deployment of the application examples and the various data objects related to the application examples and the reliability of service are ensured by the node control cluster, so that the overall service stability is higher, and the control is more convenient.

Fig. 3 is a schematic flowchart of an application instance deployment method provided in an exemplary embodiment of the present application, where the method is applied to a resource scheduling and object synchronization cluster in an edge distributed management and control system, the resource scheduling and object synchronization cluster is located in a second layer of the distributed management and control cluster, and the distributed management and control cluster further includes: as shown in fig. 3, the method includes:

301. the resource scheduling and object synchronization cluster monitors whether a plurality of object editing clusters execute the creation operation of the application instance or not so as to create the application instance;

302. when it is monitored that an application instance is created, scheduling the application instance to target resource equipment based on a routing relation between the maintained object orchestration cluster and the node management and control cluster;

303. synchronizing data related to the application examples to a target node management and control cluster so that the target node management and control cluster can control target resource equipment to locally deploy the application examples; the target node control cluster is a node control cluster which is responsible for managing the edge nodes to which the target resource equipment belongs.

In an optional embodiment, the method provided in this embodiment further includes: determining at least one edge node which can be managed by each node control cluster according to the attribute information of the edge nodes, and establishing an incidence relation between the node control cluster and the edge nodes; and/or determining at least one node control cluster which can be used by each object arrangement cluster according to the edge service requirement information of the tenant corresponding to each object arrangement cluster, and establishing a routing relation between the object arrangement clusters and the node control clusters.

Fig. 4 is another application example deployment method provided in an exemplary embodiment of the present application, where the method is applied to any node control cluster in an edge distributed control system, where the node control cluster is located at a third layer in the distributed control cluster, and the distributed control cluster further includes: a plurality of object orchestration clusters at a first level and resource scheduling and object synchronization clusters at a second level, the method comprising:

401. receiving data related to an application instance of resource scheduling and object synchronization cluster synchronization, wherein the application instance is created by an object arrangement cluster corresponding to any node control cluster, the application instance needs to be deployed on target resource equipment, and the target resource equipment is determined from edge nodes of any node control cluster responsible for management based on a routing relation between the maintained object arrangement cluster and the node control cluster;

402. and controlling the target resource equipment to locally deploy the application instance according to the data deployment task related to the application instance.

In an optional embodiment, the method provided in this embodiment further includes: and maintaining the life cycle of the application instance, and reporting the running state of the corresponding application instance to each object editing cluster.

According to the application instance deployment method provided by the embodiment of the application instance, the edge nodes are managed by adopting the distributed cluster, in the distributed cluster, the edge management and control are layered from three dimensions of object arrangement, resource scheduling and resource management and control, namely, the object arrangement cluster of the first layer executes the arrangement operation of the application instance for the tenant, tenant isolation can be realized, the resource scheduling and object synchronization cluster of the second layer undertakes the synchronization of the resource scheduling and the data related to the application instance, the deployment of the application instance is completed by the node management and control cluster of the third layer, the availability, stability and convenience of management and control of services can be integrally improved, and real wide-coverage and large-scale tenant cluster management and control services are provided.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of steps 301 to 303 may be device a; for another example, the execution subject of steps 301 and 302 may be device a, and the execution subject of step 303 may be device B; and so on.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 301, 302, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

Fig. 5 is a schematic structural diagram of a resource scheduling and object synchronization cluster according to an exemplary embodiment of the present application. The resource scheduling and object synchronizing cluster is a resource scheduling and object synchronizing cluster in the edge distributed management and control system, the resource scheduling and object synchronizing cluster is located at a second layer of the distributed management and control cluster, and the distributed management and control cluster further comprises: a plurality of object orchestration clusters of the first layer and a plurality of node management and control clusters of the third layer, as shown in fig. 5, the resource scheduling and object synchronization cluster includes: a memory 54 and a processor 55.

A memory 54 for storing computer programs and may be configured to store other various data to support operations on the resource scheduling and object synchronization cluster. Examples of such data include instructions for any application or method operating on the resource scheduling and object synchronization cluster.

The memory 54 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

A processor 55 coupled to the memory 54 for executing computer programs in the memory 54 for: the resource scheduling and object synchronization cluster monitors whether a plurality of object editing clusters execute the creation operation of the application instance or not so as to create the application instance; when it is monitored that an application instance is created, scheduling the application instance to target resource equipment based on a routing relation between the maintained object orchestration cluster and the node management and control cluster; synchronizing data related to the application examples to a target node control cluster so that the target node control cluster controls target resource equipment to locally deploy the application examples; the target node control cluster is a node control cluster which is responsible for managing the edge nodes to which the target resource equipment belongs.

In an alternative embodiment, processor 55 is further configured to: determining at least one edge node which can be managed by each node control cluster according to the attribute information of the edge nodes, and establishing an incidence relation between the node control cluster and the edge nodes; and/or determining at least one node control cluster which can be used by each object arrangement cluster according to the edge service requirement information of the tenant corresponding to each object arrangement cluster, and establishing a routing relation between the object arrangement clusters and the node control clusters.

Further, as shown in fig. 5, the resource scheduling and object synchronization cluster further includes: communication components 56, display 57, power components 58, audio components 59, and the like. Only some of the components are schematically shown in fig. 5, and it is not meant that the resource scheduling and object synchronization cluster includes only the components shown in fig. 5.

Accordingly, the present application also provides a computer readable storage medium storing a computer program, which when executed by a processor causes the processor to implement the steps executed by the method shown in fig. 3.

Embodiments of the present application also provide a computer program product, which includes computer programs/instructions, and when the computer programs/instructions are executed by a processor, the processor is caused to implement the steps executed by the method shown in fig. 3.

Fig. 6 is a schematic structural diagram of a node management and control cluster according to an exemplary embodiment of the present application. The node control cluster is any one node control cluster in the edge distributed control system, the node control cluster is located at the third layer of the distributed control cluster, and the distributed control cluster further includes: a plurality of object orchestration clusters at a first level and resource scheduling and object synchronization clusters at a second level. As shown in fig. 6, the node management cluster includes: a memory 64 and a processor 65.

A memory 64 for storing computer programs and may be configured to store other various data to support operations on the node hosting cluster. Examples of such data include instructions for any application or method operating on the node hosting cluster.

The memory 64 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

A processor 65, coupled to the memory 64, for executing computer programs in the memory 64 for: receiving a data deployment task related to an application instance of resource scheduling and object synchronization cluster synchronization, wherein the application instance is created by an object arrangement cluster corresponding to any node control cluster, the application instance needs to be arranged on target resource equipment, and the target resource equipment is determined from edge nodes which are responsible for management of any node control cluster based on a routing relation between the maintained object arrangement cluster and the node control cluster by the resource scheduling and object synchronization cluster; and controlling the target resource equipment to locally deploy the application instance according to the data related to the application instance.

In an alternative embodiment, the processor 65 is further configured to: and maintaining the life cycle of the application instance, and reporting the running state of the corresponding application instance to each object editing cluster.

Further, as shown in fig. 6, the node managing cluster further includes: communication components 66, display 67, power components 68, audio components 69, and the like. Only some of the components are schematically shown in fig. 6, and it is not meant that the node governing cluster includes only the components shown in fig. 6.

Accordingly, the present application also provides a computer readable storage medium storing a computer program, which when executed by a processor causes the processor to implement the steps that can be performed by the method shown in fig. 4.

Embodiments of the present application also provide a computer program product, which includes computer programs/instructions, and when the computer programs/instructions are executed by a processor, the processor is caused to implement the steps that can be executed by the method shown in fig. 4.

Fig. 7 is a schematic structural diagram of a distributed management and control cluster according to an exemplary embodiment of the present application. As shown in fig. 7, the distributed governing cluster includes: a plurality of object orchestration clusters 71 at a first level, a resource scheduling and object synchronization cluster 72 at a second level, and a plurality of node management and control clusters 73 at a third level.

Each object orchestration cluster 71 is delivered to a tenant, and forms a routing relationship with at least one node management and control cluster, for executing an orchestration operation of an application instance for the tenant to create the application instance;

the resource scheduling and object synchronizing cluster 72 is used for scheduling the application instance to the target resource device based on the maintained routing relationship between the object scheduling cluster and the node control cluster when it is monitored that the application instance is created, and synchronizing data related to the application instance to the target node control cluster, wherein the target node control cluster is a node control cluster responsible for managing the edge node to which the target resource device belongs;

each node management and control cluster 73 is responsible for managing at least one edge node, and is used for controlling the target resource device to locally deploy the application instance according to the data related to the application instance, when the node management and control cluster is taken as a target node.

In this embodiment, the distributed management and control cluster may manage and control other nodes in other application scenarios besides controlling the edge node, which is not limited herein. For details of the distributed regulatory cluster, reference may be made to the foregoing embodiments, and details are not described herein.

The communication components of fig. 5 and 6 described above are configured to facilitate wired or wireless communication between the device in which the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as a WiFi, a 2G, 3G, 4G/LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

The displays in fig. 5 and 6 described above include screens, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

The power supply components of fig. 5 and 6 described above provide power to the various components of the device in which the power supply components are located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

The audio components of fig. 5 and 6 described above may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. An edge distributed management and control system, comprising: a plurality of edge nodes to be managed and a distributed management and control cluster, the distributed management and control cluster comprising: a plurality of object arrangement clusters of a first layer, a resource scheduling and object synchronization cluster of a second layer and a plurality of node control clusters of a third layer;

each object orchestration cluster is delivered to a tenant, and forms a routing relationship with at least one node management and control cluster, so as to execute orchestration operation of an application instance for the tenant to create the application instance;

the resource scheduling and object synchronizing cluster is used for scheduling the application instance to a target resource device based on a routing relation between a maintained object arranging cluster and a node control cluster when it is monitored that the application instance is created, and synchronizing data related to the application instance to the target node control cluster, wherein the target node control cluster is a node control cluster which is responsible for managing an edge node to which the target resource device belongs;

each node management and control cluster is responsible for managing at least one edge node and is used for controlling the target resource device to locally deploy the application instance according to the data related to the application instance under the condition that the node management and control cluster serves as the target node.

2. The system of claim 1, wherein each object orchestration cluster is further configured to: configuring a data object on which the application instance depends; correspondingly, the resource scheduling and object synchronization cluster is specifically configured to: synchronizing the application instance and the data related to the data object depended on by the application instance to a target node management and control cluster; the target node management and control cluster is specifically configured to: and controlling the target resource equipment to locally deploy the application instance and the data objects depended on by the application instance according to the data related to the application instance and the data objects depended on by the application instance.

3. The system of claim 1, wherein each object orchestration cluster is specifically configured to: determining an application instance arrangement requirement corresponding to the tenant according to the edge service requirement information submitted by the tenant and/or the running state of the existing application instance of the tenant, and executing the arrangement operation of the application instance according to the application instance arrangement requirement to create the application instance.

4. The system of claim 3, wherein each object orchestration cluster comprises:

the first API service node is used for responding to edge service requirement information submitted by the tenant and/or determining an application instance arrangement requirement corresponding to the tenant according to the running state of the existing application instance of the tenant, and executing arrangement operation of the application instance according to the application instance arrangement requirement to create the application instance;

and the distributed storage nodes are used for storing the running state of the tenant existing application instance reported by the at least one node control cluster corresponding to the object arrangement cluster.

5. The system of claim 4, wherein each object orchestration cluster further comprises:

and the cluster management node is used for managing the life cycle of the object arrangement cluster to which the cluster management node belongs and creating a first API service node and a distributed storage node for the object arrangement cluster to which the cluster management node belongs.

6. The system of claim 1, wherein the resource scheduling and object synchronization cluster comprises:

the resource delivery executor is used for monitoring whether the tenant creates an application instance through the object arranging cluster, and scheduling the application instance to a target resource device based on the routing relation between the maintained object arranging cluster and the node control cluster under the condition that the tenant monitors that the application instance is created and is not scheduled to any resource device;

the instance synchronizer is used for synchronizing data related to the application instance to the target node management and control cluster under the condition that the application instance is scheduled to the target resource device, so that the target node management and control cluster controls the target resource device to locally generate the application instance, and synchronizing the deployment state of the application instance to the corresponding object orchestration cluster so that the object orchestration cluster presents to the corresponding tenant.

7. The system of claim 6, wherein the resource scheduling and object synchronization cluster further comprises:

the resource planner is used for determining at least one edge node which can be managed by each node control cluster according to the attribute information of the edge nodes and establishing an incidence relation between the node control cluster and the edge nodes; and/or determining at least one node control cluster which can be used by each object arrangement cluster according to the edge service requirement information of the tenant corresponding to each object arrangement cluster, and establishing a routing relation between the object arrangement clusters and the node control clusters.

8. The system according to any one of claims 1-7, wherein each node governing cluster comprises:

the second API service node is used for receiving the data related to the application example of the resource scheduling and object synchronization cluster synchronization, and sending the data related to the application example to the target resource equipment so that the target resource equipment can locally deploy the application example; and

and the instance management node is deployed on the resource equipment in each edge node and used for maintaining the life cycle of the application instance on the resource equipment to which the instance management node belongs and reporting the running state of the corresponding application instance to each object orchestration cluster.

9. An application instance deployment method is applied to a resource scheduling and object synchronization cluster in an edge distributed management and control system, wherein the resource scheduling and object synchronization cluster is located at a second layer of a distributed management and control cluster, and the distributed management and control cluster further includes: a plurality of object orchestration clusters at a first level and a plurality of node governing clusters at a third level, the method comprising:

the resource scheduling and object synchronization cluster monitors whether the object orchestration clusters execute creation operation of the application instances or not so as to create the application instances;

when it is monitored that an application instance is created, scheduling the application instance to target resource equipment based on a routing relation between a maintained object orchestration cluster and a node management and control cluster;

synchronizing data related to the application instance to a target node management and control cluster so that the target node management and control cluster can control the target resource device to locally deploy the application instance; the target node management and control cluster is a node management and control cluster which is responsible for managing the edge node to which the target resource device belongs.

10. An application instance deployment method is applied to any node management and control cluster in an edge distributed management and control system, the node management and control cluster is located at the third layer of the distributed management and control cluster, and the distributed management and control cluster further includes: a plurality of object orchestration clusters at a first layer and resource scheduling and object synchronization clusters at a second layer, the method comprising:

receiving data related to the application instance of the resource scheduling and object synchronization cluster synchronization, wherein the application instance is created by an object orchestration cluster corresponding to any one node management and control cluster, the application instance needs to be deployed on a target resource device, and the target resource device is determined by the resource scheduling and object synchronization cluster from edge nodes which are responsible for management of any one node management and control cluster based on the maintained routing relationship between the object orchestration cluster and the node management and control cluster;

and controlling the target resource equipment to locally deploy the application instance according to the data related to the application instance.

11. A resource scheduling and object synchronization cluster, comprising: a memory for storing a computer program and a processor coupled with the memory for executing the computer program for implementing the steps of the method of claim 9.

12. A node-managed cluster, comprising: a memory for storing a computer program and a processor coupled with the memory for executing the computer program for implementing the steps in the method of claim 10.

13. A distributed management and control cluster, comprising: a plurality of object arrangement clusters of a first layer, a resource scheduling and object synchronization cluster of a second layer and a plurality of node control clusters of a third layer;

the resource scheduling and object synchronizing cluster is used for scheduling the application instance to a target resource device based on a routing relation between a maintained object arranging cluster and a node control cluster when it is monitored that the application instance is created, and synchronizing data related to the application instance to the target node control cluster, wherein the target node control cluster is a node control cluster responsible for managing an edge node to which the target resource device belongs;

14. A computer storage medium having a computer program stored thereon, which, when executed by a processor, causes the processor to carry out the steps of the method of claim 9 or 10.