Container Scheduling in Domain Controller Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current container scheduling and deployment methods in domain controller systems fail to achieve load balance and dynamic adjustment, leading to decreased user experience and performance when a node is in a high-load state.

Innovation Solution

A method and apparatus for scheduling and deploying containers in a domain controller system, which includes using a domain controller node for formal environments and a remote server for development test environments, enabling dynamic management, capacity expansion/reduction, and decoupling of functional modules using containerd and K3s deployment modes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If container scheduling and deployment is performed based on a domain controller node in a formal environment, then system availability and performance are improved, but the system lacks dynamic adjustment capability when nodes are in high-load states

Engineering Contradiction:
Improvesystem availabilityVSAvoiddynamic adjustment capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic container scheduling by enabling the domain controller node to flexibly adjust container deployment based on real-time system load conditions. When the node is in a high-load state, the system can dynamically reduce or pause container scheduling to maintain system stability, and resume scheduling when load decreases, thus achieving both high availability and dynamic adaptability

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If container scheduling is centralized on a domain controller node, then deployment control is improved, but load balance across nodes cannot be achieved

Engineering Contradiction:
Improvedeployment controlVSAvoidload balance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent employs feedback mechanisms where the domain controller node continuously monitors system load conditions and adjusts container scheduling decisions accordingly. This feedback loop enables the system to maintain centralized deployment control while achieving load balance by dynamically adapting scheduling behavior based on real-time node status, preventing overload and ensuring equitable resource distribution

Inventive Principle:
Principle #23Feedback

3Object-affected harmful factors

If the domain controller system maintains strict security protocols, then network attack resistance is improved, but system expansibility and flexibility are reduced

Engineering Contradiction:
Improvenetwork attack resistanceVSAvoidsystem expansibility
Core Design Contradiction:
Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The patent introduces containerization as an intermediary layer between the domain controller node and external networks. This container-based architecture provides security isolation that protects the core system from network attacks while maintaining system expansibility, as containers can be dynamically deployed and managed without compromising the underlying secure infrastructure

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240054000A1Container scheduling and deployment method and apparatus, and domain controller system
Publication Date: 2024.02.15 BLACK SESAME TECH (CHONGQING) CO LTD
  • US20240054000A1 patent drawing
  • US20240054000A1 patent drawing
  • US20240054000A1 patent drawing

AI summary

A container scheduling and deployment method and apparatus, and a domain controller system. The method includes: scheduling and deploying, based on a domain controller node of the domain controller system, a container corresponding to the domain controller node when a current application environment of the domain controller system is a formal environment; and scheduling and deploying, based on a remote server of the domain controller system, the container when the current application environment of the domain controller system is a development test environment. According to one aspect, a flexible selection of subject used to perform scheduling and deploying on the container of the domain controller node for different application environments may be realized. Therefore, a dynamic management of the domain controller system may be completed, and a high expansibility and high availability of performance of the domain controller system may be ensured.