Hierarchical Object Model for Automated Datacenter Network Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for deploying network configurations in datacenters lack full automation, particularly in pushing Layer 2 and Layer 3 configurations, and managing complex connectivity and flexible topologies efficiently and securely.
Innovation Solution
A method involving object modeling and REST API calls to set up and push network configurations, using node, interface, evpnEdge, and layer objects to represent points of interconnection, enabling efficient deployment of Layer 2 and Layer 3 protocols like VxLAN and MPLS, ensuring valid and secure configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual configuration methods are used, then flexibility in handling complex connectivity scenarios is maintained, but deployment automation and speed are reduced
Solution Approach 1:
The configuration model is segmented into hierarchical object types (node object, interface object, evpnEdge object, layer object) that can be instantiated independently through REST API calls. This segmentation enables automated deployment while maintaining the ability to handle complex connectivity scenarios through compositional configuration of these standardized objects.
Solution Approach 2:
REST API calls serve as an intermediary between the configuration system and the network devices. The API provides a standardized interface for creating, modifying, and deleting configuration objects, enabling automation while abstracting the complexity of underlying network protocols and device-specific configurations.
2Reliability
If Layer 2 configuration is pushed to points of presence, then connectivity is established, but configuration validation and security are compromised
Solution Approach 1:
The configuration is validated against the hierarchical model schema before being pushed to the network devices. This preliminary validation ensures that only valid and secure configurations are deployed, while the automated validation process maintains high deployment speed by eliminating manual verification steps.
Solution Approach 2:
The system provides feedback through REST API responses that confirm configuration creation, modification, or deletion. This feedback mechanism ensures configuration validity and security by verifying that operations were executed successfully and that the resulting configuration meets the required criteria, while maintaining efficient automated operation.
3Adaptability or versatility
If complex connectivity scenarios are handled manually, then topology flexibility is maintained, but deployment efficiency and automation are reduced
Solution Approach 1:
The hierarchical object model provides universal structures that can represent various connectivity scenarios. The same node object, interface object, evpnEdge object, and layer object can be configured in different combinations to support Layer 2, Layer 3, and complex connectivity topologies, enabling both flexibility and automation.
Solution Approach 2:
The configuration system is dynamic, allowing configuration objects to be created, modified, and deleted through REST API calls in response to changing network requirements. This dynamic capability enables the system to adapt to complex connectivity scenarios while maintaining automated deployment efficiency through programmatic configuration.
Data Source
AI summary
A method is devised of deploying a network configuration in a datacenter. The network configuration includes one of more points of interconnection, a point of presence of the datacenter being one of the one or more points of interconnection. Each of the one or more points of interconnection in the network configuration is modeled through objects comprising, for each given point of interconnection, a node object representing the point of interconnection, an interface object hierarchically inferior to the node object and representing a connection to the point of interconnection, an evpnEdge object representing the transport to/from of the point of interconnection in the network, and a layer object hierarchically inferior to the evpnEdge object, and representing the characteristics of the protocol of transport to/from the point of interconnection. The network configuration is set up by a succession of commands on the objects and then pushed to the datacenter.