Management of a multi-process system

• US 8,140,653 B1
• Filed: 06/25/2004
• Issued: 03/20/2012
• Est. Priority Date: 06/25/2004
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: McCullough, Gary, Hamilton, Kevin, Croy, Timothy
• Primary Examiner(s): Pwu, Jeffrey
• Assistant Examiner(s): Sciacca, Scott M
• Application Number:
  US10/876,908
• Time in Patent Office: 2,825 Days
• Field of Search: 709220-226
• US Class Current: 709/223
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A system comprising a network of network elements and a data store associated with a data store manager. The data store contains data representing the actual state of the system and data representing a planned state of the system. The data store manager causes the network elements, or processes supported thereby, to conform with the planned system state. In addition, at least some of the processes communicate to the data store manager data representing their respective state. The data store manager, upon receipt of said data, updates the actual state data in accordance with the received data. The data store provides an actual model and a planned model of the system by which the state of the system can readily be managed.

Claims

1. A system comprising a network of network elements, each network element supporting at least one respective process, the network further comprising a data store associated with a data store manager, wherein the data store maintains a first model of said system, said first model representing an actual state of the system and including data identifying each of said network elements and each of said at least one respective processes that is instantiated on respective network elements, said first model further including data representing the actual state of said at least one respective process, and wherein the data store maintains a second model of said system, said second model being independent of said first model and representing a planned state of the system, said second model including data identifying each of said network elements and, in respect of each network element, at least one of said at least one respective processes that is planned to be instantiated on the respective network element, the data store manager being arranged to cause the respective network elements to instantiate each respective process that said second model identifies as being planned to be instantiated on the respective network element but is not yet instantiated on the respective network element, and at least some of said processes being arranged to communicate to said data store manager data representing their respective state, the data store manager, upon receipt of said data from said at least some processes, being arranged to update said first model in accordance with said received data, wherein the data store manager is arranged to perform a persistent search of the data store based on respective search criteria provided by one or more of said processes.

2. A system as claim in claim 1, wherein said data store contains a first data set data comprising data representing said first model of said system and a second data set representing said second model of said system.

3. A system as claimed in claim 1, wherein the data store manager is arranged to select said second model from a plurality of different second models.

4. A system as claimed in claim 1, wherein at least some of said processes are arranged to register with the data store manager an indication of one or more changes in said actual state in respect of which they are to be notified, the data store manager, upon detection of one or more of said changes in said actual state, being arranged to notify the or each process that has registered in respect of the or each detected state change.

5. A system as claimed in claim 4, wherein the data store manager monitors said first model of the system to detect changes in said actual state.

6. A system as claimed in claim 1, wherein the data store includes data representing one or more permitted states of said at least one respective process.

7. A system as claimed in claim 6, wherein the data store manager, upon receiving data representing a change in said actual state, determines from said permitted state data if said change in state is permitted and, upon determining that said change in state is permitted, updates said first model in respect of said change in state.

8. A system as claimed in claim 6, wherein the data store includes data representing one or more respective processes that are permitted to run on each network element.

9. A system as claimed in claim 8, wherein the data store manager, upon receiving data indicating that a new process has been instantiated, determines from said permitted process data if said new process is permitted and, upon determining that said new process is permitted, updates said first model in respect of said new process.

10. A system as claimed in claim 9, wherein the data store manager, upon determining that said new process is not permitted, causes said new process to be terminated.

11. A system as claimed in claim 1, wherein at least some of said network elements include a respective process manager arranged to receive data from said store manager representing the planned state of the respective network element and, upon receiving said planned state data, to cause said network element to adopt said planned state.

12. A system as claimed in claim 11, wherein said respective process manager is arranged to receive data from said store manager representing one or more planned processes and, upon receiving said planned state data, to cause the or each planned process to be instantiated on the respective network element.

13. A system as claimed in claim 1, wherein at least some of said network elements include a respective process manager arranged to detect the instantiation of processes on the respective network element and to report detected instantiations to said data store manager.

14. A method of managing a system comprising a network of network elements, each network element supporting at least one respective process, the network further comprising a data store associated with a data store manager, wherein the method comprises:

maintaining, in said data store, a first model of said system, said first model representing an actual state of the system and including data identifying each of said network elements and each of said at least one respective processes that is instantiated on respective network elements, said first model further including data representing the actual state of said at least one respective process; and

maintaining, in the data store, a second model of said system, said second model being independent of said first model and representing a planned state of the system, said second model including data identifying each of said network elements and, in respect of each network element, at least one of said at least one respective processes that is planned to be instantiated on the respective network element, the method further comprising causing said the respective network elements to instantiate each respective process that said second model identifies as being planned to be instantiated on the respective network element but is not yet instantiated on the respective network element, and updating said first model in accordance with data provided by at least some of said processes representing their respective state, wherein the data store manager is arranged to perform a persistent search of the data store based on respective search criteria provided by one or more of said processes.

15. A method as claimed in claim 14, comprising selecting said second model from a plurality of different second models.

16. A method as claimed in claim 14, comprising registering with the data store manager, in respect of at least some of said processes, an indication of one or more changes in said actual state in respect of which the respective processes are to be notified, and, upon detection of one or more of said changes in said actual state, notifying the or each respective process.

17. A method as claimed in claim 16, comprising monitoring said first model to detect changes in said actual state.

18. A method as claimed in claim 14, wherein the data store includes data representing one or more permitted states of said at least one respective process, the method comprising, upon receiving data representing a change in said actual state, determining from said permitted state data if said change in state is permitted and, upon determining that said change in state is permitted, updating said first model in respect of said change in state.

19. A method as claimed in claim 18, wherein the data store includes data representing one or more respective processes that are permitted to run on each network element, the method comprising, upon receiving data indicating that a new process has been instantiated, determining from said permitted process data if said new process is permitted and, upon determining that said new process is permitted, updating said first model in respect of said new process.

20. A method as claimed in claim 19, comprising causing said new process to be terminated upon determining that said new process is not permitted.

21. A method as claimed in claim 14, wherein at least some of said network elements include a respective process manager, the method including receiving, at a respective process manager, data from said store manager representing the planned state of the respective network element and, upon receiving said planned state data, causing said network element to adopt said planned state.

22. A method as claimed in claim 21, comprising receiving, at a respective process manager, data from said store manager representing one or more planned processes and, upon receiving said planned state data, causing the or each planned process to be instantiated on the respective network element.

23. A method as claimed in claim 14, comprising detecting the instantiation of processes on a respective network element and reporting detected instantiations to said data store manager.

24. A computer program product implemented in a non-transitory computer readable medium comprising computer usable instructions for causing a computer to perform the method of claim 14.

25. A data store manager for use in a system comprising a network of network elements, the data store manager including computer usable instructions implemented in a non-transitory computer readable medium, each network element supporting at least one respective process, the data store manager being associated with a data store, wherein the data store maintains a first model of said system, said first model representing an actual state of the system and including data identifying each of said network elements and each of said at least one respective processes that is instantiated on respective network elements, said first model further including data representing the actual state of said at least one respective process, and wherein the data store maintains a second model of said system, said second model being independent of said first model and representing a planned state of the system, said second model including data identifying each of said network elements and, in respect of each network element, at least one of said at least one respective processes that is planned to be instantiated on the respective network element, the data store manager being arranged to cause said the respective network elements to instantiate each respective process that said second model identifies as being planned to be instantiated on the respective network element but is not yet instantiated on the respective network element, and at least some of said processes being arranged to communicate to said data store manager data representing their respective state, the data store manager, upon receipt of said data from said at least some processes, being arranged to update said first model in accordance with said received data, wherein the data store manager is arranged to perform a persistent search of the data store based on respective search criteria provided by one or more of said processes.

26. A data store manager as claim in claim 25, wherein the data store manager is arranged to select said second model from a plurality of different second models.

27. A data store manager as claimed in claim 25, wherein at least some of said processes are arranged to register with the data store manager an indication of one or more changes in said actual state in respect of which they are to be notified, the data store manager, upon detection of one or more of said changes in the actual state, being arranged to notify the or each process that has registered in respect of the or each detected state change.

28. A data store manager as claimed in claim 27, wherein the data store manager monitors said first model to detect changes in the actual state.

29. A data store manager as claimed in claim 25, wherein the data store includes data representing one or more permitted states of said at least one respective process, and wherein the data store manager, upon receiving data representing a change in said actual state, determines from said permitted state data if said change in state is permitted and, upon determining that said change in state is permitted, updates said first model in respect of said change in state.

30. A data store manager as claimed in claim 29, wherein the data store includes data representing one or more respective processes that are permitted to run on each network element, and wherein the data store manager, upon receiving data indicating that a new process has been instantiated, determines from said permitted process data if said new process is permitted and, upon determining that said new process is permitted, updates said first model in respect of said new process.

31. A data store manager as claimed in claim 30, wherein the data store manager, upon determining that said new process is not permitted, causes said new process to be terminated.

32. A system comprising a network of network elements, each network element supporting at least one respective process, the network further comprising a data store associated with a data store manager, wherein the data store maintains a first model of said system, said first model representing, an actual state of the system and including data identifying each of said network elements and each of said at least one respective processes that is instantiated on respective network elements, said first model further including data representing the actual state of said at least one respective process, and wherein the data store maintains a second model of said system, said second model being independent of said first model and representing a planned state of the system, said second model including planned process data identifying each of said network elements and, in respect of each network element, at least one of said at least one respective processes that is planned to be instantiated on the respective network element, the data store manager being arranged to cause the respective network elements to instantiate each respective process that said second model identifies as being planned to be instantiated on the respective network element but is not yet instantiated on the respective network element, and at least some of said processes being arranged to communicate to said data store manager data representing their respective state, the data store manager, upon receipt of said data from said at least some processes, being arranged to update said first model in accordance with said received data, and wherein in addition to said planned process data, said second model includes, in respect of at least some of said network elements, permitted process data identifying one or more respective processes, other than said planned processes, that are permitted to run on the respective network element, and wherein, the data store manager, upon receiving data indicating that a non-planned process has been instantiated on any one of said network elements, is configured to determine from the respective permitted process data of said second model if said non-planned process is permitted and, upon determining that said non-planned process is permitted, to update said first model in respect of said non-planned process and, upon determining that said non-planned process is not permitted, to cause said new process to be terminated, wherein the data store manager is arranged to perform a persistent search of the data store based on respective search criteria provided by one or more of said processes.