Execution of a topology

1. A non-transitory computer readable medium storing lifecycle management engine instructions that when executed cause a processor to:

derive serial or parallel scripts from a graph of a topology that represents a cloud service by executing a walking algorithm guided by relationships between nodes within the graph of the topology, wherein the serial or parallel scripts define executable logic for instantiating the topology;

execute the serial or parallel scripts to create an instantiated cloud service, wherein to execute the serial or parallel scripts includes calling a number of resource providers to provision a number of devices; and

identify policies associated with at least one of the following: a node of the topology, a group of nodes of the topology, a portion of the topology, or the topology as a whole,

wherein to derive the serial or parallel scripts from the graph of the topology is based on the identified policies, and the identified policies include monitoring policies that define monitoring of nodes of the topology.

2. The non-transitory computer readable medium of claim 1 , wherein a node of the graph of the topology represents a hardware device, a virtual device, a group of hardware devices, or a group of virtual devices.

3. The non-transitory computer readable medium of claim 1 , wherein the lifecycle management engine instructions when executed cause the processor to execute a design tool for designing a cloud service topology using a graphical user interface.

4. The non-transitory computer readable medium of claim 3 , wherein the lifecycle management engine instructions when executed cause the processor to, during execution of the design tool, associate policies with a node of the topology, a group of nodes of the topology, a portion of the topology, or the topology as a whole.

5. The non-transitory computer readable medium of claim 4 , wherein the policies comprise provisioning policies and capabilities policies, the provisioning policies defining characteristics of computing devices and the capabilities policies indicating that an associated node is capable of processing data at a certain rate or has a certain storage space.

6. The non-transitory computer readable medium of claim 3 , wherein the lifecycle management engine instructions when executed cause the processor to, during execution of the design tool, associating lifecycle management actions with a node of the topology, a group of nodes of the topology, a portion of the topology, or the topology as a whole.

7. The non-transitory computer readable medium of claim 3 , wherein to derive the serial or parallel scripts from the graph of the topology is based on policies and lifecycle management actions associated with one or more nodes of the topology.

8. The non-transitory computer readable medium of claim 1 , wherein the lifecycle management engine instructions when executed cause the processor to:

obtain resource provider policies from the number of resource providers; and

select which resource providers from which to provision computing resources based on identified policies associated with a particular node of the topology and based on the resource provider policies.

9. The non-transitory computer readable medium of claim 1 , wherein

the lifecycle management engine instructions when executed cause the processor to monitor the instantiated cloud service based on monitoring policies.

10. The non-transitory computer readable medium of claim 1 , wherein the lifecycle management engine instructions when executed cause the processor to present, for a user to select as the topology, a plurality of application models as possible matches to an infrastructure template.

11. The non-transitory computer readable medium of claim 1 , wherein the lifecycle management engine instructions when executed cause the processor to stitch an application model to an infrastructure template to create the topology.

12. A system comprising:

a processor; and

a non-transitory computer readable medium storing instructions, that when executed by the processor, cause the processor to:

identify policies associated with a node of a topology, a group of nodes of the topology, a portion of the topology, or the topology as a whole, wherein the topology represents a cloud service, and wherein the identified policies include monitoring policies that define monitoring of nodes of the topology;

derive serial or parallel scripts from a graph of the topology by executing a walking algorithm guided by relationships between nodes within the graph of the topology and based on the identified policies, wherein the serial or parallel scripts define executable logic for instantiating the topology; and

execute the serial or parallel scripts to create an instantiated cloud service, wherein to execute the serial or parallel scripts includes calling a number of resource providers to provision a number of devices.

13. The system of claim 12 , wherein the instructions when executed further cause the processor to execute a design tool for designing a cloud service topology using a graphical user interface.

14. A method comprising:

identifying, by a processor-based lifecycle management engine, policies associated with a node of a topology, a group of nodes of the topology, a portion of the topology, or the topology as a whole, wherein the topology represents a cloud service, and wherein the identified policies include monitoring policies that define monitoring of nodes of the topology;

deriving, by the processor-based lifecycle management engine, serial or parallel scripts from a graph of the topology by executing a walking algorithm guided by relationships between nodes within the graph of the topology and based on the identified policies, wherein the serial or parallel scripts define executable logic for instantiating the topology; and

executing, by the processor-based lifecycle management engine, the serial or parallel scripts to create an instantiated cloud service, wherein to execute the serial or parallel scripts includes calling a number of resource providers to provision a number of devices.

15. The method of claim 14 , wherein the deriving the serial or parallel scripts is further based lifecycle management actions associated with one or more nodes of the topology.

16. The method of claim 14 , monitoring the instantiated cloud service based on monitoring policies included among the identified policies.

17. The method of claim 14 , further comprising:

obtaining resource provider policies from the number of resource providers; and

selecting which resource providers from which to provision computing resources based on identified policies associated with a particular node of the topology and based on the resource provider policies.