Shadow Dataplane Upgrade Verification for Network Edge Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Upgrades to network edge devices are disruptive, requiring scheduled maintenance windows, extensive pre- and post-upgrade checks, and uncertainty due to differences between testing environments and customer networks, leading to potential failures and downtime.
Innovation Solution
Implementing dual dataplanes, where a primary dataplane operates with the current version and a shadow dataplane verifies the updated version by comparing performance records, allowing seamless upgrades without downtime and ensuring compatibility in the customer's network environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional upgrade methods are used for network edge devices, then upgrades can be performed, but they cause downtime and require scheduled maintenance windows
Solution Approach 1:
The system segments the data plane into multiple independent dataplanes (first dataplane executing current version, second dataplane executing updated version). This allows the upgrade process to be divided into parallel tracks where the current version continues serving traffic while the updated version is verified separately, eliminating service interruption during upgrades.
Solution Approach 2:
The updated version is deployed to the second dataplane before taking over the primary role. Performance records are collected and comparisons are made in advance, allowing the system to prepare verification results before the actual switchover point, ensuring seamless transition without downtime.
2Reliability
If extensive pre- and post-upgrade checks are performed, then upgrade reliability is improved, but the complexity and time required increase
Solution Approach 1:
The system creates a copy of the data plane functionality in the form of multiple dataplanes. Each dataplane can be independently configured with different software versions, and performance records are copied and compared between dataplanes. This copying mechanism simplifies verification by allowing parallel execution and direct comparison of performance metrics without complex manual checking procedures.
Solution Approach 2:
The system automatically collects performance records from each dataplane and compares them to determine if the updated version meets performance thresholds. This automated feedback loop eliminates manual verification steps and reduces the complexity of post-upgrade checks by using objective performance metrics as decision criteria.
3Reliability
If in-house testing is performed before deployment, then some issues can be identified, but it fails to capture unique characteristics of customer networks
Solution Approach 1:
The system creates a universal verification mechanism that works across different customer network environments. By deploying updated versions to shadow dataplanes in production environments, the system achieves multi-functionality: it verifies compatibility, measures performance impact, and validates real-world behavior all within the same framework, eliminating the need for separate in-house and customer-specific testing phases.
Solution Approach 2:
The system introduces an intermediary layer in the form of shadow dataplanes that act as mediators between development and production environments. These intermediary dataplanes execute updated versions in controlled production settings, collecting performance data that bridges the gap between in-house testing and actual customer deployment, thereby capturing real network characteristics without requiring direct customer environment access.
Data Source
AI summary
A system and method are provided for implementing a network component and verifying an update of the network component. The network component can be, e.g., a software-defined wide area network, a firewall, a router, or a load balancer. The network component can be an embedded network edge device that is implemented, e.g., in software, in circuitry, or using hardware acceleration (e.g., a data processing unit (DPU), a smart network interface card (SmartNIC), etc.). The updated version of the network component is verified by implementing it on a shadow dataplane concurrently with the current version operating on a primary dataplane, and comparing the performances of these two versions. Based on this comparison satisfying various verification criteria, the updated version passes a verification test and can be promoted to the primary dataplane.