Cloud service-based logical node configuration method and cloud management platform

Abstract

The present application discloses a cloud service-based logical node configuration method and a cloud management platform, which can satisfy customization requirements of a tenant for the specifications of physical devices used by logical nodes. The method of the present application comprises: a cloud management platform receiving a logical node creation request sent by a tenant for a logical node of the tenant. Because the logical node creation request is used for indicating logical node specification requirements set by the tenant for the logical node, the cloud management platform can select, from physical device pools, physical devices that satisfy the logical node specification requirements and are idle, and create the logical node on the physical devices, wherein the logical node comprises virtual devices implemented on the basis of the physical devices. Therefore, the cloud management platform can install, on the logical node, an operating system image specified by the tenant, so that the logical node on which the operating system image is installed can allow for remote login of the tenant.

Description

A logical node configuration method based on cloud services and a cloud management platform

[0001] The present application claims priority to the Chinese Patent Application No. 202410799269.4, filed on June 19, 2024, entitled "A node creation method based on a cloud management platform and a cloud management platform", and to the Chinese Patent Application No. 202411096620.X, filed on August 09, 2024, entitled "A logical node configuration method based on cloud services and a cloud management platform", both of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of cloud technology, and in particular to a logical node configuration method based on cloud services and a cloud management platform. BACKGROUND

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

[0004] In related technologies, the cloud service system provided by the cloud vendor can include a cloud management platform and infrastructure, and the infrastructure includes various specifications of cloud resources. When a tenant needs to create a logical node that belongs to the tenant on the cloud, the cloud management platform provides various cloud resources of a preset specification that can build the logical node to the tenant, so that the tenant selects and matches these cloud resources to determine the cloud resources used to build the logical node. Based on this, the cloud management platform can create the logical node of the tenant on these cloud resources determined by the tenant to provide cloud services for the tenant.

[0005] In the above process, in order to try to meet the tenant's free customization of the specification of the resources used to build the logical node, the cloud management platform needs to create various cloud resources of enough specifications for the tenant to select and match. In this way, it will bring great consumption to the resource management of the cloud management platform, and often cannot meet the various customization needs of the tenant for the specification of the resources. SUMMARY

[0006] Embodiments of the present application provide a logical node configuration method based on cloud services and a cloud management platform, which not only helps to reduce the consumption of the cloud management platform when performing resource management, but also meets the customization needs of the tenant for the specification of the physical devices used by the logical node.

[0007] A first aspect of the embodiments of the present application provides a method for configuring a logical node based on cloud services. The method is applied to a cloud management platform, which is used to manage infrastructures. The infrastructures can include a CPU device pool, a memory device pool, a network card device pool, and a disk device pool. The CPUs in the CPU device pool, the memories in the memory device pool, the network cards in the network card device pool, and the disks in the disk device pool are all connected to a high-speed interconnection network, which is used to realize the interconnection of the physical devices in each physical device pool within the pool and between the pools. The method includes the following steps:

[0008] When a tenant needs to create a logical node dedicated to the tenant, the cloud management platform can provide a creation interface to the tenant. Then, the tenant can input a logical node creation request for the logical node to the creation interface. In this way, the cloud management platform can receive the logical node creation request for the logical node sent by the tenant through the creation interface. It is worth noting that the logical node creation request for the logical node contains the logical node specification requirements set by the tenant for the logical node, which include CPU requirements, memory requirements, network card requirements, and disk requirements.

[0009] After obtaining the logical node creation request for the logical node, the cloud management platform can parse the logical node specification requirements from the logical node creation request. Since the requirements include CPU requirements, memory requirements, network card requirements, and disk requirements, the cloud management platform can select CPUs that meet the CPU requirements and are idle from the CPU device pool, select memories that meet the memory requirements and are idle from the memory device pool, select network cards that meet the network card requirements and are idle from the network card device pool, and select disks that meet the disk requirements and are idle from the disk device pool. Then, the cloud management platform can create the logical node on the CPUs, the memories, the network cards, and the disks. The logical node contains virtual CPUs implemented based on the CPUs, virtual memories implemented based on the memories, virtual network cards implemented based on the network cards, virtual disks implemented based on the disks, and a virtual bus network. It is worth noting that in the logical node, the CPUs, the memories, the network cards, and the disks can communicate through the sub-network, so the virtual CPUs, the virtual memories, the virtual network cards, and the virtual disks can communicate through the virtual bus network implemented based on the sub-network.

[0010] After the creation of the logical node, the cloud management platform can remind the tenant to specify an operating system image. Then, 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 used by the tenant to remotely log in, so as to schedule the virtual devices of the logical node under the instruction of the tenant to complete the business of the tenant, thereby meeting the business requirements of the tenant.

[0011] As can be seen from the above method, since the logical node specification requirement set by the tenant for the logical node can be used to describe the specification of various physical devices (including CPU, memory, network card, disk, etc.) required for creating the logical node, it can be seen that the specification of the physical device required for creating the logical node can be freely customized by the tenant, and the cloud management platform only needs to select and provide physical devices matching the specifications to complete the creation of the logical node and provide it to the tenant for use, which is conducive to reducing the consumption of the cloud management platform in resource management, and can also meet the customization requirement of the tenant on the specification of the physical device used by the logical node.

[0012] In a possible implementation, the method further includes: the cloud management platform obtaining a logical node specification expansion request input by the tenant, the logical node specification expansion request being used to request expansion of one or any combination of virtual CPU, virtual memory, virtual network card, and virtual disk by a predetermined specification; the cloud management platform selecting corresponding idle devices from one or any combination of the CPU device pool, the memory device pool, the network card device pool, and the disk device pool according to the logical node specification expansion request, wherein the idle devices match the predetermined specification; and the cloud management platform connecting the idle devices to the virtual bus network. In the foregoing implementation, when the tenant needs to expand the logical node, the cloud management platform can provide an expansion interface to the tenant. Then, the tenant can input a logical node specification expansion request for the logical node to the expansion interface, the logical node specification expansion request being used to request expansion of one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk included in the logical node by a predetermined specification set by the tenant. Based on the logical node specification expansion request, the cloud management platform selects corresponding idle devices from one or any combination of the CPU device pool, the memory device pool, the network card device pool, and the disk device pool, wherein the specification of the idle devices selected by the cloud management platform matches the predetermined specification set by the tenant. After the idle devices are determined, the cloud management platform connects the idle devices to the virtual bus network of the logical node. Then, the physical devices used to implement the virtual CPU, the virtual memory, the virtual network card, and the virtual disk in the logical node include not only the original CPU, the expansion processor, the memory, the network card, and the disk, but also the idle devices, so the specification of one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk in the logical node is increased, and the expansion of the logical node is successfully implemented. As can be seen, if the tenant needs to expand the logical node, the cloud management platform can provide additional idle devices to the logical node on the basis of ensuring that the business of the tenant does not interrupt, which not only meets the expansion requirement of the tenant on the logical node, but also ensures the normal operation of the business, thereby improving the tenant experience.

[0013] In a possible implementation, the method further includes: the cloud management platform obtaining a logical node specification scaling request input by the tenant, the logical node specification scaling request being used to request scaling down one or any combination of virtual CPUs, virtual memories, virtual network cards, and virtual disks to a predetermined specification; and the cloud management platform controlling the devices mapped by one or any combination of virtual CPUs, virtual memories, virtual network cards, and virtual disks to exit the virtual bus network and marking the state of the devices as idle according to the logical node specification scaling request. In the foregoing implementation, when the tenant needs to scale down the logical node, the cloud management platform can provide a scaling interface to the tenant. Then, the tenant can input a logical node specification scaling request for the logical node to the scaling interface, the logical node specification scaling request being used to request scaling down one or any combination of the virtual CPUs, the virtual memories, the virtual network cards, and the virtual disks included in the logical node to a predetermined specification set by the tenant. Based on the logical node specification scaling request, the cloud management platform controls the devices mapped by one or any combination of virtual CPUs, virtual memories, virtual network cards, and virtual disks in the logical node to exit the virtual bus network and marks the state of the exited devices as idle. Then, the physical devices used to implement the virtual CPUs, the virtual memories, the virtual network cards, and the virtual disks in the logical node are reduced by the exited devices, the specification of one or any combination of the virtual CPUs, the virtual memories, the virtual network cards, and the virtual disks in the logical node is reduced, and the scaling down of the logical node is successfully implemented. If the tenant needs to scale down the logical node, the cloud management platform can delete the original devices from the logical node on the premise that the business of the tenant is not interrupted. This not only meets the scaling down requirement of the tenant for the logical node, but also ensures the normal operation of the business, thereby improving the tenant experience.

[0014] [Corrected according to Rule 91 on 20.10.2025] In one possible implementation manner, the infrastructure further comprises an extended processor device pool, the extended processor device pool comprising a plurality of extended processors, the plurality of extended processors in the extended processor device pool each accessing into the high-speed interconnection network, the logical node creation request further comprising an extended processor requirement, the logical node further comprising a virtual extended processor logically connected with the bus network, the virtual extended processor having a mapping relationship with at least one extended processor in the extended processor device pool that meets the extended processor requirement and is idle. In the foregoing implementation manner, when the logical node specification requirement further contains the extended processor requirement, the cloud management platform can further select an extended processor that meets the extended processor requirement and is idle from the extended processor device pool, and create the logical node on the CPUs, the extended processors, the memories, the network cards, and the disks. Accordingly, the logical node contains virtual CPUs implemented based on the CPUs, virtual extended processors implemented based on the extended processors, virtual memories implemented based on the memories, virtual network cards implemented based on the network cards, virtual disks implemented based on the disks, and a virtual bus network. The virtual bus network can be logically connected with the virtual CPUs, the virtual extended processors, the virtual memories, the virtual network cards, and the virtual disks, that is, the virtual CPUs, the virtual extended processors, the virtual memories, the virtual network cards, and the virtual disks can communicate through the virtual bus network.

[0015] In one possible implementation manner, 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 manner, the high-speed interconnection network is implemented through a PCIE network, an IB network, or a CXL network.

[0017] [Corrected according to Rule 91 on 20.10.2025] The second aspect of the embodiments of the application provides a cloud management platform, the cloud management platform is used for managing an infrastructure, the infrastructure includes a CPU device pool, a memory device pool, a network card device pool and a disk device pool, a plurality of CPUs in the CPU device pool, a plurality of memories in the memory device pool, a plurality of network cards in the network card device pool and a plurality of disks in the disk device pool are all accessed to a high-speed interconnection network, wherein the high-speed interconnection network is used to realize the interconnection of the devices in each device pool in the infrastructure within the pool and between the pools, the cloud management platform comprises: an acquisition module, configured to acquire a logical node creation request input by a tenant, the logical node creation request comprising a logical node specification requirement, the logical node specification requirement comprising a CPU requirement, a memory requirement, a network card requirement and a disk requirement; a creation module, configured to create a logical node in response to the logical node creation request, wherein the logical node comprises a virtual CPU, a virtual memory, a virtual network card, a virtual disk and a virtual bus network, the virtual CPU, the virtual memory, the virtual network card and the virtual disk are logically connected with the virtual bus network, the virtual CPU is implemented through at least one CPU in the CPU device pool that meets the CPU requirement and is idle, the virtual memory is implemented through at least one memory in the memory device pool that meets the memory requirement and is idle, the virtual network card is implemented through at least one network card in the network card device pool that meets the network card requirement and is idle, the virtual disk is implemented through at least one disk in the disk device pool that meets the disk requirement and is idle, and the virtual bus network is implemented through a sub-network of the high-speed interconnection network; a determination module, configured to determine an operating system image input or selected by the tenant; and a notification module, configured to notify the logical node to install the operating system image, wherein the logical node installed with the operating system image allows the tenant to remotely log in.

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

[0019] In a possible implementation, the obtaining module is further configured to obtain a logical node specification scaling-down request input by the tenant, the logical node specification scaling-down request being used to request scaling down of one or any combination of virtual CPUs, virtual memories, virtual network cards, and virtual disks to a predetermined specification; and the cloud management platform further includes a scaling-down module configured to control a device mapped to one or any combination of virtual CPUs, virtual memories, virtual network cards, and virtual disks to exit the virtual bus network and mark a state of the device as idle according to the logical node specification scaling-down request.

[0020] [According to Rule 91 Correction 20.10.2025] In a possible implementation, the infrastructure further includes an extension processor device pool, the extension processor device pool including a plurality of extension processors, the plurality of extension processors in the extension processor device pool being connected to the high-speed interconnection network, the logical node creation request further including an extension processor requirement, and the logical node further including a virtual extension processor logically connected to the bus network, the virtual extension processor having a mapping relationship with at least one extension processor in the extension processor device pool that meets the extension processor requirement and is idle.

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

[0022] In a possible implementation, the high-speed interconnection network is implemented through a PCIE network, an IB network, or a CXL network.

[0023] A third aspect of the embodiments of the present application provides a cloud service system, the cloud service system including infrastructure and a cloud management platform for managing the infrastructure, the infrastructure including a CPU device pool, a memory device pool, a network card device pool, and a disk device pool, a plurality of CPUs in the CPU device pool, a plurality of memories in the memory device pool, a plurality of network cards in the network card device pool, and a plurality of disks in the disk device pool being connected to a high-speed interconnection network, where the high-speed interconnection network is used to implement interconnection of devices in each device pool in the infrastructure within the pool and between the pools; and the cloud management platform performs the method described in the first aspect or any possible implementation manner of the first aspect on the infrastructure.

[0024] A fourth aspect of the embodiments of the present 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; and the processor is used to cause the computing device cluster to perform the method described in the first aspect or any possible implementation manner of the first aspect according to the instructions.

[0025] The fifth aspect of the embodiments of the present application provides a computer storage medium, which stores one or more instructions, and the instructions, when executed by one or more computers, cause the one or more computers to implement the method in the first aspect or any possible implementation manner of the first aspect.

[0026] The sixth aspect of the embodiments of the present application provides a computer program product, which stores instructions, and the instructions, when executed by a computer, cause the computer to implement the method in the first aspect or any possible implementation manner of the first aspect.

[0027] In the embodiments of the present application, when a tenant needs to create a logical node, the tenant can send a logical node creation request for the logical node to a creation interface provided by the cloud management platform, and therefore the cloud management platform can receive the logical node creation request (including CPU demand, memory demand, network card demand, disk demand, etc.) sent by the tenant through the creation interface. Since the logical node creation request includes the logical node specification demand set by the tenant for the logical node, the cloud management platform can select physical devices (including CPU, memory, network card, and disk, etc.) that meet the logical node specification demand set by the tenant and are idle from a plurality of physical device pools (including a CPU device pool, a memory device pool, a network card device pool, and a disk device pool, etc.), and create the logical node on the physical devices. Since the logical node includes virtual devices (including virtual CPU, virtual memory, virtual network card, and virtual disk, etc.) implemented based on the physical devices, and the virtual devices are connected through a virtual bus network, the cloud management platform can install an operating system image specified by the tenant on the logical node, and the logical node with the operating system image installed can be remotely logged in by the tenant to schedule the virtual devices of the logical node under the instruction of the tenant to complete the business of the tenant, thereby meeting the business demand of the tenant. In the foregoing process, since the logical node specification demand 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, and the cloud management platform only needs to select and provide physical devices matching the specifications to complete the creation of the logical node and provide the logical node for the tenant to use, which is helpful to reduce the consumption of the cloud management platform when performing resource management, and can also meet the customized demand of the tenant for the specifications of the physical devices used by the logical node. BRIEF DESCRIPTION OF DRAWINGS

[0028] FIG. 1 is a structural schematic diagram of a cloud service system provided by the embodiments of the present application;

[0029] FIG. 2 is a schematic diagram of a tenant interface provided by the embodiments of the present application;

[0030] Fig. 3a is another structural schematic diagram of a cloud service system according to an embodiment of the present application;

[0031] Fig. 3b is a structural schematic diagram of an infrastructure according to an embodiment of the present application;

[0032] Fig. 3c is another structural schematic diagram of an infrastructure according to an embodiment of the present application;

[0033] Fig. 4 is a flow schematic diagram of a node creation method based on a cloud management platform according to an embodiment of the present application;

[0034] Fig. 5 is a schematic diagram of a logical node creation according to an embodiment of the present application;

[0035] Fig. 6 is a schematic diagram of a logical node expansion according to an embodiment of the present application;

[0036] Fig. 7 is another schematic diagram of a logical node expansion according to an embodiment of the present application;

[0037] Fig. 8 is a schematic diagram of a logical node contraction according to an embodiment of the present application;

[0038] Fig. 9 is a structural schematic diagram of a cloud management platform according to an embodiment of the present application;

[0039] Fig. 10 is a structural schematic diagram of a computing device according to an embodiment of the present application;

[0040] Fig. 11 is a structural schematic diagram of a computing device cluster according to an embodiment of the present application;

[0041] Fig. 12 is a schematic diagram of a connection of computing devices in a computer cluster through a network according to an embodiment of the present application. DETAILED DESCRIPTION

[0042] The embodiments of the present application provide a logical node configuration method based on cloud service and a cloud management platform, which not only helps to reduce the consumption of the cloud management platform when performing resource management, but also meets the customization requirements of the tenant on the specifications of the physical devices used by the logical node.

[0043] The terms "first", "second", etc. in the specification and claims of the present application and in the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the terms thus used can be interchanged under appropriate circumstances, which is merely a distinguishing way adopted in the description of the embodiments of the present application for the objects with the same properties in the description. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, so that the processes, methods, systems, products or devices containing a series of units do not have to be limited to those units, but can include other units not clearly listed or inherent to the processes, methods, products or devices.

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

[0045] In related technologies, a cloud service system provided by a cloud vendor can include a cloud management platform and infrastructures, which include cloud resources of various specifications. When a tenant needs to create a logical node that belongs to the tenant in the cloud, the cloud management platform provides the tenant with various cloud resources of preset specifications that can be used to build the logical node, so that the tenant selects and matches these cloud resources to determine the cloud resources that are finally used to build the logical node. Based on this, the cloud management platform can create the logical node of the tenant on these cloud resources determined by the tenant, to provide cloud services for the tenant. For example, the cloud management platform can provide the tenant with cloud resources such as a 4-core central processing unit (CPU), an 8-core CPU, 4G storage, 8G memory, a 1G network card, or a 2G network card. Then, the tenant can select a 4-core CPU, 8G memory, and a 1G network card to match the cloud resources required by the logical node of the tenant, so the cloud management platform can create the logical node of the tenant on these cloud resources.

[0046] In the above process, in order to try to meet the tenant's free customization of the specifications of the resources used to build the logical node, the cloud management platform needs to create various cloud resources of enough specifications for the tenant to select and match. In this way, it will bring great consumption to the resource management of the cloud management platform, and often cannot meet the various customization needs of the tenant for the specifications of the resources.

[0047] Further, since the tenant cannot freely customize the specifications of the resources used to build the logical node, the cloud management platform cannot determine the specific needs of the tenant for the cloud resources, which leads to that the cloud management platform cannot determine how many cloud resources of each specification need to be prepared, and brings great uncertainty, low resource utilization, and high cost to resource management.

[0048] Further, if the tenant needs to change the specification of a certain cloud resource used by the logical node at any time, the related technologies have to shut down the logical node, migrate the logical node, and restart the logical node to realize the specification modification of the cloud resource, which may interrupt the business of the tenant and lead to poor experience of the tenant.

[0049] To solve the above problems, the embodiment of the present application provides a logical node configuration method based on cloud service. The method can be implemented through a cloud service system. FIG. 1 is a structural schematic diagram of the cloud service system provided by the embodiment of the present application. As shown in FIG. 1, the cloud service system comprises infrastructure capable of providing cloud service and a cloud management platform for managing the infrastructure. The cloud management platform and the infrastructure are introduced respectively as follows:

[0050] The cloud management platform can overall manage the infrastructure in the whole cloud service system (for example, in the infrastructure, create one or more logical nodes for a tenant according to the indication of the tenant, and the logical nodes can be used to complete the business of the tenant, etc.), and can also be open to the tenant outside the cloud service system and respond to the request of the tenant. For example, the cloud management platform can provide various interfaces such as a login interface, a creation interface, a capacity expansion interface, a capacity reduction interface, and a query interface, so as to be accessed by the client of the tenant (for example, a terminal device used by the tenant or a browser on the terminal device, etc.). Among them, the cloud management platform can authenticate the client of the tenant through the login interface, and allow the client of the tenant to log in to the cloud management platform after the authentication is successful. For another example, the cloud management platform can also allow the client of the tenant to send a logical node creation request for the logical node of the tenant to the cloud management platform through the creation interface. Since the logical node creation request is used to indicate the logical node specification requirement (customized) set by the tenant for the logical node, the logical node specification requirement is used to describe the specification of various devices required to create the logical node, the cloud management platform can select idle physical devices that meet the logical node specification requirement from various physical device pools, and create the logical node on the physical devices. Since the logical node contains virtual devices implemented based on the physical devices, the cloud management platform can install an operating system image prepared by the tenant on the logical node, so that the logical node installed with the operating system image can allow the tenant to remotely log in, thereby providing remote service for the tenant and meeting the business requirement of the tenant. For another example, the cloud management platform can also allow the client of the tenant to send a logical node specification capacity expansion request for the logical node to the cloud management platform through the capacity expansion interface. The logical node specification capacity expansion request is used to request to expand the virtual devices used by the logical node to a predetermined specification, so the cloud management platform can select idle devices that meet the predetermined specification from various physical device pools, and additionally add the idle devices to the logical node, thereby realizing capacity expansion. For another example, the cloud management platform can also allow the client of the tenant to send a logical node specification capacity reduction request for the logical node to the cloud management platform through the capacity reduction interface. The logical node specification capacity reduction request is used to request to reduce the virtual devices used by the logical node to a predetermined specification, so the cloud management platform can select virtual devices that meet the predetermined specification from the logical node, and make the logical node unable to use the physical devices mapped by the virtual devices, thereby realizing capacity reduction.

[0051] It is worth noting that, as shown in FIG. 2 (FIG. 2 is a schematic diagram of a tenant interface provided by an embodiment of the present application), the cloud management platform provides a creation interface, a capacity expansion interface, a capacity reduction interface, and a query interface to the tenant, which can correspond to a logical node creation column, a logical node capacity expansion column, a logical node capacity reduction column, and a logical node query column in the tenant interface. For the cloud management platform internally, the example code of the tenant interface can be as follows:

[0052] It can be seen that the logical node creation request is used to indicate the resource parameters set by the tenant for the logical node, which are used to describe the logical node specification requirement of the logical node, including CPU requirement (specification of CPU required for creating the logical node), memory requirement (specification of memory required for creating the logical node), network card requirement (specification of network card required for creating the logical node), disk requirement (specification of disk required for creating the logical node), and extension processor requirement (specification of extension processor required for creating the logical node, NPU being a presentation of the extension processor). For example, it is assumed that the node creation request includes:

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

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

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

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

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

[0058] The logical node creation request includes the resource parameters set by the tenant for the logical node, which are used to describe the specification requirement of the device required for creating the logical node (i.e., the logical node specification requirement), which is that the CPU required for creating the logical node needs to include 4 cores and 8 threads, the storage is 8G memory, the storage is 120G disk, the bandwidth is 1G network card, and the NPU includes 2 cores.

[0059] When the cloud management platform receives the logical node creation request for the logical node, the node creation request can be parsed to obtain the resource parameters set by the tenant for the logical node, as shown in FIG. 3a (FIG. 3a is another structural schematic diagram of a cloud service system provided by an embodiment of the present application), and the resource parameters are taken as the model of the logical node, for example, the model of the logical node can be as follows:

[0060] The model of the logical node: defining the partial specifications of various physical devices required for creating the logical node;

[0061] Method: POST / PUT

[0062] URL: / nodes

[0063] Fields:

[0064] 1. project_id: the identification of the project to which the logical node belongs;

[0065] 2. vpc_id: the identification of the VPC in which the logical node is located;

[0066] 3. cpu_devices: declaring the specifications of the CPU required for creating the logical node;

[0067] 4. mem_devices: declaring the specifications of the memory required for creating the logical node;

[0068] 5. nic_devices: declaring the specifications of the network card required for creating the logical node;

[0069] 6. disk_devices: declaring the specifications of the disk required for creating the logical node;

[0070] 7. npu_devices: declaring the specifications of the NPU required for creating the logical node;

[0071] 8. decription: the description information of the logical node;

[0072] 9. name: the name of the logical node.

[0073] After obtaining the model of the logical node, the cloud management platform can further generate sub-models of various devices of the logical node based on the model of the logical node (the sub-models contain resource parameters set by the tenant for the logical node and resource parameters set by the cloud management platform for the logical node), and the sub-models can describe the total specifications of physical devices required to create the logical node. It should be noted that the sub-models can include a sub-model of a computing device (also referred to as a computing resource, for example, the aforementioned CPU and NPU, etc.) of the logical node, a sub-model of a storage device (also referred to as a storage resource, for example, the aforementioned memory and disk, etc.) of the logical node, and a sub-model of a network device (also referred to as a network resource, for example, the aforementioned network card, etc.) of the logical node. For example, the sub-models can be as follows, respectively:

[0074] a. Sub-model of CPU of the logical node: defines the total specifications of the CPU required to create the logical node;

[0075] Method: POST / PUT

[0076] URL: / devices

[0077] Fields:

[0078] a. 1 devices_type: declares the type of the physical device, enumerated type, and the value is 0, which declares that the physical device is a CPU;

[0079] a. 2 project_id: declares the identification of the project to which the CPU belongs;

[0080] a. 3 node_id: declares the identification (name) of the logical node to which the CPU belongs, which is an optional item;

[0081] a. 4 devices_matadata: the computing power parameter of the CPU, which can include the following items;

[0082] a. 4.1 core_num: the computing power parameter is an integer parameter, which declares the number of cores of the CPU;

[0083] a. 4.2 frequency: the computing power parameter is a long integer parameter, with the unit of Hz, which declares the clock frequency of the CPU;

[0084] a. 4.3 l1_cache: the computing power parameter is a long integer parameter, which declares the size (storage amount) of the L1 cache of the CPU;

[0085] a. 4.4 l2_cache: the computing power parameter is a long integer parameter, which declares the size of the L2 cache of the CPU;

[0086] a.4.5 l3_cache: This computing power parameter is a long integer parameter, which declares the size of the L3 cache of the CPU;

[0087] a.4.6 threads: This computing power parameter is a long integer parameter, which declares the number of threads of the CPU, and the default value is twice the number of cores.

[0088] It should be noted that a.4.1 and a.4.6 are usually included in the resource parameters set by the tenant for the logical node, i.e., 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 the logical node, i.e., a.4.2 to a.4.5 are usually set by the cloud management platform.

[0089] b. Sub-model of the memory of the logical node: define the total specification of the memory required to create the logical node;

[0090] Method: POST / PUT

[0091] URL: / devices

[0092] Fields:

[0093] b.1 devices_type: declares the type of physical device, which is an enumeration type, and its value is 1, which declares that the physical device is memory;

[0094] b.2 project_id: declares the identification of the project to which the memory belongs;

[0095] b.3 node_id: declares the identification of the logical node to which the memory belongs;

[0096] b.4 devices_matadata: the capacity parameter of the memory, which can include the following items;

[0097] b.4.1 size: This capacity parameter is a string parameter, which declares the storage capacity of the memory, i.e., the number of bytes that the memory can store;

[0098] b.4.2 r_speed: This capacity parameter is a long integer parameter, which declares the read speed per second of the memory;

[0099] b.4.3 w_speed: This capacity parameter is a long integer parameter, which declares the write speed per second of the memory;

[0100] It should be noted that b.4.1 is usually included in the resource parameters set by the tenant for the 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 the logical node, that is, b.4.2 to b.4.3 are usually set by the cloud management platform.

[0101] c. Sub-model of the NPU of the logical node: define the total specification of the NPU required to create the logical node;

[0102] Method: POST / PUT

[0103] URL: / devices

[0104] Fields:

[0105] c.1 devices_type: declare the type of the physical device, enumerated type, taking the value 4, declaring the physical device as an NPU;

[0106] c.2 project_id: declare the identification of the project to which the NPU belongs;

[0107] c.3 node_id: declare the identification of the logical node to which the NPU belongs;

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

[0109] c.4.1 core_num: the computing power parameter is an integer parameter, declaring the number of cores of the NPU;

[0110] c.4.2 mem_size: the computing power parameter is a long integer parameter, with the unit byte, declaring the storage amount of the memory of the NPU;

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

[0112] c.4.4 bandwidth: the computing power parameter is a long integer parameter, with the unit bit / s, declaring the bandwidth of the NPU;

[0113] It should be noted that c.4.1 is usually included in the resource parameters set by the tenant for the 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 the logical node, that is, c.4.2 to c.4.4 are usually set by the cloud management platform.

[0114] d. The sub-model of the network card of the logical node: define the total specification of the network card required to create the logical node;

[0115] Method: POST / PUT

[0116] URL: / devices

[0117] Fields:

[0118] d.1 devices_type: declare the type of the physical device, enumerated type, whose value is 2, declare the physical device as a network card;

[0119] d.2 project_id: declare the identification of the project to which the NPU belongs;

[0120] d.3 node_id: declare the identification of the logical node to which the NPU belongs;

[0121] d.4 devices_matadata: the computing power parameters of the network card, which can include the following items;

[0122] d.4.1 pps: the computing power parameter is a long integer parameter, which declares the number of messages transmitted per second by the network card;

[0123] d.4.2 bandwidth: the computing power parameter is a long integer parameter, with a unit of byte, which declares the bandwidth of the network card;

[0124] It should be noted that d.4.1 is usually included in the resource parameters set by the tenant for the logical node, i.e. 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 the logical node, i.e. d.4.2 is usually set by the cloud management platform.

[0125] e. The sub-model of the disk of the logical node: define the total specification of the disk required to create the logical node;

[0126] Method: POST / PUT

[0127] URL: / devices

[0128] Fields:

[0129] e.1 devices_type: declare the type of the physical device, enumerated type, whose value is 2, declare the physical device as a disk;

[0130] e.2 project_id: declare the identification of the project to which the disk belongs;

[0131] e.3 node_id: declares the identity of the logical node to which the disk belongs;

[0132] e.4 devices_matadata: the computing power parameter of the disk, which can include the following items;

[0133] e.4.1 size: the capacity parameter is a long integer parameter, with the unit of bytes, which declares the storage of the disk;

[0134] e.4.2 wr_bandwidth: the capacity parameter is a long integer parameter, with the unit of byte, which declares the read-write speed of the disk;

[0135] e.4.3 interface_type: declares the interface type of the disk, enumeration, sata, etc.;

[0136] e.4.4 cache: the capacity parameter is an integer parameter, with the unit of byte, which declares the storage amount (size) of the cache of the disk;

[0137] e.4.5 ro_speed: the capacity parameter is an integer parameter, with the unit of r / min, which declares the rotation speed of the disk;

[0138] It should be noted that e.4.1 is usually included in the resource parameter set by the tenant for the logical node, that is, e.4.1 is usually set by the tenant. e.4.2 to e.4.5 are usually included in the resource parameter set by the cloud management platform for the 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-mentioned sub-models describe the total specifications of various physical devices required to create the logical node, the cloud management platform can select idle devices that meet these sub-models from various physical device pools to create the logical node of the tenant using the idle devices (of course, the cloud management platform can also not generate the model of the logical node and the sub-models included in the model after obtaining the logical node creation request of the logical node, directly analyze the logical node creation request to obtain the logical node specification requirement of the logical node, and select idle devices that meet the logical node specification requirement from various physical device pools to create the logical node of the tenant using the idle devices, which is not limited here).

[0139] The infrastructure includes a plurality of physical device pools, which include different types of computing device pools, different types of storage device pools, and network device pools. The different types of computing device pools can include a CPU device pool and an extended processor device pool, which can include a graphics processing unit (GPU) device pool, an NPU device pool, a tensor processing unit (TPU) device pool, a data processing unit (DPU) device pool, and the like. The different types of storage device pools can include a memory device pool and a disk device pool, and the like. The network device pool can include a network card device pool, and the like. The CPU device pool includes a plurality of CPUs (which can have the same or different specifications), the extended processor device pool includes a plurality of extended processor device pools (which can have the same or different specifications), the memory device pool includes a plurality of memories (which can have the same or different specifications), the disk device pool includes a plurality of disks (which can have the same or different specifications), and the network card device pool includes a plurality of network cards (which can have the same or different specifications). As can be seen, the cloud management platform can select several types of physical devices that meet the tenant's requirements and have certain specifications from the physical device pools to build the tenant's logical nodes or scale the tenant's logical nodes.

[0140] It is worth noting that the plurality of physical device pools are presented and implemented in communication connection in a plurality of ways.

[0141] (1) As shown in FIG. 3b (which is a structural schematic diagram of the infrastructure provided in an embodiment of the present application), in the plurality of physical device pools, all physical devices in each physical device pool are randomly arranged on racks, rather than being arranged in fixed combinations in the frames of physical servers in the racks. Then, in the plurality of physical device pools, any two physical devices in any physical device pool can be implemented in communication connection through high-speed interconnection devices, and the physical devices between any two physical device pools can also be implemented in communication connection through high-speed interconnection devices. The high-speed interconnection devices can include high-speed interconnection buses and high-speed interconnection bus switches, and the like. As can be seen, the high-speed interconnection devices connect all physical devices of the plurality of physical device pools, and form a high-speed interconnection network (the "high speed" of the high-speed interconnection network means that the bandwidth of the network is not less than 40G / S) between all physical devices. That is, the plurality of CPUs in the CPU device pool, the plurality of extended processors in the extended processor device pool, the plurality of memories in the memory device pool, the plurality of network cards in the network card device pool, and the plurality of disks in the disk device pool are all connected to the high-speed interconnection network, so that the physical devices can be implemented in communication through the high-speed interconnection network.

[0142] It is also worth noting that after the cloud management platform determines the logical node specification requirement of the logical node of the tenant, the cloud management platform can select several physical devices (e.g., CPU, NPU, memory, network card, and disk, etc. in the dashed box of FIG. 3b) that meet the logical node specification requirement from the multiple physical device pools, and create the logical node on these physical devices, which contains virtual devices implemented based on these physical devices (i.e., these physical devices and these virtual devices have a mapping relationship), and since these physical devices are all connected to the high-speed interconnection network, the network formed between these physical devices is part of the high-speed interconnection network, and can also be referred to as a sub-network of the high-speed interconnection network (e.g., the dashed box of FIG. 3b). Since these virtual devices are implemented based on these physical devices, logical connections can also be implemented between these virtual devices through a virtual bus network, which is implemented based on the 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).

[0143] (2) As shown in FIG. 3c (FIG. 3c is another structure schematic diagram of the infrastructure provided by the embodiments of the present application), the multiple physical device pools can be deployed in the form of multiple supernodes, each supernode containing multiple physical servers, and each physical server can contain multiple physical devices of different types (e.g., a physical server contains at least one CPU, at least one memory, at least one expansion processor, at least one network card, and at least one disk), and any two physical servers can be communicatively connected through a high-speed interconnection device, so for the CPU in any one physical server, it can not only use the network card, expansion processor, memory, and disk of the physical server, but also use the network card, expansion processor, memory, and disk of the remaining physical servers, so that the same type of physical devices of different physical servers can be considered as "pooled", so that all physical servers in multiple supernodes form multiple physical device pools. Since all physical servers in multiple supernodes are communicatively connected through high-speed interconnection devices, a high-speed interconnection network is formed between all physical servers, which is equivalent to a high-speed interconnection network formed between multiple physical device pools, that is, multiple CPUs in the CPU device pool, multiple expansion processors in the expansion processor device pool, multiple memories 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 interconnection network, so that these physical devices can communicate through the high-speed interconnection network.

[0144] It is also worth noting that after the cloud management platform obtains the resource orchestration scheme of the multiple sub-tasks of the job task of the tenant, the cloud management platform can select a number of physical devices (for example, a number of physical servers in the dashed box of FIG. 3c, which include CPUs, extended processors, memories, network cards, and disks, which can be regarded as part of the CPU device pool, part of the extended processor device pool, part of the memory device pool, part of the network card device pool, and part of the disk device pool, etc.) that meet the performance requirements of the job task of the tenant from the multiple physical device pools based on the resource orchestration scheme, and create the logical node on these physical devices. The logical node contains virtual devices implemented based on these physical devices (that is, these physical devices and these virtual devices have a mapping relationship), and since these physical devices are all connected to the high-speed interconnection network, the network formed between these physical devices is part of the high-speed interconnection network, and can also be referred to as a sub-network of the high-speed interconnection network (for example, the dashed box of FIG. 3c). Since these virtual devices are implemented based on these physical devices, logical connections can also be achieved between these virtual devices through a virtual bus network, which is implemented based on the sub-network of the high-speed interconnection network formed between these physical devices (that is, the virtual bus network and the sub-network have a mapping relationship).

[0145] Further, as shown in FIG. 3a, each physical device in the multiple physical device pools has an interface of a certain type. For any one physical device, the physical device can access the high-speed interconnection bus switch through the interface it has, and then communicate with the remaining physical devices through the high-speed interconnection bus.

[0146] Further, for the logical node of the tenant, the logical node can generally be regarded as a cloud instance in the infrastructure, which can be presented in various ways. For example, the cloud instances can be the physical server(s) selected by the cloud management platform in the infrastructure, for example, the cloud instances can be the bare metal server selected by the cloud management platform in the infrastructure, for example, the cloud instances can be the virtual machine (VM) created by the cloud management platform on the physical server through virtualization technology, for example, the virtual instances can also be the container (docker) created by the cloud management platform on the physical server through virtualization technology, for example, the virtual instances can also be the micro virtual machine (microVM) created by the cloud management platform on the physical server through virtualization technology, and the like.

[0147] Further, for the plurality of physical device pools, the plurality of physical device pools can be deployed in the same site or different sites, and the site can be presented in various forms, for example, the site can be a region in the infrastructure, for example, the site can be an availability zone in the infrastructure, for example, the site can be a data center (DC) in the infrastructure, for example, the site can be a room in the infrastructure, and the like.

[0148] Further, the high-speed interconnection network built between the plurality of physical device pools can be implemented based on a plurality of high-speed interconnection bus switches, and the plurality of physical device pools are deployed across a data center, which often contains a plurality of racks for placing a plurality of physical devices in each physical device pool. In order to realize communication connection between the physical devices of different racks, at least one high-speed interconnection bus switch needs to be deployed in each rack. In this way, the racks can realize communication connection through the high-speed interconnection bus switches, thereby forming a high-speed interconnection network within the data center.

[0149] Further, the high-speed interconnection network described above can have various forms of presentation, for example, the high-speed interconnection network can be a peripheral component interconnect express (PCIE) network, for example, the high-speed interconnection network can also be an infiniBand (IB) network, for example, the high-speed interconnection network can also be a compute express link (CXL) network, for example, the high-speed interconnection network can also be an interconnection network between devices researched and developed by a cloud vendor (the bandwidth of the network also needs to be not less than 40G / S), and the like. Accordingly, the high-speed interconnection device accessed by each physical device can be a communication device based on the PCIE protocol, the CXL protocol, the IB protocol, or a communication protocol researched and developed by a cloud vendor. Similarly, the interface of the physical device in each physical device pool for accessing the high-speed interconnection network can be a PCIE interface, a CXL interface, an IB interface, or an interface researched and developed by a cloud vendor, and the like.

[0150] Based on the cloud service system, when a tenant needs to create a logical node, the tenant can send a logical node creation request for the logical node to a 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 the logical node, the cloud management platform can select physical devices (including CPUs, memories, network cards, and disks, etc.) that meet the logical node specification requirements set by the tenant and are idle from a plurality of physical device pools (including a CPU device pool, a memory device pool, a network card device pool, and a disk device pool, etc.), and create the logical node on these physical devices. Since the logical node includes virtual devices (including virtual CPUs, virtual memories, 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 an operating system image specified by the tenant on the logical node. The logical node with the operating system image installed can be remotely logged in by the tenant to schedule the virtual devices of the logical node to complete the tenant's business under the instruction of the tenant, thereby meeting the business requirements of the tenant. In the foregoing 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, and the cloud management platform only needs to select and provide physical devices matching these specifications to complete the creation of the logical node and provide it to the tenant, which is helpful to reduce the consumption of the cloud management platform in resource management, and also meets the customization requirements of the tenant for the specifications of the physical devices used by the logical node. In order to understand the workflow of the cloud management platform, the following further introduces the workflow in combination with FIG. 4. FIG. 4 is a flowchart of a logical node configuration method based on a cloud management platform provided by an embodiment of the present application. As shown in FIG. 4, the method can be implemented through the cloud service system shown in FIG. 1. The cloud service system includes infrastructure providing cloud services for tenants and a cloud management platform managing the infrastructure. The infrastructure can include a CPU device pool, a memory device pool, a network card device pool, and a disk device pool. The plurality of CPUs in the CPU device pool, the plurality of memories in the memory device pool, the plurality of network cards in the network card device pool, and the plurality of disks in the disk device pool are all connected to a high-speed interconnection network, which is used to interconnect the physical devices in each physical device pool in the infrastructure. The method includes the following steps:

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

[0152] In this embodiment, when the tenant needs to create a logical node, the cloud management platform can provide a creation interface (e.g., a logical node creation column of a tenant interface, etc.) to the client of the tenant. Then, the tenant can input a logical node creation request for the logical node to the creation interface through the client used by the tenant. In this way, the cloud management platform can receive the logical node creation request for the logical node sent by the tenant through the client through the creation interface. It is worth noting that the logical node creation request for the logical node includes the logical node specification requirement set by the tenant for the logical node, and the logical node specification requirement includes CPU requirement, memory requirement, network card requirement, and disk requirement, wherein the CPU requirement is used to describe the specification of the CPU required for creating the logical node, the memory requirement is used to describe the specification of the memory required for creating the logical node, the network card requirement is used to describe the specification of the network card required for creating the logical node, and the disk requirement is used to describe the specification of the disk required for creating the logical node.

[0153] Further, the logical node specification requirement can also include an extension processor requirement, which is used to describe the specification of the extension processor required for creating the logical node.

[0154] For example, when the tenant needs to create a logical node 1 (node1) and a logical node 2 (node2), the tenant can log in to the cloud management platform, and the cloud management platform can provide a tenant interface to the tenant. Since the tenant interface includes a logical node creation column, the tenant can input a logical node creation request for the logical node 1 and the logical node 2 in the logical node creation column:

[0155] Based on the above logical node creation request, the tenant sets a logical node specification requirement 1 for the logical node 1, and the requirement 1 includes a CPU requirement 1, an NPU requirement 1, a memory requirement 1, a network card requirement 1, and a disk requirement 1. The CPU requirement 1 indicates that the core of the CPU required for creating the logical node 1 is 2, the NPU requirement 1 indicates that the core of the NPU required for creating the logical node 1 is 2, the memory requirement 1 indicates that the storage amount of the memory required for creating the logical node 1 is 8G, the disk requirement 1 indicates that the storage amount of the disk required for creating the logical node 1 is 80G, and the network card requirement 1 indicates that the bandwidth of the network card required for creating the logical node 1 is 1G.

[0156] Similarly, the tenant sets a logical node specification requirement 2 for the logical node 2, the requirement 2 including a CPU requirement 2, an NPU requirement 2, a memory requirement 2, a network card requirement 2, and a disk requirement 2, the CPU requirement 2 indicating that 1 core of CPU is required to create the logical node 2, the NPU requirement 2 indicating that 1 core of NPU is required to create the logical node 2, the memory requirement 2 indicating that 8G of memory is required to create the logical node 2, the disk requirement 2 indicating that 80G of disk is required to create the logical node 2, and the network card requirement 2 indicating that 1G of bandwidth of network card is required to create the logical node 2.

[0157] [According to Rule 91 correction 20.10.2025]402、The cloud management platform creates a logical node in response to a logical node creation request, wherein the logical node includes a virtual CPU, a virtual memory, a virtual network card, a virtual disk, and a virtual bus network, the virtual CPU, the virtual memory, the virtual network card, and the virtual disk are respectively logically connected with the virtual bus network, the virtual CPU is implemented through at least one CPU in a CPU device pool that meets the CPU requirement and is idle, the virtual memory is implemented through at least one memory in a memory device pool that meets the memory requirement and is idle, the virtual network card is implemented through at least one network card in a network card device pool that meets the network card requirement and is idle, the virtual disk is implemented through at least one disk in a disk device pool that meets the disk requirement and is idle, and the virtual bus network is implemented through a sub-network of a high-speed interconnection network.

[0158] After obtaining the logical node creation request for the logical node, the cloud management platform can parse the logical node specification requirement from the logical node creation request. Since the requirement contains CPU requirement, memory requirement, network card requirement and disk requirement, the cloud management platform can select (at least one) CPU that meets the CPU requirement and is idle from the CPU device pool, select (at least one) memory that meets the memory requirement and is idle from the memory device pool, select (at least one) network card that meets the network card requirement and is idle from the network card device pool, and select (at least one) disk that meets the disk requirement and is idle from the disk device pool. Then, the cloud management platform can create the logical node on the CPUs, the memories, the network cards and the disks, and the logical node contains virtual CPUs implemented based on the CPUs, virtual memories implemented based on the memories, virtual network cards implemented based on the network cards, virtual disks implemented based on the disks and a virtual bus network. It should be noted that in the logical node, since the CPUs, the memories, the network cards and the disks are all connected to the sub-network of the high-speed interconnection network, i.e., the CPUs, the memories, the network cards and the disks can communicate through the sub-network, the virtual bus network implemented based on the sub-network can be logically connected with the virtual CPUs, the virtual memories, the virtual network cards and the virtual disks respectively, i.e., the virtual CPUs, the virtual memories, the virtual network cards and the virtual disks can communicate through the virtual bus network.

[0159] Further, when the logical node specification requirement can also contain extension processor requirement, the cloud management platform can also select (at least one) extension processor that meets the extension processor requirement and is idle from the extension processor device pool, and create the logical node on the CPUs, the extension processors, the memories, the network cards and the disks. Accordingly, the logical node contains virtual CPUs implemented based on the CPUs, virtual extension processors implemented based on the extension processors, virtual memories implemented based on the memories, virtual network cards implemented based on the network cards, virtual disks implemented based on the disks and a virtual bus network. It should be noted that the virtual bus network can be logically connected with the virtual CPUs, the virtual extension processors, the virtual memories, the virtual network cards and the virtual disks respectively, i.e., the virtual CPUs, the virtual extension processors, the virtual memories, the virtual network cards and the virtual disks can communicate through the virtual bus network.

[0160] As described above, as shown in FIG. 5 (FIG. 5 is a schematic diagram of creation of a logical node according to an embodiment of the present application), since the cloud management platform has obtained the logical node specification requirement 1 set by the tenant for the logical node 1, the requirement 1 including the CPU requirement 1, the NPU requirement 1, the memory requirement 1, the network card requirement 1 and the disk requirement 1, the cloud management platform selects the CPU and the NPU satisfying the CPU requirement 1 and the NPU requirement 1 from the CPU device pool and the NPU device pool, selects the memory and the disk satisfying the memory requirement 1 and the disk requirement 1 from the memory device pool and the disk device pool, selects the network card satisfying the network card requirement 1 from the network card device pool, and creates the logical node 1 on the selected CPU, NPU, memory, disk and network card. The logical node 1 includes virtual CPUs implemented based on the CPUs, NPUs implemented based on the NPUs, virtual memories implemented based on the memories, virtual network cards implemented based on the network cards, virtual disks implemented based on the disks and a virtual bus network. The virtual CPUs, the virtual expansion processors, the virtual memories, the virtual network cards, the virtual disks can communicate with each other through the virtual bus network.

[0161] Similarly, since the cloud management platform has obtained the logical node specification requirement 2 set by the tenant for the logical node 2, the requirement 2 including the CPU requirement 2, the NPU requirement 2, the memory requirement 2, the network card requirement 2 and the disk requirement 2, the cloud management platform selects the CPU and the NPU satisfying the CPU requirement 2 and the NPU requirement 2 from the CPU device pool and the NPU device pool, selects the memory and the disk satisfying the memory requirement 2 and the disk requirement 2 from the memory device pool and the disk device pool, selects the network card satisfying the network card requirement 2 from the network card device pool, and creates the logical node 2 on the selected CPU, NPU, memory, disk and network card. The logical node 2 includes virtual CPUs implemented based on the CPUs, NPUs implemented based on the NPUs, virtual memories implemented based on the memories, virtual network cards implemented based on the network cards, virtual disks implemented based on the disks and a virtual bus network. The virtual CPUs, the virtual expansion processors, the virtual memories, the virtual network cards, the virtual disks can communicate with each other through the virtual bus network.

[0162] Specifically, the cloud management platform can further perform the following operations:

[0163] When the tenant needs to expand the capacity of the logical node, the cloud management platform can provide an expansion interface (for example, a logical node expansion column of a tenant interface, etc.) to the client of the tenant. Then, the tenant can input a logical node specification expansion request for the logical node to the expansion interface through the client used by the tenant. The logical node specification expansion request is used to request to expand one or any combination of the virtual CPUs, the virtual memories, the virtual network cards and the virtual disks included in the logical node to a predetermined specification set by the tenant.

[0164] Based on the logical node specification expansion request, the cloud management platform selects corresponding idle devices from one or any combination of the CPU device pool, the memory device pool, the network card device pool, and the disk device pool, wherein the specification of the idle devices selected by the cloud management platform matches the predetermined specification set by the tenant.

[0165] After determining the idle devices, the cloud management platform connects the idle (physical) devices to the virtual bus network of the logical node, and the idle devices can also be used to implement the virtual devices of the logical node. That is, the idle devices can include one or any combination of the newly selected idle CPU, idle NPU, idle memory, idle disk, and idle network card, and the physical devices of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk in the logical node include not only the original CPU, the expansion processor, the memory, the network card, and the disk, but also one or any combination of the newly selected idle CPU, idle NPU, idle memory, idle disk, and idle network card. Therefore, the specification of one or any combination of the virtual CPU, the virtual memory, the virtual network card, and the virtual disk in the logical node is increased, that is, the cloud management platform successfully implements expansion of the logical node.

[0166] Still as in the above example, as shown in FIG. 6 (FIG. 6 is a schematic diagram of logical node expansion provided by an embodiment of the present application, and FIG. 6 is obtained based on FIG. 5), if the tenant needs to increase the bandwidth of the virtual network card of logical node 2 by 1G and increase the storage capacity of the virtual disk to 120G, the tenant can input the following logical node specification expansion request to the logical node expansion column in the tenant interface:

[0167] Based on the above logical node specification expansion request, it is known that the tenant needs to increase the bandwidth of the virtual network card of logical node 2 by 1G and increase the storage capacity of the virtual disk by 40G. Therefore, the cloud management platform can select network cards with a bandwidth of 1G from the network card device pool and select disks with a storage capacity of 40G from the disk device pool, and connect the network cards and the disks to the virtual bus network inside logical node 2. In this way, the virtual network card of logical node 2 is implemented based on network cards with a bandwidth of 2G, and the virtual disk is implemented based on disks with a storage capacity of 120G, which is equivalent to successfully expanding the virtual network card and the virtual disk.

[0168] For example, as shown in FIG. 7 (FIG. 7 is another schematic diagram of logical node expansion provided by an embodiment of the present application, and FIG. 7 is drawn on the basis of FIG. 6), assuming that the tenant needs to increase the virtual memory of logical node 2 by 8G of storage and increase the virtual NPU by 1 core, the tenant can input the following logical node specification expansion request to the logical node expansion column in the tenant interface:

[0169] Based on the above logical node specification expansion request, the tenant needs to increase the virtual memory of logical node 2 by 8G of storage and increase the virtual NPU by 1 core. Therefore, the cloud management platform can select 8G of memory from the memory device pool and select 1 core of NPU from the NPU device pool, and add these memories and NPUs to the virtual bus network inside logical node 2. In this way, the virtual memory of logical node 2 is implemented based on 16G of memory, and the virtual NPU is implemented based on 2 cores of NPU, which is equivalent to expanding the virtual memory and virtual disk NPU.

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

[0171] When the tenant needs to perform capacity reduction on the logical node, the cloud management platform can provide the tenant's client with a capacity reduction interface (for example, a logical node capacity reduction column of the tenant interface, etc.). Then, the tenant can input a logical node specification capacity reduction request for the logical node to the capacity reduction interface through the client used by the tenant, and the logical node specification capacity reduction request is used to request to reduce one or any combination of the virtual CPU, the virtual memory, the virtual network card and the virtual disk contained in the logical node to the predetermined specification set by the tenant.

[0172] Based on the logical node specification capacity reduction request, the cloud management platform controls the (physical) devices mapped by one or any combination of the virtual CPU, the virtual memory, the virtual network card and the virtual disk in the logical node to exit the virtual bus network, and marks the state of the exited devices as idle.

[0173] Since the exited physical devices include one or any combination of the exited part of the CPUs, the exited part of the memories, the exited part of the network cards and the exited part of the disks, that is, the physical devices used to implement the virtual CPUs, the virtual memories, the virtual network cards and the virtual disks in the logical node, the specification of one or any combination of the virtual CPUs, the virtual memories, the virtual network cards and the virtual disks in the logical node is reduced, that is, the cloud management platform successfully implements the scaling down of the logical node.

[0174] Still as the above example, as shown in FIG. 8 (FIG. 8 is a schematic diagram of the scaling down of the logical node according to an embodiment of the present application, and FIG. 8 is drawn on the basis of FIG. 7), when the tenant needs to delete the virtual NPU of the logical node 2, the tenant can input the following logical node specification scaling down request into the logical node scaling down column in the tenant interface:

[0175] Based on the above logical node scaling down request, the tenant needs to delete the virtual NPU of the logical node 2, so the cloud management platform can make the two core NPUs mapped by the virtual NPU of the logical node 2 exit the virtual bus network inside the logical node 2, and mark the two core NPUs as idle, so the cloud management platform successfully implements the scaling down of the virtual NPU of the logical node 2.

[0176] More specifically, the cloud management platform can further perform the following operations:

[0177] When the tenant needs to query the information of the logical node, the tenant can input the logical node query request for the logical node into the query interface (for example, the logical node query column in the tenant interface) provided by the cloud management platform through the client of the tenant, so the cloud management platform can receive the logical node query request for the logical node sent by the tenant through the client of the tenant through the query interface. Then, based on the logical node query request for the logical node, the cloud management platform can provide the tenant with the information of the logical node, and the information of the logical node can include the specification of the physical devices used to implement the virtual devices of the logical node, for example, the specification of the virtual CPUs used to implement the logical node, and the like.

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

[0179] 404. The cloud management platform notifies the logical node to install the operating system image, wherein the logical node with the installed operating system image allows the tenant to remotely log in.

[0180] After the logical node is created, the cloud management platform can remind the tenant to provide a self-made operating system image or an operating system image selected by the tenant on the cloud management platform. Then, the cloud management platform can install the operating system image specified by the tenant on the logical node, and the logical node installed with the operating system image can be remotely logged in by the tenant to schedule the virtual devices of the logical node to complete the business of the tenant under the instruction of the tenant, thereby meeting the business requirements of the tenant.

[0181] In the embodiments of the present application, when the tenant needs to create a logical node, the tenant can send a logical node creation request for the 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, 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 the logical node, the cloud management platform can select idle physical devices (including CPUs, memories, network cards, and disks, etc.) that meet the logical node specification requirements set by the tenant from a plurality of physical device pools (including CPU device pool, memory device pool, network card device pool, and disk device pool, etc.), and create the logical node on the physical devices. Since the logical node includes virtual devices (including virtual CPUs, virtual memories, virtual network cards, and virtual disks, etc.) realized based on the physical devices, and the 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, and the logical node installed with the operating system image can be remotely logged in by the tenant to schedule the virtual devices of the logical node to complete the business of the tenant under the instruction of the tenant, thereby meeting the business requirements of the tenant. In the foregoing 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, and the cloud management platform only needs to select and provide physical devices matching the specifications to complete the creation of the logical node and provide it to the tenant, which is beneficial to reduce the consumption of the cloud management platform in resource management, and can also meet the customization requirements of the tenant for the specifications of the physical devices used by the logical node.

[0182] Further, in the embodiments of the present application, since the specifications of the physical devices required by the logical node can be freely customized by the tenant, the cloud management platform can determine the requirements of the tenant for the physical devices of the logical node (which can be determined based on the logical node creation request sent by the tenant for the logical node), and then determine the amount of various physical devices that need to be prepared, which can improve the determinacy of resource management and resource utilization, and reduce the cost of resource management.

[0183] Further, in the embodiments of the present application, if the tenant needs to scale the logical node, the cloud management platform can provide additional physical devices or delete the original physical devices to the logical node on the basis of ensuring that the business of the tenant does not interrupt, so as to not only meet the scaling demand of the tenant for the logical node, but also ensure the normal operation of the business, thereby improving the tenant experience.

[0184] The above is a detailed description of the logical node configuration method based on cloud services provided by the embodiments of the present application. The cloud management platform provided by the embodiments of the present application will be introduced below. FIG. 9 is a structural schematic diagram of a cloud management platform provided by an embodiment of the present application. As shown in FIG. 9, the cloud management platform is used to manage infrastructure, and the infrastructure includes a CPU device pool, a memory device pool, a network card device pool, and a disk device pool. The plurality of CPUs in the CPU device pool, the plurality of memories in the memory device pool, the plurality of network cards in the network card device pool, and the plurality of disks in the disk device pool are all connected to a high-speed interconnection network, wherein the high-speed interconnection network is used to realize the interconnection of the devices in each device pool in the infrastructure within the pool and between the pools. The cloud management platform includes:

[0185] The obtaining module 901 is configured to obtain a logical node creation request input by a tenant, wherein the logical node creation request includes a logical node specification requirement, and the logical node specification requirement includes a CPU requirement, a memory requirement, a network card requirement, and a disk requirement. For example, the obtaining module 901 is configured to implement the step 401 in the embodiment shown in FIG. 4.

[0186] [Corrected according to Rule 91 on 20.10.2025] The creating module 902 is configured to create a logical node in response to the logical node creation request, wherein the logical node includes a virtual CPU, a virtual memory, a virtual network card, a virtual disk, and a virtual bus network. The virtual CPU, the virtual memory, the virtual network card, and the 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 requirement and is idle. The virtual memory is implemented by at least one memory in the memory device pool that meets the memory requirement and is idle. The virtual network card is implemented by at least one network card in the network card device pool that meets the network card requirement and is idle. The virtual disk is implemented by at least one disk in the disk device pool that meets the disk requirement and is idle. The virtual bus network is implemented by a subnetwork of the high-speed interconnection network. For example, the creating module 902 is configured to implement the step 402 in the embodiment shown in FIG. 4.

[0187] The determining module 903 is configured to determine an operating system image input or selected by the tenant. For example, the determining module 903 is configured to implement the step 403 in the embodiment shown in FIG. 4.

[0188] The notification module 904 is configured to notify the logical node to install an operating system image, and the logical node with the installed operating system image allows the tenant to remotely log in. For example, the notification module 904 is configured to implement step 404 in the embodiment shown in FIG. 4.

[0189] In a possible implementation, the obtaining module 901 is further configured to obtain a logical node specification expansion request input by the tenant, the logical node specification expansion request being used to request to expand a predetermined specification of one or any combination of a virtual CPU, a virtual memory, a virtual network card, and a virtual disk; and the cloud management platform further includes an expansion module configured to: select a corresponding idle device from one or any combination of a CPU device pool, a memory device pool, a network card device pool, and a 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.

[0190] In a possible implementation, the obtaining module 901 is further configured to obtain a logical node specification expansion request input by the tenant, the logical node specification expansion request being used to request to expand a predetermined specification of one or any combination of a virtual CPU, a virtual memory, a virtual network card, and a virtual disk; and the cloud management platform further includes an expansion module configured to: select a corresponding idle device from one or any combination of a CPU device pool, a memory device pool, a network card device pool, and a 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.

[0191] [According to Rule 91 Correction 20.10.2025] In a possible implementation, the infrastructure further includes an extension processor device pool, the extension processor device pool including a plurality of extension processors, the plurality of extension processors in the extension processor device pool being connected to the high-speed interconnection network, the logical node creation request further including an extension processor requirement, and the logical node further including a virtual extension processor logically connected to the bus network, the virtual extension processor having a mapping relationship with at least one extension processor in the extension processor device pool that meets the extension processor requirement and is idle.

[0192] In a possible implementation, the extension processor of the extension processor device pool is of one or any combination of an NPU, a GPU, a TPU, and a DPU.

[0193] In a possible implementation, the high-speed interconnection network is implemented through a PCIE network, an IB network, or a CXL network.

[0194] It should be noted that the information interaction and implementation process between the modules / units of the above apparatus, since based on the same concept as the method embodiments of the present application, the technical effects brought by it are the same as the method embodiments of the present application, and the specific content can be referred to the description of the method embodiments of the foregoing application embodiments, which will not be repeated here.

[0195] Please refer to FIG. 10, which is a structural schematic diagram of a computing device provided by an embodiment of the present application. As shown in FIG. 10, the computing device 1000 (which can be used to present the cloud management platform described above) includes a processor 1001, a memory 1002, a communication interface 1003 and a bus 1004, and the processor 1001, the memory 1002 and the communication interface 1003 are coupled through the bus (not labeled in the figure). The memory 1002 stores instructions, and when the execution instructions in the memory 1002 are executed, the computing device 1000 performs the method performed by the cloud management platform in the above method embodiments.

[0196] The computing device 1000 can be one or more integrated circuits configured to implement the above method, 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 integrated circuit forms. For another example, when the units in the apparatus can be implemented in the form of a processing element scheduler, the processing element can be a general purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these units can be integrated together in the form of a system-on-a-chip (SOC).

[0197] The processor 1001 can be a central processing unit (CPU), and can also be 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. The general purpose processor can be a microprocessor, or any conventional processor.

[0198] The memory 1002 can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example, and not limitation, many forms of RAM can be used, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0199] The executable program code stored in the memory 1002 is executed by the processor 1001 to realize the functions of the aforementioned acquisition module, creation module, determination module, and notification module, and the like, thereby realizing the aforementioned cloud service-based logical node configuration method. That is, the memory 1002 has instructions for executing the aforementioned cloud service-based logical node configuration method.

[0200] The communication interface 1003 uses a transceiver module such as, but not limited to, a network interface card, a transceiver, and the like, to realize the communication between the computing device 1000 and other devices or communication networks.

[0201] Bus 1004 can include a data bus, a power bus, a control bus, and a state signal bus, among others. The bus can be a peripheral component interconnect express (PCIe) bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like.

[0202] Referring to FIG. 11, FIG. 11 is a structural schematic diagram of a computing device cluster provided by an embodiment of the present application. As shown in FIG. 11, the computing device cluster 1100 includes at least one computing device 1000.

[0203] As shown in FIG. 11, the computing device cluster 1100 includes at least one computing device 1000. The memory 1002 in one or more computing devices 1000 in the computing device cluster 1100 can store the same instructions for performing the cloud service-based logical node configuration method described above.

[0204] In some possible implementation manners, the memory 1002 in one or more computing devices 1000 in the computing device cluster 1100 can also respectively store partial instructions for performing the cloud service-based logical node configuration method described above. In other words, the combination of one or more computing devices 1000 can collectively perform the cloud service-based logical node configuration method described above.

[0205] It should be noted that the memory 1002 in different computing devices 1000 in the computing device cluster 1100 can store different instructions, respectively, for performing part of the functions of the cloud management platform described above. That is, the instructions stored in the memory 1002 in different computing devices 1000 can implement the functions of one or more of the obtaining module, the creating module, the determining module, and the notifying module, and the like.

[0206] In some possible implementation manners, one or more computing devices 1000 in the computing device cluster 1100 can be connected through a network. The network can be a wide area network or a local area network, and the like.

[0207] Referring to FIG. 12, FIG. 12 is a schematic diagram of the connection of the computer devices in the computer cluster provided in the embodiments of the present application through a network. As shown in FIG. 12, the two computer devices 1000A and 1000B are connected through a network. Specifically, the communication interface in each computer device is connected to the network.

[0208] In a possible implementation, the memory in the computer device 1000A stores instructions for performing the functions of the obtaining module and the like. Meanwhile, the memory in the computer device 1000B stores instructions for performing the functions of the creating module, the determining module, the notifying module and the like.

[0209] It should be understood that the functions of the computer device 1000A shown in FIG. 12 can also be completed by multiple computer devices. Similarly, the functions of the computer device 1000B can also be completed by multiple computer devices.

[0210] The embodiments of the present application also relate to a computer storage medium, which stores a program for performing signal processing, and when the program is run on a computer, the computer executes the steps performed by the cloud management platform in the embodiment shown in FIG. 4.

[0211] The embodiments of the present application also relate to a computer program product, which stores instructions, and when the instructions are executed by a computer, the computer executes the steps performed by the cloud management platform in the embodiment shown in FIG. 4.

[0212] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described herein.

[0213] In the several embodiments of the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. The division of the units is only a logical function division. There can be another division manner for actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or in other forms.

[0214] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0215] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0216] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical scheme of the present application essentially or the part that contributes to the prior art or the whole or part of the technical scheme can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile disk, a read-only memory (ROM, read-only memory), a random access memory (RAM, random access memory), a magnetic disk or an optical disk, and various program code storage media.

Claims

1. [Corrected according to Rule 91, October 20, 2025] 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 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. [Corrected according to Rule 91, 20.10.2025] 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 creation request also includes an extended processor requirement. The logical node also includes a virtual extended processor logically connected to the bus network. The virtual extended processor has a mapping relationship with at least one idle extended processor in the extended processor device pool that meets the extended processor requirement.

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

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. [Corrected according to Rule 91, October 20, 2025] 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 creation request. 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 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. [Correction 20.10.2025 according to Rule 91] The cloud management platform according to any one of claims 7 to 9 is 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 creation request also includes an extended processor requirement. The logical node also includes a virtual extended processor logically connected to the bus network. The virtual extended processor has a mapping relationship with at least one idle extended processor in the extended processor device pool that meets the extended processor requirement.

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

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