SYSTEMS AND METHODS FOR VALIDATING A CONFIGURATION IN A CLUSTER

• US 20130339494A1
• Filed: 06/15/2012
• Published: 12/19/2013
• Est. Priority Date: 06/15/2012
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Sharvari Mithyantha
• Inventors: MITHYANTHA, SHARVARI
• Granted Patent: US 8,832,241 B2
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: H04L 41/0846 based on copy from other elements
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements

Abstract

The present disclosure is directed towards systems and methods for validating a configuration across a cluster of intermediary devices. Within the cluster, a configuration change is entered at one node and propagated to the remaining nodes of the cluster. Before propagation, the new configuration is validated. The systems and methods include creating, on a first intermediary device, a configuration to be propagated to a plurality of routing daemons; executing, by a validation module of the first intermediary device, the configuration on a plurality of pseudo routing daemons, each pseudo routing daemon of the plurality of pseudo routing daemons corresponding to the routing daemon of a corresponding intermediary device of the cluster; and determining from results of executing the second configuration whether to propagate the second configuration to each routing daemon.

Claims

1. A method of validating a configuration across a cluster of intermediary devices, the method comprising:

(a) propagating, by a first intermediary of a cluster of intermediary devices, a first configuration to a routing daemon executing on each of the other intermediary devices of the cluster;

(b) creating, on the first intermediary device, a second configuration to be propagated to each routing daemon;

(c) executing, by a validation module of the first intermediary device, the second configuration on a plurality of pseudo routing daemons, each pseudo routing daemon of the plurality of pseudo routing daemons corresponding to the routing daemon of a corresponding intermediary device of the cluster; and

(d) determining, by the validation module, from results of executing the second configuration on the plurality of pseudo routing daemons whether to propagate the second configuration to each routing daemon of the corresponding intermediary device.

2. The method of claim 1, wherein step (a) further comprises propagating, by the first intermediary device, the first configuration via a message delivery system to each of the other intermediary devices of the cluster.

3. The method of claim 1, wherein step (a) further comprises executing, by the routing daemon on each intermediary device of the cluster, the first configuration.

4. The method of claim 1, wherein step (b) further comprises creating a second configuration comprising a set of executable configuration commands to be applied to the first configuration.

5. The method of claim 1, wherein step (c) further comprises executing, by the validation module, each pseudo routing daemon comprising a representation of a corresponding routing daemon.

6. The method of claim 1, wherein step (b) further comprises executing, by the validation module, each pseudo routing daemon as a copy of a corresponding routing daemon with a configuration thread enabled.

7. The method of claim 1, wherein step (b) further comprises executing, by the validation module, each pseudo routing daemon as a copy of a corresponding routing daemon with any network packet processing threads disabled.

8. The method of claim 1, wherein step (d) further comprises determining, by the validation module, that at least one executable configuration command of the second configuration failed execution on at least one pseudo routing daemon of the plurality of routing daemons and responsive to the determination the first intermediary devices does not propagate the second configuration file to the routing daemons on corresponding intermediary devices.

9. The method of claim 1, wherein step (d) further comprises determining, by the validation module, that every executable configuration command of the second configuration successfully executed on each pseudo routing daemon of the plurality of routing daemons and responsive to the determination the first intermediary devices propagates the second configuration file to the routing daemons on corresponding intermediary devices.

10. The method of claim 1, further comprising obtaining a copy of the running configuration from each of the intermediary devices of the cluster and creating a third configuration based on the running configuration.

11. A system of validating a configuration across a cluster of intermediary devices, the system comprising:

a cluster comprising a plurality of intermediary devices;

a first intermediary of a cluster of intermediary devices propagating a first configuration to a routing daemon executing on each of the other intermediary devices of the cluster;

a configuration tool on the first intermediary device creating a second configuration to be propagated to each routing daemon;

a validation module executing on the first intermediary device executing the second configuration on a plurality of pseudo routing daemons, each pseudo routing daemon of the plurality of pseudo routing daemons corresponding to the routing daemon of a corresponding intermediary device of the cluster; and

wherein the validation module determines from results of executing the second configuration on the plurality of pseudo routing daemons whether to propagate the second configuration to each routing daemon of the corresponding intermediary device.

12. The system of claim 11, wherein the first intermediary device propagates the first configuration via a message delivery system to each of the other intermediary devices of the cluster.

13. The system of claim 11, wherein the routing daemon on each intermediary device of the cluster executes the first configuration.

14. The system of claim 11, wherein the configuration tool creates a second configuration comprising a set of executable configuration commands to be applied to the first configuration.

15. The system of claim 11, wherein the validation module executes each pseudo routing daemon comprising a representation of a corresponding routing daemon.

16. The system of claim 11, wherein the validation module executes each pseudo routing daemon as a copy of a corresponding routing daemon with a configuration thread enabled.

17. The system of claim 11, wherein the validation module executes each pseudo routing daemon as a copy of a corresponding routing daemon with any network packet processing threads disabled.

18. The system of claim 11, wherein the validation module determines that at least one executable configuration command of the second configuration failed execution on at least one pseudo routing daemon of the plurality of routing daemons and responsive to the determination the first intermediary devices does not propagate the second configuration file to the routing daemons on corresponding intermediary devices.

19. The system of claim 11, wherein the validation module determines that every executable configuration command of the second configuration successfully executed on each pseudo routing daemon of the plurality of routing daemons and responsive to the determination the first intermediary devices propagates the second configuration file to the routing daemons on corresponding intermediary devices.

20. The system of claim 11, wherein the configuration tool obtains a copy of the running configuration from each of the intermediary devices of the cluster and creates a third configuration based on the running configuration.