Workload Migration Between Single Node and Multi-Node Environments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating workloads between single node and multi-node environments is challenging due to potential downtime, data loss, and the complexity of configuring different environments, which can result in high costs and resource burdens, including human administration, and risks of incorrect machine configuration.

Innovation Solution

A method and system for migrating workloads between single node and multi-node environments over a Transport Layer Security (TLS) network, which generates and stores files containing workload information, connects to a container cluster, and uses access information to establish a secure connection, thereby avoiding manual configuration and downtime, and ensuring compatibility with the target environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual configuration methods are used for workload migration, then flexibility in configuration is improved, but time consumption and error risk increase

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidmigration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent uses file-based copying of workload configurations and cluster information between environments. The first machine generates a first file containing workload information, and the second machine reads a second file from the container cluster, enabling automated replication of configuration data without manual intervention while maintaining adaptability through environment-specific file formats

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces access information stored in files as an intermediary mechanism to connect the first machine to the container cluster. This intermediary file-based communication layer enables secure workload migration over TLS networks while automating the configuration transfer process, reducing both time and manual configuration requirements

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If automated migration methods are used, then migration speed is improved, but complexity of the migration system increases

Engineering Contradiction:
Improvemigration speedVSAvoidmigration system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the migration process into distinct independent steps: generating workload information files on the first machine, reading cluster configuration files from the container cluster, establishing secure connections over TLS networks, and transferring workloads. This segmentation simplifies the overall system by breaking down the complex migration task into manageable, independently implementable modules

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs self-service migration by automatically generating required files, reading configuration information, establishing connections using stored access information, and executing workload transfers without requiring external manual intervention. This automation improves migration speed while the use of standard file formats and protocols keeps the system complexity manageable

Inventive Principle:
Principle #25Self-service

3Reliability

If secure connection protocols like TLS are implemented, then security is improved, but network configuration complexity increases

Engineering Contradiction:
Improveconnection securityVSAvoidnetwork configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-storing access information including TLS certificates and connection parameters in files on the first machine before migration. This advance preparation eliminates the need for complex real-time TLS configuration during migration, as the secure connection parameters are already available in the workload information files and second file

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent copies secure connection credentials and configuration files between environments using the same file-based mechanism used for workload data. The first machine generates and stores access information files, which are then read and used to establish secure connections to the container cluster, maintaining security while simplifying the migration process

Inventive Principle:
Principle #26Copying

4Quantity of substance

If single node environment is used, then resource requirements are reduced, but scalability is limited

Engineering Contradiction:
Improvecomputational resourcesVSAvoidenvironmental adaptability
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal migration system that can operate between different environment types (single node and multi-node) using the same file-based approach. The first machine can generate workload files that are compatible with both environment types, and the container cluster can read these files regardless of the source environment, enabling the system to adapt to different computational resource requirements while maintaining a consistent migration methodology

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20240214357A1Method to migrate workload between two environments and a system thereof
Publication Date: 2024.06.27 RED HAT INC
  • US20240214357A1 patent drawing
  • US20240214357A1 patent drawing
  • US20240214357A1 patent drawing

AI summary

A method to migrate workload between a single node environment and a multi-node environment over a Transport Layer Security (TLS) network, the method comprises running an application on a first machine in a first environment, wherein the first environment is any one of the environments. The method further comprises generating a first file for the application running on the first machine and storing the first file and the workload created from the first file in the first machine. The method further comprises accessing a second machine that runs a container cluster in a second environment, wherein the second environment is different from the first environment. The method further comprises reading a second file from the container cluster and storing the second file in the first machine. The method further comprises connecting the first machine to the container cluster of the second machine using access information stored in the second file.