WO2016045392A1

WO2016045392A1 - Service deployment method, service management method and apparatus

Info

Publication number: WO2016045392A1
Application number: PCT/CN2015/078914
Authority: WO
Inventors: 张毅
Original assignee: 华为技术有限公司
Priority date: 2014-09-26
Filing date: 2015-05-14
Publication date: 2016-03-31
Also published as: CN105592130B; CN105592130A

Abstract

A service deployment method, a service management method and an apparatus. The service deployment method comprises: receiving a service deployment package of a second service, the service deployment package comprising a deployment plan and a second description file (101); acquiring a second instance ID of the deployed second service after the deployment plan is executed according to the second description file (102); determining that the second description file includes information indicating that the second service restricts the execution of a plan for a first instance ID of a first service and/or a method for a node of the first instance ID (103); acquiring a first description file of the first service according to the first instance ID (104); and recording a correspondence between the second instance ID and the plan for the first instance ID and/or the method for the node of the first instance ID in the first description file according to the information indicating that the second service restricts the execution of the plan for the first instance ID of the first service and/or the method for the node of the first instance ID (105).

Description

Service deployment method, service management method and device

Technical field

The present application relates to the field of computer technologies, and in particular, to a service deployment method, a service management method, and an apparatus.

Background technique

Cloud computing is a service delivery and consumption model. Cloud Service Provider (English: Cloud Service Provider, CSP for short) connects a large number of computing resources with the network and performs unified management, distribution and scheduling to form a huge resource pool to cloud service consumers (English: Cloud Service Consumer) , referred to as: CSC) provides services. For CSC, cloud resources can be expanded infinitely, with the characteristics of efficient and flexible on-demand, pay-per-use and so on.

In the prior art, all the information required to deploy a service is described in a service deployment package called Cloud Service Archive (CSAR). The service deployment package contains at least one service deployment descriptor file. The description file is suffixed with ste, and the deployment information of the application is described in Extensible Markup Language (English: Extensible Markup Language, XML for short). The root element of the description file is the service template (ServiceTemplate). That is to say, the ServiceTemplate is used to completely describe the information of a service, and its sub-elements include TopologyTemplate, NodeType, NodeTemplate, RelationshipType, RelationshipTemplate, Plan (Plan). ), etc., the relationship between these elements is shown in Figure 1.

As shown in Figure 1, the prior art uses TopologyTemplate to depict an application topology. Each node in the topology corresponds to a NodeTemplate whose type is defined by the NodeType (the type attribute of the NodeTemplate describes the NodeType corresponding to the NodeTemplate). The NodeType defines the metadata of the NodeTemplate, such as properties (defined by Properties), the interface set of the node (defined by Interfaces), etc. Each Interfaces can contain multiple Interfaces, and each Interface can contain multiple methods (Operation) Such as Install, Config, Stop, and Remove. Each method corresponds to a method artifact (ie an executable file, such as a script file). At the same time, each node corresponds to a deployed artifact (can be a mirror, installable package, etc.). The NodeType can be inherited, the inherited NodeType is called the parent node type, and the inherited NodeType is called the child node type. Once a NodeType is inherited, the table The child node type of the NodeType contains all the attributes in its parent node type and the methods under the interface under the interface set.

Each NodeType is executed corresponding to one node type (English: Node Type Implementatio, referred to as NTI). The type attribute of the NTI describes the NodeType corresponding to the NTI, and the NTI describes the information about the deployed product of the NodeType and the method product of all methods.

Each edge in the topology is a RelationshipTemplate. The RelationshipTemplate is an instance of the RelationshipType that defines the starting point (defined by SourceElement) and the ending point (defined by TargetElement).

Each application deployment package also includes a plan, which is an executable workflow. Each node in the workflow is a method defined in the NodeType, described in a standardized language, such as business process modeling and labeling. (English: Business Process Model and Notation, referred to as: BPMN) 2.0. Currently, the prior art includes two standard plans, a deployment plan (BuildPlan) and a delete plan (TerminatePlan). At the same time, the ServiceTemplate can also contain custom Plan, such as configuration plan (ConfigPlan) and stop plan (StopPlan). When the plan is executed, the server runs the method artifacts of each node one by one according to the definition of the plan.

In addition, the ServiceTemplate can define rules that act on itself. First define the policy type (PolicyType) to describe the metadata of the rule, and then define its instance policy template (PolicyTemplate) in the ServiceTemplate.

In the prior art, it is assumed that a CSC device has deployed Service A on a CSP server, which includes a web service a. Thereafter, the CSC device deploys service B on the same CSP server, and service B uses the web service a in service A in the service logic in the manner of service invocation. The topology relationship between Service A and Service B is shown in Figure 2.

Obviously, if Service A is deleted or stopped, Service B's business logic will not function properly. In order to solve the technical problem, the existing method is: when the service B is deployed, the service A and the service B are merged into one large service C, as shown in FIG. 3. Because it is to be merged, in the service deployment package sent by the CSC device to the CSP server, the content in the deployment package of the service A is included, and the CSP server needs to deploy the service A once again, resulting in waste of resources.

Summary of the invention

The embodiment of the present application provides a service deployment method, a service management method, and a device, which are used to solve the present problem. There is a technical problem of merging resource waste caused by deployed services when deploying new services in the technology.

The first aspect of the present application provides a service deployment method, including:

Receiving a service deployment package of the second service, where the service deployment package includes a deployment plan and a description file of the second service;

After executing the deployment plan according to the description file of the second service, acquiring a second instance identification ID of the second service that has been deployed;

Determining, in the description file of the second service, information that the second service restricts execution of a plan of a first instance ID of the first service and/or a method of a node of the first instance ID;

Obtaining, according to the first instance ID, a description file of the first service;

Recording, according to the second service, information of a method of executing a first instance ID of the first service and/or a method of a node of the first instance ID, recording the second instance in a description file of the first service A correspondence between the ID and the method of the first instance ID and/or the method of the node of the first instance ID.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the plan of the second instance ID and the first instance ID is recorded in the description file of the first service, and/or the After the correspondence between the methods of the nodes of the first instance ID, the method further includes:

Receiving a deletion request for the second instance ID, where the deletion request includes the second instance ID and a deletion plan to be executed;

Obtaining the service deployment package according to the second instance ID, where the service deployment package further includes the deletion plan;

Determining, in the description file of the second service, information that the second service restricts execution of a plan of the first instance ID and/or a method of a node of the first instance ID;

Inserting a mark before the first method of the first node of the deletion plan, the mark indicating that the second service is released from the plan of the first instance ID and/or the node of the first instance ID Restrictions on the execution of the method;

Perform the delete plan after inserting the tag.

In conjunction with the first possible implementation of the first aspect, in a second possible implementation of the first aspect, performing the deleting the deleted plan includes:

Obtaining the first instance ID from a description file of the second service;

Deleting a correspondence between the second instance ID recorded in the description file of the first service and a method of the first instance ID and a method of a node of the first instance ID;

The deletion plan to be executed is executed from the first method.

In conjunction with the first aspect, in a third possible implementation of the first aspect, the plan of the second instance ID and the first instance ID is recorded in the description file of the first service and/or the After the correspondence between the methods of the nodes of the first instance ID, the method further includes:

Receiving, by the sending end, a management request for the first instance ID, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

Determining, according to the correspondence between the second instance ID recorded in the description file of the first service and the method of the first instance ID and the method of the node of the first instance ID, The execution of the method of the plan and/or the node is limited by the second service;

A message is sent to the sender that refuses to execute the plan of the program to be executed and/or the method of the node.

A second aspect of the present application provides a service management method, including:

Receiving, by the sending end, a management request for a first instance identifier ID of the first service, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

Determining the desire according to a correspondence between a second instance ID of the second service recorded in the description file of the first service and a method of the first instance ID and a method of the node of the first instance ID Execution of the executed plan and/or method of the node is restricted by the second service;

With reference to the second aspect, in a first possible implementation manner of the second aspect, the plan to be executed is at least one of a deletion plan, a restart plan, and a stop plan; and the method of the node to be executed is a deletion method. At least one of a restart method and a stop method.

The third aspect of the present application provides a service management method, including:

Receiving a deletion request for a second instance identification ID of the second service, where the deletion request includes the second instance ID and a deletion plan to be executed;

Obtaining, according to the second instance ID, a service deployment package of the second service, where the service deployment package includes a description file of the deletion plan and a second service;

Determining, in the description file of the second service, that the second service restricts execution of the first service Information of a plan of the first instance ID and/or a method of a node of the first instance ID;

Perform the delete plan after inserting the tag.

With reference to the third aspect, in a first possible implementation manner of the third aspect, performing the deleting plan after inserting the mark includes:

Deleting a correspondence between the second instance ID recorded in the description file of the first service and a method of the first instance ID and/or a method of a node of the first instance ID;

The deletion plan to be executed is executed from the first method.

A fourth aspect of the present application provides a service deployment apparatus, including:

a receiving unit, configured to receive a service deployment package of the second service, where the service deployment package includes a deployment plan and a description file of the second service;

a processing unit, configured to: after performing the deployment plan according to the description file of the second service, acquire a second instance identifier ID of the second service that has been deployed; and determine that the description file of the second service includes The second service restricts information of a method of executing a first instance ID of the first service and/or a method of a node of the first instance ID; acquiring a description file of the first service according to the first instance ID Recording the second in the description file of the first service according to the second service restriction information of executing the plan of the first instance ID of the first service and/or the method of the node of the first instance ID Correspondence relationship between the instance ID and the method of the first instance ID and/or the method of the node of the first instance ID.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the receiving unit is further configured to: when the processing unit records the second instance in a description file of the first service Receiving a deletion request for the second instance ID after the correspondence between the ID and the method of the first instance ID and/or the method of the node of the first instance ID, where the deletion request includes the second The instance ID and the deletion plan to be executed;

The processing unit is further configured to: obtain the service deployment package according to the second instance ID, where the service deployment package further includes the deletion plan; and determine that the second service includes the second service in a description file of the second service Method of restricting execution of a plan of the first instance ID and/or a node of the first instance ID Information; inserting a mark before the first method of the first node of the deletion plan, the mark indicating that the second service is released from the plan of the first instance ID and/or the first instance ID The execution limit of the method of the node; the deletion plan after inserting the tag.

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the processing unit is specifically configured to: obtain the first information from a description file of the second service Instance ID; acquiring a description file of the first service according to the first instance ID; deleting a plan of the second instance ID and the first instance ID recorded in a description file of the first service and/or Corresponding relationship of the method of the node of the first instance ID; starting from the first method, executing the deletion plan to be executed.

With reference to the fourth aspect, in a third possible implementation manner of the fourth aspect, the device further includes a sending unit,

The receiving unit is further configured to: record, in the description file of the first service, a plan of the second instance ID and the first instance ID and/or the first instance ID in the description file of the first service After receiving the corresponding relationship of the method of the node, receiving a management request sent by the sending end for the first instance ID, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

The processing unit is further configured to: acquire a description file of the first service according to the first instance ID;

The sending unit is configured to: send a message rejecting the method of executing the plan and/or the node to be executed to the sending end.

A fifth aspect of the present application provides a service management apparatus, including:

a receiving unit, configured to receive a management request sent by the sending end for the first instance identifier ID of the first service, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

a processing unit, configured to acquire, according to the first instance ID, a description file of the first service;

And a sending unit, configured to send, to the sending end, a message rejecting a method of executing the plan and/or the node to be executed.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the plan to be executed is at least one of a deletion plan, a restart plan, and a stop plan; and the method of the node to be executed is a deletion method. At least one of a restart method and a stop method.

The sixth aspect of the present application provides a service management apparatus, including:

a receiving unit, configured to receive a deletion request for a second instance identifier ID of the second service, where the deletion request includes the second instance ID and a deletion plan to be executed;

a processing unit, configured to acquire, according to the second instance ID, a service deployment package of the second service, where the service deployment package includes a description file of the deletion plan and a second service; and determining a description file of the second service Included in the information that the second service restricts execution of a plan of a first instance ID of the first service and/or a method of a node of the first instance ID; a first method of the first node of the deletion plan Inserting a mark indicating a restriction of releasing the second service from the plan of the first instance ID and/or the method of the node of the first instance ID; performing a delete plan after inserting the mark .

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the processing unit is specifically configured to: acquire a description file of the first service according to the first instance ID; and delete the first service Corresponding relationship between the second instance ID recorded in the description file and the method of the first instance ID and/or the method of the node of the first instance ID; executing the execution from the first method Delete plan.

A seventh aspect of the present application provides a server, including:

a receiver, configured to receive a service deployment package of the second service, where the service deployment package includes a deployment plan and a description file of the second service;

a processor, configured to acquire a second instance identifier ID of the second service that has been deployed after executing the deployment plan according to the description file of the second service; determining that the description file of the second service includes The second service restricts information of a method of executing a first instance ID of the first service and/or a method of a node of the first instance ID; acquiring a description file of the first service according to the first instance ID Recording the second in the description file of the first service according to the second service restriction information of executing the plan of the first instance ID of the first service and/or the method of the node of the first instance ID Correspondence between the instance ID and the method of the first instance ID and/or the method of the node of the first instance ID relationship.

With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, the receiver is further configured to: when the processor records the second instance in a description file of the first service Receiving a deletion request for the second instance ID after the correspondence between the ID and the method of the first instance ID and/or the method of the node of the first instance ID, where the deletion request includes the second The instance ID and the deletion plan to be executed;

The processor is further configured to: obtain the service deployment package according to the second instance ID, where the service deployment package further includes the deletion plan; and determine that the second service includes the second service in a description file of the second service Information limiting a method of executing the plan of the first instance ID and/or a node of the first instance ID; inserting a flag before the first method of the first node of the deletion plan, the flag indicating release Restriction of execution of the first instance ID by the second service and/or execution of the method of the node of the first instance ID; performing a deletion plan after inserting the tag.

With reference to the first possible implementation manner of the seventh aspect, in a second possible implementation manner of the seventh aspect, the processor is specifically configured to: obtain the first information from a description file of the second service Instance ID; acquiring a description file of the first service according to the first instance ID; deleting a plan of the second instance ID and the first instance ID recorded in a description file of the first service and/or Corresponding relationship of the method of the node of the first instance ID; starting from the first method, executing the deletion plan to be executed.

With reference to the seventh aspect, in a third possible implementation manner of the seventh aspect, the device further includes a transmitter,

The receiver is further configured to: record, in the description file of the first service, the plan of the second instance ID and the first instance ID and/or the first instance ID in the description file of the first service After receiving the corresponding relationship of the method of the node, receiving a management request sent by the sending end for the first instance ID, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

The processor is further configured to: acquire a description file of the first service according to the first instance ID;

The transmitter is configured to: send a message rejecting the method of executing the plan and/or the node to be executed to the sending end.

An eighth aspect of the present application provides a server, including:

a receiver, configured to receive, by the sending end, a management request for a first instance identifier ID of the first service, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

a processor, configured to acquire, according to the first instance ID, a description file of the first service;

And a transmitter, configured to send a message to the sender that rejects the method of executing the plan and/or the node to be executed.

With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, the plan to be executed is at least one of a deletion plan, a restart plan, and a stop plan; and the method of the node to be executed is a deletion method. At least one of a restart method and a stop method.

A ninth aspect of the present application provides a server, including:

a receiver, configured to receive a deletion request for a second instance identifier ID of the second service, where the deletion request includes the second instance ID and a deletion plan to be executed;

a processor, configured to acquire, according to the second instance ID, a service deployment package of the second service, where the service deployment package includes a description file of the deletion plan and a second service; and determining a description file of the second service Included in the information that the second service restricts execution of a plan of a first instance ID of the first service and/or a method of a node of the first instance ID; a first method of the first node of the deletion plan Inserting a mark indicating a restriction of releasing the second service from the plan of the first instance ID and/or the method of the node of the first instance ID; performing a delete plan after inserting the mark .

With reference to the ninth aspect, in a first possible implementation manner of the ninth aspect, the processor is specifically configured to: acquire a description file of the first service according to the first instance ID; and delete the first service Corresponding relationship between the second instance ID recorded in the description file and the method of the first instance ID and/or the method of the node of the first instance ID; executing the execution from the first method Delete plan.

One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

In the embodiment of the present application, the second service restriction execution is included in the second description file of the second service. Information of a method of a first instance ID of a first service and/or a method of a node of a first instance ID, wherein the first service is a deployed service. Therefore, when deploying a new service, ie, a second service, in addition to executing the deployment plan to deploy the second service, according to the information, the first description file of the first service or the first instance of the first service A correspondence relationship between the second instance ID and the method of the first instance ID and/or the method of the node of the first instance ID is recorded in the log file. Since the second description file contains information that needs to restrict the execution of the plan and/or method without writing all the contents of the first service deployment package, the resources of the development service deployment package and the transmission resources are saved. Moreover, as long as the correspondence between the second instance ID and the method of the first instance ID and/or the method of the node of the first instance ID is written in the description file or the log file of the first service, without re-deployment The content of the first service deployment package saves the server's deployment resources. Further, by limiting the method of executing the plan and/or node of the first instance ID, it can be avoided that the second service cannot be run due to execution of these plans and/or methods.

A tenth aspect of the present invention provides a service deployment method, including:

Receiving a service deployment request, the service deployment request including information of a service deployment package of the second service;

Obtaining, according to the information about the service deployment package of the second service, the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service;

After executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identification ID of the second service that has been deployed;

Determining that the description file of the second service includes restriction information, the restriction information includes information that the second service restricts execution of a plan of a first instance of the first service, and/or the second service restriction performs the Information about the method of the node of the first instance;

Recording, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a record file of the first instance, and/or in a node record file of the first instance Corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded.

With reference to the tenth aspect, in a first possible implementation manner of the tenth aspect, the second instance ID and the first instance are recorded in a record file of the first instance according to the restriction information Corresponding relationship of the plan ID, and/or the correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance, specifically: according to the limitation Information, obtaining a first instance ID; obtaining a record file of the first instance according to the first instance ID; Recording, in the record file of the first instance, the correspondence between the second instance ID and the plan ID of the first instance, and/or acquiring the node record file of the first instance according to the record file of the first instance, Corresponding relationship between the second instance ID and a method ID of a node of the first instance is recorded in a node record file of the first instance.

With reference to the tenth aspect, in a second possible implementation manner of the tenth aspect, the corresponding relationship between the second instance ID and the plan ID of the first instance is recorded in the record file of the first instance, and After the correspondence between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, the method further includes: receiving an instance deletion request, the instance The deletion request includes the second instance ID and the deletion plan ID to be executed; and the service deployment package is obtained according to the second instance ID, where the service deployment package further includes the deletion corresponding to the deletion plan ID to be executed. Determining, in the description file of the second service, the restriction information; acquiring the first instance ID according to the restriction information; acquiring the record file of the first instance according to the first instance ID; Deleting a correspondence between the second instance ID and the plan ID of the first instance in the record file of the first instance, and/or acquiring a section of the first instance according to the record file of the first instance Recording a file, deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of a node of the first instance; performing the deleting according to the description file of the second service plan.

With reference to the tenth aspect, in a third possible implementation manner of the tenth aspect, the corresponding relationship between the second instance ID and the plan ID of the first instance is recorded in the record file of the first instance, and After the correspondence between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, the method further includes: receiving an instance management request sent by the sender The instance management request includes the first instance ID and a plan ID to be executed; acquiring a record file of the first instance according to the first instance ID; and recording according to the record file of the first instance Corresponding relationship between the second instance ID and the plan ID of the first instance, determining that execution of the plan corresponding to the plan ID to be executed is restricted by the second instance, and sending a plan to refuse execution of the plan to be executed Message to the sender; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of the node to be executed; acquiring the record file of the first instance according to the first instance ID; a record file of the first instance, acquiring a node record file of the first instance; according to the second instance ID recorded in the node record file and a method ID of the node of the first instance Corresponding relationship, determining that the execution of the method corresponding to the method ID of the node to be executed is restricted by the second instance; sending a message rejecting the method of executing the node to be executed to the transmitting end; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed; acquiring a node record file to be executed according to the node ID to be executed; Corresponding relationship between the second instance ID recorded in the node record file and the method ID of the node of the first instance, determining that the method corresponding to the method ID of the node to be executed is performed by the second instance Restricting; sending a message rejecting the method of executing the node to be executed to the sender.

An eleventh aspect of the present invention provides an apparatus for service deployment, including: a receiving unit, configured to receive a service deployment request, where the service deployment request includes information of a service deployment package of a second service, and a processing unit configured to Obtaining, by the information of the service deployment package of the second service, a service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service; After the description file of the second service executes the deployment plan of the second service, acquiring a second instance identifier ID of the second service that has been deployed; determining that the description file of the second service includes restriction information, the limitation The information includes information that the second service restricts execution of a plan of the first instance of the first service, and/or information that the second service restricts execution of a method of the node of the first instance; Recording, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or a node record in the first instance Examples of the second member in the recording process corresponding relationship ID in the node and the first instance.

With reference to the eleventh aspect, in a first possible implementation manner of the eleventh aspect, the processing unit is configured to record the second instance in a record file of the first instance according to the restriction information Corresponding relationship between the ID and the plan ID of the first instance, and/or the correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance, Specifically, the first instance ID is obtained according to the restriction information; the record file of the first instance is obtained according to the first instance ID; and the second instance ID and the number are recorded in the record file of the first instance. Corresponding relationship of the plan ID of an instance, and/or acquiring a node record file of the first instance according to the record file of the first instance, and recording the second instance ID in the node record file of the first instance The corresponding relationship of the method IDs of the nodes of the first instance.

In conjunction with the eleventh aspect, in a second possible implementation manner of the eleventh aspect, the receiving The element is further configured to: record a correspondence between the second instance ID and a plan ID of the first instance in a record file of the first instance, and/or record in a node record file of the first instance After receiving the correspondence between the second instance ID and the method of the node ID of the first instance, receiving a receiving instance deletion request, where the instance deletion request includes the second instance ID and a deletion plan ID to be executed; The processing unit is further configured to acquire the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed; and determining a description file of the second service Include the restriction information; obtain the first instance ID according to the restriction information; acquire a record file of the first instance according to the first instance ID; delete the record file of the first instance Determining a correspondence between the second instance ID and the plan ID of the first instance, and/or acquiring a node record file of the first instance according to the record file of the first instance, deleting the section of the first instance Corresponding relationship between the ID recording method of recording a file of a second example of the node ID of the first example; the second service description file according to the execution of the program deleted.

In conjunction with the eleventh aspect, in a third possible implementation manner of the eleventh aspect, the device further includes a sending unit, where the receiving unit is further configured to: record the in the record file of the first instance Corresponding relationship between the second instance ID and the plan ID of the first instance, and/or recording the second instance ID and the method ID of the node of the first instance in the node record file of the first instance After the corresponding relationship, the instance management request sent by the sending end is received, where the instance management request includes the first instance identifier ID and a plan ID to be executed; the processing unit is further configured to: obtain, according to the first instance ID, a record file of the first instance; determining a plan ID to be executed according to a correspondence between a second instance ID of the second service recorded in the record file of the first instance and a plan ID of the first instance The execution of the corresponding plan is restricted by the second instance, and the sending unit is configured to: send a message rejecting execution of the plan to be executed to the sending end; and/or

The receiving unit is further configured to: receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of a node to be executed; the processing unit is further configured to: according to the first Obtaining, by an instance ID, a record file of the first instance; acquiring, according to the record file of the first instance, a node record file of the first instance; according to the second instance ID recorded in the node record file Corresponding relationship of the method ID of the node of the first instance, determining that the execution of the method corresponding to the method ID of the node to be executed is restricted by the second instance; the sending unit is configured to: send a rejection to execute the execution a message of the method of the node to the sender; and/or

The receiving unit is further configured to: receive an instance management request sent by the sending end, where the instance management is requested Determining a node ID to be executed and a method ID of a node to be executed; the processing unit is further configured to: acquire a node record file to be executed according to the node ID to be executed; according to the node record file to be executed Corresponding relationship between the recorded second instance ID and the method ID of the node of the first instance, determining that the execution of the method corresponding to the method ID of the node to be executed is restricted by the second instance; the sending The unit is configured to: send a message rejecting a method of executing the node to be executed to the sending end.

A twelfth aspect of the present invention provides a service deployment method, including: receiving a service deployment request, where the service deployment request includes information and restriction information of a service deployment package of a second service; and the restriction information includes the The second service restricts execution of the information of the plan of the first instance, and/or the second service limits information of the method of executing the node of the first instance; and obtains information according to the service deployment package of the second service a service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service; and performing the deployment of the second service according to the description file of the second service After the scheduling, acquiring the second instance identifier ID of the second service that has been deployed and the record file of the second instance; and according to the restriction information, recording the association information in the record file of the second instance, the association The information includes a first instance ID, and the second instance ID and the plan ID of the first instance are recorded in a log file of the first instance according to the restriction information Correspondence between the correspondence relationship, and / or recorded in a log file of the node in the first instance to the second instance node ID of the first example of the method ID.

With reference to the twelfth aspect, in a first possible implementation manner of the twelfth aspect, the second instance ID and the first part are recorded in a record file of the first instance according to the restriction information Corresponding relationship between the plan ID of an instance, and/or a correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance, specifically: according to Determining information, obtaining a first instance ID; acquiring a record file of the first instance according to the first instance ID; recording the second instance ID and the plan ID of the first instance in the record file of the first instance Corresponding relationship, and/or obtaining a node record file of the first instance according to the record file of the first instance, and recording the second instance ID and the first instance in a node record file of the first instance Correspondence of the method ID of the node.

With reference to the twelfth aspect, in a second possible implementation manner of the twelfth aspect, the correspondence between the second instance ID and the plan ID of the first instance is recorded in the record file of the first instance And/or recording the second instance ID and the first in the node record file of the first instance After the corresponding relationship of the method IDs of the nodes of the instance, the method further includes: receiving an instance deletion request, where the instance deletion request includes the second instance ID and a deletion plan ID to be executed; according to the second instance ID Acquiring the record file of the second instance and the service deployment package, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed; determining that the record file of the second instance includes the Correlating the information; acquiring the first instance ID according to the association information; acquiring the record file of the first instance according to the first instance ID; and deleting the record recorded in the record file of the first instance Obtaining a correspondence between the second instance ID and the plan ID of the first instance, and/or acquiring the node record file of the first instance according to the record file of the first instance, and deleting the node record file of the first instance Corresponding relationship between the second instance ID recorded in the node and the method ID of the node of the first instance; performing the deletion plan according to the description file of the second service.

With reference to the twelfth aspect, in a third possible implementation of the twelfth aspect, the correspondence between the second instance ID and the plan ID of the first instance is recorded in the log file of the first instance And after the correspondence between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, the method further includes: receiving an instance sent by the sender a management request, the instance management request includes the first instance ID and a plan ID to be executed; acquiring a record file of the first instance according to the first instance ID; recording according to a record file of the first instance Corresponding relationship between the second instance ID and the plan ID of the first instance, determining that the execution of the plan corresponding to the plan ID to be executed is restricted by the second instance; sending the rejection to perform the execution a planned message to the sender; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of the node to be executed; acquiring the record file of the first instance according to the first instance ID; a record file of the first instance, obtaining a node record file of the first instance; determining the desire according to a correspondence between the second instance ID recorded in the node record file and a method ID of a node of the first instance Execution of the method corresponding to the method ID of the executed node is restricted by the second instance; sending a message rejecting the method of executing the node to be executed to the sender; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed; acquiring a node record file to be executed according to the node ID to be executed; Corresponding relationship between the second instance ID recorded in the node record file and the method ID of the node of the first instance, determining that the method ID of the node to be executed corresponds to The execution of the method is limited by the second instance; a message is sent to the sender that rejects the method of executing the node to be executed.

According to a twelfth aspect, the present invention provides a service deployment apparatus, including: a receiving unit, configured to receive a service deployment request, where the service deployment request includes information and restriction information of a service deployment package of a second service; The information includes information that the second service restricts execution of the plan of the first instance, and/or information that the second service restricts execution of a method of the node of the first instance; a processing unit that is configured to Information about a service deployment package of the second service, where the service deployment package of the second service is obtained, where the service deployment package includes a deployment plan of the second service and a description file of the second service; After the description file executes the deployment plan of the second service, acquiring a second instance identifier ID of the second service that has been deployed and a log file of the second instance; according to the restriction information, in the second instance Recording associated information in the record file, the associated information including a first instance ID; recording the second in the record file of the first instance according to the restriction information Corresponding relationship between the instance ID and the plan ID of the first instance, and/or the correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance .

With reference to the twelfth aspect, in a first possible implementation manner of the twelfth aspect, the processing unit is configured to: record, according to the restriction information, the second instance in a record file of the first instance Corresponding relationship between the ID and the plan ID of the first instance, and/or the correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance, Specifically, the first instance ID is obtained according to the restriction information; the record file of the first instance is obtained according to the first instance ID; and the second instance ID and the number are recorded in the record file of the first instance. Corresponding relationship of the plan ID of an instance, and/or acquiring a node record file of the first instance according to the record file of the first instance, and recording the second instance ID in the node record file of the first instance The corresponding relationship of the method IDs of the nodes of the first instance.

In a second possible implementation manner of the twelfth aspect, the receiving unit is further configured to: record, in the recording file of the first instance, the second instance in the processing unit a correspondence between the ID and the plan ID of the first instance, and/or after the correspondence between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance Receiving an instance deletion request, the instance deletion request includes the second instance ID and a deletion plan ID to be executed; the processing unit is further configured to: acquire the record of the second instance according to the second instance ID a file and the deployment package, the deployment package further including the deletion plan ID to be executed Corresponding deletion plan; determining that the record information of the second instance includes the association information; acquiring the first instance ID according to the association information; acquiring the first instance according to the first instance ID Recording a file; deleting a correspondence between the second instance ID and the plan ID of the first instance in the record file of the first instance, and/or acquiring the first according to the record file of the first instance a node record file of the instance, deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of the node of the first instance; performing according to the description file of the second service The deletion plan.

In conjunction with the twelfth aspect, in a third possible implementation of the twelfth aspect, the apparatus further includes a transmitting unit, the receiving unit further configured to: record at the processing unit in the first instance Recording, in the file, a correspondence between the second instance ID and a plan ID of the first instance, and/or recording the second instance ID and the first instance in a node record file of the first instance After receiving the corresponding relationship of the method ID of the node, receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and a plan ID to be executed; the processing unit is further configured to: according to the first The instance ID acquires the record file of the first instance; and determines the plan to be executed according to the correspondence between the second instance ID recorded in the record file of the first instance and the plan ID of the first instance. The execution of the plan corresponding to the ID is restricted by the second instance; the sending unit is configured to: send a message rejecting execution of the plan to be executed to the sending end; and/or

The receiving unit is further configured to: receive an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed; the processing unit is further configured to: execute according to the Determining the node record file to be executed; determining the to-be-executed according to the correspondence between the second instance ID recorded in the node record file to be executed and the method ID of the node of the first instance The execution of the method corresponding to the method ID of the node is restricted by the second instance; the sending unit is configured to: send a message rejecting the method of executing the node to be executed to the Said sender.

In the embodiment of the present application, the received service deployment request includes the restriction information, where the first service is the deployed service. Therefore, when the new service is deployed, that is, the second service, in addition to executing the deployment plan to deploy the second service, according to the restriction information, the record is recorded in the record file corresponding to the second instance of the deployed second service. Correlation information of an instance ID, and recording a correspondence relationship between the second instance and the plan of the first instance in the record file of the first instance, and/or recording the second instance and the first instance in the node record file of the first instance Correspondence of the methods of the nodes. Since only the restriction information needs to be included in the service deployment request without writing all the contents of the first service deployment package, resources for developing the service deployment package and transmission resources are saved. Moreover, as long as the association information is recorded in the log file of the second instance, the correspondence between the plan of the second instance and the plan of the first instance and/or the method of the node of the second instance and the first instance are recorded in the log file of the first instance The corresponding relationship, without having to deploy the content of the deployment package of the first service again, thus saving the deployment resources of the server. Further, by limiting the method of executing the plan and/or node of the first instance, it is possible to avoid the second service being inoperable due to execution of these plans and/or methods.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following description of the embodiments will be briefly described. It is obvious that the drawings in the following description are only some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

1 is a diagram showing the relationship between elements in a file in the prior art;

2 is a schematic diagram of a topological relationship between service A and service B in the prior art;

3 is a schematic diagram of combining service A and service B into one service C in the prior art;

4 is a flowchart of a service deployment method in an embodiment of the present application;

FIG. 5 is a flowchart of a method for service management according to an embodiment of the present application;

6 is a flowchart of a method for service management in another embodiment of the present application;

FIG. 7 is a functional block diagram of a service deployment apparatus according to an embodiment of the present application;

8 is a system block diagram of a server in an embodiment of the present application;

FIG. 9 is a functional block diagram of a service management apparatus according to an embodiment of the present application; FIG.

Figure 10 is a system block diagram of a server in another embodiment of the present application;

11 is a functional block diagram of a service management apparatus in another embodiment of the present application;

12 is a system block diagram of a server in still another embodiment of the present application;

FIG. 13 is a flowchart of a service deployment method according to an embodiment of the present application;

14 is a flowchart of a method for service management in an embodiment of the present application;

15 is a flowchart of a method for service management in an embodiment of the present application;

16 is a flowchart of a method for service deployment in an embodiment of the present application;

17 is a flowchart of a method for service management in an embodiment of the present application;

FIG. 18 is a functional block diagram of a service deployment apparatus according to an embodiment of the present application;

19 is a functional block diagram of a service deployment apparatus in still another embodiment of the present application;

20 is a system block diagram of a server in an embodiment of the present application;

21 is a system block diagram of a server in still another embodiment of the present application.

detailed description

The embodiment of the present application provides a service deployment method, a service management method, and a device, which are used to solve the technical problem of merging resources caused by deployed services when deploying a new service in the prior art.

The technical solution in the embodiment of the present application is to solve the above technical problem, and the general idea is as follows:

1. The second description file of the second service includes information that the second service restricts execution of the plan of the first instance ID of the first service and/or the method of the node of the first instance ID, where the first service is The deployed service. When the new service is deployed, that is, the second service, in addition to executing the deployment plan to deploy the second service, according to the information, the second instance is recorded in the first description file of the first service or the record file of the first instance. The correspondence between the ID and the method of the first instance ID and/or the method of the node of the first instance ID.

2. The CSP server receives the service deployment request sent by the CSC device, and further includes, by the second service, restriction information of a method for executing the first instance of the first service and/or a method for the node of the first instance. When the new service is deployed, that is, the second service, in addition to executing the deployment plan to deploy the second service, the association information is recorded in the record file of the second instance according to the restriction information, and the association information includes at least the first instance. ID; the correspondence between the plan of the second instance and the plan of the first instance and/or the method of the method of the second instance and the node of the first instance is recorded in the log file of the first instance. The record file is a file that records configuration parameters, an operation status, an operation record, and the like of the instance, or a file created by the CSP server. The specific form of the record file is not limited in the present invention.

The technical solutions in the embodiments of the present application are clearly described in the following with reference to the accompanying drawings in the embodiments of the present application. It is obvious that the described embodiments are Some embodiments are applied, not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

An embodiment of the present application provides a service deployment method. Referring to FIG. 4, it is a flowchart of a service deployment method in this embodiment. The method includes the following content:

Step 101: Receive a service deployment package of a second service, where the service deployment package includes a deployment plan and a second description file.

Step 102: After executing the deployment plan according to the second description file, acquiring a second instance identifier (ID) of the second service that has been deployed;

Step 103: Determine, in the second description file, information that includes, by the second service, a method of executing a plan of the first instance ID of the first service and/or a method of a node of the first instance ID;

Step 104: Acquire a first description file of the first service according to the first instance ID.

Step 105: Record, according to the second service, the information of the method of executing the first instance ID of the first service and/or the method of the node of the first instance ID, and record the second instance ID and the first instance in the first description file. Correspondence between the plan of the ID and/or the method of the node of the first instance ID.

Wherein, the method of restricting execution of the plan of the first instance ID and/or the node of the first instance ID means that the restricted plan and/or method is not allowed to be executed during the restriction execution. Here, the restriction execution period refers to a period in which the correspondence relationship between the second instance ID and the method of the first instance ID and the method of the node of the first instance ID is recorded in the first profile.

In this embodiment, it is assumed that the service deployment package of the first service and the second service both include two plans: a deployment plan (BuildPlan) and a delete plan (TerminatePlan). Each node in the first service and the second service has four methods: start, configure, stop, and remove. In practice, the service deployment package can also include other plans, such as a restart plan. The method of each node can also be other methods, such as restarting. This application is not specifically limited.

At this point, assume that the first service (ServiceA) has been deployed, that is, running on the cloud platform. The service instance ID of the first service (ServiceA), that is, the first instance ID is ServiceA-1; the first description file, for example, the file name of the description file A is named ServiceA.ste. Further, the CSP server also records the mapping file A and the first instance ID, that is, the mapping relationship between ServiceA.ste and ServiceA-1. It should be noted that, when the first service is deployed on different servers, there will be different service instance IDs. In this embodiment, it is assumed that the service instance ID of the first service on the server is the first instance ID. The other service instance IDs of the first service are implemented in the same way.

Assume that the second service is ServiceB, and the second description file of the second service is description file B, wherein the file name of the description file B is ServiceB.ste.

When the second service needs to be deployed, the CSC device sends the service deployment package of the second service to the CSP server. That is, the CSP server performs step 101 in the method of this embodiment, and receives a service deployment package of the second service, where the service deployment package includes a deployment plan and a description file B. In other embodiments, the service deployment package may also include other plans, such as deleting the plan, restarting the plan, and the like.

After receiving the service deployment package of the second service, the deployment plan may be executed according to the second description file.

Then, step 102 is performed to obtain a second instance ID of the deployed second service after the deployment is completed.

The execution deployment plan is well known to those skilled in the art, so it will not be described here. The second instance ID is obtained, for example, the CSP server creates or allocates an instance ID to ServiceB-1 for ServiceB.

Next, step 103 is performed to determine information in the second description file that includes the second service restriction method of executing the plan of the first instance ID and/or the node of the first instance ID.

Specifically, in order to be able to describe the limitation of the second service to the plan of the first instance ID and/or the method of the node of the first instance ID, a policy named "Limitation" may be defined in the second profile. Type (PolicyType) defines a policy template (PolicyTemplate) of the policy type under the service template (ServiceTemplate) in the second description file. Specific definitions of policy types and policy templates may be, but are not limited to, the following two types, which are called (I) type and (II) type, respectively. The attributes "appliesToService" and "appliesFromService" in the (I) type are for the PolicyTemplate; while in the (II) type, both attributes are for the restricted plan and / Or the method of the node.

Among them, the type of strategy of type (I), "Limitation" can be defined by code (1). In its In the embodiment, the naming of the policy type can be arbitrarily set, which is not limited in this application.

The PolicyType name describes the name of the policy type. In this example, the restriction is Limitation; the attribute definition element PropertiesDefinition element describes the restricted element, such as a method or plan. In this example, the attribute describes the restricted method or plan, and passes The Operation id gives the method name that is restricted, and the NodeTemplateID describes the method to which the restricted method belongs. If you need to limit multiple methods, you can use the code (1) to write a multi-line Operation id and a NodeTemplateID corresponding to the Operation id. The Plan id describes the plan that needs to be restricted.

The policy template of type (I) can be defined by code (2).

Code (2): <PolicyTemplate id=“string4” name=“string5” type=“Limitation” applicantToService=“string6”appliesFromService=“string7”>//The id of the policy template is string4, the name is string5, and the type is Limitation. The requested service is string6 and the requested service is string7.

The PolicyTemplate id describes the id of the policy template, the name describes the name of the policy template, and the type describes the type of the policy description, for example, the type described by the code (1). The attribute "appliesToService" is used to describe the requested service, and the attribute "appliesFromService" is used to describe the requested service.

In code (1) and code (2), a general example is given, in which string represents a field. In actual use, the part of string needs to be replaced with the actual field. In the template of this embodiment, Differentiate the definition of different fields by string plus numbers.

In code (1) and code (2), the name of PolicyType is "Limitation", which means that it is a restriction on the plan of the service and / or the method of the node; it has two attributes, "LimitedOperations" and "LimitedPlans" Represents restricted methods and plans. Since each node may have the same name method, when describing the method, in addition to giving the id of the method, the ID of the corresponding NodeTemplate is also given, indicating which NodeTemplate the method belongs to. There is no plan with the same id in a service, so just give the id of the plan.

When the PolicyTemplate is described, its type is "Limitation", indicating that the PolicyTemplate is an example of a PolicyType named "Limitation". The embodiment of the present application uses the applicantToService to describe the ID of the requested service instance, that is, the first instance ID is the restricted service instance. At the same time, you need to add a new field to describe which service instance the PolicyTemplate comes from. The present invention uses the applicantFromService to record the requested service instance ID, that is, to restrict the service instance from the second instance ID.

For example, in this embodiment, it is assumed that the deletion plan of ServiceA, the execution of the Stop and Remove methods of each node affect the normal operation of ServiceB, and the ServiceB deletes the plan of the ServiceA instance (TerminatePlan), and the Stop and Remove of each node. The execution of the method is restricted, then the PolicyTemplate of type (I) in the description file B of ServiceB can be defined by code (3):

The policy template in code (3) indicates that Service B needs to restrict the execution of the first instance ID, the plan and method of ServiceA-1, and describes the id of the plan that restricts execution and the id of the method and the ID of the node template to which the method belongs.

In practice, in addition to defining the policy type by means of code (1), other ways can be used to define the policy type, such as the type of policy of type (II), as shown in code (4).

The PolicyType name describes the name of the policy type. In this example, the restriction is Limitation; the attribute definition element PropertiesDefinition element describes the restricted element, such as a square. Method or plan, in this example, the attribute describes the restricted method or plan, and the method name is given by the Operation id, and the NodeTemplateID describes the method to which the restricted method belongs. If you need to limit multiple methods, you can use the code (4) to write a multi-line Operation id and a NodeTemplateID corresponding to the Operation id. The Plan id describes the plan that needs to be restricted. And, after each defined method and plan, describe the services to which these methods and plans belong by the attribute "appliesToService", and describe the services that limit these methods and plans through the attribute "appliesFromService".

Corresponding code (4), (II) type policy template can be defined by code (5).

Code (5): <PolicyTemplate id=“string15” name=“string16” type=“Limitation”/>//The id of the policy template is string15, the name is string16, and the type is “Limitation”.

Among them, in the code (5) and the code (6), the meaning of the string is the same as the foregoing description, and is a substitute symbol in the general template. In actual use, it is necessary to replace the real field.

Continuing with the example of type (I), the PolicyTemplate of type (II) describing the plan of the service instance of ServiceA and the method limitation of the node in the description file B of ServiceB can be described by code (6).

It can be seen from this that in the code of type (II), the requested service instance in the policy template is directly written after the method of the plan and the node that is restricted from being executed. In the code (3) of type (I), the requested service instance is written after the policy template.

Next, step 103 will be described. Therefore, whether through the description of the (I) type or the (II) type, as long as the definition of the policy template in the file B, the attribute appliesToService=“ServiceA-1”, it can be stated that the second service refers to one of the ServiceA. An instance where the ID of the referenced ServiceA instance is ServiceA-1. The description file B also defines the policy type as shown in code (1) or code (4), and the restrictions on the plan and/or method of the instance whose instance ID is ServiceA-1, such as code (3) (corresponding to type I) ) and code (6) (corresponding to type II). Therefore, the CSP server can know, according to the second description file, that the second description file includes information that the ServiceB restricts execution of the first instance ID, the plan of the ServiceA-1 (delete plan), and the methods of all the nodes (Stop and Remove), and The first instance ID can be obtained. In this embodiment, the first instance ID is ServiceA-1.

Next, step 104 is performed, that is, the first description file of the first service is obtained according to the first instance ID. Specifically, for example, the CSP server queries the first description file corresponding to the first instance ID according to the mapping relationship between the recorded description file and the instance ID. In the present embodiment, for example, the description file A, ServiceA.ste is obtained.

When the first description file is obtained, step 105 is performed, according to which the second instance ID and the plan of the first instance ID and/or the node of the first instance ID are recorded in the first description file. The corresponding relationship of the methods.

Optionally, before performing step 105, it may be checked whether a policy type named “Limitation” is already present in the first description file.

For the case of (I) type, if not, copy the policy type in the second description file to the first description file according to the information, and then copy the policy template described in the code (3) to the first description. Under the service template in the file, where "appliesToService="ServiceA-1" is not copied. The restriction is recorded by the attribute "appliesFromService" from the second instance ID of the second service, such as the service instance ServiceB-1 of ServiceB.

If yes, copy the policy template described in code (3) to the service template in the first description file, where "appliesToService="ServiceA-1" is not copied. The restriction is recorded by the attribute "appliesFromService" from the second instance ID of the second service, such as the service instance ServiceB-1 of ServiceB.

Continuing with the foregoing example, then in the first description file, such as description file A, the policy template of type (I) is described by code (7).

For the case of type (II), if not, copy the policy type in the second description file to the first description file, for example, copy the policy type in the description file B into the description file A. Then copy the policy template described in the code (6) to the service template in the description file A, and do not copy "appliesToService = "ServiceA-1"". And, the restriction is recorded by the attribute "appliesFromService" from the second service instance ID of the second service, such as the service instance ServiceB-1 of ServiceB.

If any, copy all child elements of the restricted plan (LimitedPlans) in code (6) to the child element restriction plan (LimitedPlans) of the policy template of type "Limitation" in profile A, without copying "appliesToService="ServiceA -1"". And, the restriction is recorded by the attribute "appliesFromService" from the second service instance ID of the second service, such as the service instance ServiceB-1 of ServiceB. The restricted method (LimitedOperations) in code (6) is handled in the same way.

The complete (II) type of policy template after processing is described in the description file A as shown in code (8).

In an actual application, in addition to the manner described in the foregoing embodiments, the second service may be further described in the second description file to limit the execution of the plan of the first instance ID and/or the node method of the first instance ID. The application does not limit this. In addition, how to record the correspondence between the second instance ID and the method of the first instance ID and/or the method of the node of the first instance ID is not limited in this application.

As can be seen from the above description, since the second description file contains information on the method of the plan and/or the node that needs to be restricted, without saving all the contents in the first service deployment package, the development service is saved. The resources of the deployment package and the transmission resources. Moreover, as long as the correspondence between the second instance ID and the method of the first instance ID and/or the method of the node of the first instance ID is written in the description file of the first service, the first service is not deployed again. The content of the deployment package saves the server's deployment resources. Further, by restricting the method of executing the plan and/or node of the first instance ID, it is possible to avoid the second service from being inoperable due to execution of the methods of these plans and/or nodes.

After the second service is deployed by the foregoing service deployment method, management of the first service and the second service may be involved, and the management process for the first service will be described first.

Please refer to FIG. 5, which is a flowchart of a service management method in an embodiment of the present application, where the method includes the following content:

Step 201: Receive a management request sent by the sending end for the first instance ID of the first service, where the management request includes the first instance ID and a method of the plan and/or the node to be executed.

For example, for example, the CSC device wants to execute a plan or node method in the instance ServiceA-1 of ServiceA, such as a delete plan (TerminatePlan). Then, the client sends a management request to the CSP server, where the management request includes the ID of the ServiceA instance, ServiceA-1, and the node to which the plan and/or method and method to be executed belong.

Step 202: Acquire a first description file of the first service according to the first instance ID, where the second instance ID of the second service and the plan of the first instance ID and/or the first instance ID are recorded in the first description file. The correspondence of the methods of the nodes.

For example, the corresponding relationship is specifically written in the manner described in the steps 101 to 105 in the embodiment of FIG. 4, and may be written in other manners, which is not limited in this application.

The process of obtaining the first description file of the first service according to the first instance ID is similar to the foregoing step 104, and therefore is not described herein again.

Step 203: Determine, according to the correspondence, that the execution of the plan to be executed and/or the method of the node is restricted by the second service.

Specifically, by detecting the first description file, determining whether the plan and/or method to be executed is located in the correspondence between the second instance ID and the plan and/or method in which the second instance limits the first instance ID, and if so, It can then be determined that the execution of the plan and/or the method of the node to be executed is limited by the second service. Otherwise no.

For example, check the description file A to determine the limit of the ServiceB instance ServiceB-1 to the TerminatePlan of the instance ServiceA-1. For the case of type (I), look at the policy template with the id "LimitedTemplate" in the code (7). If "TerminatePlan" appears in "LimitedPlans", the deletion plan is restricted. For the case of type (II), check whether the plan with the plan id "TerminatePlan" is included in the code (8). If there is, it means that the delete plan is restricted to execute, otherwise it is not.

Step 204: If restricted, send a message rejecting the method of executing the plan and/or the node to be executed to the sender.

For example, by the determining process of step 203, it is determined that the plan and/or method to be executed is subject to the second The restriction of the service, then a rejection message is sent to the sender.

Optionally, the second instance ID of the second service may be included in the reject message. For example, the service instance ID ServiceB-1 of ServiceB is included to indicate that ServiceB-1 has restricted the instance ServiceA-1, thereby rejecting the request. This can ensure that the normal operation of the second service is not affected.

Regarding the second instance ID, specifically the value of the attribute "appliesFromService" in the code (7) or the code (8), so reading the value of the attribute, the second instance ID of the second service, that is, ServiceB- 1.

Alternatively, when it is determined that the execution of the plan and/or method to be executed is not restricted by the second service, the plan and/or method to be executed may be executed, such as deleting the plan.

Optionally, the plan to be executed is at least one of a deletion plan, a restart plan, and a stop plan; the method to be executed is at least one of a delete method, a restart method, and a stop method.

Of course, in actual use, it may also be a method of other plans and/or nodes, which is not limited in this application.

As can be seen from the above description, when managing the first service, it is first determined that the execution of the plan and/or method to be executed is not limited by other services, if the execution of the plan and/or the method of the node is performed. If there are restrictions on other services, the request is rejected. In this way, when the first service is managed, it is guaranteed that the normal operation of the service that restricts the execution of the method of the plan and/or the node is not affected.

Next, the management process of the second service is described. Referring to FIG. 6, a flowchart of the method for managing the second service in this embodiment is shown. The method includes the following:

Step 301: Receive a deletion request for a second instance ID of the second service, where the deletion request includes a second instance ID and a deletion plan to be executed.

For example, the second instance ID included in the delete request is ServiceB-1. The deletion plan to be executed included in the deletion request is TerminatePlan.

Step 302: Acquire a service deployment package of the second service according to the second instance ID, where the service deployment package includes a deletion plan and a second description file.

For example, the service deployment package is obtained through the instance ID ServiceB-1, and the deployment package includes a description file B and a TerminatePlan.

Step 303: Determine information that the second description file includes a method for restricting execution of the plan of the first instance ID and/or the method of the node of the first instance ID.

Specifically, if there is a restriction on the plan of the first instance ID and/or the method of the node in the second description file, the second description file includes the code (3) and the code (6) as described above, so It is determined whether the second service has restrictions on the execution of the plans of other service instances and/or the methods of the nodes by checking whether the second description file contains such code segments. And, the restricted service instance ID can be known from the value of the attribute "appliesToService" in the code segment.

In this embodiment, the first service generally refers to all services that are restricted by the second service, including, for example, ServiceA, and/or ServiceD.

Assuming that the second service is ServiceB and the first service is ServiceA, it can be seen from the description of the foregoing embodiment that the description file B has restrictions on the execution of the plan of the ServiceA-1 and/or the method of the node.

When the result is not, then the deletion plan can be executed directly.

When the result is sometimes, then step 304 is performed: inserting a flag before the first method of the first node of the deletion plan, the flag indicating that the second service is released from the plan and/or the first instance ID A limitation of the execution of the method of a node of an instance ID.

A plan is a workflow consisting of methods, so insert a tag before deleting the first method of the first node of the plan.

Assume that the initial TerminatePlan is:

TerminatePlan:

AppB.Stop; method Stop of node AppB;

AppBDb.Stop; method Stop of node AppBDb;

Apache.Stop; node Apache method Stop;

MySql.Stop; node MySql method Stop;

AppB.Remove; method of the node AppB Remove;

AppBDb.Remove; method of the node AppBDb Remove;

Apache.Remove; node Apache method Remove;

MySql.Remove; node Apache's method Remove.

Then in this embodiment, the first method of the first node is AppB.Stop.

After the modification of step 304, the deletion plan after inserting the mark is:

TerminatePlan:

DELETE_LIMITATION; / / remove the restrictions on other service instances

AppB.Stop;

AppBDb.Stop;

Apache.Stop;

MySql.Stop;

AppB.Remove;

AppBDb.Remove;

Apache.Remove;

MySql.Remove.

Step 305: Perform a deletion plan after inserting the mark.

Specifically, when performing the deletion plan after inserting the mark, when performing the markup, the method specifically includes: acquiring a first instance ID from the second description file; acquiring the first service according to the first instance ID The first description file; the correspondence between the second instance ID recorded in the first description file and the method of the first instance ID and the method of the node of the first instance ID.

The correspondence in the first description file is deleted, thereby relieving the restriction of the second service on the planning of the first instance ID and/or the execution of the method of the node, so that the plan and/or method can be executed.

The first instance ID is obtained by using the second description file. The instance ID of the restricted service can be obtained by using the value of the attribute “appliesToService” in the code segment in the second description file as described above.

For example, for the case of type (I), obtain the PolicyTemplate of the type "Limitation" in the description file B, such as the value of the attribute "appliesToService" of the code (3), and the value ServiceA-1 is the service instance of ServiceA. ID. For the case of the type (II), the value of the attribute "appliesToService" of the Plan element and the Operation element in the PolicyTemplate (such as code 6) of the type "Limitation" in the description file B is obtained (in this embodiment, the serviceA-1) ), this value is the ID of the service instance of ServiceA.

The step of obtaining the first description file of the first service by using the first instance ID may also be implemented in the foregoing manner. For example, the CSP server stores the mapping relationship between the instance ID and the description file, so the mapping relationship may be obtained by querying the mapping relationship. The first description file corresponding to the first instance ID.

The correspondence recorded in the first description file is deleted. Specifically, in the case of the (I) type, the PolicyTemplate of the type "Limitation" is deleted in the description file A, and the value of the attribute "appliesFromService" is ServiceB-1.

Optionally, check whether the description file A also includes a PolicyTemplate of the type "Limitation", and if not, delete the PolicyType whose ID is "Limitation".

For the case of type (II), find the PolicyTemplate of type "Limitation" in the description file A, and delete all the Plane elements and Operation elements of the service "appliesFromService" value of ServiceB-1.

Optionally, checking whether the LimitedPlans element and/or the LimitedOperations element in the PolicyTemplate include a child element, if not, deleting the LimitedPlans element and/or the LimitedOperations element; if there is no child element in the PolicyTemplate, deleting the PolicyTemplate and the ID is “ PolicyType of Limitation.

After the content related to the mark is executed in step 305, each method on each node in the deletion plan is executed one by one from the first method, which is a content well known to those skilled in the art, so it will not be described here. .

As can be seen from the above description, even if the second service has restrictions on the execution of the plan of the instance of the first service and/or the method of the node, the second service can be separately managed to ensure the independence of the second service management. Increased flexibility in service management.

Based on the same inventive concept, the embodiment of the present application further provides a service deployment apparatus. Referring to FIG. 7, the service deployment apparatus includes: a receiving unit 401, configured to receive a service deployment package of a second service, where the service deployment package The processing unit 402 is configured to: after executing the deployment plan according to the second description file, acquire a second instance identifier ID of the second service that has been deployed; and determine that the second description file includes the second The service restricts the information of the method of executing the first instance ID of the first service and/or the method of the node of the first instance ID; acquiring the first description file of the first service according to the first instance ID; executing the first according to the second service restriction Information of a plan of the first instance ID of the service and/or a method of the node of the first instance ID, the node of the second instance ID and the plan of the first instance ID and/or the node of the first instance ID is recorded in the first profile The corresponding relationship of the methods, as well as deploying the second service according to the service deployment package.

Optionally, the receiving unit 401 is further configured to: after the processing unit 402 records the correspondence between the second instance ID and the method of the first instance ID and the method of the node of the first instance ID in the first description file, For the deletion request of the second instance ID, the deletion request includes the second instance ID and the deletion plan to be executed;

The processing unit 402 is further configured to: obtain a service deployment package according to the second instance ID, and the service deployment package further Included in the deletion plan; determining information in the second description file that includes a method for the second service to restrict execution of the plan of the first instance ID and/or the node of the first instance ID; before deleting the first method of the first node of the plan Insertion of a mark indicating a restriction to release the second service from the plan of the first instance ID and/or the method of the node of the first instance ID; the deletion plan after the insertion of the mark is performed.

Further, the processing unit 402 is specifically configured to: obtain a first instance ID from the second description file; acquire the first description file according to the first instance ID; and delete the second instance ID and the first instance ID recorded in the first description file. Corresponding relationship between the method of the node of the plan and/or the first instance ID; starting from the first method, executing the deletion plan to be executed.

Optionally, the device further includes a sending unit,

The receiving unit 401 is further configured to: after the processing unit 402 records the correspondence between the second instance ID and the method of the first instance ID and the method of the node of the first instance ID in the first description file, the receiving terminal sends the For the management request of the first instance ID, the management request includes a first instance ID and a method of the plan and/or node to be executed;

The processing unit 402 is further configured to: acquire the first description file according to the first instance ID;

Determining, according to the correspondence between the second instance ID recorded in the first description file and the method of the first instance ID and/or the method of the node of the first instance ID, determining that the execution of the plan and/or the method of the node is performed by the second Service restrictions;

The sending unit is configured to: send a message rejecting execution of the plan to be executed and/or the method of the node to the sending end.

The various changes and specific examples in the service deployment method in the foregoing embodiment of FIG. 4 are also applicable to the service deployment device of the embodiment. The foregoing description of the service deployment method can be clearly known to those skilled in the art. In the example, the implementation method of the service deployment device is not detailed here for the sake of brevity of the description.

Based on the same inventive concept, the embodiment of the present application further includes a server. Please refer to FIG. 8 , which is a system block diagram of a server in the embodiment of the present application. As shown in FIG. 8, the server includes: a receiver 501, configured to receive a service deployment package of a second service, where the service deployment package includes a deployment plan and a second description file; and the processor 502 is configured to perform according to the second description. After the file executes the deployment plan, acquiring a second instance identifier ID of the second service that has been deployed; determining, in the second description file, a plan and/or a first instance ID of the second instance that restricts execution of the first instance ID of the first service Information of the method of the node; acquiring the first description file of the first service according to the first instance ID; executing the first service according to the second service restriction Recording information of the first instance ID and/or the method of the node of the first instance ID, in the first description file, recording the second instance ID with the plan of the first instance ID and/or the node of the first instance ID Corresponding relationship of the methods, and deploying the second service according to the service deployment package.

Optionally, the receiver 501 is further configured to: after the processor 502 records the correspondence between the second instance ID and the method of the first instance ID and the method of the node of the first instance ID in the first description file, For the deletion request of the second instance ID, the deletion request includes the second instance ID and the deletion plan to be executed;

The processor 502 is further configured to: obtain a service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan; and determine that the second description file includes a second service restriction to execute the first instance ID and/or the first instance ID. The information of the method of the node; inserting a mark before deleting the first method of the first node of the plan, the mark indicating the execution of the method of releasing the plan of the first instance ID and the node of the first instance ID of the second service ID Restriction; the deletion plan after the insertion tag is executed.

Further, the processor 502 is specifically configured to: obtain a first instance ID from the second description file; acquire the first description file according to the first instance ID; and delete the second instance ID and the first instance ID recorded in the first description file. Corresponding relationship between the method of the node of the plan and/or the first instance ID; starting from the first method, executing the deletion plan to be executed.

Optionally, the device further includes a transmitter 503,

The receiver 501 is further configured to: after the processor 502 records the correspondence between the second instance ID and the method of the first instance ID and the method of the node of the first instance ID in the first description file, the receiving sender sends the For the management request of the first instance ID, the management request includes a first instance ID and a method of the plan and/or node to be executed;

The processor 502 is further configured to: acquire the first description file according to the first instance ID;

The sender 503 is configured to: send a message rejecting execution of the plan to be executed and/or the method of the node to the sender.

Further, in FIG. 8, a bus architecture (represented by bus 500), bus 500 can include any number of interconnected buses and bridges, and bus 500 will include one or more processors and memory 504 represented by processor 502. The various circuits of the memory are linked together. Bus 500 can also Various other circuits, such as peripherals, voltage regulators, and power management circuits, are linked together, which are well known in the art and, therefore, will not be further described herein. Bus interface 505 provides an interface between bus 500 and processor 502, receiver 501, and transmitter 503. The receiver 501 and the transmitter 503 are used for data communication between the server and an external device.

The processor 502 is responsible for managing the bus 500 and the usual processing. Memory 504 can be used to store data used by processor 502 in performing operations.

This server is for example a CSP server.

The various changes and specific examples in the service deployment method in the foregoing embodiment of FIG. 4 are also applicable to the server in this embodiment. The foregoing detailed description of the service deployment method can be clearly known to those skilled in the art. The implementation method of the server, so for the sake of brevity of the description, it will not be described in detail here.

Based on the same inventive concept, the embodiment of the present application further provides a service management apparatus. Referring to FIG. 9, the service deployment apparatus includes: a receiving unit 601, configured to receive a first instance identifier for a first service sent by a sending end. a management request of the ID, the management request includes a first instance ID and a method of the plan and/or the node to be executed; the processing unit 602 is configured to acquire the first description file of the first service according to the first instance ID; according to the first description file Corresponding relationship between the second instance ID of the second service recorded in the plan of the first instance ID and the method of the node of the first instance ID, determining that the execution of the plan and/or the method of the node is performed by the second service The sending unit 603 is configured to send a message to the sending end that rejects the method of executing the plan and/or the node to be executed.

Optionally, the plan to be executed is at least one of a deletion plan, a restart plan, and a stop plan; the method of the node to be executed is at least one of a delete method, a restart method, and a stop method.

The various changes and specific examples in the service deployment method in the foregoing embodiment of FIG. 5 are also applicable to the service management apparatus of this embodiment. Through the foregoing detailed description of the service deployment method, those skilled in the art can clearly understand the implementation. In the example, the method of implementing the service management device is not described in detail for the sake of brevity of the description.

Based on the same inventive concept, the embodiment of the present application further includes a server. Referring to FIG. 10, it is a system block diagram of a server in the embodiment of the present application. As shown in FIG. 10, the server includes: a receiver 701, configured to receive a management request sent by a sending end for a first instance identifier ID of the first service, where the management request includes a first instance ID and a plan to be executed and/or a method of the node; the processor 702, configured to acquire, according to the first instance ID, a first description file of the first service; according to the first record in the first description file Corresponding relationship between the second instance ID of the second service and the method of the first instance ID and/or the method of the node of the first instance ID, determining that the execution of the plan and/or the method of the node is restricted by the second service; And 703, configured to send a message to the sender that rejects the method of executing the plan and/or the node to be executed.

Further, in FIG. 10, a bus architecture (represented by bus 700), bus 700 can include any number of interconnected buses and bridges, and bus 700 will include one or more processors and memory 704 represented by processor 702. The various circuits of the memory are linked together. The bus 700 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art and, therefore, will not be further described herein. Bus interface 705 provides an interface between bus 700 and processor 702, receiver 701, and transmitter 703. The receiver 701 and the transmitter 703 are used for data communication between the server and an external device.

The processor 702 is responsible for managing the bus 700 and the usual processing. Memory 704 can be used to store data used by processor 702 in performing operations.

This server is for example a CSP server.

The various changes and specific examples in the service management method in the foregoing embodiment of FIG. 5 are also applicable to the server in this embodiment. The foregoing detailed description of the service management method can be clearly known to those skilled in the art. The implementation method of the server, so for the sake of brevity of the description, it will not be described in detail here.

Based on the same inventive concept, the embodiment of the present application further provides a service management apparatus. Referring to FIG. 11, the service deployment apparatus includes: a receiving unit 801, configured to receive a deletion request for a second instance identifier ID of the second service. The deletion request includes a second instance ID and a deletion plan to be executed; the processing unit 802 is configured to obtain a service deployment package of the second service according to the second instance ID, where the service deployment package includes a deletion plan and a second description file; The second description file includes information that the second service restricts execution of the plan of the first instance ID of the first service and/or the method of the node of the first instance ID; inserts the mark before deleting the first method of the first node of the plan The flag indicates a restriction to release the second service from the plan of the first instance ID and/or the method of the node of the first instance ID; the deletion plan after the insertion of the tag is performed.

Optionally, the processing unit 802 is specifically configured to: acquire the first description file of the first service according to the first instance ID; delete the plan and/or the second instance ID and the first instance ID recorded in the first description file. Correspondence of the method of the node of the instance ID; starting from the first method, executing the deletion plan to be executed.

The various changes and specific examples in the service deployment method in the foregoing embodiment of FIG. 6 are also applicable to the service management apparatus in this embodiment. The foregoing description of the service deployment method can be clearly known to those skilled in the art. In the example, the method of implementing the service management device is not described in detail for the sake of brevity of the description.

Based on the same inventive concept, the embodiment of the present application further includes a server. Referring to FIG. 12, it is a system block diagram of a server in the embodiment of the present application. As shown in FIG. 10, the server includes: a receiver 901, configured to receive a deletion request for a second instance identifier ID of the second service, where the deletion request includes a second instance ID and a deletion plan to be executed; the processor 902, a service deployment package for acquiring a second service according to the second instance ID, the service deployment package includes a deletion plan and a second description file; and determining, in the second description file, a plan that includes the second service restriction to execute the first instance ID of the first service And/or information of the method of the node of the first instance ID; inserting a flag before the first method of deleting the first node of the plan, the flag indicating that the second service is released from the plan and/or the first instance of the first instance ID The execution limit of the method of the node of the ID; the deletion plan after the insertion of the markup.

Optionally, the processor 902 is specifically configured to: acquire the first description file of the first service according to the first instance ID; delete the plan and/or the first instance ID and the first instance ID recorded in the first description file. Correspondence of the method of the node of the instance ID; starting from the first method, executing the deletion plan to be executed.

Further, in FIG. 12, a bus architecture (represented by bus 900), bus 900 can include any number of interconnected buses and bridges, and bus 900 will include one or more processors and memory 904 represented by processor 902. The various circuits of the memory are linked together. The bus 900 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein. Bus interface 905 provides an interface between bus 900 and processor 902, receiver 901, and transmitter 903. The receiver 901 and the transmitter 903 are used for data communication between the server and an external device.

Processor 902 is responsible for managing bus 900 and the usual processing. Memory 904 can be used to store data used by processor 902 in performing operations.

This server is for example a CSP server.

The various changes and specific examples in the service management method in the foregoing embodiment of FIG. 6 are also applicable to the server in this embodiment. The foregoing detailed description of the service management method can be clearly known to those skilled in the art. The implementation method of the server, so for the simplicity of the manual, This is not detailed.

One or more technical solutions provided in the application embodiments have at least the following technical effects or advantages:

In the embodiment of the present application, the second description file of the second service includes information that the second service restricts the method of executing the first instance ID of the first service and/or the method of the node of the first instance ID, where A service is a deployed service. Therefore, when the new service, that is, the second service, is deployed, in addition to executing the deployment plan to deploy the second service, the second instance ID and the first instance are recorded in the first description file of the first service according to the information. Correspondence between the plan of the ID and/or the method of the node of the first instance ID. Since the second description file contains information that needs to restrict the execution of the plan and/or method without writing all the contents of the first service deployment package, the resources of the development service deployment package and the transmission resources are saved. Moreover, as long as the correspondence between the second instance ID and the method of the first instance ID and/or the method of the node of the first instance ID is written in the description file of the first service, the first service is not deployed again. The content of the deployment package saves the server's deployment resources. Further, by limiting the method of executing the plan and/or node of the first instance ID, it can be avoided that the second service cannot be run due to execution of these plans and/or methods.

FIG. 13 is a flowchart of a method for service deployment according to another embodiment of the present invention. The difference between this embodiment and the embodiment shown in FIG. 4 is that, in this embodiment, the CSP server uses the second instance and the first instance. The correspondence between the plan and/or the method of the second instance and the node of the first instance is recorded in the log file instead of the profile of the first service (i.e., the first profile in the embodiment described in FIG. 4). Since this correspondence is recorded in the log file instead of the profile of the first service, subsequent instances that are subsequently deployed for the first service will not be affected by the second instance of the second service. As shown in FIG. 13, the method provided in this embodiment includes the following steps:

Step 1301: Receive a service deployment request, where the service deployment request includes information about a service deployment package of the second service.

Specifically, the information about the service deployment package of the second service may be a service deployment package identifier or a Uniform Resource Identifier (URI) of the service deployment package, and the specific form of the information of the service deployment package is not used by the present invention. limited.

Step 1302: Obtain a service deployment package of the second service according to the information about the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a second service Description file

Specifically, the service deployment package of the second service may be sent to the CSP server to be saved locally before the CSC device sends the service deployment request, or uploaded to the third-party device on the network side by the CSC device, or deployed with the service. Requests are sent to the CSP device together. It should be noted that the description file of the second service herein is the second description file in the embodiment shown in FIG.

Steps 1301-1302 are mainly to send a service deployment request to the CSP server by the CSC device, and the CSP server obtains the service deployment package to be deployed according to the information of the service deployment package in the service deployment request. When the CSC device uploads the service deployment package, and how the CSP server obtains the service deployment package according to the information of the service deployment package, the present invention does not limit the service deployment package to be deployed.

Step 1303: After performing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identifier ID of the second service that has been deployed;

Step 1304: Determine that the description file of the second service includes restriction information, where the restriction information includes information that the second service restricts execution of a plan of the first instance of the first service, and/or the second service restriction Information of a method of performing a node of the first instance;

Step 1303 and step 1304 are the same as the embodiment described in FIG. 4, and the related content refers to the method of the embodiment described in FIG. 4, and details are not described herein again.

Step 1305: Record, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a record file of the first instance, and/or a node in the first instance. Corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the record file.

Specifically, the first instance ID may be obtained according to the restriction information; the record file of the first instance is obtained according to the first instance ID; and the second instance ID is recorded in the record file of the first instance Corresponding relationship of the plan ID of the first instance, and/or acquiring a node record file of the first instance according to the record file of the first instance, and recording the second instance ID in the node record file of the first instance Correspondence with the method ID of the node of the first instance.

The step 1305 is different from the step 104-105 of the embodiment described in FIG. 4 in that the corresponding relationship between the second instance and the plan of the first instance and/or the second instance and the The correspondence of the methods of the nodes of the first instance is recorded in the log file, not in the profile of the first service. In order to highlight the difference, the difference is described below with an example in the embodiment described in FIG. 4:

Assume that the service deployment package for the first service and the second service includes two plans: a deployment plan (BuildPlan) and a delete plan (TerminatePlan). Each node in the first service and the second service has four methods: start, configure, stop, and remove. In practice, the service deployment package can also include other plans, such as an update plan. The method of each node may also be other methods, such as restarting and updating, which is not specifically limited in this application.

At this point, assume that the first service (ServiceA) has been deployed, that is, running on the cloud platform. The service instance of the first service (ServiceA), that is, the first instance ID is ServiceA-1; the record file of the first instance is, for example, a record file A. Further, the CSP server also records the mapping relationship between the record file A and the first instance. It should be noted that, when the first service is deployed on different servers, there will be different service instances. In this embodiment, it is assumed that the deployed instance of the first service on the server is the first instance, for the first Other service instances of the service are implemented in the same way.

Assume that the second service is ServiceB, and the description file of the second service is description file B, wherein the file name of the description file B is ServiceB.ste.

When the second service needs to be deployed, the CSC device sends a service deployment request to the CSP server. That is, the CSP server performs the step 1301 in the method of the embodiment to receive the service deployment request, and the CSP server obtains the service deployment package of the second service according to the information of the service deployment package in the service deployment request. The deployment plan and description file B are included in the service deployment package of the second service. In other embodiments, the service deployment package may also include other plans, such as deleting the plan, restarting the plan, and the like. This example does not limit the specific acquisition method of the service deployment package.

After obtaining the service deployment package of the second service, the deployment plan may be executed according to the description file B of the second service.

Then, step 1303 is performed, and after the deployment is completed, the second instance ID of the deployed second service is obtained. The execution deployment plan is well known to those skilled in the art, so it will not be described here. The second instance ID is obtained, for example, the CSP server creates or allocates an instance ID to ServiceB-1 for ServiceB.

Next, in step 1304, it is determined that the restriction information is included in the description file of the second service. Step 1304 is the same as the embodiment described in FIG. 4, and details are not described herein again.

Next, step 1305 is performed, that is, the record file of the first instance is obtained according to the first instance ID. For example, the CSP server queries the record file corresponding to the first instance ID according to the mapping relationship between the recorded record file and the instance ID. In the present embodiment, for example, the log file A is obtained. According to Determining the correspondence between the second instance and the plan of the first instance in the record file A, and/or acquiring the node record file of the first instance according to the record file A, in the first Corresponding relationship between the method of the second instance and the node of the first instance is recorded in the node record file of the instance.

Specifically, a service instance includes multiple nodes. At runtime, each instance corresponds to one record file, and each node also corresponds to one record file. The restriction relationship to the plan needs to be written to the record file of the instance, and the restriction relationship of the node method needs to be written to the record file of the node. The following information can be added to the LimitedPlans field of the log file A according to the code (7):

According to the record file A, the record file A_1 of the node AppA is obtained, and the following restriction information is added to the LimitedOperations field of the record file A_1 according to the code (8):

According to the record file A, the record file A_2 of the node AppADb is obtained, and the following restriction information is added to the LimitedOperations field of the record file A_2 according to the code (9):

According to the record file A, the node Apache record file A_3 is obtained, and the following restriction information is added to the LimitedOperations field of the record file A_3 according to the code (10):

According to the record file A, the record file A_4 of the node MySql is obtained, and the following restriction information is added in the LimitedOperations field of the record file A_4 according to the code (11):

In an actual application, in addition to the manner described in the foregoing embodiments, the method for describing the second service restriction execution of the first instance and/or the method for limiting the execution of the first instance may be described in the record file in other manners. This is not limited. In addition, the correspondence between the second instance and the method of the first instance and/or the method of the node of the first instance ID is specifically recorded, which is not limited in this application.

As can be seen from the above description, since the description file of the second service only contains the restriction information without writing all the contents in the first service deployment package, the resources for developing the service deployment package description file and the transmission resources are saved. . Moreover, as long as the corresponding relationship of the plan of the second instance and the first instance is written in the record file of the first instance of the first service, and/or the correspondence between the methods of the node of the second instance and the first instance is written It is possible to enter the node record file of the first instance of the first service without re-deploying the content in the deployment package of the first service, thereby saving the deployment resources of the server. Further, by limiting the method of executing the plan and/or node of the first instance, it is possible to avoid The execution of the method and/or the method of the node causes the second service to fail.

After the second service is deployed by the service deployment method described in the embodiment of FIG. 13, the management of the first service and the second service may be involved, and the management process for the first service will be described first.

Please refer to FIG. 14 , which is a flowchart of a service management method in an embodiment of the present application, where the method includes the following content:

Step 1401: Receive an instance management request sent by the sending end, where the instance management request includes a first instance ID and a plan ID to be executed and/or a method ID of the node;

For example, for example, the CSC device wants to execute a plan or node method in the instance ServiceA-1 of ServiceA, such as a delete plan (TerminatePlan). Then, the instance management request is sent to the CSP server through the client, and the instance management request includes the ID of the ServiceA instance, ServiceA-1, and the plan ID, TerminatePlan, to be executed.

Step 1402: Acquire a record file of the first instance according to the first instance ID, and/or obtain a node record file of the first instance according to the record file of the first instance;

The record of the first instance records the corresponding relationship between the second instance ID of the second service and the plan of the first instance ID, and the node record file of the first instance records the second instance ID and the first instance respectively. The correspondence between the method IDs of the nodes.

For example, the corresponding relationship is specifically written in the manner described in the steps 1301 to 1305 in the embodiment of FIG. 13 , and may be written in other manners, which is not limited in this application.

The process of acquiring the record file of the first instance of the first service according to the first instance ID, and acquiring the record file of the node of the first instance according to the record file of the first instance, refer to the related description of the embodiment described in FIG. Let me repeat.

Step 1401 - Step 1402 is used to acquire a record file of the first instance and/or a node record file of the first instance. When the method of the node needs to be performed, optionally, step 1401 - step 1402 may also be: receiving an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method of the node to be executed. ID; acquiring a node record file to be executed according to the node ID to be executed.

Step 1403: Determine that execution of the plan to be executed and/or the method of the node is restricted by the second instance of the second service;

Specifically, by detecting the record file of the first instance, determining whether the plan ID to be executed is located in the correspondence between the second instance ID and the plan ID of the first instance, and/or by detecting The node record file of the first instance determines whether the method ID of the node to be executed is located in the correspondence between the second instance ID and the method ID of the node of the first instance. If the record of the first instance records the corresponding relationship between the second instance of the second service and the plan of the first instance, determining that execution of the plan to be executed is restricted by the second instance; Or if the correspondence between the method of the second instance and the node of the first instance is recorded in the node record file of the first instance, the execution of the method for determining the node is restricted by the second instance.

For example, check the record file A to determine the limit of the ServiceB instance ServiceB-1 to the TerminatePlan of the instance ServiceA-1. Specifically, it is to check the LimitedPlans field of the log file A. If "TerminatePlan" appears in "LimitedPlans", the deletion plan is restricted to be executed, otherwise it is not. When checking the method of a node, you first need to obtain the node record file according to the record file A, and then check the "LimitedOperations" field of each node record file separately. If the method of the node to be executed appears in "LimitedOperations", the method is restricted. It is.

Step 1404: Send a message rejecting the method of executing the plan and/or the node to be executed to the sender.

For example, by the determining process of step 1403, it is determined that the plan and/or method to be executed is restricted by the second service, then a reject message is sent to the sender.

Regarding the second instance ID, specifically, the value of the attribute "appliesFromService" in the code (7 to 11), so reading the value of the attribute, the second instance ID of the second service, that is, ServiceB-1, can be obtained.

Optionally, the plan to be executed is at least one of a delete plan, an update plan, a restart plan, and a stop plan; the method to be executed is at least one of a delete method, an update method, a restart method, and a stop method.

As can be seen from the above description, when managing the first service, it is necessary to first determine the plan to be executed. The execution of the method and/or method is not limited by other services, and the request is rejected if the execution of the plan and/or the method of the node is restricted by other services. In this way, when the first service is managed, it is guaranteed that the normal operation of the service that restricts the execution of the method of the plan and/or the node is not affected.

Next, the management process of the second service is described. Referring to FIG. 15, a flowchart of the method for managing the second service in this embodiment is shown. The method includes the following:

Step 1501: Receive an instance deletion request, where the deletion request includes a second instance ID and a deletion plan ID to be executed.

Step 1502: Obtain a service deployment package of the second service according to the second instance ID, where the service deployment package includes a deletion plan corresponding to the deletion plan ID to be executed and a description file of the second service.

For example, the service deployment package of the second service is obtained by using the instance ID ServiceB-1, and the service deployment package includes a description file B and a TerminatePlan.

Step 1503: Determine that the description file of the second service includes restriction information, where the restriction information includes information that the second service restricts execution of a plan of the first instance of the first service, and/or the second service restriction execution Information about the method of the node of the first instance.

Specifically, if there is a limitation in the description file B on the plan of the first instance and/or the method of the node, the description file B includes the code (3) and the code (6) as described above, so the description can be checked by Whether or not such a code segment is included in the file B is to determine whether the second service has restrictions on the execution of the plan of the other service instance and/or the method of the node. And, the restricted service instance ID can be known from the value of the attribute "appliesToService" in the code segment.

In this embodiment, the first instance of the first service generally refers to all instances that are subject to the second service restriction.

When the result is not, then the deletion plan can be executed directly.

When the result is sometimes, then step 1504 is performed:

Step 1504: Acquire the first instance ID according to the restriction information.

Step 1505: Obtain a record file of the first instance according to the first instance ID.

Step 1506: Delete the correspondence between the second instance ID in the record file of the first instance and the plan ID of the first instance, and/or obtain the first instance according to the record file of the first instance. a node record file, deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of a node of the first instance;

Step 1507: Perform the deletion plan according to the description file of the second service.

Specifically, the correspondence between the record file of the first instance and/or the record file of each node is deleted, thereby releasing the restriction of the execution of the plan of the first instance and/or the method of the node by the second instance, so that the plan And/or methods can be performed.

The first instance ID is obtained by using the description file of the second service. The instance ID of the restricted service can be obtained by the value of the attribute “appliesToService” in the code segment in the description file as described above. For details, please refer to the related description of the embodiment shown in FIG. 4, and details are not described herein again. The step of obtaining the record file of the first instance of the first service by using the first instance ID and acquiring the record file of each node according to the record file of the first instance may also be implemented in the manner described above, and details are not described herein again.

Delete the correspondence recorded in the record file. Specifically, it is to find whether the LimitedOlanations element of the Recorded File A of the first instance and/or the LimitedOperations element of the node record file (such as the record file A_1) contains the attribute "appliesFromService" value is ServiceB- Sub-elements of 1 and remove these sub-elements.

After the content related to the deletion of the correspondence is performed in step 1506, the respective methods on the nodes in the deletion plan can be executed, which are well-known to those skilled in the art, and therefore will not be described herein.

It can be seen from the above description that even if the second service has restrictions on the planning of the instance of the first service and/or the execution of the method of the node, the second service can be separately managed to ensure the independence of the second service management and improve The flexibility of service management.

To further improve the flexibility of service deployment, FIG. 16 is a flowchart of a method for service deployment according to another embodiment of the present invention. The difference between the embodiment and the embodiment shown in FIG. 4 and FIG. 13 is that, in this embodiment, the restriction information of the second service to the first instance of the first service is not recorded in the description file of the second service. When the second service needs to be deployed and the first instance of the first service is required to be referenced, the CSC device carries the restriction information in the service deployment request sent to the CSP server. The CSP server records the association information in the record file of the second instance, indicating that the second instance has a relationship with the first instance. And according to the restriction information, recording a correspondence between the plan of the second instance and the first instance in a record file of the first instance and/or recording the record in a node record file of the first instance Correspondence between the second instance and the method of the node of the first instance. When the CSP server manages the second instance, the record file of the first instance and/or the node record file of the first instance are checked according to the association information. Since the restriction relationship is not recorded in the description file of the first service, when the second service is subsequently deployed, there may be other restriction relationships, such as a plan for restricting execution of the third instance of the third service to the first service. There is no limit to the plan for the first instance. As shown in FIG. 16, the method provided in this embodiment includes the following steps:

Step 1601: Receive a service deployment request, where the service deployment request includes information and restriction information of a service deployment package of the second service, where the restriction information includes information that the second service restricts execution of the plan of the first instance, and / or the second service restricts information of a method of executing a node of the first instance;

Step 1602: Obtain a service deployment package of the second service according to the information about the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service.

Step 1603: After executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identifier ID of the second service that has been deployed and a record file of the second instance;

Step 1604: Record association information in the record file of the second instance according to the restriction information, where the association information includes a first instance ID;

Step 1605: Record, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a record file of the first instance, and/or a node in the first instance. Corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the record file.

For the same steps or methods as the embodiment shown in FIG. 13 , please refer to the related content of the embodiment of FIG. 13 , and details are not described herein again. An alternative implementation is described below in accordance with the method of the present embodiment.

Optionally, a limited policy template is included in a service template of the description file of the second service. The restriction policy template combines the input variables to generate corresponding restriction policy information. Specifically, in order to support the definition and acquisition of input variables, the present embodiment uses a YAML language to define a description file. Wherein, the description file B of the second service includes The following code (code 12):

The Limited_Policy_templates field defines a template for the restriction policy, and the rule describes the specific rules of the restriction policy, including the restriction plan (limit.plans) and the limit method (limit.operations). The restriction plan function needs to specify the instance ID of the request and is The restricted plan ID, limit method (limit.operations) function needs to specify the node ID and the restricted method ID. The get_input description acquires the information by input, and of course, some or all of the information may be directly specified in the description file. If all the information is specified in the description file, the embodiment will be the same as the embodiment described in FIG. The inputs field defines the information that needs to be obtained by input. In this embodiment, the information is included in the service deployment request, assuming that the requested service instance is ServiceA-1, the restricted plan is the termination plan (TerminatePlan), and the restricted node ID is AppA, AppADb, Apache and MySql, the restricted node method is stop, then the following restriction information can be included in the service deployment request:

Code (13)

Reference_instance_id_01: "ServiceA-1"

Limited_plans_of_id_01: "TermiatePlan"

Node_01_of_id_01: "AppA"

Limited_operations_of_node_01_of_id_01: "stop", "remove"

Node_02_of_id_01: "AppADb"

Limited_operations_of_node_02_of_id_01: "stop", "remove"

Node_03_of_id_01: "Apache"

Limited_operations_of_node_03_of_id_01: "stop", "remove"

Node_04_of_id_01: "MySql"

Limited_operations_of_node_04_of_id_01: "stop", "remove"

Next, it is necessary to add association information in the record file B of the second instance, the association information including at least the first instance ID:

Code (14)

<AppliesToServices>#Requested Service Instance

<ServiceInstance id=”ServiceA-1”>#The requested service instance ID is ServiceA-1

<\AppliesToServices>#End the requested service instance field

The record file B of the second example may also include information of the plan of the restricted first instance and the method of the node, and the present embodiment does not limit the content other than the first instance ID.

According to the restriction information in the service deployment request, the CSP server can obtain the information that the ServiceB restricts the execution of the plan (delete plan) of the first instance ServiceA-1 of the first service and the methods (Stop and Remove) of all the nodes, and can obtain the information. The first instance ID, in this embodiment, the first instance ID is ServiceA-1.

According to the first instance ID, the record file of the first instance is obtained. Specifically, for example, the CSP server queries the record file corresponding to the first instance according to the mapping relationship between the recorded record file and the instance ID. In the present embodiment, for example, the log file A is obtained.

In step 1605, the CSP server adds the following information to the LimitedPlans field of the record file A:

In an actual application, in addition to the manner described in the foregoing embodiments, the second service restriction execution execution of the plan of the first instance and/or the node of the first instance may be described in other manners in the deployment request and description file of the second service. The method is not limited in this application. In addition, the correspondence between the second instance and the method of the first instance and/or the method of the node of the first instance ID is specifically recorded, which is not limited in this application.

As can be seen from the above description, the embodiment does not include the restriction information of the second service on the first instance of the first service in the description file of the second service, but sends it to the CSP server along with the service deployment request. Therefore, with respect to the service deployment method described in the embodiment described in FIG. 13, the present embodiment will have greater flexibility in deploying services. For example, the instance A of the deployed second service may be implemented, the deletion plan of the instance B of the first service is restricted; the instance C of the deployed second service only limits the deletion plan of the instance D of the first service, without limiting the first The deletion plan for instance B of the service.

After the second service is deployed by the service deployment method described in FIG. 16, management of the first service and the second service may be involved. The management process of the first service is the same as the method described in the embodiment of FIG. 14, and details are not described herein again. For the management process of the second service, please refer to FIG. 17, which is a flowchart of the method for managing the second service in this embodiment. The method includes the following:

Step 1701: Receive an instance deletion request, where the instance deletion request includes a second instance identifier ID and a deletion plan ID to be executed;

Step 1702: Obtain a record file of the corresponding second instance and the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed.

Step 1703: Determine that the record file of the second instance includes association information, where the association information includes a first instance ID.

Step 1704: Acquire a record file of the first instance according to the first instance ID.

Step 1705: Delete the correspondence between the second instance ID and the plan ID of the first instance in the record file of the first instance, and/or obtain the first according to the record file of the first instance. a node record file of the instance, deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of a node of the first instance;

Step 1706: Perform the deletion plan.

For the same steps or methods as the embodiment of FIG. 15 , refer to the related content of the embodiment of FIG. 15 , and details are not described herein again.

Based on the same inventive concept as the embodiment in FIG. 13 , the embodiment of the present application further provides a service deployment apparatus. Referring to FIG. 18 , the service deployment apparatus includes: a receiving unit 1801, configured to receive a service deployment request, where The service deployment request includes the information of the service deployment package of the second service; the processing unit 1802 is configured to acquire the service deployment package of the second service according to the information of the service deployment package of the second service, where the service deployment The package includes a deployment plan of the second service and a description file of the second service; after executing the deployment plan of the second service according to the description file of the second service, acquiring the second of the second service that has been deployed An instance identifier ID; determining that the description file of the second service includes restriction information, the restriction information including information that the second service restricts execution of a plan of the first instance of the first service, and/or the second service Restricting information of a method of executing the node of the first instance; recording the second instance ID in a log file of the first instance according to the restriction information Program ID corresponding relation to said first example, and / or recorded in a log file of the node in the first instance to the second instance node ID of the first example of the method ID.

The processing unit 1802 is configured to record, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a log file of the first instance, and/or The corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, specifically: acquiring the first instance ID according to the restriction information; An instance ID, obtaining a record file of the first instance; recording, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or according to the first instance Recording file, obtaining a node record file of the first instance, and recording, in the node record file of the first instance, a correspondence between the second instance ID and a method ID of the node of the first instance system.

Optionally, the receiving unit 1801 is further configured to: record, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or in the first instance After the correspondence between the second instance ID and the method ID of the node of the first instance is recorded in the node record file, the receiving instance delete request is received, and the instance delete request includes the second instance ID and is to be executed. Delete plan ID;

The processing unit 1802 is further configured to acquire the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed; and determining the second service The description file includes the restriction information; the first instance ID is obtained according to the restriction information; the record file of the first instance is acquired according to the first instance ID; and the record file of the first instance is deleted. Corresponding relationship between the second instance ID and the plan ID of the first instance, and/or acquiring the node record file of the first instance according to the record file of the first instance, deleting the first instance Corresponding relationship between the second instance ID recorded in the node record file and the method ID of the node of the first instance; the deletion plan is executed according to the description file of the second service.

Optionally, the device further includes a sending unit 1803,

The receiving unit 1801 is further configured to: record, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or a node in the first instance After the record file records the correspondence between the second instance ID and the method ID of the node of the first instance, receiving an instance management request sent by the sending end, where the instance management request includes the first instance identifier ID and Plan ID of execution;

The processing unit 1802 is further configured to: acquire, according to the first instance ID, a record file of the first instance; according to the second instance ID of the second service recorded in the record file of the first instance, Corresponding relationship of the plan ID of the first instance, determining that execution of the plan corresponding to the plan ID to be executed is restricted by the second instance,

The sending unit 1803 is configured to: send a message rejecting execution of the plan to be executed to the sending end; and/or

The receiving unit 1801 is further configured to: receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of a node to be executed;

The processing unit 1802 is further configured to: acquire the record file of the first instance according to the first instance ID; acquire the node record file of the first instance according to the record file of the first instance; Corresponding relationship between the second instance ID recorded in the node record file and the method ID of the node of the first instance, determining that the execution of the method corresponding to the ID of the method to be executed is performed by the second instance limit;

The sending unit 1803 is configured to: send a message rejecting the method of executing the node to be executed to the sending end; and/or

The receiving unit 1801 is further configured to: receive an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed;

The processing unit 1802 is further configured to: acquire, according to the node ID to be executed, a node record file to be executed; according to the second instance ID recorded in the node record file to be executed, and the first instance Corresponding relationship of the method ID of the node, determining that the method corresponding to the method ID of the node to be executed is restricted by the second instance;

The sending unit 1803 is configured to: send a message rejecting a method of executing the node to be executed to the sending end.

The various changes and specific examples in the service deployment method in the foregoing embodiment of the present invention are also applicable to the service deployment device of the embodiment. The foregoing description of the service deployment method can be clearly known to those skilled in the art. In the example, the implementation method of the service deployment device is not detailed here for the sake of brevity of the description.

Based on the same inventive concept as the embodiment in FIG. 16 , the embodiment of the present application further provides a service deployment apparatus. Referring to FIG. 19 , the service deployment apparatus includes: a receiving unit 1901, configured to receive a service deployment request, where The service deployment request includes information and restriction information of the service deployment package of the second service; the restriction information includes information that the second service restricts execution of the plan of the first instance, and/or the second service restriction execution The information about the method of the node of the first instance; the processing unit 1902, configured to acquire the service deployment package of the second service according to the information of the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service; after executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identification ID of the second service that has been deployed And a record file of the second instance; according to the restriction information, the association information is recorded in the record file of the second instance, the association information including the first instance I D: recording, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a record file of the first instance, and/or a node record in the first instance Corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the file.

The processing unit 1902 is configured to record, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a log file of the first instance, and/or The corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, specifically: acquiring the first instance ID according to the restriction information; An instance ID, obtaining a record file of the first instance; recording, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or according to the first instance a record file, the node record file of the first instance is obtained, and the corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance.

Optionally, the receiving unit 1901 is further configured to: record, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or in the first instance After the mapping between the second instance ID and the method ID of the node of the first instance is recorded in the node record file, an instance delete request is received, where the instance delete request includes the second instance ID and the Delete the plan ID;

The processing unit 1902 is further configured to acquire the record file of the second instance according to the second instance ID, determine that the record file of the second instance includes the association information, and acquire the location according to the association information. Deleting a first instance ID; acquiring a record file of the first instance according to the first instance ID; deleting the second instance ID of the record file of the first instance and a plan ID of the first instance Corresponding relationship, and/or acquiring the node record file of the first instance according to the record file of the first instance, deleting the second instance ID and the number recorded in the node record file of the first instance Corresponding relationship of the method ID of the node of the instance; executing the deletion plan corresponding to the deletion plan ID to be executed.

Optionally, the device further includes a sending unit 1903,

The receiving unit 1901 is further configured to: record, in the recording file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or in the recording file After the corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, the instance management request sent by the sending end is received, where the instance management request includes the first The instance ID and the plan ID to be executed;

The processing unit 1902 is further configured to: acquire the record file of the first instance according to the first instance ID; and use the second instance ID and the first record recorded in the record file of the first instance Corresponding relationship of the plan ID of the instance, determining that execution of the plan corresponding to the plan ID to be executed is restricted by the second instance;

The sending unit 1903 is configured to: send a message rejecting execution of the plan to be executed to the sending end; and/or

The receiving unit 1901 is further configured to: receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of a node to be executed;

The processing unit 1902 is further configured to: acquire a record file of the first instance according to the first instance ID; acquire a node record file of the first instance according to the record file of the first instance; and record according to the node Corresponding relationship between the second instance ID recorded in the file and the method ID of the node of the first instance, determining that the execution of the method corresponding to the method ID of the node to be executed is restricted by the second instance;

The sending unit 1903 is configured to: send a message rejecting a method of executing the node to be executed to the sending end; and/or

The receiving unit 1901 is further configured to: receive an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed;

The processing unit 1902 is further configured to: acquire, according to the node ID to be executed, a node record file to be executed; according to the second instance ID recorded in the node record file to be executed, and the first instance Corresponding relationship of the method ID of the node, determining that the method corresponding to the method ID of the node to be executed is restricted by the second instance;

The sending unit 1903 is configured to: send a message rejecting a method of executing the node to be executed to the sending end.

The various changes and specific examples in the service deployment method in the foregoing embodiment of the present invention are also applicable to the service deployment device in this embodiment. The foregoing description of the service deployment method can be clearly known to those skilled in the art. In the example, the implementation method of the service deployment device is not detailed here for the sake of brevity of the description.

Based on the same inventive concept as that of the embodiment shown in FIG. 13, the embodiment of the present application further includes a server. Referring to FIG. 20, it is a system block diagram of a server in the embodiment of the present application. As shown in FIG. 20, the server includes: a receiver 2001, configured to receive a service deployment request, the service deployment request includes information of a service deployment package of the second service, and a processor 2002, configured to be used according to the second service Information about the service deployment package, where the service deployment package of the second service is obtained, where the service deployment package includes a deployment plan of the second service and a description file of the second service; after executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identifier of the second service that has been deployed Determining, in the description file of the second service, restriction information, the restriction information including information that the second service restricts execution of a plan of the first instance of the first service, and/or the second service restriction execution The information about the method of the node of the first instance; the correspondence between the second instance ID and the plan ID of the first instance is recorded in the record file of the first instance according to the restriction information, and/ Or recording a correspondence between the second instance ID and a method ID of a node of the first instance in a node record file of the first instance.

Optionally, the receiver 2001 is further configured to receive an instance deletion request, where the instance deletion request includes the second instance ID and a deletion plan ID to be executed. The processor 2002 is further configured to acquire the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed; and determining a description file of the second service. Include the restriction information; acquire the first instance ID according to the restriction information; acquire a record file of the first instance according to the first instance ID; delete the record file of the first instance Corresponding relationship between the second instance ID and the plan ID of the first instance, and/or acquiring the node record file of the first instance according to the record file of the first instance, deleting the node record of the first instance Corresponding relationship between the second instance ID recorded in the file and the method ID of the node of the first instance; performing the deletion plan according to the description file of the second service.

Optionally, the receiver 2001 is further configured to receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a plan ID to be executed. The processor 2002 is further configured to acquire, according to the first instance ID, a record file of the first instance; according to the second instance ID recorded in the record file of the first instance and the plan of the first instance The correspondence of the IDs determines that the execution of the plan corresponding to the plan ID to be executed is limited by the second instance. Optionally, the server further includes a message sent by the sender 2003 to the sender to send a method of rejecting the node to be executed.

Optionally, the receiver 2001 is further configured to receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of the node to be executed. The processor 2002 is further configured to acquire the record file of the first instance according to the first instance ID, acquire a node record file of the first instance according to the record file of the first instance, and record the file according to the node record Corresponding relationship between the second instance ID and the method ID of the node of the first instance, determining that the execution is to be performed The execution of the method corresponding to the method ID of the node is limited by the second instance. Optionally, the server further includes a message sent by the sender 2003 to the sender to send a method of rejecting the node to be executed.

Optionally, the receiver 2001 is further configured to receive an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed. The processor 2002 is further configured to: acquire, according to the node ID to be executed, a node record file to be executed; according to the second instance ID recorded in the node record file to be executed, and a method of the node of the first instance For the correspondence of the IDs, the execution of the method corresponding to the method ID of the node to be executed is determined by the second instance. Optionally, the server further includes a message sent by the sender 2003 to the sender to send a method of rejecting the node to be executed.

Further, in FIG. 20, a bus architecture (represented by bus 2000), bus 2000 can include any number of interconnected buses and bridges, and bus 2000 will include one or more processors and memory 2004 represented by processor 2002. The various circuits of the memory are linked together. The bus 2000 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is well known in the art and, therefore, will not be further described herein. The bus interface 2005 provides an interface between the bus 2000 and the processor 2002, the receiver 2001, and the transmitter 2003. The receiver 2001 and the transmitter 2003 are used for data communication between the server and an external device.

The processor 2002 is responsible for managing the bus 2000 and the usual processing. The memory 2004 can be used to store data used by the processor 2002 when performing operations.

This server is for example a CSP server.

The various changes and specific examples in the foregoing service management method in the foregoing embodiment of FIG. 13 are also applicable to the server in this embodiment. The foregoing detailed description of the service management method can be clearly known to those skilled in the art. The implementation method of the server, so for the sake of brevity of the description, it will not be described in detail here.

Based on the same inventive concept as the embodiment in FIG. 16 , the embodiment of the present application further includes a server. Referring to FIG. 21 , it is a system block diagram of a server in the embodiment of the present application. As shown in FIG. 21, the server includes: a receiver 2101, configured to receive a service deployment request, where the service deployment request includes information and restriction information of a service deployment package of the second service; and the restriction information includes the second The service restricts execution of information of the plan of the first instance, and/or the second service limits information of a method of executing the node of the first instance. a processor 2102, configured to be used according to the service part of the second service And obtaining, by the package information, a service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service; and executing the file according to the description file of the second service After the deployment plan of the second service is performed, acquiring a second instance identifier ID of the second service that has been deployed and a log file of the second instance; and recording in the log file of the second instance according to the restriction information Correlation information, the association information includes a first instance ID, and according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance is recorded in a record file of the first instance, and And mapping the correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance.

Optionally, the receiver 2101 is further configured to receive an instance deletion request, where the instance deletion request includes the second instance ID and a deletion plan ID to be executed. The processor 2102 is further configured to acquire the record file of the second instance and the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed; Determining, by the record file of the second instance, the association information; acquiring the first instance ID according to the association information; acquiring the record file of the first instance according to the first instance ID; Corresponding relationship between the second instance ID recorded in the record file of the first instance and the plan ID of the first instance, and/or acquiring the node of the first instance according to the record file of the first instance Recording a file, deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of a node of the first instance; performing the deleting according to the description file of the second service plan.

Optionally, the receiver 2101 is further configured to receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a plan ID to be executed. The processor 2102 is further configured to acquire the record file of the first instance according to the first instance ID; the second instance ID recorded in the record file of the first instance and the plan ID of the first instance Corresponding relationship, determining that the execution of the plan corresponding to the plan ID to be executed is limited by the second instance. Optionally, the server further includes a message that the transmitter 2103 is configured to send a method of rejecting the node to be executed to the sending end.

Optionally, the receiver 2101 is further configured to receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of the node to be executed. The processor 2102 is further configured to acquire the record file of the first instance according to the first instance ID, acquire a node record file of the first instance according to the record file of the first instance, and record the file according to the node record Corresponding relationship between the second instance ID and the method ID of the node of the first instance, determining that the execution is to be performed The execution of the method corresponding to the method ID of the node is limited by the second instance. Optionally, the server further includes a message that the transmitter 2103 is configured to send a method of rejecting the node to be executed to the sending end.

Optionally, the receiver 2101 is further configured to receive an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed. The processor 2102 is further configured to: acquire, according to the node ID to be executed, a node record file to be executed; according to the second instance ID recorded in the node record file to be executed, and a method of the node of the first instance For the correspondence of the IDs, the execution of the method corresponding to the method ID of the node to be executed is determined by the second instance. Optionally, the server further includes a message that the transmitter 2103 is configured to send a method of rejecting the node to be executed to the sending end.

Further, in FIG. 21, a bus architecture (represented by bus 2100), bus 2100 can include any number of interconnected buses and bridges, and bus 2100 will include one or more processors and memory 2104 represented by processor 2102. The various circuits of the memory are linked together. The bus 2100 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art and, therefore, will not be further described herein. The bus interface 2105 provides an interface between the bus 2100 and the processor 2102, the receiver 2101, and the transmitter 2103. The receiver 2101 and the transmitter 2103 are used for data communication between the server and an external device.

The processor 2102 is responsible for managing the bus 2100 and the usual processing. The memory 2104 can be used to store data used by the processor 2002 when performing operations.

This server is for example a CSP server.

The various changes and specific examples in the service management method in the foregoing embodiment of the present invention are also applicable to the server in this embodiment. The foregoing detailed description of the service management method can be clearly known to those skilled in the art. The implementation method of the server, so for the sake of brevity of the description, it will not be described in detail here.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

The present application is made with reference to a method, a device (system), and a computer program according to an embodiment of the present application. The flow chart and/or block diagram of the product is described. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A service deployment method, comprising:

Receiving a service deployment package of the second service, where the service deployment package includes a deployment plan and a second description file;

After executing the deployment plan according to the second description file, acquiring a second instance identification ID of the second service that has been deployed;

Determining, in the second description file, information that the second service restricts execution of a plan of a first instance ID of the first service and/or a method of a node of the first instance ID;

Obtaining, according to the first instance ID, a first description file of the first service;

Recording, in the first description file, the second instance ID and the information of the method of executing the first instance ID of the first service and/or the method of the node of the first instance ID according to the second service restriction Correspondence relationship between the plan of the first instance ID and/or the method of the node of the first instance ID.
The method of claim 1, wherein the method of recording the second instance ID and the plan of the first instance ID and/or the node of the first instance ID in the first description file After the correspondence, the method further includes:

Receiving a deletion request for the second instance ID, where the deletion request includes the second instance ID and a deletion plan to be executed;

Obtaining the service deployment package according to the second instance ID, where the service deployment package further includes the deletion plan;

Determining, in the second description file, information that the second service restricts execution of a plan of the first instance ID and/or a method of a node of the first instance ID;

Inserting a mark before the first method of the first node of the deletion plan, the mark indicating that the second service is released from the plan of the first instance ID and/or the node of the first instance ID Restrictions on the execution of the method;

Perform the delete plan after inserting the tag.
The method of claim 2, wherein the deleting the deleted plan after the tag is performed comprises:

Obtaining the first instance ID from the second description file;

Obtaining the first description file according to the first instance ID;

Deleting a correspondence between the second instance ID recorded in the first description file and a method of the first instance ID and a method of a node of the first instance ID;

The deletion plan to be executed is executed from the first method.
The method of claim 1, wherein the method of recording the second instance ID and the plan of the first instance ID and/or the node of the first instance ID in the first description file After the correspondence, the method further includes:

Receiving, by the sending end, a management request for the first instance ID, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

Obtaining the first description file according to the first instance ID;

Determining the plan to be executed according to the correspondence between the second instance ID recorded in the first description file and the method of the first instance ID and/or the method of the node of the first instance ID / or the execution of the method of the node is limited by the second service;

A message is sent to the sender that refuses to execute the plan of the program to be executed and/or the method of the node.
A service management method, comprising:

Receiving, by the sending end, a management request for a first instance identifier ID of the first service, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

Acquiring the first description file of the first service according to the first instance ID;

Determining the to-be-executed according to a correspondence between a second instance ID of the second service recorded in the first description file and a method of the first instance ID and a method of the node of the first instance ID The execution of the method of the plan and/or the node is limited by the second service;

A message is sent to the sender that refuses to execute the plan of the program to be executed and/or the method of the node.
The method according to claim 5, wherein the plan to be executed is at least one of a deletion plan, a restart plan, and a stop plan; and the method of the node to be executed is a delete method, a restart method, and a stop method. At least one of them.
A service management method, comprising:

Receiving a deletion request for a second instance identification ID of the second service, where the deletion request includes the second instance ID and a deletion plan to be executed;

Obtaining, according to the second instance ID, a service deployment package of the second service, where the service deployment package includes the deletion plan and a second description file;

Determining, in the second description file, that the second service restricts execution of the first service Information of the plan of the example ID and/or the method of the node of the first instance ID;

Inserting a mark before the first method of the first node of the deletion plan, the mark indicating that the second service is released from the plan of the first instance ID and/or the node of the first instance ID Restrictions on the execution of the method;

Perform the delete plan after inserting the tag.
The method of claim 7, wherein the deleting the deleted plan after the tag is performed comprises:

Acquiring the first description file of the first service according to the first instance ID;

Deleting a correspondence between the second instance ID recorded in the first description file and a method of the first instance ID and/or a method of a node of the first instance ID;

The deletion plan to be executed is executed from the first method.
A service deployment device, comprising:

a receiving unit, configured to receive a service deployment package of the second service, where the service deployment package includes a deployment plan and a second description file;

a processing unit, configured to acquire a second instance identifier ID of the second service that has been deployed after performing the deployment plan according to the second description file, and determine that the second description file includes the second The service restricts execution of a plan of the first instance ID of the first service and/or a method of a method of the node of the first instance ID; acquiring, according to the first instance ID, a first description file of the first service; The second service restricts execution of a plan of a first instance ID of the first service and/or a method of a method of a node of the first instance ID, and records the second instance ID and the location in the first description file Corresponding relationship between the plan of the first instance ID and/or the method of the node of the first instance ID.
The apparatus according to claim 9, wherein the receiving unit is further configured to: record, in the first description file, the second instance ID and the first instance ID in the processing unit Receiving a deletion request for the second instance ID after the plan and/or the correspondence of the method of the node of the first instance ID, the deletion request including the second instance ID and a deletion plan to be executed ;

The processing unit is further configured to: acquire the service deployment package according to the second instance ID, where the service deployment package further includes the deletion plan; and determine that the second description file includes the second service restriction execution Information of a plan of the first instance ID and/or a method of a node of the first instance ID; inserting a mark before the first method of the first node of the delete plan, the mark indicating a release Restricting the execution of the plan of the first instance ID and/or the method of the node of the first instance ID by the second service; performing a delete plan after inserting the tag.
The apparatus according to claim 10, wherein the processing unit is configured to: obtain the first instance ID from the second description file; and acquire the first description according to the first instance ID a file; deleting a correspondence between the second instance ID recorded in the first description file and a method of the first instance ID and/or a method of a node of the first instance ID; from the first method Start execution of the deletion plan to be executed.
The device according to claim 9, wherein said device further comprises a transmitting unit,

The receiving unit is further configured to: in the processing unit, record, in the first description file, a node of the second instance ID and the first instance ID and/or a node of the first instance ID After receiving the corresponding relationship of the method, receiving a management request sent by the sending end for the first instance ID, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

The processing unit is further configured to: acquire the first description file according to the first instance ID;

Determining the plan to be executed according to the correspondence between the second instance ID recorded in the first description file and the method of the first instance ID and/or the method of the node of the first instance ID / or the execution of the method of the node is limited by the second service;

The sending unit is configured to: send a message rejecting the method of executing the plan and/or the node to be executed to the sending end.
A service management device, comprising:

a receiving unit, configured to receive a management request sent by the sending end for the first instance identifier ID of the first service, where the management request includes the first instance ID and a method of a plan and/or a node to be executed;

a processing unit, configured to acquire, according to the first instance ID, a first description file of the first service;

Determining the to-be-executed according to a correspondence between a second instance ID of the second service recorded in the first description file and a method of the first instance ID and a method of the node of the first instance ID The execution of the method of the plan and/or the node is limited by the second service;

And a sending unit, configured to send, to the sending end, a message rejecting a method of executing the plan and/or the node to be executed.
The apparatus according to claim 13, wherein the plan to be executed is at least one of a deletion plan, a restart plan, and a stop plan; and the method of the node to be executed is a delete side At least one of a method, a restart method, and a stop method.
A service management device, comprising:

a receiving unit, configured to receive a deletion request for a second instance identifier ID of the second service, where the deletion request includes the second instance ID and a deletion plan to be executed;

a processing unit, configured to acquire, according to the second instance ID, a service deployment package of the second service, where the service deployment package includes the deletion plan and a second description file; determining that the second description file includes the The second service restricts information of a method of executing a first instance ID of the first service and/or a method of a node of the first instance ID; inserting a flag before the first method of the first node of the deletion plan, The flag indicates a restriction to release the execution of the method of the first instance ID and/or the method of the node of the first instance ID by the second service; performing a deletion plan after inserting the tag.
The device according to claim 15, wherein the processing unit is configured to: acquire a first description file of the first service according to the first instance ID; and delete a record in the first description file Corresponding relationship between the second instance ID and the method of the first instance ID and/or the method of the node of the first instance ID; starting from the first method, executing the deletion plan to be executed.
A service deployment method, comprising:

Receiving a service deployment request, the service deployment request including information of a service deployment package of the second service;

Obtaining, according to the information about the service deployment package of the second service, the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service;

After executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identification ID of the second service that has been deployed;

Determining that the description file of the second service includes restriction information, the restriction information includes information that the second service restricts execution of a plan of a first instance of the first service, and/or the second service restriction performs the Information about the method of the node of the first instance;

Recording, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a record file of the first instance, and/or in a node record file of the first instance Corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded.
The method according to claim 17, wherein the mapping of the correspondence between the second instance ID and the plan ID of the first instance is recorded in the log file of the first instance according to the restriction information And/or recording the second instance ID and the node record file of the first instance Corresponding relationship between the method IDs of the nodes of the first instance is specifically:

Obtaining a first instance ID according to the restriction information;

Obtaining a record file of the first instance according to the first instance ID;

Recording, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or acquiring a node record of the first instance according to the record file of the first instance And a file, in the node record file of the first instance, records a correspondence between the second instance ID and a method ID of a node of the first instance.
The method according to claim 17, wherein a correspondence relationship between the second instance ID and a plan ID of the first instance is recorded in a log file of the first instance, and/or in the After the mapping between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of an instance, the method further includes:

Receiving an instance deletion request, where the instance deletion request includes the second instance ID and a deletion plan ID to be executed;

Obtaining the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed;

Determining, in the description file of the second service, the restriction information;

Obtaining the first instance ID according to the restriction information;

Acquiring the record file of the first instance according to the first instance ID;

Deleting a correspondence between the second instance ID and the plan ID of the first instance in the record file of the first instance, and/or acquiring a node of the first instance according to the record file of the first instance Logging a file, deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of a node of the first instance;

The deletion plan is executed according to the description file of the second service.
The method according to claim 17, wherein a correspondence relationship between the second instance ID and a plan ID of the first instance is recorded in a log file of the first instance, and/or in the After the mapping between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of an instance, the method further includes:

Receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and a plan ID to be executed;

Acquiring the record file of the first instance according to the first instance ID;

Determining, according to the correspondence between the second instance ID recorded in the record file of the first instance and the plan ID of the first instance, that execution of the plan corresponding to the plan ID to be executed is subjected to the second instance limits,

Sending a message rejecting execution of the plan to be executed to the sender; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of a node to be executed;

Acquiring the record file of the first instance according to the first instance ID;

Obtaining, according to the record file of the first instance, a node record file of the first instance;

Determining, according to the correspondence between the second instance ID recorded in the node record file and the method ID of the node of the first instance, performing the method corresponding to the method ID of the node to be executed by the second Limitation of the instance;

Sending a message rejecting the method of executing the node to be executed to the sender; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed;

Obtaining a node record file to be executed according to the node ID to be executed;

Determining, according to the correspondence between the second instance ID recorded in the node record file to be executed and the method ID of the node of the first instance, performing execution of a method corresponding to the method ID of the node to be executed The limitations of the second example;

Sending a message rejecting the method of executing the node to be executed to the sender.
The method according to claim 20, wherein the plan to be executed is at least one of an update plan, a delete plan, a restart plan, and a stop plan; and the method of the node to be executed is an update method, a delete method At least one of a restart method and a stop method.
A service deployment device, comprising:

a receiving unit, configured to receive a service deployment request, where the service deployment request includes information about a service deployment package of the second service;

a processing unit, configured to acquire a service deployment package of the second service according to the information about the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service After executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identification ID of the second service that has been deployed; determining that the description file of the second service includes Restricting information, the restriction information including the second service restriction executing the first service Information of the plan of the first instance, and/or information of the method of the second service limiting execution of the node of the first instance; recording the record in the log file of the first instance according to the restriction information a correspondence between the second instance ID and the plan ID of the first instance, and/or a method of recording the second instance ID and the node ID of the first instance in the node record file of the first instance Correspondence relationship.
The device according to claim 22, wherein the processing unit is configured to record the second instance ID and the first instance in a record file of the first instance according to the restriction information Corresponding relationship between the plan ID, and/or the correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance, specifically:

Obtaining a first instance ID according to the restriction information;

Obtaining a record file of the first instance according to the first instance ID;

Recording, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or acquiring a node record of the first instance according to the record file of the first instance And a file, in the node record file of the first instance, records a correspondence between the second instance ID and a method ID of a node of the first instance.
The apparatus according to claim 22, wherein the receiving unit is further configured to: record a correspondence between the second instance ID and a plan ID of the first instance in a log file of the first instance And/or receiving a receiving instance deletion request in the instance deletion request after recording the correspondence between the second instance ID and the method of the node ID of the first instance in the node record file of the first instance Include the second instance ID and a deletion plan ID to be executed;

The processing unit is further configured to acquire the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed; and determining a description of the second service The file includes the restriction information; the first instance ID is obtained according to the restriction information; the record file of the first instance is obtained according to the first instance ID; and the record file of the first instance is deleted. Obtaining a correspondence between the second instance ID and the plan ID of the first instance, and/or acquiring a node record file of the first instance according to the record file of the first instance, deleting the first instance a correspondence between the second instance ID recorded in the node record file and a method ID of the node of the first instance; and the deletion plan is executed according to the description file of the second service.
The device according to claim 22, wherein said device further comprises a transmitting unit,

The receiving unit is further configured to: record the second instance in a record file of the first instance a correspondence between the ID and the plan ID of the first instance, and/or after the correspondence between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance Receiving an instance management request sent by the sending end, where the instance management request includes the first instance identifier ID and a plan ID to be executed;

The processing unit is further configured to: acquire, according to the first instance ID, a record file of the first instance; according to the second instance ID of the second service recorded in the record file of the first instance, Corresponding relationship of the plan ID of an instance, determining that execution of the plan corresponding to the plan ID to be executed is restricted by the second instance,

The sending unit is configured to: send a message rejecting execution of the plan to be executed to the sending end; and/or

The receiving unit is further configured to: receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of the node to be executed;

The processing unit is further configured to: acquire a record file of the first instance according to the first instance ID; acquire a node record file of the first instance according to the record file of the first instance; and record a file according to the node Corresponding relationship between the second instance ID recorded in the method ID of the node of the first instance, determining that the execution of the method corresponding to the method ID of the node to be executed is restricted by the second instance;

The sending unit is configured to: send a message rejecting a method of executing the node to be executed to the sending end; and/or

The receiving unit is further configured to: receive an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed;

The processing unit is further configured to: acquire, according to the node ID to be executed, a node record file to be executed; according to the second instance ID recorded in the node record file to be executed, and the node of the first instance Corresponding relationship of the method ID, determining that the execution of the method corresponding to the method ID of the node to be executed is limited by the second instance;

The sending unit is configured to: send a message rejecting a method of executing the node to be executed to the sending end.
The device according to claim 25, wherein the plan corresponding to the plan ID to be executed is at least one of an update plan, a delete plan, a restart plan, and a stop plan; and the method ID of the node to be executed corresponds to The methods are update method, delete method, restart method, and stop method. At least one of them.
A service deployment method, comprising:

Receiving a service deployment request, the service deployment request including information and restriction information of a service deployment package of the second service; the restriction information including information that the second service restricts execution of the plan of the first instance, and/or Determining, by the second service, information of a method of executing a node of the first instance;

Obtaining, according to the information about the service deployment package of the second service, the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service;

After executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identifier ID of the second service that has been deployed and a record file of the second instance;

Correlating the association information in the record file of the second instance according to the restriction information, where the association information includes a first instance ID;

Recording, according to the restriction information, a correspondence between the second instance ID and a plan ID of the first instance in a record file of the first instance, and/or in a node record file of the first instance Corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded.
The method according to claim 27, wherein the mapping of the correspondence between the second instance ID and the plan ID of the first instance is recorded in the log file of the first instance according to the restriction information Corresponding relationship between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, specifically:

Obtaining a first instance ID according to the restriction information;

Obtaining a record file of the first instance according to the first instance ID;

Recording, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or acquiring a node record of the first instance according to the record file of the first instance And a file, in the node record file of the first instance, records a correspondence between the second instance ID and a method ID of a node of the first instance.
The method according to claim 27, wherein a correspondence relationship between the second instance ID and a plan ID of the first instance is recorded in a log file of the first instance, and/or in the After the mapping between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of an instance, the method further includes:

Receiving an instance deletion request, where the instance deletion request includes the second instance ID and a deletion plan ID to be executed;

Acquiring the record file of the second instance and the service deployment package according to the second instance ID, where the service deployment package further includes a deletion plan corresponding to the deletion plan ID to be executed;

Determining that the related information is included in a record file of the second instance;

Obtaining the first instance ID according to the association information;

Acquiring the record file of the first instance according to the first instance ID;

Deleting a correspondence between the second instance ID recorded in the record file of the first instance and a plan ID of the first instance, and/or acquiring the first instance according to the record file of the first instance a node record file, deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of a node of the first instance;

The deletion plan is executed according to the description file of the second service.
The method according to claim 27, wherein a correspondence relationship between the second instance ID and a plan ID of the first instance is recorded in a log file of the first instance, and/or in the After the mapping between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of an instance, the method further includes:

Receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and a plan ID to be executed;

Acquiring the record file of the first instance according to the first instance ID;

Determining, according to the correspondence between the second instance ID recorded in the record file of the first instance and the plan ID of the first instance, that execution of the plan corresponding to the plan ID to be executed is subjected to the second instance limits;

Sending a message rejecting execution of the plan to be executed to the sender; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of a node to be executed;

Acquiring the record file of the first instance according to the first instance ID;

Obtaining, according to the record file of the first instance, a node record file of the first instance;

Determining, according to the correspondence between the second instance ID recorded in the node record file and the method ID of the node of the first instance, performing the method corresponding to the method ID of the node to be executed by the second Limitation of the instance;

Sending a message rejecting the method of executing the node to be executed to the sender; and/or

Receiving an instance management request sent by the sending end, where the instance management request includes a node to be executed ID and method ID of the node to be executed;

Obtaining a node record file to be executed according to the node ID to be executed;

Determining, according to the correspondence between the second instance ID recorded in the node record file to be executed and the method ID of the node of the first instance, performing execution of a method corresponding to the method ID of the node to be executed The limitations of the second example;

Sending a message rejecting the method of executing the node to be executed to the sender.
The method according to claim 30, wherein the plan corresponding to the plan ID to be executed is at least one of an update plan, a delete plan, a restart plan, and a stop plan; and the method ID of the node to be executed corresponds to The method is at least one of an update method, a delete method, a restart method, and a stop method.
A service deployment device, comprising:

a receiving unit, configured to receive a service deployment request, where the service deployment request includes information and restriction information of a service deployment package of the second service; and the restriction information includes information that the second service restricts execution of the plan of the first instance And/or the second service limits information of a method of performing a node of the first instance;

a processing unit, configured to acquire a service deployment package of the second service according to the information about the service deployment package of the second service, where the service deployment package includes a deployment plan of the second service and a description file of the second service After executing the deployment plan of the second service according to the description file of the second service, acquiring a second instance identification ID of the second service that has been deployed and a record file of the second instance; according to the limitation Information, in the record file of the second instance, the association information is recorded, the association information includes a first instance ID; and the second instance ID is recorded in the record file of the first instance according to the restriction information Corresponding relationship between the plan ID of the first instance, and/or a correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance.
The method according to claim 32, wherein the processing unit is configured to record the second instance ID and the first instance in a log file of the first instance according to the restriction information Corresponding relationship between the plan ID, and/or the correspondence between the second instance ID and the method ID of the node of the first instance in the node record file of the first instance, specifically:

Obtaining a first instance ID according to the restriction information;

Obtaining a record file of the first instance according to the first instance ID;

Recording, in the record file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or acquiring a node record of the first instance according to the record file of the first instance And a file, in the node record file of the first instance, records a correspondence between the second instance ID and a method ID of a node of the first instance.
The apparatus according to claim 32, wherein the receiving unit is further configured to: record, in the recording file of the first instance, the second instance ID and the first instance in the processing unit Receiving an instance deletion request after the correspondence between the plan ID and/or the correspondence between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of the first instance, The instance deletion request includes the second instance ID and a deletion plan ID to be executed;

The processing unit is further configured to: obtain the record file of the second instance and the service deployment package according to the second instance ID, where the service deployment package further includes deleting corresponding to the deletion plan ID to be executed. plan;

Determining, by the record file of the second instance, the association information; acquiring the first instance ID according to the association information; acquiring the record file of the first instance according to the first instance ID; Obtaining a correspondence between the second instance ID and the plan ID of the first instance in the record file of the first instance, and/or acquiring the node record file of the first instance according to the record file of the first instance And deleting a correspondence between the second instance ID recorded in the node record file of the first instance and a method ID of the node of the first instance; and executing the deletion plan according to the description file of the second service.
The device according to claim 32, wherein said device further comprises a transmitting unit,

The receiving unit is further configured to: record, in the recording file of the first instance, a correspondence between the second instance ID and a plan ID of the first instance, and/or in the first After the mapping between the second instance ID and the method ID of the node of the first instance is recorded in the node record file of an instance, receiving an instance management request sent by the sending end, where the instance management request includes the first instance ID and plan ID to be executed;

The processing unit is further configured to: acquire the record file of the first instance according to the first instance ID;

Determining, according to the correspondence between the second instance ID recorded in the record file of the first instance and the plan ID of the first instance, that execution of the plan corresponding to the plan ID to be executed is subjected to the second instance limits;

The sending unit is configured to: send a message rejecting execution of the plan to be executed to the sending end; and/or

The receiving unit is further configured to: receive an instance management request sent by the sending end, where the instance management request includes the first instance ID and a method ID of the node to be executed;

The processing unit is further configured to: acquire a record file of the first instance according to the first instance ID; acquire a node record file of the first instance according to the record file of the first instance; and record a file according to the node Corresponding relationship between the second instance ID recorded in the method ID of the node of the first instance, determining that the execution of the method corresponding to the method ID of the node to be executed is restricted by the second instance;

The sending unit is configured to: send a message rejecting a method of executing the node to be executed to the sending end; and/or

The receiving unit is further configured to: receive an instance management request sent by the sending end, where the instance management request includes a node ID to be executed and a method ID of the node to be executed;

The processing unit is further configured to: acquire, according to the node ID to be executed, a node record file to be executed; according to the second instance ID recorded in the node record file to be executed, and the node of the first instance Corresponding relationship of the method ID, determining that the execution of the method corresponding to the method ID of the node to be executed is limited by the second instance;

The sending unit is configured to: send a message rejecting a method of executing the node to be executed to the sending end.
The apparatus according to claim 35, wherein the plan corresponding to the plan ID to be executed is at least one of an update plan, a delete plan, a restart plan, and a stop plan; and the method ID of the node to be executed corresponds to The method is at least one of an update method, a delete method, a restart method, and a stop method.