Distributed cloud application deployment systems and/or associated methods

• US 8,434,080 B2
• Filed: 12/22/2011
• Issued: 04/30/2013
• Est. Priority Date: 12/22/2011
• Status: Active Grant

• Current Assignee: Software AG USA Incorporated (Software AG)
• Original Assignee: Software AG USA Incorporated (Software AG)
• Inventors: Yendluri, Prasadarao
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): UNG, LANNY N
• Application Number:
  US13/335,205
• Publication Number:
  US 20120102486A1
• Time in Patent Office: 495 Days
• Field of Search: 717/177
• US Class Current: 717/177
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/5072 Grid computing

Abstract

In certain example embodiments, distributed cloud application deployment systems (DCADS), and/or associated methods are provided. A formal description of the cloud application is created. The cloud application'"'"'s formal representation, with its constituent nodes and their associated properties and interfaces, etc., is exported to a machine processable form. The exported DCADS machine processable rendition and any needed implementation artifacts are retrieved by a cloud application deployer that helps facilitate the deployment of the cloud application into the distributed and heterogeneous cloud environments as prescribed in the DCADS.

Claims

1. A computer-implemented method for setting up a cloud application in a heterogeneous distributed cloud provider environment including multiple computer systems, the computer systems being operated by different cloud providers, the method comprising:

defining the cloud application in terms of constituent application nodes, each said application node representing a part of the cloud application that is to be deployed into a single one of said computer systems in the heterogeneous distributed cloud provider environment that satisfies deployment requirements of that application node;

defining properties identifying deployment requirements of, and application level instantiation logic for, each said application node;

exposing, for each said application node, any interfaces that are invokable by one or more other application nodes;

identifying, for each said application node, any interfaces that it will invoke on one or more other application nodes; and

matching exposed interfaces and complementary invokable interfaces so as to enable communications to take place between the respective nodes via the matched interfaces.

2. The method of claim 1, wherein the properties are defined as <

Name, Value>

pairs on the application nodes.

3. The method of claim 1, wherein the properties of at least one said application node include at least one pointer to an artifact associated with the at least one application node.

4. The method of claim 3, wherein the at least one pointer refers to a standards-based policy when the associated property identifies a deployment requirement.

5. The method of claim 3, wherein the at least one pointer refers to executable code and/or executable components external to the at least one application node when the associated property relates to application level instantiation logic.

6. The method of claim 3, wherein the at least one pointer is a URI.

7. The method of claim 1, wherein, for each said application node, all exposed interfaces are matched with complementary invokable interfaces.

8. The method of claim 1, further comprising specifying a secure communication mechanism to be used for communications between at least two application nodes via interfaces associated therewith.

9. The method of claim 1, further comprising designating one application node to serve as a coordinator node, the coordinator node being configured to influence the dynamic behavior of the application.

10. The method of claim 9, wherein the coordinator node is configured to influence the dynamic behavior of the application via dynamic load-balancing and/or controlling fail-over.

11. The method of claim 9, wherein program logic for influencing the dynamic behavior of the application is built into or associated with the coordinator node, and/or associated with the computer system in which the coordinator node is located.

12. The method of claim 1, further comprising generating a machine processable rendering of the defined cloud application, the machine processable rendering including descriptions of the application nodes constituting the cloud application including their respective properties and exposed and invokable interfaces, as well as the matches between the exposed interfaces and the complementary invokable interfaces.

13. The method of claim 12, wherein the machine processable rendering is generated in an XML format.

14. The method of claim 12, further comprising deploying the application nodes to the computer systems in the heterogeneous distributed cloud provider environment based in part on the machine processable rendering.

15. The method of claim 14, wherein the application nodes are deployed to computer systems identified as being their preferred computer systems, if possible.

16. The method of claim 14, wherein multiple instances of a given application node are creatable during deployment based on an initial instance cardinality property for that given application node.

17. The method of claim 14, wherein the application nodes are deployed in accordance with a specified deployment order.

18. The method of claim 1, further comprising retrieving supporting artifacts associated with the defined cloud application.

19. The method of claim 18, further comprising packaging together retrieved supporting artifacts.

20. The method of claim 18, wherein supporting artifacts are retrieved by dereferencing URIs associated therewith.

22. A non-transitory computer storage medium tangibly storing instructions that, when executed by at least one processor of a computer, perform the method of claim 1.

21. A computer-implemented method for setting up an application in a cloud computing network environment in which different cloud providers operate respective computer processing systems, the method comprising:

receiving, prior to deployment of the cloud application, a definition of the cloud application that includes a list of its constituent nodes, each said node representing a part thereof that is to be deployed into a single one of said computer processing systems, the definition including lists of predefined deployment requirements of, and application level instantiation logic for, each said node, as well as matches between exposed and invokable interfaces of complementary ones of said nodes;

deploying the nodes to the computer processing systems operated by the different respective cloud providers in dependence on the definition of the cloud application, such that the nodes are able to operate on the computer processing systems to which they are deployed, given requirements of the nodes and capabilities of the computer processing systems, the capabilities of the computer processing systems depending at least in part on the processors and infrastructure configurations thereof;

obtaining network addresses for successfully deployed nodes; and

selectively transmitting obtained network addresses between deployed nodes that have matched exposed and invokable interfaces.

23. A cloud application design system for setting up a cloud application in a heterogeneous distributed cloud provider environment including multiple computer systems, the computer systems being operated by different cloud providers, the cloud application design system comprising:

at least one processor;

a user interface operating under the control of the at least one processor and configured, prior to deployment of the cloud application, to receive input;

defining the cloud application in terms of constituent nodes, each said node representing a part of the cloud application that is to be deployed into a single one of said computer systems in the heterogeneous distributed cloud provider environment that satisfies deployment requirements of that node, at least some of the deployment requirements being indicative of resources of and/or included in the respective computer system into which the node is to be deployed, the resources being external to the cloud application and any nodes of the cloud application,

defining properties identifying deployment requirements of, and application level instantiation logic for, each said node,

indicating, for each said node, one or more interfaces thereof that are to be exposed as invokable by one or more other nodes,

identifying, for each said node, one or more interfaces thereof that it will invoke on one or more other nodes, and

indicative of how exposed interfaces are to be matched to complementary invokable interfaces as between the nodes that define the cloud application;

a first storage location configured to store the input in a predefined format; and

a second storage location configured to store artifacts used in supporting the application level instantiation logic of the nodes,

wherein each said computer system in the heterogeneous distributed cloud provider environment is a cloud operated by a different cloud provider.

24. The system of claim 23, wherein the properties are defined as <

Name, Value>

pairs on the nodes.

25. The system of claim 24, wherein the value part of at least some of said pairs are URIs.

26. The system of claim 23, wherein the user interface is configured to accept further input specifying a secure communication mechanism to be used for communications between at least two nodes via interfaces associated therewith.

27. The system of claim 23, wherein the user interface is configured to accept further input designating one node to serve as a coordinator node to be configured to influence the dynamic behavior of the application by initiating dynamic load-balancing and/or controlling fail-over.

28. The system of claim 23, wherein the at least one processor is further configured to cause the nodes to be deployed to the computer systems in the heterogeneous distributed cloud provider environment based in part on the user input stored in the predefined format.

29. The system of claim 23, wherein the at least one processor is further configured to deploy the nodes to computer systems that it determines meet specified requirements for the nodes, optionally taking into account user specified preferences for individual node deployments.

30. The system of claim 23, wherein the at least one processor is further configured to create multiple instances of a node based on a user-specified cardinality property and/or deploy nodes in accordance with a user-specified deployment order.