WO2024082930A1

WO2024082930A1 - Cloud computing instance creation method and apparatus

Info

Publication number: WO2024082930A1
Application number: PCT/CN2023/121146
Authority: WO
Inventors: 周晶; 任庚
Original assignee: 杭州阿里云飞天信息技术有限公司
Priority date: 2022-10-20
Filing date: 2023-09-25
Publication date: 2024-04-25
Also published as: CN115361389A; CN115361389B

Abstract

One or more embodiments of the present description provide a cloud computing instance creation method and apparatus. A distributed edge cloud computing system comprises a central management and control device and at least one edge cloud node. The method comprises: on the basis of at least one resource management dimension, a central management and control device performing resource management on cloud computing resources carried on at least one edge cloud node, so as to create cloud computing resource sets respectively corresponding to resource management dimensions; in response to cloud computing instance creation requirements constructed by a tenant on the basis of at least some of the resource management dimensions, determining, from the cloud computing resource sets corresponding to the at least some of the resource management dimensions, target cloud computing resources matching the cloud computing instance creation requirements; and scheduling the target cloud computing resources to create, on an edge cloud node carrying the target cloud computing resources, a cloud computing instance meeting the cloud computing instance creation requirements, and returning cloud computing instance information of the created cloud computing instance to the tenant.

Description

A method and device for creating a cloud computing instance

This application claims priority to a Chinese patent application filed with the China Patent Office on October 20, 2022, with application number 202211288355.6 and invention name “A method and device for creating a cloud computing instance”, the entire contents of which are incorporated by reference in this application.

Technical Field

One or more embodiments of the present specification relate to the field of edge cloud computing technology, and in particular, to a cloud computing instance creation method, device, electronic device, and machine-readable storage medium.

Background technique

Edge cloud is a cloud computing platform built on edge infrastructure based on the core of cloud computing technology and the capabilities of edge computing.

As more and more edge services are considering edge cloud, more central applications with strong locality and suitable for running on edge cloud nodes are also moving to the edge, and the demand for edge cloud is increasing. Currently, there is no effective resource cloudification and delivery solution in the edge cloud scenario, and various cloud vendors usually leave the resource management logic to the users themselves.

In fact, when using edge cloud, the main demand of users is to run their own services smoothly and conveniently on the edge cloud; in other words, users expect to create corresponding instances on edge cloud nodes according to the image, and then directly run the service. Users do not want to perform complex resource management and other operation and maintenance work on edge cloud nodes. Moreover, in order to bind users, the "cloud postures" (that is, the specific operation methods of users using edge cloud) provided by different cloud vendors are often varied, rather than universal; therefore, in the process of using edge cloud computing services provided by different cloud vendors, users usually need to implement their own resource management logic for different "cloud postures" provided by different cloud vendors, which further reduces the efficiency and experience of users using edge cloud.

Summary of the invention

The present application provides a method for creating a cloud computing instance, which is applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system also includes at least one edge cloud node interconnected with the central control device; the method includes: based on at least one resource management dimension, managing the cloud computing resources carried by the at least one edge cloud node to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension; in response to a cloud computing instance creation requirement constructed by a tenant based on at least part of the resource management dimensions in the at least one resource management dimension, determining a cloud computing resource set corresponding to at least part of the resource management dimensions from the cloud computing resource sets corresponding to each resource management dimension, and determining a target cloud computing resource matching the cloud computing instance creation requirement from the determined cloud computing resource sets; scheduling the target cloud computing resource to create a cloud computing instance that meets the cloud computing instance creation requirement on the edge cloud node carrying the target cloud computing resource, and returning the cloud computing instance information of the created cloud computing instance to the tenant.

The present application also provides a cloud computing instance creation device, which is applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system also includes at least one edge cloud node interconnected with the central control device; the device includes: a first creation unit, which is used to create at least one resource management dimension based on the at least one edge cloud node; The cloud computing resources carried on the edge cloud node are managed to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension; a determination unit is used to respond to the cloud computing instance creation demand constructed by the tenant based on at least part of the resource management dimensions in the at least one resource management dimension, determine the cloud computing resource set corresponding to the at least part of the resource management dimension from the cloud computing resource sets corresponding to each resource management dimension, and determine the target cloud computing resource matching the cloud computing instance creation demand from the determined cloud computing resource sets; a second creation unit is used to schedule the target cloud computing resource to create a cloud computing instance that meets the cloud computing instance creation demand on the edge cloud node equipped with the target cloud computing resource, and return the cloud computing instance information of the created cloud computing instance to the tenant.

The present application also provides an electronic device, including a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are interconnected via a bus; the memory stores machine-readable instructions, and the processor executes the above method by calling the machine-readable instructions.

The present application also provides a machine-readable storage medium, which stores machine-readable instructions. When the machine-readable instructions are called and executed by a processor, the above method is implemented.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of this specification, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

FIG1 is a schematic diagram of a system architecture of a distributed edge cloud computing system shown in an exemplary embodiment;

FIG2 is a flow chart of a method for creating a cloud computing instance according to an exemplary embodiment;

FIG3 is a schematic diagram of a system architecture of another distributed edge cloud computing system shown in an exemplary embodiment;

FIG4 is a schematic diagram of the structure of an electronic device where a cloud computing instance creation device is located, shown in an exemplary embodiment;

FIG. 5 is a block diagram of a cloud computing instance creation device shown in an exemplary embodiment.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

Edge cloud is a cloud built on edge infrastructure based on the core of cloud computing technology and edge computing capabilities. Computing platform; wherein, the edge cloud can also be referred to as an edge cloud computing system, an edge cloud computing platform, etc.

Edge cloud is a relative concept that can be distinguished from central cloud or traditional cloud computing platform. In practical applications, central cloud or traditional cloud computing platform can include data centers with scaled resources and centralized locations; while edge cloud nodes cover a wider network range, are closer to terminals, and have a larger number of edge cloud nodes, but the resource scale of a single edge cloud node is smaller.

Please refer to Figure 1, which is a schematic diagram of the system architecture of a distributed edge cloud computing system shown in an exemplary embodiment. As shown in Figure 1, the edge cloud computing system 100 may include a central control device 101, an edge cloud node 102, an edge cloud node 103, and an edge cloud node 104; the central 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 FIG1 only shows three edge cloud nodes by way of example, which does not represent any special limitation to this specification; in practical applications, the edge cloud computing system 100 may include at least one edge cloud node interconnected with the central control device 101. The central control device 101 may be deployed in one or more cloud computing data centers, or in one or more traditional data centers, and this specification does not specifically limit this.

Among them, each edge cloud node in the at least one edge cloud node may include a series of edge infrastructures; the edge infrastructure may specifically include but is not limited to: distributed data centers (DCs), wireless computer rooms or clusters, operator communication networks, core network equipment, base stations, edge gateways, home gateways, computing devices or storage devices and other edge devices and corresponding network environments, etc. It should be noted that the locations of different edge cloud nodes, the cloud computing capabilities that can be provided, and the included edge infrastructures may be the same or different, and this specification does not specifically limit this.

The terminal shown in Figure 1 may include a demand side of a cloud computing service. For example, the terminal may include a user terminal in the Internet or the Internet of Things.

In the system architecture of the edge cloud computing system as shown in FIG1, the central cloud corresponding to the central control device, the edge cloud formed by the at least one edge cloud node, and the terminal can form an end-to-end technical architecture of "cloud-edge-end three-body collaboration". In the edge cloud computing system 100, the central control device 101 can take each edge cloud node (such as edge cloud node 102, edge cloud node 103 and edge cloud node 104) as a control object, and uniformly control resource scheduling, image management, instance control, operation and maintenance, network, security, etc., so as to put the cloud computing service into each edge cloud node for processing, so as to provide cloud computing services to users with the help of various resources carried by the edge cloud node. Since the edge cloud node is closer to the user terminal, the response delay of the cloud computing service can be reduced, the pressure on the central cloud or traditional cloud computing platform corresponding to the edge cloud node can be reduced, the bandwidth cost can be reduced, and the resource demand of the terminal for large connection, low latency and large bandwidth in the cloud computing scenario can be met.

In actual applications, edge cloud nodes can create corresponding instances based on images, and provide various cloud computing services to the outside world through instances. Among them, the image is the basic file required to create an instance in the edge cloud node; for example, the image can be an image file such as an operating system, application, or operation configuration required to provide cloud computing services to users. For example, it can be a file made in a certain format according to a specific series of files in accordance with the computing deployment requirements of the edge cloud node. In addition, the form of the image is diverse, and it can be a virtual machine (Virtual Machine, VM) image file, a container (Docker) image file, or various types of application packaging files, etc. The image form can be related to the virtualization technology that needs to be used for cloud computing services, and this specification does not limit this. Corresponding to the image, the implementation form of the instance can be a virtual machine, a container, or an application, etc.

In addition, in the system architecture of the edge cloud computing system shown in FIG1, in addition to the central control device 101, the edge cloud computing system 100 may also include one or more edge control devices. The edge control device may be used to assist and cooperate with the central control device to control and schedule the at least one edge cloud node, thereby improving the control and scheduling of the edge cloud node by the central control device, thereby achieving the purpose of fully utilizing edge resources.

The edge control device can be deployed in one or more edge cloud nodes; in one embodiment, each edge cloud node can include one or more resource devices, and the edge control device can be deployed on one or more resource devices; or, in addition to resource devices, each edge cloud node can also include one or more proprietary devices that are different from the resource devices and are specifically used to deploy edge control devices, and the edge control device can be deployed on one or more proprietary devices. The edge control device can also be deployed together with the central control device, and this specification does not specifically limit this.

As more and more edge services are considering edge cloud, more central applications with strong locality and suitable for running on edge cloud nodes are also sinking to the edge, and the demand for edge cloud is increasing. At present, there is no effective resource cloudification and delivery solution in the edge cloud scenario. Each cloud vendor usually leaves resource control to the user themselves, that is, users usually need to control resources for their own physical resources and implement their own resource control logic.

In fact, when using edge cloud, the main demand of users is to run their own services smoothly and conveniently on the edge cloud. In other words, users expect to create corresponding instances on edge cloud nodes according to the image, and then directly run the service. Users do not want to perform complex resource management and other operation and maintenance work on edge cloud nodes. Moreover, in order to bind users, the "cloud postures" provided by different cloud vendors are often varied, rather than universal. Among them, "cloud posture" can include the meaning of what cloud the user goes to and how to go to the cloud, which can be used to indicate the specific operation method of the user's edge cloud. Therefore, in the process of using edge cloud computing services provided by different cloud vendors, users usually need to implement their own resource management logic for different "cloud postures" provided by different cloud vendors, which further reduces the efficiency and experience of users' edge cloud use.

It can be seen that in the embodiments shown above, since edge resources are distributed, heterogeneous, integrated, miniaturized, and have wide coverage, compared with traditional central cloud scenarios, resource management and service operation and maintenance in edge cloud computing scenarios are more complex and difficult, resulting in lower efficiency and poorer edge cloud experience for users, and may also cause waste of edge resources.

In view of this, this specification aims to propose a technical solution based on one or more resource management dimensions (dimensionality), in which the central control device in the edge cloud computing system uniformly manages resources, thereby providing users with a convenient and easy-to-use edge cloud solution.

In implementation, a central control device in a distributed edge cloud computing system can manage cloud computing resources carried on at least one edge cloud node interconnected with the central control device in the edge cloud computing system based on at least one resource management dimension, so as to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension; further, the central control device can determine the cloud computing resource set corresponding to at least part of the resource management dimensions from the cloud computing resource sets corresponding to each resource management dimension in response to the cloud computing instance creation demand constructed by the tenant based on at least part of the resource management dimensions in the at least one resource management dimension, and can determine the target cloud computing resource matching the cloud computing instance creation demand from the determined cloud computing resource set; further, the central control device can schedule the target cloud computing resource to be carried on A cloud computing instance that meets the cloud computing instance creation requirement is created on the edge cloud node having the target cloud computing resource, and cloud computing instance information of the created cloud computing instance is returned to the tenant.

It can be seen that in the technical solution in this specification, on the one hand, the central control device (that is, the platform side) in the distributed edge cloud computing system can manage the cloud computing resources carried on the edge cloud nodes based on at least one resource management dimension, and realize resource clouding in an efficient, flexible and scalable manner.

On the other hand, the central management and control device can manage cloud computing resources based on at least one resource management dimension, and the tenants can build cloud computing instance creation requirements based on at least one resource management dimension. Therefore, through a unified multi-dimensional resource modeling strategy, while decoupling the process of cloud computing resource management from the process of cloud computing instance production, it is possible to connect the process of resource management by the central management and control device and the process of tenant edge cloud use, make resource management and instance production models transparent, and improve the efficiency of tenant edge cloud use.

On the other hand, in the process of using the cloud at the edge, tenants do not need to pay attention to the underlying physical resources corresponding to each edge cloud node, nor do they need to learn the complex cloud usage postures of various cloud vendors. Tenants only need to build cloud computing instance creation requirements based on at least one resource management dimension, so that the central management and control device can determine the cloud computing resources that match the cloud computing instance creation requirements from the cloud computing resource set as the target cloud computing resources, and can schedule the determined target cloud computing resources to create a cloud computing instance that meets the cloud computing instance creation requirements on the corresponding edge cloud node; enabling the platform side to provide tenants with a more flexible, efficient, and scalable edge cloud usage method in a "cloud neutral" manner, creating more service value for tenants, and the platform side will not bind tenants, which can improve the tenants' edge cloud usage experience.

The present application is described below through specific embodiments and in combination with specific application scenarios.

Please refer to FIG. 2 , which is a flowchart of a method for creating a cloud computing instance according to an exemplary embodiment. The method can be applied to the central control device 101 shown in FIG. 1 . The method can perform the following steps:

Step 202: Based on at least one resource management dimension, manage the cloud computing resources carried on at least one edge cloud node in the edge cloud computing system that is interconnected with the central control device, so as to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension.

In this specification, the resource management can be understood as abstracting the physical resources in the edge cloud computing system into controllable cloud computing resources through modeling and orchestration.

For example, the preset resource management dimensions may include three resource management dimensions: city, computer room (IDC, Internet Data Center), and operator (ISP, Internet Service Provider); as shown in FIG1 , the central control device 101 may classify the cloud computing resources carried by the edge cloud node 102, the edge cloud node 103, and the edge cloud node 104 based on the three resource management dimensions of city, computer room, and operator, and may create cloud computing resource sets corresponding to each resource management dimension based on the classification results.

In one implementation, each resource management dimension may include several resource management sub-dimensions, and the cloud computing resource sets corresponding to each resource management dimension may include cloud computing resource subsets corresponding to each resource management sub-dimension.

For example, the resource management dimension of the computer room may include resource management sub-dimensions corresponding to different computer rooms (such as IDC1, IDC2, etc.), and the cloud computing resource set corresponding to the computer room may be divided into cloud computing resource subsets corresponding to each computer room; wherein the cloud computing resource subset corresponding to computer room IDC1 may include Cloud computing resources in computer room IDC1.

It should be noted that in the above-described embodiments, the cloud computing resource sets corresponding to the various resource management dimensions may or may not have intersections, and this specification does not specifically limit this. However, there should be no intersections between the multiple cloud computing resource subsets included in the cloud computing resource set corresponding to a certain resource management dimension; for example, the cloud computing resource subset corresponding to computer room IDC1 may only include cloud computing resources deployed in computer room IDC1, but not cloud computing resources deployed in other computer rooms.

In this specification, the cloud computing resources can still be in the form of physical resources or logical resources. MCU (Meta Control Unit) can be used as the minimum control unit for resource management, and can encapsulate atomic control capabilities.

For example, a single physical resource (such as an ARM board, a hard disk, etc.) can be used as an MCU and converted into a corresponding cloud computing resource.

For another example, physical resources can be abstracted into logical resources (such as 10GB of storage space, 100MB of bandwidth, etc.), and the logical resources can be converted into corresponding cloud computing resources according to the MCU. In one possible embodiment, cloud computing resources can be further split or grouped for management according to actual needs (such as the number of resources, etc.). For example, if a storage medium can provide 1TB of storage space, the 1TB of storage resources corresponding to the storage medium can be split into multiple smaller storage resources to facilitate flexible scheduling and avoid resource waste; while other storage media can only provide 1GB of storage space respectively, the 1GB corresponding to these storage media can be configured as a group to improve the efficiency of resource management and resource scheduling in the edge cloud computing system.

In addition, in step 202, the central control device may also obtain physical resource information of physical resources in the edge cloud computing system, and may determine resource metadata of the created cloud computing resources based on the obtained physical resource information.

In one embodiment shown, the cloud computing resources may include heterogeneous resources composed of cloud computing resources of multiple resource types; wherein the resource types may specifically include but are not limited to computing resources, storage resources, network resources, and the like.

For example, the cloud computing resources may include one or more combinations of the following: heterogeneous computing resources, heterogeneous storage resources, and heterogeneous network resources. The heterogeneous computing resources may include, but are not limited to, x86 microprocessors, ARM boards, GPU (Graphics Processing Unit) resources, etc.; the heterogeneous storage resources may include, but are not limited to, block storage, file storage, object storage, etc.; the heterogeneous network resources may include, but are not limited to, VPC (Virtual Private Cloud), LB (Load Balance), NAT (Network Address Translation), etc.

In one embodiment shown, at least one edge cloud node included in the edge cloud computing system may include IDCs distributed in different location areas; the at least one resource management dimension may include a combination of one or more of the following: the location area where the edge cloud node equipped with cloud computing resources is located, the resource type of the cloud computing resources, and the operator to which the cloud computing resources belong.

For example, according to the different coverage of the location area, you can configure the resource management dimensions such as country, province, area (such as East China, North China, etc.), city, etc.; according to the construction method of distributed data centers, you can configure the resource management dimensions such as data center (IDC), edge node service room (ENS room), etc.; according to the resource type of cloud computing resources, you can configure the resource management dimensions such as computing resources, storage resources, network resources, etc. Dimension.

It should be noted that regarding the specific dimensions of the at least one resource management dimension, technical personnel in this field can flexibly configure and expand them according to actual needs. This specification does not impose any special restrictions and it is impossible to list them all in the specification.

Step 204: In response to a cloud computing instance creation demand constructed by the tenant based on at least part of the at least one resource management dimension, determine a cloud computing resource set corresponding to at least part of the resource management dimension from the cloud computing resource sets corresponding to each resource management dimension, and determine a target cloud computing resource that matches the cloud computing instance creation demand from the determined cloud computing resource sets.

For example, the central control device 101 can classify the cloud computing resources carried by the edge cloud node 102, the edge cloud node 103 and the edge cloud node 104 based on the three resource management dimensions of city, computer room and operator, and can create cloud computing resource sets corresponding to each resource management dimension based on the classification results; accordingly, the tenant corresponding to the terminal can construct a cloud computing instance creation demand based on at least some of the three resource management dimensions; in response to the cloud computing instance creation demand constructed by the tenant based on the resource management dimension of city being [Hangzhou city, number of resources, ...], the central control device 101 can determine the cloud computing resource set corresponding to the resource management dimension of city from the cloud computing resource sets pre-created corresponding to the three resource management dimensions of city, computer room and operator, and can further determine the cloud computing resource matching the cloud computing instance creation demand [Hangzhou city, number of resources, ...] from the cloud computing resource set corresponding to the resource management dimension of city as the target cloud computing resource to be scheduled.

In a possible embodiment, the central control device may provide a demand submission portal (e.g., open API) to the outside world, and the demand submission portal may be a web page, an application page, or a command window, etc.; the demand submission portal may be used by tenants to submit cloud computing instance creation requirements to the central control device, that is, description information for the cloud computing instance to be created. The cloud computing instance creation requirements may include, but are not limited to, edge cloud node selection parameters and/or resource selection parameters; the edge cloud node selection parameters may include scheduling domains and/or performance requirements for edge cloud nodes, etc.; the resource selection parameters may include resource types, resource quantities, and performance requirements for resource devices, etc. Further, the central control device may schedule resources for the at least one edge cloud node based on the cloud computing instance creation requirements, so that the scheduled edge cloud node creates a cloud computing instance for the tenant based on the scheduled cloud computing resources, or so that the scheduled edge cloud node reserves the scheduled cloud computing resources for the tenant.

In one embodiment shown, the cloud computing instance can be divided into multiple instance types. In implementation, the cloud computing instance can specifically include one or more combinations of the following: container instance, virtual machine instance, application instance.

For example, the container instance may specifically include a container instance created on a virtual machine and/or a bare metal container instance created on a physical machine; the virtual machine instance may specifically include a virtual machine instance created on a physical machine; the application instance may specifically include an application instance created on a physical machine or a virtual machine.

It should be noted that, in step 204, the target cloud computing resource may be a resource set including one or more cloud computing resources matching the cloud computing instance creation requirement. The resource set corresponding to the target cloud computing resource may include cloud computing resources of different resource types, and may also include heterogeneous cloud computing resources.

Step 206: Schedule the target cloud computing resources to create a cloud computing instance that meets the cloud computing instance creation requirements on the edge cloud node equipped with the target cloud computing resources, and return the cloud computing instance information of the created cloud computing instance to the tenant.

For example, in response to a tenant's request for creating a cloud computing instance of [Hangzhou city, number of resources, ...], the central management After determining the target cloud computing resources that match the cloud computing instance creation requirements, the control device 101 can schedule the determined target cloud computing resources to create a cloud computing instance that meets the cloud computing instance creation requirements on the edge cloud node equipped with the target cloud computing resources, and can return the cloud computing instance information of the created cloud computing instance to the tenant, that is, the cloud computing instance produced by the edge cloud node equipped with the target cloud computing resources can be delivered to the tenant.

Among them, in the step 206, a possible resource scheduling method includes: the central control device 101 can determine the edge cloud node equipped with the target cloud computing resources as the target edge cloud node; according to the resource metadata of the target cloud computing resources, control the corresponding resource devices in the target edge cloud node to perform resource allocation or resource reservation, so as to utilize the target cloud computing resources scheduled in the target edge cloud node to provide corresponding cloud computing services for tenants.

In order to enable personnel in this technical field to better understand the technical solutions in the embodiments of this specification, the embodiments in this specification are explained below by taking the cloud computing instance as a container instance and the edge cloud node as an IDC distributed in different location areas as an example, combined with the architectural diagram as shown in Figure 3.

Please refer to Figure 3, which is a schematic diagram of the system architecture of another distributed edge cloud computing system shown in an exemplary embodiment. One or more cloud computing instance creation methods provided in this specification can be applied to the central control device 301 shown in Figure 3. As shown in Figure 3, at least one edge cloud node interconnected with the central control device 301 can include IDC1, IDC2, ... and so on.

Each of the at least one edge cloud node may be equipped with cloud computing resources of different resource types. The central control device 301 may manage the cloud computing resources carried by the edge cloud node based on the at least one resource management dimension to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension.

The central control device 301 can also provide an open API as an entry point for submitting cloud computing instance creation requirements; so that tenants can submit cloud computing instance creation requirements to the central control device 301 through the open API.

In this specification, the cloud computing instance creation service provided by the central control device to tenants may include a first service mode and a second service mode; wherein the first service mode may include a service mode in which the tenant is not aware of the logical resource objects corresponding to the cloud computing resources used to create the cloud computing instance; and the second service mode may include a service mode in which the tenant can perceive the logical resource objects corresponding to the cloud computing resources used to create the cloud computing instance.

Among them, the first service mode can be a Serverless mode; in this service mode, the tenant may only need to use the edge cloud conveniently and efficiently, so they can only obtain the cloud computing instance delivered to them that meets the cloud computing instance creation requirements, and the tenant does not care about the target cloud computing resources used to create the cloud computing instance.

Among them, the second service mode can be a Node-Aware mode, and can also be called an LRO-Aware mode; in this service mode, in addition to the need for convenient and efficient edge cloud use, tenants also need to understand the target cloud computing resources used to create the cloud computing instance. Therefore, in addition to delivering cloud computing instances that meet the cloud computing instance creation requirements to the tenants, it is also necessary to return to the tenants the logical resource object information of the logical resource objects corresponding to the target cloud computing resources.

In the implementation, in step 206, creating a cloud computing instance that meets the cloud computing instance creation requirements and returning the cloud computing instance information of the created cloud computing instance to the tenant may specifically include: determining a service mode corresponding to the instance creation requirement; if it is determined that the service mode corresponding to the cloud computing instance creation requirement is the first service mode, a cloud computing instance that meets the cloud computing instance creation requirement is created, and the cloud computing instance information of the created cloud computing instance is returned to the tenant; if it is determined that the service mode corresponding to the cloud computing instance creation requirement is the second service mode, a cloud computing instance that meets the cloud computing instance creation requirement is created, and the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource are returned to the tenant.

For example, as shown in FIG3 , in response to a container instance creation requirement constructed by tenant A based on at least part of the at least one resource management dimension (such as opening n containers of xx specifications at a certain location, where n can be any positive integer), the central control device 301 can determine the target cloud computing resource that matches the container instance creation requirement from the cloud computing resource sets corresponding to each resource management dimension; further, the central control device 301 can determine that the service mode corresponding to the container instance creation requirement is the Serverless mode, and then the target cloud computing resource can be scheduled to create a container instance Pod A that meets the container instance creation requirement on the edge cloud node IDC1 equipped with the target cloud computing resource, and the container instance information of the created container instance Pod A can be returned to tenant A.

It should be noted that, in the above-described embodiments, the specific information content of the container instance information is not limited in this specification. For example, the container instance information may specifically include but is not limited to the instance identifier of the container instance, the creation time of the container instance, the number of containers included in the container instance, the container specifications of each container included in the container instance, and the like.

For another example, as shown in FIG3 , in response to the first container instance creation requirement and the second container instance creation requirement constructed by tenant B based on at least part of the resource management dimensions in the at least one resource management dimension, the central control device 301 can determine the first target cloud computing resource that matches the first container instance creation requirement, and determine the second target cloud computing resource that matches the second container instance creation requirement from the cloud computing resource sets corresponding to the respective resource management dimensions; further, the central control device 301 can determine that the service mode corresponding to the first container instance creation requirement and the second container instance creation requirement is the Node-Aware mode, and then the first target cloud computing resource and the second target cloud computing resource can be scheduled to create a container instance Pod B1 that meets the first container instance creation requirement on the edge cloud node IDC1 equipped with the first target cloud computing resource, and to create a container instance Pod B2 that meets the second container instance creation requirement on the edge cloud node IDC2 equipped with the second target cloud computing resource, and the container instance information of the created container instance Pod B1 and container instance Pod B2 can be returned to tenant B.

It should be noted that, in the embodiments shown above, the container instance Pod B1 and the container instance Pod B2 created for tenant B are respectively located on the edge cloud node IDC1 and the edge cloud node IDC2. It can be seen that in the technical solution of this specification, the edge cloud node where the container instance created for the tenant is located is mainly related to the container instance creation requirements constructed by the tenant, and does not necessarily depend on the tenant being closer to the various edge cloud nodes.

In a possible embodiment, determining the service mode corresponding to the cloud computing instance creation requirement may specifically include: determining the service mode corresponding to the tenant as the service mode corresponding to the cloud computing instance creation requirement; or, the cloud computing instance creation requirement also includes a service mode configured for the cloud computing embodiment to be created.

In actual applications, the logical resource object may be created during the cloud computing resource management phase, or may be generated during the cloud computing instance creation phase.

In one embodiment shown, the logical resource object corresponding to the target cloud computing resource may be created in the cloud computing resource management stage. In implementation, the creation of a cloud computing instance that meets the cloud computing instance creation requirements, and returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant may specifically include: creating a cloud computing instance that meets the cloud computing instance creation requirements, and obtaining the logical resource object corresponding to the target cloud computing resource created in the resource management stage, and returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the obtained logical resource object to the tenant.

For example, in step 202, when the cloud computing resources carried by the at least one edge cloud node are managed to create a cloud computing resource set corresponding to each resource management dimension, a corresponding logical resource object can be created for each cloud computing resource included in the created cloud computing resource set, and a logical resource object identifier for globally uniquely identifying the logical resource object can be assigned to each logical resource object; subsequently, in response to a first container instance creation requirement constructed by tenant B, the central control device 301 can determine a first target cloud computing resource that matches the first container instance creation requirement; further, the central control device 301 determines that the service mode corresponding to the first container instance creation requirement is the Node-Aware mode, then the first target cloud computing resource can be scheduled to create a container instance Pod B1 that meets the first container instance creation requirement on the edge cloud node IDC1 equipped with the first target cloud computing resource, and the logical resource object IDC1.node1 corresponding to the first target cloud computing resource created in the resource management stage can be obtained, and the container instance information of the created container instance Pod B1 and the logical resource object information of the logical resource object IDC1.node1 can be returned to tenant B.

In another embodiment shown, the logical resource object corresponding to the target cloud computing resource may be created in the cloud computing instance creation phase. In implementation, the creating of a cloud computing instance that meets the cloud computing instance creation requirements, and returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant may specifically include: creating a cloud computing instance that meets the cloud computing instance creation requirements, and creating a logical resource object corresponding to the target cloud computing resource, and returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the created logical resource object to the tenant.

For example, in response to a second container instance creation requirement constructed by tenant B, the central control device 301 can determine a second target cloud computing resource that matches the second container instance creation requirement; further, the central control device 301 determines that the service mode corresponding to the second container instance creation requirement is the Node-Aware mode, and then the second target cloud computing resource can be scheduled to create a container instance Pod B2 that meets the second container instance creation requirement on the edge cloud node IDC2 equipped with the second target cloud computing resource, and a logical resource object IDC2.node1 corresponding to the second target cloud computing resource can be created, and the container instance information of the created container instance Pod B2 and the logical resource object information of the logical resource object IDC2.node1 can be returned to tenant B.

It should be noted that in the above-mentioned embodiments, the "node" in the Node-Aware mode is not an edge cloud node or a physical device in the edge cloud computing system, but a logical resource object corresponding to the cloud computing resources. The logical resource objects that can be perceived by the tenants may include logical resource objects corresponding to the cloud computing resources allocated or reserved by the central control device for the tenants.

In one embodiment shown, in the second service mode, although the tenant has the ability to perceive the logical resource object corresponding to the target cloud computing resource, the tenant does not necessarily need to enable the perception capability immediately; therefore, in the process of delivering the cloud computing instance to the tenant, only the created cloud computing instance can be returned to the tenant by default. The cloud computing instance information of the tenant is not returned directly to the tenant for the time being, and the logical resource object information of the logical resource objects that the tenant is allowed to perceive is provided to the tenant until the tenant actively queries.

During implementation, returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant may specifically include: returning the cloud computing instance information of the created cloud computing instance to the tenant; and returning the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant in response to a query request submitted by the tenant for the logical resource object corresponding to the target cloud computing resource.

In one or more of the embodiments shown above, the object information of the logical resource object may specifically include at least part of the data in the resource metadata of the cloud computing resource corresponding to the logical resource object. It should be noted that in this case, since the "logical resource object information-logical resource object-cloud computing resource-resource metadata of cloud computing resource" is corresponding, the tenant can at most perceive the logical resource object, and the resource metadata of the cloud computing resource and the logical resource object corresponding to the cloud computing resource are uniformly maintained by the central control device, so data consistency can be guaranteed. In the related technology, when the tenant manages the resources it owns by itself, it may happen that the resource information maintained by the tenant is not synchronized to the control device in the edge cloud computing system in time, resulting in data inconsistency.

In one embodiment shown, under the second service mode, tenants are supported to build their own resource management and control units according to service requirements based on the logical resource objects of the logical resource objects they obtain, thereby improving the tenants' edge cloud efficiency.

During implementation, before or simultaneously with step 204, the method may further include: in response to a resource scheduling policy configured by the tenant based on the logical resource object information of the logical resource object, determining a cloud computing resource set that matches the resource scheduling policy from the cloud computing resource sets corresponding to each resource management dimension, as a candidate cloud computing resource set; in this case, determining a cloud computing resource set corresponding to at least part of the resource management dimension from the cloud computing resource sets corresponding to each resource management dimension may specifically include: determining a cloud computing resource set corresponding to at least part of the resource management dimension from the determined candidate cloud computing resource set.

Continuing with the example of the above-described embodiment, after obtaining the logical resource object information of the logical resource object returned by the central control device, the tenant can configure the corresponding resource scheduling strategy according to the logical resource object information and the actual service requirements, and can submit the resource scheduling strategy to the central control device; in response to the resource scheduling strategy configured by the tenant based on the logical resource object information of the logical resource object, the central control device can determine the cloud computing resource set that matches the resource scheduling strategy from the created cloud computing resource sets corresponding to each resource management dimension, as a candidate cloud computing resource set; further, in response to the tenant's cloud computing instance creation requirement constructed based on at least part of the resource management dimensions in at least one resource management dimension, the central control device can further determine the cloud computing resource set corresponding to at least part of the resource management dimension from the determined candidate cloud computing resource set.

It should be noted that, in the implementation shown above, when the tenant can perceive the logical resource object information of the logical resource object corresponding to the target cloud computing resource, the tenant can customize the resource scheduling strategy according to the actual service demand, which is equivalent to the process of determining the target cloud computing resource in response to the cloud computing instance creation demand constructed by the central control device. Taking the resource scheduling strategy as an added constraint condition can improve the determination of the target cloud computing resource. The efficiency of resources can be improved, thereby improving the efficiency of creating cloud computing instances for tenants.

Through the above technical solutions, it can be seen that, on the one hand, the central control device (that is, the platform side) in the distributed edge cloud computing system can manage the cloud computing resources carried on the edge cloud nodes based on at least one resource management dimension, and realize resource clouding in an efficient, flexible and scalable manner.

Corresponding to the above-mentioned embodiment of the method for creating a cloud computing instance, this specification also provides an embodiment of a device for creating a cloud computing instance.

Please refer to Figure 4, which is a hardware structure diagram of an electronic device where a cloud computing instance creation device is located, shown in an exemplary embodiment. At the hardware level, the device includes a processor 402, an internal bus 404, a network interface 406, a memory 408, and a non-volatile memory 410, and of course may also include hardware required for other services. One or more embodiments of this specification can be implemented based on software, such as the processor 402 reading the corresponding computer program from the non-volatile memory 410 into the memory 408 and then running it. Of course, in addition to software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logical unit, but can also be hardware or logic devices.

Please refer to FIG. 5, which is a block diagram of a cloud computing instance creation device shown in an exemplary embodiment. The cloud computing instance creation device can be applied to the electronic device shown in FIG. 4 to implement the technical solution of this specification. The device is applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system also includes at least one edge cloud node interconnected with the central control device; the device may include:

The first creation unit 502 is used to manage the cloud computing resources carried by the at least one edge cloud node based on at least one resource management dimension, so as to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension;

The determining unit 504 is configured to, in response to a cloud computing instance creation requirement constructed by the tenant based on at least some of the at least one resource management dimension, determine, from cloud computing resource sets corresponding to each resource management dimension, a cloud computing resource set corresponding to the at least some of the resource management dimensions, and determine, from the determined cloud computing resource set, a target cloud computing resource matching the cloud computing instance creation requirement;

The second creation unit 506 is used to schedule the target cloud computing resources to create a cloud computing instance that meets the cloud computing instance creation requirements on the edge cloud node equipped with the target cloud computing resources, and return the cloud computing instance information of the created cloud computing instance to the tenant.

In this embodiment, the cloud computing instance creation service provided by the central control device for the tenant includes a first service mode and a second service mode; wherein the first service mode includes a service mode in which the tenant is not aware of the logical resource objects corresponding to the cloud computing resources used to create the cloud computing instance; and the second service mode includes a service mode in which the tenant can be aware of the logical resource objects corresponding to the cloud computing resources used to create the cloud computing instance.

The second creating unit 506 is specifically configured to:

Determining a service model corresponding to the cloud computing instance creation requirement;

If it is determined that the service mode corresponding to the cloud computing instance creation requirement is the first service mode, creating a cloud computing instance that meets the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance to the tenant;

If it is determined that the service mode corresponding to the cloud computing instance creation requirement is the second service mode, a cloud computing instance that meets the cloud computing instance creation requirement is created, and the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource are returned to the tenant.

In this embodiment, the second creating unit 506 is specifically configured to:

Creating a cloud computing instance that meets the cloud computing instance creation requirements, and creating a logical resource object corresponding to the target cloud computing resource, and returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the created logical resource object to the tenant; or,

Create a cloud computing instance that meets the cloud computing instance creation requirements, and obtain the logical resource object corresponding to the target cloud computing resource created in the resource management stage, and return the cloud computing instance information of the created cloud computing instance and the logical resource object information of the obtained logical resource object to the tenant.

In this embodiment, the second creating unit 506 is specifically configured to:

Returning the cloud computing instance information of the created cloud computing instance to the tenant;

In response to a query request submitted by the tenant for the logical resource object corresponding to the target cloud computing resource, logical resource object information of the logical resource object corresponding to the target cloud computing resource is returned to the tenant.

In this embodiment, the object information of the logical resource object includes at least part of the data in the resource metadata of the cloud computing resource corresponding to the logical resource object.

In this embodiment, the determining unit 504 is further configured to:

In response to a resource scheduling policy configured by the tenant based on the logical resource object information of the logical resource object, a cloud computing resource set matching the resource scheduling policy is determined from cloud computing resource sets corresponding to each resource management dimension as a candidate cloud computing resource set;

The step of determining, from the cloud computing resource sets corresponding to the respective resource management dimensions, the cloud computing resource sets corresponding to the at least part of the resource management dimensions comprises:

A cloud computing resource set corresponding to at least part of the resource management dimension is determined from the determined candidate cloud computing resource sets.

In this embodiment, the cloud computing instance includes one or more combinations of the following: a container instance, a virtual machine instance, and an application instance.

In this embodiment, the container instance includes: a container instance created on a virtual machine; and/or a bare metal container instance created on a physical machine.

In this embodiment, the cloud computing resources include heterogeneous resources composed of cloud computing resources of multiple resource types;

The cloud computing resources include one or more combinations of the following: heterogeneous computing resources, heterogeneous storage resources, and heterogeneous network resources.

In this embodiment, the at least one edge cloud node includes an Internet data center IDC distributed in different location areas;

The at least one resource management dimension includes one or more combinations of the following: the location area where the edge cloud node equipped with cloud computing resources is located, the resource type of the cloud computing resources, and the operator to which the cloud computing resources belong.

Through the above embodiments, on the one hand, the central control device (i.e., the platform side) in the distributed edge cloud computing system can manage the cloud computing resources carried on the edge cloud nodes based on at least one resource management dimension, and realize resource cloud migration in an efficient, flexible and scalable manner.

The implementation process of the functions and effects of each unit in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can refer to the partial description of the method embodiments. The device embodiments described above are only schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. Ordinary technicians in this field can understand and implement it without paying creative work.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

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

Memory may include non-permanent storage in a computer-readable medium, in the form of 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 include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

The above is a description of a specific embodiment of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "one", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

Claims

A method for creating a cloud computing instance, the method being applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system further comprising at least one edge cloud node interconnected with the central control device; the method comprising:

Based on at least one resource management dimension, manage the cloud computing resources carried by the at least one edge cloud node to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension;

In response to a cloud computing instance creation requirement constructed by the tenant based on at least part of the at least one resource management dimension, determine, from cloud computing resource sets corresponding to each resource management dimension, a cloud computing resource set corresponding to at least part of the resource management dimension, and determine, from the determined cloud computing resource set, a target cloud computing resource matching the cloud computing instance creation requirement;

The target cloud computing resources are scheduled to create a cloud computing instance that meets the cloud computing instance creation requirements on an edge cloud node equipped with the target cloud computing resources, and cloud computing instance information of the created cloud computing instance is returned to the tenant.
According to the method of claim 1, the cloud computing instance creation service provided by the central control device to the tenant includes a first service mode and a second service mode; wherein the first service mode includes a service mode in which the tenant is not aware of the logical resource objects corresponding to the cloud computing resources used to create the cloud computing instance; and the second service mode includes a service mode in which the tenant can perceive the logical resource objects corresponding to the cloud computing resources used to create the cloud computing instance;

The step of creating a cloud computing instance that meets the cloud computing instance creation requirement and returning cloud computing instance information of the created cloud computing instance to the tenant includes:

Determine a service model corresponding to the cloud computing instance creation requirement;

If it is determined that the service mode corresponding to the cloud computing instance creation requirement is the first service mode, creating a cloud computing instance that meets the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance to the tenant;

If it is determined that the service mode corresponding to the cloud computing instance creation requirement is the second service mode, a cloud computing instance that meets the cloud computing instance creation requirement is created, and the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource are returned to the tenant.
According to the method of claim 2, the creating a cloud computing instance that meets the cloud computing instance creation requirement, and returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant, comprises:

Creating a cloud computing instance that meets the cloud computing instance creation requirements, and creating a logical resource object corresponding to the target cloud computing resource, and returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the created logical resource object to the tenant; or,

Create a cloud computing instance that meets the cloud computing instance creation requirements, and obtain the logical resource object corresponding to the target cloud computing resource created in the resource management stage, and return the cloud computing instance information of the created cloud computing instance and the logical resource object information of the obtained logical resource object to the tenant.
According to the method of claim 2, the returning the cloud computing instance information of the created cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant comprises:

Returning the cloud computing instance information of the created cloud computing instance to the tenant;

In response to a query request submitted by the tenant for the logical resource object corresponding to the target cloud computing resource, logical resource object information of the logical resource object corresponding to the target cloud computing resource is returned to the tenant.
According to the method described in any one of claims 2 to 4, the object information of the logical resource object includes at least part of the data in the resource metadata of the cloud computing resource corresponding to the logical resource object.
The method according to claim 2, further comprising:

In response to a resource scheduling policy configured by the tenant based on the logical resource object information of the logical resource object, a cloud computing resource set matching the resource scheduling policy is determined from cloud computing resource sets corresponding to each resource management dimension as a candidate cloud computing resource set;

The step of determining, from the cloud computing resource sets corresponding to the respective resource management dimensions, the cloud computing resource sets corresponding to the at least part of the resource management dimensions comprises:

A cloud computing resource set corresponding to at least part of the resource management dimension is determined from the determined candidate cloud computing resource sets.
According to the method according to claim 1, the cloud computing instance includes a combination of one or more of the following: a container instance, a virtual machine instance, and an application instance.
According to the method of claim 7, the container instance includes: a container instance created on a virtual machine; and/or a bare metal container instance created on a physical machine.
According to the method of claim 1, the cloud computing resources include heterogeneous resources composed of cloud computing resources of multiple resource types;

The cloud computing resources include one or more combinations of the following: heterogeneous computing resources, heterogeneous storage resources, and heterogeneous network resources.
According to the method of claim 1, the at least one edge cloud node comprises an Internet data center IDC distributed in different location areas;

The at least one resource management dimension includes one or more combinations of the following: the location area where the edge cloud node equipped with cloud computing resources is located, the resource type of the cloud computing resources, and the operator to which the cloud computing resources belong.
A cloud computing instance creation device, the device is applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system also includes at least one edge cloud node interconnected with the central control device; the device includes:

A first creation unit is configured to manage the cloud computing resources carried by the at least one edge cloud node based on at least one resource management dimension, so as to create a cloud computing resource set corresponding to each resource management dimension in the at least one resource management dimension;

a determining unit, configured to, in response to a cloud computing instance creation requirement constructed by the tenant based on at least a part of the at least one resource management dimension, determine, from cloud computing resource sets corresponding to each resource management dimension, a cloud computing resource set corresponding to the at least part of the resource management dimension, and determine, from the determined cloud computing resource set, a target cloud computing resource matching the cloud computing instance creation requirement;

The second creation unit is used to schedule the target cloud computing resources to create a cloud computing instance that meets the cloud computing instance creation requirements on the edge cloud node equipped with the target cloud computing resources, and return the cloud computing instance information of the created cloud computing instance to the tenant.
An electronic device comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are interconnected via the bus;

The memory stores machine-readable instructions, and the processor executes the method according to any one of claims 1 to 10 by calling the machine-readable instructions.
A machine-readable storage medium storing machine-readable instructions, wherein the machine-readable instructions, when called and executed by a processor, implement the method according to any one of claims 1 to 10.