Containerized Compute Network Configuration via Dynamic Driver Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing approaches to network configuration in multi-link platforms with multiple containers lack scalable configuration at initialization, particularly in supporting dynamic network driver requirements for each container.
Innovation Solution
The implementation involves a processor subsystem and non-transitory computer-readable media that execute a basic I/O service to create a link aggregation table, a first operating system service to instantiate virtual link aggregation tables based on network bandwidth policies, and a second operating system service to instantiate an operating system driver based on dynamic detection of network driver requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing approaches are used for network configuration in virtualized systems, then basic virtualization functionality is maintained, but scalable platform configuration at container initialization is not supported
Solution Approach 1:
The patent segments the network configuration process into distinct layers: a base layer that defines platform-wide link aggregation policies and container-specific network policies, and individual container instances that inherit and apply these policies. This segmentation allows scalable configuration by separating common configuration (base layer) from instance-specific configuration (container layer), enabling efficient initialization without repeating entire configuration sets for each container.
Solution Approach 2:
The patent implements preliminary action by pre-defining link aggregation policies at the platform base layer before container instantiation. The base layer configures available network links, aggregation parameters, and policies in advance, so that when containers are initialized, they can inherit these pre-configured settings rather than requiring complex runtime configuration. This preliminary setup enables scalable deployment of multiple containers with consistent network policies.
2Reliability
If dynamic network driver requirements are supported for each container, then network performance is optimized, but configuration scalability is reduced
Solution Approach 1:
The patent implements self-service by enabling container instances to automatically detect their network driver requirements and dynamically select appropriate drivers from the base layer configuration. Each container autonomously determines its network needs and configures itself without manual intervention, while still adhering to platform-wide policies. This self-service mechanism maintains reliability through proper driver selection while preserving initialization speed by eliminating complex manual configuration processes.
Solution Approach 2:
The patent applies dynamics by allowing the network driver configuration to be flexible and adaptive at the container instance level. While the base layer establishes static policies and available drivers, individual containers can dynamically select and configure drivers based on their specific requirements. This dynamic adaptation ensures reliable network communication for diverse container needs while maintaining scalability through automated selection rather than static pre-assignment.
3Productivity
If multiple operating systems run on a single information handling system, then resource utilization is improved, but network driver compatibility across different OSes becomes more complex
Solution Approach 1:
The patent implements universality by creating a base layer that defines platform-wide link aggregation policies and a repository of network drivers that can be shared across multiple operating systems. The base layer configuration serves all container instances regardless of their underlying OS, providing a universal configuration framework. Containers can inherit and apply these universal policies while the system automatically manages driver compatibility, allowing diverse OSes to coexist with consistent network configuration management.
Data Source
AI summary
An information handling system may include a processor subsystem and non-transitory computer-readable media communicatively coupled to the processor subsystem and storing instructions, the instructions configured to, when read and executed by the processor subsystem: execute a basic/input output service to create a link aggregation table with details based on wireless and wired network interface modules present within the information handling system; execute a first operating system service on a container instantiated on a hypervisor of the information handling system to instantiate virtual link aggregation tables for the container based on a network bandwidth policy of the container and link aggregation capabilities as set forth in the link aggregation table; and execute a second operating system service on the hypervisor to instantiate an operating system driver based on operating systems for network instances of link aggregation drivers and dynamic detection of network driver requirements determined by the first operating system service.