Process Deployment Controller Image Generation Across Architectures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing deployment technologies face challenges in deploying applications across multiple architectures when the infrastructure's component description is initially unavailable to the process deployment controller, leading to errors and inability to create necessary images for executing applications.

Innovation Solution

A process deployment controller generates a partial image by executing source code from a template repository and uses a component registry to retrieve the missing infrastructure component description, creating an updated image that includes this information, enabling the execution of applications on diverse infrastructures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If the process deployment controller creates an image without accessing the infrastructure component description, then the deployment process can start, but the image lacks necessary infrastructure information leading to deployment failures

Engineering Contradiction:
Improveimage creation capabilityVSAvoidinfrastructure component description
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The system performs preliminary actions by creating a partial image first with available information, then subsequently retrieving and integrating the missing infrastructure component description from a registry. This staged approach enables the deployment controller to proceed with image creation even when complete infrastructure information is initially unavailable.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A component registry is introduced as an intermediary between the process deployment controller and the infrastructure component description. This intermediary stores and provides the necessary infrastructure information, enabling the controller to obtain complete image data without direct access to the infrastructure itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the process deployment controller waits for the infrastructure component description to be available, then the image can be complete, but the deployment time increases

Engineering Contradiction:
Improveimage completenessVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system creates the partial image immediately with available information rather than waiting for complete infrastructure descriptions. This preliminary image creation eliminates deployment delays while ensuring image completeness is achieved subsequently through registry retrieval of missing components.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the process deployment controller operates without infrastructure component description access, then the system is more flexible, but the deployment accuracy decreases

Engineering Contradiction:
Improvedeployment flexibilityVSAvoiddeployment accuracy
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The component registry serves as an intermediary that provides accurate infrastructure component descriptions to the process deployment controller. This enables the system to maintain high deployment accuracy across diverse infrastructures while preserving flexibility, as the controller can operate independently of direct infrastructure access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system achieves universality by using a standardized component registry interface that works across multiple infrastructure types. The process deployment controller can deploy to various architectures without needing direct access to each infrastructure's specific component descriptions, maintaining both flexibility and accuracy.

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

Data Source

PatentUS11366683B2Images deployment system across multiple architectures
Publication Date: 2022.06.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11366683B2 patent drawing
  • US11366683B2 patent drawing
  • US11366683B2 patent drawing

AI summary

A process deployment controller creates an updated image for an intermediary engine in order to execute one or more applications on a host infrastructure. The process deployment controller generates a partial image by executing source code from a template repository. The partial image provides a structure used to create an intermediary engine used with a container, which includes an application, as well as binaries and libraries required to execute the application in an infrastructure via the intermediary engine. The process deployment controller transmits an identifier of the infrastructure to a component registry; receives a component description of the infrastructure from the component registry; and uses the component description to create an updated image of the partial image. The process deployment controller, upon receiving a request for the application to run on the infrastructure, utilizes the updated image and intermediary engine to execute the application on the infrastructure.