Logic node configuration method based on cloud service and cloud management platform

Abstract

The invention discloses a logic node configuration method based on cloud service and a cloud management platform, which can meet the customization requirement of a tenant on the specification of physical equipment used by a logic node. The method comprises the following steps: a cloud management platform receives a logic node creation request for a logic node of a tenant sent by the tenant, and the cloud management platform can create a logic node from each physical device pool because the logic node creation request is used for indicating a logic node specification demand set by the tenant for the logic node; the method comprises the following steps: selecting idle physical equipment which meets the specification requirement of a logic node according to the specification requirement of the logic node, and creating the logic node on the physical equipment, the logic node comprising virtual equipment realized on the basis of the physical equipment, so that the cloud management platform can install an operating system mirror image formulated by a tenant on the logic node; therefore, the logic node installed with the operating system mirror image can allow the tenant to remotely log in.

Description

[0001] This application claims priority to Chinese patent application filed on June 19, 2024, with application number 202410799269.4 and entitled "A Node Creation Method Based on a Cloud Management Platform and a Cloud Management Platform", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of cloud technology, and in particular to a logical node configuration method and cloud management platform based on cloud services. Background Technology

[0003] With the rapid development of cloud technology, more and more tenants are choosing logical nodes provided by cloud vendors to complete their business. These logical nodes are usually created based on cloud resources deployed in the cloud by cloud vendors, so that the logical nodes can provide remote cloud services to tenants and thus meet the various business needs of tenants.

[0004] In related technologies, cloud service systems provided by cloud vendors can include cloud management platforms and infrastructure, which contains cloud resources of various specifications. When a tenant needs to create a dedicated logical node in the cloud, the cloud management platform provides the tenant with various cloud resources of pre-defined specifications that can be used to build the logical node. The tenant can then select and combine these cloud resources to determine the final cloud resources used to build the logical node. Based on this, the cloud management platform can create the tenant's logical node on these cloud resources to provide cloud services to the tenant.

[0005] In the process described above, in order to meet the requirements of tenants who want to freely customize the specifications of logical nodes, the cloud management platform needs to create a sufficient number of cloud resources of various specifications for tenants to choose from and combine. This will result in a significant increase in the resource management costs of the cloud management platform, and often still cannot meet the various customization requirements of tenants for resource specifications. Summary of the Invention

[0006] This application provides a method for configuring logical nodes based on cloud services and a cloud management platform, which not only helps reduce the consumption of resources when the cloud management platform performs resource management, but also meets the tenant's customization requirements for the specifications of the physical devices used by the logical nodes.

[0007] The first aspect of this application provides a logical node configuration method based on cloud services. This method is applied to a cloud management platform, which manages infrastructure including CPU device pools, memory device pools, network interface card (NIC) device pools, and disk device pools. Multiple CPUs in the CPU device pool, multiple memory modules in the memory device pool, multiple NICs in the NIC device pool, and multiple disks in the disk device pool are all connected to a high-speed interconnect network. The high-speed interconnect network is used to enable physical devices in each physical device pool within and between pools. The method includes:

[0008] When a tenant needs to create its own logical node, the cloud management platform can provide a creation interface. The tenant can then input a logical node creation request for that logical node into the creation interface. In this way, the cloud management platform can receive the logical node creation request sent by the tenant through the creation interface. It is worth noting that the logical node creation request includes the logical node specification requirements set by the tenant for that logical node, including CPU requirements, memory requirements, network interface card requirements, and disk requirements.

[0009] Upon receiving a logical node creation request for a specific logical node, the cloud management platform can parse the logical node specification requirements from the request. Since these requirements include CPU, memory, network interface card (NIC) requirements, and disk requirements, the cloud management platform can select idle CPUs that meet the CPU requirements from the CPU device pool, idle memory modules that meet the memory requirements from the memory device pool, idle NICs that meet the NIC requirements from the NIC device pool, and idle disks that meet the disk requirements from the disk device pool. Then, the cloud management platform can create the logical node on these CPUs, memory modules, NICs, and disks. This logical node includes virtual CPUs implemented based on these CPUs, virtual memory modules implemented based on these memory modules, virtual NICs implemented based on these NICs, virtual disks implemented based on these disks, and a virtual bus network. It should be noted that within this logical node, these CPUs, memory modules, NICs, and disks can communicate with each other through this sub-network; similarly, these virtual CPUs, virtual memory modules, virtual NICs, and virtual disks can communicate with each other through the virtual bus network implemented based on this sub-network.

[0010] After creating the logical node, the cloud management platform can prompt the tenant to specify an operating system image. The cloud management platform can then install the tenant-specified operating system image on the logical node. This logical node, with the operating system image installed, can be remotely logged into by the tenant to schedule virtual devices on that logical node to complete the tenant's business operations, thereby meeting the tenant's business needs.

[0011] As can be seen from the above method, since the logical node specification requirements set by the tenant for the logical node can be used to describe the specifications of various physical devices (including CPU, memory, network card, and disk, etc.) required to create the logical node, it is evident that the specifications of the physical devices required to create the logical node can be freely customized by the tenant. The cloud management platform only needs to select and provide physical devices that match these specifications to complete the creation of the logical node and provide it to the tenant for use. This helps to reduce the consumption of the cloud management platform when performing resource management and can also meet the tenant's customization requirements for the specifications of the physical devices used by the logical node.

[0012] In one possible implementation, the method further includes: a cloud management platform obtaining a logical node specification expansion request input by a tenant, the logical node specification expansion request requesting to expand one or any combination of virtual CPUs, virtual memory, virtual network interface cards (NICs), and virtual disks to a predetermined specification; the cloud management platform selecting a corresponding idle device from one or any combination of CPU device pools, memory device pools, NIC device pools, and disk device pools according to the logical node specification expansion request, wherein the idle device matches the predetermined specification; and the cloud management platform connecting the idle device to the virtual bus network. In the aforementioned implementation, when a tenant needs to expand the logical node, the cloud management platform can provide the tenant with an expansion interface. Then, the tenant can input a logical node specification expansion request for the logical node into the expansion interface, the logical node specification expansion request requesting to expand one or any combination of the virtual CPUs, virtual memory, virtual NICs, and virtual disks contained in the logical node to the predetermined specification set by the tenant. Based on a logical node expansion request, the cloud management platform selects available devices from one or any combination of CPU, memory, network interface card (NIC), and disk device pools. The specifications of the selected available devices match the predefined specifications set by the tenant. After determining the available devices, the cloud management platform connects them to the virtual bus network of the logical node. Thus, the physical devices used to implement the virtual CPUs, virtual memory, virtual NICs, and virtual disks in this logical node include not only the original CPUs, extended processors, memory, NICs, and disks, but also the available devices. Therefore, the specifications of one or any combination of the physical devices for these virtual CPUs, virtual memory, virtual NICs, and virtual disks in the logical node increase, successfully expanding the logical node's capacity. This demonstrates that if a tenant needs to expand a logical node, the cloud management platform can provide additional available devices to the logical node without interrupting the tenant's business operations. This not only meets the tenant's expansion needs but also ensures normal business operation, thereby improving the tenant's experience.

[0013] In one possible implementation, the method further includes: a cloud management platform obtaining a logical node specification scaling-down request input by a tenant, the logical node specification scaling-down request requesting that one or any combination of virtual CPUs, virtual memory, virtual network interface cards, and virtual disks be scaled down to a predetermined specification; the cloud management platform, based on the logical node specification scaling-down request, controls the devices mapped to one or any combination of virtual CPUs, virtual memory, virtual network interface cards, and virtual disks to exit the virtual bus network, and marks the device status as idle. In the aforementioned implementation, when a tenant needs to scale down the logical node, the cloud management platform can provide a scaling-down interface to the tenant. Then, the tenant can input a logical node specification scaling-down request for the logical node into the scaling-down interface, the logical node specification scaling-down request requesting that one or any combination of the virtual CPUs, virtual memory, virtual network interface cards, and virtual disks contained in the logical node be scaled down to the predetermined specification set by the tenant. Based on a logical node scaling-down request, the cloud management platform controls the devices mapped to one or any combination of virtual CPUs, virtual memory, virtual network cards, and virtual disks within that logical node to exit the virtual bus network and marks these exited devices as idle. This reduces the number of physical devices used to implement these virtual CPUs, virtual memory, virtual network cards, and virtual disks in the logical node, thus shrinking the size of one or any combination of these physical devices and successfully scaling down the logical node. If a tenant needs to scale down the logical node, the cloud management platform can remove the original devices from the logical node without interrupting the tenant's business operations. This not only meets the tenant's scaling-down needs but also ensures normal business operation, thereby improving the tenant's experience.

[0014] In one possible implementation, the infrastructure further includes an extended processor device pool comprising multiple extended processors connected to a high-speed interconnect network. The logical node specification creation request also includes extended processor requirements. The logical node further includes virtual extended processors logically connected to a bus network, and these virtual extended processors are mapped to at least one idle extended processor in the extended processor device pool that meets the extended processor requirements. In the aforementioned implementation, when the logical node specification requirements may also include extended processor requirements, the cloud management platform may select idle extended processors that meet the extended processor requirements from the extended processor device pool and create the logical node on these CPUs, these extended processors, these memories, these network interface cards (NICs), and these disks. Accordingly, the logical node includes virtual CPUs implemented based on these CPUs, virtual extended processors implemented based on these extended processors, virtual memory implemented based on these memories, virtual network interface cards (NICs) implemented based on these NICs, virtual disks implemented based on these disks, and a virtual bus network. The virtual bus network can be logically connected to these virtual CPUs, virtual extended processors, virtual memory, virtual network cards, and virtual disks respectively, that is, these virtual CPUs, virtual extended processors, virtual memory, virtual network cards, and virtual disks can communicate with each other through the virtual bus network.

[0015] In one possible implementation, the extended processor type of the extended processor device pool is one or any combination of NPU, GPU, TPU, and DPU.

[0016] In one possible implementation, high-speed interconnect networks are achieved through PCIe networks, IB networks, or CXL networks.

[0017] A second aspect of this application provides a cloud management platform for managing infrastructure, including a CPU device pool, a memory device pool, a network interface card (NIC) device pool, and a disk device pool. Multiple CPUs in the CPU device pool, multiple memory modules in the memory device pool, multiple NICs in the NIC device pool, and multiple disks in the disk device pool are all connected to a high-speed interconnect network. The high-speed interconnect network enables interconnection between devices in each device pool within and between pools. The cloud management platform includes: an acquisition module for acquiring a logical node creation request input by a tenant, the logical node creation request including logical node specification requirements, including CPU requirements, memory requirements, NIC requirements, and disk requirements; and a creation module for creating a logical node in response to the logical node specification creation request, wherein the logical node includes a virtual CPU (CPU). The system includes a virtual CPU, virtual memory, virtual network interface card (NIC), virtual disk, and virtual bus network. Virtual CPUs, virtual memory, virtual NICs, and virtual disks are logically connected to the virtual bus network. A virtual CPU is implemented using at least one idle CPU from the CPU device pool that meets CPU requirements. Virtual memory is implemented using at least one idle memory from the memory device pool that meets memory requirements. A virtual NIC is implemented using at least one idle NIC from the NIC device pool that meets NIC requirements. A virtual disk is implemented using at least one idle disk from the disk device pool that meets disk requirements. The virtual bus network is implemented through a sub-network of a high-speed interconnect network. A determination module is used to determine the operating system image entered or selected by the tenant. A notification module is used to notify logical nodes to install the operating system image, wherein logical nodes with the operating system image installed allow tenants to log in remotely.

[0018] In one possible implementation, the acquisition module is further configured to acquire a logical node specification expansion request input by a tenant, the logical node specification expansion request being used to request expansion of one or any combination of virtual CPUs, virtual memory, virtual network interface cards, and virtual disks to a predetermined specification; the cloud management platform also includes: an expansion module, configured to: select a corresponding idle device from one or any combination of CPU device pools, memory device pools, network interface card device pools, and disk device pools according to the logical node specification expansion request, wherein the idle device matches the predetermined specification; and connect the idle device to the virtual bus network.

[0019] In one possible implementation, the acquisition module is further configured to acquire a logical node specification scaling-down request input by the tenant. The logical node specification scaling-down request requests to scale down one or any combination of virtual CPUs, virtual memory, virtual network cards, and virtual disks to a predetermined specification. The cloud management platform also includes a scaling-down module, configured to control the devices mapped to one or any combination of virtual CPUs, virtual memory, virtual network cards, and virtual disks to exit the virtual bus network according to the logical node specification scaling-down request, and mark the status of the devices as idle.

[0020] In one possible implementation, the infrastructure also includes an extended processor device pool comprising multiple extended processors connected to a high-speed interconnect network. The logical node specification creation request also includes extended processor requirements. The logical node also includes virtual extended processors logically connected to the bus network. The virtual extended processors are mapped to at least one idle extended processor in the extended processor device pool that meets the extended processor requirements.

[0021] In one possible implementation, the extended processor type of the extended processor device pool is one or any combination of NPU, GPU, TPU, and DPU.

[0022] In one possible implementation, high-speed interconnect networks are achieved through PCIe networks, IB networks, or CXL networks.

[0023] A third aspect of this application provides a cloud service system. The cloud service system includes infrastructure and a cloud management platform for managing the infrastructure. The infrastructure includes a CPU device pool, a memory device pool, a network interface card (NIC) device pool, and a disk device pool. Multiple CPUs in the CPU device pool, multiple memory modules in the memory device pool, multiple NICs in the NIC device pool, and multiple disks in the disk device pool are all connected to a high-speed interconnect network. The high-speed interconnect network is used to enable interconnection between devices in each device pool within and between pools. The cloud management platform performs the method described in the first aspect or any possible implementation of the first aspect on these infrastructures.

[0024] A fourth aspect of this application provides a computing device cluster, the computing device cluster including at least one computing device, each computing device including a processor and a memory: the memory is used to store instructions; the processor is used to cause the computing device cluster to perform the method described in the first aspect or any possible implementation of the first aspect according to the instructions.

[0025] A fifth aspect of this application provides a computer storage medium storing one or more instructions that, when executed by one or more computers, cause the one or more computers to perform the method described in the first aspect or any possible implementation of the first aspect.

[0026] A sixth aspect of this application provides a computer program product storing instructions that, when executed by a computer, cause the computer to perform the method described in the first aspect or any possible implementation of the first aspect.

[0027] In this embodiment, when a tenant needs to create a logical node, the tenant can send a logical node creation request for that logical node to the creation interface provided by the cloud management platform. Therefore, the cloud management platform can receive the logical node creation request (including CPU requirements, memory requirements, network card requirements, and disk requirements, etc.) sent by the tenant through the creation interface. Since the logical node creation request includes the logical node specification requirements set by the tenant for that logical node, the cloud management platform can select idle physical devices (including CPU, memory, network card, and disk, etc.) from multiple physical device pools (including CPU device pools, memory device pools, network card device pools, and disk device pools, etc.) that meet the tenant's specification requirements for that logical node, and create the logical node on these physical devices. Since the logical node includes virtual devices (including virtual CPU, virtual memory, virtual network card, and virtual disk, etc.) implemented based on these physical devices, and these virtual devices are connected through a virtual bus network, the cloud management platform can install the operating system image specified by the tenant on the logical node. The logical node with the operating system image installed can be remotely logged into by the tenant to schedule these virtual devices on the logical node under the tenant's instructions to complete the tenant's business, thereby meeting the tenant's business needs. In the aforementioned process, since the logical node specification requirements set by the tenant for the logical node can be used to describe the specifications of various physical devices required to create the logical node, it can be seen that the specifications of the physical devices required to create the logical node can be freely customized by the tenant. The cloud management platform only needs to select and provide physical devices that match these specifications to complete the creation of the logical node and provide it to the tenant for use. This helps to reduce the consumption of the cloud management platform when performing resource management, and can also meet the tenant's customization requirements for the specifications of the physical devices used by the logical node. Attached Figure Description

[0028] Figure 1 A schematic diagram of the structure of the cloud service system provided in the embodiments of this application;

[0029] Figure 2 A schematic diagram of a tenant interface provided in an embodiment of this application;

[0030] Figure 3a This is another schematic diagram of the cloud service system provided in the embodiments of this application;

[0031] Figure 3b A schematic diagram of the infrastructure provided in the embodiments of this application;

[0032] Figure 3c Another structural diagram of the infrastructure provided in the embodiments of this application;

[0033] Figure 4A flowchart illustrating a node creation method based on a cloud management platform provided in an embodiment of this application;

[0034] Figure 5 A schematic diagram of the logical node created for the embodiments of this application;

[0035] Figure 6 A schematic diagram illustrating the expansion of a logical node provided in an embodiment of this application;

[0036] Figure 7 Another schematic diagram illustrating the expansion of logical nodes provided in this application embodiment;

[0037] Figure 8 A schematic diagram illustrating the scaling down of a logical node provided in an embodiment of this application;

[0038] Figure 9 A schematic diagram of the structure of the cloud management platform provided in the embodiments of this application;

[0039] Figure 10 A schematic diagram of the structure of a computing device provided in an embodiment of this application;

[0040] Figure 11 A schematic diagram of the structure of a computing device cluster provided in an embodiment of this application;

[0041] Figure 12 This is a schematic diagram illustrating the network connection of computer devices in a computer cluster provided in an embodiment of this application. Detailed Implementation

[0042] This application provides a method for configuring logical nodes based on cloud services and a cloud management platform, which not only helps reduce the consumption of resources when the cloud management platform performs resource management, but also meets the tenant's customization requirements for the specifications of the physical devices used by the logical nodes.

[0043] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0044] With the rapid development of cloud technology, more and more tenants are choosing logical nodes provided by cloud vendors to complete their business. These logical nodes are usually created based on cloud resources deployed in the cloud by cloud vendors, so that the logical nodes can provide remote cloud services to tenants and thus meet the various business needs of tenants.

[0045] In related technologies, cloud service systems provided by cloud vendors can include cloud management platforms and infrastructure, which contains cloud resources of various specifications. When a tenant needs to create a dedicated logical node in the cloud, the cloud management platform provides the tenant with various cloud resources of pre-defined specifications suitable for building the logical node. The tenant can then select and combine these resources to determine the final cloud resources used to build the logical node. Based on this, the cloud management platform can create the tenant's logical node on these cloud resources to provide cloud services. For example, the cloud management platform can provide the tenant with 4-core and 8-core central processing units (CPUs), 4GB and 8GB of memory, and 1G or 2G of network interface cards (NICs). The tenant can then choose a 4-core CPU, 8GB of memory, and a 1G NIC to create the cloud resources required for their logical node, and the cloud management platform can then create the tenant's logical node on these cloud resources.

[0046] In the process described above, in order to allow tenants to freely customize the specifications of the resources used to build logical nodes, the cloud management platform needs to create a sufficient number of cloud resources of various specifications for tenants to choose from and combine. This will result in a significant increase in the resource management overhead of the cloud management platform, and often still cannot meet the various customization requirements of tenants for resource specifications.

[0047] Furthermore, since tenants cannot freely customize the specifications of the resources used to build logical nodes, the cloud management platform cannot determine the tenant's specific needs for cloud resources. This results in the cloud management platform being unable to determine how much cloud resource of each specification needs to be prepared, which brings greater uncertainty, lower resource utilization, and higher costs to resource management.

[0048] Furthermore, if a tenant needs to change the specifications of a certain cloud resource used by its logical node at any time, the relevant technology has to shut down the logical node and modify the cloud resource specifications by migrating and restarting the logical node. This may interrupt the tenant's business and result in a poor tenant experience.

[0049] To address the aforementioned issues, this application provides a method for configuring logical nodes based on cloud services. This method can be implemented through a cloud service system. Figure 1 A schematic diagram of the cloud service system provided in the embodiments of this application is shown below. Figure 1As shown, a cloud service system includes the infrastructure that provides cloud services and a cloud management platform that manages this infrastructure. The cloud management platform and the infrastructure are described separately below:

[0050] A cloud management platform can centrally manage the infrastructure of the entire cloud service system (for example, creating one or more logical nodes to serve the tenant according to the tenant's instructions; these logical nodes can be used to complete the tenant's business, etc.). The cloud management platform can also be open to tenants outside the cloud service system and respond to their requests. For example, the cloud management platform can provide various interfaces such as login, creation, scaling up, scaling down, and query interfaces for tenant clients (e.g., the terminal device used by the tenant or the browser on the terminal device, etc.) to access. Specifically, the cloud management platform can authenticate the tenant's client through the login interface; after successful authentication, the tenant's client can be allowed to log in to the cloud management platform. For example, the cloud management platform can also create an interface that allows tenant clients to send logical node creation requests to the cloud management platform for the tenant's logical nodes. Since the logical node creation request is used to indicate the (custom) logical node specification requirements set by the tenant for the logical node, and the logical node specification requirements describe the specifications of various devices required to create the logical node, the cloud management platform can select idle physical devices that meet the logical node specification requirements from various physical device pools, and create the logical node on these physical devices. The logical node contains virtual devices implemented based on these physical devices, so the cloud management platform can install the operating system image specified by the tenant on the logical node, so that the logical node with the operating system image installed can allow the tenant to log in remotely, thereby providing remote services to the tenant and meeting the tenant's business needs. For example, the cloud management platform can also use a scaling-up interface to allow tenant clients to send scaling-up requests for a logical node to the cloud management platform. This request requests that the virtual devices used by the logical node be scaled up to a predetermined size. Therefore, the cloud management platform can select idle devices from various physical device pools that meet the predetermined size and add these idle devices to the logical node, thus achieving scaling up. Conversely, the cloud management platform can also use a scaling-down interface to allow tenant clients to send scaling-down requests for a logical node to the cloud management platform. This request requests that the virtual devices used by the logical node be scaled down to a predetermined size. Therefore, the cloud management platform selects virtual devices from the logical node that meet the predetermined size and prevents the logical node from using the physical devices mapped to these virtual devices, thus achieving scaling down.

[0051] It is worth noting that, such as Figure 2 As shown ( Figure 2(This is a schematic diagram of a tenant interface provided in an embodiment of this application). The cloud management platform provides tenants with creation, expansion, reduction, and query interfaces. These interfaces can be presented to tenants as logical node creation, logical node expansion, logical node reduction, and logical node query sections in the tenant interface. For the cloud management platform internally, sample code for this tenant interface is as follows:

[0052]

[0053] 2:node_status_e status

[0054] 3: string info

[0055] 4: i32 version

[0056] }

[0057] / / This allows tenants to define logical nodes, and subsequent interfaces allow tenants to input various processing requests for these logical nodes.

[0058] typedef struct node_prot_t{

[0059] 1: string project_id;

[0060] 2: string vpc_id;

[0061] 3:optional device_prot_t cpu_devices

[0062] 4:optional device_prot_t mem_devices

[0063] 5:optional device_prot_t nic_devices

[0064] 6:optional device_prot_t disk_devices

[0065] 7:optional device_prot_t npu_devices

[0066] 8: optional string description

[0067] typedef struct node_info_t{

[0068] 1: string id

[0069] 2: node_prot_t node_info;

[0070] 3: string created_time

[0071] 4: string updated_time

[0072] }

[0073] / / Corresponding to various interfaces in the tenant interface

[0074] service node_cfg{

[0075] / **

[0076] *Add nodes / / An interface for tenants to input logical node creation requests.

[0077] *@param node property

[0078] *@return status code

[0079] /

[0080] list<node_result_t> add_nodes(1:list<node_prop_t> props)

[0081] / **

[0082] *Update node / / This is the expansion (update) interface, allowing tenants to input expansion requests for logical nodes based on their specifications.

[0083] *@param node property

[0084] *@return status code

[0085] /

[0086] list<node_result_t> update_nodes(1:list<node_prop_t> props)

[0087] / **

[0088] *Delete node / / This is the expansion (deletion) interface, allowing tenants to input requests to reduce the size of logical nodes according to their specifications.

[0089] *@param node id

[0090] *@return status code

[0091] * /

[0092] list<node_result_t>delete_nodes(1:list <string>node_ids)

[0093] / **

[0094]

[0095] When a tenant needs to create a logical node, a logical node creation request for the logical node can be input in a logical node creation column of a tenant interface, for example, the logical node creation request is as follows:

[0096] {

[0097] "name":"xxxx", / / The name of the logical node;

[0098] "project_id":"xxxx", / / The identification of the project to which the logical node belongs;

[0099] "vpc_id":"xxxx", / / The identification of a virtual private cloud (VPC) in which the logical node is located;

[0100] "cpu_devices":{xxxx}, / / A resource parameter, indicating the specification of a CPU required for creating the logical node;

[0101] "mem_devices":{xxxx}, / / A resource parameter, indicating the specification of a memory required for creating the logical node;

[0102] "nic_devices":{xxxx}, / / A resource parameter, indicating the specification of a network interface controller (NIC) required for creating the logical node;

[0103] "disk_devices":{xxxx}, / / A resource parameter, indicating the specification of a disk required for creating the logical node;

[0104] "npu_devices":{xxxx} / / A resource parameter, indicating the specification of a neural networks process unit (NPU) required for creating the logical node;

[0105] }

[0106] Therefore, a logical node creation request is used to instruct the tenant to set the resource parameters for that logical node. These resource parameters describe the logical node's specification requirements, including CPU requirements (the specifications of the CPU required to create the logical node), memory requirements (the specifications of the memory required to create the logical node), network interface card (NIC) requirements (the specifications of the NIC required to create the logical node), disk requirements (the specifications of the disk required to create the logical node), and extended processor requirements (the specifications of the extended processors required to create the logical node; NPU is a representation of extended processors). For example, suppose the node creation request includes:

[0107] "cpu_devices":{"devices_type":0,"core_num":4,"threads":8;

[0108] "mem_devices":{"devices_type":1,"size":8589934592};

[0109] "nic_devices":{"devices_type":2,"bandwidth":1000000000};

[0110] "disk_devices":{"devices_type":3,"size":120000000000};

[0111] "npu_devices":{"devices_type":4,"core_num":2}.

[0112] The logical node creation request includes the resource parameters set by the tenant for the logical node. These resource parameters describe the device specifications required to create the logical node (i.e., logical node specifications). The requirements are that the logical node needs to have a CPU with 4 cores and 8 threads, 8GB of memory, 120GB of disk storage, a network card with 1G bandwidth, and an NPU with 2 cores, etc.

[0113] When the cloud management platform receives a logical node creation request for this logical node, it can parse the request to obtain the resource parameters set by the tenant for that logical node, such as... Figure 3a As shown ( Figure 3a (This is another structural diagram of the cloud service system provided in the embodiments of this application), and these resource parameters are used as the model of the logical node. For example, the model of the logical node can be as follows:

[0114] The model of this logical node: defines some specifications of the various physical devices required to create this logical node;

[0115] Method: POST / PUT

[0116] URL: / nodes

[0117] Fileds:

[0118] 1. project_id: The identifier of the project to which this logical node belongs;

[0119] 2. vpc_id: The identifier of the VPC where this logical node resides;

[0120] 3. cpu_devices: Declare the specifications of the CPUs required to create this logical node;

[0121] 4. mem_devices: Declare the specifications of the memory required to create this logical node;

[0122] 5. nic_devices: Declare the specifications of the network interface cards required to create this logical node;

[0123] 6. disk_devices: Declare the specifications of the disks required to create this logical node;

[0124] 7. npu_devices: Declare the specifications of the NPUs required to create this logical node;

[0125] 8. Description: The description information of this logical node;

[0126] 9. name: The name of this logical node.

[0127] After obtaining the model of the logical node, the cloud management platform can also generate sub-models of various devices of the logical node based on the model. These sub-models include resource parameters set by the tenant for the logical node and resource parameters set by the cloud management platform for the logical node. These sub-models describe the overall specifications of the physical devices required to create the logical node. It should be noted that these sub-models may include sub-models of the logical node's computing devices (also called computing resources, such as the aforementioned CPU and NPU), storage devices (also called storage resources, such as the aforementioned memory and disk), and network devices (also called network resources, such as the aforementioned network interface card). For example, these sub-models may be as follows:

[0128] a. Sub-model of the CPU for this logical node: Defines the total specifications of the CPU required to create this logical node;

[0129] Method: POST / PUT

[0130] URL: / devices

[0131] Fileds:

[0132] a.1devices_type: Declares the type of physical device. It is an enumeration type, and its value is 0, which declares the physical device as CPU.

[0133] a.2project_id: Declares the identifier of the project to which the CPU belongs;

[0134] a.3node_id: Declares the identifier (name) of the logical node to which the CPU belongs. This item is optional.

[0135] a.4devices_matadata: CPU computing power parameters, which can include the following items;

[0136] a.4.1core_num: This computing power parameter is an integer parameter that declares the number of CPU cores;

[0137] a.4.2frequency: This computing power parameter is a long integer parameter in Hz, declaring the CPU clock frequency;

[0138] a.4.3l1_cache: This computing power parameter is a long integer parameter that declares the size (storage amount) of the CPU's L1 cache;

[0139] a.4.4l2_cache: This computing power parameter is a long integer parameter that declares the size of the CPU's L2 cache;

[0140] a.4.5l3_cache: This computing power parameter is a long integer parameter that declares the size of the CPU's L3 cache;

[0141] a.4.6threads: This computing power parameter is a long integer parameter that declares the number of CPU threads. The default value is twice the number of cores.

[0142] It should be noted that a.4.1 and a.4.6 are usually included in the resource parameters set by the tenant for this logical node; that is, a.4.1 and a.4.6 are usually set by the tenant. a.4.2 to a.4.5 are usually included in the resource parameters set by the cloud management platform for this logical node; that is, a.4.2 to a.4.5 are usually set by the cloud management platform.

[0143] b. Sub-model of the memory of this logical node: Defines the total memory specifications required to create this logical node;

[0144] Method: POST / PUT

[0145] URL: / devices

[0146] Fileds:

[0147] b.1devices_type: Declares the type of physical device. It is an enumeration type, and its value is 1, which declares the physical device as memory.

[0148] b.2project_id: Declares the identifier of the project to which the memory belongs;

[0149] b.3node_id: Declares the identifier of the logical node to which the memory belongs;

[0150] b.4devices_matadata: Memory capacity parameter, which can include the following items;

[0151] b.4.1size: This capacity parameter is a string parameter that declares the amount of memory that can be stored, i.e., the number of bytes that can be stored in memory;

[0152] b.4.2r_speed: This capacity parameter is a long integer parameter that declares the memory read speed per second;

[0153] b.4.3w_speed: This capacity parameter is a long integer parameter that declares the memory write speed per second;

[0154] It should be noted that b.4.1 is usually included in the resource parameters set by the tenant for this logical node, that is, b.4.1 is usually set by the tenant. b.4.2 to b.4.3 are usually included in the resource parameters set by the cloud management platform for this logical node, that is, b.4.2 to b.4.3 are usually set by the cloud management platform.

[0155] c. Sub-model of the NPU for this logical node: Defines the total specifications of the NPU required to create this logical node;

[0156] Method: POST / PUT

[0157] URL: / devices

[0158] Fileds:

[0159] c.1devices_type: Declares the type of physical device. It is an enumeration type with a value of 4, which declares the physical device as an NPU.

[0160] c.2project_id: Declares the identifier of the project to which the NPU belongs;

[0161] c.3node_id: Declares the identifier of the logical node to which the NPU belongs;

[0162] c.4devices_matadata: NPU computing power parameters, which can include the following items;

[0163] c.4.1core_num: This computing power parameter is an integer parameter that declares the number of NPU cores;

[0164] c.4.2mem_size: This computing power parameter is a long integer parameter, in bytes, declaring the storage amount of the NPU's memory;

[0165] c.4.3tflops: This computing power parameter is a long integer parameter, declaring the floating-point operation capability of the NPU;

[0166] c.4.4bandwidth: This computing power parameter is a long integer parameter, in bits / s, representing the declared bandwidth of the NPU;

[0167] It should be noted that c.4.1 is usually included in the resource parameters set by the tenant for this logical node, that is, c.4.1 is usually set by the tenant. c.4.2 to c.4.4 are usually included in the resource parameters set by the cloud management platform for this logical node, that is, c.4.2 to c.4.4 are usually set by the cloud management platform.

[0168] d. Sub-model of the network interface card (NIC) of this logical node: Defines the total specifications of the NIC required to create this logical node;

[0169] Method: POST / PUT

[0170] URL: / devices

[0171] Fileds:

[0172] d.1devices_type: Declares the type of physical device. It is an enumeration type with a value of 2, which declares the physical device as a network interface card (NIC).

[0173] d.2project_id: Declares the identifier of the project to which the NPU belongs;

[0174] d.3node_id: Declares the identifier of the logical node to which the NPU belongs;

[0175] d.4devices_matadata: Network interface card (NIC) computing power parameters, which may include the following items;

[0176] d.4.1pps: This computing power parameter is a long integer parameter, declaring the number of packets transmitted per second by the network card;

[0177] d.4.2bandwidth: This computing power parameter is a long integer parameter, in bytes, declaring the bandwidth of the network card;

[0178] It should be noted that d.4.1 is usually included in the resource parameters set by the tenant for this logical node; that is, d.4.1 is usually set by the tenant. d.4.2 is usually included in the resource parameters set by the cloud management platform for this logical node; that is, d.4.2 is usually set by the cloud management platform.

[0179] e. Disk sub-model of this logical node: Defines the total disk specifications required to create this logical node;

[0180] Method: POST / PUT

[0181] URL: / devices

[0182] Fileds:

[0183] e.1devices_type: Declares the type of physical device. It is an enumeration type with a value of 2, which declares the physical device as a disk.

[0184] e.2project_id: Declares the identifier of the project to which the disk belongs;

[0185] e.3node_id: Declares the identifier of the logical node to which the disk belongs;

[0186] e.4devices_matadata: Disk computing power parameters, which can include the following items;

[0187] e.4.1size: This capacity parameter is a long integer parameter in bytes, declaring the disk storage;

[0188] e.4.2wr_bandwidth: This capacity parameter is a long integer parameter, in bytes, and declares the disk read and write speed;

[0189] e.4.3 interface_type: Declares the disk interface type, enumeration, sata, etc.;

[0190] e.4.4cache: This capacity parameter is an integer parameter, in bytes, and declares the storage size (size) of the disk cache;

[0191] e.4.5ro_speed: This capacity parameter is an integer parameter, in r / min, and declares the disk's rotational speed;

[0192] It should be noted that e.4.1 is typically included in the resource parameters set by the tenant for this logical node; that is, e.4.1 is usually set by the tenant. e.4.2 to e.4.5 are typically included in the resource parameters set by the cloud management platform for this logical node; that is, e.4.2 to e.4.5 are usually set by the cloud management platform. As can be seen, since the above sub-models describe the overall specifications of the various physical devices required to create this logical node, the cloud management platform can select idle devices from various physical device pools that meet these sub-models to create the tenant's logical node using these idle devices. (Of course, after receiving the logical node creation request, the cloud management platform may also choose not to generate the logical node model and its sub-models, but directly parse the logical node creation request to obtain the logical node specification requirements, and select idle devices from various physical device pools that meet these requirements to create the tenant's logical node; this is not restricted here.)

[0193] The infrastructure comprises multiple pools of physical devices, including pools of computing devices, storage devices, and network devices of various types. The computing device pools may include CPU pools and extended processor pools. Extended processor pools may include graphics processing unit (GPU) pools, NPU pools, tensor processing unit (TPU) pools, and data processing unit (DPU) pools, etc. Storage device pools may include memory pools and disk pools, etc. Network device pools may include network interface card (NIC) pools, etc. Specifically, the CPU pool contains multiple CPUs (these CPUs can be identical or different in specifications), the extended processor pool contains multiple extended processor pools (these extended processor pools can be identical or different in specifications), the memory pool contains multiple memory modules (these memory modules can be identical or different in specifications), the disk pool contains multiple disks (these disks can be identical or different in specifications), and the NIC pool contains multiple network interface cards (these NICs can be identical or different in specifications). As can be seen, the cloud management platform can select several physical devices from these physical device pools that meet the tenant's needs and have certain specifications to build the tenant's logical node, or to expand or shrink the tenant's logical node.

[0194] It is worth noting that these multiple physical device pools are presented and communicated with in various ways:

[0195] (1) As Figure 3b As shown ( Figure 3b (A schematic diagram of the infrastructure provided in this application embodiment) In these multiple physical device pools, all physical devices in each physical device pool are randomly and dispersedly arranged on racks, rather than being arranged in a fixed combination within the chassis of physical servers in the racks. Therefore, any two physical devices within any physical device pool can communicate with each other through a high-speed interconnect device, and physical devices between any two physical device pools can also communicate with each other through a high-speed interconnect device. This high-speed interconnect device may include a high-speed interconnect bus and a high-speed interconnect bus switch, etc. Thus, the high-speed interconnect device connects all physical devices in multiple physical device pools, forming a high-speed interconnect network (the "high-speed" in high-speed interconnect network refers to a bandwidth of no less than 40G / S). That is, multiple CPUs in the CPU device pool, multiple extended processors in the extended processor device pool, multiple memory modules in the memory device pool, multiple network cards in the network card device pool, and multiple disks in the disk device pool are all connected to the high-speed interconnect network, and therefore, these physical devices can communicate with each other through the high-speed interconnect network.

[0196] It is also worth noting that after the cloud management platform determines the logical node specification requirements of a tenant's logical node, the cloud management platform can select several physical devices from multiple physical device pools that meet those logical node specification requirements (e.g., Figure 3b The dashed box contains the CPU, NPU, memory, network card, and disk, etc., and a logical node is created on these physical devices. This logical node contains virtual devices implemented based on these physical devices (i.e., these physical devices have a mapping relationship with these virtual devices). Since these physical devices are all connected to a high-speed interconnect network, the network formed between these physical devices is part of the high-speed interconnect network, and can also be called a subnetwork of the high-speed interconnect network (e.g., Figure 3b (The dashed box). Since these virtual devices are implemented based on these physical devices, they can also be logically connected through a virtual bus network. This virtual bus network is implemented based on a sub-network of the high-speed interconnection network formed between these physical devices (i.e., the virtual bus network and the sub-network have a mapping relationship).

[0197] (2) Figure 3c As shown ( Figure 3c (Another structural diagram of the infrastructure provided in the embodiments of this application) These multiple physical device pools can be deployed in the form of multiple supernodes. Each supernode contains multiple physical servers, and each physical server can contain multiple physical devices of different types (for example, a physical server contains at least one CPU, at least one memory, at least one extended processor, at least one network card, and at least one disk). Any two physical servers can communicate with each other through a high-speed interconnect device. Therefore, for any physical server's CPU, it can not only use the physical server's network card, extended processor, memory, and disk, but also the network card, extended processor, memory, and disk of other physical servers. In this way, the same type of physical devices in different physical servers can be regarded as "pooled", thereby enabling all physical servers in multiple supernodes to form these multiple physical device pools. Since all physical servers within multiple supernodes communicate with each other through high-speed interconnect devices, a high-speed interconnect network is formed among all physical servers. This is equivalent to a high-speed interconnect network being formed among multiple physical device pools. In other words, multiple CPUs in the CPU device pool, multiple extended processors in the extended processor device pool, multiple memory modules in the memory device pool, multiple network cards in the network card device pool, and multiple disks in the disk device pool are all connected to the high-speed interconnect network. Therefore, these physical devices can communicate with each other through the high-speed interconnect network.

[0198] It is also worth noting that after the cloud management platform obtains the resource orchestration scheme for multiple subtasks of a tenant's job task, the cloud management platform can select several physical devices from multiple physical device pools that meet the performance requirements of the tenant's job task based on the resource orchestration scheme (e.g., Figure 3c The dashed box contains several physical servers. These physical servers include CPUs, extended processors, memory, network interface cards (NICs), and disks (which can be considered as parts of the CPU device pool, extended processor device pool, memory device pool, NIC device pool, and disk device pool, etc.). A logical node is created on these physical devices. This logical node contains virtual devices implemented based on these physical devices (i.e., these physical devices have a mapping relationship with these virtual devices). Since these physical devices are all connected to a high-speed interconnect network, the network formed by these physical devices is part of the high-speed interconnect network, and can also be called a subnetwork of the high-speed interconnect network (e.g., ...). Figure 3c (The dashed box). Since these virtual devices are implemented based on these physical devices, they can also be logically connected through a virtual bus network. This virtual bus network is implemented based on a sub-network of the high-speed interconnection network formed between these physical devices (i.e., the virtual bus network and the sub-network have a mapping relationship).

[0199] Furthermore, such as Figure 3a As shown, in these multiple physical device pools, each physical device has a certain type of interface. For any given physical device, it can connect to a high-speed interconnect bus switch through its interface, and then communicate with other physical devices through the high-speed interconnect bus.

[0200] Furthermore, for the tenant's logical node, the logical node can typically be regarded as a cloud instance in the infrastructure. These cloud instances can be presented in various ways. For example, these cloud instances can be (one or more) physical servers selected by the cloud management platform in the infrastructure; they can also be bare metal servers selected by the cloud management platform in the infrastructure; they can also be virtual machines (VMs) created by the cloud management platform on physical servers using virtualization technology; they can also be containers (Docker) created by the cloud management platform on physical servers using virtualization technology; they can also be micro VMs created by the cloud management platform on physical servers using virtualization technology, and so on.

[0201] Furthermore, for the aforementioned multiple physical device pools, these multiple physical device pools can be deployed in the same site or different sites. The site can be presented in various forms, such as a region in the infrastructure, an availability zone in the infrastructure, a data center (DC) in the infrastructure, a room in the infrastructure, and so on.

[0202] Furthermore, the high-speed interconnection network built between these multiple physical device pools can be implemented based on multiple high-speed interconnect bus switches. Suppose these multiple physical device pools are deployed across a data center, which often contains multiple racks. These racks are used to house several physical devices from each physical device pool. In order to enable communication between physical devices in different racks, each rack often needs to deploy at least one high-speed interconnect bus switch. In this way, the racks can communicate with each other through the high-speed interconnect bus switches, thereby forming a high-speed interconnection network within the data center.

[0203] Furthermore, the aforementioned high-speed interconnect network can take many forms. For example, it can be a high-speed serial computer expansion bus standard (Peripheral Component Interconnect Express, PCIe) network, an InfiniBand (IB) wireless network, a Compute Express Link (CXL) network, or even an interconnect network between devices developed by cloud vendors (the bandwidth of which also needs to be no less than 40 Gbps), etc. Correspondingly, the high-speed interconnect devices connected to each physical device can be communication devices based on the PCIe protocol, CXL protocol, IB protocol, or a communication protocol developed by the cloud vendor. Similarly, the interfaces used by the physical devices in each physical device pool to access the high-speed interconnect network can be PCIe interfaces, CXL interfaces, IB interfaces, or interfaces developed by the cloud vendor, etc.

[0204] Based on the aforementioned cloud service system, when a tenant needs to create a logical node, the tenant can send a logical node creation request for that logical node to the creation interface provided by the cloud management platform. Therefore, the cloud management platform can receive the logical node creation request (including CPU requirements, memory requirements, network interface card (NIC) requirements, and disk requirements, etc.) sent by the tenant through the creation interface. Since the logical node creation request includes the logical node specification requirements set by the tenant for that logical node, the cloud management platform can select from multiple physical device pools (including CPU device pools, memory device pools, NIC device pools, and disk device pools, etc.) that meet the tenant's specification requirements for that logical node and are available, and create the logical node on these physical devices. Because this logical node contains virtual devices (including virtual CPUs, virtual memory, virtual network cards, and virtual disks, etc.) implemented based on these physical devices, and these virtual devices are connected through a virtual bus network, the cloud management platform can install the operating system image specified by the tenant on this logical node. The logical node with this operating system image installed can be remotely logged into by the tenant to schedule these virtual devices on the logical node to complete the tenant's business, thereby meeting the tenant's business needs. In the aforementioned process, since the logical node specification requirements set by the tenant for this logical node can describe the specifications of the various physical devices required to create the logical node, it is evident that the specifications of the physical devices required to create the logical node can be freely customized by the tenant. The cloud management platform only needs to select and provide physical devices that match these specifications to complete the creation of the logical node and provide it to the tenant for use. This helps reduce the resource consumption of the cloud management platform during resource management and also meets the tenant's customization requirements for the specifications of the physical devices used by the logical node. To understand the workflow of the cloud management platform described above, the following section combines... Figure 4 This workflow will be described in further detail. Figure 4 A flowchart illustrating the logical node configuration method based on a cloud management platform provided in this application embodiment is shown below. Figure 4 As shown, this method can be achieved through, as Figure 1 The cloud service system implementation shown includes infrastructure providing cloud services to tenants and a cloud management platform for managing this infrastructure. This infrastructure may include CPU device pools, memory device pools, network interface card (NIC) device pools, and disk device pools. Multiple CPUs in the CPU device pool, multiple memory modules in the memory device pool, multiple NICs in the NIC device pool, and multiple disks in the disk device pool are all connected to a high-speed interconnect network. This high-speed interconnect network is used to interconnect physical devices within and between the various physical device pools in the infrastructure. The method includes:

[0205] 401. The cloud management platform obtains the logical node creation request input by the tenant. The logical node creation request includes logical node specification requirements, which include CPU requirements, memory requirements, network card requirements, and disk requirements.

[0206] In this embodiment, when a tenant needs to create its own logical node, the cloud management platform can provide a creation interface to the tenant's client (e.g., a logical node creation section on the tenant's interface). The tenant can then input a logical node creation request for that logical node into the creation interface through their client. In this way, the cloud management platform can receive the logical node creation request sent by the tenant through their client via the creation interface. It is worth noting that the logical node creation request includes the logical node specification requirements set by the tenant for that logical node. These specifications include CPU requirements, memory requirements, network interface card (NIC) requirements, and disk requirements. Specifically, the CPU requirements describe the specifications of the CPU needed to create the logical node, the memory requirements describe the specifications of the memory needed to create the logical node, the NIC requirements describe the specifications of the NIC needed to create the logical node, and the disk requirements describe the specifications of the disk needed to create the logical node.

[0207] Furthermore, the logical node specification requirements may also include extended processor requirements, which describe the specifications of the extended processors required to create the logical node.

[0208] For example, when a tenant needs to create logical node 1 and logical node 2, the tenant can log in to the cloud management platform. The cloud management platform can provide the tenant with a tenant interface. Since the tenant interface includes a logical node creation field, the tenant can enter logical node creation requests for logical node 1 and logical node 2 in the logical node creation field.

[0209] curl POST / nodes [

[0211] {

[0212] "project_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0213] "vpc_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0214] "cpu_devices":{"devices_type":0,"core_num":2,"threads":4},

[0215] "mem_devices":{"devices_type":1,"size":8589934592},

[0216] "nic_devices":{"devices_type":2,"bandwidth":1000000000},

[0217] "disk_devices":{"devices_type":3,"size":80000000000},

[0218] "npu_devices":{"devices_type":4,"core_num":2},

[0219] "decription":"Node1,2U+8G+2NPU",

[0220] "name":"Node1"

[0221] },

[0222] {

[0223] "project_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0224] "vpc_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0225] "cpu_devices":{"devices_type":0,"core_num":1,"threads":2},

[0226] "mem_devices":{"devices_type":1,"size":8589934592},

[0227] "nic_devices":{"devices_type":2,"bandwidth":1000000000},

[0228] "disk_devices":{"devices_type":3,"size":80000000000},

[0229] "npu_devices":{"devices_type":4,"core_num":1},

[0230] "description":"Node2,1U+8G+1NPU",

[0231] "name":"Node2"

[0232] } ]

[0234] Based on the above logical node creation request, it can be seen that the tenant sets logical node specification requirement 1 for logical node 1. This requirement 1 includes CPU requirement 1, NPU requirement 1, memory requirement 1, network card requirement 1, and disk requirement 1. CPU requirement 1 means that the CPU cores required to create logical node 1 are 2. NPU requirement 1 means that the NPU cores required to create logical node 1 are 2. Memory requirement 1 means that the memory storage required to create logical node 1 is 8G. Disk requirement 1 means that the disk storage required to create logical node 1 is 80G. Network card requirement 1 means that the bandwidth of the network card required to create logical node 1 is 1G.

[0235] Similarly, the tenant sets logical node specification requirement 2 for logical node 2. This requirement 2 includes CPU requirement 2, NPU requirement 2, memory requirement 2, network card requirement 2, and disk requirement 2. CPU requirement 2 means that one CPU core is required to create logical node 2. NPU requirement 2 means that one NPU core is required to create logical node 2. Memory requirement 2 means that 8GB of memory is required to create logical node 2. Disk requirement 2 means that 80GB of disk storage is required to create logical node 2. Network card requirement 2 means that 1G of bandwidth is required to create logical node 2.

[0236] 402. The cloud management platform responds to the logical node specification creation request and creates a logical node, which includes a virtual CPU, virtual memory, virtual network interface card (NIC), virtual disk, and virtual bus network. The virtual CPU, virtual memory, virtual NIC, and virtual disk are logically connected to the virtual bus network. The virtual CPU is implemented by at least one CPU in the CPU device pool that meets the CPU requirements and is idle. The virtual memory is implemented by at least one memory in the memory device pool that meets the memory requirements and is idle. The virtual NIC is implemented by at least one NIC in the NIC device pool that meets the NIC requirements and is idle. The virtual disk is implemented by at least one disk in the disk device pool that meets the disk requirements and is idle. The virtual bus network is implemented by a sub-network of the high-speed interconnect network.

[0237] Upon receiving a logical node creation request for a given logical node, the cloud management platform can parse the logical node specification requirements from the request. Since these requirements include CPU, memory, network interface card (NIC) requirements, and disk requirements, the cloud management platform can select at least one idle CPU from the CPU device pool that meets the CPU requirements, at least one idle memory module from the memory device pool, at least one idle NIC from the NIC device pool, and at least one idle disk from the disk device pool. Then, the cloud management platform can create the logical node on these CPUs, memory modules, NICs, and disks. This logical node includes a virtual CPU implemented based on these CPUs, virtual memory implemented based on these memory modules, a virtual NIC implemented based on these NICs, a virtual disk implemented based on these disks, and a virtual bus network. It should be noted that in this logical node, since these CPUs, these memories, these network cards, and these disks are all connected to the sub-network of the high-speed interconnect network, that is, these CPUs, these memories, these network cards, and these disks can communicate with each other through this sub-network, the virtual bus network implemented based on this sub-network can be logically connected to these virtual CPUs, these virtual memories, these virtual network cards, and these virtual disks respectively. In other words, these virtual CPUs, these virtual memories, these virtual network cards, and these virtual disks can communicate with each other through this virtual bus network.

[0238] Furthermore, when the logical node specification requirements may also include extended processor requirements, the cloud management platform can select at least one idle extended processor from the extended processor device pool that meets the extended processor requirements, and create the logical node on these CPUs, these extended processors, these memories, these network cards, and these disks. Accordingly, the logical node includes virtual CPUs implemented based on these CPUs, virtual extended processors implemented based on these extended processors, virtual memory implemented based on these memories, virtual network cards implemented based on these network cards, virtual disks implemented based on these disks, and a virtual bus network. It should be noted that the virtual bus network can be logically connected to these virtual CPUs, these virtual extended processors, these virtual memories, these virtual network cards, and these virtual disks respectively; that is, these virtual CPUs, these virtual extended processors, these virtual memories, these virtual network cards, and these virtual disks can communicate with each other through this virtual bus network.

[0239] As in the example above, such as Figure 5 As shown ( Figure 5 (A schematic diagram of the creation of a logical node provided in this application embodiment) Since the cloud management platform has obtained the logical node specification requirement 1 set by the tenant for logical node 1, which includes CPU requirement 1, NPU requirement 1, memory requirement 1, network card requirement 1, and disk requirement 1, a CPU and NPU that meet CPU requirement 1 and NPU requirement 1 are selected from the CPU device pool and NPU device pool, a memory and disk that meet memory requirement 1 and disk requirement 1 are selected from the memory device pool and disk device pool, and a network card that meets network card requirement 1 is selected from the network card device pool. Logical node 1 is then created on the selected CPU, NPU, memory, disk, and network card. Logical node 1 includes virtual CPUs implemented based on these CPUs, NPUs implemented based on these NPUs, virtual memory implemented based on these memory, virtual network cards implemented based on these network cards, virtual disks implemented based on these disks, and a virtual bus network. These virtual CPUs, these virtual extended processors, these virtual memory, these virtual network cards, and these virtual disks can communicate with each other through the virtual bus network.

[0240] Similarly, since the cloud management platform has received the logical node specification requirement 2 set by the tenant for logical node 2, which includes CPU requirement 2, NPU requirement 2, memory requirement 2, network card requirement 2, and disk requirement 2, it selects CPUs and NPUs that meet CPU requirement 2 and NPU requirement 2 from the CPU device pool and NPU device pool, memory and disks that meet memory requirement 2 and disk requirement 2 from the memory device pool and disk device pool, and network cards that meet network card requirement 2 from the network card device pool. Logical node 2 is then created on the selected CPUs, NPUs, memory, disks, and network cards. Logical node 2 includes virtual CPUs implemented based on these CPUs, NPUs implemented based on these NPUs, virtual memory implemented based on these memory units, virtual network cards implemented based on these network cards, virtual disks implemented based on these disks, and a virtual bus network. These virtual CPUs, these virtual extended processors, these virtual memories, these virtual network cards, and these virtual disks can communicate with each other through this virtual bus network.

[0241] Specifically, the cloud management platform can also perform the following operations:

[0242] When a tenant needs to expand the capacity of a logical node, the cloud management platform can provide an expansion interface to the tenant's client (e.g., the logical node expansion section in the tenant's interface). The tenant can then submit a logical node expansion request to the expansion interface through their client. This request requests that one or any combination of the virtual CPUs, virtual memory, virtual network interface cards, and virtual disks contained within the logical node be expanded to the tenant's predetermined specifications.

[0243] Based on the logical node specification expansion request, the cloud management platform selects the corresponding idle device from one or any combination of CPU device pool, memory device pool, network card device pool, and disk device pool. The specifications of the idle device selected by the cloud management platform match the pre-defined specifications set by the tenant.

[0244] After identifying idle devices, the cloud management platform connects these idle (physical) devices to the virtual bus network of the logical node. These idle devices can also be used to implement virtual devices for the logical node. In other words, idle devices can include one or any combination of idle CPUs, idle NPUs, idle memory, idle disks, and idle network cards newly selected by the cloud management platform. These are used to implement the physical devices for these virtual CPUs, virtual memory, virtual network cards, and virtual disks in the logical node. This includes not only the original CPUs, extended processors, memory, network cards, and disks, but also the newly selected idle CPUs, idle NPUs, idle memory, idle disks, and idle network cards, or any combination thereof. Therefore, the specifications of the physical devices (or combinations thereof) for these virtual CPUs, virtual memory, virtual network cards, and virtual disks in the logical node have increased, meaning the cloud management platform has successfully expanded the capacity of the logical node.

[0245] As in the example above, such as Figure 6 As shown ( Figure 6 A schematic diagram illustrating the expansion of a logical node provided in an embodiment of this application. Figure 6 Is Figure 5 Based on the above (drawn), if a tenant needs to increase the bandwidth of the virtual network card of logical node 2 by 1G and increase the storage of the virtual disk to 120G, the tenant can enter the following logical node specification expansion request in the logical node expansion field in the tenant interface:

[0246] curl PUT / nodes [

[0248] {

[0249] "name":"Node2",

[0250] "id":"xxxxx",

[0251] "project_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0252] "vpc_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0253] "nic_devices":{"devices_type":2,"bandwidth":2000000000},

[0254] "disk_devices":{"device_id":"xxxxxxxx-a9d0-4709-9d84-xxxxxxxx","devices_type":3,"size":120000000000},

[0255] "description":"Node2,1U+8G+1NPU,nic*2,120G disk"

[0256] } ]

[0258] Based on the aforementioned logical node expansion request, it is known that the tenant needs to increase the bandwidth of the virtual network interface card (NIC) of logical node 2 by 1G and the storage capacity of the virtual disk by 40G. Therefore, the cloud management platform can select a NIC with a bandwidth of 1G from the NIC device pool and a disk with a storage capacity of 40G from the disk device pool, and then add these NICs and disks to the virtual bus network within logical node 2. In this way, the virtual NIC of logical node 2 is implemented based on a NIC with a bandwidth of 2G, and the virtual disk is implemented based on a disk with a storage capacity of 120G, which is equivalent to successfully expanding the capacity of its virtual NIC and virtual disk.

[0259] For example, such as Figure 7 As shown ( Figure 7 Another schematic diagram illustrating the expansion of logical nodes provided in this application embodiment. Figure 7 Is Figure 6 Based on the above (drawn), if a tenant needs to increase the virtual memory of logical node 2 by 8GB and add 1 core to the virtual NPU, the tenant can enter the following logical node specification expansion request in the logical node expansion field of the tenant interface:

[0260] curl PUT / nodes [

[0262] {

[0263] "name":"Node2",

[0264] "id":"xxxxx",

[0265] "project_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0266] "vpc_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0267] "mem_devices":{"devices_type":1,"size":8589934592},

[0268] "npu_devices":{"devices_type":4,"core_num":1},

[0269] "description":"Node2,1U+16G,nic*2,120G disk,2NPU"

[0270] } ]

[0272] Based on the aforementioned logical node expansion request, it is known that the tenant needs to increase the virtual memory storage of logical node 2 by 8GB and add one core to the virtual NPU. Therefore, the cloud management platform can select 8GB of memory from the memory device pool and one NPU with one core from the NPU device pool, and then add this memory and these NPUs to the virtual bus network inside logical node 2. In this way, the virtual memory of logical node 2 is implemented based on 16GB of memory storage, and the virtual NPU is implemented based on two NPUs, which is equivalent to expanding its virtual memory and virtual disk NPU.

[0273] More specifically, the cloud management platform can also perform the following operations:

[0274] When a tenant needs to scale down a logical node, the cloud management platform can provide a scaling-down interface to the tenant's client (e.g., the logical node scaling-down section in the tenant's interface). The tenant can then use their client to submit a scaling-down request to the scaling-down interface, requesting that one or any combination of the virtual CPUs, virtual memory, virtual network interface cards, and virtual disks contained within the logical node be scaled down to the tenant's predetermined specifications.

[0275] Based on the request to scale down a logical node, the cloud management platform controls the (physical) devices mapped by one or any combination of virtual CPUs, virtual memory, virtual network cards, and virtual disks in the logical node to exit the virtual bus network, and marks the status of these exited devices as idle.

[0276] Since the decommissioned devices include one or any combination of the original CPUs, memory, network cards, and disks, that is, the physical devices used to implement the virtual CPUs, virtual memory, virtual network cards, and virtual disks in the logical node have been reduced, the specifications of the virtual CPUs, virtual memory, virtual network cards, and virtual disks in the logical node have been reduced. In other words, the cloud management platform has successfully reduced the size of the logical node.

[0277] As in the example above, such as Figure 8 As shown ( Figure 8 This is a schematic diagram illustrating the scaling down of a logical node provided in an embodiment of this application. Figure 8 Is Figure 7 Based on the data drawn above, if a tenant needs to delete the virtual NPU of logical node 2, the tenant can enter the following logical node specification scaling request in the logical node scaling down field in the tenant interface:

[0278] curl PUT / nodes [

[0280] {

[0281] "name":"Node2",

[0282] "id":"xxxxx",

[0283] "project_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0284] "vpc_id":"xxxxxxxx-a9d0-4709-9d84-138c8ed73d5a",

[0285] "npu_devices":{"devices_type":4,"core_num":0},

[0286] "description":"Node2,2U+8G+2NPU,nic*2",

[0287] } ]

[0289] Based on the above logical node scaling-down request, it can be seen that the tenant needs to delete the virtual NPU of logical node 2. Therefore, the cloud management platform can make the two core NPUs mapped by the virtual NPU of logical node 2 exit the virtual bus network inside logical node 2 and mark these two core NPUs as idle. Thus, the cloud management platform has successfully scaled down the virtual NPU of logical node 2.

[0290] More specifically, the cloud management platform can also perform the following operations:

[0291] When a tenant needs to query information about a logical node, the tenant can input a query request for that logical node into the query interface provided by the cloud management platform (e.g., the logical node query bar on the tenant's interface) through their client. The cloud management platform can then receive this query request from the tenant via their client. Based on this query request, the cloud management platform can provide the tenant with information about the logical node. This information may include the specifications of the physical devices used to implement the logical node, such as the specifications of the CPU used to implement the virtual CPU.

[0292] 403. The cloud management platform determines the operating system image entered or selected by the tenant.

[0293] 404. The cloud management platform notifies logical nodes to install the operating system image. Logical nodes with the operating system image installed allow tenants to log in remotely.

[0294] After creating the logical node, the cloud management platform can prompt the tenant to provide a self-defined operating system image or an operating system image selected by the tenant on the cloud management platform. The cloud management platform can then install the tenant-specified operating system image on the logical node. This logical node, with the operating system image installed, can be remotely logged into by the tenant to schedule the virtual devices on that logical node to complete the tenant's business operations, thereby meeting the tenant's business needs.

[0295] In this embodiment, when a tenant needs to create a logical node, the tenant can send a logical node creation request for that logical node to the creation interface provided by the cloud management platform. Therefore, the cloud management platform can receive the logical node creation request (including CPU requirements, memory requirements, network card requirements, and disk requirements, etc.) sent by the tenant through the creation interface. Since the logical node creation request includes the logical node specification requirements set by the tenant for that logical node, the cloud management platform can select idle physical devices (including CPU, memory, network card, and disk, etc.) from multiple physical device pools (including CPU device pools, memory device pools, network card device pools, and disk device pools, etc.) that meet the tenant's specification requirements for that logical node, and create the logical node on these physical devices. Since the logical node includes virtual devices (including virtual CPU, virtual memory, virtual network card, and virtual disk, etc.) implemented based on these physical devices, and these virtual devices are connected through a virtual bus network, the cloud management platform can install the operating system image specified by the tenant on the logical node. The logical node with the operating system image installed can be remotely logged into by the tenant to schedule these virtual devices on the logical node under the tenant's instructions to complete the tenant's business, thereby meeting the tenant's business needs. In the aforementioned process, since the logical node specification requirements set by the tenant for the logical node can be used to describe the specifications of various physical devices required to create the logical node, it can be seen that the specifications of the physical devices required to create the logical node can be freely customized by the tenant. The cloud management platform only needs to select and provide physical devices that match these specifications to complete the creation of the logical node and provide it to the tenant for use. This helps to reduce the consumption of the cloud management platform when performing resource management, and can also meet the tenant's customization requirements for the specifications of the physical devices used by the logical node.

[0296] Furthermore, in this embodiment of the application, since the specifications of the physical equipment required by the logical node can be freely customized by the tenant, the cloud management platform can determine the tenant's physical equipment requirements for the logical node (which can be determined based on the logical node creation request sent by the tenant for the logical node), and thus determine the amount of various physical equipment that needs to be prepared, which can improve the certainty of resource management and resource utilization, and reduce the cost of resource management.

[0297] Furthermore, in this embodiment, if a tenant needs to scale up or down the logical node, the cloud management platform can provide additional physical devices to the logical node or remove the original physical devices while ensuring that the tenant's business is not interrupted. This not only meets the tenant's scaling up or down requirements for the logical node, but also ensures the normal operation of the business, thereby improving the tenant's experience.

[0298] The above is a detailed description of the logical node configuration method based on cloud services provided in the embodiments of this application. The cloud management platform provided in the embodiments of this application will be introduced below. Figure 9 A schematic diagram of the structure of the cloud management platform provided in the embodiments of this application is shown below. Figure 9 As shown, the cloud management platform is used to manage the infrastructure, which includes CPU device pools, memory device pools, network interface card (NIC) device pools, and disk device pools. Multiple CPUs in the CPU device pool, multiple memory modules in the memory device pool, multiple NICs in the NIC device pool, and multiple disks in the disk device pool are all connected to a high-speed interconnect network. This high-speed interconnect network enables interconnection between devices within and between the various device pools in the infrastructure. The cloud management platform includes:

[0299] The acquisition module 901 is used to acquire the logical node creation request input by the tenant. The logical node creation request includes logical node specification requirements, which include CPU requirements, memory requirements, network card requirements, and disk requirements. For example, the acquisition module 901 is used to implement... Figure 4 Step 401 in the illustrated embodiment.

[0300] Creation module 902 is used to create logical nodes in response to logical node specification creation requests. These logical nodes include virtual CPUs, virtual memory, virtual network interface cards (NICs), virtual disks, and a virtual bus network. The virtual CPUs, virtual memory, virtual NICs, and virtual disks are logically connected to the virtual bus network. The virtual CPU is implemented using at least one idle CPU from the CPU device pool that meets CPU requirements. The virtual memory is implemented using at least one idle memory from the memory device pool that meets memory requirements. The virtual NIC is implemented using at least one idle NIC from the NIC device pool that meets NIC requirements. The virtual disk is implemented using at least one idle disk from the disk device pool that meets disk requirements. The virtual bus network is implemented through a sub-network of a high-speed interconnect network. For example, creation module 902 is used to implement... Figure 4 Step 402 in the illustrated embodiment.

[0301] Module 903 is used to determine the operating system image entered or selected by the tenant; for example, module 903 is used to implement... Figure 4 Step 403 in the illustrated embodiment.

[0302] Notification module 904 is used to notify logical nodes to install the operating system image, wherein logical nodes with the operating system image installed allow tenants to log in remotely. For example, notification module 904 is used to implement... Figure 4 Step 404 in the illustrated embodiment.

[0303] In one possible implementation, the acquisition module 901 is further configured to acquire a logical node specification expansion request input by the tenant, the logical node specification expansion request being used to request the expansion of one or any combination of virtual CPU, virtual memory, virtual network interface card, and virtual disk to a predetermined specification; the cloud management platform also includes: an expansion module, configured to: select a corresponding idle device from one or any combination of CPU device pool, memory device pool, network interface card device pool, and disk device pool according to the logical node specification expansion request, wherein the idle device matches the predetermined specification; and connect the idle device to the virtual bus network.

[0304] In one possible implementation, the acquisition module 901 is further configured to acquire a logical node specification scaling-down request input by the tenant. The logical node specification scaling-down request is used to request scaling down one or any combination of virtual CPUs, virtual memory, virtual network cards, and virtual disks to a predetermined specification. The cloud management platform also includes a scaling-down module, configured to control the devices mapped to one or any combination of virtual CPUs, virtual memory, virtual network cards, and virtual disks to exit the virtual bus network according to the logical node specification scaling-down request, and mark the status of the devices as idle.

[0305] In one possible implementation, the infrastructure also includes an extended processor device pool comprising multiple extended processors connected to a high-speed interconnect network. The logical node specification creation request also includes extended processor requirements. The logical node also includes virtual extended processors logically connected to the bus network. The virtual extended processors are mapped to at least one idle extended processor in the extended processor device pool that meets the extended processor requirements.

[0306] In one possible implementation, the extended processor type of the extended processor device pool is one or any combination of NPU, GPU, TPU, and DPU.

[0307] In one possible implementation, high-speed interconnect networks are achieved through PCIe networks, IB networks, or CXL networks.

[0308] It should be noted that the information interaction and implementation process between the modules / units of the above-mentioned device are based on the same concept as the method embodiment of this application, and the resulting technical effects are the same as those of the method embodiment of this application. For details, please refer to the description in the method embodiment shown above in the embodiment of this application, and it will not be repeated here.

[0309] Please see Figure 10 , Figure 10 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Figure 10 As shown, the computing device 1000 (which can be used to present the aforementioned cloud management platform) includes: a processor 1001, a memory 1002, a communication interface 1003, and a bus 1004. The processor 1001, memory 1002, and communication interface 1003 are coupled via the bus (not shown in the figure). The memory 1002 stores instructions. When the instructions in the memory 1002 are executed, the computing device 1000 executes the method performed by the cloud management platform in the above method embodiment.

[0310] The computing device 1000 may be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. Furthermore, when the units in the device can be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling programs. Alternatively, these units may be integrated together and implemented as a system-on-a-chip (SOC).

[0311] The processor 1001 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0312] The memory 1002 can be volatile memory or non-volatile memory, or it can include both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0313] The memory 1002 stores executable program code, and the processor 1001 executes this executable program code to implement the functions of the aforementioned acquisition module, creation module, determination module, and notification module, thereby realizing the above-mentioned cloud service-based logical node configuration method. That is, the memory 1002 stores instructions for executing the above-mentioned cloud service-based logical node configuration method.

[0314] The communication interface 1003 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the computing device 1000 and other devices or communication networks.

[0315] In addition to the data bus, the 1004 bus can also include a power bus, a control bus, and a status signal bus. The bus can be a Peripheral Component Interconnect Express (PCIe) bus, an Extended Industry Standard Architecture (EISA) bus, a Unified Bus (Ubus or UB), a Compute Express Link (CXL) bus, a Cache Coherent Interconnect for Accelerators (CCIX) bus, etc. The bus can be divided into address bus, data bus, and control bus.

[0316] Please see Figure 11 , Figure 11 This is a schematic diagram of a computing device cluster provided in an embodiment of this application. Figure 11 As shown, the computing device cluster 1100 includes at least one computing device 1000.

[0317] like Figure 11 As shown, the computing device cluster 1100 includes at least one computing device 1000. The memory 1002 of one or more computing devices 1000 in the computing device cluster 1100 may store the same instructions for executing the above-described cloud service-based logical node configuration method.

[0318] In some possible implementations, the memory 1002 of one or more computing devices 1000 in the computing device cluster 1100 may also store partial instructions for executing the above-described cloud service-based logical node configuration method. In other words, a combination of one or more computing devices 1000 can jointly execute the above-described cloud service-based logical node configuration method.

[0319] It should be noted that the memory 1002 in different computing devices 1000 within the computing device cluster 1100 can store different instructions, which are used to execute certain functions of the aforementioned cloud management platform. That is, the instructions stored in the memory 1002 of different computing devices 1000 can implement the functions of one or more modules, such as the acquisition module, creation module, determination module, and notification module.

[0320] In some possible implementations, one or more computing devices 1000 in the computing device cluster 1100 can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc.

[0321] Please see Figure 12 , Figure 12 This is a schematic diagram illustrating the network connection of computer devices in a computer cluster provided in an embodiment of this application. Figure 12 As shown, the two computing devices 1000A and 1000B are connected via a network. Specifically, they are connected to the network through the communication interfaces in each computing device.

[0322] In one possible implementation, the memory in computing device 1000A stores instructions for performing the functions of modules such as the acquisition module. Meanwhile, the memory in computing device 1000B stores instructions for performing the functions of modules such as the creation module, the determination module, and the notification module.

[0323] It should be understood that Figure 12 The functions of computing device 1000A shown can also be performed by multiple computing devices. Similarly, the functions of computing device 1000B can also be performed by multiple computing devices.

[0324] This application also relates to a computer storage medium storing a program for signal processing, which, when run on a computer, causes the computer to perform actions such as... Figure 4 The steps performed by the cloud management platform in the illustrated embodiment.

[0325] This application also relates to a computer program product that stores instructions that, when executed by a computer, cause the computer to perform actions such as... Figure 4 The steps performed by the cloud management platform in the illustrated embodiment.

[0326] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0327] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0328] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0329] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0330] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.< / string>

Claims

1. A method for configuring logical nodes based on cloud services, characterized in that, The method is applied to a cloud management platform for managing infrastructure, which includes a CPU device pool, a memory device pool, a network interface card (NIC) device pool, and a disk device pool. Multiple CPUs in the CPU device pool, multiple memory modules in the memory device pool, multiple NICs in the NIC device pool, and multiple disks in the disk device pool are all connected to a high-speed interconnect network. This high-speed interconnect network enables interconnection between devices in each device pool within and between pools. The method includes: The cloud management platform obtains a logical node creation request input by the tenant. The logical node creation request includes logical node specification requirements, which include CPU requirements, memory requirements, network card requirements, and disk requirements. The cloud management platform responds to the logical node specification creation request to create a logical node, wherein the logical node includes a virtual CPU, virtual memory, virtual network interface card (NIC), virtual disk, and virtual bus network. The virtual CPU, virtual memory, virtual NIC, and virtual disk are logically connected to the virtual bus network. The virtual CPU is implemented using at least one idle CPU from the CPU device pool that meets the CPU requirements. The virtual memory is implemented using at least one idle memory from the memory device pool that meets the memory requirements. The virtual NIC is implemented using at least one idle NIC from the NIC device pool that meets the NIC requirements. The virtual disk is implemented using at least one idle disk from the disk device pool that meets the disk requirements. The virtual bus network is implemented through a sub-network of the high-speed interconnect network. The cloud management platform determines the operating system image entered or selected by the tenant; The cloud management platform notifies the logical node to install the operating system image, wherein the logical node with the operating system image installed allows the tenant to log in remotely.

2. The method according to claim 1, characterized in that, The method further includes: The cloud management platform obtains a logical node specification expansion request input by the tenant. The logical node specification expansion request is used to request that one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk be expanded to a predetermined specification. The cloud management platform selects a corresponding idle device from one or any combination of the CPU device pool, memory device pool, network card device pool, and disk device pool according to the logical node specification expansion request, wherein the idle device matches the predetermined specification. The cloud management platform connects the idle devices to the virtual bus network.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The cloud management platform obtains a logical node specification scaling-down request input by the tenant. The logical node specification scaling-down request is used to request that one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk be scaled down to a predetermined specification. The cloud management platform controls one or any combination of the virtual CPU, virtual memory, virtual network card, and virtual disk mapped to the device to exit the virtual bus network according to the logical node specification scaling-down request, and marks the status of the device as idle.

4. The method according to any one of claims 1 to 3, characterized in that, The infrastructure also includes an extended processor device pool, which includes multiple extended processors. All of the multiple extended processors in the extended processor device pool are connected to the high-speed interconnect network. The logical node specification creation request also includes extended processor requirements. The logical node also includes virtual extended processors logically connected to the bus network. The virtual extended processors have a mapping relationship with at least one idle extended processor in the extended processor device pool that meets the extended processor requirements.

5. The method according to claim 4, characterized in that, The extended processor device pool includes an extended processor type of NPU, GPU, TPU, DPU, or any combination thereof.

6. The method according to any one of claims 1 to 5, characterized in that, The high-speed interconnect network is implemented through PCIE network, IB network, or CXL network.

7. A cloud management platform, characterized in that, The cloud management platform is used to manage infrastructure, which includes a CPU device pool, a memory device pool, a network interface card (NIC) device pool, and a disk device pool. Multiple CPUs in the CPU device pool, multiple memory modules in the memory device pool, multiple NICs in the NIC device pool, and multiple disks in the disk device pool are all connected to a high-speed interconnect network. This high-speed interconnect network is used to enable interconnection between devices in each device pool within and between pools. The cloud management platform includes: The acquisition module is used to acquire the logical node creation request input by the tenant. The logical node creation request includes logical node specification requirements, which include CPU requirements, memory requirements, network card requirements, and disk requirements. A creation module is used to create a logical node in response to the logical node specification creation request. The logical node includes a virtual CPU, virtual memory, a virtual network interface card (NIC), a virtual disk, and a virtual bus network. The virtual CPU, virtual memory, virtual NIC, and virtual disk are logically connected to the virtual bus network. The virtual CPU is implemented using at least one idle CPU from the CPU device pool that meets the CPU requirements. The virtual memory is implemented using at least one idle memory from the memory device pool that meets the memory requirements. The virtual NIC is implemented using at least one idle NIC from the NIC device pool that meets the NIC requirements. The virtual disk is implemented using at least one idle disk from the disk device pool that meets the disk requirements. The virtual bus network is implemented through a sub-network of the high-speed interconnect network. The determination module is used to determine the operating system image input or selected by the tenant; The notification module is used to notify the logical node to install the operating system image, wherein the logical node with the operating system image installed allows the tenant to log in remotely.

8. The cloud management platform according to claim 7, characterized in that, The acquisition module is further configured to acquire a logical node specification expansion request input by the tenant, wherein the logical node specification expansion request is used to request that one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk be expanded to a predetermined specification; The cloud management platform also includes: a capacity expansion module, used for: Based on the logical node specification expansion request, a corresponding idle device is selected from one or any combination of the CPU device pool, memory device pool, network card device pool, and disk device pool, wherein the idle device matches the predetermined specification. Connect the idle device to the virtual bus network.

9. The cloud management platform according to claim 7 or 8, characterized in that, The acquisition module is further configured to acquire a logical node specification scaling-down request input by the tenant, wherein the logical node specification scaling-down request is used to request scaling down one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk to a predetermined specification. The cloud management platform also includes a scaling-down module, which controls the device mapped to one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk to exit the virtual bus network according to the scaling-down request of the logical node specifications, and marks the status of the device as idle.

10. The cloud management platform according to any one of claims 7 to 9, characterized in that, The infrastructure also includes an extended processor device pool, which includes multiple extended processors. All of the multiple extended processors in the extended processor device pool are connected to the high-speed interconnect network. The logical node specification creation request also includes extended processor requirements. The logical node also includes virtual extended processors logically connected to the bus network. The virtual extended processors have a mapping relationship with at least one idle extended processor in the extended processor device pool that meets the extended processor requirements.

11. The cloud management platform according to claim 10, characterized in that, The extended processor device pool includes an extended processor type of NPU, GPU, TPU, DPU, or any combination thereof.

12. The cloud management platform according to any one of claims 7 to 11, characterized in that, The high-speed interconnect network is implemented through PCIE network, IB network, or CXL network.

13. A computing device cluster, characterized in that, The computing device cluster includes at least one computing device, each computing device including a processor and memory: The memory is used to store instructions; The processor is configured to, according to the instructions, cause the computing device cluster to perform the method of any one of claims 1 to 6.

14. A computer storage medium, characterized in that, The computer storage medium stores one or more instructions that, when executed by one or more computers, cause the one or more computers to perform the method of any one of claims 1 to 6.

15. A computer program product, characterized in that, The computer program product stores instructions that, when executed by a computer, cause the computer to perform the method described in any one of claims 1 to 6.

Images