Container IP Persistence via MAC-VLAN Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network management systems face inefficiencies when deploying and migrating software containers, as they require frequent network reconfiguration due to network address translation (NAT) changes, which disrupt network connectivity.
Innovation Solution
The Data Center Network Manager (DCNM) employs a namespace modification mechanism to create direct connections between containers and network planes using MAC-VLAN interfaces, ensuring consistent IP addresses across container movements and avoiding NAT changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If containers are migrated across compute nodes using conventional network management, then container mobility is enabled, but network connectivity is disrupted due to NAT changes
Solution Approach 1:
The patent introduces a network controller as an intermediary that manages IP address allocation and maintains mapping between container identifiers and IP addresses. This mediator enables containers to migrate across compute nodes while the network controller ensures continuous connectivity by updating NAT rules and reassigning IP addresses without disrupting the underlying network infrastructure.
Solution Approach 2:
The system dynamically changes network parameters (IP addresses, NAT rules) based on container migration events. When a container moves to a new compute node, the network controller updates the IP address assignment and corresponding NAT translations, allowing the container to maintain network connectivity despite changes in its physical location and network environment.
2Productivity
If containers are frequently deployed and updated, then application deployment speed is improved, but network reconfiguration overhead increases
Solution Approach 1:
The network controller pre-allocates IP addresses from pools and establishes NAT rule templates before containers are deployed. This preliminary preparation allows containers to be rapidly instantiated and connected to the network without requiring time-consuming ad-hoc network configuration, thus accelerating deployment while minimizing reconfiguration overhead.
Solution Approach 2:
The system implements automated IP address assignment and NAT rule generation, where the network controller autonomously handles network reconfiguration in response to container deployment events. This self-service mechanism eliminates manual network configuration steps, reducing the time loss associated with frequent container updates and deployments.
3Productivity
If IP addresses are reassigned to new containers after container loss, then IP address utilization is improved, but network address translation complexity increases
Solution Approach 1:
The network controller serves multiple functions: it manages IP address allocation, maintains container-to-IP mappings, generates NAT rules, and handles reassignment upon container loss. This multi-functional approach consolidates NAT management complexity into a single controller that can efficiently handle IP address utilization and reassignment while maintaining overall system simplicity.
Data Source
AI summary
A network controller deploys network management applications to containers hosted on compute nodes. For each container on each compute node, the controller determines the network connectivity required by the application; assigns to the container one or more Internet Protocol (IP) addresses that satisfy the network connectivity, and provides the one or more IP addresses to the container; upon detecting the container is lost, blocks the one or more IP addresses so that the they cannot be re-assigned to any other container; and upon detecting that the application has been re-deployed to a new container on a new compute node, unblock the blocked one or more IP addresses, and assign and send the one or more IP addresses to the new container to enable the new container to establish the network connectivity required by the application without network address translation.