Localized service resiliency

Patent metadata

Field	Value
Publication number	US-10666497-B2
Application number	US-201816015247-A
Country	US
Kind code	B2
Filing date	Jun 22, 2018
Priority date	Jun 22, 2018
Publication date	May 26, 2020
Grant date	May 26, 2020

Abstract

There is disclosed in one example a computing apparatus, including: a local platform including a hardware platform; a management interface to communicatively couple the local platform to a management controller; a virtualization infrastructure to operate on the hardware platform and to provide a local virtualized function; and a resiliency controller to operate on the hardware platform, and configured to: receive a resiliency policy from the management controller via the management interface, the resiliency policy including information to handle a fault in the virtualized function; detect a fault in the local virtualized function; and effect a resiliency action responsive to detecting the fault.

First claim

What is claimed is:

1. A computing apparatus, comprising:
a local platform including a hardware platform;
a management interface to communicatively couple the local platform to a management controller;
a virtualization infrastructure to operate on the hardware platform and to provide a local virtualized function; and
a resiliency controller to operate on the hardware platform, and configured to perform operations comprising:
generate and maintain a topology hardware dependency graph;
receive a resiliency policy from the management controller via the management interface, the resiliency policy comprising information to handle a fault in the local virtualized function;
detect a fault in the local virtualized function; and
effect a resiliency action responsive to detecting the fault and according to the topology hardware dependency graph.

2. The computing apparatus of claim 1 , wherein the resiliency controller is further configured to notify the management controller of the resiliency action via a one-directional message on the management interface, wherein the one-directional message is a message that may receive, but does not require, an acknowledgement or response from the management controller.

3. The computing apparatus of claim 1 , wherein the resiliency controller is further configured to detect a failure of the resiliency action, and to place the local virtualized function into a failsafe mode.

4. The computing apparatus of claim 3 , wherein the failsafe mode comprises disabling or isolating one or more egress ports of the local platform or of the local virtualized function.

5. The computing apparatus of claim 1 , wherein the resiliency controller is further configured to associate hardware resources of the hardware platform with the local virtualized function.

6. The computing apparatus of claim 5 , wherein the resiliency controller is further configured to continuously monitor fault domains on the hardware platform.

7. The computing apparatus of claim 1 , wherein the resiliency controller is further configured to customize the resiliency policy according to the hardware dependency graph.

8. The computing apparatus of claim 1 , wherein the resiliency policy includes a virtual network function (VNF) policy and a network function virtualization infrastructure (NFVI) policy.

9. The computing apparatus of claim 1 , wherein the local virtualized function is a virtual network function (VNF), and the fault is a failure of a virtualized resource.

10. The computing apparatus of claim 1 , wherein the local virtualized function is a virtual network function (VNF), and the fault is a failure of a localized hardware element on the hardware platform.

11. The computing apparatus of claim 1 , wherein the local virtualized function is a virtual network function (VNF), and the fault is a failure of connectivity to the management controller.

12. The computing apparatus of claim 1 , wherein the local virtualized function is a virtual switch (vSwitch).

13. The computing apparatus of claim 1 , wherein the resiliency controller is isolated from software faults.

14. A resiliency controller, comprising:
a management interface to communicatively couple the local platform to a management controller;
a virtualization infrastructure interface to communicatively couple to a local virtualized function; and
logic to:
construct a topology hardware dependency graph;
receive a resiliency policy from the management controller via the management interface, the resiliency policy comprising information to handle a fault in the local virtualized function;
detect a fault in the local virtualized function; and
according to the topology hardware dependency graph, effect a resiliency action responsive to detecting the fault.

15. A computing apparatus comprising software configured to provide the resiliency controller of claim 14 .

16. A computing apparatus comprising a co-processor configured to provide the resiliency controller of claim 14 .

17. An application-specific integrated circuit (ASIC) comprising the resiliency controller of claim 14 .

18. A field-programmable gate array (FPGA) comprising the resiliency controller of claim 14 .

19. An intellectual property (IP) block comprising the resiliency controller of claim 14 .

20. The resiliency controller of claim 14 comprising microcode hooks into a core architecture.

21. A method of providing local resiliency control on a computing apparatus, comprising:
communicatively coupling to a management controller via a management interface;
communicatively coupling to a local virtualized function via a virtualization infrastructure interface;
associating hardware controlled by the computing apparatus with the local virtualized function;
receiving a resiliency policy from the management controller via the management interface, the resiliency policy comprising information to handle a fault in the local virtualized function;
monitoring a plurality of fault domains of the local virtualized function according to the resiliency policy;
detecting a fault in a monitored fault domain; and
effecting a resiliency action responsive to detecting the fault.

22. The method of claim 21 , further comprising notifying the management controller of the resiliency action via a one-directional message on the management interface, wherein the one-directional message is a message that may receive, but does not require, an acknowledgement or response from the management controller.

23. The method of claim 21 , further comprising detecting a failure of the resiliency action, and to place the local virtualized function into a failsafe mode.

24. The method of claim 23 , wherein the failsafe mode comprises disabling or isolating one or more egress ports of a local platform or of the local virtualized function.

Assignees

• Intel Corp

Inventors

• Tahhan Maryam
• Browne John Joseph
• Walsh Eoin
• Verrall Timothy
• Browne Rory
• Foley Emma Louise
• Jain Shobhi
• Mangan Peter

Classifications

• G06F2009/45587

  Isolation or security of virtual machine instances · CPC title

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• H04L41/0654 Primary

  using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) · CPC title

• G06F2009/45595

  Network integration; Enabling network access in virtual machine instances · CPC title