CN111488217A

CN111488217A - Cloud server deployment method and management equipment

Info

Publication number: CN111488217A
Application number: CN201910087039.4A
Authority: CN
Inventors: 于颜硕; 徐海弘; 王渊平
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-01-29
Filing date: 2019-01-29
Publication date: 2020-08-04

Abstract

The invention discloses a cloud server deployment method, which comprises the following steps: acquiring user level information of a cloud server issuing party and cloud server limits corresponding to service tags of the cloud server; acquiring a host machine with the service label; and deploying the cloud server to the host with the service label when the deployed cloud server does not exceed the cloud server limit. The invention also provides corresponding cloud server deployment management equipment.

Description

Cloud server deployment method and management equipment

Technical Field

The invention relates to the field of cloud services, in particular to the field of cloud server deployment.

Background

With the continuous development of cloud computing services, cloud server products and functions bearing cloud computing functions are also continuously updated, and multiple products and functions are frequently released in an iterative manner. Due to the complexity of the cloud server product and the functions, the new cloud server product often has many problems in terms of hardware and software stability. Even if a new cloud server product is fully tested, it cannot be guaranteed that all problems can be covered by the test.

There is a need for a new cloud server deployment scheme that can correlate cloud server deployment with the software and hardware characteristics of the hosts that host the cloud servers, and can also provide user-level grayscale control.

Disclosure of Invention

To this end, the present invention provides a new cloud server deployment approach in an attempt to solve, or at least alleviate, at least one of the problems identified above.

According to an aspect of the present invention, there is provided a cloud server deployment method, including the steps of: acquiring a cloud server limit corresponding to a user level of a cloud server issuing party and a service tag of a cloud server; acquiring a host machine with the service label; and deploying the cloud server to the host with the service label when the deployed cloud server does not exceed the cloud server limit.

Optionally, the deployment method according to the present invention further comprises the steps of: acquiring attribute information of a host machine; and distributing the service label for the host machine based on the acquired attribute information according to the preset service rule.

Optionally, in the deployment method according to the present invention, the step of obtaining the attribute information of the host includes: and acquiring the attribute information of the host by using the query service deployed in the host.

Optionally, in the deployment method according to the present invention, the preset service rule defines attribute information associated with the service tag, and the step of allocating the service tag to the host includes: and if the attribute information of the host machine is matched with the attribute information defined in the preset service rule, distributing the service label for the host machine.

Optionally, in the deployment method according to the present invention, the attribute information includes software and hardware resource information.

Optionally, in the deployment method according to the present invention, the step of obtaining the cloud server limit corresponding to the user level and the service tag includes: a cloud server limit corresponding to the user level and the business label is determined with reference to a business issuance policy. The service publishing policy defines the service, the user level at which the service can be published, and the cloud server restrictions.

Optionally, in the deployment method according to the present invention, the cloud server limit includes one or more of the following: the number of cloud servers and the number of computing cores of the cloud servers.

Optionally, in the deployment method according to the present invention, the service publishing policy further defines a scheduling policy associated with the specific service, where the scheduling policy indicates whether the cloud server having the specific service label is to be deployed in the host having the specific service label all the time.

Optionally, in the deployment method according to the present invention, the step of determining the user level of the cloud server publisher includes determining the user level according to one or more of the following attributes of the user: credit level, product purchasing habits, and account number type.

According to another aspect of the present invention, there is also provided a cloud server deployment management apparatus, including: the user level determining unit is suitable for determining the user level of the cloud server publisher; a policy determining unit adapted to obtain cloud server restrictions corresponding to the user level and a service tag of a cloud server; the host machine determining unit is suitable for acquiring the host machine with the service label; and the deployment unit is suitable for deploying the cloud server to the host with the service label when the deployed cloud server does not exceed the limit of the cloud server.

According to still another aspect of the present invention, there is also provided a computing device. The computing device includes at least one processor and a memory storing program instructions, wherein the program instructions are configured to be executed by the at least one processor and include instructions for performing the rack power consumption management method described above.

According to yet another aspect of the present invention, there is also provided a readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform the rack power consumption management method described above.

According to the cloud server deployment scheme provided by the invention, the deployment mode related to the service is determined by considering the user level when the cloud server is deployed, so that the fine-grained gray control of the user can be provided.

In addition, according to the cloud server deployment scheme provided by the invention, the software and hardware characteristics of the host machine can be collected in advance, and the service labels are distributed to the host machine according to the software and hardware characteristics, so that the cloud server deployment can be carried out by referring to the software and hardware characteristics when the gray level service deployment is carried out subsequently, and the problem of the existing gray level deployment scheme is solved.

Drawings

To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings, which are indicative of various ways in which the principles disclosed herein may be practiced, and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description read in conjunction with the accompanying drawings. Throughout this disclosure, like reference numerals generally refer to like parts or elements.

FIG. 1 shows a schematic diagram of a cloud server deployment system 100 according to one embodiment of the invention;

FIG. 2 shows a schematic diagram of a computing device 200, according to one embodiment of the invention;

FIG. 3 shows a flow diagram of a cloud server deployment method 300 according to one embodiment of the invention; and

fig. 4 shows a schematic diagram of a cloud server deployment management device 400 according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Fig. 1 shows a schematic diagram of a cloud server deployment system 100 according to one embodiment of the invention. As shown in fig. 1, the cloud server deployment system 100 includes a host 110, a cloud server 120 deployed on the host 110, a deployment management apparatus 130, and a user front end 140.

The cloud server 120 is a simple, efficient, safe, reliable computing service with elastically scalable processing capability. Cloud server 120 is typically deployed on host 110 through hardware resource virtualization. The host 110 serves as a physical server for supporting the cloud server 120, and provides a management control software system of the cloud server 110 and an operating environment of the cloud server 110. In one embodiment, host 110 provides a consistent hosting environment by virtualizing the underlying software and hardware resources. Cloud server 120 may select and reside hosts 110 according to its required computing resources.

Typically, multiple cloud servers 120 may be hosted on one host 110. The deployment management device 130 may manage deployment of the cloud server 120 on hosts, including but not limited to management, scheduling, and control of the cloud server 120 during a life cycle, for example, management of scenarios such as migration of the cloud server 120 between hosts triggered by operations such as selection, restart, and configuration change of the hosts 110 during creation of the cloud server 120, and resource release of the cloud server 120 after use is completed.

The user front end 140 provides an interface for a user to manage the cloud server 110. The user creates and manages the cloud server 110 according to business needs, and thus the user sends a request to the deployment management apparatus 130 via the user front end 140. The deployment management device 130 creates the cloud server 120 related to the user and the service scenario according to the user request, and deploys the cloud server 120 to the corresponding host 110. Hereinafter, a manner in which the deployment management apparatus 130 manages the deployment of the cloud server 130 will be described in detail with reference to fig. 3 and 4.

Optionally, each host 110 also includes a query service 112. Query service 112 may query the physical resource attributes (e.g., model, network architecture) and software resource attributes (e.g., software version) of host 110 and create attribute tags for these software and hardware resource attributes. The attribute tags are typically in the format of key-value pairs, e.g. for hosts #1 to #3 in fig. 1, the attribute tags can be established as follows:

#1：type＝F42 net＝25G

#2：type＝M51 net＝10G

#3：type＝F42 net＝10G

according to one embodiment, each host 110 may utilize the query service 112 to send its software and hardware resource attributes to the deployment management device 130 so that the deployment management device 130 records these attribute tags. The deployment management device 130 may also remotely invoke various query services 112 to obtain and record these attribute tags. Additionally, optionally, software and hardware resource attributes of the host 110 may be manually recorded in the deployment management device 130. The deployment management device 130 may refer to the software and hardware resource attributes of the host 110 when deploying the cloud server 120.

It should be noted that although the attribute information of the host is described above by taking the attribute of the software and hardware resources as an example, the present invention is not limited thereto, and all the information that can characterize the host may be the attribute information of the host.

According to an embodiment of the present invention, the deployment management device 130 may be implemented by the computing device 200 as described below or by a series of related cooperating computing devices 200. FIG. 2 shows a schematic diagram of a computing device 200, according to one embodiment of the invention.

As shown in FIG. 2, in a basic configuration 202, a computing device 200 typically includes a system memory 206 and one or more processors 204. A memory bus 208 may be used for communication between the processor 204 and the system memory 206.

Depending on the desired configuration, the processor 204 may be any type of processing, including but not limited to a microprocessor (μ P), a microcontroller (μ C), a digital information processor (DSP), or any combination thereof the processor 204 may include one or more levels of cache, such as a level one cache 210 and a level two cache 212, a processor core 214, and registers 216 the example processor core 214 may include an arithmetic logic unit (A L U), a Floating Point Unit (FPU), a digital signal processing core (DSP core), or any combination thereof the example memory controller 218 may be used with the processor 204 or, in some implementations, the memory controller 218 may be an internal part of the processor 204.

Depending on the desired configuration, system memory 206 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 206 may include an operating system 220, one or more applications 222, and program data 224. In some implementations, the application 222 can be arranged to execute instructions on the operating system with the program data 224 by the one or more processors 204.

Computing device 200 may also include an interface bus 240 that facilitates communication from various interface devices (e.g., output devices 242, peripheral interfaces 244, and communication devices 246) to the basic configuration 202 via the bus/interface controller 230. The example output device 242 includes a graphics processing unit 248 and an audio processing unit 250. They may be configured to facilitate communication with various external devices, such as a display or speakers, via one or more a/V ports 252. Example peripheral interfaces 244 can include a serial interface controller 254 and a parallel interface controller 256, which can be configured to facilitate communications with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/O ports 258. An example communication device 246 may include a network controller 260, which may be arranged to facilitate communications with one or more other computing devices 262 over a network communication link via one or more communication ports 264.

A network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media, such as carrier waves or other transport mechanisms, in a modulated data signal. A "modulated data signal" may be a signal that has one or more of its data set or its changes made in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or private-wired network, and various wireless media such as acoustic, Radio Frequency (RF), microwave, Infrared (IR), or other wireless media. The term computer readable media as used herein may include both storage media and communication media.

Computing device 200 may be implemented as a server, such as a database server, an application server, a WEB server, and the like, or as a personal computer including desktop and notebook computer configurations. Of course, computing device 200 may also be implemented as part of a small-sized portable (or mobile) electronic device.

Fig. 3 shows a flowchart of a cloud server deployment method 300 according to an embodiment of the invention. The method 300 is suitable for execution in the cloud server deployment management device 130 shown in fig. 1 to determine the deployment of the cloud server 120 onto that host 110.

As shown in fig. 3, the method 300 begins at step S310. The method 300 begins processing when a user publishes a cloud server for a certain service. To this end, a user level of the cloud server publisher is first determined in step S310. The users are divided into different levels according to the user attributes, and corresponding level labels are added to the users, so that the corresponding cloud server deployment is performed on the users by considering the attributes of the users subsequently. According to one embodiment, the user level may be determined based on the credit status of the user. For example, users may be divided into five levels, C1-C5, according to user credit, representing a user's low-to-high credit level, respectively. According to another embodiment, the user level may be further divided in consideration of a combination of one or more of the user's credit level, product purchasing habits, account number type, and the like. Therefore, when a cloud server request for a user to issue a certain service is received, the user level of the user may be determined with reference to the pre-divided user levels.

Subsequently, in step S320, a corresponding cloud server limit is obtained according to the user level determined in step S310 and the service tag associated with the cloud server. The cloud server limit herein refers to a limit that a cloud server of a corresponding service that a user has published cannot exceed. According to one embodiment, the cloud server limit comprises a cloud server number limit, in which case the number of cloud servers for the relevant service that the user has published cannot exceed this number limit. Only if this number limit is not exceeded, the user can deploy a new cloud server. According to another embodiment, the cloud server limitations further include a number of computing cores limitation, a network bandwidth limitation, and the like. The invention is not limited to the specific content of cloud server limitation, and all the limiting ways that the number of deployed cloud servers can be quantitatively limited are within the protection scope of the invention.

Optionally, in order to obtain the corresponding cloud server limit, a service publishing policy may be formulated first. The service publishing policy defines a service, a user level capable of publishing the service, cloud server limitations for publishing the service, and the like. For example, the following table gives one specific example of a service publishing policy:

business	User level	Number of	Scheduling policy
				Newly purchase	C1，C2，C3	1000	Without forcing
Dragon's spirit	C1，C2	2	Without forcing
				Multi-network card	C3	10	Force the

As shown in the above table, the cloud server limit is a cloud server limit. For users at C1 level, a maximum of 1000 cloud servers with business label "newly purchased" and 2 cloud servers with business label "shenlong" may be released. In step S320, cloud server restrictions corresponding to the user level and the service tag may be determined with reference to the service issuance policy.

Subsequently, in step S330, a host having a business tag corresponding to the cloud server to be published by the user is acquired. According to one embodiment, each host may be assigned a corresponding service label in advance. Specifically, the software and hardware resource limit required by each service can be determined, and when the software and hardware resource attribute of a certain host meets the requirement of the service, the service label of the service is allocated to the host.

Next, in step S340, when it is determined that the cloud server of the specified service type that the user has deployed does not exceed the cloud server limit acquired in step S320, the cloud server is deployed into the host with the service tag determined in step S330.

According to the cloud server deployment scheme provided by the method 300, the deployment of the cloud server can be controlled in consideration of the user level, and when the scheme is used for gray level deployment, gray level flow control of user granularity can be provided.

It should be noted that the order of execution of steps S330 and S340 may be reversed. For example, after determining that the deployed cloud server does not exceed the cloud server limit in step S340, then determining the host with the corresponding service tag in step S330, and completing the deployment of the cloud server.

Optionally, the method 300 further comprises a processing step of allocating a service label to the host in advance. In step S350, software and hardware resource information of each host is collected. The software and hardware resource information of each host can be collected in various ways. In one embodiment, as described above with reference to FIG. 1, a query service 112, for example, in a host 110, obtains and stores software and hardware resource attribute tags for the host 110. According to another embodiment, the software and hardware resource attributes of each host may also be manually obtained, for example, when a host is newly added to the cloud service system, the software and hardware resource attributes of the host may be manually added to the cloud server deployment management device.

Subsequently, in step S360, based on the host software and hardware resource information obtained in step S350, a service label is allocated to the host, so as to add the service label to each host. As described above, the required software and hardware resource requirements can be defined in advance for each service. When the software and hardware resource attributes of the host obtained in step S350 match the defined resource requirement, a corresponding service tag is allocated to the host, so as to determine the service tag of the host.

For example, if there are the following preset business rules:

(1) multiple network cards: model F42 and network architecture 25G

(2) Shenlong: m51 model and 10G network architecture

(3) Newly purchasing: model F42 and network architecture 10G

For the #1, #2, and #3 hosts described with reference to fig. 1, according to the preset business rules, the business label "multi-network card" may be allocated to the #1 host 110, the business label "shenlong" may be allocated to the #2 host 110, and the business label "newly purchased" may be allocated to the #3 host 110. The traffic label of each host is then recorded so that the traffic label of each host can be determined.

It should be noted that although the attribute information of the host and the definition of the preset business rule are described above by taking the attributes of the software and hardware resources as examples, the present invention is not limited thereto, and all the information that can characterize the host may be the attribute information of the host.

The method 300 including the above steps S350 and S360 may also associate the hardware and software resource attributes of the host with the services, so that when the cloud server solution provided by the method 300 is used for gray scale deployment, a specific gray scale service may be deployed to the host with specific hardware and software resources.

Optionally, referring to the service publishing policy table, a scheduling policy of each service is further defined in the service publishing policy. The scheduling policy indicates whether the cloud server under the service is to be deployed in the host with the service label all the time. For example, if the scheduling policy is mandatory, the corresponding host traffic label must be exactly matched during the lifecycle of the deployed cloud server. The forced scheduling strategy can enable the cloud server product needing specific software or hardware resource support to be deployed in the host machine comprising corresponding software or hardware resources, so that the problem that the cloud server product cannot work normally because the bottom layer software or hardware resources do not support is avoided.

FIG. 4 shows a schematic diagram of a deployment management device 400 according to an embodiment of the invention. The deployment management apparatus 400 shows the various components of the deployment management apparatus 130 shown in fig. 1 divided by functional logic, while fig. 2 shows the various components of the deployment management apparatus 130 shown in fig. 1 divided by physical structure, both of which illustrate the same apparatus from different angles.

In addition, the functions executed by each logic unit shown in fig. 4 correspond to the cloud server deployment method described with reference to fig. 3, and the same or similar parts between the two will not be repeated.

As shown in fig. 4, the deployment management apparatus 400 includes a user level determining unit 410, a policy determining unit 420, a host determining unit 430, and a deployment unit 440.

After the user sends the cloud server deployment request to the deployment management device 400 via the user front end 140, the user level determination unit 410 determines the user level of the user, i.e., the cloud server publisher. As described with reference to fig. 3, the user level may be determined according to one or more of various ways, such as a credit level, product purchasing habits, and account number type, and the like, and combinations thereof.

The policy determination unit 420 coupled to the user level determination unit 410 obtains a cloud server limit corresponding to the determined user level and the service tag of the cloud server. As described with reference to fig. 3, the cloud server limit refers to a limit that a cloud server of a corresponding service that a user has issued cannot exceed. According to one embodiment, the cloud server limitations include cloud server number limitations, computing core number limitations, network bandwidth limitations, and the like. The invention is not limited to the specific content of cloud server limitation, and all the limiting ways that the number of deployed cloud servers can be quantitatively limited are within the protection scope of the invention.

Alternatively, the policy determination unit 420 may determine the cloud server limit with reference to the service issuance policy 450. The service publishing policy 450 defines the service, the user level at which the service can be published, the cloud server limit at which the service is published, and the like. An example of a service publishing policy 450 is given above with reference to fig. 3.

The host determination unit 430 determines a host having a service tag to which the cloud server belongs. According to an embodiment, each host may be assigned a corresponding service label in advance, so that the host determination unit 430 may determine the host having the corresponding service label with reference to the assignment record.

The deployment unit 440 coupled to the policy determination unit 420 and the host determination unit 430 refers to the cloud server limit acquired by the policy determination unit, and deploys the cloud server to the host with the service tag acquired by the host determination unit 430 when the deployed cloud server does not exceed the cloud server limit.

Optionally, the deployment management apparatus 400 may further include a service label assignment unit 460. The service label allocation unit 460 obtains the software and hardware resource information of the host, and allocates a service label to the host according to the obtained software and hardware resource information. According to one embodiment, as described above with reference to fig. 1, the service label assignment unit 460 may utilize the query service 112 deployed in the host 110 to obtain and store the software and hardware resource attribute labels of the host 110. According to another embodiment, the service label allocating unit 460 may also manually obtain the software and hardware resource attributes of each host, for example, when a host is newly added to the cloud service system, the software and hardware resource attributes of the host may be manually added to the cloud server deployment management apparatus 400.

Subsequently, the service label allocation unit 460 allocates a service label to the host according to the acquired host software and hardware resource information, so as to add the service label to each host. As described above, the required software and hardware resource requirements for each service tag can be defined in advance in the preset service rule. And when the acquired software and hardware resource attributes of the host machine are matched with the defined resource requirements, distributing corresponding service labels for the host machine so as to determine the service labels of the host machine.

By utilizing the deployment management scheme provided by the invention, the labels generated by the host machines (with different software or hardware environments) in which the cloud server is deployed through the service expression can be divided into different service environments, and a service party can flexibly make a multi-service-environment user purchase matching rule aiming at a specific service release strategy and a gray scale strategy.

In addition, according to the deployment management scheme provided by the invention, a cloud server deployment scheme with user granularity can be provided, so that the flexibility of cloud server deployment is increased.

It should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into multiple sub-modules.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

Furthermore, some of the described embodiments are described herein as a method or combination of method elements that can be performed by a processor of a computer system or by other means of performing the described functions. A processor having the necessary instructions for carrying out the method or method elements thus forms a means for carrying out the method or method elements. Further, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is used to implement the functions performed by the elements for the purpose of carrying out the invention.

As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this description, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The present invention has been disclosed in an illustrative rather than a restrictive sense, and the scope of the present invention is defined by the appended claims.

Claims

1. A cloud server deployment method comprises the following steps:

acquiring user level information of a cloud server issuing party and cloud server limits corresponding to service tags of the cloud server;

acquiring a host with the service label; and

deploying the cloud server into the host with the traffic tag when the deployed cloud server does not exceed the cloud server limit.

2. The method of claim 1, further comprising the steps of:

acquiring attribute information of the host machine; and

and distributing a service label for the host machine based on the attribute information of the host machine according to a preset service rule.

3. The method of claim 2, wherein the step of obtaining attribute information of the host comprises:

and acquiring the attribute information of the host by using a query service deployed in the host.

4. A method according to claim 2 or 3, wherein said preset business rules define attribute information associated with said business label, said step of assigning a business label to a host comprising:

and if the attribute information of the host machine is matched with the attribute information defined in the preset service rule, distributing the service label to the host machine.

5. The method of any of claims 2-4, wherein the attribute information comprises software and hardware resource information.

6. The method of any of claims 1-5, the step of obtaining cloud server restrictions corresponding to the user level information and business tags comprising:

and determining the cloud server limit corresponding to the user level and the service label by referring to a service publishing policy, wherein the service publishing policy defines a specific service, the user level capable of publishing the service and the cloud server limit.

7. The method of claim 6, wherein the cloud server limitations include one or more of: the number of cloud servers and the number of computing cores of the cloud servers.

8. The method of claim 6 or 7, wherein the traffic publishing policy further defines a scheduling policy associated with a particular traffic, the scheduling policy indicating whether a cloud server having a particular traffic label is to be deployed in a host having the particular traffic label at all times.

9. The method of any of claims 1-8, the step of determining a user level of a cloud server publisher comprising:

determining the user level from one or more of the following attributes of the user: credit level, product purchasing habits, and account number type.

10. A cloud server deployment management apparatus comprising:

the user level determining unit is suitable for determining the user level of the cloud server publisher;

a policy determination unit adapted to obtain cloud server restrictions corresponding to the user level and a service tag of the cloud server;

the host machine determining unit is suitable for acquiring the host machine with the service label; and

a deployment unit adapted to deploy the cloud server to the host with the business label when the deployed cloud server does not exceed the cloud server limit.

11. The management device of claim 10, further comprising:

and the service label distribution unit is suitable for acquiring the attribute information of the host machine and distributing the service label to the host machine based on the acquired attribute information according to a preset service rule.

12. The management device according to claim 11, wherein the traffic label assigning unit is further adapted to receive attribute information of the host obtained by the query service in the host.

13. The management device according to claim 11 or 12, wherein the preset business rule defines attribute information associated with the business label, the business label assigning unit is further adapted to assign the business label to the host when the attribute information of the host matches the attribute information defined by the preset business rule.

14. The management device according to any one of claims 11 to 13, wherein the attribute information includes software and hardware resource information.

15. The management device of any of claims 10-14, further comprising

A service release policy defining a specific service, a user level at which the service can be released, and cloud server restrictions;

the policy determination unit is adapted to determine cloud server restrictions corresponding to the user level and the service tag with reference to the service publishing policy.

16. The management device of claim 15, wherein the cloud server limitations include one or more of: the number of cloud servers and the number of computing cores of the cloud servers.

17. The management device according to claim 15 or 16, wherein the service publishing policy further defines a scheduling policy associated with a particular service, the scheduling policy indicating whether a cloud server having a particular service label is to be deployed in a host having the particular service label at all times.

18. The management device according to any of claims 10-17, the user level determination unit being adapted to determine the user level based on one or more of the following attributes of a user: credit level, product purchasing habits, and account number type.

19. A computing device, comprising:

at least one processor; and

a memory storing program instructions configured for execution by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 1-9.