Assignment of application models to deployment targets

• US 8,087,015 B2
• Filed: 10/26/2007
• Issued: 12/27/2011
• Est. Priority Date: 10/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Pogrebinsky, Vladimir, Johnson, Benjamin George, Panditharadhya, Nagalinga Durga Prasad Sripathi, Bhaskara, Udaya Kumar, Eshner, Daniel
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Smith, Cheneca
• Application Number:
  US11/925,731
• Publication Number:
  US 20090112966A1
• Time in Patent Office: 1,523 Days
• Field of Search: None
• US Class Current: 717/172
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A distributed application deployment engine uses declarative deployment data that describes deployment characteristics for application modules, and potential target environments. The engine uses the deployment data to potentially match a module to a deployment target. At some point, the modules may then be actually deployed on the identified deployment target. This may be performed for multiple modules in the distributed application, thereby deploying the distributed application in a distributed environment.

Claims

1. A computer-implemented method for determining whether and how one or more modules of a distributed application may be distributed to one or more machines in a distributed computing environment, the method comprising:

storing in a model repository

deployment data for each module of the distributed application, the deployment data of each module identifying deployment requirements for the respective module of the distributed application, and

deployment data for a plurality of machines in the distributed environment, the deployment data for a given machine identifying at least one characteristic of the machine and at least one characteristic of a runtime for the given machine;

a distributed application deployment engine accessing from the model repository

deployment data for at least one module of the distributed application, and

deployment data for said plurality of machines in the distributed environment, each of said machines representing a potential deployment target for deployment of the at least one module of the distributed application;

the distributed application deployment engine thereafter automatically performing a matching operation for the at least one module using the deployment data accessed from the model repository for the at least one module and using the deployment data accessed from the model repository for said potential deployment targets;

if the deployment data for the at least one module cannot be matched to a deployment target, returning a message indicating one or more reasons why the deployment data cannot be matched,

but if the deployment data for the at least one module is matched to one or more potential deployment targets, then selecting one of the targets and deploying the at least one module to that deployment target;

thereafter redeploying the distributed application by performing the following;

identifying that a redeployment event has occurred for at least one module of the distributed application; and

upon determining that the redeployment event has occurred, performing the following for each of the plurality of modules in the distributed application;

the deployment engine accessing from the model repository the deployment data for each of the modules;

the deployment engine accessing from the model repository deployment data for a plurality of potential redeployment targets;

the deployment engine automatically performing a matching operation for one or more of the modules using the deployment data stored for each of the modules and using the deployment data for the potential redeployment targets to identify whether one or more of the potential redeployment targets match one or more of the modules; and

if so, causing the modules which have a match to be redeployed on one of the matched redeployment targets.

2. The computer-implemented method in accordance with claim 1, wherein deploying the at least one module comprises:

an altering a property of the module to specify the deployment target;

using the property to identify where the module should be deployed; and

installing and configuring the module in the deployment target as specified by the altered property of the module.

3. A computer program product comprising a computer system hardware memory having thereon one or more computer-executable instructions which, when executed by one or more processors of the computing system, implements a method for determining whether and how one or more modules of a distributed application may be distributed to one or more machines in a distributed computing environment, and wherein the method comprises:

storing in a model repository

deployment data for each module of the distributed application, the deployment data of each module identifying deployment requirements for the respective module of the distributed application, and

deployment data for a plurality of machines in the distributed environment, the deployment data for a given machine identifying at least one characteristic of the machine and at least one characteristic of a runtime for the given machine;

a distributed application deployment engine accessing from the model repository

deployment data for at least one module of the distributed application, and

deployment data for said plurality of machines in the distributed environment, each of said machines representing a potential deployment target for deployment of the at least one module of the distributed application; and

the distributed application deployment engine thereafter automatically performing a matching operation for the at least one module using the deployment data accessed from the model repository for the at least one module and using the deployment data accessed from the model repository for said potential deployment targets; and

if the deployment data for the at least one module cannot be matched to a deployment target, returning a message indicating one or more reasons why the deployment data cannot be matched,

but if the deployment data for the at least one module is matched to one or more potential deployment targets, then selecting one of the targets and deploying the at least one module to that deployment target;

thereafter redeploying the distributed application by performing the following;

identifying that a redeployment event has occurred for at least one module of the distributed application; and

upon determining that the redeployment event has occurred, performing the following for each of the plurality of modules in the distributed application;

the deployment engine accessing from the model repository the deployment data for each of the modules;

the deployment engine accessing from the model repository deployment data for a plurality of potential redeployment targets;

the deployment engine automatically performing a matching operation for one or more of the modules using the deployment data stored for each of the modules and using the deployment data for the potential redeployment targets to identify whether one or more of the potential redeployment targets match one or more of the modules; and

if so, causing the modules which have a match to be redeployed on one of the matched redeployment targets.

4. A computer program product in accordance with claim 3, wherein the redeployment event is user-initiated.

5. A computer program product in accordance with claim 3, wherein the redeployment event is detected without involving a user-initiated process.

6. A computer program product in accordance with claim 3, wherein the at least one characteristic of the machine includes at least one of a computer model, a number of processors, a processor speed, an available memory, an available disk space, a memory access speed, or a disk access speed.

7. A computer program product in accordance with claim 3, wherein the at least one characteristic of the runtime includes at least one of a technology type supported by the runtime, a version of the runtime, or a clustering support status for the runtime.

8. A computer program product in accordance with claim 3, wherein the deployment data for at least one of the modules identifies a machine that the module can be deployed on, whereas the deployment data for at least others of the modules does not expressly identify a machine that the module is to be deployed on.

9. A computer program product in accordance with claim 3, wherein the deployment data for one of the modules specifies that the module is to be deployed on a different machine than at least one other of the modules.

10. A computer program product in accordance with claim 3, wherein the deployment data for one of the modules specifies that the module is to be deployed on the same machine as at least one of the other modules.

11. A computer program product in accordance with claim 3, wherein the deployment data for at least one of the machines in the distributed environment specifies that the total processing power used by all of the modules deployed to that machine is to remain below a particular level.

12. A computer program product in accordance with claim 3, wherein the deployment data for at least one of the machines in the distributed environment specifies that the total memory used by all of the modules deployed to that machine is to remain below a particular level.