CN115361389A

CN115361389A - Cloud computing instance creation method and device

Info

Publication number: CN115361389A
Application number: CN202211288355.6A
Authority: CN
Inventors: 周晶; 任庚
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2022-10-20
Filing date: 2022-10-20
Publication date: 2022-11-18
Anticipated expiration: 2042-10-20
Also published as: WO2024082930A1; CN115361389B

Abstract

One or more embodiments of the present specification provide a cloud computing instance creation method and apparatus. The distributed edge cloud computing system comprises a central management and control device and at least one edge cloud node; the method comprises the following steps: the method comprises the steps that a central control device conducts resource admission on cloud computing resources carried on at least one edge cloud node based on at least one resource admission dimension to create cloud computing resource sets corresponding to the resource admission dimensions respectively; in response to a cloud computing instance creation requirement constructed by a tenant based on at least part of the resource hosting dimension, determining a target cloud computing resource matched with the cloud computing instance creation requirement from a cloud computing resource set corresponding to at least part of the resource hosting dimension; scheduling the target cloud computing resources to create a cloud computing instance meeting the cloud computing instance creation requirement on the edge cloud node carrying the target cloud computing resources, and returning the cloud computing instance information of the created cloud computing instance to the tenant.

Description

Cloud computing instance creation method and device

Technical Field

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

Background

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.

With the consideration of edge clouds, more central applications which are highly generic and suitable for operating at edge cloud nodes also sink towards the edge, and the demand for edge clouds is increasing. At present, in an edge cloud scene, an effective resource clouding and delivery scheme does not exist, and each cloud manufacturer generally delivers resource management and control logic to a user to realize the resource management and control logic.

In fact, in the process of using the cloud by the user at the edge, the main requirement is to stably and conveniently operate the service of the user on the edge cloud; in other words, the user expects that the service can be run directly by creating the corresponding instance at the edge cloud node according to the mirror image, and the user does not want to perform operation and maintenance work such as complex resource management and control at the edge cloud node. In other words, in order to bind users, the current "cloud-up gesture" (i.e. the specific operation manner of the cloud used by the user edge) provided by different cloud manufacturers is often five-fold rather than general; therefore, in the process of using the edge cloud computing services provided by different cloud vendors, a user generally needs to respectively implement resource management and control logic for different "cloud-up gestures" provided by different cloud vendors, so that the edge cloud efficiency and experience of the user are further reduced.

Disclosure of Invention

The application provides a cloud computing instance creating method, which is applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system further comprises at least one edge cloud node interconnected with the central management and control device; the method comprises the following steps:

performing resource admission on cloud computing resources loaded on the at least one edge cloud node based on at least one resource admission dimension to create a cloud computing resource set corresponding to each resource admission dimension in the at least one resource admission dimension;

responding to a cloud computing instance creation requirement constructed by a tenant based on at least part of the at least one resource management dimension, determining a cloud computing resource set corresponding to the at least part of the resource management dimension from cloud computing resource sets corresponding to the resource management dimensions respectively, and determining a target cloud computing resource matched with the cloud computing instance creation requirement from the determined cloud computing resource sets;

scheduling the target cloud computing resources to create a cloud computing instance meeting the cloud computing instance creation requirement on an edge cloud node carrying the target cloud computing resources, and returning cloud computing instance information of the created cloud computing instance to the tenant.

The application also provides a cloud computing instance creating device, which is applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system further comprises at least one edge cloud node interconnected with the central management and control device; the device comprises:

a first creating unit, configured to perform resource hosting on cloud computing resources hosted on the at least one edge cloud node based on at least one resource hosting dimension, so as to create a cloud computing resource set corresponding to each resource hosting dimension in the at least one resource hosting dimension;

a determining unit, configured to determine, in response to a cloud computing instance creation requirement that is constructed by a tenant based on at least part of the at least one resource hosting dimension, a cloud computing resource set corresponding to the at least part of the resource hosting dimensions from cloud computing resource sets respectively corresponding to the resource hosting dimensions, and determine, from the determined cloud computing resource sets, a target cloud computing resource that matches the cloud computing instance creation requirement;

and the second creating unit is used for scheduling the target cloud computing resources, creating a cloud computing instance meeting the cloud computing instance creating requirement on the edge cloud node loaded with the target cloud computing resources, and returning the cloud computing instance information of the created cloud computing instance to the tenant.

The application also provides an electronic device, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus;

the memory stores machine-readable instructions, and the processor executes the method by calling the machine-readable instructions.

The present application also provides a machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, implement the above-described method.

Through the above embodiments, on one hand, the central management and control device (i.e., the platform side) in the distributed edge cloud computing system can manage the resources of the cloud computing resources carried on the edge cloud nodes based on the at least one resource management and control dimension, so that the cloud computing resources are efficiently, flexibly and extendably distributed.

On the other hand, the central control device can conduct resource management on cloud computing resources based on the at least one resource management dimension, and the tenant can establish a cloud computing instance creation requirement based on the at least one resource management dimension, so that through a unified multi-dimensional resource modeling strategy, the process of resource management and cloud use of tenant edges can be conducted by the central control device while the process of cloud computing resource management and cloud computing instance production is decoupled, a resource management and instance production model is made transparent, and the edge cloud use efficiency of the tenant is improved.

On the other hand, in the process of edge cloud utilization, tenants do not need to pay attention to underlying physical resources corresponding to each edge cloud node and learn complex cloud utilization postures of each cloud manufacturer, and the tenants only need to construct cloud computing instance creation requirements based on at least one resource management dimension, so that the central control equipment can determine cloud computing resources matched with the cloud computing instance creation requirements from a cloud computing resource set as target cloud computing resources and can schedule the determined target cloud computing resources to create cloud computing instances meeting the cloud computing instance creation requirements on corresponding edge cloud nodes; the platform side can provide a more flexible, efficient and extensible edge cloud mode for the tenant in a cloud neutral posture, more service values are created for the tenant, the tenant cannot be bound by the platform side, and the edge cloud experience of the tenant can be improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments in the present specification, the drawings required to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments described in the present specification, and it is obvious for those skilled in the art that other drawings may be obtained according to these drawings without inventive labor.

FIG. 1 is a system architecture diagram of a distributed edge cloud computing system, in accordance with an exemplary embodiment;

FIG. 2 is a flow diagram illustrating a method for cloud computing instance creation in accordance with an illustrative embodiment;

FIG. 3 is a system architecture diagram of another distributed edge cloud computing system, shown in an exemplary embodiment;

fig. 4 is a schematic structural diagram of an electronic device in which a cloud computing instance creating apparatus is located according to an exemplary embodiment;

fig. 5 is a block diagram of a cloud computing instance creation apparatus, according to an example embodiment.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort shall fall within the protection scope of the present specification.

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 method 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 edge infrastructure based on the core of the cloud computing technology and the capability of edge computing; the edge cloud may also be referred to as an edge cloud computing system, an edge cloud computing platform, or the like.

Edge clouds are a relative concept that can be distinguished from a 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 a distributed edge cloud computing system according to an exemplary embodiment. As shown in fig. 1, edge cloud computing system 100 may include a central administration device 101, edge cloud nodes 102, edge cloud nodes 103, and edge cloud nodes 104; 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 is not intended to limit the present specification; in practical applications, the edge cloud computing system 100 may include at least one edge cloud node interconnected with the central managing device 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.

Wherein 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 (DC), a wireless room or cluster, an operator's communication network, core network devices, base stations, edge devices such as edge gateways, home gateways, computing devices or storage devices, and corresponding network environments, and so on. 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 system architecture of the edge cloud computing system shown in fig. 1, a center cloud corresponding to a center management and control device, an edge cloud formed by the at least one edge cloud node, and a terminal may form an end-to-end technical architecture of "cloud edge-to-end three-body cooperation". In the edge cloud computing system 100, the central management and control device 101 may use each edge cloud node (such as the edge cloud node 102, the edge cloud node 103, and the 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, operation and maintenance, network, security, and the like, so as to place cloud computing services into each edge cloud node for processing, so as to provide cloud computing services for users by means of various resources carried by the edge cloud node. Because the distance between the edge cloud node and the user terminal is closer, the response time delay of the cloud computing service can be reduced, the pressure of a central cloud corresponding to the edge cloud node 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, which is required for providing a cloud computing service for a user, and specifically may be a file that meets computing deployment requirements of an edge cloud node and is manufactured according to a certain format according to a specific series of files. In addition, the image may be in various forms, such as a Virtual Machine (VM) image file, a container (Docker) image file, or various types of application package files, and the image form may be related to virtualization technologies that the cloud computing service needs to use, which is not limited in this specification. Corresponding to mirroring, the implementation of an instance may be a virtual machine, a container, an application, or the like.

In addition, in the system architecture of the edge cloud computing system as shown in fig. 1, the edge cloud computing system 100 may include one or more edge management devices in addition to the center management device 101. The edge management and control equipment can be used for assisting and matching with the central management and control equipment to manage and control and schedule the at least one edge cloud node, so that the management and control and the scheduling of the central management and control equipment to the edge cloud node can be improved, and the purpose of fully utilizing edge resources is further achieved.

The edge management and control equipment can be deployed in one or more edge cloud nodes; specifically, each edge cloud node may include one or more resource devices, and the edge management and control device may be deployed on one or more resource devices; alternatively, each edge cloud node may include, in addition to the resource device, one or more proprietary devices that are different from the resource device and are dedicated to deployment of the edge management and control device, and the edge management and control device may be deployed on one or more proprietary devices. The edge management control device may also be deployed together with a central management control device, which is not limited in this specification.

With the consideration of edge clouds, more central applications which are highly generic and suitable for operating at edge cloud nodes also sink towards the edge, and the demand for edge clouds is increasing. At present, in an edge cloud scenario, there is no effective resource clouding and delivery scheme, and each cloud manufacturer usually hands over resource control to a user to implement the resource control, that is, the user usually needs to perform resource control on physical resources owned by the user to implement a resource control logic of the user.

In fact, in the process of using the cloud by the user at the edge, the main requirement is to stably and conveniently operate the service of the user on the edge cloud; in other words, the user expects that the service can be run directly by creating the corresponding instance at the edge cloud node according to the mirror image, and the user does not want to perform operation and maintenance work such as complex resource management and control at the edge cloud node. In other words, in order to bind users, the current "cloud-up gesture" provided by different cloud manufacturers is often five-door instead of general; the "cloud-up gesture" may include what cloud the user is on, and how to cloud the user, and may be used to indicate a specific operation manner of the user edge cloud; therefore, in the process of using edge cloud computing services provided by different cloud vendors, a user generally needs to respectively implement resource management and control logics of the user according to different "cloud-up gestures" provided by different cloud vendors, so that edge cloud utilization efficiency and experience of the user are further reduced.

Therefore, in the embodiment shown above, because the edge resources have the characteristics of distribution, heterogeneity, fusion, miniaturization, and wide coverage, compared with the traditional central cloud scenario, the complexity and difficulty of resource management and control and service operation and maintenance in the edge cloud computing scenario are higher, which results in lower efficiency of the edge cloud for the user, poorer experience of the edge cloud, and possibly causes waste of the edge resources.

In view of this, the present specification aims to provide a technical solution for uniformly performing resource management by a central management and control device in an edge cloud computing system based on one or more resource management dimensions (dimensions), so as to provide a set of convenient and easy-to-use edge cloud solutions for users.

When the resource management method is implemented, a central management and control device in a distributed edge cloud computing system may perform resource management on cloud computing resources hosted on at least one edge cloud node interconnected with the central management and control device in the edge cloud computing system based on at least one resource management and control dimension, so as to create a cloud computing resource set corresponding to each resource management and control dimension in the at least one resource management and control dimension; further, in response to a cloud computing instance creation requirement constructed by a tenant based on at least part of the at least one resource hosting dimension, the central management and control device may determine, from cloud computing resource sets respectively corresponding to the resource hosting dimensions, cloud computing resource sets corresponding to the at least part of the resource hosting dimensions, and may determine, from the determined cloud computing resource sets, a target cloud computing resource matching the cloud computing instance creation requirement; further, the central management and control device may schedule the target cloud computing resource to create a cloud computing instance meeting the creation requirement of the cloud computing instance on an edge cloud node carrying the target cloud computing resource, and return cloud computing instance information of the created cloud computing instance to the tenant.

Therefore, in the technical solution in this specification, on one hand, a central management and control device (i.e., a platform side) in the distributed edge cloud computing system can manage the resources of the cloud computing resources loaded on the edge cloud nodes based on the at least one resource management dimension, so as to efficiently, flexibly, and extendably implement resource cloud service.

On the other hand, in the process of edge cloud utilization, tenants do not need to pay attention to underlying physical resources corresponding to each edge cloud node and learn complex cloud utilization postures of each cloud manufacturer, and the tenants only need to construct cloud computing instance creation requirements based on at least one resource management dimension, so that the central control equipment can determine cloud computing resources matched with the cloud computing instance creation requirements from a cloud computing resource set as target cloud computing resources and can schedule the determined target cloud computing resources to create cloud computing instances meeting the cloud computing instance creation requirements on corresponding edge cloud nodes; the platform side can provide a more flexible, efficient and extensible edge cloud mode for the tenant in a cloud-neutral posture, more service values are created for the tenant, the tenant cannot be bound by the platform side, and edge cloud experience of the tenant can be improved.

The present application is described below by using specific embodiments and in conjunction with specific application scenarios.

Referring to fig. 2, fig. 2 is a flowchart illustrating a cloud computing instance creation method according to an exemplary embodiment. The method may be applied to a central administration device 101 as shown in fig. 1. The method may perform the steps of:

step 202: and performing resource management on cloud computing resources carried on at least one edge cloud node interconnected with a central management and control device in an edge cloud computing system based on 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.

In this specification, the resource nano-management may be understood as abstracting physical resources in the edge cloud computing system into manageable cloud computing resources through modeling and arrangement.

For example, the preset resource hosting dimension may include 3 resource hosting dimensions of a city (city), an equipment room (IDC, internet Data Center), and an operator (ISP, internet Service Provider); as shown in fig. 1, the central management and control device 101 may classify, based on 3 resource management dimensions of a city, a machine room, and an operator, cloud computing resources hosted on the edge cloud node 102, the edge cloud node 103, and the edge cloud node 104, and may create, based on a classification result, a cloud computing resource set corresponding to each resource management dimension.

Optionally, each resource nanotube dimension may include a plurality of resource nanotube sub-dimensions, and the cloud computing resource sets corresponding to the resource nanotube dimensions may include the cloud computing resource sub-sets corresponding to the resource nanotube dimensions.

For example, the resource nanotube dimension of the machine room may include resource nanotube sub-dimensions corresponding to different machine rooms (e.g., IDC1, IDC2, etc.), and then the cloud computing resource set corresponding to the machine room may be divided into cloud computing resource sub-sets corresponding to the machine rooms respectively; the cloud computing resource subset corresponding to the machine room IDC1 may include cloud computing resources deployed in the machine room IDC1.

It should be noted that, in the above illustrated embodiment, there may be an intersection or no intersection between the cloud computing resource sets corresponding to the resource nanotube dimensions, and this specification is not particularly limited to this. The plurality of cloud computing resource subsets included in the cloud computing resource set corresponding to a certain resource nano-management dimension have no intersection; for example, the subset of cloud computing resources corresponding to machine room IDC1 may include only the cloud computing resources deployed in machine room IDC1, but not the cloud computing resources deployed in other machine rooms.

In this specification, the cloud computing resources may still be in the form of physical resources or may also be in the form of logical resources. An MCU (Meta Control Unit) may be used as a minimum management and Control Unit for resource management, and an atomic management and Control capability may be encapsulated.

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

For another example, the physical resources may be abstracted into logical resources (e.g., 10GB of storage space, 100MB of bandwidth, etc.), and the logical resources may be converted into corresponding cloud computing resources according to the MCU. In one possible embodiment, the cloud computing resources may be further split or managed in groups according to actual requirements (such as the number of resources, etc.). For example, a storage medium can provide a storage space of 1TB, and a storage resource of 1TB corresponding to the storage medium can be split into a plurality of smaller storage resources, which is convenient for flexible scheduling and can avoid resource waste; and in addition, the other storage media can only respectively provide 1GB storage space, so that the 1GB corresponding to the storage media can be configured into a group, and the efficiency of resource management and resource scheduling in the edge cloud computing system is improved.

In addition, in the step 202, the central management and control device may further 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; the resource types may specifically include, but are not limited to, computational resources, storage resources, network resources, and the like.

For example, the cloud computing resources may include a combination of one or more of the following: heterogeneous computing resources, heterogeneous storage resources, and heterogeneous network resources. The heterogeneous computing resources may specifically include, but are not limited to, an x86 microprocessor, an ARM board card, a GPU (Graphics Processing Unit) resource, and the like; the heterogeneous storage resources may specifically include but are not limited to forms such as block storage, file storage, object storage, and the like; the heterogeneous Network resources may specifically include, but are not limited to, VPC (Virtual Private Cloud), LB (Load Balance), NAT (Network Address Translation), and the like.

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 nanotube dimension may include a combination of one or more of the following: the method comprises the steps of loading the position area where the edge cloud node of the cloud computing resource is located, the resource type of the cloud computing resource and an operator to which the cloud computing resource belongs.

For example, according to different coverage areas of a location area, resource management dimensions such as country (county), province (province), area (such as east China, north China, etc.), city (city), etc. may be configured; according to the construction mode of the distributed data center, resource management dimensions such as a data center (IDC) and an edge node service room (ENS room) can be configured; according to the resource type of the cloud computing resource, the resource nano-management dimensions such as operation resources, storage resources and network resources can be configured.

It should be noted that, regarding the specific dimension of the at least one resource nanotube dimension, those skilled in the art may flexibly configure and expand according to actual needs, and the description is not particularly limited, and cannot be exhaustive.

Step 204: in response to a cloud computing instance creation requirement constructed by a tenant based on at least part of the at least one resource hosting dimension, determining a cloud computing resource set corresponding to the at least part of the resource hosting dimension from cloud computing resource sets corresponding to the resource hosting dimensions respectively, and determining a target cloud computing resource matched with the cloud computing instance creation requirement from the determined cloud computing resource sets.

For example, the central management and control device 101 may classify cloud computing resources hosted by the edge cloud nodes 102, 103, and 104 based on 3 resource management dimensions, such as a city, a machine room, and an operator, and may create a cloud computing resource set corresponding to each resource management dimension based on a classification result; correspondingly, a tenant corresponding to a terminal can construct a cloud computing instance creation requirement based on at least part of the 3 resource hosting dimensions; in response to that a tenant establishes a demand of [ Hangzhou city, resource quantity, \ 8230; ] ] for establishing a cloud computing instance based on the resource management dimension of the city, the central management and control device 101 may determine a cloud computing resource set corresponding to the resource management dimension of the city from cloud computing resource sets respectively corresponding to 3 resource management dimensions of the city, the machine room, and the operator, and may further determine a cloud computing resource matched with the cloud computing instance establishment demand [ Hangzhou city, resource quantity, \8230; ], and 8230 ], as a target cloud computing resource to be scheduled, from the cloud computing resource set corresponding to the resource management dimension of the city.

In one possible embodiment, the central control device may provide a requirement submission entry (e.g., open API) externally, where the requirement submission entry may be a web page, an application page, a command window, or the like; the requirement submitting inlet can be used for a tenant to submit a cloud computing instance creating requirement, namely description information for the cloud computing instance to be created, to the central control device. Wherein the cloud computing instance creation requirement may include, but is not limited to, an edge cloud node selection parameter and/or a resource selection parameter; the edge cloud node selection parameters may include a scheduling domain and/or performance requirements for edge cloud nodes, and the like; the resource selection parameters may include resource type, resource quantity, and performance requirements for the resource device. Further, the central management and control device may perform resource scheduling on the at least one edge cloud node according to the cloud computing instance creation requirement, so that the scheduled edge cloud node creates a cloud computing instance for a tenant based on the scheduled cloud computing resource, or so that the scheduled edge cloud node reserves the scheduled cloud computing resource for the tenant.

In one illustrated embodiment, the cloud computing instances may be divided into a plurality of instance types. In implementation, the cloud computing instance may specifically include a combination of one or more 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, or may include heterogeneous cloud computing resources.

Step 206: scheduling the target cloud computing resources to create a cloud computing instance meeting the cloud computing instance creation requirement on an edge cloud node carrying the target cloud computing resources, and returning cloud computing instance information of the created cloud computing instance to the tenant.

For example, in response to a cloud computing instance creation requirement submitted by a tenant being [ hangzhou city, resource quantity, \8230 ], the central management and control device 101 may, after determining a target cloud computing resource matching the cloud computing instance creation requirement, schedule the determined target cloud computing resource to create a cloud computing instance satisfying the cloud computing instance creation requirement on an edge cloud node carrying the target cloud computing resource, and may return cloud computing instance information of the created cloud computing instance to the tenant, that is, may deliver the cloud computing instance produced by the edge cloud node carrying the target cloud computing resource to the tenant.

In step 206, one possible resource scheduling manner includes: the central control device 101 may determine an edge cloud node carrying the target cloud computing resource as a target edge cloud node; and controlling corresponding resource equipment in the target edge cloud node to perform resource allocation or resource reservation according to the resource metadata of the target cloud computing resource so as to provide corresponding cloud computing service for the tenant by using the scheduled target cloud computing resource in the target edge cloud node.

In order to enable those skilled in the art to better understand the technical solution in the embodiment of the present disclosure, the embodiment of the present disclosure is described below with reference to an architecture diagram shown in fig. 3, taking the cloud computing example as a container example, and the edge cloud nodes as IDCs distributed in different location areas as an example.

Referring to fig. 3, fig. 3 is a schematic diagram of a system architecture of another distributed edge cloud computing system according to an exemplary embodiment. One or more cloud computing instance creation methods provided by the present specification may be applied to the central management and control device 301 shown in fig. 3. As shown in fig. 3, the at least one edge cloud node interconnected with the central management and control device 301 may include IDC1, IDC2, \8230, etc.

Each of the at least one edge cloud node may be loaded with cloud computing resources of different resource types. The central management and control device 301 may perform resource management on the cloud computing resources hosted on the edge cloud node based on the 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 central management and control device 301 may also provide an open API to the outside as a submission entry for a cloud computing instance creation requirement; so that the tenant can submit the cloud computing instance creation requirement to the central control device 301 through the open API.

In this specification, the central management and control device creates a service for a cloud computing instance provided by a tenant, and may include a first service mode and a second service mode; the first service mode can comprise a service mode that a tenant does not sense a logic resource object corresponding to a cloud computing resource used for creating a cloud computing instance; the second service pattern may include a service pattern that a tenant may perceive a logical resource object corresponding to a cloud computing resource used to create a cloud computing instance.

Wherein, the first service mode may be a Serverless mode; in this service mode, the tenant may only need to use the edge cloud conveniently and efficiently, so that only the cloud computing instance delivered for the tenant meeting the cloud computing instance creation requirement may be obtained, and the tenant does not care about the target cloud computing resources for creating the cloud computing instance.

Wherein, the second service mode may be a Node-Aware mode, which may also be referred to as an LRO-Aware mode; in this service model, the tenant needs to know the target cloud computing resource for creating the cloud computing instance in addition to the edge cloud being used conveniently and efficiently, and therefore, in addition to delivering the cloud computing instance satisfying the cloud computing instance creation requirement for the tenant, the tenant needs to return the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant.

In implementation, in the step 206, the creating a cloud computing instance meeting the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance to the tenant may specifically include: determining a service mode corresponding to the cloud computing instance creation requirement; if the service mode corresponding to the cloud computing instance creation requirement is determined to be the first service mode, creating a cloud computing instance meeting the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance to the tenant; and if the service mode corresponding to the cloud computing instance creation requirement is determined to be the second service mode, creating a cloud computing instance meeting the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance and logic resource object information of a logic resource object corresponding to the target cloud computing resource to the tenant.

For example, as shown in fig. 3, in response to a container instance creation requirement (for example, n xx containers are opened at some place, n may be any positive integer) constructed by tenant a based on at least a part of the at least one resource hosting dimension, the central management and control device 301 may determine, from a set of cloud computing resources corresponding to each resource hosting dimension, a target cloud computing resource matching the container instance creation requirement; further, the central management and control device 301 may determine that the service mode corresponding to the container instance creation requirement is a Serverless mode, and may schedule the target cloud computing resource, so as to create a container instance Pod a meeting the container instance creation requirement on the edge cloud node IDC1 loaded with the target cloud computing resource, and may return container instance information of the created container instance Pod a to the tenant a.

It should be noted that, in the above illustrated 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, an instance identifier of the container instance, a creation time of the container instance, a number of containers included in the container instance, container specifications of respective containers included in the container instance, and the like.

For another example, as shown in fig. 3, in response to a first container instance creation requirement and a second container instance creation requirement that are constructed by tenant B based on at least part of the at least one resource hosting dimension, the central management and control device 301 may determine, from the cloud computing resource sets respectively corresponding to the resource hosting dimensions, a first target cloud computing resource matching the first container instance creation requirement and a second target cloud computing resource matching the second container instance creation requirement; further, the central management and control device 301 may determine that a service mode corresponding to the first container instance creation requirement and the second container instance creation requirement is a Node-Aware mode, and may schedule the first target cloud computing resource and the second target cloud computing resource to create a container instance PodB1 meeting the first container instance creation requirement on an edge cloud Node IDC1 carrying the first target cloud computing resource, create a container instance Pod B2 meeting the second container instance creation requirement on an edge cloud Node IDC2 carrying the second target cloud computing resource, and return container instance information of the created container instance PodB1 and container instance Pod B2 to the tenant B.

It should be noted that, in the above illustrated embodiment, according to that the container instance Pod B1 and the container instance Pod B2 created for the tenant B are respectively located on the edge cloud node IDC1 and the edge cloud node IDC2, it can be known that in the technical solution of the present specification, an edge cloud node where the container instance created for the tenant is located is mainly related to a container instance creation requirement constructed by the tenant, and does not necessarily depend on that the tenant is closer to each edge cloud node.

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

In practical applications, the logical resource object may be created in a cloud computing resource hosting phase, or may be generated in a cloud computing instance creation phase.

In one embodiment, the logical resource object corresponding to the target cloud computing resource may be created during a cloud computing resource hosting phase. In implementation, the creating a cloud computing instance meeting the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance and logical resource object information of a logical resource object corresponding to the target cloud computing resource to the tenant, which may specifically include: and creating a cloud computing instance meeting the creation requirement of the cloud computing instance, acquiring a logic resource object which is created in a resource storage and management stage and corresponds to the target cloud computing resource, and returning cloud computing instance information of the created cloud computing instance and the acquired logic resource object information of the logic resource object to the tenant.

For example, in the step 202, when resource admission is performed on cloud computing resources hosted on the at least one edge cloud node to create a cloud computing resource set corresponding to each resource admission dimension, a corresponding logical resource object may be created for each cloud computing resource included in the created cloud computing resource set, and a logical resource object identifier for globally and uniquely identifying the logical resource object may be allocated to each logical resource object; subsequently, in response to a first container instance creation requirement constructed by tenant B, the central management and control device 301 may determine a first target cloud computing resource matching the first container instance creation requirement; further, the central management and control device 301 determines that the service mode corresponding to the first container instance creation requirement is a Node-Aware mode, and may schedule the first target cloud computing resource to create a container instance Pod B1 meeting the first container instance creation requirement on an edge cloud Node IDC1 carrying the first target cloud computing resource, may obtain a logical resource object id c1.Node1 corresponding to the first target cloud computing resource created at a resource admission management stage, and may return container instance information of the created container instance Pod B1 and logical resource object information of the logical resource object id c1.Node1 to the tenant B.

In another embodiment shown, the logical resource object corresponding to the target cloud computing resource may be created during a cloud computing instance creation phase. In implementation, the creating a cloud computing instance meeting the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance and logical resource object information of a logical resource object corresponding to the target cloud computing resource to the tenant, which may specifically include: and creating a cloud computing instance meeting the creation requirement of the cloud computing instance, creating a logic resource object corresponding to the target cloud computing resource, and returning cloud computing instance information of the created cloud computing instance and logic resource object information of the created logic resource object to the tenant.

For example, in response to a second container instance creation requirement constructed by tenant B, the central managing and controlling device 301 may determine a second target cloud computing resource matching the second container instance creation requirement; further, the central management and control device 301 determines that the service mode corresponding to the second container instance creation requirement is a Node-Aware mode, may schedule the second target cloud computing resource to create a container instance Pod B2 meeting the second container instance creation requirement on an edge cloud Node IDC2 carrying the second target cloud computing resource, may create a logical resource object IDC2.Node1 corresponding to the second target cloud computing resource, and may return container instance information of the created container instance Pod B2 and logical resource object information of the logical resource object IDC2.Node1 to the tenant B.

It should be noted that, in the above illustrated embodiment, the "Node" in the Node-Aware schema is not a certain edge cloud Node or a certain entity device in the edge cloud computing system, but a logical resource object corresponding to a cloud computing resource. The logic resource object which can be perceived by the tenant may include a logic resource object corresponding to the cloud computing resource allocated or reserved by the central control device for the tenant.

In one illustrated embodiment, in the second service mode, although a tenant has a sensing capability for a logical resource object corresponding to the target cloud computing resource, the tenant does not necessarily need to enable the sensing capability at once; therefore, in the process of delivering the cloud computing instance to the tenant, only the cloud computing instance information of the created cloud computing instance can be returned to the tenant by default, and the logic resource object information of the logic resource object which is allowed to be perceived by the tenant is temporarily not directly returned to the tenant; and providing the logic resource object information of the logic resource object which allows the tenant to sense for the tenant until the tenant actively queries.

In implementation, the returning the created cloud computing instance information of the 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 created cloud computing instance information of the cloud computing instance to the tenant; and responding to a query request which is submitted by the tenant and aims at the logical resource object corresponding to the target cloud computing resource, and returning the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant.

In one or more of the above-described embodiments, the object information of the logical resource object may specifically include at least part of data in the resource metadata of the cloud computing resource corresponding to the logical resource object. It should be noted that, in this case, because "logical resource object information-logical resource object-cloud computing resource-resource metadata of cloud computing resource" corresponds to each other, at most, the tenant can perceive the logical resource object, and the resource metadata of cloud computing resource and the logical resource metadata corresponding to the cloud computing resource are uniformly maintained by the central management and control device, so that data consistency can be ensured. In the related art, under the condition that the tenant manages the owned resources, the problem of inconsistent data may occur because the resource information maintained by the tenant is not synchronized to the management and control device in the edge cloud computing system in time.

In an embodiment shown in the figure, in the second service mode, the tenant is supported to construct its own resource control unit according to the obtained logical resource object of the logical resource object and the business requirement, so that the edge cloud utilization efficiency of the tenant is improved.

When implemented, prior to or concurrently with the step 204, the method may further comprise: responding to a resource scheduling strategy configured by a tenant based on the logical resource object information of the logical resource object, and determining a cloud computing resource set matched with the resource scheduling strategy from cloud computing resource sets respectively corresponding to the resource receiving and managing dimensions as a candidate cloud computing resource set; in this case, the determining, from the cloud computing resource sets respectively corresponding to the resource nanotube dimensions, the cloud computing resource set corresponding to the at least part of resource nanotube dimensions may specifically include: and determining a cloud computing resource set corresponding to the at least part of the resource nano-management dimensions from the determined candidate cloud computing resource set.

Continuing to illustrate the above illustrated embodiment, after obtaining the logical resource object information of the logical resource object returned by the central control device, the tenant may configure a corresponding resource scheduling policy according to the logical resource object information and the actual service requirement, and may submit the resource scheduling policy to the central control device; in response to a resource scheduling policy configured by a tenant based on the logical resource object information of the logical resource object, the central management and control device may determine, from the created cloud computing resource sets respectively corresponding to the resource hosting dimensions, a cloud computing resource set matched with the resource scheduling policy as a candidate cloud computing resource set; further, in response to a cloud computing instance creation requirement constructed by the tenant based on at least part of the at least one resource hosting dimension, the central management and control device may further determine, from the determined candidate cloud computing resource sets, a cloud computing resource set corresponding to the at least part of the resource hosting dimension.

It should be noted that, in the above illustrated embodiment, under the condition that a tenant can perceive logical resource object information of a logical resource object corresponding to the target cloud computing resource, the tenant may customize a resource scheduling policy according to an actual business requirement, which is equivalent to a process of determining the target cloud computing resource for a central control device in response to a cloud computing instance creation requirement constructed by the tenant, and the resource scheduling policy is used as an increased constraint condition, so that efficiency of determining the target cloud computing resource may be improved, and further, efficiency of creating a cloud computing instance for the tenant is improved.

According to the technical scheme, on one hand, the central control equipment (namely, the platform side) in the distributed edge cloud computing system can carry out resource management on the cloud computing resources carried on the edge cloud nodes based on the at least one resource management dimension, so that the cloud computing resources can be efficiently, flexibly and extendably loaded on the cloud.

On the other hand, the central control device can conduct resource admission on the cloud computing resources based on the at least one resource admission dimension, and the tenant can establish a cloud computing instance creation requirement based on the at least one resource admission dimension, so that through a unified multi-dimensional resource modeling strategy, the central control device can be opened to conduct a resource admission and tenant edge cloud using process while the cloud computing resource admission and cloud computing instance production process is decoupled, a resource admission and instance production model is made transparent, and tenant edge cloud using efficiency is improved.

Corresponding to the embodiment of the cloud computing instance creating method, the specification also provides an embodiment of a cloud computing instance creating device.

Referring to fig. 4, fig. 4 is a hardware structure diagram of an electronic device in which a cloud computing instance creating apparatus is located according to 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, although it may include hardware required for other services. One or more embodiments of the present description may be implemented in software, such as by processor 402 reading corresponding computer programs from non-volatile storage 410 into memory 408 and then executing. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 5, fig. 5 is a block diagram of a cloud computing instance creation apparatus according to an exemplary embodiment. The cloud computing instance creating apparatus may be applied to an electronic device as shown in fig. 4 to implement the technical solution of the present specification. The device is applied to a central management and control device in a distributed edge cloud computing system; the edge cloud computing system further comprises at least one edge cloud node interconnected with the central management and control device; the apparatus may include:

a first creating unit 502, configured to perform resource hosting on cloud computing resources hosted on the at least one edge cloud node based on at least one resource hosting dimension, so as to create a cloud computing resource set corresponding to each resource hosting dimension in the at least one resource hosting dimension;

a determining unit 504, configured to, in response to a cloud computing instance creation requirement that is constructed by a tenant based on at least part of the at least one resource hosting dimension, determine, from cloud computing resource sets respectively corresponding to the resource hosting dimensions, a cloud computing resource set corresponding to the at least part of the resource hosting dimensions, and determine, from the determined cloud computing resource set, a target cloud computing resource that matches the cloud computing instance creation requirement;

a second creating unit 506, configured to schedule the target cloud computing resource, to create a cloud computing instance meeting the cloud computing instance creation requirement on an edge cloud node loaded with the target cloud computing resource, and return cloud computing instance information of the created cloud computing instance to the tenant.

In this embodiment, the central management and control device creates a service for a cloud computing instance provided by a tenant, where the service includes a first service mode and a second service mode; the first service mode comprises a service mode that a tenant does not sense a logic resource object corresponding to a cloud computing resource used for creating a cloud computing instance; the second service mode comprises a service mode which can be perceived by a tenant of a logical resource object corresponding to a cloud computing resource used for creating a cloud computing instance;

the second creating unit 506 is specifically configured to:

determining a service mode corresponding to the cloud computing instance creation requirement;

if the service mode corresponding to the cloud computing instance creation requirement is determined to be the first service mode, creating a cloud computing instance meeting the cloud computing instance creation requirement, and returning cloud computing instance information of the created cloud computing instance to the tenant;

and if the service mode corresponding to the cloud computing instance creation requirement is determined to be the second service mode, creating the cloud computing instance meeting 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.

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

creating a cloud computing instance meeting the creation requirement of the cloud computing instance, creating a logic resource object corresponding to the target cloud computing resource, and returning cloud computing instance information of the created cloud computing instance and logic resource object information of the created logic resource object to the tenant; alternatively, the first and second electrodes may be,

and creating a cloud computing instance meeting the creation requirement of the cloud computing instance, acquiring a logic resource object which is created in a resource storage and management stage and corresponds to the target cloud computing resource, and returning cloud computing instance information of the created cloud computing instance and the acquired logic resource object information of the logic resource object to the tenant.

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

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

and responding to a query request which is submitted by the tenant and aims at the logic resource object corresponding to the target cloud computing resource, and returning the logic resource object information of the logic resource object corresponding to the target cloud computing resource to the tenant.

In this embodiment, the object information of the logical resource object includes at least part of 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:

responding to a resource scheduling strategy configured by a tenant based on the logical resource object information of the logical resource object, and determining a cloud computing resource set matched with the resource scheduling strategy from cloud computing resource sets respectively corresponding to the resource receiving and managing dimensions as a candidate cloud computing resource set;

determining, from the cloud computing resource sets respectively corresponding to the resource nanotube dimensions, a cloud computing resource set corresponding to the at least part of the resource nanotube dimensions, including:

and determining a cloud computing resource set corresponding to the at least part of the resource nano-management dimensions from the determined candidate cloud computing resource set.

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

In this embodiment, the container example includes: a container instance created on a virtual machine; and/or bare metal container instances 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 a combination of one or more of the following: heterogeneous computing resources, heterogeneous storage resources, and heterogeneous network resources.

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

the at least one resource nanotube dimension comprising a combination of one or more of the following: the method comprises the steps of loading the position area where the edge cloud node of the cloud computing resource is located, the resource type of the cloud computing resource and an operator to which the cloud computing resource belongs.

The specific details of the implementation process of the functions and actions of each unit in the above device are the implementation processes of the corresponding steps in the above method, and are not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are only illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the present specification. One of ordinary skill in the art can understand and implement it without inventive effort.

The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented 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 phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or apparatus comprising 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 this 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 in one or more embodiments of the present description 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 \8230; \8230when" or "when 8230; \823030when" 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

1. A cloud computing instance creating method is applied to a central control device in a distributed edge cloud computing system; the edge cloud computing system also comprises at least one edge cloud node interconnected with the central management and control equipment; the method comprises the following steps:

2. The method according to claim 1, wherein the central management and control device creates a service for the cloud computing instance provided by the tenant, and the service comprises a first service mode and a second service mode; the first service mode comprises a service mode that a tenant does not sense a logic resource object corresponding to a cloud computing resource used for creating a cloud computing instance; the second service mode comprises a service mode which can be perceived by a tenant of a logical resource object corresponding to a cloud computing resource used for creating a cloud computing instance;

the creating of the cloud computing instance meeting the cloud computing instance creating requirement and the returning of the cloud computing instance information of the created cloud computing instance to the tenant comprise:

and if the service mode corresponding to the cloud computing instance creation requirement is determined to be the second service mode, creating the cloud computing instance meeting the cloud computing instance creation requirement, and returning the cloud computing instance information of the created cloud computing instance and the logic resource object information of the logic resource object corresponding to the target cloud computing resource to the tenant.

3. The method of claim 2, wherein the creating of the cloud computing instance meeting the cloud computing instance creation requirement and the returning of the created cloud computing instance information of the cloud computing instance and the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant comprise:

creating a cloud computing instance meeting the requirement for creating the cloud computing instance, creating a logic resource object corresponding to the target cloud computing resource, and returning cloud computing instance information of the created cloud computing instance and logic resource object information of the created logic resource object to the tenant; alternatively, the first and second electrodes may be,

4. The method of claim 2, the returning cloud computing instance information for the created cloud computing instance and logical resource object information for a logical resource object corresponding to the target cloud computing resource to the tenant, comprising:

and responding to a query request which is submitted by the tenant and aims at the logical resource object corresponding to the target cloud computing resource, and returning the logical resource object information of the logical resource object corresponding to the target cloud computing resource to the tenant.

5. The method of any of claims 2-4, the object information of the logical resource object comprising at least a portion of data in resource metadata of a cloud computing resource corresponding to the logical resource object.

6. The method of claim 2, further comprising:

and determining a cloud computing resource set corresponding to the at least part of resource nano-management dimensions from the determined candidate cloud computing resource set.

7. The method of claim 1, the cloud computing instance, comprising a combination of one or more of the following: container instance, virtual machine instance, application instance.

8. The method of claim 7, the container instance, comprising: a container instance created on a virtual machine; and/or bare metal container instances created on a physical machine.

9. The method of claim 1, the cloud computing resources comprising heterogeneous resources comprised of cloud computing resources of multiple resource types;

10. The method of claim 1, the at least one edge cloud node comprising Internet Data Centers (IDCs) distributed in different location areas;

11. A cloud computing instance creating device is applied to a central management and control device in a distributed edge cloud computing system; the edge cloud computing system further comprises at least one edge cloud node interconnected with the central management and control device; the device comprises:

and the second creating unit is used for scheduling the target cloud computing resources, creating a cloud computing instance meeting the creation requirement of the cloud computing instance on an edge cloud node carrying the target cloud computing resources, and returning the cloud computing instance information of the created cloud computing instance to the tenant.

12. An electronic device comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory has stored therein machine-readable instructions, which the processor executes by calling to perform the method of any one of claims 1 to 10.

13. A machine readable storage medium having stored thereon machine readable instructions which, when invoked and executed by a processor, carry out the method of any of claims 1 to 10.