Cloud server deployment method, device, electronic device and storage medium

Abstract

The present application provides a cloud server deployment method, apparatus, electronic device, and storage medium, relating to the technical field of cloud computing. The method includes: determining attribute information of a current tenant; the attribute information is used to characterize that the current tenant is a resource competing tenant or a non-resource competing tenant; in the case that it is determined based on the attribute information that the current tenant is a resource competing tenant, determining a target physical server among multiple physical servers of existing cloud servers on which resource competing tenants have been deployed; and deploying a new cloud server corresponding to the current tenant on the target physical server. In the technical solution of the present application, when deploying cloud servers for tenants, resource competing tenants are aggregated, avoiding affecting the operation of cloud servers of non-resource competing tenants, and improving the stability of the cloud computing platform.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular, to a method, device, electronic device, and storage medium for deploying cloud servers. Background Art

[0002] A cloud computing platform, also known as a cloud platform, refers to a service based on hardware resources and software resources that provides computing, network, and storage capabilities. There are scenarios where underlying physical resources are shared in a cloud platform. Multiple cloud servers of the cloud platform are deployed on the same physical server to achieve physical server sharing, which can save hardware resources. However, during the operation of cloud servers, if resource contention occurs in one of the cloud servers deployed on a physical server, it will affect the operation of other cloud servers deployed on that physical server, and further affect the stability of the cloud computing platform. Therefore, an effective method for deploying cloud servers is needed to improve the stability of the cloud computing platform. Summary of the Invention

[0003] Embodiments of this application provide a method, device, electronic device, and storage medium for deploying cloud servers to improve the stability of the cloud computing platform.

[0004] In a first aspect, embodiments of this application provide a method for deploying cloud servers, including:

[0005] Determine the attribute information of the current tenant; the attribute information is used to characterize whether the current tenant is a resource contention tenant or a non-resource contention tenant;

[0006] When it is determined based on the attribute information that the current tenant is a resource contention tenant, determine a target physical server among multiple physical servers on which a stock cloud server of the resource contention tenant has been deployed;

[0007] Deploy the new cloud server corresponding to the current tenant on the target physical server.

[0008] In a second aspect, embodiments of this application provide a device for deploying cloud servers, including:

[0009] A first determination module, configured to determine the attribute information of the current tenant; the attribute information is used to characterize whether the current tenant is a resource contention tenant or a non-resource contention tenant;

[0010] A second determination module, configured to determine a target physical server among multiple physical servers on which a stock cloud server of the resource contention tenant has been deployed when it is determined based on the attribute information that the current tenant is a resource contention tenant;

[0011] A deployment module, configured to deploy the new cloud server corresponding to the current tenant on the target physical server.

[0012] In a third aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory. When the processor executes the computer program, the method provided in any embodiment of the present application is implemented.

[0013] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. A computer program is stored in the computer-readable storage medium. When the computer program is executed by a processor, the method provided in any embodiment of the present application is implemented.

[0014] Compared with the prior art, the present application has the following advantages:

[0015] The cloud server deployment method, device, electronic device, and storage medium provided in the embodiments of the present application determine the attribute information of the current tenant; the attribute information is used to characterize that the current tenant is a resource competing tenant or a non-resource competing tenant; in the case that it is determined that the current tenant is a resource competing tenant based on the attribute information, a target physical server is determined among multiple physical servers of the stock cloud servers where resource competing tenants have been deployed; and the new cloud server corresponding to the current tenant is deployed in the target physical server. In the technical solution of the present application, when deploying cloud servers for tenants, resource competing tenants are aggregated, avoiding affecting the operation of the cloud servers of non-resource competing tenants, and improving the stability of the cloud computing platform.

[0016] The above summary is only for the purpose of the specification and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of the present application will be readily apparent by reference to the drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In the drawings, unless otherwise specified, the same reference numerals throughout the several views denote the same or similar components or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed in the present application and should not be regarded as limiting the scope of the present application.

[0018] Figure 1 It is a schematic diagram of the system architecture of the cloud server deployment method provided in an embodiment of the present application;

[0019] Figure 2 It is a flowchart of the cloud server deployment method provided in an embodiment of the present application;

[0020] Figure 3 It is a schematic diagram of the cloud server deployment method provided in an embodiment of the present application;

[0021] Figure 4 It is a schematic diagram of the cloud server deployment method provided in an embodiment of the present application;

[0022] Figure 5 Schematic diagram of a cloud server deployment device provided by an embodiment of the present application;

[0023] Figure 6 Block diagram of an electronic device for implementing the embodiment of the present application. Detailed implementation manners

[0024] In the following, only some exemplary embodiments are simply described. As those skilled in the art can recognize, the described embodiments can be modified in various different ways without departing from the spirit or scope of the present application. Therefore, the drawings and the description are considered to be exemplary in nature rather than restrictive.

[0025] To facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be combined with the technical solutions of the embodiments of the present application in any way as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0026] To more clearly show the cloud server deployment method provided in the embodiments of the present application, the application scenarios that can be used to implement this method are introduced first.

[0027] The technical solutions of the present application can be applied to the scenario of allocating physical servers to multiple cloud servers of a cloud computing platform. Among them, the cloud server can be a virtual machine or also called an instance. Tenants can include people, organizations, institutions, etc. Tenants can rent multiple cloud servers on the cloud computing platform. The cloud servers are used to provide computing services for tenants. Multiple cloud servers can be deployed in different physical servers, and multiple cloud servers can be deployed in the same physical server. Figure 1 Schematic diagram of the system architecture of the cloud server deployment method provided by an embodiment of the present application, as Figure 1As shown, the cloud computing platform manages multiple cloud servers and multiple physical servers. The cloud servers include: Cloud Server 1, Cloud Server 2, Cloud Server 3... Cloud Server n; the physical servers include: Physical Server 1, Physical Server 2... Physical Server m, where m and n can be any integers. The cloud servers are respectively deployed on the physical servers. If a new cloud server is to be started for the current tenant, first determine the attribute information of the current tenant. The attribute information is used to represent whether the current tenant is a resource competing tenant or a non-resource competing tenant. In the case where it is determined based on the attribute information that the current tenant is a resource competing tenant, determine the target physical server among the multiple physical servers on which the existing cloud servers of the resource competing tenants are deployed, and deploy the new cloud server corresponding to the current tenant on the target physical server. In an example, Cloud Server 1 and Cloud Server 2 corresponding to the current tenant are deployed in Physical Server 1, and Cloud Server 3 is deployed in Physical Server 2. If the current tenant is a resource competing tenant, since the number of existing cloud servers of the resource competing tenants deployed on Physical Server 1 is relatively large, the new existing server of the current tenant is deployed in Physical Server 1; if the current tenant is a non-resource competing tenant, since there are no existing cloud servers of the resource competing tenants deployed on Physical Server 2 and the number of existing cloud servers of the non-resource competing tenants deployed is relatively small, the new existing server of the current tenant is deployed in Physical Server 2.

[0028] The embodiments of the present application provide a method for deploying cloud servers. Figure 2 It is a flowchart of the method for deploying cloud servers according to an embodiment of the present application. This method can be applied to a cloud server deployment device, and this device can be deployed in a server or other processing devices. In some possible implementation manners, this method can also be implemented by a processor calling computer-readable instructions stored in a memory. As Figure 2 shown, this method includes:

[0029] Step S201, determine the attribute information of the current tenant; the attribute information is used to represent whether the current tenant is a resource competing tenant or a non-resource competing tenant.

[0030] In this embodiment, the execution subject can be the server of the meta-computing platform. Among them, a tenant can be an object to which the cloud computing platform provides computing services. A tenant can rent multiple cloud servers on the cloud computing platform, and the cloud servers are used to provide computing services for the tenant. The cloud computing platform can deploy cloud servers that meet different requirements for the tenant according to different application requirements of the tenant in the physical servers.

[0031] Among them, there can be multiple specific ways to determine the attribute information of the current tenant, and the embodiments of this application do not limit this. The attribute information is used to characterize that the current tenant is a resource contention tenant or a non-resource contention tenant. A resource contention tenant can be a tenant for which it is evaluated that resource contention may occur. The cloud server corresponding to the resource contention tenant may cause sudden power consumption of the physical server where it is located, or abnormal cloud server traffic, etc. The resource contention of the cloud server corresponding to the resource contention tenant may cause other cloud servers on the physical server where it is located to not operate properly.

[0032] Step S202, in the case where it is determined based on the attribute information that the current tenant is a resource contention tenant, determine a target physical server among multiple physical servers on which the stock cloud servers of the resource contention tenant have been deployed.

[0033] For resource contention tenants and non-resource contention tenants, different methods are used to determine the target physical server among multiple physical servers. For resource contention tenants, when deploying cloud servers, aggregated deployment is performed. Among multiple physical servers, determine the physical servers on which the stock cloud servers of the resource contention tenant have been deployed, and among these physical servers, determine the target physical server.

[0034] Step S203, deploy the new cloud server corresponding to the current tenant on the target physical server.

[0035] Enable at least one cloud server on the target physical server as the new cloud server corresponding to the current tenant.

[0036] In the related art, a contention scheduling domain is divided, and some physical servers are defined as a separate scheduling domain for contending cloud servers. The cloud servers corresponding to contending users are preferentially scheduled into the contention scheduling domain. The contention scheduling domain needs to be planned in advance and will cause resource waste when there is no contention. In other related technologies, after the cloud server contention corresponding to the tenant occurs, the physical server where the cloud server is located is locked, and at the same time, other cloud servers are migrated. This belongs to ex post governance and has migration costs. At the same time, the influence range of the cloud servers of contending users is uncontrollable.

[0037] The cloud server deployment method provided by the embodiments of the present application does not require advance planning of the scheduling domain. When deploying a newly added cloud server for a tenant, the attribute information of the current tenant is determined; in the case that the current tenant is determined to be a resource contention tenant based on the attribute information, a target physical server is determined among multiple physical servers on which the stock cloud servers of the resource contention tenant have been deployed; and the newly added cloud server corresponding to the current tenant is deployed on the target physical server. In the technical solution of the present application, when deploying cloud servers for tenants, the resource contention tenants are aggregated, which avoids affecting the operation of the cloud servers of non-resource contention tenants. Moreover, it avoids the resource waste caused by advance planning of the scheduling domain and the migration cost after the contention behavior occurs, and can improve the stability of the cloud computing platform.

[0038] For tenants with different attribute information, the specific implementation manner of determining the target physical server among multiple physical servers is shown in the following embodiments:

[0039] In a possible implementation manner, step S202 of determining a target physical server among multiple physical servers on which the stock cloud servers of the resource contention tenant have been deployed includes:

[0040] Among multiple physical servers, the physical server with the top-ranked number of stock cloud servers on which the resource contention tenant has been deployed is used as the target physical server.

[0041] In practical applications, if the current tenant is a resource contention tenant, that is, resource contention has occurred or may occur for the current tenant before, the physical servers are sorted according to the number of stock cloud servers of the resource contention tenant, and the physical server with the top rank is used as the target physical server.

[0042] Optionally, the physical server with the largest number of stock cloud servers on which the resource contention tenant has been deployed is used as the target physical server.

[0043] In this embodiment, aggregating the cloud servers of the resource contention tenants onto one or several physical servers for deployment can prevent the cloud servers of the resource contention tenants from affecting the operation of the cloud servers corresponding to non-resource contention tenants and narrow the scope of resource contention.

[0044] In a possible implementation manner, step S202 of determining a target physical server among multiple physical servers on which the stock cloud servers of the resource contention tenant have been deployed includes:

[0045] Among multiple physical servers on which the stock cloud servers of the current tenant have been deployed, the target physical server is determined.

[0046] In practical applications, for resource-competing tenants, in addition to aggregating and deploying cloud servers of tenants with the same attribute information in the aggregation manner in the above embodiments, aggregation can also be further performed according to tenants. Among multiple physical servers where the cloud servers of resource-competing tenants have been deployed, a physical server with a larger number of existing cloud servers of the current tenant is preferentially selected as the target physical server to continue deploying the cloud servers of the current tenant.

[0047] In a possible implementation manner, the method further includes:

[0048] In the case where it is determined based on the attribute information that the current tenant is a non-resource-competing tenant, among multiple physical servers where no cloud servers of resource-competing tenants are deployed, a physical server with a relatively lower ranking in terms of the number of existing cloud servers of non-resource-competing tenants deployed thereon is used as the target physical server.

[0049] In practical applications, if the current tenant is a non-resource-competing tenant, that is, there has been no resource competition situation for the current tenant before or the possibility of a resource competition situation is relatively small, then the physical servers where no cloud servers of resource-competing tenants are deployed are sorted according to the number of existing cloud servers corresponding to non-competing tenants, and the physical server with a relatively lower ranking is used as the target physical server. Among them, the physical servers where no cloud servers of resource-competing tenants are deployed can be physical servers where neither cloud servers of resource-competing tenants nor cloud servers of non-resource-competing tenants are deployed, that is, they can be idle physical servers where no cloud servers are deployed. The physical servers where no cloud servers of resource-competing tenants are deployed can also be physical servers where only cloud servers of non-resource-competing tenants are deployed.

[0050] Optionally, a physical server with the smallest number of existing cloud servers of non-resource-competing tenants deployed thereon is used as the target physical server.

[0051] In this embodiment, the cloud servers of non-resource-competing tenants are deployed dispersedly, that is, they are deployed on multiple physical servers.

[0052] Figure 3 It is a schematic diagram of the cloud server deployment method provided by an embodiment of the present application; as Figure 3As shown in the figure, VM represents the cloud server corresponding to each tenant, and the inventory cloud servers of the tenant are deployed on each physical server. When deploying cloud servers for non-resource-competing tenants, decentralized deployment is carried out, and the newly added cloud servers are dispersed to different physical servers for deployment. These physical servers have not deployed the inventory cloud servers of this tenant before. When deploying cloud servers for resource-competing tenants, centralized deployment is carried out. For each newly added cloud server, select the physical server with the largest number of inventory cloud servers of the resource-competing tenant as the target physical server, and deploy the newly added cloud server in the target physical server, so as to aggregate the cloud servers of the resource-competing tenant to the same physical server. Aggregating the cloud servers of the resource-competing tenant to one physical server reduces the scope of resource competition and avoids the cloud servers of the resource-competing tenant from affecting the operation of the cloud servers of the non-resource-competing tenant.

[0053] In a possible implementation, the cloud server deployment method further includes:

[0054] Based on the historical operation information of the cloud servers corresponding to the inventory tenants, determine the attribute information of the inventory tenants;

[0055] The historical operation information includes at least one of the following:

[0056] The power consumption, network traffic, central processing unit (CPU) occupancy rate, or memory occupancy rate of the physical server where it is located.

[0057] In practical applications, obtaining the historical operation information of the cloud servers of the inventory tenants of the cloud computing platform includes one or more of the power consumption of the physical server where the cloud server is located, the network traffic of the cloud server, the central processing unit (CPU) occupancy rate of the cloud server, or the memory occupancy rate. According to the historical operation information of the cloud servers corresponding to the inventory tenants, it can be determined whether there has been a competition situation for the cloud servers corresponding to the inventory tenants. If there has been a resource competition situation, the tenant corresponding to the cloud server where the resource competition occurred is the resource-competing tenant. Among them, the network traffic of the cloud server includes the uplink traffic and downlink traffic of the cloud server, etc.

[0058] In an example, according to the historical operation information of the cloud server B1 of tenant A1 within one month, it is found that the cloud server B1 has caused the power consumption of the physical server where it is located to increase significantly in a short period of time, then it is determined that the cloud server B1 has had a resource competition, and tenant A1 is determined as the resource-competing tenant.

[0059] In a possible implementation, step S201, determining the attribute information of the current tenant, includes:

[0060] Obtain the first feature information of the newly added cloud server corresponding to the current tenant, and the second feature information of the cloud server corresponding to the resource contention tenant among the existing tenants;

[0061] Match the first feature information with the second feature information, and determine the attribute information of the current tenant according to the matching result.

[0062] In practical applications, when allocating newly added cloud servers to tenants, extract the feature information of the newly added cloud server corresponding to the current tenant, that is, the first feature information. After pre-determining the resource contention tenants among the existing tenants, pre-extract the feature information of the cloud server corresponding to the resource contention tenant, that is, the second feature information, and a tenant contention portrait can be generated based on the feature information of the cloud server corresponding to the resource contention tenant. Among them, the first feature information and the second feature information can be the attribute features that the cloud server has. For example, the user, industry, region, product, time period, etc. corresponding to the cloud server.

[0063] Match the first feature information with the user contention portrait. That is to say, match the first feature information with the second feature information. If one or more features in the first feature information match the user contention portrait, it indicates that the current tenant is a resource contention tenant; otherwise, it is a non-resource contention tenant.

[0064] Among them, the current tenant can be a newly added tenant or an existing tenant. If it is a newly added tenant, it can be determined whether the current tenant is a resource contention tenant through the matching results of features such as industry, region, product, and time period; if the current tenant is an existing tenant, it is determined whether the current tenant is a resource contention tenant through the matching results of features such as user, industry, region, product, and time period.

[0065] Optionally, if the current tenant is a newly added tenant and the number of existing cloud servers corresponding to the current tenant deployed in the physical server is zero, the target physical server can be determined according to the attribute information of the current tenant, and the cloud server corresponding to the current tenant is deployed in the target physical server. Among them, the target physical server can be a pre-configured specified physical server.

[0066] In a possible implementation manner, the cloud server deployment method further includes:

[0067] Determine the attribute information of the existing tenants according to a preset time period, and update the attribute information of the existing tenants.

[0068] In practical applications, according to a preset time period, based on the historical operation information of the cloud servers corresponding to the existing tenants in the cloud computing platform, the attribute information of the existing tenants can be determined, the attribute information can be updated, and according to the updated attribute information, the deployment method of the cloud servers can be adjusted to improve the usage experience of the tenants' cloud servers.

[0069] For example, according to the historical operation information of the cloud server corresponding to tenant A2 from January to March of the current year, it is determined that tenant A2 is a tenant competing for resources. However, according to the historical operation information of tenant A2's cloud server from April to June of the current year, it is found that there is no resource competition situation. Then, in July of the current year, the attribute information of tenant A2 can be updated, and the attribute information of tenant A2 can be updated to a non-resource-competing tenant. When deploying the cloud server corresponding to tenant A2, the cloud server can be deployed according to the deployment method of the cloud server for non-resource-competing tenants.

[0070] It should be noted that the preset time period can be configured according to specific needs, and this application does not make any limitations in this regard.

[0071] In a possible implementation manner, step S202, determining a target physical server among multiple physical servers of the existing cloud servers that have already deployed resource-competing tenants, includes:

[0072] Based on the resource type in contention in the attribute information, among the multiple physical servers of the existing cloud servers that have already deployed resource-competing tenants, the physical server that deploys the cloud server corresponding to the contended resource type is used as the target physical server.

[0073] In practical applications, when extracting the characteristics of the cloud servers corresponding to resource-competing users and generating a resource competition portrait of resource-competing tenants, a power consumption competition portrait, a network traffic competition portrait, etc. can be generated according to the contended resource type. The attribute information may include the contended resource type. Cloud servers corresponding to resource-competing users of different types are deployed in the physical servers corresponding to the cloud servers of the corresponding contended resource types, which can make the cloud servers corresponding to tenants with the same resource competition type aggregated together, reduce the dimension of physical server damage caused by resource competition, and facilitate taking corresponding measures for disaster recovery processing.

[0074] In a possible implementation manner, deploying the newly added cloud server corresponding to the current tenant in the target physical server includes:

[0075] Obtain the specification information of the newly added cloud server;

[0076] Deploy a cloud server corresponding to the specification information in the target physical server as the newly added cloud server corresponding to the current tenant.

[0077] Among them, the specification information of the cloud server may include CPU specifications, memory size, disk space size, network bandwidth, security policies (for example, externally open ports), etc. According to the specification information of the cloud server purchased by the tenant, the corresponding cloud server is started in the target physical server to provide computing services for the tenant.

[0078] To make the specific implementation process of the technical solution of this application clearer, the process of the technical solution of this application will be introduced in detail through a specific embodiment below. Figure 4 It is a schematic diagram of the cloud server deployment method provided by an embodiment of this application; in this embodiment, an instance represents a cloud server. This embodiment includes three modules: a scheduling module, an instance contention information collection module, and a user contention portrait extraction module. When allocating a new cloud server for a tenant (such as "create instance" shown in the figure), the scheduling module is used to obtain the characteristic information of the new cloud server corresponding to the tenant, and match the characteristic information with the user contention portrait of the users competing for the stock resources. If the match is successful (such as "portrait match" shown in the figure), it indicates that the current tenant is a resource competing tenant, and the physical server with the largest number of stock cloud servers deployed with the resource competing tenant is used as the target physical server (such as "select physical server" shown in the figure), and the new physical server corresponding to the current tenant is deployed in the target physical server (such as "create instance" shown in the figure). Thus, the scattering is reduced and the aggregation is improved. The instance contention information collection module is used to monitor the running status of the cloud servers running on the cloud computing platform and collect abnormal information, including the historical running information of the cloud servers of the resource competing tenants. The user contention portrait extraction module is used to analyze and summarize the historical running information of the cloud servers of the resource competing tenants, extract common features, such as users, regions, products, time periods, etc., and generate different user contention portraits according to different types of resources being contended, for example, power consumption contention portraits, network contention portraits, etc., for the scheduling module to use.

[0079] Corresponding to the application scenario and method of the method provided by the embodiment of this application, the embodiment of this application also provides a cloud server deployment device. As Figure 5 shown, the cloud server deployment device may include:

[0080] A first determination module 501, configured to determine the attribute information of the current tenant; the attribute information is used to characterize whether the current tenant is a resource competing tenant or a non-resource competing tenant;

[0081] A second determination module 502, configured to determine a target physical server among multiple physical servers on which stock cloud servers of resource competing tenants have been deployed when it is determined based on the attribute information that the current tenant is a resource competing tenant;

[0082] A deployment module 503, configured to deploy newly added cloud servers corresponding to the current tenant in a target physical server.

[0083] The cloud server deployment device provided by the embodiments of the present application can determine the attribute information of the current tenant when deploying newly added cloud servers for the tenant without prior planning of the scheduling domain; in the case where it is determined based on the attribute information that the current tenant is a resource contention tenant, determine a target physical server among multiple physical servers where the stock cloud servers of the resource contention tenant have been deployed; and deploy the newly added cloud servers corresponding to the current tenant in the target physical server. In the technical solution of the present application, when deploying cloud servers for a tenant, resource contention tenants are aggregated, which avoids affecting the operation of cloud servers of non-resource contention tenants. Moreover, it avoids the resource waste caused by prior planning of the scheduling domain and the migration cost after contention occurs, and can improve the stability of the cloud computing platform.

[0084] In a possible implementation manner, the second determination module 502 is specifically configured to:

[0085] Among multiple physical servers, use the physical server with the top-ranked number of stock cloud servers where the resource contention tenant has been deployed as the target physical server.

[0086] In a possible implementation manner, the second determination module 502 is further configured to:

[0087] In the case where it is determined based on the attribute information that the current tenant is a non-resource contention tenant, among multiple physical servers where the cloud servers of the resource contention tenant have not been deployed, use the physical server with the bottom-ranked number of stock cloud servers where the non-resource contention tenant has been deployed as the target physical server.

[0088] In a possible implementation manner, the second determination module 502 is specifically configured to:

[0089] Among multiple physical servers where the stock cloud servers of the current tenant have been deployed, determine the target physical server.

[0090] In a possible implementation manner, the cloud server deployment device further includes a third determination module, configured to:

[0091] Determine the attribute information of the stock tenant based on the historical operation information of the cloud servers corresponding to the stock tenant;

[0092] The historical operation information includes at least one of the following:

[0093] Power consumption, network traffic, central processing unit (CPU) occupancy rate, or memory occupancy rate of the physical server where it is located.

[0094] In a possible implementation, the first determination module 501 is specifically configured to:

[0095] Obtain first feature information of the newly added cloud servers corresponding to the current tenant, and second feature information of the cloud servers corresponding to the resource contention tenants among the existing tenants;

[0096] Match the first feature information with the second feature information, and determine the attribute information of the current tenant according to the matching result.

[0097] In a possible implementation, the apparatus further includes an attribute update module, which is configured to:

[0098] Determine the attribute information of the existing tenants according to a preset time period, and update the attribute information of the existing tenants.

[0099] In a possible implementation, the second determination module 502 is specifically configured to:

[0100] Based on the resource types in contention in the attribute information, among the multiple physical servers of the existing cloud servers where the resource contention tenants have been deployed, the physical server that deploys the cloud servers corresponding to the resource types in contention is used as the target physical server.

[0101] In a possible implementation, the deployment module 503 is specifically configured to:

[0102] Obtain the specification information of the newly added cloud servers;

[0103] Deploy the cloud servers corresponding to the specification information in the target physical server as the newly added cloud servers corresponding to the current tenant.

[0104] For the functions of the modules in each device of the embodiments of the present application, reference may be made to the corresponding descriptions in the above methods, and they have the corresponding beneficial effects, which will not be elaborated here.

[0105] Figure 6 It is a block diagram of an electronic device for implementing the embodiments of the present application. As Figure 6 shown, the electronic device includes: a memory 610 and a processor 620. The memory 610 stores a computer program that can run on the processor 620. When the processor 620 executes the computer program, the method in the above embodiments is implemented. The number of the memory 610 and the processor 620 can be one or more.

[0106] The electronic device further includes:

[0107] A communication interface 630, which is used to communicate with external devices and perform data interaction and transmission.

[0108] If the memory 610, the processor 620, and the communication interface 630 are implemented independently, the memory 610, the processor 620, and the communication interface 630 can be interconnected through a bus and communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. This bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 only a thick line is used to represent it in Figure 6 , but it does not mean that there is only one bus or one type of bus.

[0109] Optionally, in a specific implementation, if the memory 610, the processor 620, and the communication interface 630 are integrated on a single chip, the memory 610, the processor 620, and the communication interface 630 can communicate with each other through an internal interface.

[0110] The embodiments of the present application provide a computer-readable storage medium that stores a computer program, and when the program is executed by a processor, the methods provided in the embodiments of the present application are implemented.

[0111] The embodiments of the present application also provide a chip that includes a processor for calling and running instructions stored in a memory, so that a communication device installed with the chip executes the methods provided in the embodiments of the present application.

[0112] The embodiments of the present application also provide a chip that includes: an input interface, an output interface, a processor, and a memory. The input interface, the output interface, the processor, and the memory are connected through an internal connection path. The processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the methods provided in the embodiments of the application.

[0113] It should be understood that the above-mentioned processor can be a Central Processing Unit (CPU), or it can also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc. It is worth noting that the processor can be a processor that supports the Advanced RISC Machines (ARM) architecture.

[0114] Further, optionally, the above-mentioned memory can include a read-only memory and a random access memory, and can also include a non-volatile random access memory. The memory can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can include a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. The volatile memory can include a Random Access Memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available. For example, Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0115] 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 program instructions are loaded and executed on a computer, the processes or functions according to the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. 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.

[0116] In the description of this specification, the descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or more embodiments or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0117] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" can explicitly or implicitly include at least one of the features. In the description of the present application, "a plurality" means two or more unless otherwise specifically defined.

[0118] Any process or method description represented in the flowchart or described in other ways herein can be understood as representing a module, segment, or part of code including one or more executable instructions for implementing a specific logical function or process. And the scope of the preferred embodiments of the present application includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in the reverse order according to the involved functions, rather than in the order shown or discussed.

[0119] The logic and / or steps represented in the flowchart or described in other ways herein, for example, can be considered as a sequenced list of executable instructions for implementing a logical function, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or in combination with these instruction execution systems, apparatus, or devices.

[0120] It should be understood that each part of the present application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the method in the above embodiments can be completed by a program instructing relevant hardware. The program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0121] In addition, in each embodiment of the present application, each functional unit can be integrated in a processing module, or each unit can exist physically alone, or two or more units can be integrated in a module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a magnetic disk, an optical disk, etc.

[0122] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of various changes or substitutions, and these should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A cloud server deployment method, characterized in that, The method includes: Determining the attribute information of the current tenant; the attribute information is used to characterize that the current tenant is a resource competing tenant or a non-resource competing tenant; In the case that it is determined based on the attribute information that the current tenant is a resource competing tenant, determining a target physical server among multiple physical servers where the inventory cloud servers with resource competing tenants are already deployed; the physical servers are deployed with the inventory cloud servers of the tenant; in the case that it is determined based on the attribute information that the current tenant is a non-resource competing tenant, among the multiple physical servers where the cloud servers without resource competing tenants are deployed, taking the physical server with a relatively lower ranking in terms of the number of inventory cloud servers deploying non-resource competing tenants as the target physical server; Deploying the new cloud server corresponding to the current tenant in the target physical server.

2. The method according to claim 1, characterized in that, The determining of the target physical server among multiple physical servers where the inventory cloud servers with resource competing tenants are already deployed includes: Among the multiple physical servers, taking the physical server with a relatively higher ranking in terms of the number of inventory cloud servers deploying resource competing tenants as the target physical server.

3. The method according to claim 1, characterized in that, The determining of the target physical server among multiple physical servers where the inventory cloud servers with resource competing tenants are already deployed includes: Determining a target physical server among multiple physical servers where the inventory cloud servers of the current tenant are already deployed.

4. The method according to claim 1 or 2, characterized in that The method further includes: Determining the attribute information of the inventory tenant based on the historical operation information of the cloud servers corresponding to the inventory tenant; The historical operation information includes at least one of the following: Power consumption, network traffic, central processing unit (CPU) occupancy rate, or memory occupancy rate of the physical server where it is located.

5. The method according to claim 4, characterized in that The determining of the attribute information of the current tenant includes: Obtaining the first feature information of the new cloud server corresponding to the current tenant, and the second feature information of the cloud servers corresponding to the resource competing tenants among the inventory tenants; Matching the first feature information with the second feature information, and determining the attribute information of the current tenant according to the matching result.

6. The method according to claim 4, characterized in that The method further includes: Determining the attribute information of the inventory tenant according to a preset time period, and updating the attribute information of the inventory tenant.

7. The method according to claim 1 or 2, characterized in that, The determining of the target physical server among multiple physical servers where the inventory cloud servers with resource competing tenants are already deployed includes: Based on the resource type being competed for in the attribute information, among multiple physical servers where the inventory cloud servers with resource competing tenants are already deployed, taking the physical server that deploys the cloud servers corresponding to the resource type being competed for as the target physical server.

8. The method according to claim 1 or 2, characterized in that, The deploying of the new cloud server corresponding to the current tenant in the target physical server includes: Obtaining the specification information of the new cloud server; Deploying the cloud server corresponding to the specification information in the target physical server as the new cloud server corresponding to the current tenant.

9. A cloud server deployment device, characterized in that, The device includes: A first determining module, configured to determine the attribute information of the current tenant; the attribute information is used to characterize that the current tenant is a resource competing tenant or a non-resource competing tenant; A second determination module, configured to, when determining, based on the attribute information, that the current tenant is a resource contention tenant, determine a target physical server from multiple physical servers on which there are existing cloud servers of the resource contention tenant deployed; a physical server has existing cloud servers of a tenant deployed thereon; and when determining, based on the attribute information, that the current tenant is not a resource contention tenant, from multiple physical servers on which there are no cloud servers of the resource contention tenant deployed, use, as the target physical server, a physical server on which the number of existing cloud servers of the non-resource contention tenant deployed is ranked relatively low. A deployment module, configured to deploy, in the target physical server, a new cloud server corresponding to the current tenant.

10. An electronic device, comprising a memory, a processor, and a computer program stored on the memory, where the processor, when executing the computer program, implements the method according to any one of claims 1-8.

11. A computer-readable storage medium, in which a computer program is stored, where the computer program, when executed by a processor, implements the method according to any one of claims 1-8.

Images