Managing configuration information for multiple devices

The invention provides for managing information for multiple devices. Each of a set of devices retrieves information from a sequence of servers. A device when starting up reads a list of file names, reads information from each file in sequence, and resolves conflicts among files to present a consistent configuration on each restart of each device. A file includes a sequence of <name, value> pairs. In those cases when two variables have the same name, an operator associated with the second pair indicates whether to overwrite the first value or to edit the first value, such as by appending the second value. One of the pairs indicates the list of file names itself. When the list of file names is changed, the device for which the change is made re-reads the sequence of files and repeats its determination of the pairs, until the list of file names is stabilized.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to managing configuration information for multiple devices.

2. Related Art

Each computer system includes information about its internal state, such as where its software elements are located, where data is maintained for those software elements, and the like. As computer systems become relatively large, the amount of that information also becomes relatively large, and the task maintaining that information in a manageable form becomes relatively difficult. For one example, in a cache management system (a system including a set of caching devices each of which maintains relatively local copies of web pages and possibly other network objects obtained from relatively remote origination servers), each one of a set of multiple caches can include information regarding how web pages should be downloaded, how quickly, whether selected client devices can download web pages, where selected web pages would be downloaded from, and the like; when there are many such caches, assuring that each cache has correct and up-to-date information can be detailed and time-consuming. For a second example, there can be multiple devices each having at least some information that is unique for each device and at least some information that is identical for multiple devices. In both examples, management of such information, including assuring that each device has correct and up-to-date information, can be detailed and time-consuming, and therefore error-prone.

A first problem in the known art is that access to multiple devices involves either direct physical access or communication with each such device. Direct physical connections to multiple devices can be inconvenient, such as in those cases where the set of devices is physically dispersed. Using a communication link is subject to the drawback that at least some of the devices might be unavailable at the time. Moreover, both of these methods presume that the manger already knows of the existence (and how to reach) each of the multiple devices, to direct them to use the particular information the manager selects.

Additional problems in the known art include the following: There is no convenient method in the known art for managing both local and remote information for multiple such devices.There is no convenient method in the known art for managing multiple such devices in groups or subgroups.There is no convenient method in the known art for managing device information by multiple information managers.There is no convenient method in the known art for managing device information when those devices are protected by firewalls, without granting access to those devices to managers.

Accordingly, it would be advantageous to provide an improved technique for managing information, particularly configuration information, for multiple devices.

SUMMARY OF THE INVENTION

The invention provides a method and system for managing device information for multiple devices, particularly configuration information. This is achieved in an embodiment of the invention in which each one of a set of devices retrieves information from a sequence of information servers (preferably both local and remote).

In a preferred embodiment, a device when starting up reads a list of configuration file names; reads configuration information from each configuration file in sequence; and resolves conflicts among configuration files to present a consistent configuration on each restart of each device.

In a preferred embodiment, a configuration file includes a sequence of <name, value> pairs, each of which represents a variable having the name <name> and the value <value>. In those cases when two variables have the same name, an operator associated with the second <name, value> pair indicates whether to overwrite the first value or to edit the first value, such as by appending the second value.

In a preferred embodiment, one of the <name, value> pairs indicates the list of configuration file names itself. When the list of configuration file names is changed, the device for which the change is made re-reads the sequence of configuration files and repeats its determination of the <name, value> pairs, until the list of configuration file names is stabilized (until it is possible to re-read the sequence of configuration files without further changes).

In a preferred embodiment, a device when starting up reads a value for the list of configuration file names, equal to the stabilized value determined by the device at the most recent restart.

Those of ordinary skill in the art will recognize, after perusal of this application, the many advantages provided by the invention. These include, but are not limited to, the following:maintaining information other than configuration information, such as for example information to be communicated among devices or users;maintaining information by multiple managers or by a hierarchy of managers, such as for example when each manager is assigned a subgroup of the information or a subgroup of the devices to manage;maintaining information in multiple locations, such as for example when at least part of the information can be found local to devices and at least part of the information can be found remotely from devices.

The invention has general applicability to maintaining information for multiple devices. Although a preferred embodiment is described with regard to configuration information for a set of multiple caches, there is no particular limitation of the invention to caches or similar devices, nor is there any particular limitation of the invention to configuration information. Techniques used by a preferred embodiment of the invention for remotely maintaining information for multiple devices, for resolving conflicts at devices between differing sets of information, and for remotely maintaining information by multiple managers, can be used in contexts other than the specific applications disclosed herein.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. Those skilled in the art would recognize after perusal of this application that embodiments of the invention can be implemented using one or more general purpose processors or special purpose processors or other circuits adapted to particular process steps and data structures described herein, and that implementation of the process steps and data structures described herein would not require undue experimentation or further invention.

The following terms refer or relate to aspects of the invention as described below. The descriptions of general meanings of these terms are not intended to be limiting, only illustrative.information to be maintained—in general, any values or other data to be recorded in selected locations for possible retrieval by devices for which that information is maintained.maintaining information—in general, any operation for creating, modifying, deleting, assigning, or otherwise managing information for possible use by devices.local and remote information—in general, local information is that which is accessible by a device without cooperation with any other device, while remote information is that which is accessible by a device using a communication link or a communication protocol to record or retrieve that information.device groups—in general, any technique for associating sets of devices with an identifier selecting those devices. Device groups can have zero, one, or more members, and can overlap.configuration information—in general, any information used during an initial (“start-up”) phase of operation for a device. There is no particular limitation of the invention to information that is not used after start-up.configuration file names—in general, any identifier allowing a device to identify a source for configuration information. For one example, such “file names” might be URLs or database queries, rather than names in a filesystem namespace.

As noted above, these descriptions of general meanings of these terms are not intended to be limiting, only illustrative. Other and further applications of the invention, including extensions of these terms and concepts, would be clear to those of ordinary skill in the art after perusing this application. These other and further applications are part of the scope and spirit of the invention, and would be clear to those of ordinary skill in the art, without further invention or undue experimentation.

System Elements

FIG. 1shows a block diagram of a system capable of managing information for a set of devices.

A system100includes a set of devices110, a set of configuration servers120, a set of management consoles130, and a communication link140. These elements operate together as described to perform the functions shown herein for the system100.

Devices

Each device110preferably includes a processor, program and data memory, mass storage, and a network interface to the communication link140. Each device110is therefore capable of performing programmed processes and communicating with other elements of the system100using the communication link140. The program and data memory in each device110include computer programs and data structures for performing steps described in this application. There is no particular requirement that the devices110must include mass storage, merely that at least some of their storage is persistent across restart operations. References herein to mass storage for the devices110are intended to be read broadly to include other forms of persistent storage and techniques for retaining information for restarting and communicating with other elements of the system100.

Each device110includes a set of local configuration files111, having information for use by the device110. In a preferred embodiment, these local configuration files111include at least a default configuration file11aand a last-boot configuration file111b. The default configuration file111aincludes information for the device110determined by a manufacturer for the device110. The last-boot configuration file111bincludes information for the device110as determined by the device110at of its last boot time, as described further in this application.

Each device110can have computer programs and data structures capable of defining a relative priority for a first and a second information server in response to a relative position of a first and second information server in a sequence of locations to be read by the device. Each device110can have computer programs and data structures capable of selecting the sequence of locations in response to a variable settable in response to at least one information server.

Configuration Servers

Similar to the devices110, each configuration server120preferably includes a processor, program and data memory, mass storage, and a network interface to the communication link140. Each configuration server120is therefore capable of performing programmed processes and communicating with other elements of the system100using the communication link140. Similar to the devices110, the program and data memory in each configuration server120include computer programs and data structures for performing steps described in this application. There is no particular requirement that the configuration servers120must include mass storage, merely that at least some of their information is retained sufficient for restarting and communicating with other elements of the system100.

One or more (or all of the) configuration servers120can be located on the same physical device as one of the devices110, in which case those devices110also include program and data information for performing the functions described herein for a configuration server120.

Each configuration server120includes a set of remote configuration files121, having information for use by one or more devices110. There is no particular requirement for any arrangement or hierarchy of remote configuration files121. However, in a preferred embodiment, the remote configuration files121include at least one global configuration file121a, and a set of group configuration files121b. The global configuration file121aincludes information determined by at least one manager131(as further described below) to be for use by substantially all devices110. The group configuration files121binclude information determined by at least one manager131(as further described below) to be for use by devices110associated with one or more device groups122.

For example, a first device group122might be associated with those devices in an engineering department of a company, while a second device group122might be associated with those devices in a marketing department of a company. There is no particular requirement regarding the arrangement or hierarchy of device groups122. For example, some devices110might be associated with more than one device group122(such as for example an “engineering” device group122and an “executive” device group122).

The remote configuration files121are accessible by the devices110using1one or more information transfer protocols. Accordingly, each device110includes computer programs and data structures capable of preparing request messages and responding to response messages in at least one such information transfer protocol. Similarly, each configuration server120includes computer programs and data structures capable of responding to request messages and preparing response messages in at least one such information transfer protocol. There is no particular requirement that the information transfer protocol be any specific protocol. In a preferred embodiment, the information transfer protocols include HTTP, SHTTP, some similar protocol, or a combination or variant thereof. However, in alternative embodiments, the information transfer protocols may include FTP, FSP, MUD, RSH, an embodiment-specific protocol using a selected port, or a combination or variant thereof.

Although there is no particular requirement therefore, in a preferred embodiment one or more devices110might also include remote configuration files121(“remote” in the sense that they are remote to other devices110), accessible by the devices110using one or more information transfer protocols. Accordingly, each such device110also includes computer programs and data structures capable of responding to request messages and preparing response messages in at least one such information transfer protocol.

In a preferred embodiment, each device110includes a cache, and is responsive to HTTP, SHTTP, and similar protocols. Each device is also responsive to local file access (by the device110itself), remote file access (both other devices110), FTP, RSH, and similar protocols.

Management Consoles

Similar to the devices110and the configuration servers120, each management console130preferably includes a processor, program and data memory, mass storage, and a network interface to the communication link140. Each management console130is therefore capable of performing programmed processes and communicating with other elements of the system100using the communication link140. Similar to the devices110and the configuration servers120, the program and data memory in each configuration server120includes computer programs and data structures for performing steps described in this application. There is no particular requirement that the management console130must include mass storage.

Similar to the devices110and the configuration servers120, one or more (or all of the) management consoles130can be located on the same physical device as one of the devices110, in which case those devices110also include program and data information for performing the functions described herein for a configuration server120.

Each management console130has associated with it a manager131(as further described above), such as a human operator capable of interacting with the management console130to create, edit, and delete both local configuration files111and remote configuration files121, and to assign them to devices110. There is no particular requirement that the manager131is actually a human operator; in alternative embodiments, the manager131can include a program for automatic management of configuration information or artificial intelligence software for performing general-purpose tasks.

Communication Link

In a preferred embodiment, the communication link140includes a LAN (local area network). However, in alternative embodiments, the communication link140may include any technique for communicating information, including without limitation a WAN (wide area network), an enterprise network, a VPN (virtual private network), a private or public switched network, or some combination or variant thereof.

There is no particular requirement that the communication link140must have any particular physical form, only that devices110, configuration servers120, and management consoles130can communicate with each other using the communication link140. In a preferred embodiment, each element of the system100is accessible by each other element using a protocol such as HTTP, SHTTP, or a variant thereof. However, there is no particular requirement that such HTTP access must be direct access; the communication link140might include intermediate devices such as proxies, firewalls, NAT translators, and the like.

Method of Operation

FIG. 2shows a process flow diagram of a method including steps of managing information for a set of devices.

A method200includes a set of flow points and process steps as described herein.

Although by the nature of textual description, the flow points and process steps are described sequentially, there is no particular requirement that the flow points or process steps must be sequential. Rather, in various embodiments of the invention, the described flow points and process steps can be performed in a parallel or pipelined manner, either by one device performing multitasking or multithreading, or by a plurality of devices operating in a cooperative manner. Parallel and pipelined operations are known in the art of computer science.

At a flow point210, the system100is ready to set configuration information for a device110.

At a step211, the device110restarts. Any individual device restart can be in response to one or more of a set of factors, including without limitation a hardware interrupt, a software panic (sometimes known as a “crash”), an operator command, a scheduled operation or some combination or variant thereof.

At a step212, the device110reads its last-restart configuration file111b. As part of this step, the device110reads a sequence of <name, value> pairs and sets the value of a set of variables, one for each <name> (having that name) equal to the corresponding <value>. One of these variables is a FILE-LIST variable, which describes the sequence of locations in which the device110looks for configuration information.

In a preferred embodiment, the FILE-LIST variable has a syntax including an initial delimeter (shown below as “\\”), a list of URL (uniform resource locator) values each on a separate line, and a final delimeter (shown below as “\\”). There is no particular requirement for using this syntax or these particular delimeters; any syntax or delimeters that could be consistently parsed by the devices110would suffice. Note that one of the URLs recited in the FILE-LIST variable has an “ftp:” prefix, indicating that the file is to be obtained using the FTP protocol.\\default.cfgftp://ncl-sun-0.lab.netapp.com/pub/global.cfglocal.cfg\\

In a preferred embodiment, the default configuration file111a(shown above as “default.cfg”) is always named first in the list. A preferred embodiment explicitly recites the location of the default configuration file111ain the FILE-LIST variable (which will be a variable named in the last-restart configuration file111b). However, in alternative embodiments, the default configuration file111amay be implicitly recited, that is, not recited but simply understood by the device110to come first.

At a step213, the device110determines the value of the FILE-LIST variable.

At a step214, the device110reads each file named in the FILE-LIST variable in sequence. As part of this step, the device110performs the following sub-steps:At a sub-step214(a), the device110selects a next file from the FILE-LIST variable. Initially, the “next” file is the first file designated by the FILE-LIST variable.Although these sub-steps214(a),214(b),214(c), and214(d) are described as if changes to variables are made immediately, in a preferred embodiment, the device110assures that all files specified by the FILE-LIST variable are accessible before making those changes. Each device100thus avoids using a specified configuration until complete copies of all configuration files have been obtained, so that it can assure that when the values in each configuration file are applied, they include a complete set.At a sub-step214(b), the device110determines if selected file has been updated. If not, the device110skips that file and continues with the substep214(d). Otherwise, the device110continues with the next sub-step.At a sub-step214(c), the device110reads each <name, value> pair from the selected file in turn. In a preferred embodiment, each <name, value> pair appears in one of the following syntactic forms:name=valuename+=valueIn either case, if the variable named <name> is not yet defined, it is defined and set equal to the associated value <value>.If the variable named <name> is already defined, there is a difference in treatment depending on the choice of form. For the first syntactic form, the variable is set equal to the new value <value> without regard for its earlier value. In the second syntactic form, the variable has the new value appended to the earlier value.At a sub-step214(d), the device110determines if there are any further files to read. If so, the device110loops back to the sub-step214(a). Otherwise, the device110continues with the next step.

If two inconsistent values are assigned to a single variable, the conflict can be resolved by determining, for any two sources for information about a set of values for named variables, a higher priority source and a lower priority source; parsing, from a higher priority source, an instruction relating to setting the variable; and performing the instruction from the higher priority source. The instruction can have a syntactic form indicating one or more of the following operations: replacing a value from the lower priority source with a value from the higher priority source, or appending a value from the higher priority source to a value from the lower priority source.

At a step215, the device110saves its set of variables in the last-restart configuration file111b, thus preserving the values associated with those variables for the next time the device110is restarted.

At a step216, the device110determines if the FILE-LIST variable has been changed by performance of the step214. If so, the method200goes back to the step214. Accordingly, the method200will perform the step214, the step215, and the step216repeatedly until the FILE-LIST variable reaches a settled value.

At a flow point220, the device110has set all its variables using the information in the local configuration files111and remote configuration files121, and is ready to run.

GENERALITY OF THE INVENTION

The invention has general applicability to maintaining information for multiple devices. Although a preferred embodiment is described with regard to configuration information for a set of multiple caches, there is no particular limitation of the invention to caches or similar devices, nor is there any particular limitation of the invention to configuration information. Techniques used by a preferred embodiment of the invention for remotely maintaining information for multiple devices, for resolving conflicts at devices between differing sets of information, and for remotely maintaining information by multiple managers, can be used in contexts other than the specific applications disclosed herein.

Other and further applications of the invention in its most general form would be clear to those skilled in the art after perusal of this application. The invention would be usable for such other and further applications without undue experimentation or further invention.

Although preferred embodiments are disclosed herein, many variations are possible which remain within the concept, scope and spirit of the invention; these variations would be clear to those skilled in the art after perusal of this application.