Topology remediation

• US 10,177,988 B2
• Filed: 10/30/2013
• Issued: 01/08/2019
• 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): Chan, Wing F
• Assistant Examiner(s): Maniwang, Joseph R
• Application Number:
  US15/028,510
• Publication Number:
  US 20160269249A1
• Time in Patent Office: 1,896 Days
• Field of Search: 709223, 709224
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9538 Presentation of query results
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/18 Delegation of network management function, e.g. customer network management [CNM]
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/5029 Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
• CPC Class Codes: H04L 41/5074 Handling of user complaints or trouble tickets
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 45/02 Topology update or discovery

Abstract

A topology remediation method includes with a remediation engine, deriving a number of remediation actions based on a number of incidents within an instantiated topology, and with a lifecycle management engine, modifying the instantiated topology based on a number of lifecycle management actions (LCMAs) determined to remediate the incidents.

Claims

1. A method, comprising:

instantiating, by a system comprising a hardware processor, an instantiated service according to a topology comprising a plurality of nodes, wherein lifecycle management actions (LCMAs) are individually associated with respective nodes of the plurality of nodes of the topology;

deriving, by the system, a number of remediation actions in response to a number of incidents within the instantiated service;

modifying, by the system, the topology based on a number of the LCMAs invoked by the number of remediation actions, the number of the LCMAs to remediate the number of incidents; and

forming, by the system, a modified instantiated service based on the modified topology.

2. The method of claim 1, wherein deriving the number of remediation actions is performed based on a number of policies associated with the topology.

3. The method of claim 1, further comprising:

monitoring, by the system, a number of metrics for the instantiated service;

deriving, by the system, a number of events based on the number of metrics;

deriving, by the system, the number of incidents based on the number of events.

4. The method of claim 1, further comprising:

obtaining, by the system, a number of service tickets from an information technology (IT) service management system (ITSM);

deriving, by the system, the number of incidents based on the number of service tickets,

wherein deriving the number of remediation actions is based on the number of incidents derived from the number of service tickets.

5. The method of claim 1, further comprising presenting, with a self-service subscription management device, a number of graphical user interfaces (GUIs) including information regarding the number of incidents.

6. The method of claim 5, wherein presenting the number of GUIs comprises presenting a number of notification icons associated with the number of incidents within the instantiated service.

7. The method of claim 1, wherein deriving the number of remediation actions is based on a number of policies, a context of events relating to the number of incidents a configuration of the topology, or a combination thereof.

8. The method of claim 1, wherein the instantiating of the instantiated service is based on policies individually associated with the nodes of the topology, the nodes representing corresponding devices.

9. The method of claim 1, wherein the number of incidents comprise a hardware failure and a software failure, and the modifying of the topology is to remediate the hardware failure and the software failure.

10. The method of claim 1, wherein the topology comprises policies individually associated with the nodes of the topology, the policies defining the number of remediation actions for the number of incidents.

11. The method of claim 10, further comprising:

in response to the number of incidents, provisioning and deploying a previously non-existent remediation engine according to a policy of the policies,

wherein the deriving and the modifying are performed by the remediation engine.

12. A system, comprising:

a processor; and

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

present a number of graphical user interfaces (GUIs) to a user regarding a number of incidents within an instantiated service instantiated according to a topology comprising a plurality of nodes, wherein lifecycle management actions (LCMAs) are individually associated with respective nodes of the plurality of nodes of the topology;

derive a number of remediation actions based on the number of the incidents;

modify the topology based on a number of the LCMAs called by the number of remediation actions; and

form a modified instantiated service based on the modified topology, the modified instantiated service including a modified computing device.

13. The system of claim 12, wherein number of the GUIs comprise:

a realized topology GUI to display a realized topology derived from the instantiated service, the realized topology GUI comprising;

a number of user-selectable detail buttons to, when selected, display details regarding a number of nodes within the realized topology;

a number of user-selectable nodes to, when selected, present a remediation menu associated with a selected node; and

a number of user-selectable optional nodes to, when selected, alter the realized topology.

14. The system of claim 12, wherein the instructions are executable on the processor to:

monitor the instantiated service for a number of events; and

create the number of the incidents based on the number of events.

15. The system of claim 12, wherein the instructions are executable on the processor to:

in response to the number of incidents, provision and deploy a previously non-existent remediation engine according to a policy of the policies,

wherein the deriving and the modifying are performed by the remediation engine.

16. The system of claim 12, wherein the topology comprises policies individually associated with the nodes of the topology, the policies defining the number of remediation actions for the number of incidents.

17. The system of claim 12, wherein the number of incidents comprise an improperly provisioned device, and the modifying of the topology is to remediate the improperly provisioned device.

18. A non-transitory computer readable storage medium storing instructions that upon execution cause a system to:

monitor an instantiated service for an event, the instantiated service instantiated according to a topology comprising a plurality of nodes, wherein lifecycle management actions (LCMAs) are individually associated with respective nodes of the plurality of nodes of the topology;

derive an incident based on the event;

derive a lifecycle management action (LCMA) based on the incident;

modify the instantiated service based on the LCMA; and

form a modified instantiated service based on the modified topology.

19. The non-transitory computer readable storage medium of claim 18, wherein the instructions upon execution cause the system to:

in response to the incident, provision and deploy a previously non-existent remediation engine according to a policy of the policies,

wherein the deriving of the LCMA and the modifying of the topology are performed by the remediation engine.

20. The non-transitory computer readable storage medium of claim 18, wherein the topology comprises policies individually associated with the nodes of the topology, the policies defining the LCMA for the incident.