Cloud Network Configuration Versioning via Poller Daemon
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The manual and time-consuming process of setting up and managing complex cloud networks, such as CLOS networks, is inefficient due to the need for individual configuration of numerous devices from different vendors, leading to scalability issues and increased complexity as network size grows.
Innovation Solution
A method and apparatus for automating network configuration and management through a centralized system that uses a poller daemon to detect discrepancies in device configurations, generate patch files, and manage snapshot databases, enabling automated provisioning and configuration of devices within the network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual configuration methods are used for each network device, then configuration accuracy can be maintained, but the time consumption and operational complexity increase significantly as network size grows
Solution Approach 1:
The patent uses template-based configuration files that serve as reusable copies for network device settings. Instead of manually configuring each device individually, administrators can create a master configuration template and automatically replicate it across multiple devices, maintaining consistency and accuracy while dramatically reducing the time required for network setup and management
Solution Approach 2:
The system performs preliminary configuration validation and discrepancy detection before actual configuration deployment. By checking for configuration mismatches between master templates and device-specific configurations in advance, the system prevents errors and ensures accuracy before applying configurations, thereby maintaining high precision while streamlining the overall process
2Reliability
If individual configuration of numerous devices is performed manually, then configuration control can be maintained, but scalability deteriorates as network size increases
Solution Approach 1:
The patent implements a universal configuration management system that handles multiple network devices from different vendors through a single automated platform. The system can manage diverse device types using standardized template mechanisms, enabling centralized control and significantly improving scalability without sacrificing configuration reliability across heterogeneous network environments
Solution Approach 2:
The system continuously monitors and detects configuration discrepancies between master templates and actual device configurations, providing feedback loops that maintain configuration control. This automated feedback mechanism ensures reliability by detecting and alerting administrators to mismatches while enabling scalable management of large networks through centralized oversight
3Productivity
If automated configuration systems are implemented, then productivity and scalability improve, but system complexity increases due to integration of multiple vendor devices
Solution Approach 1:
The patent segments the configuration management system into distinct modular components: template definition modules, discrepancy detection modules, and configuration deployment modules. This segmentation allows the automated system to handle multi-vendor device complexity through organized, manageable segments rather than monolithic complexity, maintaining high productivity while reducing the cognitive and operational burden of system management
Data Source
AI summary
The present disclosure relates to a method and/or apparatus for versioning cloud network configuration. The method can include receiving base configuration files for a set of devices forming at least a portion of a computing network, pulling current configuration files from each device of the set of devices, for each device, and determining a discrepancy when a base configuration file of the device and a current configuration file of the device do not match. When the discrepancy is determined for a device, generating a patch file based on the determined discrepancy for that device. The method can include extracting a last configuration commit time from that device, allocating a unique snapshot identifier to the patch file and associated with the last configuration commit time, and populating a snapshot database.