Execution of a topology

• US 10,567,231 B2
• Filed: 10/30/2013
• Issued: 02/18/2020
• 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
• Primary Examiner(s): Joshi, Suraj M
• Application Number:
  US15/028,466
• Publication Number:
  US 20160254961A1
• Time in Patent Office: 2,302 Days
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3048 where the topology of the computing system or computing system component explicitly influences the monitoring activity, e.g. serial, hierarchical systems
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: G06F 11/3093 Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 47/829 Topology based
• 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
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A method of executing a topology includes deriving executable logic from the topology. The method of executing the topology further includes, with an LCM engine, executing the topology based on the executable logic.

Claims

1. A method executed by a system comprising a processor, comprising:

associating a monitoring policy and a provisioning policy with respective nodes of a topology, the nodes of the topology representing respective resources for implementing a service;

associating a blueprint with service workflows to be executed and managed, wherein the blueprint is a collection of workflows to be executed;

deriving executable logic based on the topology, the monitoring policy, and the provisioning policy, wherein the topology and the blueprint are supported by a same management engine and the blueprint is executed by the management engine to produce an instantiated service independent of the topology;

identifying non-dependent relationships among objects of the blueprint;

executing the executable logic that causes instantiating of the service to produce an instantiated service using a resource specified by the provisioning policy, wherein the executable logic with non-dependent relationships are executed in parallel; and

monitoring the instantiated service for an event according to the monitoring policy.

2. The method of claim 1, wherein deriving the executable logic based on the topology comprises walking the topology based on relationships between the nodes of the topology, and wherein walking the topology creates an execution plan.

3. The method of claim 1, further comprising:

associating a remediation policy with the topology, wherein the executable logic is derived further based on the remediation policy; and

in response to the monitoring identifying an incident, causing implementation of a remediation action according to the remediation policy to address the incident.

4. The method of claim 3, wherein causing the implementation of the remediation action to address the incident comprises modifying the topology.

5. The method of claim 1, wherein the executable logic comprises a script produced by an interpreter using the monitoring policy and the provisioning policy.

6. The method of claim of claim 1, wherein the topology is a realized topology.

7. The method of claim 1, wherein deriving the executable logic comprises:

identifying dependent relationships among the objects of the blueprint, the dependent relationships defining serial executions among dependently related nodes of the topology;

identifying non-dependent relationships among the objects of the blueprint, the non-dependent relationships defining parallel executions among non-dependently related nodes of the topology; and

designing the blueprint based on the objects of the blueprint, the dependent relationships and the non-dependent relationships.

8. The method of claim 1, further comprising associating lifecycle management actions (LCMAs) with a number of the nodes of the topology, the LCMAs comprising a first LCMA triggered by the monitoring policy, and a second LCMA triggered by the provisioning policy.

9. The method of claim 8, further comprising:

performing the LCMAs including the first LCMA during execution of the instantiated service.

10. The method of claim 1, further comprising executing, by a lifecycle management engine, a number of blueprints, the number of blueprints comprising the executable logic.

11. The method of claim 1, wherein executing the executable logic comprises:

converting the executable logic into an execution plan;

calling a number of resources providers to provision a number of devices; and

instantiating the service based on the execution plan.

12. A system comprising:

a processor; and

a non-transitory storage medium comprising instructions executable on the processor to;

determine whether a blueprint is to be executed, wherein the blueprint is executed to produce an instantiated service and is independent of a topology;

associate actions with a first and second node within the topology;

associate a monitoring policy with the first node of the topology, and associate a remediation policy with the second node of the topology;

derive executable logic based on the topology, the monitoring policy, and the remediation policy;

identify non-dependent relationships among objects of the blueprint;

execute the executable logic to cause instantiating of the service to produce an instantiated service, wherein the executable logic with non-dependent relationships are executed in parallel;

monitor a first resource of the instantiated service during execution for an event according to the monitoring policy, the first resource represented by the first node; and

in response to the monitoring identifying an incident, cause implementation of a remediation action with respect to a second resource according to the remediation policy to address the incident, the second resource represented by the second node.

13. The system of claim 12,

wherein deriving the executable logic comprises deriving a script using an interpreter that receives as inputs policies including the monitoring policy and the remediation policy.

14. The system of claim 12, wherein causing the implementation of the remediation action to address the incident comprises modifying the topology.

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

associate policies with nodes of a topology, the policies comprising a remediation policy associated with an individual node of the nodes;

associate a blueprint with service workflows to be executed and managed, wherein the blueprint is a collection of workflows to be executed and wherein the topology and the blueprint are supported by a same management engine and the blueprint is executed by the management engine to produce an instantiated service independent of the topology;

derive executable logic from the topology and the policies;

identify non-dependent relationships among objects of the blueprint execute the topology based on the executable logic to instantiate a cloud service, wherein the executable logic with non-dependent relationships are executed in parallel; and

perform a remediation action with respect to a resource of the instantiated cloud service according to the remediation policy to address an incident detected during execution of the instantiated cloud service, the resource represented by the individual node.

16. The non-transitory computer readable storage medium of claim 15, wherein the policies further comprise a monitoring policy, and the executable logic is derived further based on the monitoring policy, and wherein the computer usable program code upon execution causes the system to:

detect the incident according to the monitoring policy during the execution of the instantiated cloud service.

17. The non-transitory computer readable storage medium of claim 15, wherein the policies further comprise a provisioning policy, and the executable logic is derived further based on the monitoring policy, and wherein the instantiating of the cloud service uses a resource specified by the provisioning policy.

18. The non-transitory computer readable storage medium of claim 15, wherein performing the remediation action to address the incident comprises modifying the topology.

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

associate a lifecycle management action with a node of the topology; and

perform the lifecycle management action during execution of the instantiated cloud service.

20. The non-transitory computer readable storage medium of claim 15, wherein deriving the executable logic comprises deriving a script by an interpreter that receives as inputs the policies.