Comparative updates tracking to synchronize local operating parameters with centrally maintained reference parameters in a multiprocessing system

• US 6,167,408 A
• Filed: 08/31/1998
• Issued: 12/26/2000
• Est. Priority Date: 08/31/1998
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cannon, David Maxwell, Crockett, David Romney
• Primary Examiner(s): Follansbee, John A.
• Assistant Examiner(s): Whitmore, Stacy
• Application Number:
  US09/144,425
• Time in Patent Office: 848 Days
• Field of Search: 707/9, 707/200-204, 709/201, 709/220, 709/221, 709/225, 709/229, 709/248, 713/200-202, 395/712, 712/32
• US Class Current: 1/1
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0866 Checking the configuration
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

In a multiprocessing system, a configuration manager maintains various reference parameters that are selectively copied by subordinate managed units to form local operating parameters, which subsequently govern operation of these managed units. A comparative technique is employed to track reference parameter updates, and synchronize each local operating parameter counterpart accordingly. At the configuration manager, reference parameters include reference profiles and reference characteristics. Each reference profile specifies one or more of the reference characteristics. At each managed unit, the operating parameters include subcribed-to profiles and operating characteristics; both are initially copied from the configuration manager'"'"'s reference profiles/characteristics. Each local operating profile specifies one or more of the operating characteristics. Each managed unit operates according to its locally maintained operating characteristics. When certain update criteria are satisfied, a managed unit and the configuration manager cooperatively synchronize the manage unit'"'"'s local operating profiles and characteristics with the configuration manager'"'"'s reference profiles and characteristics. This involves comparing the reference and operating profiles to identify new, updated, or deleted operating characteristics. Also, the local operating profiles and operating characteristics may be cross-referenced to identify any "orphan" characteristics for deletion.

Claims

1. In a multiprocessing system that includes:

a configuration manager maintaining the following data;

reference data, comprising;

a record of reference characteristics;

a record of reference profiles, each reference profile having a name and an associated profile version code, each reference profile identifying one or more constituent reference characteristics; and

a subscription list identifying each managed unit subscribing to any of the reference profiles, and in association with each subscribing managed unit, all reference profiles subscribed to and their profile version codes;

multiple managed units, each coupled to the configuration manager, each managed unit maintaining the following data;

a record of one or more operating characteristics;

a record of one or more subscribed-to profiles, each subscribed-to profile comprising a name of a counterpart reference profile maintained by the configuration manager at a past time, and the counterpart reference profile'"'"'s profile version code; and

a profile master view containing master copy counterparts of all reference profiles maintained by the configuration manager at a past time;

where each managed unit functions according to contents of its record of operating characteristics;

a method of comparative update tracking to change local configuration settings at the managed units for synchronization with centrally maintained configuration settings at the configuration manager, comprising operations of;

the configuration manager receiving changes to the reference data;

in response to the changes, determining whether profile version codes of any of the subscribed-to profiles are older than profile version codes of their reference profile counterparts currently being maintained by the configuration manager;

if so, comparing the master copy counterpart of the subscribed-to profile to the reference profile counterpart of the subscribed-to profile as maintained by the configuration manager to identify any differences there between, and

in response to finding any new reference characteristics identified by the reference profile counterpart of the subscribed-to profile but not identified by the master copy counterpart of the subscribed-to profile, copying the new reference characteristics to the record of operating characteristics;

in response to finding any updated reference characteristics identified by the reference profile counterpart of the subscribed-to profile where previous versions of the reference characteristic are identified by the master copy counterpart of the subscribed-to-profile, copying the updated reference characteristics to the record of operating characteristics; and

in response to finding any omitted reference characteristics not identified by the reference profile counterpart of the subscribed-to profile but identified by the master copy counterpart of the subscribed-to-profile, determining whether any other master copy counterparts of subscribed-to profiles refer to the omitted reference characteristic, and if not, deleting the omitted reference characteristic from the record of operating characteristics.

2. The method of claim 1, the method further comprising:

if profile version codes of any of the subscribed-to profiles are older than profile version codes of their counterpart reference profile counterparts currently being maintained by the configuration manager,

changing the older version code of the subscribed-to profile to match the profile version code of its counterpart reference profile currently being maintained by the configuration manager;

changing the version code of the reference profile as listed in the subscription list in association with the managed unit; and

updating the master copy counterpart of the subscribed-to profile in the profile master view to replicate the reference profile.

3. The method of claim 2, the updating of the counterpart of the subscribed-to profile in the profile master view comprising copying all reference profiles from the record of reference profiles of the configuration manager into the profile master view.

4. The method of claim 1,

further comprising, responsive to profile version codes of any of the subscribed-to profiles being older than profile version codes of their counterpart reference profiles currently being maintained by the configuration manager, the managed unit sending contents of its record of subscribed-to profiles to the configuration manager;

where the comparing comprises;

the configuration manager examining the master copy counterpart of the subscribed-to profile to the reference profile counterpart of the subscribed-to profile as maintained by the configuration manager to identify new reference characteristics listed in the reference profile but not listed in the master copy counterpart; and

the configuration manager examining the master copy counterpart of the subscribed-to profile to the reference profile counterpart as maintained by the configuration manager to identify updated reference characteristics listed in the reference profile where previous versions of the reference characteristic are listed in the master copy counterpart.

5. The method of claim 4,

where each reference profile includes, in association with each constituent reference characteristic, a characteristic version code comprising the profile version code of the reference profile at a time the constituent reference characteristic was added to the reference profile;

where the identification of updated reference characteristics comprises comparing the each characteristic version code in the reference profile counterpart to the profile version code of the master copy counterpart of the subscribed-to profile.

6. The method of claim 1,

further comprising duplicating the reference profiles from the configuration manager at the managed unit;

where the comparing includes the managed unit comparing the master copy counterpart of the subscribed-to profile to the duplicate reference profile counterpart of the subscribed-to profile to identify any omitted reference characteristics not identified by the master copy counterpart of the subscribed-to-profile, and also determining whether any other master copy counterparts of subscribed-to profiles refer to the omitted reference characteristic, and if not, deleting the omitted reference characteristic from the record of operating characteristics.

7. The method of claim 6, further comprising:

replacing contents of the profile master view with the reference profiles duplicated from the configuration manager.

8. The method of claim 1, each profile version code comprising an integer, the method further including incrementing a reference profile'"'"'s version code each time the reference profile is changed.

9. The method of claim 1, further comprising:

the managed unit receiving a subscription request identifying a desired reference profile;

in response to the subscription request, the managed unit representing the desired reference profile in the record of subscribed-to profiles.

10. The method of claim 9, where the desired reference profile has a name, and where the managed unit representing the desired reference profile in the record of subscribed-to profiles comprises storing the name in the record of subscribed-to profiles in association with a predetermined version code earlier than all previous versions of the desired reference profile.

11. The method of claim 10, the predetermined version code being zero.

12. The method of claim 1, further comprising:

the managed unit receiving operating characteristics from source other than the configuration manager, and in response, storing the received operating characteristics in the record of operating characteristics.

13. A multiprocessing system, comprising:

a configuration manager maintaining the following data;

reference data, comprising;

a record of reference characteristics;

a record of reference profiles, each reference profile having a name and an associated profile version code, each reference profile identifying one or more constituent reference characteristics; and

a subscription list identifying each of the managed units subscribing to any of the reference profiles, and in association with each subscribing managed unit, all reference profiles subscribed to and their profile version codes;

one or more managed units, each coupled to the configuration manager, each managed unit maintaining the following data;

a record of one or more operating characteristics;

a record of one or more subscribed-to profiles, each subscribed-to profile comprising a name of a counterpart reference profile maintained by the configuration manager at a past time, and the counterpart reference profile'"'"'s profile version code; and

a profile master view containing master copy counterparts of all reference profiles maintained by the configuration manager at a past time;

where each managed unit functions according to contents of its record of operating characteristics;

a communications link coupling the configuration manager to the managed units;

where the configuration manager and managed units are programmed to perform operations of comparative update tracking to synchronize local configuration settings with centrally maintained paradigm settings, the operations comprising;

the configuration manager receiving changes to the reference data;

in response to the changes, determining whether profile version codes of any of the subscribed-to profiles are older than profile version codes of their reference profile counterparts currently being maintained by the configuration manager;

if so, comparing the master copy counterpart of the subscribed-to profile to the reference profile counterpart of the subscribed-to profile as maintained by the configuration manager to identify any differences there between, and

in response to finding any new reference characteristics identified by the reference profile counterpart of the subscribed-to profile but not identified by the master copy counterpart of the subscribed-to profile, copying the new reference characteristics to the record of operating characteristics;

in response to finding any updated reference characteristics identified by the reference profile counterpart of the subscribed-to profile where previous versions of the reference characteristic are identified by the master copy counterpart of the subscribed-to-profile, copying the updated reference characteristics to the record of operating characteristics; and

in response to finding any omitted reference characteristics not identified by the reference profile counterpart of the subscribed-to profile but identified by the master copy counterpart of the subscribed-to-profile, determining whether any other master copy counterparts of subscribed-to profiles refer to the omitted reference characteristic, and if not, deleting the omitted reference characteristic from the record of operating characteristics.

14. The system of claim 13, the configuration manager and managed units being further programmed to perform operations comprising:

if profile version codes of any of the subscribed-to profiles are older than profile version codes of their counterpart reference profile counterparts currently being maintained by the configuration manager,

changing the older version code of the subscribed-to profile to match the profile version code of its counterpart reference profile currently being maintained by the configuration manager;

changing the version code of the reference profile as listed in the subscription list in association with the managed unit; and

updating the master copy counterpart of the subscribed-to profile in the profile master view to replicate the reference profile.

15. The system of claim 14, the configuration manager and managed units being programmed such that the updating of the counterpart of the subscribed-to profile in the profile master view comprises copying all reference profiles from the record of reference profiles of the configuration manager into the profile master view.

16. The system of claim 13,

the configuration manager and managed units being further programmed to perform operations further comprising, responsive to profile version codes of any of the subscribed-to profiles being older than profile version codes of their counterpart reference profiles currently being maintained by the configuration manager, the managed unit sending contents of its record of subscribed-to profiles to the configuration manager;

where the configuration manager and managed units are programmed such that the comparing comprises;

the configuration manager examining the master copy counterpart of the subscribed-to profile to the reference profile counterpart of the subscribed-to profile as maintained by the configuration manager to identify new reference characteristics listed in the reference profile but not listed in the master copy counterpart; and

the configuration manager examining the master copy counterpart of the subscribed-to profile to the reference profile counterpart as maintained by the configuration manager to identify updated reference characteristics listed in the reference profile where previous versions of the reference characteristic are listed in the master copy counterpart.

17. The system of claim 16,

where each reference profile includes, in association with each constituent reference characteristic, a characteristic version code comprising the profile version code of the reference profile at a time the constituent reference characteristic was added to the reference profile;

where the configuration manager and managed units are programmed such that the identification of updated reference characteristics comprises comparing the each characteristic version code in the reference profile counterpart to the profile version code of the master copy counterpart of the subscribed-to profile.

18. The system of claim 13,

the configuration manager and managed units being further programmed to perform operations comprising duplicating the reference profiles from the configuration manager at the managed unit;

where the configuration manager and managed units are programmed such that the comparing includes the managed unit comparing the master copy counterpart of the subscribed-to profile to the duplicate reference profile counterpart of the subscribed-to profile to identify any omitted reference characteristics not identified by the master copy counterpart of the subscribed-to-profile, and also determining whether any other master copy counterparts of subscribed-to profiles refer to the omitted reference characteristic, and if not, deleting the omitted reference characteristic from the record of operating characteristics.

19. The system of claim 18, the configuration manager and managed units being further programmed to perform operations comprising:

replacing contents of the profile master view with the reference profiles copied from the configuration manager.

20. The system of claim 13, each profile version code comprising an integer, the configuration manager and managed units being further programmed to perform operations including incrementing a reference profile'"'"'s version code each time the reference profile is changed.

21. The system of claim 13, each managed unit being programmed such that the operations further comprise:

the managed unit receiving a subscription request identifying a desired reference profile;

in response to the subscription request, the managed unit representing the desired reference profile in the record of subscribed-to profiles.

22. The system of claim 21, where the desired reference profile has a name, and where each managed unit is programmed such that the operations further comprise the managed unit representing the desired reference profile in the record of subscribed-to profiles comprises storing the name in the record of subscribed-to profiles in association with a predetermined version code earlier than all previous versions of the desired reference profile.

23. The system of claim 22, the predetermined version code being zero.

24. The system of claim 13, each managed unit being programmed such that the operations further comprise:

the managed unit receiving operating characteristics from source other than the configuration manager, and in response, storing the received operating characteristics in the record of operating characteristics.

25. A method for operating a multiprocessing system including a configuration manager and multiple hierarchically inferior managed units, comprising operations of:

the configuration manager maintaining reference compilations of (1) different operating characteristics specifying operating parameters for a managed unit, and (2) different operating profiles, each profile defining a managed unit operating mode by identifying a particular combination of one or more of the operating characteristics;

the managed units subscribing to one or more selected operating profiles, comprising the following operations for each managed unit;

copying each selected operating profile from the configuration manager to local storage of the managed unit;

copying each operating characteristic identified in the selected operating profiles to local storage of the managed unit;

the managed unit conducting operations according to the locally-stored operating characteristics identified in the subscribed-to operating profiles;

on a recurring basis, each managed unit synchronizing its local storage with the reference compilation of the configuration manager, comprising;

identifying any locally stored operating profiles that are stale relative to changed counterparts in the reference compilation;

for each stale operating profile, comparing the stale operating profile to its counterpart in the reference compilation to identify any (1) updated operating characteristics listed in the counterpart profile that have been updated relative to earlier versions of the operating characteristics in the stale profile, (2) new operating characteristics listed in the counterpart profile that do not appear in the stale profile, and (3) deleted operating characteristics that are absent from the counterpart profile yet present in the stale profile;

updating the operating characteristics in local storage by adding any identified updated operating characteristics, adding any identified new operating characteristics, and deleting any identified absent operating characteristics;

updating each stale operating profile in local storage according to its counterpart at the configuration manager; and

the managed unit conducting operations according to the updated locally-stored operating characteristics identified in the updated subscribed-to operating profiles.