Automated Maintenance Scheduling for Containerized Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In data centers with container orchestration systems, determining optimal maintenance times is challenging due to complex interactions between services and global user patterns, leading to potential significant downtime impacts on end users, especially in software-defined data centers where dependencies are dense and difficult to analyze manually.

Innovation Solution

An automated system that determines service dependencies and learns collective usage patterns to predict low-impact maintenance intervals by analyzing resource utilization and network interactions, providing a recommended maintenance schedule that minimizes overall impact across dependent services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Object-affected harmful factors

If maintenance is performed during off-peak hours to reduce user impact, then user experience is improved, but determining optimal times becomes complex and error-prone due to global user patterns and service dependencies

Engineering Contradiction:
Improveuser impact from maintenance downtimeVSAvoidcomplexity of determining optimal maintenance times
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent introduces an automated maintenance scheduling system that acts as an intermediary between maintenance needs and user impact. This system analyzes service dependencies, collects usage metrics globally, and automatically determines optimal maintenance windows, eliminating the complexity of manual analysis while protecting user experience.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback loops by continuously collecting usage metrics from global users and analyzing service dependencies. This feedback enables the automated scheduling system to learn from actual user patterns and adjust maintenance timing decisions to minimize impact, transforming the complex decision-making process into an automated adaptive system.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If manual analysis of service dependencies is performed, then some maintenance scheduling can be achieved, but the dense interdependencies in software-defined data centers make manual analysis infeasible and error-prone

Engineering Contradiction:
Improveease of maintenance schedulingVSAvoiddifficulty of analyzing service dependencies
Core Design Contradiction:
Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent replaces the mechanical process of manual dependency analysis with an automated computational system. The system automatically traverses service dependency graphs, collects usage metrics, and calculates optimal maintenance windows, substituting human analytical effort with automated algorithms that can handle the complexity of dense service interdependencies in software-defined data centers.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The maintenance scheduling system performs self-service by automatically analyzing its own service dependencies and usage patterns. The system collects metrics from itself and other services, traverses the dependency graph, and generates maintenance recommendations without external intervention, making the complex analysis process transparent and automated.

Inventive Principle:
Principle #25Self-service

3Ease of manufacture

If broadcast approaches are used for maintenance scheduling, then simple implementation is achieved, but significant downtime impact on end users occurs due to lack of optimized timing

Engineering Contradiction:
Improvesimplicity of maintenance scheduling implementationVSAvoiddowntime impact on end users
Core Design Contradiction:
Ease of manufactureVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by pre-analyzing service dependencies and collecting usage metrics before maintenance is needed. The system determines optimal maintenance windows in advance based on learned user patterns and dependency analysis, allowing maintenance to be scheduled at optimal times rather than using simple broadcast approaches that cause unnecessary downtime impact.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11381483B2Maintenance recommendation for containerized services
Publication Date: 2022.07.05 VMWARE INC
  • US11381483B2 patent drawing
  • US11381483B2 patent drawing
  • US11381483B2 patent drawing

AI summary

A maintenance recommendation for containerized services can find a time to perform maintenance on a particular service based on resource usage patterns such that the maintenance will have a reduced impact on dependent services. The dependent services can be determined for the particular service based on network interactions between the services.