Container Network Manager for Switch Configuration Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network switches are not container-aware, requiring manual configuration for each container deployment and updates, leading to burdensome and error-prone processes, especially with changes in container IP addresses or port numbers.

Innovation Solution

Implementing a container network manager that interacts with container orchestration engines on behalf of network switches, allowing them to obtain and update container attribute data via lifecycle notifications, thereby automating the configuration of networking functionality without direct interaction with container orchestration engines.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If manual configuration is used for each container deployment and updates, then network switches can be simple and non-container-aware, but the configuration process becomes burdensome and error-prone

Engineering Contradiction:
Improvenetwork switch complexityVSAvoidconfiguration process ease
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent introduces a container network manager as an intermediary component that sits between the container orchestration engine and the network switch. This manager automatically translates container attribute data into network configuration data and pushes it to the network switch, eliminating the need for manual configuration while keeping the network switch itself simple and non-container-aware.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service configuration by having the container network manager automatically subscribe to container lifecycle notifications, extract relevant attribute data, generate appropriate network configurations, and push updates to the network switch without human intervention. This automates the entire configuration workflow from container deployment to network setup.

Inventive Principle:
Principle #25Self-service

2Extent of automation

If manual configuration is used for container networking, then automation extent is low, but system complexity remains manageable

Engineering Contradiction:
Improveconfiguration automationVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent segments the configuration automation functionality into a dedicated container network manager component, separate from both the container orchestration engine and the network switch. This segmentation allows automation to be introduced without complicating the core network switch, as the manager handles all container-aware logic independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The container network manager serves as an intermediary layer that absorbs the complexity of container lifecycle management and attribute extraction. It translates complex container events into simple network configuration commands, thereby increasing automation while containing system complexity within the manager component itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If network switches are made container-aware to automatically configure networking, then configuration accuracy improves, but device complexity increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidnetwork switch complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

Instead of making the network switch container-aware, the patent uses a container network manager as an intermediary that extracts container attribute data (such as IP addresses, port mappings, and network policies) from lifecycle notifications and translates it into accurate network configurations. This achieves high configuration accuracy while keeping the network switch simple.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The container network manager creates a copy or representation of container attribute data from lifecycle notifications and uses this copied information to generate network configurations. This copying approach ensures accurate configuration without requiring the network switch to directly process or understand container-specific data structures.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If manual updates are performed when container attributes change, then adaptability is limited, but operational simplicity is maintained

Engineering Contradiction:
Improvedynamic configuration adaptabilityVSAvoidoperational simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The container network manager subscribes to container lifecycle notifications that provide real-time feedback about container events (creation, deletion, attribute changes). This feedback mechanism enables the system to automatically detect when container attributes change and dynamically update network configurations accordingly, providing high adaptability without manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system transitions from static manual configuration to dynamic automated configuration. The container network manager continuously monitors container lifecycle events and automatically adjusts network configurations in real-time as container attributes change, enabling the system to adapt dynamically to changing container deployments while maintaining operational simplicity.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10659301B2Configuring container attribute data on network switches to enable networking functionality
Publication Date: 2020.05.19 CISCO TECHNOLOGY INC
  • US10659301B2 patent drawing
  • US10659301B2 patent drawing
  • US10659301B2 patent drawing

AI summary

An approach enables networking functionality to be configured at network switches for containers hosted by computing devices. A container supervisor on the network switch is configured to obtain, via a container network manager, container attribute data for containers hosted by the computing devices. The container network manager is configured to interact with and manage container orchestration engines on behalf of the containers. This allows the network switch to be container orchestration agnostic. The network switch enables networking functionality for the containers by updating container configuration data on the networking switch based upon the container attribute data obtained from the container network manager. This may include, for example, updating hardware tables on the network switch with the container attribute data to allow the network switch, and applications executing on the network switch, to perform networking functionality with respect to the containers.