Event notifications in a shared infrastructure environment

• US 9,780,960 B2
• Filed: 09/25/2014
• Issued: 10/03/2017
• Est. Priority Date: 09/25/2014
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Bidaralli, Santosh Kumar, Kulkarni, Yogesh Prabhakar, Krishna Bangera, Lokesh, Mugunda, Chandrasekhar
• Primary Examiner(s): Lazaro, David
• Assistant Examiner(s): SHITAYEWOLDETADIK, BERHANU
• Application Number:
  US14/497,303
• Publication Number:
  US 20160094359A1
• Time in Patent Office: 1,104 Days
• Field of Search: 709224-245
• CPC Class Codes: H04L 12/1895 for short real-time information, e.g. alarms, notifications, alerts, updates
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

A shared infrastructure environment system is provided that includes a capability to notify individual nodes of notifications, events, and alerts. The system receives, via a management fabric, a subscription from an event client module for information associated with a component. The system also receives a component update associated with the component. The system identifies if any event client module operating on any node has subscribed to receive component updates associated with the component, and sends the component update, via the management fabric, to the identified event client modules.

Claims

1. A method performed on a computing device having a processor and memory, the method comprising:

receiving, via a management fabric and at an event server module executing on the computing device, a subscription from at least one of a plurality of event client modules, where each of the plurality of event client modules corresponds to one of a plurality of nodes, where the subscription is associated with a hardware component, and where the management fabric comprises an out-of-band communication channel communicated over a second network interface separate from an in-band communication channel communicated over a first network interface;

receiving, via the management fabric and at the event server module, a hardware component update from at least one of the plurality of event client modules, where the hardware component update is associated with the hardware component;

identifying event client modules of the plurality of event client modules that have subscribed to receive hardware component updates associated with the hardware component;

sending the hardware component update, via the management fabric, to the identified event client modules through the out-of-band communication channel; and

receiving node information from each of the plurality of event client modules, wherein the node information comprises a firmware version for each hardware component attached to a corresponding node of the plurality of nodes, and wherein at least one of the steps of receiving a hardware component update and sending the hardware component update is performed while the node corresponding to the event client module receiving or sending the hardware component update is in a powered down or standby state.

2. The method of claim 1, further comprising maintaining a list of subscriptions from the plurality of nodes.

3. The method of claim 1, further comprising updating a central data manager with the hardware component update.

4. The method of claim 1, further comprising monitoring a plurality of hardware components for a change in operating mode, where the change in operating mode comprises at least one of a firmware update, a power status update, or a service degradation update, and where the hardware component update comprises information detailing the change in operating mode.

5. The method of claim 1, where the event server module is an asynchronous messaging server configured for many-to-many connections with the plurality of event client modules.

6. At least one computer storage device storing computer-executable instructions that, when executed by a computing device that includes a processor and a memory, cause the computing device to perform actions comprising:

receiving, via a management fabric and at an event server module executing on the computing device, a subscription from at least one of a plurality of event client modules, where each of the plurality of event client modules corresponds to one of a plurality of nodes, and where the subscription is associated with a hardware component, where the management fabric comprises an out-of-band communication channel communicated over a second network interface separate from an in-band communication channel communicated over a first network interface;

receiving, via the management fabric and at the event server module, a hardware component update from at least one of the plurality of event client modules, where the hardware component update is associated with the hardware component;

identifying event client modules of the plurality of event client modules that have subscribed to receive hardware component updates associated with the hardware component;

sending the hardware component update, via the management fabric, to the identified event client modules through the out-of-band communication channel; and

receiving node information from each of the plurality of event client modules, wherein the node information comprises a firmware version for each hardware component attached to a corresponding node of the plurality of nodes, and wherein at least one of the steps of receiving a hardware component update and sending the hardware component update is performed while the node corresponding to the event client module receiving or sending the hardware component update is in a powered down or standby state.

7. The at least one computer storage device of claim 6, the actions further comprising maintaining a list of subscriptions from the plurality of nodes.

8. The at least one computer storage device of claim 6, the actions further comprising updating a central data manager with the hardware component update.

9. The at least one computer storage device of claim 6, the actions further comprising monitoring a plurality of hardware components for a change in operating mode, where the change in operating mode comprises at least one of a firmware update, a power status update, or a service degradation update, and where the hardware component update comprises information detailing the change in operating mode.

10. The at least one computer storage device of claim 6, where the event server module is an asynchronous messaging server configured for many-to-many connections with the plurality of event client modules.

11. A system comprising at least one computing device and at least one software module that are together configured for performing actions, where the computing device includes a processor, a first network interface, a second network interface, and a memory, the actions comprising:

receiving, via a management fabric and at an event server module executing on the computing device, a subscription from at least one of a plurality of event client modules, where each of the plurality of event client modules corresponds to one of a plurality of nodes, where the subscription is associated with a hardware component, and where the management fabric comprises an out-of-band communication channel communicated over the second network interface separate from an in-band communication channel communicated over the first network interface;

receiving, via the management fabric and at the event server module, a hardware component update from at least one of the plurality of event client modules, where the hardware component update is associated with the hardware component;

identifying event client modules of the plurality of event client modules that have subscribed to receive hardware component updates associated with the hardware component;

sending the hardware component update, via the management fabric, to the identified event client modules through the out-of-band communication channel; and

receiving node information from each of the plurality of event client modules, wherein the node information comprises a firmware version for each hardware component attached to a corresponding node of the plurality of nodes, and wherein at least one of the steps of receiving a hardware component update and sending the hardware component update is performed while the node corresponding to the event client module receiving or sending the hardware component update is in a powered down or standby state.

12. The system of claim 11, the actions further comprising maintaining a list of subscriptions from the plurality of nodes.

13. The system of claim 11, the actions further comprising updating a central data manager with the hardware component update.

14. The system of claim 11, the actions further comprising monitoring a plurality of hardware components for a change in operating mode, where the change in operating mode comprises at least one of a firmware update, a power status update, or a service degradation update.