Software change modeling for network devices

Abstract

A method for software change modeling for network devices provides dynamic (on the device) and static (computer) change modeling. The same source code and libraries are used for both modeling applications, allowing a user to see the impact of activating or deactivating specific software modules without affecting the actual node. A master node passes a node the identity of the software package(s) to be updated and the dependencies. The node notifies its running processes about the update. If any of the processes determine that the update will degrade or have a negative impact on the operation of the node, it returns a veto to the node which sends a list of the processes that are impacted along with the reasons why to the master node.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS[0001]This application is a continuation of U.S. patent application Ser. No. 10 / 727,099 filed Dec. 2, 2003 which is incorporated herein by reference as if fully set forth herein, under 35 U.S.C. §120.FIELD OF THE INVENTION[0002]The present invention generally relates to the management, loading, and installation of select software modules onto networked nodes. The invention relates more specifically to a method and apparatus for the modeling of software packages for a distributed networking device.BACKGROUND OF THE INVENTION[0003]The approaches described in this section could be pursued, but are not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, the approaches described in this section are not prior art to the claims in this application and are not admitted to be prior art by inclusion in this section.[0004]Networked computer systems have evolved over the years from simple ser...

AI Technical Summary

Problems solved by technology

The issue of how a computer system obtains its operating software and the effects upon the overall networked system by the loading of new operating software on the computer system has been a complex and perplexing problem.

This requires that all processes on the computer be halted and restarted, thereby interrupting any tasks that the computer may be performing.

However, if a multi-node system is purposed to perform an uninterruptible operation, such as managing telecommunications links, the restarting of a computer is not acceptable because a telecommunications link will be disturbed.

The computer must also be running an operational version of Windows to be able to communicate with the server, therefore, a new computer is useless until a copy of Windows is installed by a user.

Further, the reliance on a human being to perform software selection and initiate software downloads is not desirable in stand-alone systems.

This approach worked well for homogeneous systems, but could not work with heterogeneous systems.

However, the drawback to this approach is that it requires that an identical program be distributed to all of the networked computers and it does not contemplate the problems associated with a heterogeneous set of computers that require individual software component updates, nor the management of such components.

Images