WO2016041202A1

WO2016041202A1 - Deployment method and apparatus based on cloud environment system

Info

Publication number: WO2016041202A1
Application number: PCT/CN2014/086952
Authority: WO
Inventors: 吴君怡; 李蔚海
Original assignee: 华为技术有限公司
Priority date: 2014-09-19
Filing date: 2014-09-19
Publication date: 2016-03-24
Also published as: CN105612727B; CN105612727A

Abstract

Embodiments of the present invention relate to the technical field of communications. Disclosed are a deployment method and apparatus based on a cloud environment system, so as to improve the deployment efficiency. The deployment method based on a cloud environment system in an embodiment of the present invention comprises: a control module determines a to-be-deployed first node in a cloud environment system; the control module acquires the node type of the first node; the control module matches the node type of the first node with a node type in a preset table, so as to obtain a set of deployment units that can be deployed to the first node; the control module selects, according to a policy corresponding to a deployment unit in the set of deployable deployment units, a deployment unit that needs to be deployed to the first node in the set of deployable deployment units; and the control module deploys the deployment unit that needs to be deployed to the first node. The technical solution provided in the embodiments of the present invention can be used in a cloud environment system.

Description

Deployment method and device based on cloud environment system

Technical field

The present invention relates to the field of communications technologies, and in particular, to a deployment method and apparatus based on a cloud environment system.

Background technique

The SOA (Service-Oriented Architecture)-based cloud environment system includes a control platform and multiple nodes. The control platform utilizes the computing power of the cloud computing and the SOA scheduling capability to uniformly manage and schedule the processes deployed on each node. This provides on-demand web services for individuals and businesses.

Currently, the process in each node of the cloud environment system is deployed in a static configuration manner. Specifically, the to-be-deployed process in the node to be deployed is pre-deployed into a software package; The package starts the process in the package.

In the process of the above deployment process, the default value of which processes are deployed in which nodes is determined by the user experience, so that an inexperienced user generally has difficulty setting the processes to be deployed for each node in a short time, thereby Lead to less efficient deployment.

Summary of the invention

Embodiments of the present invention provide a deployment method and apparatus based on a cloud environment system to improve deployment efficiency.

In order to achieve the above object, embodiments of the present invention adopt the following technical solutions:

In a first aspect, a method for deploying a cloud environment based system is provided, including:

The control module determines the first node to be deployed in the cloud environment system;

The control module acquires a node type of the first node;

The control module compares a node type of the first node with a node class in a preset table The matching is performed to obtain a set of deployment units that can be deployed by the first node; wherein the preset table is used to record a correspondence between a node type and a deployment unit that can be deployed by a node having the node type;

The control module selects, according to a policy corresponding to the deployment unit in the deployable deployment unit set, a deployment unit that needs to be deployed by the first node in the set of deployable deployment units;

The control module deploys the deployment unit to be deployed in the first node.

With reference to the first aspect, in a first possible implementation, the determining, by the first node to be deployed, includes:

The node that is being started in the system is determined to be the first node to be deployed, or the node that is determined to be actually deployed in the system is different from the pre-deployed deployment unit is the first node to be deployed.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation, the policy corresponding to the deployment unit in the deployable deployment unit set includes: a general policy, a single policy, Quantity policy, node type policy, resource policy.

In conjunction with the second possible implementation of the first aspect, in a third possible implementation, the deployable deployment unit is configured according to a policy corresponding to a deployment unit in the deployable deployment unit set Selecting the deployment unit to be deployed by the first node in the collection, including:

When the policy corresponding to the deployment unit in the deployable deployment unit set includes a single policy or a quantity policy, according to the policy corresponding to the deployment unit in the deployable deployment unit set and the deployment unit in other nodes in the system, Selecting, in the set of deployable deployment units, a deployment unit to be deployed by the first node;

Or, when the policy corresponding to the deployment unit in the deployable deployment unit set includes a resource policy, selecting the first one of the deployable deployment unit sets according to the resource policy and the resource of the first node The deployment unit that the node needs to deploy.

In combination with the first aspect, the first possible implementation manner of the first aspect, or the third possible implementation manner, in the fourth possible implementation manner, where the deployment unit to be deployed is deployed After the first node, the method further includes:

At least one of the first nodes is migrated under a trigger condition.

In conjunction with the fourth possible implementation of the first aspect, in the fifth possible implementation, the migrating the at least one of the first nodes includes:

Deleting at least one deployment unit of the first node;

And deleting the deleted at least one deployment unit in other nodes in the system according to the policy corresponding to the deleted at least one deployment unit.

With reference to the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner, in a sixth possible implementation manner, the triggering condition includes at least one of: a deployment unit in the first node The occupied resource is greater than or equal to a threshold, and at least one deployment unit in the first node is faulty, and the load of the system in which the first node is located is less than or equal to a threshold.

In combination with the fourth possible implementation manner of the first aspect, the sixth possible implementation manner, in the seventh possible implementation manner, the migrating the at least one deployment unit of the first node, including :

Determining n migratable deployment units in the first node; wherein n>1, n is an integer;

Determining a migration order of the n migratable deployment units according to a migration weight of the n migratable deployment units;

The n migratable deployment units are sequentially migrated according to the migration order.

With reference to the first aspect, the first possible implementation manner of the first aspect, and the seventh possible implementation manner, in the eighth possible implementation manner, where the deployment unit to be deployed is deployed After the first node, the method further includes:

When the first node is no longer a node in the system, at least one of the first nodes is deployed in other nodes in the system.

With reference to the eighth possible implementation of the first aspect, in the ninth possible implementation, the deploying the at least one deployment unit of the first node in another node in the system includes:

Selecting a target node for at least one of the first nodes according to a policy corresponding to at least one of the first nodes;

At least one deployment unit of the first node is deployed in the target node.

With reference to the first aspect, the first possible implementation manner of the first aspect, and the ninth possible implementation manner, in a tenth possible implementation manner, the deployment unit includes at least one of the following: a process, Process group, virtual machine, application system.

The second aspect provides a deployment method based on a cloud environment system, including:

Determining a policy corresponding to the deployment unit to be deployed and the deployment unit to be deployed;

Selecting a target node for the deployment unit to be deployed according to the policy corresponding to the deployment unit to be deployed;

The unit to be deployed is deployed in the target node.

With reference to the second aspect, in a first possible implementation, the policy corresponding to the deployment unit to be deployed includes: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation, the selecting a target node for the to-be-deployed unit according to the policy corresponding to the deployment unit to be deployed includes:

When the policy corresponding to the deployment unit to be deployed includes a single policy or a quantity policy, the target node is selected for the to-be-deployed unit according to the policy corresponding to the deployment unit to be deployed and the deployment unit in other nodes in the system;

Or, when the policy corresponding to the deployment unit to be deployed includes a resource policy, select a target node for the deployment unit to be deployed according to the resource policy and resources of other nodes in the system.

With reference to the second aspect, the first possible implementation manner of the second aspect, or the second possible implementation manner, in a third possible implementation manner, the deployment unit to be deployed includes at least one of the following: a process, Process group, virtual machine, application system.

In a third aspect, a deployment device based on a cloud environment system is provided, including:

a storage module, configured to store a preset table, where the preset table is used to record a correspondence between a node type and a deployment unit deployable by a node having the node type;

Processing module for performing the following actions:

Determining a first node to be deployed in a cloud environment system;

Obtaining a node type of the first node;

Matching the node type of the first node with the node type in the preset table to obtain a deployment unit set that can be deployed by the first node;

Selecting, according to a policy corresponding to the deployment unit in the deployable deployment unit set, a deployment unit that needs to be deployed by the first node in the set of deployable deployment units;

Deploying the deployment unit to be deployed in the first node.

With reference to the third aspect, in a first possible implementation manner, the processing module is specifically configured to: determine that a node that is being started in the system is a first node to be deployed, or determine a deployment unit that is actually running in the system and the foregoing The different nodes of the deployed deployment unit are the first nodes to be deployed.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in a second possible implementation, the policy corresponding to the deployment unit in the deployable deployment unit set includes: a general policy, a single policy, Quantity policy, node type policy, resource policy.

In conjunction with the second possible implementation of the third aspect, in a third possible implementation, the processing module is specifically configured to:

In combination with the third aspect, the first possible implementation manner of the third aspect, or the third possible implementation manner, in a fourth possible implementation manner, the processing module is further configured to be used under a trigger condition Relocating at least one of the first nodes.

In conjunction with the fourth possible implementation of the third aspect, in a fifth possible implementation, the processing module is specifically configured to:

Deleting at least one deployment unit of the first node;

With reference to the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner, in a sixth possible implementation manner, the triggering condition includes at least one of: a deployment unit in the first node The occupied resource is greater than or equal to a threshold, and at least one deployment unit in the first node is faulty, and the load of the system in which the first node is located is less than or equal to a threshold.

With reference to the fourth possible implementation of the third aspect, the sixth possible implementation manner, in the seventh possible implementation, the processing module is specifically configured to:

With reference to the third aspect, the first possible implementation manner of the third aspect, and the seventh possible implementation manner, in the eighth possible implementation manner, the processing module is further configured to: when the When a node is no longer a node in the system, at least one of the first nodes is deployed in other nodes in the system.

In conjunction with the eighth possible implementation of the third aspect, in a ninth possible implementation, the deployment module is specifically configured to:

At least one deployment unit of the first node is deployed in the target node.

With reference to the third aspect, the first possible implementation manner of the third aspect, and the ninth possible implementation manner, in a tenth possible implementation manner, the deployment unit includes at least one of the following: a process, Process group, virtual machine, application system.

The fourth aspect provides a deployment device based on a cloud environment system, including:

Processing module for performing the following actions:

Deploying the to-be-deployed unit in the target node;

And a storage module, configured to store a policy corresponding to the deployment unit to be deployed. With reference to the fourth aspect, in a first possible implementation manner, the policy corresponding to the deployment unit to be deployed includes: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.

In conjunction with the first possible implementation of the fourth aspect, in a second possible implementation, the processing module is specifically configured to:

With reference to the fourth aspect, the first possible implementation manner of the fourth aspect, or the second possible implementation manner, in a third possible implementation manner, the deployment unit to be deployed includes at least one of the following: a process, Process group, virtual machine, application system.

A fifth aspect provides a cloud environment system-based deployment apparatus, including: a memory and a processor;

The memory is for storing a set of codes for controlling the processor Do the following actions:

Determining a first node to be deployed in a cloud environment system;

Obtaining a node type of the first node;

Matching the node type of the first node with the node type in the preset table to obtain a deployment unit set that can be deployed by the first node; wherein the preset table is used to record a node type and have the node type Correspondence between deployment units of nodes that can be deployed;

Deploying the deployment unit to be deployed in the first node.

With reference to the fifth aspect, in a first possible implementation manner, the processor is specifically configured to:

With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, in a second possible implementation, the policy corresponding to the deployment unit in the deployable deployment unit set includes: a general policy, a single policy, Quantity policy, node type policy, resource policy.

In conjunction with the second possible implementation of the fifth aspect, in a third possible implementation, the processor is specifically configured to:

When the policy corresponding to the deployment unit in the deployable deployment unit set includes a single policy or a quantity policy, according to the deployment order in the deployable deployment unit set a policy corresponding to the element and a deployment unit in the other nodes in the system, and selecting, in the set of deployable deployment units, the deployment unit to be deployed by the first node;

With reference to the fifth aspect, the first possible implementation manner of the fifth aspect, and the third possible implementation manner, in a fourth possible implementation manner, the processor is further configured to:

At least one of the first nodes is migrated under a trigger condition.

In conjunction with the fourth possible implementation of the fifth aspect, in a fifth possible implementation, the processor is specifically configured to:

Deleting at least one deployment unit of the first node;

With reference to the fourth possible implementation manner of the fifth aspect, or the fifth possible implementation manner, in a sixth possible implementation manner, the triggering condition includes at least one of the following: a deployment unit in the first node The occupied resource is greater than or equal to a threshold, and at least one deployment unit in the first node is faulty, and the load of the system in which the first node is located is less than or equal to a threshold.

With reference to the fourth possible implementation manner of the fifth aspect, the sixth possible implementation manner, in the seventh possible implementation manner, the processor is specifically configured to:

Determining the n migrateable according to the migration weights of the n migratable deployment units The migration order of the deployment unit;

With reference to the fifth aspect, the first possible implementation manner of the fifth aspect, and the seventh possible implementation manner, in the eighth possible implementation manner, the processor is further configured to:

In conjunction with the eighth possible implementation of the fifth aspect, in a ninth possible implementation, the processor is specifically configured to:

At least one deployment unit of the first node is deployed in the target node.

With reference to the fifth aspect, the first possible implementation manner of the fifth aspect, and the ninth possible implementation manner, in the tenth possible implementation manner, the deployment unit includes at least one of the following: a process, Process group, virtual machine, application system.

a sixth aspect provides a cloud environment system-based deployment apparatus, including a memory and a processor;

The memory is for storing a set of codes for controlling the processor to perform the following actions:

Determining, in the cloud environment system, a policy corresponding to the deployment unit to be deployed and the deployment unit to be deployed;

The unit to be deployed is deployed in the target node.

With reference to the sixth aspect, in a first possible implementation, the policy corresponding to the deployment unit to be deployed includes: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.

In conjunction with the first possible implementation of the sixth aspect, in a second possible implementation, the processor is specifically configured to:

With reference to the sixth aspect, the first possible implementation manner of the sixth aspect, or the second possible implementation manner, in a third possible implementation manner, the deployment unit to be deployed includes at least one of the following: a process, Process group, virtual machine, application system.

The cloud environment system-based deployment method and apparatus provided by the embodiment of the present invention determine the node type of the first node and the first node to be deployed, and determine the deployable deployment unit set according to the node type of the first node, and then Determining the deployment units to be deployed by the first node according to the policy corresponding to the deployment unit in the deployable deployment unit set, so that the deployed deployment units are deployed in the first node. That is to say, the embodiment of the present invention can deploy a node by using an automatic control method; compared with the prior art, manual deployment is not required, thereby improving deployment efficiency.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present invention, and those skilled in the art can obtain other drawings according to the drawings without any creative work.

FIG. 1 is a flowchart of a method for deploying a cloud environment system according to Embodiment 1 of the present invention;

2 is a flowchart of a method for deploying a cloud environment system according to Embodiment 2 of the present invention;

3 is a flowchart of a method for deploying a cloud environment system according to Embodiment 3 of the present invention;

4 is a schematic structural diagram of a deployment apparatus based on a cloud environment system according to Embodiment 4 of the present invention;

FIG. 5 is a schematic structural diagram of a deployment apparatus based on a cloud environment system according to Embodiment 5 of the present invention; FIG.

6 is a schematic structural diagram of a deployment apparatus based on a cloud environment system according to Embodiment 6 of the present invention;

FIG. 7 is a schematic structural diagram of a cloud environment system-based deployment apparatus according to Embodiment 7 of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The term "and/or" in this article is merely an association describing the associated object, the table There may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. The character "/" in this article generally indicates that the contextual object is an "or" relationship. In addition, the term "plurality" herein means two or more.

The cloud environment system-based deployment method provided by the embodiment of the present invention is described in the following two aspects: "how to determine the deployment unit to be deployed for the node to be deployed" and "how to determine the target node for the deployment unit to be deployed".

Embodiment 1

This embodiment describes a cloud environment system-based deployment method provided by an embodiment of the present invention by using the "how to determine the deployment unit to be deployed for the node to be deployed." As shown in FIG. 1 , the cloud environment system-based deployment method provided by this embodiment includes:

101. The control module determines a first node to be deployed in the cloud environment system.

The execution body of the cloud environment system-based deployment method provided by the embodiment of the present invention may be a control module. The cloud environment system-based deployment method provided by the embodiment of the present invention can be applied to an SOA-based cloud environment system; in this case, the control module can be integrated in a device independent of the cloud environment system, or can be integrated in the system. In any device. In addition, the cloud environment system-based deployment method provided by the embodiment of the present invention may also be applied to a physical device; in this case, the control module may be integrated in a device independent of the physical device, or may be in the physical device. Processor. The following applies to an SOA-based cloud environment system (referred to as "system") as an example.

The "first node" can be any physical node or logical node that runs the deployment unit. The deployment unit may include at least one of the following: a process, a process group, a virtual machine, an application system; wherein the process group is composed of multiple processes. It should be noted that, all the processes in a process group are bound together according to a certain rule, and the specific setting manner of the rule is not limited in the embodiment of the present invention. In general, all processes in a process group are simultaneously The department was moved or removed at the same time. In a specific implementation, some processes can be bound to a process group according to requirements, and the process group is used as a deployment unit.

Optionally, the step 101 may include: determining that the node being started in the system is the first node to be deployed, or determining that the node that is actually running in the system is different from the pre-deployed deployment unit is the first node to be deployed. . Exemplarily, "starting" includes: initial startup or restart; "nodes that are initially started in the system" include: new nodes or existing nodes that are initially started in the system; "pre-deployed deployment units" may Each deployment unit that needs to be deployed for the node that is pre-stored may also be a deployment unit that needs to be deployed for the node before the control module performs step 101.

It should be noted that, in a specific implementation, the control module may simultaneously deploy multiple first nodes according to the method provided by the embodiment of the present invention.

102. The control module acquires a node type of the first node.

The embodiment of the present invention does not limit the manner of the "node type", and can be implemented by using the method in the prior art. For example, the "node type" can be classified into a storage type, a switch type, a forwarding type, a calculation type, and a signaling type. Wait.

The control module executing step 102 can obtain the node type of the first node by means of information interaction or direct reading.

103. The control module matches a node type of the first node with a node type in a preset table, to obtain a deployment unit set that can be deployed by the first node, where the preset table is used to record a node. The correspondence between a type and a deployment unit that can be deployed by a node with that node type.

In order to clearly illustrate the technology provided by the embodiment of the present invention, the following two concepts are first described: "a deployment unit with a node type deployable" refers to a deployment unit that can theoretically be deployed on a node having the node type; A deployment unit to be deployed on a node refers to a deployment unit that can be deployed on the node according to actual conditions, that is, when The deployment unit that needs to be deployed in this node before.

The manner of setting the correspondence between the "node type" and the "deployable unit deployable by the node having the node type" is not limited in the embodiment of the present invention. The number of deployment units that can be deployed by a node having the node type corresponding to a node type may be one or more. Generally, different nodes with the same node type can deploy the same deployment unit, and different nodes with different node types can deploy the deployment units partially or completely the same or different. The "first node deployable set of deployment units" may be composed of one or more deployment units that the first node may deploy.

The “preset table” may be pre-stored in the device where the control module is located, and the control module may match the node type of the first node with the node type in the preset table after acquiring the node type of the first node, and The deployment unit corresponding to the node type of the node type of the first node in the table constitutes a deployment unit set that the first node can deploy. The expressions of "preset tables" include but are not limited to: tables, charts, and the like.

The control module selects, according to the policy corresponding to the deployment unit in the deployable deployment unit set, the deployment unit that needs to be deployed by the first node in the set of deployable deployment units.

The policy corresponding to the deployment unit may be a policy defined in advance for the deployment unit, or a policy obtained through a policy customization interface. The policy customization interface is used to enable the application to customize a specific policy. The method for setting the policy corresponding to the deployment unit is not limited in the embodiment of the present invention. In specific implementation, the policy corresponding to the deployment unit may be set according to factors such as the application scenario and the purpose of the deployment unit. The number of policies corresponding to one deployment unit may be one or more; the policies corresponding to different deployment units may be the same or different.

Exemplarily, the policies corresponding to the deployment unit may include but are not limited to the following:

1. General strategy: deploy the corresponding deployment unit in each node in the system. Strategy.

2. Single strategy: A policy in which only the corresponding deployment unit is deployed in one node in the system.

3. Quantity Policy: A policy that limits the number of deployed deployment units in the system and/or any one or more nodes. For example, the quantity policy corresponding to the deployment unit A is: deploying the corresponding deployment unit on at least one and up to five nodes in the system, and deploying at least two corresponding deployment unit policies in each node.

4. Node type policy: A policy in which the corresponding deployment unit is deployed in a node of the system having the node type.

5. Resource policy: A policy that limits the available resources of the nodes deployed by the corresponding deployment unit; wherein the "available resources" may include at least one of the following: available hard disks, available memory, available capacity, available bandwidth, and the like.

It should be noted that a deployment unit corresponds to at least one of “single policy, quantity policy, and general policy”; in addition, since “the deployable deployment unit” in this embodiment is determined according to the node type, step 103 is performed. The resulting deployable deployment units all meet the node type policy.

Optionally, step 104 may include:

Or, when the policy corresponding to the deployment unit in the deployable deployment unit set includes a resource policy, selecting the first one of the deployable deployment unit sets according to the resource policy and the resource of the first node The deployment unit to be deployed by the node; wherein the resource of the first node may specifically be an available resource of the first node.

It should be noted that, because the deployment unit set to be deployed by the first node is determined by the policy of the deployable deployment unit set corresponding to the deployment unit in the deployable deployment unit set; further, it may also be in other nodes. The deployment unit, or the available resources of the first node, are determined; therefore, in the specific implementation, the deployment unit to be deployed by the first node may be empty; in this case, no deployment unit is deployed to the first node.

105. The control module deploys the deployment unit to be deployed in the first node.

To illustrate the specific implementation of step 105, the concept of the first node device is proposed in this document. Specifically, when the first node is a logical node, the first node device refers to the physical device where the first node is located; when the first node is In the case of a physical node, the first node device and the first node represent the same physical device.

The step 105 may specifically include: when the device where the control module is located is different from the first node device, the control module sends an indication message to the first node, where the indication message includes information indicating the deployment unit to be deployed, The first node runs the deployment unit to be deployed according to the indication message; when the device where the control module is located is the same as the first node device, the control module controls the deployment unit to be deployed to run in the first node. It should be noted that the related instruction file of the deployment unit that the first node can deploy is pre-stored in the first node device.

It should be noted that the deployment unit will always run once deployed to the node, unless the deployment unit fails, or is deleted, or the node is faulty; therefore, if not stated, the "nodes" mentioned in this article "Deployment unit" refers to the node that actually runs in this node. The "deployment unit to be deployed" in step 105 can be used as the pre-deployed deployment unit corresponding to the first node when step 101 is executed next time.

The cloud environment system-based deployment method provided by the embodiment of the present invention determines the node type of the first node and the first node to be deployed, and according to the node class of the first node Determining the set of deployment units that can be deployed, and determining the deployment units to be deployed by the first node according to the policy corresponding to the deployment unit in the deployable deployment unit set, thereby deploying the deployed deployment units in the first node. . That is to say, the embodiment of the present invention can deploy a node by using an automatic control method; compared with the prior art, manual deployment is not required, thereby improving deployment efficiency.

In an embodiment of the present invention, after step 105, the method may further include: migrating at least one of the first nodes in a trigger condition. Specifically, the migrating the at least one deployment unit of the first node may include: deleting at least one deployment unit of the first node; and deleting the deleted according to a policy corresponding to the deleted at least one deployment unit At least one deployment unit is deployed in other nodes in the system.

Exemplarily, the "trigger condition" in the optional implementation may include, but is not limited to, at least one of the following: the resource occupied by the deployment unit in the first node is greater than or equal to a threshold; at least one of the first nodes A deployment unit fails; the load of the system where the first node is located is less than or equal to a threshold.

The “resources occupied by the deployment unit in the first node” include, but are not limited to, the following: the ratio of the capacity of the deployment unit in the first node to the total capacity of the hard disk, and the capacity of the deployment unit in the first node. The proportion of the total memory capacity. "Deployment unit failure" can be understood as: the deployment unit is unable to provide services properly. When the load of a system is small, the deployment units in one or more nodes can be migrated to other deployment units; of course, some deployment units can be shut down. It should be noted that, compared with a deployment unit in the prior art, the optional method can implement flexible configuration of the deployment unit, thereby improving system resource utilization.

Optionally, the migrating the at least one deployment unit in the first node may include: determining n migratable deployment units in the first node; n>1, n being an integer; and migrating weight values according to n migratable deployment units Determine the migration order of n migratable deployment units; press N migrateable deployment units are migrated in sequence according to the migration order.

Exemplarily, any deployment unit in the first node may correspond to a migration weight, which is used to represent the cost of the deployment unit to migrate out of the first node; the cost may specifically be reliability of the system or The impact of availability, where the impact on the availability of the system can be an impact on the business in the system (eg, causing business disruptions, etc.). The smaller the migration weight corresponding to a deployment unit in the first node, the greater the cost of migrating the deployment unit out of the first node. The corresponding migration weights of the same deployment unit in different nodes may be the same or different. The control node may set a corresponding migration weight value of each deployment unit in the first node when deploying the deployment unit for the first node.

The "migrated deployment unit" refers to a deployment unit that can be migrated to other nodes under certain conditions; the specific setting of the condition is not limited in the embodiment of the present invention. In a specific implementation, the deployment unit of the first node whose corresponding migration weight is greater than or equal to a threshold may be used as the migratable deployment unit in the first node.

The specific implementation manner of determining the n migratable deployment units in the first node is not limited in the embodiment of the present invention, for example, may be determined according to the “trigger condition”. Specifically, when the triggering condition is that the resource occupied by the deployment unit in the first node is greater than or equal to a threshold, the deployment unit that is greater than a threshold and whose migration weight is greater than a threshold may be used in the first node. As n migrateable deployment units; when the trigger condition is that at least one deployment unit in the first node is faulty, the at least one deployment unit may be used as n migratable deployment units; when the trigger condition is the system where the first node is located When the load is less than or equal to a threshold, the deployment unit in the first node and the migration weight greater than a threshold may be used as the n migratable deployment units.

It should be noted that when the number of deployable deployment units in the first node is 1, the migrateable deployment unit may be directly migrated.

In another embodiment of the present invention, after step 105, the method may further include: when the first node is no longer a node in the system, the first node At least one of the deployment units is deployed in other nodes in the system. The method may include: selecting, according to a policy corresponding to the at least one deployment unit of the first node, a target node for at least one deployment unit of the first node; deploying at least one deployment unit of the first node in the In the target node.

Exemplarily, "the first node is no longer a node in the system" can be understood as the first node being removed from the system. It should be noted that the specific implementation method of “selecting a target node according to a policy corresponding to at least one deployment unit of the first node to at least one deployment unit in the first node” may refer to a related description in the following.

Embodiment 2

In this embodiment, the cloud environment system-based deployment method provided by the foregoing embodiment is described by using the method of how to configure the node to be deployed. In this embodiment, the node where the control module is located is taken as an example. The control node is different from the first node to be deployed. As shown in FIG. 2, the cloud environment system-based deployment method provided by this embodiment includes:

201: The control node uses the discovered one node as the first node to be deployed, and acquires the logical identifier of the first node.

A node discovered by the control node may be a node initially started in the system (including: a new node in the system or a node already existing in the system), or a node restarted in the system. This embodiment does not limit the implementation method of the first node to be found by the control node, and can be implemented, for example, by using the method in the prior art.

After any node in the system is initially started, the control module assigns a logical identifier to it, and records the logical identifier in a preset logical identifier set. In the subsequent process, the control module uses the logical identifier to communicate with the node. The preset logical identifier set is a set formed by the logical identifier assigned by the control node to the nodes in the system, and the preset logical identifier set is updated as the nodes in the system are updated.

When the first node is a node that is initially started in the system, the control module has not assigned a logical identifier to the first node. In this case, the logical identifier of the first node acquired by the control node is empty. In addition, in this case, The logical identifier of the first node acquired by the control node may also be a logical identifier assigned by the control node in the other system when the first node is in another system. When the first node is a node that is restarted in the system, the control node has assigned a logical identifier to the first node. In this case, the logical identifier of the first node acquired by the control node is one of the preset logical identifier sets. Logical identity.

202: The control node determines whether the logical identifier belongs to a preset logical identifier set.

If the node is a node that is restarted in the system, step 203 is performed; if not, the node is an initial node in the system or a new node in the system, and step 205 is performed.

Steps 201-202 may be referred to as a process in which the control node determines a deployment scenario, where the deployment scenario is a restart scenario or an initial startup scenario. Certainly, the deployment scenario may be determined by other methods, which is not limited in this embodiment.

It should be noted that, in a specific implementation, if the determination result in step 202 is no, before performing step 205, the method may further include: assigning a logical identifier to the first node, and adding the assigned logical identifier to the preset In the logical identification set; in a subsequent process, the control node uses the logical identifier to communicate with the first node.

203. The control node acquires a deployment unit that is actually running in the first node.

It should be noted that, in a specific implementation, when there is no node in the system, the control node may also perform step 203 under the trigger condition; that is, the control node may execute without performing steps 201-202. Step 203, in this case, the "first node" is a node that has been started in the system. The specific setting manner of the trigger condition is not limited in the embodiment of the present invention, for example, periodically.

204. The control node determines a deployment unit and a pre-deployment actually running in the first node. Whether the deployment unit is consistent.

If no, indicating that the first node needs to be re-deployed, step 205 is performed; if yes, the first node is not required to be deployed, and then ends.

Optionally, in a specific implementation, if the determination result in step 204 is no, the method may further include: the control node sending a deletion indication message to the first node, where the deletion indication message is used to delete the actual operation of the first node. All deployment units; the first node deletes all deployment units that it actually runs according to the delete message indication. This optional method can avoid the problem of poor deployment accuracy when deploying the deployment unit to be deployed for the first node due to the deployment node already deployed in the first node.

In addition, if the determination result in step 204 is no, only the running, non-pre-deployed deployment unit may be deleted, and the deployment unit that is not deployed in the pre-deployed deployment unit is deployed in the first node.

205. The control node acquires a node type of the first node.

206. The control node matches the node type of the first node with the node type in the preset table to obtain a deployment unit set that can be deployed by the first node.

As shown in Table 1, it is a schematic diagram of a preset table:

Table 1

节点类型Node type	可部署的部署单元Deployable deployment unit
节点类型Node type	可部署的部署单元Deployable deployment unit	节点类型1Node type 1	部署单元A、部署单元B、部署单元C、部署单元DDeployment unit A, deployment unit B, deployment unit C, deployment unit D
节点类型2Node type 2	部署单元A、部署单元B、部署单元C、部署单元DDeployment unit A, deployment unit B, deployment unit C, deployment unit D	节点类型1Node type 1
节点类型2Node type 2		节点类型3Node type 3	部署单元A、部署单元C、部署单元DDeployment unit A, deployment unit C, deployment unit D
节点类型4Node type 4	部署单元EDeployment unit E	节点类型3Node type 3
节点类型4Node type 4	部署单元EDeployment unit E	……......	……......

Assuming that the node type of the first node is node type 1, according to the preset table shown in Table 1, the set of deployment units that can be deployed by the first node obtained in step 206 is: a deployment list. Element A, deployment unit B, deployment unit C, and deployment unit D.

207. The control node acquires a policy corresponding to the deployment unit in the deployable deployment unit set.

Based on the example in step 206, it is assumed that the policies corresponding to deployment unit A and deployment unit B are as shown in Table 2:

Table 2

208. The control node selects a deployment unit to be deployed by the first node according to a policy corresponding to each deployment unit in the deployable deployment unit set.

Based on the example in step 207, the specific implementation of step 208 is illustrated below:

1), for the deployment unit A: determining whether the number of nodes in the system where the deployment unit A has been deployed is greater than or equal to 5, and if so, determining that the deployment unit A is not the deployment unit to be deployed by the first node; Whether there is an available hard disk in the first node, if not, it is determined that the deployment unit A is not the deployment unit to be deployed by the first node; if yes, it is determined that the deployment unit A is the deployment unit to be deployed on the first node.

2), for the deployment unit B: determining whether the deployment unit B has been deployed in the system, and if so, determining that the deployment unit B is not the deployment unit to be deployed by the first node; if not, determining that the deployment unit B is the first node The deployed deployment unit.

3) For deployment unit C: Determine deployment unit C as the deployment unit to be deployed on the first node.

4), for the deployment unit D: determining whether the first node has available memory, if not, determining that the deployment unit D is not the deployment unit to be deployed by the first node; if yes, determining that the deployment unit D is the first node to be deployed Deployment unit. It should be noted that, in this embodiment, the deployment unit D must conform to the node type policy, and the specific reason is referred to the foregoing embodiment 1.

209: The control node deploys the deployment unit to be deployed in the first node.

Based on the example in step 207, the deployment unit to be deployed obtained in step 208 is deployed in the first node. If the deployment unit A is a deployment unit to be deployed, the number of deployment units A deployed in the first node cannot exceed two (that is, the quantity policy in Table 2 is satisfied).

The cloud environment system-based deployment method provided by the embodiment of the present invention determines the node type of the first node and the first node to be deployed, and determines the deployable deployment unit set according to the node type of the first node, and then according to the The policy corresponding to the deployment unit in the deployable deployment unit set determines the deployment unit that the first node needs to deploy, so that the deployed deployment units are deployed in the first node. That is to say, the embodiment of the present invention can deploy a node by using an automatic control method; compared with the prior art, manual deployment is not required, thereby improving deployment efficiency.

Embodiment 3

This embodiment describes a cloud environment system-based deployment method provided by an embodiment of the present invention by using the method of "how to determine a target node for a deployment unit to be deployed." As shown in Figure 3 The cloud environment system-based deployment method provided by this embodiment includes:

301. The control module determines, in the cloud environment system, a policy corresponding to the deployment unit to be deployed and the deployment unit to be deployed.

This embodiment can be applied to a scenario in which a deployment unit is added to a system or a deployment unit that exists in the system is migrated. That is to say, the "deployment unit to be deployed" in this embodiment may be a new deployment unit in the system, or may be a deployment unit that has been deployed in one or more nodes in the system.

Optionally, the deployment unit to be deployed includes at least one of the following: a process, a process group, a virtual machine, and an application system.

Optionally, the policy corresponding to the deployment unit to be deployed may include, but is not limited to, any one of the following: a general policy, a single policy, a quantity policy, a node type policy, a resource policy, and the like.

It should be noted that a deployment unit corresponds to at least one of “single policy, quantity policy, and general policy”. In addition, the explanations of terms such as the policy corresponding to the deployment unit to be deployed, the process group, the general policy, the single policy, the quantity policy, the node type policy, and the resource policy may be referred to in the above embodiment. The first embodiment is not described here.

302. The control module selects a target node for the deployment unit to be deployed according to the policy corresponding to the deployment unit to be deployed. Specifically, a node that satisfies a policy corresponding to the deployment unit to be deployed is used as the target node.

Optionally, step 302 may include:

Or, when the policy corresponding to the deployment unit to be deployed includes a resource policy, the root The target node is selected for the deployment unit to be deployed according to the resource policy and resources of other nodes in the system. The resources of other nodes may specifically be available resources of other nodes.

Assuming that the deployment unit to be deployed is the deployment unit A, step 302 can be implemented as follows:

1) When the policy corresponding to deployment unit A is a general policy, all nodes in the system are used as target nodes.

2) When the policy corresponding to the deployment unit A is a single policy, it is determined whether the deployment unit A has been deployed in the system; if yes, the process ends; if not, any node in the system is used as the target node.

3) When the policy corresponding to the deployment unit A is a quantity policy (for example, the quantity policy is: when the corresponding deployment unit is deployed on at least one and at most five nodes in the system, it is determined that the deployment unit has been deployed in the system) Whether the number of nodes of A is greater than or equal to 5, and if so, ends, if not, selects at least one and at most 5 nodes in the system as target nodes.

4) When the policy corresponding to the deployment unit A is a node type policy, one or more nodes having the node type in the system are used as target nodes.

5) When the policy corresponding to deployment unit A is a resource policy (for example, the resource policy is: the corresponding deployment unit is deployed in a node with available memory), one or more available memory in the system The node acts as the target node.

It should be noted that, in a specific implementation, a deployment unit may also correspond to multiple policies, and those skilled in the art should be able to infer the specific implementation steps in this case from the above examples, and will not be described herein.

303. The control module deploys the to-be-deployed unit in the target node.

For example, the specific implementation manner of step 303 in the foregoing Embodiment 1 may refer to the specific implementation manner of step 105 in the foregoing Embodiment 1. It should be noted that the field provided in this embodiment In the scene, the relevant instruction file of the unit to be deployed may be pre-stored in the target node.

The cloud environment system-based deployment method provided by the embodiment of the present invention determines a policy corresponding to the deployment unit to be deployed and the deployment unit to be deployed, and selects a target for the to-be-deployed unit according to the policy corresponding to the deployment unit to be deployed. A node, thereby deploying the deployment unit to be deployed in the target node. That is to say, the embodiment of the present invention can determine the target node for a deployment unit by using an automatic control method, thereby deploying the target node; compared with the prior art, manual deployment is not required, compared with the prior art, Manual deployment is required, thus increasing deployment efficiency.

Embodiment 4

As shown in FIG. 4, the embodiment of the present invention provides a cloud environment system-based deployment device 40, which is used to implement the cloud environment system-based deployment method shown in FIG. 1. The deployment device 40 includes:

The storage module 401 is configured to store a preset table, where the preset table is used to record a correspondence between a node type and a deployment unit deployable by a node having the node type;

The processing module 402 is configured to perform the following actions:

Determining a first node to be deployed in a cloud environment system;

Obtaining a node type of the first node;

Deploying the deployment unit to be deployed in the first node.

Optionally, the processing module 402 is specifically configured to: determine that the node that is being started in the system is the first node to be deployed, or determine that the node that is actually running in the system is different from the pre-deployed deployment unit is to be deployed. The first node.

Optionally, the policy corresponding to the deployment unit in the deployable deployment unit set includes: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.

Optionally, the processing module 402 is specifically configured to:

Optionally, the processing module 402 is further configured to migrate at least one deployment unit in the first node under a trigger condition.

Optionally, the processing module 402 is specifically configured to: delete at least one deployment unit of the first node; deploy the deleted at least one deployment unit according to a policy corresponding to the deleted at least one deployment unit Among other nodes in the system.

Optionally, the triggering condition includes at least one of the following: a resource occupied by a deployment unit in the first node is greater than or equal to a threshold, and at least one deployment unit in the first node is faulty, the first The load of the system where the node is located is less than or equal to a threshold.

Optionally, the processing module 402 is specifically configured to: determine n migratable deployment units in the first node; where n>1, n is an integer; and according to the migration rights of the n migratable deployment units The value determines the migration order of the n migratable deployment units; The migration sequence sequentially migrates the n migratable deployment units.

Optionally, the processing module 402 is further configured to: when the first node is no longer a node in the system, deploy at least one deployment unit of the first node in another node in the system. .

Optionally, the processing module 402 is specifically configured to: select, according to a policy corresponding to the at least one deployment unit of the first node, a target node for at least one deployment unit of the first node; At least one of the deployment units is deployed in the target node.

Optionally, the deployment unit includes at least one of the following: a process, a process group, a virtual machine, and an application system.

It should be noted that, in specific implementation, the deployment device 40 may be integrated in a device independent of the cloud environment system, or may be integrated in any device in the cloud environment system.

The cloud environment system-based deployment apparatus provided by the embodiment of the present invention determines the node type of the first node and the first node to be deployed, and determines the deployable deployment unit set according to the node type of the first node, and then according to the The policy corresponding to the deployment unit in the deployable deployment unit set determines the deployment unit that the first node needs to deploy, so that the deployed deployment units are deployed in the first node. That is to say, the device can automatically deploy a node; compared with the prior art, manual deployment is not required, thereby improving deployment efficiency.

Embodiment 5

In hardware implementation, each module in Embodiment 4 may be embedded in a hardware form or independent of a processor of a cloud environment system-based deployment device, or may be stored in software in a cloud environment system-based deployment device. In the memory, in order to facilitate the processor to perform the operations corresponding to the above modules, the processor may be a central processing unit (CPU), a microprocessor, a single chip microcomputer, or the like.

As shown in FIG. 5, a deployment device 50 is provided for implementing the cloud environment system-based deployment method shown in FIG. 1. The deployment device 50 includes: a memory 501, a processor 502, and a bus system. 503.

The memory 501 and the processor 502 are coupled together by a bus system 503, wherein the memory 501 may include a high speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. . The bus system 503 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component) bus, or an EISA (Extended Industry Standard Architecture) bus. The bus system 503 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 5, but it does not mean that there is only one bus or one type of bus.

The memory 501 is configured to store a set of codes for controlling the processor 502 to perform the following actions:

Determining a first node to be deployed in a cloud environment system;

Obtaining a node type of the first node;

Deploying the deployment unit to be deployed in the first node.

Optionally, the processor 502 is specifically configured to: determine a section that is being started in the system. The point is the first node to be deployed, or the node that determines that the deployment unit actually running in the system is different from the pre-deployed deployment unit is the first node to be deployed.

Optionally, the processor 502 is specifically configured to:

Optionally, the processor 502 is further configured to migrate at least one deployment unit in the first node under a trigger condition.

Optionally, the processor 502 is further configured to delete at least one deployment unit of the first node, and deploy the deleted at least one deployment unit to the system according to the policy corresponding to the deleted at least one deployment unit. Among the other nodes in .

Optionally, the processor 502 is specifically configured to: determine n migratable deployment units in the first node; where n>1, n is an integer; and according to the migration rights of the n migratable deployment units The value determines a migration order of the n migratable deployment units; and the n migratable deployment units are sequentially migrated according to the migration order.

Optionally, the processor 502 is further configured to: when the first node is no longer a node in the system, deploy at least one deployment unit of the first node in another node in the system. .

Optionally, the processor 502 is specifically configured to: select, according to a policy corresponding to the at least one deployment unit of the first node, a target node for at least one deployment unit of the first node; At least one of the deployment units is deployed in the target node.

The cloud environment system-based deployment apparatus provided by the embodiment of the present invention determines the node type of the first node and the first node to be deployed, and determines the deployable deployment unit set according to the node type of the first node, and then according to the The policy corresponding to the deployment unit in the deployable deployment unit set determines the deployment unit that the first node needs to deploy, so that the deployed deployment units are deployed in the first node. That is to say, the device can deploy a node by an automatic control method; compared with the prior art, manual deployment is not required, thereby improving deployment efficiency.

Embodiment 6

As shown in FIG. 6, the embodiment of the present invention provides a cloud environment system-based deployment device 60, which is used to implement the cloud environment system-based deployment method shown in FIG.

The processing module 601 is configured to perform the following actions:

Deploying the to-be-deployed unit in the target node;

The storage module 602 is configured to store a policy corresponding to the deployment unit to be deployed. Optionally, the policy corresponding to the deployment unit to be deployed includes: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.

Optionally, the processing module 601 is specifically configured to:

Example 7

In hardware implementation, each module in Embodiment 6 may be embedded in or independent of the processor of the user equipment UE in hardware, or may be stored in the memory of the device 70 in software, so that the processor can execute the call. For the operations corresponding to the above modules, the processor may be a central processing unit (CPU), a microprocessor, a single chip microcomputer, or the like.

As shown in FIG. 7, a cloud environment system based deployment is provided according to an embodiment of the present invention. The device 70 is configured to implement the cloud environment system-based deployment method shown in FIG. 3, where the deployment device 70 includes a memory 701, a processor 702, and a bus system 703.

The memory 701 and the processor 702 are coupled together by a bus system 703, wherein the memory 701 may include a high speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. . The bus system 703 can be an ISA bus, a PCI bus, or an EISA bus. The bus system 703 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 7, but it does not mean that there is only one bus or one type of bus.

The memory 701 is for storing a set of codes including computer operating instructions. The code is used to control the processor 702 to perform the following actions:

The unit to be deployed is deployed in the target node.

Optionally, the policy corresponding to the deployment unit to be deployed includes: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.

Optionally, the processor 702 is specifically configured to:

It should be noted that, in a specific implementation, the deployment device 70 may be integrated in a device independent of the cloud environment system, or may be integrated in any device in the cloud environment system.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be another division manner, for example, multiple modules or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.

The modules described as separate components may or may not be physically separated. The components displayed as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or two or more modules may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of hardware plus software function modules.

The above-described integrated modules implemented in the form of software function modules can be stored in a computer readable storage medium. The software functional modules described above are stored in a storage medium and include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform some of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.

It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not limited thereto; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments are modified, or the equivalents of the technical features are replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

A deployment method based on a cloud environment system, comprising:

The control module determines the first node to be deployed in the cloud environment system;

The control module acquires a node type of the first node;

The control module matches the node type of the first node with the node type in the preset table to obtain a deployment unit set that can be deployed by the first node; wherein the preset table is used to record the node type and Correspondence between deployment units that can be deployed by nodes of the node type;

The control module selects, according to a policy corresponding to the deployment unit in the deployable deployment unit set, a deployment unit that needs to be deployed by the first node in the set of deployable deployment units;

The control module deploys the deployment unit to be deployed in the first node.
The method according to claim 1, wherein the determining the first node to be deployed comprises:

The node that is being started in the system is determined to be the first node to be deployed, or the node that is determined to be actually deployed in the system is different from the pre-deployed deployment unit is the first node to be deployed.
The method according to claim 1 or 2, wherein the policy corresponding to the deployment unit in the set of deployable deployment units comprises: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.
The method according to claim 3, wherein the selecting the first node to be deployed in the set of deployable deployment units according to a policy corresponding to a deployment unit in the deployable deployment unit set Deployment unit, including:

When the policy corresponding to the deployment unit in the deployable deployment unit set includes a single policy or a quantity policy, according to the policy corresponding to the deployment unit in the deployable deployment unit set and the deployment unit in other nodes in the system, In the deployable department Selecting a deployment unit to be deployed by the first node in the set of unit units;

Or, when the policy corresponding to the deployment unit in the deployable deployment unit set includes a resource policy, selecting the first one of the deployable deployment unit sets according to the resource policy and the resource of the first node The deployment unit that the node needs to deploy.
The method according to any one of claims 1 to 4, wherein after the deploying the deployment unit to be deployed in the first node, the method further comprises:

At least one of the first nodes is migrated under a trigger condition.
The method according to claim 5, wherein the migrating at least one of the first nodes comprises:

Deleting at least one deployment unit of the first node;

And deleting the deleted at least one deployment unit in other nodes in the system according to the policy corresponding to the deleted at least one deployment unit.
The method according to claim 5 or 6, wherein the triggering condition comprises at least one of the following: a resource occupied by a deployment unit in the first node is greater than or equal to a threshold, in the first node. At least one deployment unit fails, and the load of the system in which the first node is located is less than or equal to a threshold.
The method according to any one of claims 5 to 7, wherein the migrating at least one of the first nodes comprises:

Determining n migratable deployment units in the first node; wherein n>1, n is an integer;

Determining a migration order of the n migratable deployment units according to a migration weight of the n migratable deployment units;

The n migratable deployment units are sequentially migrated according to the migration order.
The method according to any one of claims 1 to 8, wherein after the deploying the deployment unit to be deployed in the first node, the method further comprises:

When the first node is no longer a node in the system, at least one of the first nodes is deployed in other nodes in the system.
The method according to claim 9, wherein the deploying at least one of the first nodes in other nodes in the system comprises:

Selecting a target node for at least one of the first nodes according to a policy corresponding to at least one of the first nodes;

At least one deployment unit of the first node is deployed in the target node.
The method according to any one of claims 1 to 10, wherein the deployment unit comprises at least one of the following: a process, a process group, a virtual machine, and an application system.
A deployment method based on a cloud environment system, comprising:

The control module determines a policy corresponding to the deployment unit to be deployed and the deployment unit to be deployed in the cloud environment system;

The control module selects a target node for the deployment unit to be deployed according to the policy corresponding to the deployment unit to be deployed;

The control module deploys the to-be-deployed unit in the target node.
The method according to claim 12, wherein the policy corresponding to the deployment unit to be deployed comprises: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.
The method according to claim 13, wherein the selecting a target node for the to-be-deployed unit according to the policy corresponding to the deployment unit to be deployed includes:

When the policy corresponding to the deployment unit to be deployed includes a single policy or a quantity policy, the target node is selected for the to-be-deployed unit according to the policy corresponding to the deployment unit to be deployed and the deployment unit in other nodes in the system;

Or, when the policy corresponding to the deployment unit to be deployed includes a resource policy, the resource policy and the resources of other nodes in the system are selected as the deployment unit to be deployed. Target node.
The method according to any one of claims 12 to 14, wherein the deployment unit to be deployed comprises at least one of the following: a process, a process group, a virtual machine, and an application system.
A deployment device based on a cloud environment system, comprising:

a storage module, configured to store a preset table, where the preset table is used to record a correspondence between a node type and a deployment unit deployable by a node having the node type;

Processing module for performing the following actions:

Determining a first node to be deployed in a cloud environment system;

Obtaining a node type of the first node;

Matching the node type of the first node with the node type in the preset table to obtain a deployment unit set that can be deployed by the first node;

Selecting, according to a policy corresponding to the deployment unit in the deployable deployment unit set, a deployment unit that needs to be deployed by the first node in the set of deployable deployment units;

Deploying the deployment unit to be deployed in the first node.
The device according to claim 16, wherein the processing module is specifically configured to:

The node that is being started in the system is determined to be the first node to be deployed, or the node that is determined to be actually deployed in the system is different from the pre-deployed deployment unit is the first node to be deployed.
The device according to claim 16 or 17, wherein the policy corresponding to the deployment unit in the set of deployable deployment units comprises: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.
The device according to claim 18, wherein the processing module is specifically configured to:

The policy corresponding to the deployment unit in the deployable deployment unit set includes a single When a policy or quantity policy is selected, the first node needs to be selected among the deployable deployment unit sets according to a policy corresponding to a deployment unit in the deployable deployment unit set and a deployment unit in other nodes in the system. The deployed deployment unit;

Or, when the policy corresponding to the deployment unit in the deployable deployment unit set includes a resource policy, selecting the first one of the deployable deployment unit sets according to the resource policy and the resource of the first node The deployment unit that the node needs to deploy.
The apparatus according to any one of claims 16 to 19, wherein the processing module is further configured to migrate at least one deployment unit of the first node under a trigger condition.
The device according to claim 20, wherein the processing module is specifically configured to:

Deleting at least one deployment unit of the first node;

And deleting the deleted at least one deployment unit in other nodes in the system according to the policy corresponding to the deleted at least one deployment unit.
The device according to claim 20 or 21, wherein the triggering condition comprises at least one of the following: a resource occupied by a deployment unit in the first node is greater than or equal to a threshold, in the first node. At least one deployment unit fails, and the load of the system in which the first node is located is less than or equal to a threshold.
The device according to any one of claims 20 to 22, wherein the processing module is specifically configured to:

Determining n migratable deployment units in the first node; wherein n>1, n is an integer;

Determining a migration order of the n migratable deployment units according to a migration weight of the n migratable deployment units;

The n migratable deployment units are sequentially migrated according to the migration order.
The device according to any one of claims 16 to 23, wherein the processing module is further configured to:

When the first node is no longer a node in the system, at least one of the first nodes is deployed in other nodes in the system.
The device according to claim 24, wherein the processing module is specifically configured to:

Selecting a target node for at least one of the first nodes according to a policy corresponding to at least one of the first nodes;

At least one deployment unit of the first node is deployed in the target node.
The device according to any one of claims 16 to 25, wherein the deployment unit comprises at least one of the following: a process, a process group, a virtual machine, and an application system.
A deployment device based on a cloud environment system, comprising:

Processing module for performing the following actions:

Determining a policy corresponding to the deployment unit to be deployed and the deployment unit to be deployed;

Selecting a target node for the deployment unit to be deployed according to the policy corresponding to the deployment unit to be deployed;

Deploying the to-be-deployed unit in the target node;

And a storage module, configured to store a policy corresponding to the deployment unit to be deployed.
The device according to claim 27, wherein the policy corresponding to the deployment unit to be deployed comprises: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.
The device according to claim 28, wherein the processing module is specifically configured to:

When the policy corresponding to the deployment unit to be deployed includes a single policy or a quantity policy, the target node is selected for the to-be-deployed unit according to the policy corresponding to the deployment unit to be deployed and the deployment unit in other nodes in the system;

Or, when the policy corresponding to the deployment unit to be deployed includes a resource policy, the resource policy and the resources of other nodes in the system are selected as the deployment unit to be deployed. Target node.
The device according to any one of claims 27 to 29, wherein the deployment unit to be deployed comprises at least one of the following: a process, a process group, a virtual machine, and an application system.
A deployment device based on a cloud environment system, comprising: a memory and a processor;

The memory is for storing a set of codes for controlling the processor to perform the following actions:

Determining a first node to be deployed in a cloud environment system;

Obtaining a node type of the first node;

Matching the node type of the first node with the node type in the preset table to obtain a deployment unit set that can be deployed by the first node; wherein the preset table is used to record a node type and have the node type Correspondence between deployment units of nodes that can be deployed;

Selecting, according to a policy corresponding to the deployment unit in the deployable deployment unit set, a deployment unit that needs to be deployed by the first node in the set of deployable deployment units;

Deploying the deployment unit to be deployed in the first node.
The device according to claim 31, wherein the processor is specifically configured to:

The node that is being started in the system is determined to be the first node to be deployed, or the node that is determined to be actually deployed in the system is different from the pre-deployed deployment unit is the first node to be deployed.
The device according to claim 31 or 32, wherein the policy corresponding to the deployment unit in the set of deployable deployment units comprises: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.
The device according to claim 33, wherein said treatment tool Body for:

When the policy corresponding to the deployment unit in the deployable deployment unit set includes a single policy or a quantity policy, according to the policy corresponding to the deployment unit in the deployable deployment unit set and the deployment unit in other nodes in the system, Selecting, in the set of deployable deployment units, a deployment unit to be deployed by the first node;

Or, when the policy corresponding to the deployment unit in the deployable deployment unit set includes a resource policy, selecting the first one of the deployable deployment unit sets according to the resource policy and the resource of the first node The deployment unit that the node needs to deploy.
The device according to any one of claims 31 to 34, wherein the processor is further configured to:

At least one of the first nodes is migrated under a trigger condition.
The device according to claim 35, wherein the processor is specifically configured to:

Deleting at least one deployment unit of the first node;

And deleting the deleted at least one deployment unit in other nodes in the system according to the policy corresponding to the deleted at least one deployment unit.
The device according to claim 35 or claim 36, wherein the triggering condition comprises at least one of the following: a resource occupied by a deployment unit in the first node is greater than or equal to a threshold, in the first node. At least one deployment unit fails, and the load of the system in which the first node is located is less than or equal to a threshold.
The device according to any one of claims 35 to 37, wherein the processor is specifically configured to:

Determining n migratable deployment units in the first node; wherein n>1, n is an integer;

Determining a migration order of the n migratable deployment units according to a migration weight of the n migratable deployment units;

The n migratable deployment units are sequentially migrated according to the migration order.
The device according to any one of claims 31 to 38, wherein the processor is further configured to:

When the first node is no longer a node in the system, at least one of the first nodes is deployed in other nodes in the system.
The device according to claim 39, wherein the processor is specifically configured to:

Selecting a target node for at least one of the first nodes according to a policy corresponding to at least one of the first nodes;

At least one deployment unit of the first node is deployed in the target node.
The apparatus according to any one of claims 31 to 40, wherein the deployment unit comprises at least one of the following: a process, a process group, a virtual machine, and an application system.
A deployment device based on a cloud environment system, comprising: a memory and a processor;

The memory is for storing a set of codes for controlling the processor to perform the following actions:

Determining, in the cloud environment system, a policy corresponding to the deployment unit to be deployed and the deployment unit to be deployed;

Selecting a target node for the deployment unit to be deployed according to the policy corresponding to the deployment unit to be deployed;

The unit to be deployed is deployed in the target node.
The device according to claim 42, wherein the policy corresponding to the deployment unit to be deployed comprises: a general policy, a single policy, a quantity policy, a node type policy, and a resource policy.
The device according to claim 43, wherein the processor is specifically configured to:

When the policy corresponding to the deployment unit to be deployed includes a single policy or a quantity policy Selecting a target node for the to-be-deployed unit according to a policy corresponding to the deployment unit to be deployed and a deployment unit in another node in the system;

Or, when the policy corresponding to the deployment unit to be deployed includes a resource policy, select a target node for the deployment unit to be deployed according to the resource policy and resources of other nodes in the system.
The device according to any one of claims 42 to 44, wherein the deployment unit to be deployed comprises at least one of the following: a process, a process group, a virtual machine, and an application system.