HARDWARE CONSUMPTION ARCHITECTURE

• US 20130086411A1
• Filed: 09/30/2011
• Published: 04/04/2013
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Inventors: Bauer, Eric J., Adams, Randee S., Clougherty, Mark M., Reents, William D.
• Granted Patent: US 9,183,102 B2
• Time in Patent Office: Days
• US Class Current: 714/3
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 11/1484 involving virtual machines
• CPC Class Codes: G06F 11/1666 where the redundant component is memory or memory area
• CPC Class Codes: G06F 11/20 using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 11/2041 with more than one idle spare processing component
• 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

Abstract

Various exemplary embodiments relate to a method and related network node including one or more of the following: identifying a hardware failure of a failed component of a plurality of hardware components; determining a set of agent devices currently configured to utilize the failed component; reconfiguring an agent device to utilize a working component of the plurality of hardware components. Various exemplary embodiments additionally or alternatively relate to a method and related network node including one or more of the following: projecting a failure date for the hardware module; determining whether the projected failure date is acceptable based on a target replacement date for the hardware module; if the projected failure date is not acceptable: selecting a parameter adjustment for a hardware component, wherein the parameter adjustment is selected to move the projected failure date closer to the target replacement date, and applying the parameter adjustment to the hardware component.

Claims

1. A method performed by a hardware management device for enabling incremental failure of a hardware system, the hardware system including a hardware module, the hardware module including a circuit board upon which a plurality of hardware components is mounted, the method comprising:

identifying a hardware failure of a failed component of the plurality of hardware components;

determining a set of agent devices currently configured to utilize the failed component;

for at least one agent device of the set of agent devices, reconfiguring the agent device to utilize a working component of the plurality of hardware components in place of the failed component; and

deactivating the failed component, wherein other hardware components of the plurality of hardware components remain in operation.

2. The method of claim 1, further comprising reconfiguring the hardware module to power down the failed component while continuing to provide power to at least one other component of the plurality of hardware components.

3. The method of claim 1, wherein all hardware components mounted on the circuit board are of a single type of hardware component.

4. The method of claim 1, wherein the hardware management device comprises a hypervisor and wherein the hardware management device utilizes at least one component of the plurality of hardware components to operate.

5. The method of claim 1, wherein the hardware management device comprises a cloud computing gateway device and wherein:

the hardware management device manages a plurality of hypervisors; and

a first hypervisor of the plurality of hypervisors manages the plurality of hardware components.

6. The method of claim 5, further comprising:

for at least one agent device of the set of agent devices, reconfiguring the agent device to be managed by a second hypervisor of the plurality of hypervisors.

7. A hardware system capable of incremental hardware failure, the hardware system comprising:

a circuit board;

a plurality of hardware components mounted on the circuit board;

at least one agent device configured to utilize at least one hardware component of the plurality of hardware components; and

a management device that, during run time, deactivates at least one hardware component of the plurality of hardware components while at least one remaining component of the plurality of hardware components remains in operation,

8. The hardware system of claim 7, wherein, in deactivating the at least one hardware component, the management device reconfigures the circuit board to power down the at least one component.

9. The hardware system of claim 7, wherein the management device includes a hypervisor and the management device utilizes at least one hardware component of the plurality of hardware components.

10. The hardware system of claim 7, wherein all hardware components mounted on the circuit board are of the same type.

11. The hardware system of claim 7, wherein, in deactivating the at least one hardware component, the management device:

identifies a set of agent devices configured to utilize the at least one hardware component; and

reconfigures at least one agent device of the set of agent devices to utilize the at least one remaining component instead of the at least one hardware component.

12. The hardware system of claim 7, wherein the management device deactivates the at least one hardware component of the plurality of hardware components in response to determining that the at least one hardware component has failed.

13. A tangible and non-transitory machine-readable storage medium encoded with instructions for execution by a hardware management device for enabling incremental failure of a hardware system, the hardware system including a hardware module, the hardware module including a circuit board upon which a plurality of hardware components is mounted, the tangible and non-transitory machine-readable storage medium comprising:

instructions for identifying a hardware failure of a failed component of the plurality of hardware components;

instructions for determining a set of agent devices currently configured to utilize the failed component;

instructions for, for at least one agent device of the set of agent devices, reconfiguring the agent device to utilize a working component of the plurality of hardware components in place of the failed component; and

instructions for deactivating the failed component, wherein other hardware components of the plurality of hardware components remain in operation.

14. The tangible and non-transitory machine-readable storage medium of claim 13, instructions for reconfiguring the hardware module to power down the failed component while continuing to provide power to at least one other component of the plurality of hardware components.

15. The tangible and non-transitory machine-readable storage medium of claim 13, wherein all hardware components mounted on the circuit board are of a single type of hardware component.

16. The tangible and non-transitory machine-readable storage medium of claim 13, wherein the hardware management device comprises a hypervisor and wherein the hardware management device utilizes at least one component of the plurality of hardware components to operate.

17. The tangible and non-transitory machine-readable storage medium of claim 13, wherein the hardware management device comprises a cloud computing gateway device and wherein:

the hardware management device manages a plurality of hypervisors; and

a first hypervisor of the plurality of hypervisors manages the plurality of hardware components.

18. The tangible and non-transitory machine-readable storage medium of claim 17, further comprising:

instructions for, for at least one agent device of the set of agent devices, reconfiguring the agent device to be managed by a second hypervisor of the plurality of hypervisors.

19. A method performed by a hardware management device for controlling consumption of a hardware module, the hardware module including a plurality of hardware components, the method comprising:

projecting a failure date for the hardware module;

determining whether the projected failure date is acceptable based on a target replacement date for the hardware module;

if the projected failure date is not acceptable;

determining at least one parameter adjustment for at least one hardware component of the plurality of hardware components, wherein the at least one parameter adjustment is selected to move the projected failure date closer to the target replacement date; and

applying the at least one parameter adjustment to the least one hardware component of the plurality of hardware components.

20. The method of claim 19, wherein the at least one parameter adjustment is selected to cause the hardware module to fail sooner than the projected failure date.

21. The method of claim 19, further comprising:

estimating a current life phase for the module based on a failure rate for each of the plurality of hardware components;

wherein the step of projecting a failure date for the hardware module is performed based on the current life phase of the module.

22. The method of claim 21, wherein the hardware management device manages a plurality of hardware modules and each hardware module is associated with a current life phase, the method further comprising:

receiving a request for establishment of an agent device;

determining a life phase permission associated with the request, wherein the life phase permission indicates that a module having a permitted life phase should be used for fulfilling the request;

selecting a hardware module of the plurality of hardware modules, wherein the selected hardware module is associated with the permitted life phase; and

fulfilling the request using the selected hardware module.

23. The method of claim 19, wherein the step of projecting a failure date for the hardware module comprises projecting a date at which a failure condition will be met, wherein the failure condition is met when less than a configured number of hardware components remain operational.

24. The method of claim 19, further comprising determining a failure rate of at least one of the plurality of hardware components, wherein the step of projecting a failure date for the hardware module is performed based on the failure rate of at least one of the plurality of hardware components.

25. The method of claim 19, wherein the at least one parameter adjustment comprises an adjustment to at least one of the following:

a cooling rate, a voltage, a clock frequency, and an activation schedule.

26. A hardware management device for controlling consumption of a hardware module, the hardware module including a plurality of hardware components, the hardware management device comprising:

a consumption policy engine configured to;

project a failure date for the hardware module, and

determine whether the projected failure date is acceptable based on a target replacement date for the hardware module; and

a parameter adjuster that is configured to, if the projected failure date is not acceptable;

determine at least one parameter adjustment for at least one hardware component of the plurality of hardware components, wherein the at least one parameter adjustment is selected to move the projected failure date closer to the target replacement date, and

apply the at least one parameter adjustment to the at least one hardware component of the plurality of hardware components.

27. The hardware management device of claim 26, wherein parameter adjuster selects a parameter adjustment to cause the hardware module to fail sooner than the projected failure date.

28. The hardware management device of claim 26, further comprising a diagnostic engine that estimates a current life phase for the module based on a failure rate for each of the plurality of hardware components, wherein, the consumption policy engine projects the failure date for the hardware module based on the current life phase of the module.

29. The hardware management device of claim 28, wherein the hardware management device manages a plurality of hardware modules and each hardware module is associated with a current life phase, the hardware management device further comprising:

a request handler configured to;

receive a request for establishment of an agent device;

determine a life phase permission associated with the request, wherein the life phase permission indicates that a module having a permitted life phase should be used for fulfilling the request;

select a hardware module of the plurality of hardware modules, wherein the selected hardware module is associated with the permitted life phase; and

fulfill the request using the selected hardware module.

30. The hardware management device of claim 26, wherein the consumption policy engine projects the failure date for the hardware module by projecting a date at which a failure condition will be met, wherein the failure condition is met when less than a configured number of hardware components remain operational.

31. The hardware management device of claim 26, wherein the at least one parameter adjustment comprises an adjustment to at least one of the following:

a cooling rate, a voltage, a clock frequency, and an activation schedule.

32. A tangible and non-transitory machine-readable storage medium encoded with instructions for execution by a hardware management device for controlling consumption of a hardware module, the hardware module including a plurality of hardware components, the tangible and non-transitory machine-readable storage medium comprising:

instructions for projecting a failure date for the hardware module;

instructions for determining whether the projected failure date is acceptable based on a target replacement date for the hardware module;

instructions for, if the projected failure date is not acceptable;

determining at least one parameter adjustment for at least one hardware component of the plurality of hardware components, wherein the at least one parameter adjustment is selected to move the projected failure date closer to the target replacement date, and

applying the at least one parameter adjustment to the at least one hardware component of the plurality of hardware components.

33. The tangible and non-transitory machine-readable storage medium of claim 32, wherein the at least one parameter adjustment is selected to cause the hardware module to fail sooner than the projected failure date.

34. The tangible and non-transitory machine-readable storage medium of claim 32, further comprising:

instructions for estimating a current life phase for the module based on a failure rate for each of the plurality of hardware components;

wherein the instructions for projecting a failure date for the hardware module operate based on the current life phase of the module.

35. The tangible and non-transitory machine-readable storage medium of claim 34, wherein the hardware management device manages a plurality of hardware modules and each hardware module is associated with a current life phase, the tangible and non-transitory machine-readable storage medium further comprising:

instructions for receiving a request for establishment of an agent device;

instructions for determining a life phase permission associated with the request, wherein the life phase permission indicates that a module having a permitted life phase should be used for fulfilling the request;

instructions for selecting a hardware module of the plurality of hardware modules, wherein the selected hardware module is associated with the permitted life phase; and

instructions for fulfilling the request using the selected hardware module.

36. The tangible and non-transitory machine-readable storage medium of claim 32, wherein the instructions for projecting a failure date for the hardware module comprise instructions for projecting a date at which a failure condition will be met, wherein the failure condition is met when less than a configured number of hardware components remain operational.

37. The tangible and non-transitory machine-readable storage medium of claim 32, further comprising instructions for determining a failure rate of at least one of the plurality of hardware components, wherein the instructions for projecting a failure date for the hardware module operate based on the failure rate of at least one of the plurality of hardware components.

38. The tangible and non-transitory machine-readable storage medium of claim 32, wherein the at least one parameter adjustment comprises an adjustment to at least one of the following:

a cooling rate, a voltage, a clock frequency, and an activation schedule.