CN115361388B - Resource scheduling method and device in edge cloud computing system - Google Patents

Resource scheduling method and device in edge cloud computing system Download PDF

Info

Publication number
CN115361388B
CN115361388B CN202211288350.3A CN202211288350A CN115361388B CN 115361388 B CN115361388 B CN 115361388B CN 202211288350 A CN202211288350 A CN 202211288350A CN 115361388 B CN115361388 B CN 115361388B
Authority
CN
China
Prior art keywords
edge cloud
network communication
cloud node
target
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202211288350.3A
Other languages
Chinese (zh)
Other versions
CN115361388A (en
Inventor
熊鹰
任庚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202211288350.3A priority Critical patent/CN115361388B/en
Publication of CN115361388A publication Critical patent/CN115361388A/en
Application granted granted Critical
Publication of CN115361388B publication Critical patent/CN115361388B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

One or more embodiments of the present specification provide a method and an apparatus for resource scheduling in an edge cloud computing system, where the edge cloud computing system includes a central management and control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node; the method is applied to central management and control equipment and comprises the following steps: acquiring a calculation instance creation requirement submitted by a tenant; in response to a computing instance creation requirement, determining a target edge cloud node meeting the computing instance creation requirement from at least one edge cloud node; determining a target network communication channel for carrying out network communication with a target edge cloud node from multiple types of network communication channels; and performing resource scheduling on the resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node. The present description may enable an edge cloud computing system to provide cloud computing services based on multiple types of network architectures.

Description

Resource scheduling method and device in edge cloud computing system
Technical Field
One or more embodiments of the present disclosure relate to the field of cloud computing technologies, and in particular, to a method and an apparatus for resource scheduling in an edge cloud computing system.
Background
Cloud computing is a concept proposed based on centralized resource management. With the arrival of the age of 5G and the internet of things and the gradual increase of cloud computing applications, the requirements of a terminal on the performances of time delay, bandwidth and the like of cloud resources are higher and higher, and a centralized cloud computing system cannot meet the increasingly higher cloud resource requirements of the terminal. Aiming at the problem, the central control equipment and the edge cloud nodes can be combined, under the control of the central control equipment, cloud computing is placed in the edge cloud nodes closer to the terminal for processing, so that cloud computing services are provided for tenants by means of resources in the edge cloud nodes, and the cloud resource requirements of the terminal on large connection, low time delay and large bandwidth can be met.
However, the current edge cloud computing system is generally limited by a network architecture, and cannot provide cloud computing services based on multiple network architectures for tenants, which affects user experience of the tenants when using the cloud computing services.
Disclosure of Invention
One or more embodiments of the present disclosure provide the following:
the present specification provides a resource scheduling method in an edge cloud computing system, where the edge cloud computing system includes a central management and control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node; the method is applied to the central management and control equipment and comprises the following steps:
acquiring a calculation instance creation requirement submitted by a tenant;
in response to the computing instance creation requirement, determining a target edge cloud node satisfying the computing instance creation requirement from the at least one edge cloud node;
determining a target network communication channel for performing network communication with the target edge cloud node from the multiple types of network communication channels;
and performing resource scheduling on the resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node.
The present specification further provides a resource scheduling method in an edge cloud computing system, where the edge cloud computing system includes a central management and control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node; the method is applied to any one target edge cloud node;
the target edge cloud node is an edge cloud node which is determined by the central management and control equipment from the at least one edge cloud node and meets the computing instance creation requirement in response to the computing instance creation requirement submitted by a tenant;
the method comprises the following steps:
based on resource scheduling of resources carried by the target edge cloud node by the central control equipment through a target network communication channel, creating a computing instance for the tenant on the target edge cloud node;
the target network communication channel is a network communication channel which is determined by the central management and control equipment from the multiple types of network communication channels and is used for carrying out network communication with the target edge cloud node.
The present specification also provides a resource scheduling apparatus in an edge cloud computing system, where the edge cloud computing system includes a central control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node; the device is applied to the central management and control equipment and comprises:
the acquisition module is used for acquiring the calculation example creation requirement submitted by a tenant;
a node determination module, configured to determine, in response to the computing instance creation requirement, a target edge cloud node that meets the computing instance creation requirement from the at least one edge cloud node;
the channel determining module is used for determining a target network communication channel for carrying out network communication with the target edge cloud node from the multiple types of network communication channels;
and the scheduling module is used for performing resource scheduling on the resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node.
The present specification also provides a resource scheduling apparatus in an edge cloud computing system, where the edge cloud computing system includes a central control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node; the device is applied to any one target edge cloud node;
the target edge cloud node responds to a computing instance creation requirement submitted by a tenant for the central control equipment, and determines an edge cloud node meeting the computing instance creation requirement from the at least one edge cloud node;
the device comprises:
the creation module is used for scheduling resources carried by the target edge cloud node through a target network communication channel based on the central management and control equipment, and creating a computing instance for the tenant on the target edge cloud node;
the target network communication channel is a network communication channel which is determined by the central management and control equipment from the multiple types of network communication channels and is used for carrying out network communication with the target edge cloud node.
The present specification also provides an edge cloud computing system comprising: the system comprises a central control device, a cooperative network and at least one edge cloud node;
the cooperative network comprises a plurality of types of network communication channels established between the central management and control equipment and each edge cloud node;
the center management and control equipment and the at least one edge cloud node perform the following interaction:
the central management and control equipment acquires the calculation instance creation requirement submitted by a tenant;
the central management and control equipment responds to the computing instance creation requirement, and determines a target edge cloud node meeting the computing instance creation requirement from the at least one edge cloud node;
the central control equipment determines a target network communication channel for carrying out network communication with the target edge cloud node from the multiple types of network communication channels;
and the central control equipment performs resource scheduling on the resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node.
The present specification also provides an electronic device comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the steps of the method as described in any one of the above by executing the executable instructions.
The present specification also provides a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of the preceding claims.
In the foregoing technical solution, for an edge cloud computing system including a center management and control device and at least one edge cloud node, multiple types of network communication channels may be established between the center management and control device and each edge cloud node, so that when a tenant uses a cloud computing service provided by the edge cloud computing system, the center management and control device may determine a suitable target edge cloud node from the at least one edge cloud node according to an actual situation, determine a suitable target network communication channel from the multiple types of network communication channels established between the center management and control device and the target edge cloud node, and interact through the target network communication channel between the center management and control device and the target edge cloud node, so as to provide a cloud computing service for the tenant.
By adopting the above mode, in the edge cloud computing system, various types of network communication channels are established between the center control device and the edge cloud nodes, which is equivalent to that the center control device and the edge cloud nodes form various types of network architectures, so that the limitation of the edge cloud computing system on the network architecture can be removed, and the edge cloud computing system can provide cloud computing services of various modes for tenants based on various types of network architectures; furthermore, the edge cloud computing system can provide cloud computing services of multiple modes for the tenant, so that the tenant can select the mode when using the cloud computing services provided by the edge cloud computing system, and corresponding user experience is improved.
Drawings
Fig. 1 is a system architecture diagram of an edge cloud computing system according to an exemplary embodiment of the present disclosure.
Fig. 2 is a system architecture diagram of another edge cloud computing system shown in an exemplary embodiment of the present specification.
Fig. 3 is a flowchart illustrating a resource scheduling method in an edge cloud computing system according to an exemplary embodiment of the present disclosure.
Fig. 4 is a flowchart illustrating a resource scheduling method in another edge cloud computing system according to an exemplary embodiment of the present disclosure.
Fig. 5 is a schematic diagram of a network architecture of cloud edge collaboration, according to an exemplary embodiment of the present disclosure.
Fig. 6 is a flowchart illustrating a resource scheduling method in another edge cloud computing system according to an exemplary embodiment of the present disclosure.
Fig. 7 is a flowchart illustrating a resource scheduling method in another edge cloud computing system according to an exemplary embodiment of the present disclosure.
Fig. 8 is a schematic diagram of a network architecture of cloud edge collaboration and edge collaboration, according to an exemplary embodiment of the present specification.
Fig. 9 is a diagram illustrating a hardware structure of an apparatus according to an exemplary embodiment of the present disclosure.
Fig. 10 is a block diagram of a resource scheduling apparatus in an edge cloud computing system according to an exemplary embodiment of the present specification.
Fig. 11 is a block diagram illustrating a resource scheduling apparatus in another edge cloud computing system according to an exemplary embodiment of the present specification.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the methods may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
The edge cloud is a cloud computing platform constructed on an edge infrastructure based on the core of the cloud computing technology and the capability of edge computing.
The edge cloud is a relative concept and can be distinguished from the central cloud or a traditional cloud computing platform. In practical applications, a central cloud or a traditional cloud computing platform may include a data center with large-scale and centralized resources; the network coverage of the edge cloud nodes is wider, the distance from the edge cloud nodes to the terminal is closer, the number of the edge cloud nodes is larger, and the resource scale of a single edge cloud node is smaller.
Referring to fig. 1, fig. 1 is a system architecture diagram of an edge cloud computing system according to an exemplary embodiment of the present disclosure.
In the edge cloud computing system shown in fig. 1, a central management and control device 101, an edge Yun Jiedian, an edge cloud node 103, and an edge cloud node 104 may be included; the central management and control device 101 may be interconnected with the edge cloud node 102, the edge cloud node 103, and the edge cloud node 104, respectively.
It should be noted that fig. 1 only shows 3 edge cloud nodes by way of example, which does not represent that the present specification particularly limits this; in practical applications, the edge cloud computing system shown in fig. 1 may include at least one edge cloud node interconnected with the central management apparatus 101.
The central control apparatus 101 may be deployed in one or more cloud computing data centers, or may be deployed in one or more conventional data centers, which is not limited in this specification.
Each of the at least one edge cloud node may comprise a series of edge infrastructures; the edge infrastructure may specifically include, but is not limited to: a distributed data center, a wireless computer room or a cluster, a communication network of an operator, a core network device, a base station, an edge gateway, a home gateway, an edge device such as a computing device or a storage device, a corresponding network environment, and the like. It should be noted that the locations of different edge cloud nodes, the available cloud computing power, and the included edge infrastructure may be the same or different, and this specification does not limit this specifically.
The terminal shown in fig. 1 may include a demand side of a cloud computing service. For example, the terminal may comprise a user terminal in the internet or internet of things.
In the edge cloud computing system shown in fig. 1, a center cloud corresponding to the center management and control device 101, an edge cloud corresponding to at least one edge cloud node, and a terminal may form a network architecture of "cloud edge-end three-body cooperation". The central management and control device 101 may use each edge cloud node (e.g., edge Yun Jiedian, edge cloud node 103, or edge cloud node 104) as a management and control object, and perform unified management and control in terms of resource scheduling, mirror image management, instance management and control, operation and maintenance, network, security, and the like, so as to place the cloud computing service into each edge cloud node for processing, and provide the cloud computing service for a user (which may also be referred to as a tenant) by using various resources hosted by the edge cloud node. Because the edge cloud nodes are closer to the terminal, the response time delay of the cloud computing service can be reduced, the pressure of a central cloud corresponding to the edge cloud nodes or a traditional cloud computing platform is reduced, the bandwidth cost is reduced, and the resource requirements of the terminal on large connection, low time delay and large bandwidth in a cloud computing scene are met.
In practical application, the edge cloud node can create a corresponding instance according to the mirror image, and provide various cloud computing services to the outside through the instance. The mirror image is a basic file required by creating an instance in an edge cloud node; for example, the image may be an image file of an operating system, an application, or an operation configuration required for providing a cloud computing service for a tenant, and specifically may be a file that meets the computing deployment requirement of an edge cloud node and is made according to a certain format according to a specific series of files. In addition, the image may be a virtual machine image file, a container image file, or various types of application packaging files, and the image may be related to virtualization technologies that the cloud computing service needs to use, which is not particularly limited in this specification. Corresponding to mirroring, the implementation of an instance may be a virtual machine, a container, an application, or the like.
Generally, the central management and control device 101 may perform resource scheduling on at least one edge cloud node, and may also perform management and distribution of a mirror image for at least one edge cloud node; of course, the resource scheduling may be performed on at least one edge cloud node, and the mirroring may be provided for at least one edge cloud node.
Specifically, the center managing device 101 has, but is not limited to, the following functions: the edge cloud nodes can be scheduled according to the specification of the cloud computing service, the region where the cloud computing service needs to be deployed, the distribution of an operator network, network delay, load conditions, bandwidth cost, the type of required resources and/or the performance requirements of resource equipment and the like; the mirror image required by the cloud computing service can be obtained, and the mirror image is provided for the edge cloud node to be configured and installed so that the edge cloud node can create a corresponding instance to provide the cloud computing service; operation and maintenance management and control can be performed on the edge cloud nodes, including but not limited to: the states, resource usage and/or infrastructure conditions and the like of applications, virtualized components and instances in the edge cloud nodes are managed and controlled, and remote operation and maintenance, log management and the like are achieved.
In addition to the above functions, the central managing device 101 may also have other functions, such as: the safety guarantee function relates to the safety of the central control equipment, the link safety between the central control equipment and the edge cloud nodes and between different edge cloud nodes and/or the safety of the edge cloud nodes; and the system is responsible for maintaining networking information of the edge cloud computing system and the like.
For an edge cloud computing system in the related art, a central management and control device and at least one edge cloud node need to be both in the internet or in the same local area network, so as to ensure that the central management and control device is interconnected with each edge cloud node, that is, the central management and control device and each edge cloud node can interact with each other.
However, the limitations of the edge cloud computing system in terms of network architecture may also limit the mode of cloud computing services provided by the edge cloud computing system for tenants. For example, if a central management and control device and at least one edge cloud node in an edge cloud computing system are both in the internet, the interaction between the central management and control device and each edge cloud node is performed through the internet, and the edge cloud computing system can only provide a public cloud mode for a tenant, that is, data related to the tenant is public to the outside, so that privacy and security of the data related to the tenant are difficult to guarantee. For another example, assuming that a central management and control device in an edge cloud computing system and at least one edge cloud node are in the same local area network, since the interaction between the central management and control device and the edge cloud node is performed through the local area network, the edge cloud computing system can only provide a private cloud mode for a tenant, that is, data related to the tenant is not exposed to the outside, although privacy and security of the data related to the tenant can be guaranteed, the network architecture is more difficult to implement specifically.
In addition, because the edge cloud computing system can only provide cloud computing services of a single mode for tenants, the tenant cannot select the mode when using the cloud computing services provided by the edge cloud computing system, and user experience of the tenant when using the cloud computing services provided by the edge cloud computing system is affected.
The present specification provides a technical solution for resource scheduling in an edge cloud computing system, where in the technical solution, for an edge cloud computing system including a center management and control device and at least one edge cloud node, multiple types of network communication channels may be established between the center management and control device and each edge cloud node, so that when a tenant uses a cloud computing service provided by the edge cloud computing system, the center management and control device may determine a suitable target edge cloud node from the at least one edge cloud node according to an actual situation, determine a suitable target network communication channel from the multiple types of network communication channels established between the center management and control device and the target edge cloud node, and subsequently interact with the target edge cloud node through the target network communication channel to provide the cloud computing service for the tenant.
By adopting the above mode, in the edge cloud computing system, various types of network communication channels are established between the center control device and the edge cloud nodes, which is equivalent to that the center control device and the edge cloud nodes form various types of network architectures, so that the limitation of the edge cloud computing system on the network architecture can be removed, and the edge cloud computing system can provide cloud computing services of various modes for tenants based on various types of network architectures; furthermore, the edge cloud computing system can provide cloud computing services of multiple modes for the tenant, so that the tenant can select the mode when using the cloud computing services provided by the edge cloud computing system, and corresponding user experience is improved.
Referring to fig. 2, fig. 2 is a system architecture diagram of another edge cloud computing system according to an exemplary embodiment of the present disclosure.
In the edge cloud computing system shown in fig. 2, a central management and control device 201, an edge Yun Jiedian, an edge cloud node 203, and an edge cloud node 204 may be included; central management and control device 201 may be interconnected with edge cloud node 202, edge cloud node 203, and edge cloud node 204, respectively. That is, in the edge cloud computing system, a central management and control device and at least one edge cloud node may be included; the central management and control equipment can be interconnected with each edge cloud node.
In this embodiment, a network communication channel may be established between the central control device and each edge cloud node, so that the central control device and each edge cloud node are interconnected through the network communication channel, that is, the central control device and each edge cloud node interact through the network communication channel.
It should be noted that multiple types of network communication channels may be established between the central management and control device and each edge cloud node. For any one edge cloud node, the center management and control device and the edge cloud node may interact through any type of network communication channel established between the center management and control device and the edge cloud node.
In some embodiments, the plurality of types of network communication channels established between the central management and control device and the respective edge cloud nodes may include an internet communication channel, a wide area network communication channel, a dedicated network communication channel, and the like. The dedicated network communication channel may include a network communication channel for implementing interconnection of different devices in the same local area network, and may also include a network communication channel (for example, a network tunnel) for implementing interconnection of different devices in different local area networks, which is not limited in this specification.
In the foregoing case, the central control device and the at least one edge cloud node may implement cooperation between a central cloud corresponding to the central control device and an edge cloud corresponding to the at least one edge cloud node, that is, "cloud-edge cooperation", through multiple types of network communication channels established between the central control device and each edge cloud node.
Further, in some embodiments, multiple types of network communication channels may also be established between different edge cloud nodes. For any two edge cloud nodes, the two edge cloud nodes can interact with each other through any type of network communication channel established between the two edge cloud nodes.
Similarly, the multiple types of network communication channels established between different edge cloud nodes may also include an internet communication channel, a wide area network communication channel, a dedicated network communication channel, and the like.
In this case, the at least one edge cloud node may implement coordination between edge clouds corresponding to the at least one edge cloud node, that is, "edge-edge coordination" through multiple types of network communication channels established between different edge cloud nodes.
In the edge cloud computing system shown in fig. 2, multiple types of network communication channels established between the central management device and each edge cloud node, and multiple types of network communication channels established between different edge cloud nodes, may be collectively referred to as a cooperative network 205.
Referring to fig. 3 in conjunction with the edge cloud computing system shown in fig. 2, fig. 3 is a flowchart illustrating a resource scheduling method in the edge cloud computing system according to an exemplary embodiment of the present disclosure.
As shown in fig. 2, in this embodiment, the edge cloud computing system may include a central management and control device and at least one edge cloud node; various types of network communication channels can be established between the central management and control equipment and each edge cloud node. The resource scheduling method in the edge cloud computing system can be applied to a central control device in the edge cloud computing system; the method may comprise the steps of:
step 301: and acquiring the calculation instance creation requirement submitted by the tenant.
In this embodiment, when using the cloud computing service provided by the edge cloud computing system, a tenant may first submit a computing instance creation requirement to the central management and control device. Wherein, the computing instance creating requirement can be information for describing the computing instance which the tenant needs to create.
For example, the central management and control device may provide a demand submission entrance to the outside; through the requirement submitting inlet, the tenant submits various types of requirements including a computing instance creating requirement to the central management and control equipment. Wherein the requirement submitting portal can be a web page, an application page, a command window, or the like.
Accordingly, the central management and control device can acquire the calculation instance creation requirement submitted by the tenant.
Step 302: in response to the computing instance creation requirement, determining a target edge cloud node from the at least one edge cloud node that satisfies the computing instance creation requirement.
In this embodiment, the central management and control device may determine, in response to a computing instance creation requirement submitted by a tenant, an edge Yun Jiedian (hereinafter referred to as a target edge cloud node) that meets the computing instance creation requirement from the at least one edge cloud node.
For example, the computing instance creation requirement may include a node identifier of an edge cloud node specified by a tenant, so that the central management and control device may determine the edge cloud node corresponding to the node identifier in the computing instance creation requirement as the target cloud node.
As another example, the computing instance creation requirements described above may include edge cloud node selection parameters. The edge cloud node selection parameter refers to a parameter required for determining the target edge cloud node from the at least one edge cloud node, so that the central management and control device can determine the target edge cloud node from the at least one edge cloud node according to the edge cloud node selection parameter in the computing instance creation requirement. In practical applications, the edge cloud node selection parameter may include QoS requirements of a scheduling domain and/or a cloud computing service; the QoS requirements of the cloud computing service may include requirements of the cloud computing service on network delay, load conditions, and/or bandwidth cost; in this case, the central management and control device may select, according to the QoS requirement of the scheduling domain and/or the cloud computing service, an edge cloud node that can meet the QoS requirement of the scheduling domain and/or the cloud computing service from the QoS requirement of the scheduling domain and/or the cloud computing service, in combination with the geographic location and the resource remaining amount of the at least one edge cloud node, as the target edge cloud node.
Step 303: and determining a target network communication channel for carrying out network communication with the target edge cloud node from the multiple types of network communication channels.
In this embodiment, when the center management and control device determines the target edge cloud node, a network communication channel (hereinafter referred to as a target network communication channel) for performing network communication with the target edge cloud node may be determined from multiple types of network communication channels established between the center management and control device and the target edge cloud node.
Step 304: and performing resource scheduling on the resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node.
In this embodiment, when the target edge cloud node and the target network communication channel are determined, the central management and control device may perform resource scheduling on a resource carried by the target edge cloud node through the target network communication channel.
Correspondingly, the target edge cloud node may create a computing instance for the tenant on the target edge cloud node under resource scheduling performed by the central control device on the resources hosted by the target edge cloud node.
Referring to fig. 4 in conjunction with the edge cloud computing system shown in fig. 2, fig. 4 is a flowchart of another resource scheduling method in the edge cloud computing system shown in an exemplary embodiment of the present specification.
As shown in fig. 2, the edge cloud computing system may include a central management and control device and at least one edge cloud node; various types of network communication channels can be established between the central management and control equipment and each edge cloud node. The resource scheduling method in the edge cloud computing system can be applied to any target edge cloud node in the edge cloud computing system.
The target edge cloud node is an edge cloud node which is determined by the central management and control device in response to a computing instance creation requirement submitted by a tenant and meets the computing instance creation requirement from the at least one edge cloud node.
The resource scheduling method in the edge cloud computing system may include the following steps:
step 401: based on resource scheduling of resources carried by the target edge cloud node by the central control equipment through a target network communication channel, creating a computing instance for the tenant on the target edge cloud node; the target network communication channel is a network communication channel which is determined by the central management and control device from the multiple types of network communication channels and is used for carrying out network communication with the target edge cloud node.
For specific implementation of the embodiment shown in fig. 4, reference may be made to the embodiment shown in fig. 3, and details of this description are not repeated here.
In the embodiments shown in fig. 3 and fig. 4, for an edge cloud computing system including a center management and control device and at least one edge cloud node, multiple types of network communication channels may be established between the center management and control device and each edge cloud node, so that when a tenant uses a cloud computing service provided by the edge cloud computing system, the center management and control device may determine, according to actual conditions, an appropriate target edge cloud node from the at least one edge cloud node, determine an appropriate target network communication channel from the multiple types of network communication channels established between the center management and control device and the target edge cloud node, and subsequently, the center management and control device and the target edge cloud node may interact through the target network communication channel to provide the cloud computing service for the tenant.
By adopting the above mode, in the edge cloud computing system, various types of network communication channels are established between the center control device and the edge cloud nodes, which is equivalent to that the center control device and the edge cloud nodes form various types of network architectures, so that the limitation of the edge cloud computing system on the network architecture can be removed, and the edge cloud computing system can provide cloud computing services of various modes for tenants based on various types of network architectures; furthermore, the edge cloud computing system can provide cloud computing services in multiple modes for the tenant, so that the tenant can select the mode when using the cloud computing services provided by the edge cloud computing system, and corresponding user experience is improved.
In the embodiments shown in fig. 3 and fig. 4, the central management and control device and the at least one edge cloud node may perform resource scheduling through multiple types of network communication channels established between the central management and control device and each edge cloud node. Thus, the embodiments shown in fig. 3 and 4 pertain to a "cloud-edge collaborative" network architecture.
The network architecture of the "cloud edge coordination" will be described below with reference to fig. 5.
As shown in fig. 5, in an edge cloud computing system including a central management and control device and at least one edge cloud node, the central management and control device may acquire a computing instance creation requirement submitted by a tenant, and determine, in response to the computing instance creation requirement, a target edge cloud node that meets the computing instance creation requirement from the at least one edge cloud node. Subsequently, the central control device may perform resource scheduling on the resource carried by the target edge cloud node through the cooperative network, so that the target edge cloud node may create a computing instance for the tenant on the target edge cloud node under the resource scheduling performed by the central control device on the resource carried by the target edge cloud node.
Specifically, the cooperative network includes multiple types of network communication channels established between the central control device and the target edge cloud node, and when the central control device performs resource scheduling on the resource carried by the target edge cloud node through the cooperative network, the central control device may determine, from the multiple types of network communication channels, a target network communication channel for performing network communication with the target edge cloud node, and perform resource scheduling on the resource carried by the target edge cloud node through the target network communication channel.
In some embodiments, the computing instance may include any one or a combination of the following: container instance, virtual machine instance.
Further, in some embodiments, the container instance may comprise a container instance created on a virtual machine, and/or a bare metal container instance created on a physical machine.
In some embodiments, the computing instance creation requirement may include requirement information corresponding to the computing instance to be created. In this case, when the target edge cloud node creates a computing instance for the tenant on the target edge cloud node, a computing instance that meets the requirement information may be specifically created for the tenant on the target edge cloud node.
In practical applications, the requirement information refers to information required for creating a computing instance on the target edge cloud node, and may include: resource type, resource quantity and/or performance requirements on edge cloud nodes, etc.
For example, the central management and control device may generate rules and policies for creating a computing instance according to the requirement information in the computing instance creation requirement, and issue the rules and policies for creating the computing instance to the target edge cloud node through the target network communication channel, so that the target edge cloud node may create a computing instance for the tenant on the target edge cloud node according to the rules and policies for creating the computing instance; at this time, the created calculation instance is the calculation instance satisfying the demand information.
In some embodiments, the resources hosted by the respective edge cloud nodes may include heterogeneous resources composed of multiple types of resources. The heterogeneous resources may include heterogeneous computing resources, heterogeneous storage resources, and/or heterogeneous network resources, among others.
Further, in some embodiments, the heterogeneous computing resources may include x86 computing resources, ARM computing resources, and/or GPU computing resources. The heterogeneous storage resources may include block storage resources, file storage resources, and/or object storage resources. The heterogeneous network resources may include network resources obtained by performing hybrid networking on any one or more of the following network resources: the network resource comprises underlay network resources, overlay network resources and network resources obtained by performing hybrid networking on the basis of at least one network component. The specific type of the network component may not be particularly limited in this specification.
It should be noted that, for the above heterogeneous resources, resource abstraction may be performed on various types of resources according to a unified standard, so as to provide unified and standardized heterogeneous resources to the outside, and a tenant is convenient to determine the requirements of the tenant on various types of resources.
In some embodiments, a tenant may specify a target network communication channel used by the central control device to interact with the target edge cloud node.
Specifically, the computing instance creation requirement may further include a type identifier corresponding to a specified network communication channel, in multiple types of network communication channels established between the central management and control device and the target edge cloud node by the tenant. In this case, the central managing and controlling device may determine, as the target network communication channel, a network communication channel corresponding to the type identifier among the plurality of types of network communication channels.
Or, in some embodiments, the central management and control device may select a target network communication channel used by the central management and control device to interact with the target edge cloud node by itself.
Specifically, the central management and control device may determine a type of a network communication channel used for network communication between an edge cloud node accessed by a tenant and the central management and control device, and determine, as the target network communication channel, a network communication channel belonging to the type among multiple types of network communication channels established between the central management and control device and the target edge cloud node. The edge cloud node accessed by the tenant may be the target edge cloud node, or may be another edge cloud node except the target edge cloud node, which is not particularly limited in this specification.
In some embodiments, in the case that the target edge cloud node creates a computing instance for the tenant on the target edge cloud node, a service instance corresponding to the computing instance may be further created based on a service image provided by the tenant.
Specifically, in some embodiments, the service instance may include an application instance, and the service image may include an application package file; in this case, the target edge cloud node may obtain an application package file provided by the tenant, and deploy the application package file to a computing instance created for the tenant on the target edge cloud node to create an application instance corresponding to the computing instance; at this time, the application instance is the service instance.
In the above case, the target edge cloud node may implement autonomy for a service instance further created based on the created compute instance. That is, the creation and execution of the service instance can be completed only by the target edge cloud node without the participation of the above central control device. Therefore, even if the network communication between the target edge cloud node and the central control device fluctuates and is disconnected in a short time, the target edge cloud node can work normally due to the autonomous capability of the target edge cloud node.
In some embodiments, the center management and control device may periodically send, to the target edge cloud node, check information of data to be synchronized (which may include service data and configuration data; configuration data may include system configuration data, and the like), so that the target edge cloud node device may determine, based on the check information, whether data stored in the target edge cloud node is consistent with corresponding data stored in the center management and control device, and if the data stored in the target edge cloud node is inconsistent with the corresponding data stored in the center management and control device, the target edge cloud node may return, to the center management and control device, information indicating that the data is inconsistent or a data synchronization request, so as to trigger the center management and control device to synchronize the corresponding data stored in the center management and control device to the target edge cloud node.
In some embodiments, the target edge cloud node may send a data synchronization request to the central management and control device when detecting that an abnormal condition (for example, data loss, generation of a large amount of abnormal data due to abnormal service, or the like) occurs in the data stored in the target edge cloud node, so as to trigger the central management and control device to synchronize corresponding data stored in the central management and control device to the target edge cloud node.
On the basis of the embodiment shown in fig. 3, referring to fig. 6, fig. 6 is a flowchart of a resource scheduling method in another edge cloud computing system shown in an exemplary embodiment of this specification.
In this embodiment, multiple types of network communication channels may also be established between different edge cloud nodes in the edge cloud computing system. The resource scheduling method in the edge cloud computing system may include the following steps:
step 601: acquiring a service data synchronization requirement which is submitted by the tenant and corresponds to the service instance; the service data synchronization requirement comprises a data identifier of service data to be synchronized.
In this embodiment, the central management and control device may further acquire a service data synchronization requirement corresponding to the service instance, which is submitted by the tenant. The service data synchronization requirement may include a data identifier of service data to be synchronized.
It should be noted that the service instance may be an instance created based on the computing instance and related to a target service deployed on the target edge cloud node; the target service may be a tenant-specified service.
Step 602: and responding to the service data synchronization requirement, and determining other edge cloud nodes which meet the service data synchronization requirement and serve as synchronous data receiving ends from the at least one edge cloud node.
In this embodiment, the central management and control device may determine, in response to a service data synchronization requirement submitted by a tenant, another edge cloud node serving as a synchronization data receiving end, which meets the service data synchronization requirement, from the at least one edge cloud node.
It should be noted that, as for the manner of determining the other edge cloud nodes, reference may be made to the manner of determining the target edge cloud node, which is not described herein again.
Step 603: and determining a network communication channel for performing network communication with the target edge cloud node from the multiple types of network communication channels, issuing the data identifier and the node identifiers of the other edge cloud nodes to the target edge cloud node through the network communication channel, so that the target edge cloud node determines a network communication channel for performing network communication with the other edge cloud nodes from the multiple types of network communication channels, and synchronizing the service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel.
In this embodiment, when determining the other edge cloud nodes, the central control device may determine, from among multiple types of network communication channels established between the central control device and the target edge cloud node, a network communication channel for performing network communication with the target edge cloud node, and issue the data identifier and the node identifiers of the other edge cloud nodes to the target edge cloud node through the network communication channel.
Correspondingly, when the target edge cloud node receives the data identifier and the node identifier, the other edge cloud nodes corresponding to the node identifier may be determined, then a network communication channel for performing network communication with the other edge cloud nodes is determined from multiple types of network communication channels established between the target edge cloud node and the other edge cloud nodes, and the service data corresponding to the data identifier is synchronized to the other edge cloud nodes through the network communication channel.
On the basis of the embodiment shown in fig. 4, referring to fig. 7, fig. 7 is a flowchart of a resource scheduling method in another edge cloud computing system shown in an exemplary embodiment of this specification.
In this embodiment, multiple types of network communication channels may also be established between different edge cloud nodes in the edge cloud computing system. The resource scheduling method in the edge cloud computing system may include the following steps:
step 701: and receiving the network communication channel which is determined by the central control equipment and is used for carrying out network communication with the target edge cloud node, the data identification of the service data to be synchronized and the node identification of other edge cloud nodes serving as a synchronous data receiving end from the various network communication channels.
Step 702: determining a network communication channel for performing network communication with the other edge cloud nodes corresponding to the node identifier from the multiple types of network communication channels, and synchronizing service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel; the data identification is a data identification included in service data synchronization requirements which are submitted by the tenant and correspond to the service instances; and the other edge cloud nodes are edge cloud nodes which are determined by the central management and control equipment from the at least one edge cloud node and meet the service data synchronization requirement in response to the service data synchronization requirement.
For specific implementation of the embodiment shown in fig. 7, reference may be made to the embodiment shown in fig. 6, and details of this description are not repeated here.
In the embodiments shown in fig. 6 and 7, for an edge cloud computing system including a center management and control device and at least one edge cloud node, not only multiple types of network communication channels may be established between the center management and control device and each edge cloud node, but also multiple types of network communication channels may be established between different edge cloud nodes, so that the center management and control device may determine other edge cloud nodes serving as synchronization data receiving ends from the at least one edge cloud node, and determine an appropriate network communication channel from the multiple types of network communication channels established between the center management and control device and a target edge cloud node serving as synchronization data sending ends, so as to send data identifiers of service data to be synchronized and node identifiers of the other edge cloud nodes to the target edge cloud node through the network communication channel, and the target edge cloud node may subsequently determine an appropriate network communication channel from the multiple types of network communication channels established between the target edge cloud node and the other edge cloud nodes, and perform service data synchronization through the network communication channel.
By adopting the above manner, in the edge cloud computing system, the center management and control device and the edge cloud nodes can realize service data synchronization based on various network architectures through various types of network communication channels established therebetween, so as to meet data synchronization requirements of tenants when using cloud computing services provided by the edge cloud computing system (for example, the edge cloud nodes located at different geographic positions need to keep data synchronization).
In the embodiments shown in fig. 6 and 7, the central management and control device and the at least one edge cloud node may perform resource scheduling and service data synchronization through multiple types of network communication channels established between the central management and control device and each edge cloud node, and multiple types of network communication channels established between different edge cloud nodes. Thus, the embodiments shown in fig. 6 and 7 pertain to a "cloud edge collaboration + edge collaboration" network architecture.
The network architecture of "cloud edge collaboration + edge collaboration" is described below with reference to fig. 8.
As shown in fig. 8, in an edge cloud computing system including a central management and control device and at least one edge cloud node, the central management and control device may acquire, in addition to a computing instance creation requirement submitted by a tenant, a service data synchronization requirement submitted by the tenant and corresponding to a service instance further created based on the created computing instance. The service data synchronization requirement may include a data identifier of service data to be synchronized. The central management and control device can respond to the service data synchronization requirement, and determine other edge cloud nodes serving as a synchronization data receiving end and meeting the service data synchronization requirement from at least one edge cloud node. Subsequently, the central control device may issue the data identifier and the node identifiers of the other edge cloud nodes to the target edge cloud node through a cooperative network; at this time, the method is cloud edge collaboration.
Specifically, since the cooperative network includes multiple types of network communication channels established between the central control device and the target edge cloud node, when the central control device issues the data identifier and the node identifiers of the other edge cloud nodes to the target edge cloud node through the cooperative network, the central control device may determine, from the multiple types of network communication channels, a network communication channel for performing network communication with the target edge cloud node, and issue the data identifier and the node identifiers of the other edge cloud nodes to the target edge cloud node through the network communication channel.
Correspondingly, when the target edge cloud node receives the data identifier and the node identifier, the service data corresponding to the data identifier may be synchronized to the other edge cloud nodes corresponding to the node identifier through the cooperative network; this is called edge-to-edge collaboration.
Specifically, since the cooperative network further includes multiple types of network communication channels established between the target edge cloud node and the other edge cloud nodes, when the target edge cloud node synchronizes the service data corresponding to the data identifier to the other edge cloud nodes through the cooperative network, a network communication channel for performing network communication with the other edge cloud nodes may be determined from the multiple types of network communication channels, and the service data corresponding to the data identifier is synchronized to the other edge cloud nodes through the network communication channel.
For example, the central control device may generate a rule and a policy for synchronizing service data according to information such as a data identifier in the service data synchronization requirement, and issue the rule and the policy for synchronizing service data to the target edge cloud node through a network communication channel between the central control device and the target edge cloud node that meets the requirement, so that the target edge cloud node may synchronize corresponding service data to other edge cloud nodes through the network communication channel between the target edge cloud node and the other edge cloud nodes that meets the requirement according to the rule and the policy for synchronizing service data.
In some embodiments, a tenant may specify a network communication channel used by the central control device to interact with the target edge cloud node.
Specifically, the service data synchronization requirement may further include a type identifier corresponding to a designated network communication channel in multiple types of network communication channels established between the central management and control device and the target edge cloud node by the tenant. In this case, the central managing and controlling device may determine, as the network communication channel to be used, a network communication channel corresponding to the type identifier among the plurality of types of network communication channels.
Or, in some embodiments, the central management and control device may select a target network communication channel used by the central management and control device to interact with the target edge cloud node by itself.
Specifically, the central management and control device may determine a type of a network communication channel used by the edge cloud node accessed by the tenant for performing network communication with the central management and control device, and determine, as the network communication channel used, a network communication channel belonging to the type among multiple types of network communication channels established between the central management and control device and the target edge cloud node. The edge cloud node accessed by the tenant may be the target edge cloud node, or may be another edge cloud node other than the target edge cloud node, which is not limited in this specification.
In some embodiments, the tenant may also specify a network communication channel used by the target edge cloud node to interact with the other edge cloud nodes.
Specifically, the service data synchronization requirement may further include a type identifier corresponding to a designated network communication channel in multiple types of network communication channels established between the central management and control device and the target edge cloud node by the tenant. In this case, the central management and control device may also issue the type identifier to the target edge cloud node, so that the target edge cloud node may determine, as the network communication channel to be used, a network communication channel corresponding to the type identifier in multiple types of network communication channels established between the target edge cloud node and the other edge cloud nodes.
Or, in some embodiments, the target edge cloud node may select, by itself, a network communication channel used by the target edge cloud node to interact with the other edge cloud nodes.
Specifically, the target edge cloud node determines the type of a network communication channel used by the edge cloud node accessed by the tenant for performing network communication with the central management and control device, and determines, as the network communication channel used, a network communication channel belonging to the type among multiple types of network communication channels established between the target edge cloud node and the other edge cloud nodes. The edge cloud node accessed by the tenant may be the target edge cloud node, or may be another edge cloud node except the target edge cloud node, which is not particularly limited in this specification.
In some embodiments, the central management and control device may send, to the target edge cloud node, a data identifier of service data to be synchronized and node identifiers of other edge cloud nodes serving as a synchronization data receiving end in advance. In order to ensure the accuracy of service data synchronization, the target edge cloud node may determine, from multiple types of network communication channels established between the target edge cloud node and the other edge cloud nodes, a network communication channel for performing network communication with the other edge cloud nodes after the service data is locally stored (for example, the service data is landed, that is, the service data is successfully stored to a disk in the target edge cloud node), and synchronize the service data to the other edge cloud nodes through the network communication channel.
Specifically, the target edge cloud node may store the service data locally when acquiring the service data generated by executing a service instance further created based on the created computing instance, and determine a network communication channel for performing network communication with the other edge cloud node from multiple types of network communication channels established between the target edge cloud node and the other edge cloud node in response to completion of local storage of the service data, so as to perform service data synchronization through the network communication channel.
In some embodiments, the central management and control device may periodically send the rule and the policy for synchronizing the configuration data to the target edge cloud node, so that the target edge cloud node may synchronize the corresponding configuration data to other edge cloud nodes serving as a synchronization data receiving end according to the rule and the policy for synchronizing the service data. The configuration data may be configuration data with a large data volume, such as: system configuration data associated with the tenant.
In some embodiments, the central control device may further distribute the configuration data to each edge cloud node in a broadcast manner. The configuration data may be configuration data with a small data amount, for example: and system configuration data inside the edge cloud computing system.
Referring to fig. 9, fig. 9 is a schematic diagram illustrating a hardware structure of a device according to an exemplary embodiment of the present disclosure.
As shown in fig. 9, at the hardware level, the above devices include a processor 902, an internal bus 904, a network interface 906, a memory 908, and a non-volatile memory 910, but may also include hardware required for other services. One or more embodiments of the present description may be implemented in software, such as by processor 902 reading a corresponding computer program from non-volatile storage 910 into memory 908 and then executing the computer program. Of course, besides software implementation, the one or more embodiments of the present disclosure do not exclude other implementations, such as logic devices or combination of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic module, and may also be hardware or logic devices.
Referring to fig. 10, fig. 10 is a block diagram illustrating a resource scheduling apparatus in an edge cloud computing system according to an exemplary embodiment of the present disclosure.
The resource scheduling apparatus in the edge cloud computing system may be applied to the device shown in fig. 9, so as to implement the technical solution of this specification. The device can be used as a central management and control device in the edge cloud computing system; the edge cloud computing system comprises a central management and control device and at least one edge cloud node; and various types of network communication channels are established between the central control equipment and each edge cloud node.
The resource scheduling apparatus in the edge cloud computing system may include:
an obtaining module 1001, configured to obtain a calculation instance creation requirement submitted by a tenant;
a node determining module 1002, configured to determine, in response to the computing instance creation requirement, a target edge cloud node that meets the computing instance creation requirement from the at least one edge cloud node;
a channel determining module 1003, configured to determine, from the multiple types of network communication channels, a target network communication channel for performing network communication with the target edge cloud node;
a scheduling module 1004, configured to perform resource scheduling on resources carried by the target edge cloud node through the target network communication channel, so as to create a compute instance for the tenant on the target edge cloud node.
Optionally, the computing instance creation requirement includes requirement information corresponding to a computing instance to be created;
the scheduling module 1004 is specifically configured to:
and performing resource scheduling on the resources carried by the target edge cloud node so as to create a computing instance meeting the demand information for the tenant on the target edge cloud node.
Optionally, the computing instance creation requirement includes a type identifier corresponding to a network communication channel specified by the tenant from among the multiple types of network communication channels;
the channel determining module 1003 is specifically configured to:
and determining a network communication channel corresponding to the type identifier in the multiple types of network communication channels as a target network communication channel for network communication with the target edge cloud node.
Optionally, the channel determining module 1003 is specifically configured to:
determining the type of a network communication channel adopted by the edge cloud node accessed by the tenant for carrying out network communication with the central control equipment, and determining the network communication channel belonging to the type in the multiple types of network communication channels as a target network communication channel for carrying out network communication with the target edge cloud node.
Optionally, multiple types of network communication channels are also established between different edge cloud nodes;
the computing instance is used for creating a service instance related to a target service deployed on the target edge cloud node;
the obtaining module 1001 is further configured to obtain a service data synchronization requirement corresponding to the service instance, which is submitted by the tenant; the service data synchronization requirement comprises a data identifier of service data to be synchronized;
the node determining module 1002 is further configured to determine, in response to the service data synchronization requirement, another edge cloud node serving as a synchronization data receiving end, which meets the service data synchronization requirement, from the at least one edge cloud node;
the channel determining module 1003 is further configured to determine, from the multiple types of network communication channels, a network communication channel used for performing network communication with the target edge cloud node, and send the data identifier and the node identifiers of the other edge cloud nodes to the target edge cloud node through the network communication channel, so that the target edge cloud node determines, from the multiple types of network communication channels, a network communication channel used for performing network communication with the other edge cloud nodes, and synchronizes, through the network communication channel, the service data corresponding to the data identifier to the other edge cloud nodes.
Optionally, the multiple types of network communication channels include: an internet communication channel and a private network communication channel.
Optionally, the computing instance comprises any one or a combination of more of the following: container instance, virtual machine instance.
Optionally, the container example comprises: a container instance created on a virtual machine and/or a bare metal container instance created on a physical machine.
Optionally, the resource comprises a heterogeneous resource composed of multiple types of resources; the heterogeneous resources include: heterogeneous computing resources, heterogeneous storage resources, and/or heterogeneous network resources.
Optionally, the heterogeneous computing resources include: x86 computational resources, ARM computational resources and/or GPU computational resources;
the heterogeneous storage resources include: block storage resources, file storage resources and/or object storage resources;
the heterogeneous network resources include network resources obtained by performing hybrid networking on any one or more network resources shown below: the network resource comprises underlay network resources, overlay network resources and network resources obtained by performing hybrid networking on the basis of at least one network component.
Referring to fig. 11, fig. 11 is a block diagram illustrating a resource scheduling apparatus in another edge cloud computing system according to an exemplary embodiment of the present disclosure.
The resource scheduling apparatus in the edge cloud computing system may be applied to the device shown in fig. 9, so as to implement the technical solution of this specification. The device can be used as any target edge cloud node in the edge cloud computing system; the edge cloud computing system comprises a central management and control device and at least one edge cloud node; and various types of network communication channels are established between the central control equipment and each edge cloud node.
The target edge cloud node is an edge cloud node which is determined by the central management and control equipment from the at least one edge cloud node and meets the computing instance creation requirement in response to the computing instance creation requirement submitted by a tenant.
The resource scheduling apparatus in the edge cloud computing system may include:
a creating module 1101, configured to perform resource scheduling on resources carried by the target edge cloud node through a target network communication channel based on the central control device, and create a computation instance for the tenant on the target edge cloud node;
the target network communication channel is a network communication channel which is determined by the central management and control equipment from the multiple types of network communication channels and is used for carrying out network communication with the target edge cloud node.
Optionally, the computing instance creation requirement includes requirement information corresponding to a computing instance to be created;
the creating module 1101 is specifically configured to:
creating a compute instance on the target edge cloud node for the tenant that satisfies the demand information.
Optionally, multiple types of network communication channels are also established between different edge cloud nodes;
the computing instance is used for creating a service instance related to a target service deployed on the target edge cloud node;
the device further comprises:
the receiving module is used for receiving the network communication channel which is determined by the central control equipment and is used for carrying out network communication with the target edge cloud node, the data identification of the service data to be synchronized and the node identification of other edge cloud nodes serving as a synchronous data receiving end from the various network communication channels;
a channel determining module, configured to determine, from the multiple types of network communication channels, a network communication channel used for performing network communication with the other edge cloud nodes corresponding to the node identifier, and synchronize service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel;
the data identification is a data identification included in service data synchronization requirements which are submitted by the tenant and correspond to the service instances; and the other edge cloud nodes are edge cloud nodes which are determined by the central management and control equipment from the at least one edge cloud node and meet the service data synchronization requirement in response to the service data synchronization requirement.
Optionally, the service data synchronization requirement further includes a type identifier corresponding to a network communication channel specified by the tenant from the multiple types of network communication channels;
the receiving module is further configured to receive the type identifier issued by the central control device through the network communication channel;
the channel determination module is specifically configured to:
and determining the network communication channel corresponding to the type identifier in the multiple types of network communication channels as the network communication channel for performing network communication with the other edge cloud nodes.
Optionally, the channel determining module is specifically configured to:
determining the type of a network communication channel adopted by the edge cloud node accessed by the tenant for carrying out network communication with the central control equipment, and determining the network communication channel belonging to the type in the multiple types of network communication channels as the network communication channel for carrying out network communication with other edge cloud nodes.
Optionally, the creating module 1101 is further configured to create a service instance corresponding to the computing instance based on a service image provided by the tenant.
Optionally, the service instance comprises an application instance; the service mirror image comprises an application packaging file;
the creating module 1101 is specifically configured to:
and acquiring the application package file provided by the tenant, and deploying the application package file to the computing instance to create an application instance corresponding to the computing instance.
Optionally, the channel determining module is specifically configured to:
acquiring service data generated by executing a service instance corresponding to the calculation instance, and storing the service data locally;
and determining a network communication channel for performing network communication with the other edge cloud nodes corresponding to the node identifiers from the multiple types of network communication channels in response to the completion of the local storage of the service data.
Optionally, the multiple types of network communication channels include: an internet communication channel and a private network communication channel.
Optionally, the computing instance comprises any one or a combination of more of the following: container instance, virtual machine instance.
Optionally, the container example comprises: a container instance created on a virtual machine and/or a bare metal container instance created on a physical machine.
Optionally, the resource comprises a heterogeneous resource composed of multiple types of resources; the heterogeneous resources include: heterogeneous computing resources, heterogeneous storage resources, and/or heterogeneous network resources.
Optionally, the heterogeneous computing resources include: x86 computational resources, ARM computational resources and/or GPU computational resources;
the heterogeneous storage resources include: block storage resources, file storage resources and/or object storage resources;
the heterogeneous network resources include network resources obtained by performing hybrid networking on any one or more network resources shown below: the network resource comprises underlay network resources, overlay network resources and network resources obtained by performing hybrid networking on the basis of at least one network component.
For the device embodiments, they substantially correspond to the method embodiments, and so reference may be made to some of the descriptions of the method embodiments for their relevant points.
The above-described embodiments of the apparatus are merely illustrative, and the modules described as separate components may or may not be physically separate, and the components displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the technical solution in this specification.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer 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 Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media 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 a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein in one or more embodiments to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if," as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination," depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims (12)

1. A resource scheduling method in an edge cloud computing system comprises a center management and control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node and between different edge cloud nodes; the method is applied to the central management and control equipment and comprises the following steps:
acquiring a calculation instance creation requirement submitted by a tenant;
in response to the computing instance creation requirement, determining a target edge cloud node satisfying the computing instance creation requirement from the at least one edge cloud node;
determining a target network communication channel for performing network communication with the target edge cloud node from multiple types of network communication channels between the central management and control equipment and the target edge cloud node;
performing resource scheduling on resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node; the computing instance is used for creating a service instance related to a target service deployed on the target edge cloud node;
acquiring a service data synchronization requirement which is submitted by the tenant and corresponds to the service instance; the service data synchronization requirement comprises a data identifier of service data to be synchronized;
responding to the service data synchronization requirement, and determining other edge cloud nodes which meet the service data synchronization requirement and serve as synchronization data receiving ends from the at least one edge cloud node;
determining a network communication channel for performing network communication with the target edge cloud node from multiple types of network communication channels between the central control device and the target edge cloud node, issuing the data identifier and the node identifiers of other edge cloud nodes to the target edge cloud node through the network communication channel, so that the target edge cloud node determines the network communication channel for performing network communication with the other edge cloud nodes from the multiple types of network communication channels between the target edge cloud node and the other edge cloud nodes, and synchronizing service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel.
2. The method of claim 1, the compute instance creation requirement comprising requirement information corresponding to a compute instance to be created;
the resource scheduling of the resource carried by the target edge cloud node to create a computing instance for the tenant on the target edge cloud node includes:
and performing resource scheduling on the resources carried by the target edge cloud node so as to create a computing instance meeting the demand information for the tenant on the target edge cloud node.
3. The method of claim 1, the multiple types of network communication channels comprising: an internet communication channel and a private network communication channel.
4. The method of claim 1, the computing instance comprising a combination of any one or more of the following: container instance, virtual machine instance.
5. The method of claim 1, the resource comprising a heterogeneous resource comprised of multiple types of resources; the heterogeneous resources include: heterogeneous computing resources, heterogeneous storage resources, and/or heterogeneous network resources.
6. A resource scheduling method in an edge cloud computing system comprises a center management and control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node and between different edge cloud nodes; the method is applied to any one target edge cloud node;
the target edge cloud node is an edge cloud node which is determined by the central management and control equipment from the at least one edge cloud node and meets the computing instance creation requirement in response to the computing instance creation requirement submitted by a tenant;
the method comprises the following steps:
based on resource scheduling of resources carried by the target edge cloud node by the central control equipment through a target network communication channel, creating a computing instance for the tenant on the target edge cloud node; the computing instance is used for creating a service instance related to a target service deployed on the target edge cloud node;
the target network communication channel is a network communication channel which is determined by the central control device from various types of network communication channels between the central control device and the target edge cloud node and is used for carrying out network communication with the target edge cloud node;
receiving a network communication channel which is determined by the center control equipment and is used for carrying out network communication with the target edge cloud node, a data identifier of service data to be synchronized and a node identifier of other edge cloud nodes serving as a synchronous data receiving end from various types of network communication channels between the center control equipment and the target edge cloud node;
determining a network communication channel for performing network communication with the other edge cloud nodes corresponding to the node identifier from multiple types of network communication channels between the target edge cloud node and the other edge cloud nodes, and synchronizing service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel;
the data identification is a data identification included in service data synchronization requirements which are submitted by the tenant and correspond to the service instances; and the other edge cloud nodes are edge cloud nodes which are determined by the central management and control equipment from the at least one edge cloud node and meet the service data synchronization requirement in response to the service data synchronization requirement.
7. The method of claim 6, the compute instance creation requirement comprising requirement information corresponding to a compute instance to be created;
the creating a compute instance for the tenant on the target edge cloud node, comprising:
creating a compute instance on the target edge cloud node for the tenant that satisfies the demand information.
8. A resource scheduling device in an edge cloud computing system comprises a central management and control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node and between different edge cloud nodes; the device is applied to the central management and control equipment and comprises:
the acquisition module is used for acquiring the calculation instance creation requirement submitted by a tenant;
a node determination module, configured to determine, in response to the computing instance creation requirement, a target edge cloud node that meets the computing instance creation requirement from the at least one edge cloud node;
the channel determining module is used for determining a target network communication channel for carrying out network communication with the target edge cloud node from multiple types of network communication channels between the central control equipment and the target edge cloud node;
the scheduling module is used for performing resource scheduling on the resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node; the computing instance is used for creating a service instance related to a target service deployed on the target edge cloud node;
the obtaining module is further configured to obtain a service data synchronization requirement corresponding to the service instance, which is submitted by the tenant; the service data synchronization requirement comprises a data identifier of service data to be synchronized;
the node determining module is further configured to determine, in response to the service data synchronization requirement, other edge cloud nodes serving as a synchronization data receiving end, which meet the service data synchronization requirement, from the at least one edge cloud node;
the channel determination module is further configured to determine a network communication channel for performing network communication with the target edge cloud node from among multiple types of network communication channels between the central management and control device and the target edge cloud node, and send the data identifier and the node identifiers of the other edge cloud nodes to the target edge cloud node through the network communication channel, so that the target edge cloud node determines a network communication channel for performing network communication with the other edge cloud node from among the multiple types of network communication channels between the target edge cloud node and the other edge cloud nodes, and synchronizes service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel.
9. A resource scheduling device in an edge cloud computing system comprises a central management and control device and at least one edge cloud node; various types of network communication channels are established between the central control equipment and each edge cloud node and between different edge cloud nodes; the device is applied to any one target edge cloud node;
the target edge cloud node is an edge cloud node which is determined by the central management and control equipment from the at least one edge cloud node and meets the computing instance creation requirement in response to the computing instance creation requirement submitted by a tenant;
the device comprises:
the creation module is used for scheduling resources carried by the target edge cloud node through a target network communication channel based on the central management and control equipment, and creating a computing instance for the tenant on the target edge cloud node; the computing instance is used for creating a service instance related to a target service deployed on the target edge cloud node;
the target network communication channel is a network communication channel which is determined by the center control device from multiple types of network communication channels between the center control device and the target edge cloud node and is used for carrying out network communication with the target edge cloud node;
the creation module is further configured to receive a network communication channel determined by the central control device for performing network communication with the target edge cloud node, a data identifier of service data to be synchronized, and a node identifier of another edge cloud node serving as a synchronization data receiving end, from among multiple types of network communication channels between the central control device and the target edge cloud node; determining a network communication channel for performing network communication with the other edge cloud nodes corresponding to the node identifier from multiple types of network communication channels between the target edge cloud node and the other edge cloud nodes, and synchronizing service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel;
the data identification is a data identification included in service data synchronization requirements which are submitted by the tenant and correspond to the service instances; the other edge cloud nodes are the edge cloud nodes which are determined by the central management and control equipment in response to the service data synchronization requirement and meet the service data synchronization requirement from the at least one edge cloud node.
10. An edge cloud computing system, comprising: the system comprises a central control device, a cooperative network and at least one edge cloud node;
the cooperative network comprises a plurality of types of network communication channels established between the central management and control equipment and each edge cloud node and between different edge cloud nodes;
the center management and control equipment and the at least one edge cloud node perform the following interaction:
the central management and control equipment acquires the calculation instance creation requirement submitted by a tenant;
the central management and control equipment responds to the computing instance creation requirement, and determines a target edge cloud node which meets the computing instance creation requirement from the at least one edge cloud node;
the central control equipment determines a target network communication channel for network communication with the target edge cloud node from multiple types of network communication channels between the central control equipment and the target edge cloud node;
the central control equipment performs resource scheduling on the resources carried by the target edge cloud node through the target network communication channel so as to create a computing instance for the tenant on the target edge cloud node; the computing instance is used for creating a service instance related to a target service deployed on the target edge cloud node;
the central management and control equipment acquires service data synchronization requirements which are submitted by the tenants and correspond to the service instances; the service data synchronization requirement comprises a data identifier of service data to be synchronized;
the central control equipment responds to the service data synchronization requirement, and determines other edge cloud nodes which meet the service data synchronization requirement and serve as synchronous data receiving ends from the at least one edge cloud node;
the central control equipment determines a network communication channel for carrying out network communication with the target edge cloud node from various types of network communication channels between the central control equipment and the target edge cloud node, and issues the data identification and the node identifications of other edge cloud nodes to the target edge cloud node through the network communication channel;
and the target edge cloud node determines a network communication channel for performing network communication with other edge cloud nodes from various types of network communication channels between the target edge cloud node and the other edge cloud nodes, and synchronizes the service data corresponding to the data identifier to the other edge cloud nodes through the network communication channel.
11. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 1-7 by executing the executable instructions.
12. A computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method of any one of claims 1-7.
CN202211288350.3A 2022-10-20 2022-10-20 Resource scheduling method and device in edge cloud computing system Active CN115361388B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211288350.3A CN115361388B (en) 2022-10-20 2022-10-20 Resource scheduling method and device in edge cloud computing system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211288350.3A CN115361388B (en) 2022-10-20 2022-10-20 Resource scheduling method and device in edge cloud computing system

Publications (2)

Publication Number Publication Date
CN115361388A CN115361388A (en) 2022-11-18
CN115361388B true CN115361388B (en) 2023-04-11

Family

ID=84008730

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211288350.3A Active CN115361388B (en) 2022-10-20 2022-10-20 Resource scheduling method and device in edge cloud computing system

Country Status (1)

Country Link
CN (1) CN115361388B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112003924A (en) * 2020-08-20 2020-11-27 浪潮云信息技术股份公司 Industrial internet-oriented edge cloud platform building method and system
CN112491957A (en) * 2020-10-27 2021-03-12 西安交通大学 Distributed computing unloading method and system under edge network environment
CN113382032A (en) * 2020-03-10 2021-09-10 阿里巴巴集团控股有限公司 Cloud node changing, network expanding and service providing method, device and medium

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9391801B2 (en) * 2013-08-13 2016-07-12 Vmware, Inc. Virtual private networks distributed across multiple cloud-computing facilities
CN107566429A (en) * 2016-06-30 2018-01-09 中兴通讯股份有限公司 Base station, the response method of access request, apparatus and system
CN109274745B (en) * 2018-09-28 2021-07-30 石家庄良村热电有限公司 Internet of things system and method for optimizing calculation of edge nodes
CN111800443B (en) * 2019-04-08 2022-04-29 阿里巴巴集团控股有限公司 Data processing system and method, device and electronic equipment
CN116170317A (en) * 2019-04-08 2023-05-26 阿里巴巴集团控股有限公司 Network system, service providing and resource scheduling method, device and storage medium
CN112953992B (en) * 2019-12-11 2023-06-23 阿里巴巴集团控股有限公司 Network system, communication and networking method, device and storage medium
CN113727406B (en) * 2020-05-21 2022-11-29 北京三快在线科技有限公司 Communication control method, device, equipment and computer readable storage medium
CN112769938B (en) * 2021-01-12 2022-08-23 烽火通信科技股份有限公司 Kubernets cloud side communication system and method based on QUIC
CN114143144A (en) * 2021-11-30 2022-03-04 招商局金融科技有限公司 Distributed gateway-based micro-service calling method and device and related equipment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113382032A (en) * 2020-03-10 2021-09-10 阿里巴巴集团控股有限公司 Cloud node changing, network expanding and service providing method, device and medium
CN112003924A (en) * 2020-08-20 2020-11-27 浪潮云信息技术股份公司 Industrial internet-oriented edge cloud platform building method and system
CN112491957A (en) * 2020-10-27 2021-03-12 西安交通大学 Distributed computing unloading method and system under edge network environment

Also Published As

Publication number Publication date
CN115361388A (en) 2022-11-18

Similar Documents

Publication Publication Date Title
EP3885908A1 (en) A computer-readable storage medium, an apparatus and a method to select access layer devices to deliver services to clients in an edge computing system
US11159609B2 (en) Method, system and product to implement deterministic on-boarding and scheduling of virtualized workloads for edge computing
US10347542B2 (en) Client-initiated leader election in distributed client-server systems
KR20220027818A (en) Automated resource management for distributed computing
JP6113849B2 (en) Method and apparatus for automatically deploying geographically distributed applications in the cloud
CN111897654B (en) Method and device for migrating application to cloud platform, electronic equipment and storage medium
CN113301078B (en) Network system, service deployment and network division method, device and storage medium
CN113965585B (en) Multi-cloud interconnection method and device
CN113645262A (en) Cloud computing service system and method
CN113300866B (en) Node capacity control method, device, system and storage medium
CN113382032B (en) Cloud node changing, network expanding and service providing method, device and medium
CN112995303A (en) Cross-cluster scheduling method and device
CN115361388B (en) Resource scheduling method and device in edge cloud computing system
WO2023066053A1 (en) Service request processing method, network device and computer-readable storage medium
US10143022B2 (en) Dynamic generation of geographically bound MANET IDs
CN112953993A (en) Resource scheduling method, device, network system and storage medium
CN114697219B (en) Network control method, equipment and system for live network
Sampath Towards Seamless Edge Computing in Connected Vehicles
Pham et al. Fast Optimal Resource Allocation for Resilient Service Coordination in an NFV-Enabled Internet-of-Things System
US20230236897A1 (en) On-demand clusters in container computing environment
CN117971983A (en) Data synchronization method, device, computer equipment and computer readable storage medium
CN114721832A (en) Initialization method and device for block chain nodes
CN116954878A (en) Method, apparatus, device, storage medium and program product for managing container clusters
CN117675548A (en) Data acquisition method, device, equipment and storage medium
CN117369981A (en) Container adjusting method, device and storage medium based on monitor

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant