Configuration objectification and version control

• US 7,860,959 B1
• Filed: 03/04/2004
• Issued: 12/28/2010
• Est. Priority Date: 03/04/2004
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Luxenberg, Roni, Oz, Doron, Ward, David D., Karpati, Danny
• Primary Examiner(s): Etienne; Ario
• Assistant Examiner(s): Williams; Clayton R
• Application Number:
  US10/793,195
• Time in Patent Office: 2,490 Days
• Field of Search: None
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/0859 by keeping history of different configuration generations or by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions

Abstract

A technique maintains configurations of an intermediate node in a version control system. Entities within the intermediate node are represented by objects. Each object is associated with a state. Each object is distinct from other objects in the intermediate node, thus enabling the state of an object to be changed, without affecting other objects. Versions of the objects'"'"' states are maintained in the version control system. The version control system is configured to maintain one or more versions of state associated with the objects. A configuration of the intermediate node is defined by labeling a version of objects saved in the version control system. A configuration is applied to the intermediate node by acquiring the states of objects associated with the configuration from the version control system and configuring the intermediate node'"'"'s entities represented by the objects in accordance with the acquired states.

Claims

1. A method for configuring an intermediate node contained in a data network, the method comprising the steps of:

defining a plurality of objects representing entities within the intermediate node;

arranging, by a processor, the objects in a multi-level hierarchical object tree;

saving a plurality of versions of state of at least some of the objects in a memory, the versions of state for each of these objects organized into a respective multi-level hierarchical version control tree, each multi-level hierarchical version control tree associated with a respective one of the objects in the multi-level hierarchical object tree;

associating selected ones of the plurality of versions of state, that are each located in different multi-level hierarchical version control trees associated with different objects in the multi-level hierarchical object tree, with a first label to establish a first configuration of the intermediate node, the first label indicating a name of the first configuration; and

configuring entities within the intermediate node according to the first configuration by accessing the selected ones of the plurality of versions of state of different objects, in the different multi-level hierarchical version control trees associated with the different objects, that are each associated with the first label.

2. The method as defined in claim 1 comprising the step of:

defining the objects that represent the entities within the intermediate node to include an object that represents the intermediate node as a top level object.

3. The method as defined in claim 1 wherein the objects are defined using a network management system.

4. The method as defined in claim 1 wherein the version control trees are contained in the intermediate node.

5. The method as defined in claim 1 wherein the version control trees are contained in a management system.

6. The method as defined in claim 1 wherein the version control trees are contained in a version control database.

7. The method as defined in claim 6 wherein the version control database is maintained on a remote system capable of communicating with the intermediate node.

8. The method as defined in claim 1 comprising the steps of:

defining a second configuration of the intermediate node by generating a new plurality of versions of state for the objects;

saving the new plurality of versions of state in version control trees; and

associating the new plurality of versions of state with a second label, the second label indicating a name of the second configuration.

9. The method as defined in claim 8 comprising the step of:

configuring the entities in accordance with the second configuration.

10. The method as defined in claim 8 comprising the steps of:

generating undo state that enables the changes made in the second configuration to be undone; and

saving the undo state.

11. The method as defined in claim 10 wherein the undo state comprises instructions configured to direct the intermediate node to configure the entities in accordance with the first configuration.

12. The method as defined in claim 8 comprising the steps of:

configuring one or more entities contained in the intermediate node in accordance with the second configuration;

determining if an error has occurred; and

if so, configuring the entities in accordance with another configuration.

19. The method as defined in claim 1 comprising the step of:

configuring at least some of the version control trees to have a mainline and one or more branches, where state of an object maintained in versions of state on a branch is independent of state of the object maintained in versions of state on the mainline.

20. The method as defined in claim 19 comprising the step of:

merging a version of state of an object on a branch with a version of state of the object on the mainline to incorporate changes made to state by the branch.

23. The method as defined in claim 1 wherein the step of configuring is performed, automatically, without user intervention, in response to reaching a first time.

13. An apparatus comprising:

one or more entities of an intermediate node; and

a processor configured to;

a) define objects to represent the entities within the intermediate node and arranging the objects in a multi-level hierarchical object tree,

b) save a plurality of versions of state of at least some of the objects, the versions of state for each of these objects organized into a respective multi-level hierarchical version control tree, each multi-level hierarchical version control tree associated with a respective one of the objects in the multi-level hierarchical object tree,

c) associate selected ones of the plurality of versions of state, in different multi-level hierarchical version control trees associated with different objects in the multi-level hierarchical object tree, with a first label to establish a first configuration of the intermediate node, the first label indicating a name of the first configuration; and

d) configure entities within the intermediate node according to the first configuration by accessing the selected ones of the plurality of versions of state of different objects, in the different multi-level hierarchical version control trees associated with the different objects, that are each associated with the first label.

14. The apparatus as defined in claim 13 wherein the version control trees are contained in a version control database.

15. The apparatus as defined in claim 14 wherein the processor is configured to:

a) generate a new configuration of the intermediate node by saving a new plurality of versions of state in version control trees of the version control database; and

b) associate the new plurality of versions of state with a second label, the second label indicating a name of the second configuration.

16. The apparatus as defined in claim 13 wherein the processor is further configured to:

a) generate undo state that configures the entities in accordance with a prior saved configuration; and

b) save the undo state.

21. The apparatus as defined in claim 13 wherein the processor is further configured to:

configure at least some of the version control trees to have a mainline and one or more branches, where state of an object maintained in versions of state on a branch is independent of state of the object maintained in versions of state on the mainline.

22. The apparatus as defined in claim 21 wherein the processor is further configured to:

merge a version of state of an object on a branch with a version of state of the object on the mainline to incorporate changes made to state by the branch.

17. An intermediate node comprising:

one or more entities;

means for defining a plurality of objects representing the entities within the intermediate node and arranging the objects in a multi-level hierarchical object tree;

means for saving a plurality of versions of state of at least some of the objects, the versions of state for each of these objects organized into a respective multi-level hierarchical version control tree, each multi-level hierarchical version control tree associated with a respective one of the objects in the multi-level hierarchical object tree;

means for associating selected ones of the plurality of versions of state, that are each located in different multi-level hierarchical version control trees associated with different objects in the multi-level hierarchical object tree, with a first label to establish a first configuration of the intermediate node, the first label indicating a name of the first configuration; and

means for configuring entities within the intermediate node according to the first configuration by accessing the selected ones of the plurality of versions of state of different objects, in the different multi-level hierarchical version control trees associated with the different objects, that are associated with the first label.

18. A non-transitory computer readable medium comprising computer executable instructions for:

defining a plurality of objects to represent entities contained in an intermediate node and arranging the objects in a multi-level hierarchical object tree;

saving a plurality of versions of state of at least some of the objects, the versions of state for each of these objects organized into a respective multi-level hierarchical version control tree, each multi-level hierarchical version control tree associated with a respective one of the objects in the multi-level hierarchical object tree;

associating selected ones of the plurality of versions of state, that are each located in different multi-level hierarchical version control trees associated with different objects in the multi-level hierarchical object tree, with a first label to establish a first configuration of the intermediate node, the first label indicating a name of the first configuration; and

configuring entities within the intermediate node according to the first configuration by accessing the selected ones of the plurality of versions of state of different objects, in the different multi-level hierarchical version control trees associated with the different objects, that are each associated with the first label.

24. A method comprising:

defining, by a processor, a plurality of objects representing entities of an intermediate node;

saving a plurality of versions of state of at least some of the objects in a memory, the versions for each of these objects organized into a respective multi-level hierarchical version control tree, each multi-level hierarchical version control tree associated with a respective one of the objects;

associating first selected ones of the plurality of versions of state, that are each located in different multi-level hierarchical version control trees associated with different objects, with a first label to establish a first configuration of the intermediate node, the first label indicating a name of the first configuration;

associating second selected ones of the plurality of versions of state, that are each located in different multi-level hierarchical version control trees associated with different objects, with a second label to establish a second configuration of the intermediate node, the second label indicating a name of the second configuration;

in response to reaching a first time, automatically, without user intervention, configuring entities of the intermediate node according to the first configuration by accessing the first selected ones of the plurality of versions of state in the different multi-level hierarchical version control trees that are associated with the first label; and

in response to reaching a second time, automatically, without user intervention, configuring entities of the intermediate node according to the second configuration by accessing the second selected ones of the plurality of versions of state in the different multilevel hierarchical version control trees that are associated with the second label.

25. The method as defined in claim 24 wherein the first time is a first time of day and the second time is a second time of day.

26. An apparatus comprising:

one or more entities of an intermediate node;

a memory; and

a processor configured to

define a plurality of objects representing the entities of the intermediate node,

save a plurality of versions of state of at least some of the objects in the memory, the versions of objects organized into respective multi-level hierarchical version control trees, each multi-level hierarchical version control tree associated with a respective one of the objects,

associate first selected ones of the plurality of versions of state, that are each located in different multi-level hierarchical version control trees associated with different objects, with a first label to establish a first configuration of the intermediate node, the first label indicating a name of the first configuration,

associate second selected ones of the plurality of versions of state, that are each located in different multi-level hierarchical version control trees associated with different objects, with a second label to establish a second configuration of the intermediate node, the second label indicating a name of the second configuration,

automatically configure entities of the intermediate node according to the first configuration using the first selected ones of the plurality of versions of state in the different multi-level hierarchical version control trees that are associated with the first label, in response to reaching a first time, and

automatically configure entities of the intermediate node according to the second configuration by accessing the second selected ones of the plurality of versions of state in the different multi-level hierarchical version control trees that are associated with the second label, in response to reaching a second time.

27. The apparatus as defined in claim 26 wherein the first time is a first time of day and the second time is a second time of day.