Management of the lifecycle of a cloud service modeled as a topology

1. A method of managing a lifecycle of a cloud service modeled as a topology, comprising:

with a processor, generating the topology representing the cloud service;

associating a number of lifecycle management actions (LCMAs) with respective nodes within the topology, the associating comprising associating a first LCMA of the number of LCMAs individually with a node of the respective nodes or with a subset of the respective nodes;

associating a number of policies with corresponding nodes within the topology, the number of policies guiding a lifecycle management of the corresponding nodes, the number of policies comprising a monitoring policy that specifies monitoring a device represented by a first node within the topology, the monitoring being part of the lifecycle management; and

with a lifecycle management engine, executing the topology, the executing of the topology instantiating the cloud service and comprising calling an LCMA of the number of LCMAs in response to the monitoring according to the monitoring policy, wherein the executing of the topology comprises performing a remediation action that is part of the called LCMA in response to an incident of the instantiated cloud service detected according to the monitoring policy, and wherein the remediation action causes creation of a subsequent instantiated service, the subsequent instantiated service comprising a number of computing resources that match the topology and a change made to the instantiated cloud service by the remediation action.

2. The method of claim 1 , further comprising, with the lifecycle management engine, deriving a realized topology from the instantiated cloud service.

3. The method of claim 2 , further comprising tracking the realized topology, wherein the tracking of the realized topology comprises storing the realized topology in a database of realized topologies.

4. The method of claim 1 , further comprising:

with an event handler, determining, based on the number of policies, how to handle events; and

generating a number of incidents based on the policies.

5. The method of claim 4 , further comprising processing the number of incidents, wherein the processing of the number of incidents comprises at least one selected from among providing notifications to a user, obtaining instructions from the user, taking manual actions input by the user, taking autonomous actions after receiving instructions from the user, taking autonomous actions without receiving instructions from the user, taking autonomous actions without notifying the user, receiving instructions from the user, or a combination thereof.

6. The method of claim 5 , further comprising, with a self-service subscription management engine, presenting a number of graphical user interfaces (GUIs) to the user regarding the number of incidents, wherein the self-service subscription management engine receives, through the number of GUIs, a number of user inputs regarding the number of incidents and a number of remediation actions.

7. The method of claim 1 , wherein the generating of the topology comprises:

generating a number of application models; and

stitching the number of application models to a number of infrastructure topologies.

8. The method of claim 1 , wherein the number of policies further comprise at least one selected from among a provisioning policy, a remediation policy, an event processing policy, a resource provider policy, a governance policy, a security policy, an access control policy, a usage control policy, or a combination thereof.

9. The method of claim 1 , wherein the generating of the topology comprises one of:

receiving selection of the topology stored in a catalog from a user; and

with a topology designer, generating the topology de novo.

10. The method of claim 1 , wherein associating the monitoring policy with the first node within the topology comprises adding information of the monitoring policy to the first node within the topology.

11. The method of claim 1 , wherein calling the LCMA causes updating of the topology.

12. A system, comprising:

a processor; and

a non-transitory storage medium storing instructions executable on the processor to:

associate a number of lifecycle management actions (LCMAs) with respective nodes within a topology, the associating comprising associating a first LCMA of the number of LCMAs individually with a node of the respective nodes or with a subset of the respective nodes;

add information of a monitoring policy to a first node within the topology, the monitoring policy specifying monitoring of a device represented by the first node within the topology; and

execute the topology to instantiate a service based on the topology, the executing of the topology using a number of functions calls defined by the number of LCMAs and guided by a number of policies including the monitoring policy, wherein the executing of the topology comprises performing a remediation action that is part of the number of LCMAs in response to an incident of the instantiated service detected according to the monitoring policy, and wherein the remediation action causes creation of a subsequent instantiated service, the subsequent instantiated service comprising a number of computing resources that match the topology and a change made to the instantiated service by the remediation action.

13. The system of claim 12 , wherein the instructions are executable on the processor to stitch a number of application models to a number of infrastructure topologies to form the topology.

14. The system of claim 12 , wherein the function calls comprise accessing uniform resource identifiers of application programming interfaces.

15. A non-transitory computer readable storage medium comprising a program code that upon execution causes a system to:

generate a topology representing a cloud service;

associate a number of lifecycle management actions (LCMAs) with respective nodes within the topology, the associating comprising associating a first LCMA of the number of LCMAs individually with a node of the respective nodes or with a subset of the respective nodes;

associate a number of policies with corresponding nodes within the topology, the number of policies guiding a lifecycle management of the corresponding nodes, the number of policies comprising a monitoring policy that specifies monitoring a device represented by a first node within the topology, the monitoring being part of the lifecycle management; and

execute the topology, the executing of the topology to instantiate the cloud service and comprises calling an LCMA of the number of LCMAs in response to the monitoring according to the monitoring policy, wherein the executing of the topology comprises performing a remediation action that is part of the called LCMA in response to an incident of the instantiated cloud service detected according to the monitoring policy, and wherein the remediation action causes creation of a subsequent instantiated service, the subsequent instantiated service comprising a number of computing resources that match the topology and a change made to the instantiated cloud service by the remediation action.

16. The non-transitory computer readable storage medium of claim 15 , wherein the program code upon execution causes the system to:

receive a blueprint from a blueprint source; and

execute the blueprint according to a number of workflows associated with the blueprint.

17. The non-transitory computer readable storage medium of claim 15 , wherein associating the monitoring policy with the first node within the topology comprises adding information of the monitoring policy to the first node within the topology.