Managing a network of computer systems using a version identifier generated based on software packages installed on the computing systems

FIELD

This invention relates generally to computer software installation for computing systems and network management.

DESCRIPTION OF THE RELATED ART

Today, a person using a computing system has a variety of avenues for obtaining software and installing the software on the computing system, such as purchasing physical media and downloading the software over a network. When downloading the software over a network, the person can acquire and install the software using a software package management system. The software package management system typically consists of a software repository which stores and maintains various software packages. The software packages typically consist of software stored in an archive format that includes data for installing the software.

To obtain the software package, the person can utilize a package manager. The package manager is responsible for retrieving the software package and installing the software package on the computing system. Typically, the package manager maintains a record of how the software package was installed. However, the user of the computing system or an administrator overseeing the computing system cannot easily determine if the correct software package is installed on the computing system. For example, if the administrator is overseeing a large network of computing system, the administrator may desire to maintain the same software packages on all the computing systems. Typically, the administrator must examine each software package on each computing system to determine if the correct packages are installed. Moreover, a user of the computing system may desire to update the software packages. The user, however, lacks the ability to determine if the update will properly install on the system, for example, due to changes in the software packages since the last update.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features of the embodiments can be more fully appreciated, as the same become better understood with reference to the following detailed description of the embodiments when considered in connection with the accompanying figures, in which:

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary software package delivery and management system including an administrator system, in which various embodiments of the present teachings can be practiced;

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary process for generating a version identifier, according to various embodiments;

<figref idref="DRAWINGS">FIG. 3</figref> illustrates another exemplary software package delivery and management system including the administrator system, according to various embodiments;

<figref idref="DRAWINGS">FIG. 4</figref> illustrates an exemplary hardware configuration for an administrator system, according to various embodiments; and

<figref idref="DRAWINGS">FIGS. 5A and 5B</figref> illustrate flowcharts of exemplary processes for managing a network of computing systems utilizing a version identifier, according to various embodiments.

DETAILED DESCRIPTION OF EMBODIMENTS

For simplicity and illustrative purposes, the principles of the present teachings are described by referring mainly to exemplary embodiments thereof. However, one of ordinary skill in the art would readily recognize that the same principles are equally applicable to, and can be implemented in, all types of information and systems, and that any such variations do not depart from the true spirit and scope of the present teachings. Moreover, in the following detailed description, references are made to the accompanying figures, which illustrate specific embodiments. Electrical, mechanical, logical and structural changes may be made to the embodiments without departing from the spirit and scope of the present teachings. The following detailed description is, therefore, not to be taken in a limiting sense and the scope of the present teachings is defined by the appended claims and their equivalents.

Embodiments of the present teachings relate to systems and methods for managing computing systems and software packages installed on the computing systems. More particularly, an administrator system can utilize a version identifier for the computing systems in order to track the software packages installed on the computing systems.

According to embodiments, an administrator system can be configured to generate a version identifier for a computing system based on the software packages installed on a computing system. The version identifier can be generated to represent the software packages installed on the computing system. In particular, the administrator system can be configured to include a version tool to generate the version identifier. The version tool can be configured to identify the software packages installed on the computing system and data specific to the software packages. For example, the specific data can include a name of the software package, an epoch of the software package, a version of the software package, a release of the software package, an arch of the software package, a checksum of the software package, and a format of the checksum. The version tool can be configured to identify the software packages and specific data by communicating with a package manager installed on the computing system.

According to embodiments, once the software packages and specific data are identified, the version tool can be configured to order the software packages and/or the specific data. The version tool can be configured to order the specific data based on an any ordering algorithm, such as alphabetically based on the name of the software packages, hierarchically based on the type of specific data, etc. Once ordered, the version tool can be configured to apply a hash function to the specific data to generate hashed data. The version tool can be configured to utilize any type of hash function to generate hashed data, for example, Secure Hash Algorithm (SHA1, SHA2, etc.).

According to embodiments, once the hashed data is generated, the version tool can be configured to concentrate the hashed data to generate the version identifier. In particular, the version tool can be configured to concentrate the hashed data according to the ordering of the software packages and/or ordering of the specific data. Once generated, the version tool can be configured to store the version identifier and/or provide the version identifier to the computing system.

According to embodiments, the administrator system can utilize the version identifier for a variety of tasks. For example, the administrator system can compare the version identifier of the computing system to version identifier of other computing systems to determine if the software packages installed on the computing system match the software packages installed on the other computing systems. Additionally, the administrator system can utilize the version identifier to determine if updates to the software packages on the computing system will install properly.

By utilizing the version tool, the administrator system can generate a version identifier that represents the software packages installed on the computing system. As such, the administrator system can quickly and efficiently identify the software packages installed on a computing system without having to individually examine each software package on the computing system. Likewise, the administrator system can quickly and efficiently confirm that a group of computing systems have the same software packages installed.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a software package delivery and management system <b>100</b>, according to various embodiments of the present teachings. While <figref idref="DRAWINGS">FIG. 1</figref> illustrates various components that can be included in the software package delivery and management system <b>100</b>, one skilled in the art will realize that additional components can be added or existing components can be removed.

In embodiments, as illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, the software package delivery and management system <b>100</b> can be designed to allow a computing system <b>102</b> to communicate with a software repository <b>104</b>, via one or more networks <b>106</b>, in order to obtain and install one or more software packages <b>108</b>. The software repository <b>104</b> can be implemented as any type of open-source or proprietary software repository, which can store the software packages <b>108</b> and provide the software packages to computing systems, such as the computing system <b>102</b>, requesting the software packages via the one or more networks <b>106</b>. For example, the software repository <b>104</b> can be implemented as a Yum repository, Debian™ repository, or any other type of conventional software repository.

In embodiments, as described herein, the software packages <b>108</b>, can include one or more software programs that are packaged together in a format that allows a package manger or package installer to install the software programs, contained in the software packages <b>108</b>, on the computing system <b>102</b>. The software programs included in the software packages <b>108</b> can be any type of software programs such as operating systems (OS), application programs, and the like. The software packages <b>108</b> can also include metadata that describes the software package, such as the name of the software package, the software programs included in the package, epoch, version, release and arch of the software package, description of the purpose of the software package, etc. The software packages <b>108</b> can also include metadata that aids in the installation of the software programs contained in the software packages <b>108</b>, such as checksums, format of the checksums, and a list of dependencies of the software package. The checksums verify the integrity of the files of the software packages <b>108</b> e.g. that the files of the software packages <b>108</b> are complete and correct. The list of dependencies can describe the relationship of the software programs contained in the software packages <b>108</b> and any other software programs, file, software libraries, etc. required by the software packages <b>108</b>.

In embodiments, the software repository <b>104</b> can store the software packages <b>108</b> in any type of open-source or proprietary format depending on the type of software repository <b>104</b>. For example, the software packages <b>108</b> can be in conventional formats such as RPM format for a Yum repository, .deb format for a Debian™ repository, or other conventional formats.

In embodiments, the software package delivery and management system <b>100</b> can also include one or more software repository mirrors <b>109</b>, coupled to the network <b>106</b>. The software repository mirrors <b>109</b> can be configured to maintain copies of the software packages <b>108</b>. The software repository mirrors <b>109</b> can be configured to backup the software repository <b>104</b>. For example, the software repository mirrors <b>109</b> can provide the software packages <b>108</b> to computing systems, such as computing system <b>102</b>, in the event that the software repository <b>104</b> is unavailable or the software repository <b>104</b> is experiencing high traffic.

In embodiments, the software repository <b>104</b> and the software repository mirrors <b>109</b> can be supported by any type of computing system capable of storing the software packages <b>108</b>, capable of communicating with the one or more networks <b>106</b>, and capable of running a repository application for cooperating with a package manager or package installer in order to deliver the software packages <b>108</b>. For example, the software repository <b>104</b> and the software repository mirrors <b>109</b> can be supported by conventional computing systems or other devices such as such as servers, personal computers, laptop computers, network-enabled media devices, networked stations, etc. As such, the computing system supporting the software repository <b>104</b> and the software repository mirrors <b>109</b> can include conventional hardware such as processors, memory, computer readable storage media and devices (CD, DVD, hard drive, portable storage memory, etc.), network devices, and the like.

In embodiments, the one or more networks <b>106</b> can be or include the Internet, or other public or private networks. The one or more networks <b>106</b> can be or include wired, wireless, optical, and other network connections. One skilled in the art will realize that the one or more networks <b>106</b> can be any type of network, utilizing any type of communication protocol, to connect computing systems.

In embodiments, the computing system <b>102</b> can be any type of conventional computing system or other device such as such as servers, personal computers, laptop computers, network-enabled media devices, networked stations, etc. As such, the computing system <b>102</b> can include conventional hardware such as processors, memory, computer readable storage media and devices (CD, DVD, hard drive, portable storage memory, etc.), network devices, and the like.

In embodiments, the computing system <b>102</b> can be configured to include a package manager <b>110</b>. The package manager <b>110</b> can be configured to cooperate with the software repository <b>104</b> to perform various actions associated with the software packages <b>108</b>. For example, the package manager <b>110</b> can be configured to retrieve one or more of the software packages <b>108</b> and configured to install the software packages on the computing system <b>102</b>. Likewise, the package manager <b>110</b> can be configured to retrieve updates to software packages <b>108</b>, already installed on the computing system <b>102</b>, and install the updates on the computing system <b>102</b>.

In embodiments, the package manager <b>110</b> can be configured to cooperate with manager tools <b>112</b> to perform actions related to the software packages <b>108</b>. For example, the manager tools <b>112</b> can be configured to install and update particular application programs, files, or software libraries maintained by the software repository <b>104</b>. As such, the manager tool <b>112</b> can be configured to provide a request to the package manager <b>110</b> to perform the installation or update.

In embodiments, the package manager <b>110</b> can be configured to allow a user of the computing system <b>102</b> to request the various actions associated with the software repository <b>104</b> to be performed. To achieve this, the package manager <b>110</b> can be configured to provide command line or graphical user interfaces (GUIs) that allow the user to direct the package manager <b>110</b> to perform the actions. For example, the package manager <b>110</b> can provide GUIs that display the software packages <b>108</b>, such as new software packages and software package updates, available in the software repository <b>104</b> and that allow the user to select the action to be performed related to the software packages <b>108</b>.

In embodiments, in order to perform the various actions, the package manager <b>110</b> can be configured to communicate with the software repository <b>104</b> and retrieve data from the software repository <b>104</b>. For example, when providing the GUIs to a user of the computing system <b>102</b>, the package manager <b>110</b> can retrieve a list of the software packages <b>108</b> from the software repository <b>104</b>. Likewise, for example, when installing or updating a particular software package <b>108</b>, the package manager <b>110</b> can retrieve the particular software package <b>108</b> and any other data associated with the particular software package <b>108</b>.

In embodiments, when performing the various actions, the package manager <b>110</b> can be configured to utilize the metadata associated with the software packages <b>108</b> in order to perform the actions. For example, when installing a particular software package <b>108</b> or updating a particular software package <b>108</b>, the package manager <b>110</b> can access the metadata associated with the particular software packages <b>108</b> in order to properly install or update the software packages on the computing system <b>102</b>. For instance, the package manager <b>110</b> can utilize the checksums and the list of dependencies in the metadata in order to identify and verify the software programs, files, and software libraries that are affected. Additionally, when performing the various actions, the package manager <b>110</b> can be configured to store the metadata in a database <b>114</b>.

In embodiments, the package manager <b>110</b> can be any application program that is capable of executing on the computing system <b>102</b> to perform the actions related to the software repository <b>104</b>. For example, the package manager <b>110</b> can be any type of conventional open-source or proprietary package manager such as Yum package manager, Debian™ package manager, and the like. The package manager <b>110</b> can be stored on computer readable storage devices or media (CD, DVD, hard drive, portable storage memory, etc.) of the computing system <b>102</b> and executed by the computing system <b>102</b>.

In embodiments, the software package delivery and management system <b>100</b> can also include an administrator system <b>116</b>. The administrator system <b>116</b> can be configured to manage the software repository <b>104</b>, software repository mirrors <b>109</b>, and/or the computing system <b>102</b> via the network <b>106</b>. For example, the administrator system <b>116</b> can be configured to manage the software repository <b>104</b> and/or software repository mirrors <b>109</b> and provide support to the computing system <b>102</b> when installing the software packages <b>108</b>. Likewise, for example, the administrator system <b>116</b> can be configured to manage the computing system <b>102</b> to ensure that the computing system <b>102</b> is properly configured and that the correct software packages <b>108</b> are installed on the computing system <b>102</b>.

In embodiments, the administrator system <b>116</b> can be any type of computing system or other device such as such as a server, personal computer, laptop computer, network-enabled media device, networked station, etc. The administrator system <b>116</b> can be coupled to the one or more networks <b>106</b> in order to communicate with the computing systems <b>102</b>, the software repository <b>104</b>, and the software repository mirrors <b>109</b>.

In embodiments, the administrator system <b>116</b> can be configured to generate a version identifier for a computing system based on the software packages <b>108</b> installed on a computing system <b>102</b>. The version identifier can be data of fixed size such as a number, character string, etc., derived from the software packages installed on the computing system <b>102</b>, that provides a “snap shot” of the particular software packages installed on the computing system <b>102</b>. To achieve this, the administrator system <b>116</b> can be configured to include a version tool <b>118</b>.

In embodiments, the version tool <b>118</b> can be implemented as an application program that is capable of executing on the administrator system <b>116</b> to perform the processes as described herein. As such, the version tool <b>118</b> can be configured to include the necessary logic, commands, instructions, and protocols in order to perform the methods and processes described herein. Likewise, the version tool <b>118</b> can be implemented as a portion of another application program of the administrator system <b>116</b>, such as the OS or management software. In either case, the version tool <b>118</b> can be stored on computer readable storage devices or media (CD, DVD, hard drive, portable storage memory, etc.) of the administrator system <b>116</b> and executed by the administrator system <b>116</b>.

In embodiments, the version tool <b>118</b> can be configured to identify particular software packages <b>108</b> installed on the computing system <b>102</b>. In particular, the version tool <b>118</b> can be configured to identify the names of the particular software packages <b>108</b> and data specific to the particular software packages <b>108</b> installed on the computing system <b>102</b>. For example, the specific data can include names of the software packages, epochs of the software packages, versions of the software packages, releases of the software packages, archs of the software packages, checksums of the software package, and formats of the checksums.

In embodiments, to identify the particular software packages <b>108</b>, the version tool <b>118</b> can be configured to communicate with the package manager <b>110</b> installed on the computing system <b>102</b>. To achieve this, the version tool <b>118</b> can be configured to include the necessary logic, commands, instructions, and protocols to communicate with the package manager <b>110</b> via the network <b>106</b>.

In embodiments, once the software packages and specific data are identified, the version tool <b>118</b> can be configured to order the software packages and/or the specific data. The version tool <b>118</b> can be configured to order the software packages and/or specific data based on any ordering algorithm, such as alphabetically based on the name of the software packages <b>108</b>, hierarchically by software package type based on dependencies, hierarchically by the type of specific data, and the like.

In embodiments, once ordered, the version tool <b>118</b> can be configured to apply a hash function to the specific data to generate hashed data. The version tool <b>118</b> can be configured to utilize any type of hash function to generate hashed data on a fixed size, for example, Secure Hash Algorithm (SHA1, SHA2, etc.). Once the hashed data is generated, the version tool <b>118</b> can be configured to concentrate the hashed data to generate the version identifier. In particular, the version tool <b>118</b> can be configured to concentrate the hashed data according to the ordering of the software packages and/or specific data.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary method for generating a version identifier <b>200</b> utilizing the processes described above, according to various embodiments. As illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, for example, the version tool <b>118</b> can identify four (4) particular software packages <b>202</b> from the software packages <b>108</b> that are installed on the computing system <b>102</b>. Likewise, the version tool <b>118</b> can identify the specific data <b>204</b> associated with the software packages <b>202</b>. As illustrated, the specific data <b>204</b> can be any type of data (numbers, character strings, etc.) in any format that is specific to a software package and can be different data sizes (different number of bits). For example, “Package A” can be a version of Yum with the specific data <b>204</b>: package name—“yum”, package epoch—“0”, package version—“3.2.25”, package release—“1.fc12”, package arch—“noarch”, package checksum type—“sha256”, package checksum—“cc8623522dc4bb1e2c0856e58f57119a00a34abee79128bcfa3f7126936”.

In embodiments, the version tool <b>118</b> can be configured to order the software packages <b>202</b> and specific data <b>204</b> according to an order procedure <b>205</b>, such as alphabetically by software package name, hierarchically by software package type based on dependencies, hierarchically by specific data type based on dependencies, hierarchically based on software package version, and combinations thereof. The version tool <b>118</b> can be configured to order the software packages <b>202</b> so that the software package <b>202</b> and/or specific data <b>204</b> order is consistent each time a version identifier is generated. In other words, the version tool <b>118</b> can order the software packages <b>202</b> and/or specific data <b>204</b> such that, if a version identifier was generated for a different computing which has the same software packages, the version tool <b>118</b> would create the same version identifier.

In embodiments, the version tool <b>118</b> can be configured to apply a hash function <b>206</b> to the specific data <b>204</b> to generate the hashed data <b>208</b>. As illustrated, the hash function <b>206</b> can be any type of defined procedure or mathematical function which converts large, possibly variable-sized data into fixed output data size (number of bits).

In embodiments, the version tool <b>118</b> can be configured to concentrate the hashed data <b>208</b> to generate the version identifier <b>200</b>. As illustrated, the version tool <b>118</b> can be configured to concentrate the hashed data <b>208</b> according to the order procedure <b>205</b>. As such, the version tool <b>118</b> can repeatably generate the same version identifier <b>200</b> for the same set of software packages <b>202</b>.

In embodiments, once generated, the version tool <b>118</b> can be configured to store the version identifier. As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, the version tool <b>118</b> can be configured to store the version identifier in a version record <b>120</b>. The version record <b>120</b> can be configured to include an identification of the computing system <b>102</b> (e.g. name of the user of computing system <b>102</b>, network address of the computing system <b>102</b>, etc.), names of the software packages <b>108</b> installed on the computing system <b>102</b>, and the version identifier. The version tool <b>118</b> can be configured to maintain the version record <b>120</b> in a repository <b>122</b>, such as a database. The repository <b>122</b> can be stored on computer readable storage devices or media (CD, DVD, hard drive, portable storage memory, etc.) of the administrator system <b>116</b>.

In embodiments, the version tool <b>118</b> can be configured to provide the version identifier to the computing system <b>102</b>. For example, the version tool <b>118</b> can be configured to provide the version identifier to the computing system <b>102</b> via the network <b>106</b>.

In embodiments, the administrator system <b>116</b> can utilize the version identifier for a variety of tasks. For example, the administrator system <b>116</b> can compare the version identifier of the computing system <b>102</b> to version identifiers of other computing systems (not shown) to determine if the software packages installed on the computing system <b>102</b> match the software packages installed on the other computing systems. Additionally, the administrator system <b>116</b> can utilize the version identifier to determine if updates to the software packages on the computing system will install properly.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates another example of a software package delivery and management system <b>300</b>, according to various embodiments of the present teachings. While <figref idref="DRAWINGS">FIG. 3</figref> illustrates various components that can be included in the software package delivery and management system <b>300</b>, one skilled in the art will realize that additional components can be added or existing components can be removed.

As illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, the software package delivery and management system <b>300</b> can include a number of computing systems <b>102</b>. For example, the computing systems <b>102</b> can form a network <b>302</b> of computing systems for an entity such as a corporation, company, university, etc. In this example, the administrator system <b>116</b> can be configured to manage the network <b>302</b>. For instance,the administrator system <b>116</b> can be responsible for ensuring that the computing systems <b>102</b> in the network <b>302</b> are functioning properly. For instance, the administrator <b>116</b> can be responsible for ensuring that the computing systems <b>102</b> have the same set of software packages <b>108</b> installed.

In embodiments, the administrator system <b>116</b> can be configured to utilize the version tool <b>118</b> to verify that the computing systems <b>102</b> have the same set of software packages <b>108</b> installed. The administrator system <b>116</b> can utilize the version tool <b>118</b> to generate a version identifier for each of the computing systems <b>102</b>, as described above. In particular, the version tool <b>118</b> can be configured to identify the software packages <b>108</b> installed on each of the computing systems <b>102</b> and the data specific to the software packages <b>108</b>. For each of the computing systems <b>102</b>, the version tool <b>118</b> can be configured to apply a hash function to the specific data to generate hashed data. For each of the computing systems <b>102</b>, the version tool <b>118</b> can be configured to concentrate the hashed data to generate the version identifier for each of the computing systems <b>102</b>.

In embodiments, once the versions identifiers have been generated for each of the computing systems <b>102</b>, the administrator system <b>116</b> can compare the version identifiers to identify if the computing systems <b>102</b> have the same set of software packages <b>108</b> installed. For example, if a particular computing system <b>102</b> has a version identifier that differs from the other computing systems <b>102</b>, the administrator system <b>116</b> can determine that the particular computing system <b>102</b> does not have the correct software packages installed.

In embodiments, likewise, the administrator system <b>116</b> can be configured to generate a test version identifier, which represents the software packages that should be installed on the computing systems <b>102</b>. To generate the test version identifier, the version tool <b>118</b> can be configured to identify the software packages that should be installed on the computing systems <b>102</b> and the data specific to the software packages. To identify the software packages, the administrator system <b>116</b> can be configured to maintain a configuration record <b>304</b>. The configuration record <b>304</b> can be configured to store the software packages that should be installed on the computing systems <b>102</b> and the specific data associated with the software packages. The version tool <b>118</b> can be configured to store the configuration record <b>304</b> in the repository <b>122</b>.

In embodiments, additionally, to generate the test version identifier, the version tool <b>118</b> can be configured to retrieve the software packages that should be installed on the computing systems <b>102</b> and the specific data from the software repository <b>104</b> or the software repository mirrors <b>109</b>. For instance, to generate the configuration record <b>304</b>, the version tool <b>118</b> can be configured to retrieve the software packages that should be installed on the computing systems <b>102</b> and the specific data from the software repository <b>104</b> or the software repository minors <b>109</b>. To determine which software packages and specific data to retrieve, the version tool <b>118</b> can be configured to generate an interface <b>306</b> to receive an identification of the software packages from art administrator controlling the administrator system <b>116</b>. As such, the version tool <b>118</b> can be configured to include the necessary logic, commands, instructions, and protocols to generate commands line and/or GUIs to function as the interface <b>306</b>.

In embodiments, once the software packages that should be installed on the computing systems <b>102</b> and the specific data are identified, the version tool <b>118</b> can be configured to generate the test version identifier using the processes described above. Once generated, the administrator system <b>116</b> can compare the test version identifier to the version identifiers of each of the computing systems <b>102</b>. If a particular computing system <b>102</b> has a version identifier that differs from the test version identifier, the administrator system <b>116</b> can determine that the particular computing system <b>102</b> does not have the correct software packages installed.

In embodiments, if the administrator system <b>116</b> determines that a particular computing system <b>102</b> does not have the correct software packages installed, the administrator system <b>116</b> can be configured to take a variety of actions. The administrator system <b>116</b> can be configured to notify the particular computing system <b>102</b> via the network <b>106</b>. For instance, the administrator system <b>116</b> can be configured to notify the particular computing system <b>102</b> via the network <b>106</b> using networks protocols, such as Internet protocol (IP), user datagram protocol (UDP), transmission control protocol (TCP), hypertext transfer protocol (HTTP), file transfer protocol (FTP), electronic mail (email) protocols, or any other type of known or proprietary network protocol.

In embodiments, additionally, if the administrator system <b>116</b> determines that a particular computing system <b>102</b> does not have the correct software packages installed, the administrator system <b>116</b> can be configured to instruct the particular computing system <b>102</b> to install the correct software packages. In particular, the administrator system <b>116</b> can be configured to instruct the package manager <b>110</b> to install the correct software packages. To achieve this, the administrator system <b>116</b> can be configured to communicate with the package manager <b>110</b> of the the particular computing system <b>102</b> via the network <b>106</b> using networks protocols, such as Internet protocol (IP), user datagram protocol (UDP), transmission control protocol (TCP), hypertext transfer protocol (HTTP), file transfer protocol (FTP), electronic mail (email) protocols, or any other type of known or proprietary network protocol.

In embodiments, as described above, when communicating with the computing systems <b>102</b>, the software repository <b>104</b>, and/or the software repository mirrors <b>109</b>, the administrator system <b>116</b> can be configured to utilize any type of network management application or tool, located separate from or incorporated in the administrator system <b>116</b>, to securely communicate with the computing systems <b>102</b>, to monitor the state of the computing systems <b>102</b>, to retrieve and request data from the computing systems <b>102</b>, and to manage and direct the computing systems <b>102</b>. For example, the administrator system <b>116</b> can utilize a “FUNC” server as described in U.S. patent application Ser. No. 12/130,424, filed May 30, 2008, entitled “REMOTE MANAGEMENT OF NETWORKED SYSTEMS USING SECURE MODULAR PLATFORM” (U.S. Patent Application Publication No. 20090300180) assigned to Red Hat.™. Corporation, the disclosure of which is incorporated herein, in its entirety, by reference.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates an exemplary diagram of hardware and other resources that can be incorporated in the administrator system <b>116</b> and configured to communicate with the computer systems <b>102</b> via one or more networks <b>106</b>, according to embodiments. In embodiments as shown, the administrator system <b>116</b> can comprise a processor <b>402</b> communicating with memory <b>404</b>, such as electronic random access memory, operating under control of or in conjunction with operating system <b>406</b>. Operating system <b>406</b> can be, for example, a distribution of the Linux™ operating system, such as Red Hat™ Enterprise Linux, Fedora, etc., the Unix™ operating system, or other open-source or proprietary operating system or platform. Processor <b>402</b> also communicates with one or more computer readable storage devices or media <b>408</b>, such as hard drives, optical storage, and the like, for maintaining the operating system <b>406</b>, the version tool <b>118</b>, and the repository <b>122</b>. Processor <b>402</b> further communicates with network interface <b>410</b>, such as an Ethernet or wireless data connection, which in turn communicates with one or more networks <b>106</b>, such as the Internet or other public or private networks.

Processor <b>402</b> also communicates with the version tool <b>118</b> and the repository <b>122</b> to execute control logic and allow performance of the processes as described herein. Other configurations of the administrator system <b>116</b>, associated network connections, and other hardware and software resources are possible.

While <figref idref="DRAWINGS">FIG. 3</figref> illustrates the administrator system <b>116</b> as a standalone system including a combination of hardware and software, the administrator system <b>116</b> can include multiple systems operating in cooperation. The version tool <b>118</b> can be implemented as a software application or program capable of being executed by the administrator system <b>116</b>, as illustrated, or other conventional computer platforms. Likewise, the version tool <b>118</b> can also be implemented as a software module or program module capable of being incorporated in other software applications and programs, such as the operating system of the administrator system <b>116</b> and/or combined in a single application or program. In any example, the version tool <b>118</b> can be implemented in any type of conventional proprietary or open-source computer language. When implemented as a software application or program code, the version tool <b>118</b> can be stored in a computer readable storage medium, such as storage <b>408</b>, accessible by the administrator system <b>116</b>. Likewise, during execution, a copy of the version tool <b>118</b> can be stored in the memory <b>404</b>.

<figref idref="DRAWINGS">FIG. 5A</figref> illustrates a flow diagram for managing computing systems <b>102</b> utilizing a version identifier, according to embodiments of the present teachings. In <b>502</b>, the process can begin. In <b>504</b>, the administrator system <b>116</b> can determine the version identifiers for the computing systems <b>102</b> in a network <b>302</b>. The administrator system <b>116</b> can identify the software packages <b>108</b> installed on each of the computing systems <b>102</b> and the data specific to the software packages <b>108</b>. For each of the computing systems <b>102</b>, the version tool <b>118</b> can apply a hash function to the specific data to generate hashed data. For each of the computing systems <b>102</b>, the version tool <b>118</b> can concentrate the hashed data to generate the version identifier for each of the computing systems <b>102</b>.

In <b>506</b>, the administrator system <b>116</b> can determine a test version identifier for the network <b>302</b>. To generate the test version identifier, the administrator system <b>116</b> can identify the software packages that should be installed on the computing systems <b>102</b> and the data specific to the software packages. Once the software packages that should be installed on the computing systems <b>102</b> and the specific data are identified, the administrator system <b>116</b> can generate the test version identifier using the processes described above.

In <b>508</b>, the administrator system <b>116</b> can compare the version identifier for each computing system <b>102</b> to the test version identifier. In <b>510</b>, the administrator system <b>116</b> can identify whether the computing systems <b>102</b> have the correct software packages installed on the computing systems <b>102</b>. The administrator system <b>116</b> can identify any computing system <b>102</b> as having the incorrect software packages installed if the version identifier of that computing system <b>102</b> does not match the test version identifier.

In <b>512</b>, the administrator system <b>116</b> can instruct the computing systems <b>102</b> to install the correct software packages if necessary. If a particular computing system <b>102</b> is identified as not having the correct software packages, the administrator system <b>116</b> can instruct the particular computing system <b>102</b> to install the software packages that were used to determine the test version identifier. For example, the administrator system <b>116</b> can instruct the package manager <b>110</b> of the particular computing system <b>102</b> to install the correct software packages.

In <b>514</b>, the process can end, but the process can return to any point and repeat.

<figref idref="DRAWINGS">FIG. 5B</figref> illustrates another flow diagram for managing computing systems <b>102</b> utilizing a version identifier, according to embodiments of the present teachings. In <b>550</b>, the process can begin. In <b>552</b>, the administrator system <b>116</b> can determine the version identifiers for the computing systems <b>102</b> in a network <b>302</b>. The administrator system <b>116</b> can identify the software packages <b>108</b> installed on each of the computing systems <b>102</b> and the data specific to the software packages <b>108</b>. For each of the computing systems <b>102</b>, the version tool <b>118</b> can apply a hash function to the specific data to generate hashed data. For each of the computing systems <b>102</b>, the version tool <b>118</b> can concentrate the hashed data to generate the version identifier for each of the computing systems <b>102</b>.

In <b>554</b>, the administrator system <b>116</b> can compare the version identifier for each computing system <b>102</b>. In particular, the administrator system <b>116</b> can compare version identifier of each computing system <b>102</b> to the version identifiers of the other computing systems <b>102</b> in the network <b>302</b>. In <b>556</b>, the administrator system <b>116</b> can identify whether the computing systems <b>102</b> have the correct software packages installed on the computing systems <b>102</b>. The administrator system <b>116</b> can identify any computing system <b>102</b> as having the incorrect software packages installed if the version identifier of that computing system <b>102</b> does not match the version identifiers of the other computing systems <b>102</b> in the network <b>302</b>.

In <b>558</b>, the administrator system <b>116</b> can instruct the computing systems <b>102</b> to install the correct software packages if necessary. If a particular computing system <b>102</b> is identified as not having the correct software packages, the administrator system <b>116</b> can instruct the particular computing system <b>102</b> to install the software packages that were used to determine the test version identifier. For example, the administrator system <b>116</b> can instruct the package manager <b>110</b> of the particular computing system <b>102</b> to install the correct software packages.

In <b>560</b>, the process can end, but the process can return to any point and repeat.

Certain embodiments may be performed as a computer application or program. The computer program may exist in a variety of forms both active and inactive. For example, the computer program can exist as software program(s) comprised of program instructions in source code, object code, executable code or other formats; firmware program(s); or hardware description language (HDL) files. Any of the above can be embodied on a computer readable medium, which include computer readable storage devices and media, and signals, in compressed or uncompressed form. Exemplary computer readable storage devices and media include conventional computer system RAM (random access memory), ROM (read-only memory), EPROM (erasable, programmable ROM), EEPROM (electrically erasable, programmable ROM), and magnetic or optical disks or tapes. Exemplary computer readable signals, whether modulated using a carrier or not, are signals that a computer system hosting or running the present teachings can be configured to access, including signals downloaded through the Internet or other networks. Concrete examples of the foregoing include distribution of executable software program(s) of the computer program on a CD-ROM or via Internet download. In a sense, the Internet itself, as an abstract entity, is a computer readable medium. The same is true of computer networks in general.

While the teachings have been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments without departing from the true spirit and scope. The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. In particular, although the method has been described by examples, the steps of the method may be performed in a different order than illustrated or simultaneously. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” As used herein, the term “one or more of” with respect to a listing of items such as, for example, A and B, means A alone, B alone, or A and B. Those skilled in the art will recognize that these and other variations are possible within the spirit and scope as defined in the following claims and their equivalents.