EVENT NOTIFICATIONS IN A SHARED INFRASTRUCTURE ENVIRONMENT

• US 20160094359A1
• Filed: 09/25/2014
• Published: 03/31/2016
• 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, Chandresekhar
• Granted Patent: US 9,780,960 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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, and where the subscription is associated with a component;

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

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

sending the component update, via the management fabric, to the identified event client modules.

2. The method of claim 1, further comprising receiving node information from each of the plurality of event client modules.

3. The method of claim 2, where the node information comprises a firmware version for each component attached to a corresponding node of the plurality of nodes.

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

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

6. The method of claim 1, further comprising monitoring a plurality of 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.

7. 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.

8. 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 component;

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

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

sending the component update, via the management fabric, to the identified event client modules.

9. The at least one computer storage device of claim 8, the actions further comprising receiving node information from each of the plurality of event client modules.

10. The at least one computer storage device of claim 9, where the node information comprises a firmware version for each component attached to a corresponding node of the plurality of nodes.

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

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

13. The at least one computer storage device of claim 8, the actions further comprising monitoring a plurality of 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.

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

15. 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 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, and where the subscription is associated with a component;

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

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

sending the component update, via the management fabric, to the identified event client modules.

16. The system of claim 15, the actions further comprising receiving node information from each of the plurality of event client modules.

17. The system of claim 16, where the node information comprises a firmware version for each component attached to a corresponding node of the plurality of nodes.

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

19. The system of claim 15, the actions further comprising updating a central data manager with the component update.

20. The system of claim 15, the actions further comprising monitoring a plurality of 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.