Vendor-neutral network device provisioning platform
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud-computing infrastructure faces challenges in efficiently provisioning and managing network devices due to the lack of standardization, leading to errors, resource inefficiency, prolonged downtimes, and increased maintenance costs, particularly as datacenters grow and become more complex.
Innovation Solution
A vendor-neutral network device provisioning platform using a dynamic, programmable infrastructure with software-defined networking principles, employing declarative configuration and model-driven management, and a NoSQL document database to encode provisioning requirements into a unified abstract data model for all types of network devices, enabling automated configuration and validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual provisioning and configuration of network devices is performed, then flexibility and adaptability to specific device requirements are maintained, but time consumption and human resource requirements increase significantly
Solution Approach 1:
The patent uses templates to store standardized configuration data for different network device types. When a new device is provisioned, the system automatically copies the appropriate template and applies it to the device, eliminating manual configuration while maintaining adaptability through template selection and customization.
Solution Approach 2:
Configuration templates are prepared in advance with pre-defined settings for various network device types. This preliminary action allows the system to quickly deploy devices by simply selecting and applying the appropriate pre-configured template, rather than configuring each device from scratch.
2Productivity
If standardized configuration processes are implemented across different network devices, then provisioning time is reduced and efficiency increases, but the ability to handle device-specific variations and complexities decreases
Solution Approach 1:
The configuration template system is segmented into hierarchical levels: generic network device configurations, vendor-specific configurations, device-type-specific configurations, and individual device customizations. This segmentation allows standardized processes at higher levels while accommodating device-specific variations at lower levels.
Solution Approach 2:
The template system serves multiple functions: it provides standardized configurations for common devices, handles vendor-specific variations, accommodates different device types, and allows individual customization. This multi-functionality enables a single system to address diverse provisioning needs efficiently.
3Reliability
If comprehensive validation and testing of network device configurations are performed, then configuration accuracy and reliability are improved, but provisioning time and system complexity increase
Solution Approach 1:
Validation rules and configuration checks are embedded within the templates themselves during the template creation phase. This preliminary action ensures that configurations are validated automatically as part of the provisioning process, rather than requiring separate extensive validation steps later.
Solution Approach 2:
The system incorporates automated validation that provides immediate feedback on configuration correctness during provisioning. This real-time feedback mechanism identifies and corrects configuration errors early in the process, ensuring reliability without requiring time-consuming post-provisioning testing.
Data Source
AI summary
Network devices are provisioned using a single vendor-neutral data model with a non-relational database. Provisioning requirements are collected upon detecting a new network device that needs to be configured and/or installed. Based on the provisioning requirements, a configuration object is retrieved using a data model in the non-relational database. The configuration object is transformed to a concrete configuration file for the network device. After applying the configuration file to the network device, a separate process validates the configuration of the network device by comparing the observed network configuration with the initial target configuration data included in the configuration object.