Method for providing cloud service, cloud platform and related device
Through the elastic memory acceleration service management node, tenants allow custom cloud services according to their needs, solving the problems of insufficient memory capacity and low resource utilization in the existing technology, and improving the performance and resource utilization of cloud services.
Patent Information
- Application Number
- CN202311054802.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-02
- Filing Date
- 2023-08-21
- Publication Date
- 2024-12-03
AI Technical Summary
In existing cloud computing technology, the memory capacity requirements of tenants are difficult to meet, and the preset specification limitations lead to low resource utilization and high operation and maintenance costs, and the inability to effectively utilize idle resources in the data center.
Provide a cloud service method to manage nodes through Elastic Memory Acceleration Service (EMAS), allowing tenants to input attribute information of target cloud service according to business needs, create Elastic Memory Acceleration Super Instance (EMA Super Instance), and use configuration interfaces and management interfaces. Provides customized computing and memory resources for tenants, and supports dynamic resource scheduling and utilization.
It realizes cloud services customized according to business needs, improves resource utilization and performance, reduces resource waste and operation and maintenance costs, and effectively utilizes idle resources in the data center.
Smart Images

Figure CN119071291A_ABST
Abstract
Description
[0001] This application claims priority to Chinese patent application No. 202310655416.6, filed on June 2, 2023, with invention name “Method, cloud platform and related devices for providing cloud services”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of cloud computing technology, and in particular to a method for providing cloud services, a cloud platform, and related devices. Background Art
[0003] With the continuous development of information technology, especially the advancement of Internet technology, large government enterprises and financial institutions have begun to gradually build their own data centers to meet their business needs for resources. Simply relying on adding physical equipment is very expensive. Against this background, cloud computing came into being. Relying on virtualization technology, cloud service providers integrate resources and provide unified services to the outside world, greatly improving the efficiency of resource use.
[0004] In the related art, cloud service providers provide basic resource services to tenants through virtual machines, containers, etc. Taking virtual machines as an example, the specifications of virtual machines are predefined modes, that is, tenants need to specify the number of central processing units (CPUs) and memory size of the virtual machine from the preset specifications. If the specification of the virtual machine specified by the tenant from the preset specifications is 4U8G, this specification means that the virtual machine has 4 CPU cores and 8 gigabytes (GB) of memory, and the resources of the tenant cannot exceed the specified specifications when using the virtual machine.
[0005] However, in cloud computing scenarios, with the development of business and the evolution of applications, tenants have an increasing demand for memory capacity, and the current preset specifications often cannot meet the needs of some tenants. Summary of the invention
[0006] The present application provides a method, apparatus, device, storage medium and computer program for providing cloud services, which can solve the problem that related technologies cannot meet user needs. The technical solution is as follows:
[0007] In a first aspect, a method for providing cloud services is provided, which is applied to an elastic memory acceleration service EMAS management node included in a cloud platform, wherein the cloud platform also includes multiple resource nodes, and the resource nodes are used to provide at least one of computing resources and memory resources. The method includes: providing a configuration interface, wherein the configuration interface is used to prompt a tenant to input attribute information of a target cloud service to be provided according to business requirements, wherein the attribute information includes a provision method of the target cloud service and performance configuration information of the target cloud service; obtaining the attribute information of the target cloud service from the configuration interface; based on the attribute information, creating a target elastic memory acceleration EMA super instance in a target resource node included in the multiple resource nodes, wherein the target EMA super instance is used to provide the target cloud service to the tenant, wherein the target resource node includes at least one resource node, and the available resources of the target resource node meet the business requirements; based on the provision method of the target cloud service, setting a management interface of the target EMA super instance, and providing the management interface to the tenant.
[0008] Since the attribute information of the target cloud service is input by the tenant according to business needs, that is, the tenant does not need to be restricted by the preset specifications, and can directly customize the computing resources and memory resources of the target cloud service according to its own business needs, thereby meeting the needs of the tenant and improving the performance of the cloud service. In addition, since the target resource node includes at least one resource node, that is, the present application can integrate the resources of the at least one resource node to provide services for the tenant, so that while meeting the needs of users, it can also effectively improve the utilization rate of idle resources in the data center, reduce resource waste and the operation and maintenance costs of the cloud service provider.
[0009] In the case where the target cloud service selected by the tenant is provided in a different manner, the performance configuration information of the target cloud service includes different contents, which will be introduced below respectively.
[0010] In the first case, the target cloud service is provided in a super instance provision mode. In this case, the performance configuration information of the target cloud service includes usage type, memory capacity, capacity guarantee mode, capacity step, computing resources and bandwidth. Among them, the usage type indicates whether the target EMA super instance provides services in the form of mounting, the memory capacity indicates the memory capacity of the target EMA super instance, the capacity guarantee mode indicates whether the resource nodes to which the memory resources of the target EMA super instance are distributed are variable, the capacity step indicates the memory size of each EMAI included in the target EMA super instance, the computing resources indicate the computing performance of the target EMA super instance, and the bandwidth indicates the data transmission volume of the target EMA super instance per unit time.
[0011] Optionally, the usage type includes single instance usage and mounted usage. Single instance usage means that the target EMA super instance does not provide services in a mounted form. Mounted usage means that the target EMA super instance provides services in a mounted form.
[0012] Optionally, the memory capacity is divided into a guaranteed capacity and a burst capacity, wherein the guaranteed capacity refers to the minimum memory capacity required to be guaranteed by the target EMA super instance, and the burst capacity indicates the maximum capacity of the target EMA super instance, which is greater than or equal to the guaranteed capacity.
[0013] Optionally, the capacity guarantee mode includes a dynamic mode and a static mode. The dynamic mode is a rotatable mode, which means that the EMAS management node can split and relocate the EMAI included in the target EMA super instance according to the resource usage of the underlying physical server. The static mode is a non-rotatable mode, which means that after the EMASI is created, it is not allowed to be split or relocated.
[0014] Splitting means providing resources originally provided by one EMAI through at least two EMAIs. Relocation means providing resources originally provided by a first resource node through other resource nodes except the first resource node.
[0015] Optionally, the default capacity guarantee mode of the EMAS management node is the dynamic mode, that is, when the tenant does not select the capacity guarantee mode, the default capacity guarantee mode is the dynamic mode, so that resources can be scheduled according to the resource usage of the underlying physical server, thereby achieving full utilization of resources.
[0016] Optionally, the capacity step indicates the minimum value of the memory capacity of each EMASI included in the target EMA superinstance, that is, the memory capacity of each EMAI is not less than the capacity step, and the capacity step limits the lower limit of the memory capacity specification of all EMAIs constituting the EMA superinstance. In this case, the number of EMAIs constituting the EMA superinstance is not greater than the value after the actual memory capacity of the EMA superinstance is divided by the capacity step.
[0017] Optionally, if the tenant sets the capacity step to 0, in this case, it does not mean that the memory resources corresponding to each EMASI are 0, but that the EMAS management node can create EMASI for the tenant based on the resource usage of the underlying physical server without being constrained by the capacity step. The size of the EMASI memory resources is related to the size of the resources actually allocated by the EMAS management node.
[0018] Bandwidth may refer to the amount of data transmitted per second by the target EMA superinstance, in GB per second. Of course, in practical applications, bandwidth may also be represented in other forms.
[0019] Optionally, the unit of computing resources is a virtual CPU unit (VCU), and one VCU can be a core in a physical CPU or a data processing unit (DPU), or a hyperthread of a core in a physical CPU or a DPU. It should be noted that the one VCU can be a computing resource used solely by the target EMA super instance, or a computing resource shared with other EMA super instances.
[0020] Since the usage types include single instance usage and mounted usage, the performance configuration information of the target cloud service may include some different information in different usage types, which will be introduced below.
[0021] In case 1, the usage type is single instance usage, that is, the usage type indicates that the target EMA super instance does not provide services in the form of mounting. At this time, the performance configuration information of the target cloud service also includes a latency specification and a placement strategy. The latency specification indicates the access latency of the memory resources of the target EMA super instance, and the placement strategy indicates whether the memory resources and computing resources of the target EMA super instance are located in the same resource node.
[0022] Optionally, the latency specification includes performance priority or cost priority. Performance priority means that the EMAS management node selects a resource node with the shortest latency from multiple resource nodes as the target resource node. Cost priority means that the EMAS management node selects a resource node with a lower price from multiple resource nodes as the target resource node.
[0023] In actual applications, in addition to directly selecting performance priority or cost priority, tenants can also enter a specific latency threshold to determine the latency specification. In this case, the EMAS management node determines the target resource node based on the latency threshold, and the access latency of the memory resource of the target EMA super instance is not greater than the latency threshold.
[0024] Optionally, the default latency specification of the EMAS management node is cost priority, that is, when the tenant does not select a latency specification, the default latency specification is cost priority. Since resources with low utilization rates are usually lower in price, the EMAS management node can schedule lower-priced resources for tenants based on the resource usage of the underlying physical servers, thereby making full use of the idle resources of the data center.
[0025] Optionally, the placement strategy includes affinity and anti-affinity, wherein affinity means that the memory resources and computing resources of the target EMA superinstance are located in the same resource node, and anti-affinity means that the memory resources and computing resources of the target EMA superinstance are not located in the same resource node.
[0026] It should be noted that if the tenant does not fill in the placement strategy, the EMAS management node can determine the resource node where the computing resources and memory resources of the target EMA super instance are located based on the resource usage of the underlying physical server.
[0027] Case 2: The usage type is mount usage, that is, the usage type indicates that the target EMA super instance provides services in the form of mounting. At this time, the performance configuration information of the target cloud service also includes the identification, latency specification, placement strategy, access strategy and usage mode of at least one target instance, the target instance refers to the instance used to mount the target EMA super instance, the latency specification indicates the access latency of the target instance to the target EMA super instance, the placement strategy indicates whether the target EMA super instance and the first instance are located in the same resource node, the first instance is one of the at least one target instance, the access strategy indicates the read and write permissions of the at least one target instance to the target EMA super instance, and the usage mode indicates the memory addressing method of the target EMA super instance and the second instance, the second instance is one of the at least one target instance.
[0028] It should be noted that the target instance can be a virtual machine instance, a bare metal server instance, or a container instance. The target instance needs to be created using an image that supports EMA capabilities.
[0029] Optionally, the latency specification includes performance priority or cost priority. Performance priority means that the EMAS management node selects a resource node with the shortest access latency to the target instance from multiple resource nodes as the target resource node. Cost priority means that the EMAS management node selects a resource node with a lower price from multiple resource nodes as the target resource node.
[0030] In actual applications, in addition to directly selecting performance priority or cost priority, tenants can also enter a specific latency threshold to determine the latency specification. In this case, the EMAS management node determines the target resource node based on the latency threshold so that the access latency of the target instance to the target EMA super instance is no greater than the latency threshold.
[0031] Optionally, the default latency specification of the EMAS management node is cost priority, that is, when the tenant does not select a latency specification, the default latency specification is cost priority. Since resources with low utilization rates are usually lower in price, the EMAS management node can schedule lower-priced resources for tenants based on the resource usage of the underlying physical servers, thereby making full use of the idle resources of the data center.
[0032] Optionally, the placement strategy includes affinity and anti-affinity, wherein affinity means that the target EMA super instance and the first instance are located in the same resource node, and anti-affinity means that the target EMA super instance and the first instance are not located in the same resource node.
[0033] It should be noted that if the tenant selects a placement strategy, the tenant also needs to enter the identifier of the first instance so that the EMAS management node can determine the location where the first instance is deployed. If the tenant does not fill in the placement strategy, the EMAS management node can determine the resource node where the computing resources and memory resources of the target EMA super instance are located based on the resource usage of the underlying physical server.
[0034] Optionally, the access policy includes private, shared read-only, and shared read-write. Among them, private means that when the number of target instances is 1, the target instance has read and write permissions to the target EMA super instance. Shared read-only means that when the number of target instances mounted on the target EMA super instance is greater than or equal to 2, the primary mounted instance among the at least two target instances has read and write permissions, and other target instances have only read-only permissions. Shared read-write means that when the number of target instances mounted on the target EMA super instance is greater than or equal to 2, the at least two target instances have read and write permissions.
[0035] It should be noted that if the tenant only enters the ID of one target instance, the access policy is set to private by default. In addition, if the access policy is set to shared read-only, the tenant also needs to enter the ID of the primary mounting instance.
[0036] Optionally, usage modes include full peer mode, semi-peer mode and heterogeneous mode. Among them, full peer mode means that GuestOS is fully managed, that is, the total memory of the second instance is composed of the local memory of the second instance and the memory of the target EMA super instance, and the local memory of the second instance and the memory of the target EMA super instance are uniformly addressed. Semi-peer mode means that GuestOS is partially managed, that is, the total memory of the second instance is composed of the local memory of the second instance and the memory of the target EMA super instance, and the local memory of the second instance and the memory of the target EMA super instance are uniformly addressed, but the user can know the address segment corresponding to the local memory of the second instance and the address segment corresponding to the memory of the target EMA super instance. In heterogeneous mode, GuestOS does not manage the EMA super instance memory pool and does not uniformly address it.
[0037] In the second case, the target cloud service is provided in a non-instance-free manner. At this time, the performance configuration information of the target cloud service includes service type, performance specifications, maximum number of simultaneous connections and rate cap. The service type indicates the tenant's business demand for memory resources and computing resources, the performance specifications indicate the number of target EMA super instances, the maximum number of simultaneous connections indicates the number of instances that the target EMA super instance can connect to at the same time, and the rate cap indicates the upper limit of resources provided by the cloud platform to tenants.
[0038] Optionally, the service types include memory expansion, computing power offloading, and cache. Different service types have different performance requirements for the target EMA super instance. Among them, cache requires high bandwidth, but not high requirements for computing resources and latency specifications. Memory expansion has requirements for computing resources and memory capacity, and computing power offloading does not require high computing resources. Of course, in actual applications, there may be other service types that can reflect business scenarios.
[0039] Optionally, the performance specifications include standard, high performance, and best effort. Under the standard specification, the number of target EMA superinstances is related to the number of instances connected to the target EMA superinstance, and the number of instances connected to the target EMA superinstance is greater than the number of target EMA superinstances. Under the high performance specification, the number of instances connected to the target EMA superinstance is equal to the number of EMA superinstances, that is, each instance connected to the target EMA superinstance corresponds to one target EMA superinstance. Under the best effort specification, there is only one target EMA superinstance, that is, all the instances connected to the target EMA superinstances share one target EMA superinstance.
[0040] It should be noted that if the tenant does not fill in the above performance specifications and the maximum number of simultaneous connections, the EMAS management node can dynamically adjust the number of target EMA super instances and the maximum number of simultaneous connections based on the resource usage of the underlying physical server.
[0041] Optionally, the unit of the rate cap may be RMB per hour, RMB per month, or RMB per year.
[0042] Optionally, after the tenant determines the above service type, performance specifications, and maximum number of simultaneous connections, the EMAS management node can determine the basic price corresponding to the service type, performance specifications, and maximum number of simultaneous connections configured by the tenant according to relevant algorithms, and the upper limit of the rate filled in by the tenant is greater than or equal to the basic price.
[0043] Optionally, the EMAS management node can obtain the attribute information of the available resources of each resource node in each resource pool, determine the target resource node from the multiple resource nodes based on the attribute information of the available resources of each resource node in each resource pool and the attribute information of the target cloud service, each resource node in the target resource node is located in the same resource pool, and create an elastic memory acceleration instance EMAI in each resource node included in the target resource node to obtain one or more EMAIs, and generate a target EMA super instance based on the one or more EMAIs.
[0044] Optionally, configuration parameters of the target cloud service may be determined based on the attribute information of the target cloud service, and the target resource node may be determined from multiple resource nodes based on the configuration parameters of the target cloud service and attribute information of available resources of each resource node in each resource pool.
[0045] In the case where the target cloud service is provided in different ways, the methods for determining the configuration parameters of the target cloud service are different, which will be introduced below respectively.
[0046] In the first case, the target cloud service is provided in a super instance provision mode. In this case, the performance configuration information of the target cloud service can be directly used as the configuration parameters of the target cloud service.
[0047] In the second case, the target cloud service is provided in a non-instance provision mode. In this case, the EMAS management node stores the correspondence between the service type and the configuration parameters of the target cloud service. The configuration parameters of the target cloud service include guaranteed capacity, burst capacity, computing resources, capacity step, bandwidth, latency specification, guarantee mode, and placement strategy. The EMAS management node can determine the configuration parameters of the target cloud service from the correspondence between the service type and the configuration parameters of the target cloud service according to the service type configured by the tenant.
[0048] It should be noted that, in addition to obtaining the attribute information of the target cloud service from the configuration interface, the attribute information of the target cloud service can also be obtained through API calls, email interactions, work order interactions, and the like.
[0049] In actual applications, after providing the management interface to tenants, the EMAS management node can also determine whether the resources of the target EMA super-instance are overloaded based on the tenants' resource usage of the target EMA super-instance. When it is determined that the resources of the target EMA super-instance are overloaded, it determines whether the resources provided by the cloud platform for the target EMA super-instance have reached the upper limit of configured resources based on the attribute information of the target cloud service. When the resources provided by the cloud platform for the target EMA super-instance do not reach the upper limit of configured resources, the target resource node is adjusted.
[0050] Optionally, the resources of the target EMA superinstance include memory resources and computing resources. Based on the tenant's usage of the target EMA superinstance's memory resources, it is determined whether the target EMA superinstance's memory resources are overloaded. Based on the usage of the computing resources of the target EMA superinstance, it is determined whether the computing resources of the target EMA superinstance are overloaded. When it is determined that the memory resources and / or computing resources of the target EMA superinstance are overloaded, it is determined that the resources of the target EMA superinstance are overloaded.
[0051] Optionally, the memory resource usage includes a memory occupancy ratio. If the memory occupancy ratio is greater than a memory ratio threshold, it is determined that the memory resource of the target EMA superinstance is overloaded; otherwise, it is determined that the memory resource of the target EMA superinstance is not overloaded.
[0052] Optionally, the computing resource usage includes a computing resource occupancy ratio, a request queue number, and a response time. If the computing resource occupancy ratio is less than a computing resource ratio threshold, the request queue number is less than a queue number threshold, and the response time is less than a response time threshold, it is determined that the computing resource of the target EMA superinstance is not overloaded, otherwise, it is determined that the computing resource of the target EMA superinstance is overloaded.
[0053] Of course, in actual applications, the computing resource usage may also include at least one of the computing resource occupancy ratio, the number of request queues, and the response time.
[0054] Optionally, when the resources provided by the cloud platform for the target EMA super instance reach the upper limit of configured resources, a prompt message is sent to the tenant, where the prompt message is used to indicate that the resources provided by the cloud platform for the target EMA super instance have reached the upper limit of configured resources.
[0055] In a second aspect, a cloud platform is provided, wherein the cloud platform has the function of implementing the method of providing cloud services in the first aspect. The cloud platform includes at least one module, and the at least one module is used to implement the method of providing cloud services provided in the first aspect.
[0056] In a third aspect, a computing device cluster is provided, the computing device cluster comprising at least one computing device, each computing device comprising a processor and a memory, the processor of the at least one computing device being used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method for providing cloud services described in the first aspect.
[0057] Optionally, each computing device may further include a communication bus, which is used to establish a connection between the processor and the memory of each computing device.
[0058] In a fourth aspect, a computer-readable storage medium is provided, wherein the storage medium includes computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the steps of the method for providing cloud services described in the first aspect.
[0059] In a fifth aspect, a computer program product comprising instructions is provided. When the instructions are executed by a computing device cluster, the computing device cluster executes the steps of the method for providing cloud services described in the first aspect.
[0060] The technical effects obtained by the above-mentioned second, third, fourth and fifth aspects are similar to the technical effects obtained by the corresponding technical means in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0061] Figure 1 is a schematic diagram of an EMA superinstance provided in an embodiment of the present application;
[0062] Figure 2 It is a schematic diagram of an implementation environment provided by an embodiment of the present application;
[0063] Figure 3 is a schematic diagram of another implementation environment provided by an embodiment of the present application;
[0064] Figure 4 It is a structural diagram of a POD resource management node provided in an embodiment of the present application;
[0065] Figure 5 is a flow chart of a method for providing cloud services provided by an embodiment of the present application;
[0066] Figure 6 It is a schematic diagram of resource distribution of an EMA super instance provided in an embodiment of the present application;
[0067] Figure 7 This is a schematic diagram of an EMA super instance mounting provided in an embodiment of the present application;
[0068] Figure 8 This is a schematic diagram of another EMA super instance mounting method provided in an embodiment of the present application;
[0069] Fig. 9 It is a schematic diagram of a non-example providing method provided in an embodiment of the present application;
[0070] Fig.10 It is a schematic diagram of another non-example providing method provided in the embodiment of the present application;
[0071] Fig.11 is a flow chart of using a target cloud service provided by an embodiment of the present application;
[0072] Fig.12 It is a schematic diagram of a non-example providing method provided in an embodiment of the present application;
[0073] Fig.13 This is a flow chart of a Java application performance optimization service provided by an embodiment of the present application;
[0074] Fig.14 is a schematic diagram of a Java application performance optimization service provided by an embodiment of the present application;
[0075] Fig.15 is a schematic diagram of a data caching service provided by an embodiment of the present application;
[0076] Fig.16 It is a structural diagram of an EMAS management node provided in an embodiment of the present application;
[0077] Fig.17 This is an architecture diagram of a cloud platform provided in an embodiment of the present application;
[0078] Fig.18 is a structural schematic diagram of a computer device provided in an embodiment of the present application;
[0079] Fig.19 It is an architecture diagram of a computing device cluster provided in an embodiment of the present application;
[0080] Fig. 20 It is a schematic diagram of the connection between computing devices provided in an embodiment of the present application. DETAILED DESCRIPTION
[0081] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.
[0082] For ease of understanding, before explaining in detail the method for providing cloud services provided in the embodiment of the present application, the nouns, application scenarios and implementation environments involved in the embodiment of the present application are first introduced.
[0083] Virtual machine / virtual server (virtual machine): also known as cloud server in cloud scenarios, is a complete computer system with complete hardware system functions running in a completely isolated environment based on virtualization technology on the same physical server / host, simulated by software.
[0084] Elastic cloud server: A virtual machine or cloud server managed by the elastic computing service in cloud computing. It has the characteristics of instant expansion and instant release. It can adjust computing resources at any time according to business needs and can achieve horizontal expansion and contraction. It can also be called an ECS instance.
[0085] Super instance: refers to a type of virtualized logical instance. A super instance is exposed as a logical instance, but its underlying layer may be composed of one or more homogeneous or heterogeneous instances. These underlying topologies are transparent to users. Users can only directly operate the super instance itself, and the experience is similar to operating an instance.
[0086] It should be noted that when a superinstance consists of only one instance, the superinstance is equivalent to the instance, that is, when there is only one instance at the bottom of the superinstance, the user can operate the instance.
[0087] Instanceless: refers to a type of virtual resource provisioning method. When virtual resources are provided through instanceless, the underlying implementation relies on a superinstance. That is, the virtual resource is composed of one or more homogeneous or heterogeneous instances. These underlying topologies are transparent to users, and the superinstance is also transparent to users. Users cannot directly operate the underlying instance or superinstance.
[0088] Elastic memory accelerator super instance (EMASI): A super instance managed by the elastic memory accelerator service (EMAS) management node. An EMASI is a logical instance with memory resources. Its memory capacity is composed of the memory resources of at least one elastic memory accelerator instance (EMAI). For ease of description, EMASI is uniformly referred to as an EMA super instance in the following text.
[0089] For example, see Figure 1 , the memory resource of the EMA super instance is 128 GB, and the memory resource of the EMA super instance is provided by EMAI1_1 on host01, EMAI1_2 on host02, EMAI1_3 and EMAI1_4 on host03. Among them, EMAI1_1 provides 16 GB of memory resources, EMAI1_2 provides 16 GB of memory resources, EMAI1_3 provides 32 GB of memory resources, and EMAI1_4 provides 16 GB of memory resources.
[0090] EMAI: An instance that makes up the EMA superinstance. EMAI is a physical instance and cannot be deployed across physical servers.
[0091] Guest operating system (Guest OS): refers to the operating system running in the virtual cloud server.
[0092] Node operating system (Node OS): The operating system of the host node where the virtual machine or container is located.
[0093] Software Development Kit (SDK): A software package that integrates a set of development tools to help developers develop applications on a specific platform. SDKs usually include development tools such as compilers, debuggers, library files, API documentation, and sample code, which can help developers develop applications more efficiently and ensure that applications can interact well with the platform when running. For example, for a specific operating system or development language, there may be a corresponding SDK to help developers develop applications on that platform.
[0094] With the continuous development of information technology, especially the advancement of Internet technology, large government enterprises and financial institutions have begun to gradually build their own data centers to meet their business needs for resources. As the scale of data centers expands rapidly, their complexity is also increasing, and energy consumption is also increasing year by year. Simply relying on adding physical equipment is very expensive. Against this background, cloud computing came into being. Relying on virtualization technology, cloud service providers integrate resources and provide unified services to the outside world, greatly improving the efficiency of resource use.
[0095] In the related art, cloud service providers provide basic resource services of the infrastructure as a service (Iaas) layer to tenants through virtual machines, containers, etc. Taking virtual machines as an example, the specifications of virtual machines are predefined modes, and tenants need to specify the size of the computing resources and memory resources of the virtual machine from the preset specifications, that is, the number of central processing units (CPUs) and the size of the memory. If the specification of the virtual machine specified by the tenant from the preset specifications is 4U8G, this specification means that the virtual machine has 4 CPU cores and 8 gigabytes of memory, and the resources of the tenant cannot exceed the specified specifications when using the virtual machine. Compared with virtual machines, containers are more flexible. After selecting the number of CPUs for the container, the tenant can configure the memory capacity according to a certain step size, but the step size is fixed, and the ratio of the number of CPUs to the memory capacity also needs to be within the preset ratio range. For example, the preset ratio range is between 1:4 and 1:8. In this case, if the tenant selects 4 CPU cores as computing resources, the memory capacity selection range can only be 4GB-32GB, and the step size is 1GB. In other words, the user can only select an integer memory capacity and cannot select a memory capacity of 4.5GB.
[0096] However, in cloud computing scenarios, with the development of business and the evolution of applications, tenants have an increasing demand for memory capacity. The current preset specifications often cannot meet the needs of some tenants. If memory resources are insufficient, the computing performance of cloud services will be seriously affected.
[0097] In addition, the memory resources provided by the current Iaas layer are basically homogeneous, that is, the memory performance specifications are the same and the address space performance specifications are the same. Among them, the same memory performance specifications mean that the memory performance of virtual machines with different memory specifications is the same when the computing resources are the same. The same address space performance specifications mean that for virtual machines with the same specifications, the speed of reading and writing each memory address in the virtual machine is also the same. Therefore, when the computing resources remain unchanged, the performance of memory resources with different memory capacities remains unchanged, and the larger the memory capacity, the higher the corresponding selling price of the memory resource. If the tenant purchases a larger memory capacity when the memory capacity demand increases, the tenant's cost will be greatly increased. In addition, if the business itself does not require high memory performance, the tenant only needs to expand the memory capacity. In this case, the tenant may not be willing to pay more to purchase high-performance memory capacity. Moreover, in real life, some businesses do not require high performance of computing resources, but have high requirements for memory capacity and memory performance. In this case, if the tenant purchases computing resources and memory resources at the same time, the utilization rate of the computing resources purchased by the tenant will be very low, and the memory capacity will also be very limited, so that the tenant has to pay for unused computing resources and the tenant's demand for memory capacity is not met.
[0098] If a cloud service provider provides tenants with a preset specification with a larger memory ratio, it will seriously affect the efficiency of computing resources in the physical server. For example, if a 1:6 specification virtual machine is provided to a tenant in a 1:4 specification physical server (the ratio of computing resources to memory resources is 1:4), the utilization rate of computing resources in the physical server will be reduced, resulting in a waste of physical server resources and an increase in the operation and maintenance costs of the cloud service provider. For example, physical server A has 100 CPU cores and 400GB of memory, that is, the specification of the physical server is 1:4. If a 1:6 specification virtual machine is issued in the physical server A, then the physical server A has 66 CPU cores and 396GB of memory that can provide services to tenants. Since computing resources cannot usually be sold separately, in this case, the 34 CPU cores and 4GB of memory in the physical server A will not be able to provide services to tenants, resulting in a waste of resources and an increase in the operation and maintenance costs of the cloud service provider. At the same time, there are still some idle memory resources in the data centers of cloud service providers that have not been sold yet. The overall sales rate of memory resources is not high, but most of these unsold memory resources are scattered, that is, distributed on different physical servers, and cannot form a complete memory block to be sold together with the virtual machine or container, resulting in insufficient resource utilization and waste of resources.
[0099] Based on this, the embodiment of the present application provides a method for providing cloud services, the EMAS management node can provide a configuration interface, and obtain the attribute information of the target cloud service from the configuration interface, the attribute information includes the provision method of the target cloud service and the performance configuration information of the target cloud service, based on the performance configuration information, the EMAS management node can create a target EMA super instance in the target resource node, and then set the management interface of the target EMA super instance based on the provision method of the target cloud service, and provide the management interface to the tenant, so as to provide the target cloud service to the tenant through the target EMA super instance. Since the attribute information is input by the tenant according to the business needs, that is, the tenant does not need to be restricted by the preset specifications, and can directly customize the computing resources and memory resources of the target cloud service according to its own business needs, thereby meeting the needs of the tenant and improving the performance of the cloud service. In addition, since the target resource node includes at least one resource node, that is, the embodiment of the present application can integrate the resources of at least one resource node to provide services for the tenant, so that while meeting the needs of users, it can also effectively improve the utilization rate of idle resources in the data center, reduce resource waste and the operation and maintenance costs of the cloud service provider.
[0100] Please refer to Figure 2 , Figure 2 Schematic diagram of an implementation environment provided by an embodiment of the present application, the implementation environment includes a tenant side 10 and a service side (cloud platform) 20, the service side 20 includes an EMAS management node 21 ( Figure 2 ) and a plurality of resource nodes 22 ( Figure 2 Optionally, the EMAS management node 21 includes a first management and control node 211 , a data persistence layer 212 , a billing system 213 , and an application deployment channel 214 .
[0101] Among them, the first control node 211 provides a configuration interface 2111 and displays it to the tenant side. The configuration interface 2111 is used to prompt the tenant to input the attribute information of the target cloud service to be provided according to the business requirements, and then the first control node 211 can obtain the attribute information of the target cloud service, and based on the attribute information of the target cloud service, create a target EMA super instance in the target resource node included in the multiple resource nodes 22 and set the management interface of the target EMA super instance, and provide the management interface to the tenant. The first control node 211 can also store the relevant data of the target cloud service, that is, convert the relevant data of the target cloud service into a data model that can be stored in the data persistence layer 212, and store it in the data persistence layer 212, so as to realize the long-term preservation and access of the data, thereby completing the storage of the data. The data persistence layer 212 can be a disk or a database, which is not limited in the embodiment of the present application. After the target EMA super instance is created, the first control node 211 can connect the target EMA super instance to the billing system 213 to realize the billing of the target EMA super instance. After acquiring the management interface of the target EMA super instance, the tenant can deploy the required application through the management interface of the target EMA super instance and the application deployment channel 214 .
[0102] Please refer to Figure 3 , Figure 3 is a schematic diagram of another implementation environment provided by an embodiment of the present application, the implementation environment includes an EMAS management node 21 ( Figure 3 ) and a plurality of resource nodes 22 ( Figure 3 In the figure, resource node 1 and resource node 2 are used to schematically represent the multiple resource nodes 22). In addition to the first control node 211, the data persistence layer 212, the billing system 213, and the application deployment channel 214, the EMAS management node 21 also includes at least one POD resource management node 215 ( Figure 3 ), a cluster resource management node 216, a thermal demounting management node 217, and a DC (Data Center) topology management node 218.
[0103] The multiple resource nodes 22 are located in at least one resource pool, a resource pool can be called a POD, each POD corresponds to a POD resource management node 215, each POD includes at least one resource node, the resource nodes in the same POD are located in the same ultra-high-speed network plane, each resource node can be a physical server, or it can be a combination of part of the resources (computing and memory) in the physical server.
[0104] For any resource node in any POD, the resource node includes Node OS, EMAS virtualization layer, and EMAS agent. The EMAS virtualization layer is used to provide the virtualization interface (also known as the application programming interface (API)) of the resource node and manage the resources in the resource node. The EMAS Agent is usually deployed on the physical server where the resource node is located, and is used to report the resource status of the resource node to the POD resource management node 214 to which the resource node belongs. The EMAS Agent is also used to create an EMA super instance by calling the API provided by the EMAS virtualization layer when the resource node is determined to be the target resource node.
[0105] The POD resource management node 215 is used to manage the resources in the POD, maintain the topological information of the resources in the POD, receive the resource status of the resource nodes reported by the EMAS Agent, and integrate the resources of the resource nodes in the POD resource management node 215 into a resource pool. The POD resource management node 215 can also report the resource status of the resource pool in the POD to the cluster resource management node, and instruct the target resource node to create an EMAI.
[0106] In some embodiments, the resource pool may include a computing resource pool and a memory resource pool, each resource node may provide memory resources and / or computing resources, and a resource node that can provide memory resources is referred to as a memory resource node, and a resource node that can provide computing resources is referred to as a computing resource node. The memory resources of each memory resource node may be accumulated into a memory resource pool. Computing resources may be isolated according to computing resource nodes, and computing resources of different computing resource nodes may not be accumulated and pooled to obtain computing resource pools corresponding to multiple computing resource nodes. Of course, in practical applications, the computing resources of the computing resource nodes may also be accumulated into a computing resource pool, and the embodiments of the present application do not limit this. It should be noted that the above-mentioned ultra-high-speed network plane may be built by computing high-speed connection (Compute ExpressLink, CXL), remote direct memory access (Remote Direct Memory Access, RDMA) and other technologies, and the embodiments of the present application do not limit this.
[0107] In some embodiments, the first control node 211 can receive CRUD (Create, Retrieve, Update, and Delete), mount, and detach requests of the EMA super instance, and manage the life cycle of the EMA super instance based on the request, that is, perform operations such as creation, retrieval, update, deletion, mount, and detach on the EMA super instance. The first control node 211 can also set a management interface for the EMA super instance and provide the management interface to the tenant. In some embodiments, the first resource node 211 can send a resource application or a resource release request to the cluster resource management node 216, and the resource application request includes the performance configuration information of the target cloud service, and the resource release request includes the identifier of the EMA super instance to be released. The cluster resource management node 216 can determine the target resource node based on the performance configuration information of the target cloud service and the resource status of the resource pool in each POD, and send the scheduling result (identifier of the target resource node) to the first control node 211. The cluster resource management node 216 can also determine the resource node that needs to release resources based on the identifier of the EMA super instance, and send the scheduling result (the identifier of the resource node that needs to release resources) to the first control node 211. The first control node 211 receives the scheduling result sent by the cluster resource management node 216 and sends instance creation, update, deletion and other requests to the POD resource management node 215 based on the scheduling result. Taking the first control node 211 sending a super instance creation request to the POD resource management node 215 as an example, the instance creation request includes the identifier of the target resource node. Based on the identifier of the target resource node, the POD resource management node 215 sends an instruction to create an EMAI to the target resource node.
[0108] Optionally, the first control node 211 can also perform metadata management, quotas, and authentication. Metadata management refers to inventorying, integrating, and managing metadata such as technical metadata and operational metadata. Quotas refer to limiting the number of cloud products (services) purchased by tenants to prevent tenants from purchasing a large number of single cloud products, resulting in insufficient underlying resources. Authentication refers to verifying the identity of the user, thereby ensuring that only authorized or authorized users can access cloud services or use cloud resources.
[0109] The hot unmounting management node 217 can manage the hot unmounting of the EMA super instance, that is, when the EMA super instance is mounted on an instance A, the EMA super instance can be unmounted without affecting the service of the instance A. The DC topology management node 218 can manage and optimize the physical topology structure of the data center to improve the reliability and efficiency of the data center.
[0110] It should be noted that the above-mentioned cloud platform can be a server cluster or distributed system composed of multiple physical servers, or it can be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), as well as big data and artificial intelligence platforms, or it can be a cloud computing service center.
[0111] The above-mentioned first control node 211, data persistence layer 212, billing system 213, application deployment channel 214, POD resource management node 215, cluster resource management node 216, thermal demounting management node 217, and DC topology management node 218 can be the same node, or they can be different nodes, or at least two of the above-mentioned multiple nodes can constitute the same node, which is not limited to this in the embodiment of the present application.
[0112] Those skilled in the art should understand that the above-mentioned EMAS management node, multiple resource nodes and cloud platform are only examples, and other existing or future EMAS management nodes, multiple resource nodes and cloud platforms, if applicable to the embodiments of the present application, should also be included in the scope of protection of the embodiments of the present application and are included here by reference.
[0113] It should be noted that the application scenarios and implementation environments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0114] Please refer to Figure 4 , Figure 4 It is a structural diagram of a POD resource management node provided in an embodiment of the present application. The POD resource management node includes a POD resource allocator, a POD memory global allocator, a POD computing power pool, a POD resource global monitor and a POD resource global scheduler.
[0115] Among them, the POD resource allocator receives the super instance creation request sent by the first control node 211, and the instance creation instruction includes the target resource node identifier and occupancy information, and the occupancy information indicates the resource size of each target resource node that the current super instance needs to occupy, and sends the target resource node identifier and occupancy information to the POD memory global addresser and the POD computing power pool respectively. The POD memory global addresser records the memory resource occupancy based on the occupancy information, and the POD computing power pool records the occupancy of computing resources based on the occupancy information. The POD resource allocator can also send an instruction to create an EMAI to the virtualization layer of the target resource node. The POD memory global allocator can also integrate the memory resources of the resource nodes in the POD, and record the memory model, rate, bandwidth and other information of the resource nodes, and then perform unified addressing to realize the registration of the resource nodes, and hierarchically manage the resource nodes through data structures such as bitmaps and hash tables. The POD computing power pool can also integrate the computing resources of the resource nodes within the POD, and record the CPU architecture, generation, main frequency, number of cores and other information of the resource nodes to realize the registration of the resource nodes. The POD resource global monitor monitors the CPU, memory utilization, and bandwidth occupancy of the resource nodes within the POD to identify resource nodes with high resource occupancy (overload), i.e., hotspots. The POD resource global scheduler can reallocate resources across resource nodes based on the hotspots identified by the POD resource global monitor and the real-time global resource status sent by the POD memory global addresser and the POD computing power pool.
[0116] Next, the method for providing cloud services provided in the embodiment of the present application is explained in detail.
[0117] Figure 5 This is a flow chart of a method for providing cloud services provided by an embodiment of the present application. The method is applied to an EMAS management node included in a cloud platform. The cloud platform also includes multiple resource nodes, which are used to provide at least one of computing resources and memory resources. Please refer to Figure 5 , the method comprises the following steps.
[0118] Step 501: providing a configuration interface, where the configuration interface is used to prompt the tenant to input attribute information of the target cloud service to be provided according to business requirements, where the attribute information of the target cloud service includes the provision method of the target cloud service and performance configuration information of the target cloud service.
[0119] In some embodiments, the EMAS management node prompts the tenant to input the attribute information of the target cloud service to be provided according to the business requirements by providing a configuration interface. The tenant inputs the provision mode of the target cloud service and the performance configuration information of the target cloud service based on the configuration interface.
[0120] As an example, the target cloud service may be provided in a super instance provision mode or a non-instance provision mode, and the tenant may select either of the two as the target cloud service provision mode.
[0121] The super-instance provision mode means that the target EMA super-instance used to provide the target cloud service to the tenant is visible to the tenant, and the life cycle of the target EMA is managed by the tenant. The non-instance provision mode means that the target EMA super-instance is not visible to the tenant, and the life cycle of the target EMA is not managed by the tenant.
[0122] In the case where the target cloud service selected by the tenant is provided in a different manner, the performance configuration information of the target cloud service includes different contents, which will be introduced below respectively.
[0123] In the first case, the target cloud service is provided in a super instance provision mode. In this case, the performance configuration information of the target cloud service includes usage type, memory capacity, capacity guarantee mode, capacity step, computing resources and bandwidth. Among them, the usage type indicates whether the target EMA super instance provides services in the form of mounting, the memory capacity indicates the memory capacity of the target EMA super instance, the capacity guarantee mode indicates whether the resource nodes to which the memory resources of the target EMA super instance are distributed are variable, the capacity step indicates the memory size of each EMAI included in the target EMA super instance, the computing resources indicate the computing performance of the target EMA super instance, and the bandwidth indicates the data transmission volume of the target EMA super instance per unit time.
[0124] In some embodiments, the usage type includes single instance usage and mounted usage. Single instance usage means that the target EMA super instance does not provide services in a mounted form. Mounted usage means that the target EMA super instance provides services in a mounted form.
[0125] It should be noted that the tenant can directly select one of the two parameters, single instance use or mounted use, to determine the usage type. In actual applications, the tenant can also determine the usage type of the target cloud service by selecting the corresponding image for single instance use or the corresponding image for mounted use, that is, determining the usage type of the target cloud service based on the image type, which is not limited in the embodiments of the present application.
[0126] Optionally, when the usage type is single instance, the tenant can use the target EMA super instance as a special cloud server, that is, a low-cost, large-memory instance. The tenant can mount data volumes, mount virtual network cards, or add elastic IP addresses to the target EMA super instance.
[0127] In some embodiments, the memory capacity is divided into guaranteed capacity and burst capacity, wherein the guaranteed capacity refers to the minimum memory capacity required to be guaranteed by the target EMA super instance, and the burst capacity indicates the maximum capacity of the target EMA super instance, which is greater than or equal to the guaranteed capacity.
[0128] It should be noted that, when charging, the larger the guaranteed capacity is, the higher the price is; and when the guaranteed capacity is the same, the larger the difference between the guaranteed capacity and the burst capacity is, the higher the price is.
[0129] In some embodiments, the capacity guarantee mode includes a dynamic mode and a static mode. The dynamic mode is a rotatable mode, which means that the EMAS management node can split and relocate the EMAI included in the target EMA super instance according to the resource usage of the underlying physical server. The static mode is a non-rotatable mode, which means that after the EMASI is created, it is not allowed to be split or relocated.
[0130] Splitting means providing resources originally provided by one EMAI through at least two EMAIs. For example, EMAI1 on resource node A provides 8G of memory resources. After splitting, EMAI2 on resource node B can provide 3G of memory resources, and EMAI3 on resource node C can provide 5G of memory resources. That is, the 8G of memory resources are ultimately provided by two EMAIs.
[0131] Relocation means providing resources originally provided by the first resource node through other resource nodes except the first resource node. For example, EMASI1 on resource node A provides 8G memory resources, and after relocation, EMAI2 on resource node B can provide 8G memory resources.
[0132] Optionally, the default capacity guarantee mode of the EMAS management node is the dynamic mode, that is, when the tenant does not select the capacity guarantee mode, the default capacity guarantee mode is the dynamic mode, so that resources can be scheduled according to the resource usage of the underlying physical server, thereby achieving full utilization of resources.
[0133] It should be noted that when billing, the price of dynamic mode is higher than that of static mode.
[0134] In some embodiments, the capacity step indicates the minimum value of the memory capacity of each EMASI included in the target EMA super instance, that is, the memory capacity of each EMAI is not less than the capacity step, and the capacity step limits the lower limit of the memory capacity specification of all EMAIs that constitute the EMA super instance. In this case, the number of EMAIs that constitute the EMA super instance is not greater than the value after the actual memory capacity of the EMA super instance is divided by the capacity step.
[0135] For example, the target EMA superinstance requires 128G memory capacity, and the capacity step is set to 32G. Then the memory capacity of the EMAIs that constitute the target EMA superinstance is greater than or equal to 32G. In this case, the target EMA superinstance consists of at most 4 EMAIs.
[0136] Optionally, if the tenant sets the capacity step to 0, in this case, it does not mean that the memory resource corresponding to each EMASI is 0, but that the EMAS management node can create EMASI for the tenant based on the resource usage of the underlying physical server, without being constrained by the capacity step. The size of the EMASI memory resource is related to the size of the resources actually allocated by the EMAS management node. For example, the EMAS management node can create EMASI in resource nodes with small memory capacity first based on the resource usage of the underlying physical server.
[0137] It should be noted that the default capacity step of the EMAS management node is 0, that is, when the tenant does not select a capacity step, the EMAS management node can create an EMASI for the tenant based on the resource usage of the underlying physical server.
[0138] It should be noted that when billing, the larger the capacity step, the higher the price.
[0139] For example, bandwidth may refer to the amount of data transmitted per second by the target EMA super instance, in units of GB per second. Of course, in practical applications, bandwidth may also be represented in other forms, which is not limited in the embodiments of the present application.
[0140] It should be noted that when charging, the greater the bandwidth, the higher the price.
[0141] In some embodiments, the unit of computing resources is a virtual computing unit (virtual CPU unit, VCU). One VCU can be a core in a physical CPU or a data processor (Data Processing Unit, DPU), or a hyperthread of a core in a physical CPU or DPU. This is not limited to the embodiments of the present application.
[0142] It should be noted that the one VCU can be a computing resource used by the target EMA superinstance alone, or a computing resource shared with other EMA superinstances, and this embodiment of the application does not limit this. For example, if the target EMA superinstance includes the computing resources of 1VCU, EMA superinstance 1 and the target EMA superinstance can share the computing resources of the 1VCU. For example, please refer to Figure 6The memory resources of EMA super instance 01 are 128GB, and the computing resources are 16VCU. The memory resources of EMA super instance 02 are 256GB, and the computing resources are 16VCU. The usage type of EMA super instance 01 and EMA super instance 02 is single instance usage, and EMA super instance 01 and EMA super instance 02 share the computing resources of 16VCU. The memory resources of EMA super instance 01 and EMA super instance 02 are not shared.
[0143] Optionally, the default computing resource of the EMAS management node is 1 VCU, that is, when the tenant does not set the computing resource, the default computing resource is 1 VCU.
[0144] Based on the above description, the usage types include single instance usage and mounted usage. In the case of different usage types, the performance configuration information of the target cloud service may also include some different information, which will be introduced below.
[0145] In case 1, the usage type is single instance usage, that is, the usage type indicates that the target EMA super instance does not provide services in the form of mounting. At this time, the performance configuration information of the target cloud service also includes a latency specification and a placement strategy. The latency specification indicates the access latency of the memory resources of the target EMA super instance, and the placement strategy indicates whether the memory resources and computing resources of the target EMA super instance are located in the same resource node.
[0146] In some embodiments, the latency specification includes performance priority or cost priority. Performance priority means that the EMAS management node selects a resource node with the shortest latency from multiple resource nodes as the target resource node. Cost priority means that the EMAS management node selects a resource node with a lower price from multiple resource nodes as the target resource node.
[0147] For example, if one target resource node is needed, but there are five resource nodes that meet the requirements of the tenant's memory capacity, capacity step, computing resources, and bandwidth, in this case, if the tenant chooses performance first, the EMAS management node can select one resource node with the smallest memory resource access latency from the five resource nodes as the target resource node. If the tenant chooses cost first, the EMAS management node can determine the price of each resource node according to the relevant algorithm, and then select the one resource node with the lowest price from the five resource nodes as the target resource node.
[0148] In actual applications, in addition to directly selecting performance priority or cost priority, tenants can also enter a specific latency threshold to determine the latency specification. In this case, the EMAS management node determines the target resource node based on the latency threshold, and the access latency of the memory resource of the target EMA super instance is not greater than the latency threshold.
[0149] For example, the latency threshold input by the tenant may be 100 milliseconds. If one target resource node is currently required, but there are five resource nodes that meet the memory capacity, capacity step, computing resources, and bandwidth requirements configured by the tenant, in this case, a resource node with a latency less than or equal to the latency threshold may be selected from the five resource nodes as the target resource node.
[0150] It should be noted that if there are at least two resource nodes among the above-mentioned five resource nodes whose delays are less than or equal to the delay threshold, then one resource node can be randomly selected from the at least two resource nodes as the target resource node, or, the resource node with the lowest price can be selected from the two resource nodes as the target resource node, or, the resource node with the best performance can be selected from the two resource nodes as the target resource node. The embodiments of the present application do not limit this.
[0151] Optionally, the default latency specification of the EMAS management node is cost priority, that is, when the tenant does not select a latency specification, the default latency specification is cost priority. Since resources with low utilization rates are usually lower in price, the EMAS management node can schedule lower-priced resources for tenants based on the resource usage of the underlying physical servers, thereby making full use of the idle resources of the data center.
[0152] In some embodiments, the placement strategy includes affinity and anti-affinity, wherein affinity means that the memory resources and computing resources of the target EMA superinstance are located in the same resource node, and anti-affinity means that the memory resources and computing resources of the target EMA superinstance are not located in the same resource node.
[0153] It should be noted that if the tenant does not fill in the placement strategy, the EMAS management node can determine the resource node where the computing resources and memory resources of the target EMA super instance are located based on the resource usage of the underlying physical server.
[0154] Case 2: The usage type is mount usage, that is, the usage type indicates that the target EMA super instance provides services in the form of mounting. At this time, the performance configuration information of the target cloud service also includes the identification, latency specification, placement strategy, access strategy and usage mode of at least one target instance, the target instance refers to the instance used to mount the target EMA super instance, the latency specification indicates the access latency of the target instance to the target EMA super instance, the placement strategy indicates whether the target EMA super instance and the first instance are located in the same resource node, the first instance is one of the at least one target instance, the access strategy indicates the read and write permissions of the at least one target instance to the target EMA super instance, and the usage mode indicates the memory addressing method of the target EMA super instance and the second instance, the second instance is one of the at least one target instance.
[0155] It should be noted that the target instance can be a virtual machine instance, a bare metal server instance, or a container instance. The target instance needs to be created using an image that supports EMA capabilities.
[0156] In some embodiments, the latency specification includes performance priority or cost priority. Among them, performance priority means that the EMAS management node selects the resource node with the shortest access latency to the target instance from multiple resource nodes as the target resource node. Cost priority means that the EMAS management node selects the resource node with the lowest price from multiple resource nodes as the target resource node.
[0157] For example, if one target resource node is needed, but there are five resource nodes that meet the requirements of the tenant's memory capacity, capacity step, computing resources, and bandwidth, in this case, if the tenant chooses performance first, the EMAS management node can select one resource node with the smallest access latency to the target instance from the five resource nodes as the target resource node according to the relevant algorithm. If the tenant chooses cost first, the EMAS management node can determine the price of each resource node according to the relevant algorithm, and then select one resource node with the lowest price from the five resource nodes as the target resource node.
[0158] In actual applications, in addition to directly selecting performance priority or cost priority, tenants can also enter a specific latency threshold to determine the latency specification. In this case, the EMAS management node determines the target resource node based on the latency threshold so that the access latency of the target instance to the target EMA super instance is no greater than the latency threshold.
[0159] For example, the latency threshold input by the tenant may be 100 milliseconds. If one target resource node is currently needed, but there are five resource nodes that meet the requirements of memory capacity, capacity step, computing resources, and bandwidth configured by the above tenant, in this case, a resource node whose access latency to the target instance is less than or equal to the latency threshold can be selected from the five resource nodes as the target resource node.
[0160] It should be noted that if there are at least two resource nodes among the above-mentioned five resource nodes whose delays are less than or equal to the delay threshold, then one resource node can be randomly selected from the at least two resource nodes as the target resource node, or, the resource node with the lowest price can be selected from the two resource nodes as the target resource node, or, the resource node with the best performance can be selected from the two resource nodes as the target resource node. The embodiments of the present application do not limit this.
[0161] Optionally, the default latency specification of the EMAS management node is cost priority, that is, when the tenant does not select a latency specification, the default latency specification is cost priority. Since resources with low utilization rates are usually lower in price, the EMAS management node can schedule lower-priced resources for tenants based on the resource usage of the underlying physical servers, thereby making full use of the idle resources of the data center.
[0162] In some embodiments, the placement strategy includes affinity and anti-affinity, wherein affinity means that the target EMA superinstance and the first instance are located in the same resource node, and anti-affinity means that the target EMA superinstance and the first instance are not located in the same resource node.
[0163] It should be noted that if the tenant selects a placement strategy, the tenant also needs to enter the identifier of the first instance so that the EMAS management node can determine the location where the first instance is deployed. If the tenant does not fill in the placement strategy, the EMAS management node can determine the resource node where the computing resources and memory resources of the target EMA super instance are located based on the resource usage of the underlying physical server.
[0164] In some embodiments, the access policies include private, shared read-only, and shared read-write. Among them, private means that when the number of target instances is 1, the target instance has read and write permissions to the target EMA super instance. Shared read-only means that when the number of target instances mounted on the target EMA super instance is greater than or equal to 2, the primary mounted instance of the at least two target instances has read and write permissions, and the other target instances have only read-only permissions. Shared read-write means that when the number of target instances mounted on the target EMA super instance is greater than or equal to 2, the at least two target instances have read and write permissions.
[0165] It should be noted that if the tenant only enters the ID of one target instance, the access policy is set to private by default. In addition, if the access policy is set to shared read-only, the tenant also needs to enter the ID of the primary mounting instance.
[0166] In some embodiments, the usage modes include full peer mode, semi-peer mode and heterogeneous mode. Among them, the full peer mode refers to the full management of GuestOS, that is, the total memory of the second instance is composed of the local memory of the second instance and the memory of the target EMA super instance, and the local memory of the second instance and the memory of the target EMA super instance are uniformly addressed. The semi-peer mode refers to the partial management of GuestOS, that is, the total memory of the second instance is composed of the local memory of the second instance and the memory of the target EMA super instance, and the local memory of the second instance and the memory of the target EMA super instance are uniformly addressed, but the user can know the address segment corresponding to the local memory of the second instance and the address segment corresponding to the memory of the target EMA super instance. In the heterogeneous mode, GuestOS does not manage the EMA super instance memory pool and does not uniformly address it. The EMA super instance is similar to another non-uniform memory access architecture (NUMA) node, and the tenant or authorized user is responsible for resource management.
[0167] Optionally, an EMA superinstance can be mounted with a virtual machine or container. Two EMA superinstances can be mounted on the same virtual machine or container. For example, refer to Figure 7 , the virtual machine or container mounts a 2 terabyte (TB) Elastic Volume Service, namely a 2 TB cloud hard disk, EMA super instance 1 and EMA super instance 2. In some embodiments, EMA super instance 3 can also support sharing, please refer to Figure 8 ,EMA super instance 3 can be mounted to two virtual machines or containers at the same time.
[0168] In the second case, the target cloud service is provided in a non-instance-free manner. At this time, the performance configuration information of the target cloud service includes service type, performance specifications, maximum number of simultaneous connections and rate cap. The service type indicates the tenant's business demand for memory resources and computing resources, the performance specifications indicate the number of target EMA super instances, the maximum number of simultaneous connections indicates the number of instances that the target EMA super instance can connect to at the same time, and the rate cap indicates the upper limit of resources provided by the cloud platform to tenants.
[0169] In some embodiments, service types include memory expansion, computing power offloading, and caching. Different service types have different performance requirements for the target EMA super instance. Among them, the cache requires high bandwidth, and the requirements for computing resources and latency specifications are not high. Memory expansion has requirements for computing resources and memory capacity, and computing power offloading does not require high computing resources. Of course, in actual applications, there may be other service types that can reflect business scenarios, and the embodiments of the present application do not limit this.
[0170] For example, the performance specifications include standard, high performance, and best effort. Under the standard specification, the number of target EMA superinstances is related to the number of instances connected to the target EMA superinstance, and the number of instances connected to the target EMA superinstance is greater than the number of target EMA superinstances. Under the high performance specification, the number of instances connected to the target EMA superinstance is equal to the number of EMA superinstances, that is, each instance connected to the target EMA superinstance corresponds to one target EMA superinstance. Under the best effort specification, there is only one target EMA superinstance, that is, all the instances connected to the target EMA superinstances share one target EMA superinstance.
[0171] It should be noted that if the tenant does not fill in the above performance specifications and the maximum number of simultaneous connections, the EMAS management node can dynamically adjust the number of target EMA super instances and the maximum number of simultaneous connections based on the resource usage of the underlying physical server.
[0172] Optionally, the unit of the rate cap can be RMB per hour, RMB per month, or RMB per year. The embodiment of the present application does not limit the billing period of the rate cap.
[0173] In some embodiments, after the tenant determines the above-mentioned service type, performance specifications, and maximum number of simultaneous connections, the EMAS management node can determine the basic price corresponding to the service type, performance specifications, and maximum number of simultaneous connections configured by the tenant according to relevant algorithms, and the upper limit of the rate filled in by the tenant is greater than or equal to the basic price.
[0174] Optionally, the EMAS management node stores the correspondence between the service type and the service price, the correspondence between the performance specification and the first price coefficient, and the correspondence between the maximum number of simultaneous links and the second price coefficient. Based on the service type configured by the tenant, the target service price corresponding to the service type configured by the tenant can be determined. Based on the performance specifications and the maximum number of simultaneous links configured by the tenant, the target first price coefficient and the target second price coefficient can be determined from the correspondence between the performance specification and the first price coefficient, and the correspondence between the maximum number of simultaneous links and the second price coefficient. The target service price is multiplied by the target first price coefficient and then by the target second price coefficient to obtain the base price corresponding to the service type, performance specification, and maximum number of simultaneous links configured by the tenant. Of course, the above method of determining the base price is only an example. In actual applications, the base price can also be determined by other methods, and the embodiments of the present application do not limit this.
[0175] Step 502: Obtain attribute information of the target cloud service from the configuration interface, and based on the attribute information of the target cloud service, create a target EMA super instance in the target resource node included in the multiple resource nodes, wherein the target EMA super instance is used to provide the target cloud service for the tenant, and the target resource node includes at least one resource node, and the available resources of the target resource node meet the business needs of the tenant.
[0176] Obtain the attribute information of the available resources of each resource node in each resource pool, determine the target resource node from the multiple resource nodes based on the attribute information of the available resources of each resource node in each resource pool and the attribute information of the target cloud service, each resource node in the target resource node is located in the same resource pool, create an elastic memory acceleration instance EMAI in each resource node included in the target resource node to obtain one or more EMAIs, and generate a target EMA super instance based on the one or more EMAIs.
[0177] In some embodiments, the configuration parameters of the target cloud service can be determined based on the attribute information of the target cloud service, and the target resource node can be determined from multiple resource nodes based on the configuration parameters of the target cloud service and the attribute information of the available resources of each resource node in each resource pool.
[0178] In the case where the target cloud service is provided in different ways, the methods for determining the configuration parameters of the target cloud service are different, which will be introduced below respectively.
[0179] In the first case, the target cloud service is provided in a super instance provision mode. In this case, the performance configuration information of the target cloud service can be directly used as the configuration parameters of the target cloud service.
[0180] In the second case, the target cloud service is provided in a non-instance provision mode. In this case, the EMAS management node stores the correspondence between the service type and the configuration parameters of the target cloud service. The configuration parameters of the target cloud service include guaranteed capacity, burst capacity, computing resources, capacity step, bandwidth, latency specification, guarantee mode, and placement strategy. The EMAS management node can determine the configuration parameters of the target cloud service from the correspondence between the service type and the configuration parameters of the target cloud service according to the service type configured by the tenant.
[0181] Based on the attribute information of the available resources of each resource node in each resource pool and the configuration parameters of the target cloud service, there are many ways to determine the target resource node from multiple resource nodes. In some embodiments, the first fit, best fit and other algorithms can be used to determine the target resource node, which is not limited to the embodiments of the present application.
[0182] It should be noted that in addition to obtaining the attribute information of the target cloud service from the configuration interface, the attribute information of the above-mentioned target cloud service can also be obtained through API calls, email interactions, work order interactions, etc., which is not limited in this embodiment of the present application.
[0183] Step 503: Based on the provision mode of the target cloud service, a management interface of the target EMA superinstance is set, and the management interface of the target EMA superinstance is provided to the tenant.
[0184] In some embodiments, the EMAS management node can send an SDK corresponding to the target cloud service provision method to the tenant, and the tenant can use the target EMA super instance based on the SDK, and the SDK can indicate the method of using the target EMA super instance.
[0185] In actual applications, when the target cloud service is provided in a non-instance provision mode, the EMAS management node can create a target non-instance service node and return the identifier of the target non-instance service node to the tenant. The underlying layer of the target non-instance service node is the target EMA super-instance. In this case, the SDK corresponding to the non-instance provision mode includes the EMA server installation package. The tenant can install the EMA server for the instance that needs to connect to the target EMA super-instance, and based on the SDK and the identifier of the target non-instance service node, configure the backend target of the EMA server as the target non-instance service node.
[0186] For example, see Fig. 9 In the case where the target cloud service is provided in an instance-free manner, the resources of the target instance-free service node may come from the resources of the memory resource node and the computing resource node. In some embodiments, the resources of the target instance-free service node may also be resources from the DPU or other devices collected by the idle resource collection node, such as idle resources of the acceleration node and the network node. Please refer to Fig.10 , the target instanceless service node still provides resources for the target EMA super instance, but the target EMA super instance itself is transparent to the tenant. The EMAS management node can gradually allocate resources to the target EMA super instance. That is to say, when there is a request and the rate cap is met, resources are allocated to the target EMA super instance according to the resources required by the request. If there is no request, no resources are allocated to the target EMA super instance. That is, the resources allocated by the EMAS management node to the target EMA super instance depend on the actual amount of resources required by the tenant. As long as it is within the rate cap, the EMAS management node can continue to provide resources step by step. Once the rate cap is reached, the request will be rejected or the historical data in the memory will be replaced with new data through memory page swap technology (swap) and the least recently used (LRU) algorithm.
[0187] Next, a method for providing cloud services provided by an embodiment of the present application will be described again through three examples.
[0188] For the first example, see Fig.11 The tenant first creates four ECS instances through the ECS management node included in the cloud platform, namely virtual machine 01, virtual machine 02, virtual machine 03 and virtual machine 04. The images of these four ECS instances support EMA capabilities. Then the tenant can enter the attribute information of the target cloud service in the configuration interface provided by the EMAS management node. Among them, the service provision mode of the target cloud service is the non-instance provision mode. The performance configuration information of the target cloud service includes the service type of computing power offloading, the performance specification is standard, the maximum number of simultaneous links is 4, and the rate cap is 20.98 yuan / hour. Please refer to Fig.12 . The EMAS management node creates the target instanceless service node 01 and the EMA super instance 01 based on the attribute information of the target cloud service, and returns the identifier 01 of the target instanceless service node and the SDK corresponding to the instanceless provision method to the tenant. Based on the SDK corresponding to the instanceless provision method and the identifier 01 of the target instanceless service node, the tenant can install the EMA server on the ECS instance and set the backend target of the EMA server to the target instanceless service node, so as to connect the four ECS instances with the target instanceless service node, and then offload the computing operations that need to be offloaded in the business to the EMA super instance 01. The computing operations that need to be offloaded can be network packaging / unpacking, encryption / decryption, and other input / output operations. It should be noted that Fig.12 This is just an example. In actual applications, the backend of the target instanceless service node 01 is not necessarily an EMA super instance. The number of the EMA super instances can be flexibly adjusted according to the performance configuration information of the target cloud service set by the tenant.
[0189] In the second example, if the tenant needs to use ECS instance 1 to execute the computing work brought by the Java application deployed on the ECS instance 1, the ECS instance 1 itself also needs to perform the memory garbage collection function, and the execution of the garbage collection function will affect the efficiency of business execution. In order to improve the performance of Java applications, the cloud platform can provide a Java Runtime Environment Accelerating Service (Java Runtime Environment Accelerating Service, JAS) based on a virtual machine, also known as a Java application performance optimization service. The JAS can provide services to tenants in combination with a method for providing cloud services provided in an embodiment of the present application.
[0190] In this case, the cloud platform includes JAS management nodes, ECS management nodes, and EMAS management nodes. Please refer to Fig.13. The tenant purchases ECS instance 1 through the JAS management node and enters the unloading service type, which refers to the computing type that ECS instance 1 needs to unload. In the above scenario, the unloading service type is the garbage collection unloading service. The JAS management node can call the ECS management node to create ECS instance 1. The ECS management node uses an image that contains the Java Runtime Environment (JRE) and supports JAS capabilities to create ECS instance 1 and ECS instance 2. Among them, ECS instance 1 is used to execute the computing work brought by the Java application deployed on the ECS instance 1, and ECS instance 2 is used to perform garbage collection functions.
[0191] In some embodiments, the JAS management node stores a correspondence between the offloading service type and the attribute information of the target cloud service. The attribute information includes the provision method of the target cloud service and the performance configuration information of the target cloud service. The performance configuration information includes guaranteed capacity, burst capacity, capacity guarantee mode, bandwidth, latency specification, access strategy and usage type. The JAS management node can determine the attribute information of the target cloud service from the correspondence. Among them, the provision method of the target cloud service corresponding to the garbage collection offloading service is the super instance provision method, the guaranteed capacity is a guaranteed capacity of 64GB, the burst capacity is 64GB, the capacity guarantee mode is a static mode, the bandwidth is 12GB per second, the latency specification is performance priority, the access strategy is shared read and write, the usage type is mounted and used, the target instances are ECS instance 1 and ECS instance 2, and the placement strategy is affinity with ECS instance 2. The JAS management node can determine the attribute information of the target cloud service based on the garbage collection offloading service, and then send the attribute information of the target cloud service to the EMAS management node, please refer to Fig.14 , the EMAS management node can create EMA super instance 1 based on the attribute information of the target cloud service. The EMA super instance 1 and ECS instance 2 are located in the same resource node, namely resource node 1. The JAS management node calls the EMAS management node to mount the EMA super instance 1 to ECS instance 1 and ECS instance 2.
[0192] The tenant can directly operate ECS instance 1, which is responsible for the computing work of the application itself. The local memory of ECS instance 1 is equivalent to a high-speed memory buffer. EMA super instance 1 stores complete local memory information of ECS instance 1. ECS instance 2 can perform garbage collection on the memory in EMA super instance 1 and synchronize the garbage collection results to the local memory of ECS instance 1, so that ECS instance 2 can assist ECS instance 1 in completing the garbage collection function.
[0193] Considering that the computing resource performance of EMA super instance 1 is insufficient, in the second example, ECS instance 2 is created and garbage collection is performed through ECS instance 2. EMA super instance 1 is used to synchronize the local memory information of ECS instance 1. In actual applications, if the computing resource performance of EMA super instance 1 is high, there is no need to create ECS instance 2, and garbage collection can be performed directly through EMA super instance 1.
[0194] For the third example, see Fig.15 , the cloud platform can provide a data caching service, through which tenants can purchase ultra-high cost-effective memory caching services. The data caching service can provide services to tenants in combination with a method for providing cloud services provided in an embodiment of the present application. The data caching service can be a memory architecture and system (memArts), and in actual applications it can also be other types of data caching services, which are not limited in the embodiments of the present application.
[0195] Tenants purchase memory cache services through the data cache service management node and specify the attribute information of the target cloud service. The target cloud service is provided in the super instance mode, with a guaranteed capacity of 128GB, a burst capacity of 128GB, a capacity guarantee mode of dynamic mode, a bandwidth of 16GB per second, a latency specification of cost priority, an access policy of private, and a usage type of mounted use. In this case, the data cache service management node calls the EMAS management node to create EMA super instance 2. Since the latency specification is cost priority, the target resource node gives priority to the resource node with the smallest resource specification among the resource nodes that meet the attribute information of the target cloud service. The data cache service control plane calls the ECS management node to create an ECS instance for the tenant as a cache controller. The cache controller instance is responsible for maintaining the synchronization of data in the cache with data in the persistence layer. The cache controller instance uses the image that supports the data cache service provided by the data cache service to ensure that the ECS contains the server of the data cache service. The data cache service management node calls the EMAS management node to mount the EMA super instance to the cache controller instance. The EMAS management node sets the management interface of the target EMA super instance based on the provision method of the target cloud service, and sends the SDK corresponding to the provision method of the target cloud service to the tenant. The tenant can use the target EMA super instance based on the SDK.
[0196] In actual applications, after providing the management interface to tenants, the EMAS management node can also determine whether the resources of the target EMA super-instance are overloaded based on the tenants' resource usage of the target EMA super-instance. When it is determined that the resources of the target EMA super-instance are overloaded, it determines whether the resources provided by the cloud platform for the target EMA super-instance have reached the upper limit of configured resources based on the attribute information of the target cloud service. When the resources provided by the cloud platform for the target EMA super-instance do not reach the upper limit of configured resources, the target resource node is adjusted.
[0197] In some embodiments, the resources of the target EMA superinstance include memory resources and computing resources. Based on the usage of the memory resources of the target EMA superinstance by the tenants, it is determined whether the memory resources of the target EMA superinstance are overloaded. Based on the usage of the computing resources of the target EMA superinstance, it is determined whether the computing resources of the target EMA superinstance are overloaded. If it is determined that the memory resources and / or computing resources of the target EMA superinstance are overloaded, it is determined that the resources of the target EMA superinstance are overloaded.
[0198] In some embodiments, the memory resource usage includes a memory occupancy ratio. If the memory occupancy ratio is greater than a memory ratio threshold, it is determined that the memory resources of the target EMA superinstance are overloaded; otherwise, it is determined that the memory resources of the target EMA superinstance are not overloaded.
[0199] The memory ratio threshold is set in advance, and the value range of the memory ratio threshold is [0-1]. For example, the memory ratio threshold can be set to 0.8, that is, when the memory resource usage ratio of the target EMA super instance is greater than 0.8, the memory resource of the target EMA super instance is determined to be overloaded. Of course, in actual applications, the memory ratio threshold can also be adjusted according to needs.
[0200] In some embodiments, the computing resource usage includes a computing resource occupancy ratio, a request queue number, and a response time. If the computing resource occupancy ratio is less than a computing resource ratio threshold, and the request queue number is less than a queue number threshold, and the response time is less than a response time threshold, it is determined that the computing resources of the target EMA superinstance are not overloaded, otherwise, it is determined that the computing resources of the target EMA superinstance are overloaded.
[0201] Of course, in actual applications, the computing resource usage may also include at least one of the computing resource occupancy ratio, the number of request queues, and the response time, which is not limited in the embodiments of the present application.
[0202] Among them, the computing resource ratio threshold, the queue quantity threshold and the response time threshold are set in advance. In actual applications, the computing resource ratio threshold, the queue quantity threshold and the response time threshold can also be adjusted according to needs.
[0203] In the case of different target cloud service provisioning methods, the implementation methods for determining whether the resources provided by the cloud platform for the target EMA super instance reach the configured resource upper limit are different, which will be introduced below.
[0204] When the target cloud service is provided in a non-instance provision mode, the resource configuration information provided by the current cloud platform for the target EMA super instance is obtained, and based on the resource configuration information, the configuration price corresponding to the resource configuration information is determined according to the relevant algorithm. If the configuration price is greater than or equal to the rate cap, it is determined that the resources provided by the cloud platform for the target EMA super instance have reached the configuration resource cap. Otherwise, it is determined that the resources provided by the cloud platform for the target EMA super instance have not reached the configuration resource cap.
[0205] When the resources of the target EMA super instance are overloaded, it means that the memory resources and / or computing resources of the target EMA super instance are overloaded. Therefore, when the target cloud service is provided in a super instance provision mode, if the types of overloaded resources are different, the methods of determining whether the resources provided by the cloud platform for the target EMA super instance reach the configured resource upper limit are different, which will be introduced below.
[0206] When it is determined that the memory resources of the target EMA super instance are overloaded, obtain resource configuration information provided by the current cloud platform for the target EMA super instance, where the configuration information includes the deployed memory capacity. If the deployed memory capacity is greater than or equal to the burst memory capacity, it is determined that the resources provided by the cloud platform for the target EMA super instance have reached the upper limit of the configured resources.
[0207] When it is determined that the computing resources of the target EMA super instance are overloaded, obtain the resource configuration information provided by the current cloud platform for the target EMA super instance, which includes the deployed computing resource specifications. If the deployed computing resource specifications are greater than or equal to the computing resource specifications configured by the tenant, it is determined that the resources provided by the cloud platform for the target EMA super instance have reached the configured resource upper limit.
[0208] When it is determined that both the memory resources and computing resources of the target EMA super instance are overloaded, obtain the resource configuration information provided by the current cloud platform for the target EMA super instance, which includes the deployed computing resource specifications and the deployed memory capacity. If the deployed computing resource specifications are greater than or equal to the computing resource specifications configured by the tenant and / or the deployed memory capacity is greater than or equal to the burst memory capacity, it is determined that the resources provided by the cloud platform for the target EMA super instance have reached the upper limit of the configured resources.
[0209] Optionally, when the resources provided by the cloud platform for the target EMA super instance reach the upper limit of configured resources, a prompt message is sent to the tenant, where the prompt message is used to indicate that the resources provided by the cloud platform for the target EMA super instance have reached the upper limit of configured resources.
[0210] In the case where the target cloud service is provided in a super-instance provision mode and the target EMA super-instance provides services in a mounted form, if the instance on which the target EMA super-instance is mounted also has other EMA super-instances or system volumes (for example, EVS) mounted thereon, and the remaining storage capacity of the other EMA super-instances or system volumes is greater than or equal to the amount of data in the target super-instance, the tenant may also trigger a hot demount instruction, and the EMAS management node may migrate the data in the target EMA super-instance to the migration destination in response to the hot demount instruction, thereby achieving hot demounting of the target EMA super-instance, and the migration destination is other EMA super-instances or system volumes other than the target EMA super-instance mounted thereon by the instance on which the target EMA super-instance is mounted.
[0211] In some embodiments, the implementation process of migrating the data in the target EMA superinstance to the migration destination includes: setting the status of the target EMA superinstance to being unhooked, packetizing the data in the target EMA superinstance according to a relevant algorithm to obtain multiple data packets, marking data attributes corresponding to the multiple data packets, respectively, the data attributes indicating the frequency of access to the data in the data packets, and migrating the multiple data packets to the migration destination based on the data attributes of the multiple data packets.
[0212] The data attributes include cold data, warm data and hot data. The frequency of cold data being accessed is lower than the frequency of warm data being accessed, and the frequency of warm data being accessed is lower than the frequency of hot data being accessed.
[0213] Based on the data attributes of the multiple data packets, the implementation process of migrating the multiple data packets to the migration destination includes: packaging and copying the data packets with data attributes of cold data and warm data to the migration destination, and copying the data packets with data attributes of hot data to the migration destination in multiple times according to relevant algorithms.
[0214] It should be noted that if the instance on which the target EMA super-instance is mounted has other EMA super-instances and a system volume mounted on it, the other EMA super-instance will be preferentially selected as the migration destination.
[0215] In the embodiment of the present application, since the attribute information of the target cloud service is input by the tenant according to the business needs, that is, the tenant does not need to be restricted by the preset specifications, and can directly customize the computing resources and memory resources of the target cloud service according to its own business needs, thereby meeting the needs of the tenant and improving the performance of the cloud service. In addition, since the target resource node includes multiple resource nodes, that is, the embodiment of the present application can integrate the resources of at least one resource node to provide services for the tenant. In this way, while meeting the needs of users, it can also effectively improve the utilization rate of idle resources in the data center, reduce resource waste and the operation and maintenance costs of the cloud service provider.
[0216] Fig.16 is a schematic diagram of the structure of an EMAS management node provided in an embodiment of the present application. The EMAS management node is an EMAS management node included in a cloud platform, and the cloud platform also includes multiple resource nodes. Fig.16 The EMAS management node includes: a providing module 1601, an acquiring module 1602, a creating module 1603 and a setting module 1604.
[0217] The provision module 1601 is used to provide a configuration interface, which is used to prompt the tenant to input the attribute information of the target cloud service to be provided according to the business requirements, and the attribute information includes the provision method of the target cloud service and the performance configuration information of the target cloud service. The detailed implementation process refers to the corresponding content in the above embodiments, which will not be repeated here.
[0218] The acquisition module 1602 is used to acquire the attribute information of the target cloud service from the configuration interface. The detailed implementation process refers to the corresponding content in the above embodiments, which will not be repeated here.
[0219] The creation module 1603 is used to create a target elastic memory acceleration EMA super instance in a target resource node included in multiple resource nodes based on the attribute information of the target cloud service, and the target EMA super instance is used to provide the target cloud service for the tenant, and the target resource node includes at least one resource node, and the available resources of the target resource node meet the business requirements. The detailed implementation process refers to the corresponding content in the above embodiments, which will not be repeated here.
[0220] The setting module 1604 is used to set the management interface of the target EMA super instance based on the provision mode of the target cloud service, and provide the management interface to the tenant. The detailed implementation process refers to the corresponding content in the above embodiments, which will not be repeated here.
[0221] Optionally, the target cloud service is provided in a super-instance provision mode, which means that the target EMA super-instance is visible to the tenant and the life cycle of the target EMA is managed by the tenant; the performance configuration information of the target cloud service includes usage type, memory capacity, capacity guarantee mode, capacity step, computing resources and bandwidth; the usage type indicates whether the target EMA super-instance provides services in a mounted form, the memory capacity indicates the memory capacity of the target EMA super-instance, the capacity guarantee mode indicates whether the resource nodes to which the memory resources of the target EMA super-instance are distributed are variable, the capacity step indicates the memory size of each elastic memory acceleration instance EMAI included in the target EMA super-instance, the computing resources indicate the computing performance of the target EMA super-instance, and the bandwidth indicates the amount of data transmitted by the target EMA super-instance per unit time.
[0222] Optionally, when the usage type indicates that the target EMA super instance does not provide services in a mounted form, the performance configuration information of the target cloud service also includes a latency specification and a placement strategy, wherein the latency specification indicates the access latency of the memory resources of the target EMA super instance, and the placement strategy indicates whether the memory resources and computing resources of the target EMA super instance are located on the same resource node.
[0223] Optionally, when the usage type indicates that the target EMA super instance provides services in a mounted form, the performance configuration information of the target cloud service also includes an identifier, latency specification, placement strategy, access policy and usage mode of at least one target instance, where the target instance refers to an instance used to mount the target EMA super instance, the latency specification indicates the access latency of the target instance to the target EMA super instance, the placement strategy indicates whether the target EMA super instance and the first instance are located on the same resource node, the first instance is one of the at least one target instance, the access policy indicates the read and write permissions of at least one target instance to the target EMA super instance, and the usage mode indicates the memory addressing method of the target EMA super instance and the second instance, and the second instance is one of the at least one target instance.
[0224] Optionally, the target cloud service is provided in an instance-free manner, which means that the target EMA super-instance is not visible to the tenant and the life cycle of the target EMA is not managed by the tenant; the performance configuration information of the target cloud service includes service type, performance specifications, maximum number of simultaneous connections and rate cap; the service type indicates the tenant's business demand for memory resources and computing resources, the performance specification indicates the number of target EMA super-instances, the maximum number of simultaneous connections indicates the number of instances that the target EMA super-instance can connect to at the same time, and the rate cap indicates the upper limit of resources provided by the cloud platform to the tenant.
[0225] Optionally, the multiple resource nodes are located in at least one resource pool; the creation module 1603 is specifically used to:
[0226] Obtain the attribute information of available resources of each resource node in each resource pool;
[0227] Determine a target resource node from a plurality of resource nodes based on the attribute information and performance configuration information of the available resources of each resource node in each resource pool, wherein each resource node in the target resource node is located in the same resource pool;
[0228] Creating an elastic memory acceleration instance EMAI in each resource node included in the target resource node to obtain one or more EMAIs;
[0229] Based on one or more EMAIs, a target EMA superinstance is generated.
[0230] Optionally, the EMAS management node also includes:
[0231] A first determination module is used to determine whether the resources of the target EMA super instance are overloaded according to the resource usage of the target EMA super instance by the tenant;
[0232] The second determination module is used to determine whether the resources provided by the cloud platform for the target EMA super instance have reached the upper limit of the configured resources based on the attribute information of the target cloud service when it is determined that the resources of the target EMA super instance are overloaded;
[0233] The adjustment module is used to adjust the target resource node when the resources provided by the cloud platform for the target EMA super instance do not reach the upper limit of the configured resources.
[0234] Optionally, the EMAS management node also includes:
[0235] The prompt module is used to send a prompt message to the tenant when the resources provided by the cloud platform for the target EMA super instance reach the upper limit of the configured resources. The prompt message is used to indicate that the resources provided by the cloud platform for the target EMA super instance have reached the upper limit of the configured resources.
[0236] In the embodiment of the present application, since the attribute information of the target cloud service is input by the tenant according to the business needs, that is, the tenant does not need to be restricted by the preset specifications, and can directly customize the computing resources and memory resources of the target cloud service according to its own business needs, thereby meeting the needs of the tenant and improving the performance of the cloud service. In addition, since the target resource node includes multiple resource nodes, that is, the embodiment of the present application can integrate the resources of at least one resource node to provide services for the tenant. In this way, while meeting the needs of users, it can also effectively improve the utilization rate of idle resources in the data center, reduce resource waste and the operation and maintenance costs of the cloud service provider.
[0237] It should be noted that: the EMAS management node device provided in the above embodiment only uses the division of the above functional modules as an example when providing cloud services. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the node is divided into different functional modules to complete all or part of the functions described above. In addition, the EMAS management node provided in the above embodiment and the method embodiment for providing cloud services belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.
[0238] Fig.16 The provision module, acquisition module, creation module and setting module in the EMAS management node shown can be implemented by software, or can be implemented by hardware, or can be implemented by a combination of software and hardware. Next, taking the provision module in the device for providing cloud services as an example, the implementation method of the provision module is introduced. Similarly, the implementation methods of the above-mentioned other modules can refer to the implementation method of the provision module.
[0239] As an example of a software functional unit, a module may include code running on a computing instance. The computing instance may include at least one of a physical host, a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, a module may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple data centers with similar geographical locations. Generally, a region may include multiple AZs.
[0240] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same VPC or in multiple virtual private clouds (VPCs). Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.
[0241] As an example of a hardware functional unit, the module provided may include at least one computing device, such as a server, etc. Alternatively, the module provided may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
[0242] The multiple computing devices included in the provision module can be distributed in the same region or in different regions. The multiple computing devices included in the provision module can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the provision module can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.
[0243] In other embodiments, the providing module in the EMAS management node can be used to execute any step in the above-mentioned method for providing cloud services, the acquiring module in the EMAS management node can be used to execute any step in the above-mentioned method for providing cloud services, the creating module in the EMAS management node can be used to execute any step in the above-mentioned method for providing cloud services, and the setting module in the EMAS management node can be used to execute any step in the above-mentioned method for providing cloud services. The steps that the providing module, acquiring module, creating module and setting module in the EMAS management node are responsible for implementing can be specified as needed. The different steps in the above-mentioned method for providing cloud services are respectively implemented by the providing module, acquiring module, creating module and setting module in the EMAS management node, thereby realizing the full functions of providing the EMAS management node.
[0244] Fig.17 1 is an architecture diagram of a cloud platform provided in an embodiment of the present application. The cloud platform includes an EMAS management node and multiple resource nodes, and the resource node is used to provide at least one of computing resources and memory resources. The EMAS management node and the multiple resource nodes establish a communication connection.
[0245] The EMAS management node is used to provide a configuration interface and obtain attribute information of the target cloud service from the configuration interface. Based on the attribute information, a target elastic memory acceleration EMA super instance is created in the target resource node included in multiple resource nodes. Then, based on the provision method of the target cloud service, a management interface of the target EMA super instance is set and provided to the tenant.
[0246] Fig.17 The EMAS management node and multiple resource nodes in the embodiment can be implemented by software or hardware. For example, the implementation of the EMAS management node is described below by taking the EMAS management node as an example. Similarly, the implementation of the resource node can refer to the implementation of the EMAS management node.
[0247] The EMAS management node may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the computing instance may be one or more. For example, the EMAS management node may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same AZ or in different AZs, each AZ including one data center or multiple data centers with close geographical locations. Generally, a region may include multiple AZs.
[0248] Similarly, multiple hosts / virtual machines / containers used to run the code can be distributed in the same VPC or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.
[0249] The EMAS management node may include at least one computing device, such as a server, etc. Alternatively, the EMAS management node may also be a device implemented using ASIC or PLD, etc. The PLD may be implemented using CPLD, FPGA, GAL or any combination thereof.
[0250] The multiple computing devices included in the EMAS management node can be distributed in the same region or in different regions. The multiple computing devices included in the EMAS management node can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the EMAS management node can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.
[0251] The present application embodiment also provides a computing device 100. Fig.18 As shown, the computing device 100 includes: a bus 102, a processor 104, a memory 106, and a communication interface 108. The processor 104, the memory 106, and the communication interface 108 communicate with each other through the bus 102. The computing device 100 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 100.
[0252] The bus 102 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.18 The bus 102 is represented by only one line, but it does not mean that there is only one bus or one type of bus. The bus 102 may include a path for transmitting information between various components of the computing device 100 (eg, the memory 106, the processor 104, and the communication interface 108).
[0253] The processor 104 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), a digital signal processor (DSP), an integrated circuit, etc. The integrated circuit may be an ASIC, a PLD, or a combination thereof. Optionally, the PLD may be a CPLD, an FPGA, a GAL, or any combination thereof.
[0254] The memory 106 may include a volatile memory, such as a random access memory (RAM). The memory 106 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid state drive (SSD), or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 106 exists independently and is connected to the processor 104 through the bus 102, or the memory 106 is integrated with the processor 104.
[0255] The memory 106 stores executable program codes, and the processor 104 executes the executable program codes to implement the aforementioned method for providing cloud services. That is, the memory 106 stores instructions for executing the method for providing cloud services.
[0256] For example, the memory 106 stores executable code, and the processor 104 executes the executable code to implement the above Fig.16 The functions of the providing module, obtaining module, creating module and setting module are shown. That is, the memory 106 stores instructions for executing the method for providing cloud services provided in the embodiment of the present application.
[0257] The communication interface 108 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 100 and other devices or communication networks. The network interface includes a wired communication interface, or also includes a wireless communication interface. Among them, the wired communication interface is, for example, an Ethernet interface. The Ethernet interface is an optical interface, an electrical interface, or a combination thereof. The wireless communication interface is a wireless local area network (WLAN) interface, a cellular network communication interface, or a combination thereof.
[0258] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes multiple computing devices. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.
[0259] like Fig.19As shown, the computing device cluster includes multiple computing devices 100. The memory 106 in the multiple computing devices 100 in the computing device cluster may store the same instructions for executing the above-mentioned method for providing cloud services.
[0260] In some possible implementations, the memory 106 of the multiple computing devices 100 in the computing device cluster may also store partial instructions for executing the above method for providing cloud services. In other words, the combination of the multiple computing devices 100 can jointly execute all instructions for executing the above method for providing cloud services.
[0261] It should be noted that the memory 106 in different computing devices 100 in the computing device cluster may store different instructions for executing part of the functions of the above-mentioned method for providing cloud services. That is, the instructions stored in the memory 106 in different computing devices 100 may implement the functions of some or all modules included in the apparatus for providing cloud services described below.
[0262] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network, etc. Fig. 20 A possible implementation is shown. Fig.16 As shown, two computing devices 100A and 100B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 106 in the computing device 100A stores instructions for executing the functions of a portion of the modules included in the EMAS management node described above. At the same time, the memory 106 in the computing device 100B stores instructions for executing the functions of another portion of the modules included in the EMAS management node described above.
[0263] It should be understood that Fig. 20 The functions of the computing device 100A shown in FIG. 1 may also be completed by multiple computing devices 100. Similarly, the functions of the computing device 100B may also be completed by multiple computing devices 100.
[0264] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to that of Fig.19 and Fig. 20 The connection mode of the computing device cluster is different in that the memory 106 in one or more computing devices 100 in the computing device cluster may store the same instructions for executing the method for providing cloud services.
[0265] In some possible implementations, the memory 106 of one or more computing devices 100 in the computing device cluster may also store partial instructions for executing the method for providing cloud services. In other words, the combination of one or more computing devices 100 may jointly execute instructions for executing the method for providing cloud services.
[0266] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by the computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device in the computer device cluster to execute the method for providing cloud services provided in the embodiment of the present application.
[0267] The embodiment of the present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device cluster, the computing device cluster executes a method for providing cloud services.
[0268] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)). It is worth noting that the computer-readable storage medium mentioned in the embodiment of the present application may be a non-volatile storage medium, in other words, a non-transient storage medium.
[0269] It should be understood that the "multiple" mentioned herein refers to two or more. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in order to facilitate the clear description of the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish between the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not limit them to be necessarily different.
[0270] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions. For example, the attribute information of the target cloud service involved in the embodiments of this application is obtained with full authorization.
[0271] The above-mentioned embodiments are provided for the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.
Claims
1. A method for providing cloud services, characterized in that: Applied to an elastic memory acceleration service EMAS management node included in a cloud platform, the cloud platform also includes a plurality of resource nodes, the resource nodes are used to provide at least one of computing resources and memory resources, the method includes: Providing a configuration interface, wherein the configuration interface is used to prompt the tenant to input attribute information of the target cloud service to be provided according to business requirements, wherein the attribute information includes the provision method of the target cloud service and the performance configuration information of the target cloud service; Acquire attribute information of the target cloud service from the configuration interface; Based on the attribute information, create a target elastic memory acceleration EMA super instance in a target resource node included in the multiple resource nodes, the target EMA super instance is used to provide the target cloud service for the tenant, the target resource node includes at least one resource node, and the available resources of the target resource node meet the business requirements; Based on the provision mode of the target cloud service, a management interface of the target EMA super instance is set, and the management interface is provided to the tenant.
2. The method according to claim 1, characterized in that The target cloud service is provided in a super instance provision mode, which means that the target EMA super instance is visible to the tenant and the life cycle of the target EMA is managed by the tenant; The performance configuration information of the target cloud service includes usage type, memory capacity, capacity guarantee mode, capacity step, computing resources and bandwidth; the usage type indicates whether the target EMA super instance provides services in a mounted form, the memory capacity indicates the memory capacity of the target EMA super instance, the capacity guarantee mode indicates whether the resource nodes to which the memory resources of the target EMA super instance are distributed are variable, the capacity step indicates the memory size of each elastic memory acceleration instance EMAI included in the target EMA super instance, the computing resources indicate the computing performance of the target EMA super instance, and the bandwidth indicates the amount of data transmitted by the target EMA super instance per unit time.
3. The method according to claim 2, characterized in that When the usage type indicates that the target EMA super instance does not provide services in a mounted form, the performance configuration information of the target cloud service also includes a latency specification and a placement strategy, wherein the latency specification indicates the access latency of the memory resources of the target EMA super instance, and the placement strategy indicates whether the memory resources and computing resources of the target EMA super instance are located on the same resource node.
4. The method according to claim 2, characterized in that In the case where the usage type indicates that the target EMA super instance provides services in a mounted form, the performance configuration information of the target cloud service also includes an identifier, a latency specification, a placement strategy, an access strategy and a usage mode of at least one target instance, wherein the target instance refers to an instance used to mount the target EMA super instance, the latency specification indicates the access latency of the target instance to the target EMA super instance, the placement strategy indicates whether the target EMA super instance and the first instance are located on the same resource node, the first instance is one of the at least one target instance, the access policy indicates the read and write permissions of the at least one target instance to the target EMA super instance, and the usage mode indicates the memory addressing method of the target EMA super instance and the second instance, and the second instance is one of the at least one target instance.
5. The method according to claim 1, characterized in that The target cloud service is provided in an instance-free provision mode, which means that the target EMA super instance is not visible to the tenant and the life cycle of the target EMA is not managed by the tenant; The performance configuration information of the target cloud service includes service type, performance specification, maximum number of simultaneous connections and rate cap; The service type indicates the tenant's business demand for memory resources and computing resources, the performance specification indicates the number of target EMA super instances, the maximum number of simultaneous connections indicates the number of instances that the target EMA super instance can connect to at the same time, and the rate cap indicates the upper limit of resources provided by the cloud platform to the tenant.
6. The method according to claim 1, characterized in that The multiple resource nodes are located in at least one resource pool; and based on the performance configuration information, creating a target elastic memory acceleration EMA super instance in a target resource node included in the multiple resource nodes includes: Obtain the attribute information of available resources of each resource node in each resource pool; Based on the attribute information of the available resources of each resource node in each resource pool and the performance configuration information, determining the target resource node from the multiple resource nodes, each resource node in the target resource node is located in the same resource pool; Creating an elastic memory acceleration instance EMAI in each resource node included in the target resource node to obtain one or more EMAIs; Based on the one or more EMAIs, the target EMA superinstance is generated.
7. The method according to claim 1, characterized in that After setting the management interface of the target EMA super instance based on the provision mode of the target cloud service and providing the management interface to the tenant, the method further includes: Determining whether resources of the target EMA superinstance are overloaded according to resource usage of the target EMA superinstance by the tenant; In the case where it is determined that the resources of the target EMA super instance are overloaded, determining whether the resources provided by the cloud platform for the target EMA super instance have reached a configured resource upper limit based on the attribute information of the target cloud service; When the resources provided by the cloud platform for the target EMA super instance do not reach the upper limit of configured resources, the target resource node is adjusted.
8. The method according to claim 7, characterized in that The method further comprises: When the resources provided by the cloud platform for the target EMA super instance reach the upper limit of configured resources, a prompt message is sent to the tenant, where the prompt message is used to indicate that the resources provided by the cloud platform for the target EMA super instance have reached the upper limit of configured resources.
9. A cloud platform, characterized in that: The cloud platform includes an elastic memory acceleration service EMAS management node and a plurality of resource nodes, wherein the resource node is used to provide at least one of computing resources and memory resources; The EMAS management node is used to provide a configuration interface, wherein the configuration interface is used to prompt the tenant to input attribute information of the target cloud service to be provided according to business requirements, wherein the attribute information includes a provision method of the target cloud service and performance configuration information of the target cloud service; and obtain the attribute information of the target cloud service from the configuration interface; Based on the attribute information, create a target elastic memory acceleration EMA super instance in a target resource node included in the multiple resource nodes, the target EMA super instance is used to provide the target cloud service for the tenant, the target resource node includes at least one resource node, and the available resources of the target resource node meet the business requirements; Based on the provision mode of the target cloud service, a management interface of the target EMA super instance is set, and the management interface is provided to the tenant.
10. The cloud platform according to claim 9, characterized in that: The target cloud service is provided in a super instance provision mode, which means that the target EMA super instance is visible to the tenant and the life cycle of the target EMA is managed by the tenant; The performance configuration information of the target cloud service includes usage type, memory capacity, capacity guarantee mode, capacity step, computing resources and bandwidth; the usage type indicates whether the target EMA super instance provides services in a mounted form, the memory capacity indicates the memory capacity of the target EMA super instance, the capacity guarantee mode indicates whether the resource nodes to which the memory resources of the target EMA super instance are distributed are variable, the capacity step indicates the memory size of each elastic memory acceleration instance EMAI included in the target EMA super instance, the computing resources indicate the computing performance of the target EMA super instance, and the bandwidth indicates the amount of data transmitted by the target EMA super instance per unit time.
11. The cloud platform according to claim 10, characterized in that: When the usage type indicates that the target EMA super instance does not provide services in a mounted form, the performance configuration information of the target cloud service also includes a latency specification and a placement strategy, wherein the latency specification indicates the access latency of the memory resources of the target EMA super instance, and the placement strategy indicates whether the memory resources and computing resources of the target EMA super instance are located on the same resource node.
12. The cloud platform according to claim 10, characterized in that: In the case where the usage type indicates that the target EMA super instance provides services in a mounted form, the performance configuration information of the target cloud service also includes an identifier, a latency specification, a placement strategy, an access strategy and a usage mode of at least one target instance, wherein the target instance refers to an instance used to mount the target EMA super instance, the latency specification indicates the access latency of the target instance to the target EMA super instance, the placement strategy indicates whether the target EMA super instance and the first instance are located on the same resource node, the first instance is one of the at least one target instance, the access policy indicates the read and write permissions of the at least one target instance to the target EMA super instance, and the usage mode indicates the memory addressing method of the target EMA super instance and the second instance, and the second instance is one of the at least one target instance.
13. The cloud platform according to claim 9, characterized in that: The target cloud service is provided in an instance-free provision mode, which means that the target EMA super instance is not visible to the tenant and the life cycle of the target EMA is not managed by the tenant; The performance configuration information of the target cloud service includes service type, performance specification, maximum number of simultaneous connections and rate cap; The service type indicates the tenant's business demand for memory resources and computing resources, the performance specification indicates the number of target EMA super instances, the maximum number of simultaneous connections indicates the number of instances that the target EMA super instance can connect to at the same time, and the rate cap indicates the upper limit of resources provided by the cloud platform to the tenant.
14. The cloud platform according to claim 9, characterized in that: The plurality of resource nodes are located in at least one resource pool; The EMAS management node is used to obtain the attribute information of the available resources of each resource node in each resource pool; based on the attribute information of the available resources of each resource node in each resource pool and the performance configuration information, determine the target resource node from the multiple resource nodes, and each resource node in the target resource node is located in the same resource pool; create an elastic memory acceleration instance EMAI in each resource node included in the target resource node to obtain one or more EMAIs; based on the one or more EMAIs, generate the target EMA super instance.
15. The cloud platform according to claim 9, characterized in that: The EMAS management node is used to determine whether the resources of the target EMA super-instance are overloaded based on the resource usage of the target EMA super-instance by the tenant; when it is determined that the resources of the target EMA super-instance are overloaded, based on the attribute information of the target cloud service, determine whether the resources provided by the cloud platform for the target EMA super-instance have reached the upper limit of configured resources; when the resources provided by the cloud platform for the target EMA super-instance have not reached the upper limit of configured resources, adjust the target resource node.
16. The cloud platform according to claim 15, characterized in that: The EMAS management node is used to send a prompt message to the tenant when the resources provided by the cloud platform for the target EMA super instance reach the configured resource upper limit, and the prompt message is used to indicate that the resources provided by the cloud platform for the target EMA super instance have reached the configured resource upper limit.
17. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, each computing device including a processor and a memory; The processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1-8.
18. A computer-readable storage medium, characterized in that: The storage medium includes computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 8.
19. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 8.
Citation Information
Cited By
Method for providing cloud service, cloud platform, and related apparatus
EP4712442A1
Method for providing cloud service, cloud platform, and related apparatus
WO2024245394A1
