MANAGEMENT OF THE LIFECYCLE OF A CLOUD SERVICE MODELED AS A TOPOLOGY

• US 20160285694A1
• Filed: 10/30/2013
• Published: 09/29/2016
• Est. Priority Date: 10/30/2013
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Maes, Stephane Herman
• Granted Patent: US 10,230,580 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• 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 method of managing the lifecycle of cloud service modeled as a topology includes, with a processor, generating a topology, the topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology, associating a number of policies with a number of nodes within the topology, the policies guiding the lifecycle management of the nodes, and with a lifecycle management engine, executing the topology.

Claims

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

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

associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology;

associating a number of policies with a number of nodes within the topology, the policies guiding the lifecycle management of the nodes; and

with a lifecycle management engine, executing the topology.

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.

4. The method of claim 3, in which tracking the realized topology comprises storing the topology in a database of realized topologies.

5. The method of claim 1, further comprising:

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

generating a number of incidents based on the policies.

6. The method of claim 5, further comprising processing the incidents, in which processing the incidents comprises 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 combinations thereof.

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

8. The method of claim 1, in which, generating a topology, comprises:

with a topology designer, generating a number of application models; and

with a stitching engine, stitching the application model to a number of infrastructure topologies,

in which the application models and infrastructure topologies are designed by a topology designer, obtained from a database, or combinations thereof.

9. The method of claim 1, in which the policies comprise provisioning policies, monitoring policies, remediation policies, event processing policies, resource provider policies, governance policies, security polices, access control policies, usage control policies, or combinations thereof.

10. The method of claim 1, in which, generating a topology comprises:

receiving a topology from a user, the topology being stored in a catalog.

11. The method of claim 1, in which, generating a topology comprises:

with a topology designer, generating a topology de novo.

12. A topology-based cloud management system, comprising:

a topology lifecycle management (LCM) engine to execute an topology to instantiate a service based on the topology,

in which the LCM engine executes the instantiated service using a number of functions calls defined by a number of LCMAs and guided by a number of policies associated with a number of nodes within the topology.

13. The system of claim 12, further comprising a realized topology system management (RTSM) database to store a number of realized topologies, the realized topologies comprising:

a number of nodes representing computing resources provisioned in the instantiated service;

a number of the policies associated with the nodes, the policies being assigned to corresponding nodes in the topology; and

a number of the LCMAs associated with the nodes, the LCMAs being assigned to corresponding nodes in the topology.

14. The system of claim 12, further comprising a remediation system to generate a number of remediating actions based on a number of incidents derived from the instantiated service.

15. The system of claim 14, in which the remediating actions are utilized by the LCM engine to create a subsequent instantiated service, the subsequent instantiated service comprising a number of computing resources that match the designed topology and changes made to the instantiated service as defined by the remediating actions.

16. The system of claim 12, further comprising a stitching engine to stitch a number of application models to a number of infrastructure topologies to form the topology.

17. A computer program product for managing the lifecycle of a topology-based instantiated service, the computer program product comprising:

a computer readable storage medium comprising computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code to, when executed by a processor, generating a topology, the topology representing a cloud service;

computer usable program code to, when executed by a processor, associate a number of lifecycle management actions (LCMAs) with a number of nodes within the topology;

computer usable program code to, when executed by a processor, associate a number of policies with a number of nodes within the topology, the policies guiding the lifecycle management of the nodes; and

computer usable program code to, when executed by a processor, execute the topology.

18. The computer program product of claim 17, in which the computer usable program code to, when executed by a processor, generate a topology and executing the topology, comprises:

computer usable program code to, when executed by a processor, receive a blueprint from a blueprint source; and

computer usable program code to, when executed by a processor, execute the blueprint according to a number of workflows associated with the blueprints.

19. The computer program product of claim 17, in which the computer usable program code to, when executed by a processor, generate a topology comprises:

computer usable program code to, when executed by a processor, receive a topology from a user, the topology being stored in a catalog.

20. The computer program product of claim 17, in which the computer usable program code to, when executed by a processor, generating a topology comprises:

computer usable program code to, when executed by a processor, generate a topology de novo.