Substrate-Managed Containers for Scalable Cloud Control Planes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional cloud computing environments utilizing virtual machines face inefficiencies due to resource quantization, duplication of operating systems and agents, and difficulty in scaling, leading to capacity waste and operational challenges, especially in managing multiple regions.

Innovation Solution

Implementing a substrate managed container (SMC) infrastructure that uses container-based virtualization with a dynamic pool of computing nodes, managed by a control plane, to deploy applications efficiently, reducing duplication and enabling flexible scaling and patching through a shared immutable operating system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If virtual machine-based virtualization is used, then resource isolation and security are improved, but resource utilization efficiency deteriorates due to quantization and duplication

Engineering Contradiction:

Improveresource isolationVSAvoidresource utilization efficiency

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

Multiple virtual machine instances are merged into a single container runtime environment, allowing shared use of operating system kernels and system libraries. This consolidation eliminates the need for separate OS copies in each VM, reducing resource duplication while maintaining isolation through container-level security mechanisms.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The container runtime environment serves multiple functions simultaneously: it provides process isolation, resource management, security boundaries, and application execution capabilities that were previously required by full virtual machine instances. This multi-functional approach reduces overall system overhead.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Stability of the object's composition

If static pool of computing nodes is used, then system stability is improved, but scalability deteriorates due to difficulty in on-demand scaling

Engineering Contradiction:

Improvesystem stabilityVSAvoidscalability

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system transitions from a static pool of computing nodes to a dynamic pool where container instances can be rapidly created, moved, and destroyed based on demand. The container orchestration platform enables automatic scaling by dynamically provisioning container runtimes on available hardware without requiring pre-configured static allocations.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The computing node pool is segmented into modular container runtime instances that can be independently managed, scaled, and distributed across different physical hosts. This segmentation allows flexible allocation of computational resources while maintaining system stability through standardized container interfaces.

Inventive Principle:

Principle #1Segmentation

3Reliability

If manual curation of services is used, then service quality is improved, but operational complexity deteriorates as number of regions grows

Engineering Contradiction:

Improveservice qualityVSAvoidoperational complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The container orchestration platform implements self-service capabilities that automatically manage service deployment, scaling, and maintenance across multiple regions. The system autonomously handles resource allocation, load balancing, and failure recovery without requiring manual intervention, reducing operational complexity while maintaining service quality through automated quality assurance mechanisms.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system incorporates continuous feedback loops that monitor service performance, resource utilization, and system health across all regions. This feedback enables automatic adjustments to maintain service quality standards while simplifying operations through closed-loop control mechanisms that respond to changing conditions without human intervention.

Inventive Principle:

Principle #23Feedback

4Reliability

If duplicated copies of operating systems are maintained, then system reliability is improved, but resource wastage increases

Engineering Contradiction:

Improvesystem reliabilityVSAvoidresource wastage

Core Design Contradiction:

ReliabilityVSLoss of substance

Solution Approach 1:

Multiple container instances share a common operating system kernel and system library space, eliminating the need for duplicated OS copies. This merging reduces resource wastage significantly while maintaining reliability through container-level isolation mechanisms that provide security and stability boundaries without requiring separate operating system instances.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS12615220B2Control plane techniques for substrate managed containers

Publication Date: 2026.04.28 ORACLE INT CORP

AI summary

Techniques discussed herein include providing a cloud computing environment in which applications are deployed using virtual-machine-based virtualization with a static pool of computing nodes (e.g., substrate nodes, overlay nodes) and container-based virtualization with a dynamic pool of computing nodes (e.g., nodes managed by a container orchestration platform). The control plane functionality may be invoked by a deployment orchestrator (e.g., using a client of the container orchestration platform). In some embodiments, the control plane may include a set of applications that are configured to communicate with core services for certificate generation and rotation, namespace and quota management, metric monitoring and alarming, node authentication, and cluster membership management.