CN114756380A - Cloud server deployment method and device, electronic equipment and storage medium - Google Patents
Cloud server deployment method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114756380A CN114756380A CN202210553965.8A CN202210553965A CN114756380A CN 114756380 A CN114756380 A CN 114756380A CN 202210553965 A CN202210553965 A CN 202210553965A CN 114756380 A CN114756380 A CN 114756380A
- Authority
- CN
- China
- Prior art keywords
- tenant
- resource
- cloud server
- cloud
- servers
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a cloud server deployment method and device, electronic equipment and a storage medium, and relates to the technical field of cloud computing. The method comprises the following steps: determining attribute information of a current tenant; the attribute information is used for representing that the current tenant is a resource contention tenant or a non-resource contention tenant; determining a target physical server in a plurality of physical servers of a stock cloud server which is already deployed with a resource contending tenant under the condition that the current tenant is determined to be the resource contending tenant based on the attribute information; and deploying a newly-added cloud server corresponding to the current tenant in the target physical server. According to the technical scheme, when the tenants are deployed with the cloud servers, the tenants with the resource contention are aggregated, the cloud servers which do not influence the tenants with the resource contention are prevented from running, and the stability of the cloud computing platform can be improved.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a cloud server deployment method and apparatus, an electronic device, and a storage medium.
Background
The cloud computing platform is also called a cloud platform, and is a service based on hardware resources and software resources, and provides computing, network and storage capabilities. The cloud platform has a scene of sharing underlying physical resources, and a plurality of cloud servers of the cloud platform are deployed on the same physical server to realize physical server sharing, so that hardware resources can be saved. However, in the operation process of the cloud servers, if a resource contention situation occurs in one cloud server deployed in a physical server, the operation of other cloud servers deployed in the physical server may be affected, and thus the stability of the cloud computing platform is affected. Therefore, an effective cloud server deployment method is needed to improve the stability of the cloud computing platform.
Disclosure of Invention
The embodiment of the application provides a cloud server deployment method and device, electronic equipment and a storage medium, so as to improve the stability of a cloud computing platform.
In a first aspect, an embodiment of the present application provides a cloud server deployment method, including:
determining attribute information of a current tenant; the attribute information is used for representing that the current tenant is a resource dispute tenant or a non-resource dispute tenant;
determining a target physical server in a plurality of physical servers of a stock cloud server which is already deployed with a resource contention tenant under the condition that the current tenant is determined to be the resource contention tenant based on the attribute information;
and deploying a newly-added cloud server corresponding to the current tenant in the target physical server.
In a second aspect, an embodiment of the present application provides a cloud server deployment apparatus, including:
the first determining module is used for determining the attribute information of the current tenant; the attribute information is used for representing that the current tenant is a resource dispute tenant or a non-resource dispute tenant;
the second determining module is used for determining a target physical server in a plurality of physical servers of the stock cloud server which is already deployed with the resource contention tenant under the condition that the current tenant is determined to be the resource contention tenant based on the attribute information;
and the deployment module is used for deploying the newly-added cloud server corresponding to the current tenant in the target physical server.
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, where the processor, when executing the computer program, implements the method provided in any embodiment of the present application.
In a fourth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the method provided in any embodiment of the present application.
Compared with the prior art, the method has the following advantages:
according to the cloud server deployment method and device, the electronic equipment and the storage medium, the attribute information of the current tenant is determined; the attribute information is used for representing that the current tenant is a resource dispute tenant or a non-resource dispute tenant; determining a target physical server in a plurality of physical servers of a stock cloud server which is already deployed with a resource contention tenant under the condition that the current tenant is determined to be the resource contention tenant based on the attribute information; and deploying a newly-added cloud server corresponding to the current tenant in the target physical server. According to the technical scheme, when the tenants are deployed with the cloud servers, the tenants with the resource contention are aggregated, the cloud servers which do not influence the tenants with the resource contention are prevented from running, and the stability of the cloud computing platform can be improved.
The foregoing summary is provided for the purpose of description only 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 following detailed description.
Drawings
In the drawings, like reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily to scale. It is appreciated that these drawings depict only some embodiments in accordance with the disclosure and are therefore not to be considered limiting of its scope.
Fig. 1 is a schematic diagram of a system architecture of a cloud server deployment method according to an embodiment of the present application;
fig. 2 is a flowchart of a cloud server deployment method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a cloud server deployment method according to an embodiment of the present application;
fig. 4 is a schematic diagram of a cloud server deployment method according to an embodiment of the present application;
fig. 5 is a schematic diagram of a cloud server deployment apparatus according to an embodiment of the present application;
FIG. 6 is a block diagram of an electronic device used to implement embodiments of the present application.
Detailed Description
In the following, only certain exemplary embodiments are briefly described. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present application. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.
For convenience of understanding of technical solutions of the embodiments of the present application, the following description is provided for related technologies of the embodiments of the present application, and the following related technologies may be arbitrarily combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.
In order to more clearly show the cloud server deployment method provided in the embodiment of the present application, an application scenario that can be used to implement the method is first introduced.
The technical scheme can be applied to a scene of distributing physical servers for a plurality of cloud servers of a cloud computing platform, wherein the cloud servers can be virtual machines and can also be called as instances. The tenant can comprise people, organizations and the like, the tenant can rent a plurality of cloud servers on the cloud computing platform, the cloud servers are used for providing computing services for the tenant, the cloud servers can be deployed in different physical servers, and the cloud servers can be deployed in the same physical server. Fig. 1 is a schematic diagram of a system architecture of a cloud server deployment method provided in an embodiment of the present application, and as shown in fig. 1, a cloud computing platform manages a plurality of cloud servers and a plurality of physical servers, where each cloud server includes: cloud servers 1, 2, 3 …, and n; the physical server includes: physical server 1, physical server 2 … physical server m, where m and n may be any integer. The cloud servers are respectively deployed on the physical servers. If a new cloud server needs to be started for a current tenant, firstly, attribute information of the current tenant is determined, the attribute information is used for representing that the current tenant is a resource-contended tenant or a non-resource-contended tenant, under the condition that the current tenant is determined to be the resource-contended tenant based on the attribute information, a target physical server is determined in a plurality of physical servers of stock cloud servers of the resource-contended tenant, and a newly-added cloud server corresponding to the current tenant is deployed in the target physical server. In one example, a cloud server 1 and a cloud server 2 corresponding to a current tenant are deployed in a physical server 1, a cloud server 3 is deployed in the physical server 2, and if the current tenant is a resource robbing tenant, because the number of stock cloud servers of the resource robbing tenant deployed by the physical server 1 is large, a newly added stock server of the current tenant is deployed in the physical server 1; if the current tenant is a non-resource-contending tenant, because the physical server 2 does not deploy the stock cloud servers of the resource-contending tenant and the number of the deployed stock cloud servers of the non-resource-contending tenant is small, the newly-added stock servers of the current tenant are deployed in the physical server 2.
An embodiment of the present application provides a cloud server deployment method, and fig. 2 is a flowchart of the cloud server deployment method according to the embodiment of the present application, where the method may be applied to a cloud server deployment device, and the device may be deployed in a server or other processing devices. In some possible implementations, the method may also be implemented by a processor calling computer readable instructions stored in a memory. As shown in fig. 2, the method includes:
step S201, determining attribute information of a current tenant; the attribute information is used for representing that the current tenant is a resource contention tenant or a non-resource contention tenant.
In this embodiment, the execution subject may be a server of the meta-computing platform. The tenant can be an object for providing computing service by the cloud computing platform, the tenant can rent a plurality of cloud servers on the cloud computing platform, the cloud servers are used for providing computing service for the tenant, and the cloud computing platform can provide cloud servers meeting different requirements for the tenant according to different application requirements of the tenant and deploy the cloud servers in the physical servers.
The specific manner of determining the attribute information of the current tenant may be various, and this is not limited in the embodiment of the present application. The attribute information is used for representing that the current tenant is a resource dispute tenant or a non-resource dispute tenant, the resource dispute tenant may be an evaluated tenant which may have resource dispute, a cloud server corresponding to the resource dispute tenant may cause sudden power consumption of the physical server where the resource dispute tenant is located, or cloud server traffic is abnormal, and the like, and the resource dispute of the cloud server corresponding to the resource dispute tenant may cause that other cloud servers of the physical server where the resource dispute is located may not operate normally.
Step S202, under the condition that the current tenant is determined to be the resource robbery tenant based on the attribute information, a target physical server is determined in a plurality of physical servers of the stock cloud server which is already deployed with the resource robbery tenant.
And respectively determining a target physical server in a plurality of physical servers in different modes for the tenants with resource contention and the tenants without resource contention. For the tenant with the resource contention, aggregation deployment is carried out when the cloud servers are deployed, the physical servers of the stock cloud servers where the tenant with the resource contention is deployed are determined in the plurality of physical servers, and the target physical server is determined in the physical servers.
Step S203, deploying a newly added cloud server corresponding to the current tenant in the target physical server.
And starting at least one cloud server in the target physical server to serve as a newly-added cloud server corresponding to the current tenant.
In the related technology, a contention and preemption scheduling domain is divided, part of physical servers are defined as scheduling domains of single contention and preemption cloud servers, the cloud servers corresponding to contention and preemption users are preferentially scheduled in the contention and preemption scheduling domains, the contention and preemption scheduling domains need to be planned in advance, and resource waste can be caused when no contention and preemption exist. 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 other cloud servers are migrated at the same time, so that the problem of post treatment is solved, the migration cost is high, and the influence range of the cloud server contending for the user is uncontrollable.
According to the cloud server deployment method provided by the embodiment of the application, the attribute information of the current tenant is determined when the newly-added cloud server of the tenant is deployed without planning a scheduling domain in advance; determining a target physical server in a plurality of physical servers of a stock cloud server which is already deployed with a resource contending tenant under the condition that the current tenant is determined to be the resource contending tenant based on the attribute information; and deploying a newly-added cloud server corresponding to the current tenant in the target physical server. According to the technical scheme, when the tenants are deployed with the cloud servers, the tenants with the resource contention are aggregated, the cloud servers which do not influence the tenants with the resource contention are prevented from running, in addition, the resource waste caused by the fact that scheduling domains are planned in advance is avoided, the migration cost after the contention behavior occurs is avoided, and the stability of the cloud computing platform can be improved.
Specific implementation manners of determining a target physical server in a plurality of physical servers for tenants with different attribute information are as follows:
in one possible implementation manner, in step S202, determining a target physical server among a plurality of physical servers of a stock cloud server that have been deployed with a resource contending tenant includes:
and in the plurality of physical servers, the physical servers with the quantity of stock cloud servers which have deployed resources to contend for tenants and are ranked in the top order are used as target physical servers.
In practical application, if the current tenant is a resource-robbed tenant, that is, a resource-robbed situation occurs before the current tenant or a resource-robbed situation may occur, the physical servers are sorted according to the number of the stock cloud servers of the resource-robbed tenant, and the physical server in the front of the sorting is used as a target physical server.
Optionally, the physical server with the largest quantity of inventory cloud servers deployed with the resource contending tenant is used as the target physical server.
In this embodiment, the cloud servers of the tenants subject to resource contention are aggregated to one or more physical servers for deployment, so that the cloud servers of the tenants subject to resource contention do not affect the operation of the cloud servers corresponding to the tenants subject to non-resource contention, and the resource contention range is narrowed.
In one possible implementation manner, in step S202, determining a target physical server among a plurality of physical servers of a stock cloud server that have been deployed with a resource contending tenant includes:
determining a target physical server among a plurality of physical servers already deployed with an inventory cloud server of a current tenant.
In practical application, for tenants contending for resources, aggregation deployment can be performed on cloud servers of tenants with the same attribute information according to the aggregation manner in the above embodiment, and aggregation can be further performed according to the tenants. Preferentially selecting a physical server with more stock cloud servers of the current tenant from a plurality of physical servers of the stock cloud servers of the tenant with the resource contention, and taking the physical server as a target physical server to continue deploying the cloud server of the current tenant.
In one possible implementation, the method further includes:
and under the condition that the current tenant is determined to be a non-resource-contended tenant based on the attribute information, in a plurality of physical servers of cloud servers which are not deployed with the resource-contended tenant, sequencing the physical servers with the number of stock cloud servers deployed with the non-resource-contended tenant behind as target physical servers.
In practical application, if the current tenant is a non-resource-robbed tenant, that is, the current tenant has no or low possibility of resource-robbed occurrence, the physical servers of the cloud servers which are not deployed with the resource-robbed tenant are sorted according to the number of stock cloud servers corresponding to the non-robbed tenant, and the physical servers after sorting are used as target physical servers. The physical server of the cloud server which is not deployed with the resource contention tenant may be a physical server of the cloud server which is not deployed with the resource contention tenant, or a physical server of the cloud server which is not deployed with the resource contention tenant, that is, an idle physical server which is not deployed with any cloud server. The physical server of the cloud server not deployed with the resource contending tenant may also be a physical server of a cloud server deployed with only a non-resource contending tenant.
Optionally, the physical server with the minimum number of inventory cloud servers deployed by the non-resource-robbing tenant is used as the target physical server.
In this embodiment, the cloud servers of the tenants which are not subjected to resource contention are deployed in a dispersed manner and are deployed on a plurality of physical servers in a dispersed manner.
Fig. 3 is a schematic diagram of a cloud server deployment method according to an embodiment of the present application; as shown in fig. 3, the VM represents a cloud server corresponding to each tenant, and each physical server is deployed with an inventory cloud server of the tenant. When cloud server deployment is performed on tenants which are not in conflict with resources, decentralized deployment is performed, newly-added cloud servers are decentralized to different physical servers for deployment, and the physical servers do not deploy stock cloud servers of the tenants before. When the cloud servers of the tenants contend for the resources are deployed, centralized deployment is carried out, for each newly-added cloud server, the physical server with the largest quantity of the cloud servers of the tenants contend for the resources is selected as a target physical server, and the newly-added cloud servers are deployed in the target physical server, so that the cloud servers of the tenants contend for the resources are aggregated into the same physical server. The cloud servers of the tenants with the resource contention are aggregated to one physical server, so that the resource contention range is reduced, and the cloud servers of the tenants with the resource contention are prevented from influencing the operation of the cloud servers of the tenants without the resource contention.
In one possible implementation manner, the cloud server deployment method further includes:
determining attribute information of the stock tenants based on historical operating information of cloud servers corresponding to the stock tenants;
the historical operational information includes at least one of:
the power consumption of the physical server, the network flow, the CPU occupancy rate or the memory occupancy rate.
In practical application, historical operation information of a cloud server of a stock tenant of a cloud computing platform is obtained, wherein the historical operation information comprises one or more of power consumption of a physical server where the cloud server is located, network flow of the cloud server, Central Processing Unit (CPU) occupancy rate or memory occupancy rate of the cloud server. According to historical operation information of the cloud server corresponding to the stock tenant, whether the cloud server corresponding to the stock tenant is in a resource contention condition or not can be determined, and if the resource contention condition occurs, the tenant corresponding to the cloud server in which the resource contention occurs is the resource contention tenant. The network traffic of the cloud server includes uplink traffic, downlink traffic and the like of the cloud server.
In an example, according to historical operating information of cloud server B1 of tenant a1 within one month, it is found that power consumption of a physical server where cloud server B1 is located increases for a short time due to multiple times, and it is determined that resource contention occurs in cloud server B1, and tenant a1 is determined as a resource contention tenant.
In a possible implementation manner, in step S201, determining attribute information of a current tenant includes:
acquiring first characteristic information of a newly-added cloud server corresponding to a current tenant and second characteristic information of a cloud server corresponding to a resource contention tenant in a stock tenant;
and matching the first characteristic information with the second characteristic information, and determining the attribute information of the current tenant according to the matching result.
In practical application, when a newly-added cloud server is allocated to a tenant, feature information of the newly-added cloud server corresponding to the current tenant, namely first feature information, is extracted. After the resource dispute tenants in the inventory tenants are determined in advance, the feature information of the cloud server corresponding to the resource dispute tenants, namely the second feature information, is extracted in advance, and the feature information of the cloud server corresponding to the resource dispute tenants can be generated into tenant dispute portraits. The first characteristic information and the second characteristic information may be attribute characteristics that the cloud server may have, for example, a user, an industry, a region, a product, a time period, and the like, which correspond to the cloud server.
And matching the first characteristic information with the user scramble portrait, namely matching the first characteristic information with the second characteristic information, wherein if one or more characteristics in the first characteristic information are matched with the user scramble portrait, the current tenant is a resource scramble tenant, and otherwise, the current tenant is a non-resource scramble tenant.
The current tenant can be a newly added tenant or a stock tenant, and if the current tenant is the newly added tenant, whether the current tenant is a resource dispute tenant can be determined according to matching results of characteristics of industries, regions, products, time periods and the like; and if the current tenant is the inventory tenant, determining whether the current tenant is a resource contending tenant or not according to the matching result of the characteristics of the user, the industry, the region, the product, the time period and the like.
Optionally, if the current tenant is a newly added tenant, the number of stock cloud servers corresponding to the current tenant deployed in the physical server is zero, and a target physical server may 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. Wherein the target physical server may be a pre-configured designated physical server.
In one possible implementation manner, the cloud server deployment method further includes:
determining the attribute information of the stock tenants according to a preset time period, and updating the attribute information of the stock tenants.
In practical application, according to a preset time period, determining attribute information of stock tenants according to historical operating information of cloud servers corresponding to the stock tenants of the cloud computing platform, updating the attribute information, and adjusting deployment modes of the cloud servers according to the updated attribute information to improve the use experience of the cloud servers of the tenants.
For example, according to the historical operating information of the cloud server corresponding to tenant a2 in the current 1 month to 3 months, tenant a2 is determined as a resource robbery tenant, but according to the historical operating information of the cloud server of tenant a2 in the current 4 months to 6 months, it is found that no resource robbery occurs, the attribute information of tenant a2 may be updated in the current 7 months, and the attribute information of tenant a2 is updated to a non-resource robbery tenant. When the cloud server corresponding to the tenant a2 is deployed, the cloud server may be deployed in a cloud server deployment manner of a non-resource-contended tenant.
It should be noted that the preset time period may be configured according to specific needs, and the present application does not limit this.
In a possible implementation manner, in step S202, determining a target physical server among a plurality of physical servers already deployed with inventory cloud servers of resource contending tenants includes:
and based on the resource types of the contention in the attribute information, taking the physical server of the cloud server corresponding to the resource types of the contention as a target physical server in the plurality of physical servers of the stock cloud server where the resource contention tenants are deployed.
In practical application, when the characteristics of the cloud server corresponding to the resource dispute user are extracted and the resource dispute portrait of the resource dispute tenant is generated, the power consumption dispute portrait, the network flow dispute portrait and the like can be generated according to the type of the dispute resource, the attribute information can comprise the dispute resource type and the cloud servers corresponding to the resource dispute users of different types, and the cloud servers corresponding to the tenants with the same resource dispute type are deployed in the physical servers corresponding to the cloud servers of the corresponding dispute resource type, so that the cloud servers corresponding to the tenants with the same resource dispute type can be aggregated together, the dimension of damage of the physical servers caused by the resource dispute can be reduced, and the corresponding measures can be taken conveniently for disaster recovery processing.
In one possible implementation manner, deploying a newly added cloud server corresponding to a current tenant in a target physical server includes:
acquiring specification information of a newly added cloud server;
and deploying the cloud server corresponding to the specification information in the target physical server to serve as a newly-added cloud server corresponding to the current tenant.
The specification information of the cloud server may include a CPU specification, a memory size, a disk space size, a network bandwidth, a security policy (e.g., an externally open port), and the like. And starting a corresponding cloud server in the target physical server according to the specification information of the cloud server purchased by the tenant, and providing computing service for the tenant.
In order to make the specific implementation process of the technical solution of the present application clearer, the following describes the process of the technical solution of the present application in detail by using a specific embodiment. Fig. 4 is a schematic diagram of a cloud server deployment method according to an embodiment of the present application; in this embodiment, an example represents a cloud server. This embodiment includes three modules: the system comprises a scheduling module, an example contention information acquisition module and a user contention portrait extraction module. When a newly added cloud server (such as a "creation example" shown in the figure) is allocated to a tenant, the scheduling module is configured to obtain feature information of the newly added cloud server corresponding to the tenant, match the feature information with a user contending image of a stock resource contending user, if the matching is successful (such as the "image matching" shown in the figure), indicate that the current tenant is the resource contending tenant, use a physical server with the largest number of stock cloud servers where the resource contending tenant is deployed as a target physical server (such as a "selected physical server" shown in the figure), and deploy the newly added physical server corresponding to the current tenant in the target physical server (such as the "creation example" shown in the figure). Thereby achieving reduced breakup and improved polymerization. The example robbery information acquisition module is used for monitoring the running state of the cloud server running on the cloud computing platform and acquiring abnormal information including historical running information of the cloud server of the tenant of resource robbery. The user scramble portrait extracting module is used for analyzing and summarizing historical operation information of a cloud server of the tenant of resource scramble, extracting common characteristics such as users, regions, products, time periods and the like, and generating different user scramble portraits such as power consumption scramble portraits and network scramble portraits according to different types of scramble resources for the scheduling module to use.
Corresponding to the application scenario and the method of the method provided by the embodiment of the application, the embodiment of the application further provides a cloud server deployment device. As shown in fig. 5, the cloud server deployment apparatus may include:
a first determining module 501, configured to determine attribute information of a current tenant; the attribute information is used for representing that the current tenant is a resource dispute tenant or a non-resource dispute tenant;
a second determining module 502, configured to determine, when it is determined that the current tenant is a resource robbing tenant based on the attribute information, a target physical server among a plurality of physical servers of a stock cloud server to which the resource robbing tenant has been deployed;
the deployment module 503 is configured to deploy, in the target physical server, a newly added cloud server corresponding to the current tenant.
The cloud server deployment device provided by the embodiment of the application does not need to plan a scheduling domain in advance, and determines the attribute information of the current tenant when a newly-added cloud server of the tenant is deployed; determining a target physical server in a plurality of physical servers of a stock cloud server which is already deployed with a resource contention tenant under the condition that the current tenant is determined to be the resource contention tenant based on the attribute information; and deploying a newly-added cloud server corresponding to the current tenant in the target physical server. According to the technical scheme, when the tenants are deployed with the cloud servers, the tenants with the resource contention are aggregated, the cloud servers which do not influence the tenants with the resource contention are prevented from running, in addition, the resource waste caused by the fact that scheduling domains are planned in advance is avoided, the migration cost after the contention behavior occurs is avoided, and the stability of the cloud computing platform can be improved.
In a possible implementation manner, the second determining module 502 is specifically configured to:
and in the plurality of physical servers, the physical servers with the quantity of stock cloud servers which have deployed resources to contend for tenants and are ranked in the top order are used as target physical servers.
In a possible implementation manner, the second determining module 502 is further configured to:
and under the condition that the current tenant is determined to be a non-resource-robbing tenant based on the attribute information, in a plurality of physical servers of cloud servers which are not deployed with the resource-robbing tenant, the physical servers with the quantity of stock cloud servers deployed with the non-resource-robbing tenant ranked in the later order are used as target physical servers.
In a possible implementation manner, the second determining module 502 is specifically configured to:
determining a target physical server among a plurality of physical servers already deployed with an inventory cloud server of a current tenant.
In a possible implementation manner, the cloud server deployment apparatus further includes a third determining module, configured to:
determining attribute information of the stock tenants based on historical operation information of cloud servers corresponding to the stock tenants;
the historical operating information includes at least one of:
power consumption, network flow, Central Processing Unit (CPU) occupancy rate or memory occupancy rate of the physical server.
In a possible implementation manner, the first determining module 501 is specifically configured to:
acquiring first characteristic information of a newly-added cloud server corresponding to a current tenant and second characteristic information of a cloud server corresponding to a resource contention tenant in a stock tenant;
and matching the first characteristic information with the second characteristic information, and determining the attribute information of the current tenant according to the matching result.
In one possible implementation manner, the apparatus further includes an attribute updating module, configured to:
determining the attribute information of the stock tenants according to a preset time period, and updating the attribute information of the stock tenants.
In a possible implementation manner, the second determining module 502 is specifically configured to:
and based on the contended resource types in the attribute information, taking the physical server of the cloud server corresponding to the contended resource types as a target physical server from a plurality of physical servers of the stock cloud server which are already deployed with the resource contending tenants.
In a possible implementation manner, the deployment module 503 is specifically configured to:
acquiring specification information of a newly added cloud server;
and deploying the cloud server corresponding to the specification information in the target physical server to serve as a newly-added cloud server corresponding to the current tenant.
The functions of each module in each device in the embodiment of the present application can be referred to the corresponding description in the above method, and have corresponding beneficial effects, which are not described herein again.
FIG. 6 is a block diagram of an electronic device used to implement embodiments of the present application. As shown in fig. 6, the electronic apparatus includes: a memory 610 and a processor 620, the memory 610 having stored therein computer programs executable on the processor 620. The processor 620, when executing the computer program, implements the method in the above embodiments. The number of the memory 610 and the processor 620 may be one or more.
The electronic device further includes:
the communication interface 630 is used for communicating with an external device to perform data interactive transmission.
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 may be connected to each other through a bus and perform communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 6, but this is not intended to represent only one bus or type of bus.
Optionally, in an implementation, if the memory 610, the processor 620, and the communication interface 630 are integrated on a chip, the memory 610, the processor 620, and the communication interface 630 may complete communication with each other through an internal interface.
Embodiments of the present application provide a computer-readable storage medium, which stores a computer program, and when the program is executed by a processor, the computer program implements the method provided in the embodiments of the present application.
The embodiment of the present application further provides a chip, where the chip includes a processor, and is configured to call and execute the instruction stored in the memory from the memory, so that the communication device in which the chip is installed executes the method provided in the embodiment of the present application.
An embodiment of the present application further provides a chip, including: the system comprises an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected through an internal connection path, the processor is used for executing codes in the memory, and when the codes are executed, the processor is used for executing the method provided by the embodiment of the application.
It should be understood that the processor may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be a processor supporting an Advanced reduced instruction set machine (ARM) architecture.
Further, optionally, the memory may include a read-only memory and a random access memory, and may further include a nonvolatile random access memory. The memory may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may include a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can include Random Access Memory (RAM), which acts as external cache Memory. By way of example, and not limitation, many forms of RAM are available. For example, Static Random Access Memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDR SDRAM), Enhanced SDRAM (ESDRAM), SLDRAM (SLDRAM), and Direct Memory bus RAM (DR RAM).
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may 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. The procedures or functions according to the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
In the description of the present specification, reference to the description of "one embodiment," "some embodiments," "an example," "a specific example," or "some examples" or the like means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or to implicitly indicate the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present application includes other implementations in which functions may be performed out of the order shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the method of the above embodiments may be implemented by hardware that is configured to be instructed to perform the relevant steps by a program, which may be stored in a computer-readable storage medium, and which, when executed, includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The above-described integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer-readable storage medium. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various changes or substitutions within the technical scope of the present application, and these should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (12)
1. A cloud server deployment method, the method comprising:
determining attribute information of a current tenant; the attribute information is used for representing that the current tenant is a resource dispute tenant or a non-resource dispute tenant;
determining a target physical server in a plurality of physical servers of a stock cloud server already deployed with the resource contending tenant under the condition that the current tenant is determined to be the resource contending tenant based on the attribute information;
and deploying a newly-added cloud server corresponding to the current tenant in the target physical server.
2. The method of claim 1, wherein determining a target physical server among a plurality of physical servers of a stock cloud server that have been deployed with a resource contending tenant comprises:
and in the plurality of physical servers, the physical servers with the quantity of stock cloud servers which have deployed resources to contend for tenants and are ranked in the front are used as the target physical servers.
3. The method of claim 1, further comprising:
and under the condition that the current tenant is determined to be a non-resource-robbed tenant based on the attribute information, in a plurality of physical servers of cloud servers which are not deployed with the resource-robbed tenant, sequencing the physical servers with the quantity of stock cloud servers deployed with the non-resource-robbed tenant behind as the target physical server.
4. The method of claim 1, wherein determining a target physical server among a plurality of physical servers of a stock cloud server that have been deployed with a resource contending tenant comprises:
determining a target physical server among a plurality of physical servers already deployed with the current tenant's inventory cloud server.
5. The method according to any one of claims 1-3, further comprising:
determining attribute information of the stock tenants based on historical operating information of cloud servers corresponding to the stock tenants;
the historical operating information includes at least one of:
power consumption, network flow, Central Processing Unit (CPU) occupancy rate or memory occupancy rate of the physical server.
6. The method of claim 5, wherein the determining attribute information of the current tenant comprises:
acquiring first characteristic information of a newly-added cloud server corresponding to the current tenant and second characteristic information of a cloud server corresponding to a resource contention tenant in the inventory tenant;
and matching the first characteristic information with the second characteristic information, and determining the attribute information of the current tenant according to the matching result.
7. The method of claim 5, further comprising:
and determining the attribute information of the stock tenants according to a preset time period, and updating the attribute information of the stock tenants.
8. The method according to any one of claims 1-3, wherein determining a target physical server among a plurality of physical servers of an inventory cloud server that have been deployed with a resource contending tenant comprises:
and based on the contended resource types in the attribute information, taking the physical server of the cloud server corresponding to the contended resource types as the target physical server from a plurality of physical servers of the stock cloud server which is already deployed with the resource contending tenants.
9. The method according to any one of claims 1 to 3, wherein deploying the newly added cloud server corresponding to the current tenant in the target physical server comprises:
acquiring specification information of the newly-added cloud server;
and deploying the cloud server corresponding to the specification information in the target physical server to serve as a newly-added cloud server corresponding to the current tenant.
10. A cloud server deployment apparatus, the apparatus comprising:
the first determining module is used for determining attribute information of a current tenant; the attribute information is used for representing that the current tenant is a resource dispute tenant or a non-resource dispute tenant;
a second determining module, configured to determine a target physical server among a plurality of physical servers of the stock cloud server to which the resource-robbing tenant has been deployed, when it is determined that the current tenant is a resource-robbing tenant based on the attribute information;
and the deployment module is used for deploying the newly-added cloud server corresponding to the current tenant in the target physical server.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory, the processor implementing the method of any one of claims 1-9 when executing the computer program.
12. A computer-readable storage medium, having stored therein a computer program which, when executed by a processor, implements the method of any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210553965.8A CN114756380A (en) | 2022-05-20 | 2022-05-20 | Cloud server deployment method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210553965.8A CN114756380A (en) | 2022-05-20 | 2022-05-20 | Cloud server deployment method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114756380A true CN114756380A (en) | 2022-07-15 |
Family
ID=82334860
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210553965.8A Pending CN114756380A (en) | 2022-05-20 | 2022-05-20 | Cloud server deployment method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114756380A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116600014A (en) * | 2023-07-17 | 2023-08-15 | 中移(苏州)软件技术有限公司 | Server scheduling method and device, electronic equipment and readable storage medium |
-
2022
- 2022-05-20 CN CN202210553965.8A patent/CN114756380A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116600014A (en) * | 2023-07-17 | 2023-08-15 | 中移(苏州)软件技术有限公司 | Server scheduling method and device, electronic equipment and readable storage medium |
| CN116600014B (en) * | 2023-07-17 | 2023-10-10 | 中移(苏州)软件技术有限公司 | Server scheduling method and device, electronic equipment and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110535777B (en) | Access request control method and device, electronic equipment and readable storage medium | |
| CN108399101B (en) | Method, device and system for scheduling resources | |
| US8695079B1 (en) | Allocating shared resources | |
| US20170324612A1 (en) | Network function virtualization | |
| CN108021400B (en) | Data processing method and device, computer storage medium and equipment | |
| CN112579622B (en) | Method, device and equipment for processing service data | |
| CN111880936A (en) | Resource scheduling method and device, container cluster, computer equipment and storage medium | |
| CN110826799A (en) | Service prediction method, device, server and readable storage medium | |
| US20230061228A1 (en) | Managing shared applications at the edge of a content delivery network | |
| CN108390786B (en) | Business operation and maintenance method and device and electronic equipment | |
| CN114756380A (en) | Cloud server deployment method and device, electronic equipment and storage medium | |
| CN110489227B (en) | Resource allocation method, device, computer equipment and storage medium | |
| EP3355190A1 (en) | Device and system for maintaining a ditributed ledger | |
| CN111984991A (en) | Data encryption storage method, system, terminal and storage medium | |
| CN111277626A (en) | Server upgrading method and device, electronic equipment and medium | |
| CN116436968A (en) | Service grid communication method, system, device and storage medium | |
| CN106936643B (en) | Equipment linkage method and terminal equipment | |
| CN115604103A (en) | Configuration method and device of cloud computing system, storage medium and electronic equipment | |
| CN109492376B (en) | Device access authority control method and device and bastion machine | |
| CN112417402B (en) | Authority control method, authority control device, authority control equipment and storage medium | |
| CN112035379B (en) | Method and device for using storage space, storage medium and electronic device | |
| CN114860266A (en) | Deployment method and system of multi-party security computing model | |
| CN111491040B (en) | IP distribution method and IP distribution device | |
| CN113746918A (en) | Hypertext transfer protocol proxy method and system | |
| CN114328650A (en) | Database resource management method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |