Method and apparatus for controlling process dependencies

• US 7,376,951 B1
• Filed: 09/06/2002
• Issued: 05/20/2008
• Est. Priority Date: 09/06/2002
• Status: Active Grant

• Current Assignee: Extreme Networks, Inc.
• Original Assignee: Extreme Networks, Inc.
• Inventors: Berenberg, Anna, Yip, Michael
• Primary Examiner(s): An, Meng-Al T.
• Assistant Examiner(s): Tang, Kenneth
• Application Number:
  US10/236,403
• Time in Patent Office: 2,083 Days
• Field of Search: 718/102, 718/100
• US Class Current: 718/102
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine

Abstract

A method and system is provided to control and check run-time process dependencies. When a process manager receives a request to start a new process, the process manager accesses a configuration file to check if the new process depends on any other processes to be running and what versions of these prerequisite processes are required. If an exact version is specified in the configuration file, the prerequisite process version must match the exact version specified to be compatible with the new process. If a range of acceptable versions is specified in the configuration file, the prerequisite process version must fall within the range of acceptable versions to be compatible with the new process. If a minimum acceptable version is specified in the configuration file, then the prerequisite process version must be greater than or equal to the minimum acceptable version specified. If a maximum acceptable version is specified in the configuration file, then the prerequisite process version must be less than or equal to the maximum acceptable version specified. If the prerequisite processes are not running or the versions of the running prerequisite processes are not compatible with the new process, then the new process is not started. If the new process does not depend on any processes or all the prerequisite are running with compatible versions, then the new process may be started.

Claims

1. A method for starting a dependent process in a network device, comprising:

starting one or more processes in the network device;

registering the one or more processes with a process manager running in the network device;

receiving, after the one or more processes are running in the network device, a request to start a second process in the network device;

accessing a configuration file to determine if the second process is dependent on one or more prerequisite processes that must be running before the second process can be started, the configuration file further identifying a version of each prerequisite process required by the dependent process;

if there is a prerequisite process of the second process defined in the configuration file, comparing the one or more prerequisite processes with the one or more registered running processes to determine if each of the one or more prerequisite processes is running in the network device and whether the second process is compatible with the version identifier of each of the one or more running prerequisite processes; and

starting the second process only if every prerequisite process of the second process is running and the second process is compatible with the version identifier of each of the one or more running prerequisite processes.

2. The method of claim 1, wherein the configuration file is accessed by the process manager and contains one or more dependency entries for a dependent process, each dependency entry defining the prerequisite process of the dependent process and the version of the prerequisite process required by the dependent process.

3. The method of claim 2, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be an exact match of a particular version.

4. The method of claim 2, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be within a range of acceptable versions.

5. The method of claim 2, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be greater than or equal to a minimum acceptable version.

6. The method of claim 2, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be less than or equal to a maximum acceptable version.

7. The method of claim 1, wherein the network device is a router and the second process is a route manager application process to be run on the active Router Protocol (RP).

8. A system for controlling process dependency in a network device comprising:

a process manager to be run in the network device;

one or more processes to be started in the network device and to be registered with the process manager;

a second process to be run in the network device after the one or more processes are running in the network device;

data in a configuration file identifying the second process as dependent on one or more prerequisite processes that must be running before the second process can be started the data also identifying a version of each prerequisite process required by the dependent process; and

a processor to compare the data in the configuration file with the one or more running processes registered with the process manager to determine if each of the one or more prerequisite processes is running in the network device and that the second process is compatible with the version identifier of each of the one or more running prerequisite processes, and to start the second process only after determining that every prerequisite processes is running and each is of a compatible version.

9. The system of claim 8, wherein the configuration file is accessed by the process manager and the data contains one or more dependency entries for a dependent process, each dependency entry defining the prerequisite process of the dependent process and defining the version of the prerequisite process required by the dependent process.

10. The system of claim 8, wherein each of the one or more prerequisite processes is compatible with the second process if the prerequisite process version registered with the process manager matches the version identifier defined by the configuration file data.

11. The system of claim 8, wherein the version identifier specifies an earliest acceptable version and wherein the second process is compatible with each of the one or more prerequisite processes if the version of each prerequisite process registered with the process manager matches or is later than the earliest acceptable version specified.

12. The system of claim 8, wherein the version identifier specifies a latest acceptable version and wherein the second process is compatible with each of the one or more prerequisite processes if the version of each prerequisite process registered with the process manager matches or is earlier than the latest acceptable version specified.

13. The system of claim 8, wherein the version identifier specifies a range of acceptable versions and wherein the second process is compatible with each of the one or more prerequisite processes if the version of each prerequisite process registered with the process manager falls within the range of acceptable versions specified.

14. The system of claim 8, wherein the network device is a router and the second process is a route manager application process to be run on the active Router Protocol (RP).

15. A computer-readable storage media with instruction stored thereon, which when executed, causes a computer to perform the method comprising:

starting one or more processes in the network device;

registering the one or more processes with a process manager running in the network device;

receiving, after the one or more processes are running in the network device, a request to start a second process in the network device;

accessing a configuration file to determine if the second process is dependent on one or more prerequisite processes that must be running before the second process can be started, the configuration file further identifying a version of each prerequisite process required by the dependent process;

if there is a prerequisite process of the second process defined in the configuration file, comparing the one or more prerequisite processes with the one or more registered running processes to determine if each of the one or more prerequisite processes is running in the network device and whether the second process is compatible with the version identifier of each of the one or more running prerequisite processes; and

starting the second process only if every prerequisite process of the second process is running and the second process is compatible with the version identifier of each of the one or more running prerequisite processes.

16. The media of claim 15, wherein the configuration file is accessed by the process manager and contains one or more dependency entries for a dependent process, each dependency entry defining the prerequisite process of the dependent process and defining the version of the prerequisite process required by the dependent process.

17. The media of claim 15, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be an exact match of a particular version.

18. The media of claim 15, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be within a range of acceptable versions.

19. The media of claim 15, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be greater than or equal to a minimum acceptable version.

20. The media of claim 15, wherein determining whether the second process is compatible with the version identification of each of the one or more prerequisite processes comprises:

obtaining, from the configuration file, a version requirement of the second process for each prerequisite process;

comparing the version requirement for each prerequisite process to the version identifier registered by each prerequisite process; and

determining whether the version identifier registered by each prerequisite process satisfies the version requirement of the second process, wherein the version requirement is that the prerequisite process be less than or equal to a maximum acceptable version.