Log-Based Service Package Porting Layer Removal

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software porting in complex computing environments, such as cloud computing, is challenging due to the numerous configurations and the need for extensive testing across different platforms, leading to high costs and time consumption.

Innovation Solution

The method involves using component descriptions to provision and build service packages in a layered approach, collecting log information on build failures, and removing components if the failures are related to a specific layer, thereby reducing the number of necessary tests and simplifying the porting process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If extensive testing is performed across all configurations to ensure software compatibility, then reliability of software porting is improved, but loss of time and productivity deteriorate

Engineering Contradiction:
Improvesoftware compatibilityVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the software package into multiple layers (first layer, second layer, etc.) and systematically tests each layer independently. This segmentation allows the testing process to focus on specific components rather than testing all configurations simultaneously, reducing overall testing time while maintaining reliability through systematic validation of each layer's compatibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary analysis of log information to identify build failures before conducting exhaustive testing. By analyzing logs upfront to determine which components are incompatible with specific layers, the system avoids performing unnecessary tests on known-incompatible configurations, thereby reducing testing time while preserving reliability by focusing tests only on potentially compatible combinations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive testing across all configurations is conducted to ensure software compatibility, then reliability is improved, but productivity deteriorates

Engineering Contradiction:
Improvesoftware compatibilityVSAvoidporting efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the software package into hierarchical layers and tests them systematically. This segmentation enables parallel testing of different layers and eliminates redundant test cases, significantly improving porting efficiency while maintaining comprehensive compatibility validation through structured testing of each layer's component descriptions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary log analysis to identify incompatible components before executing the full testing sequence. This preliminary action filters out known-incompatible configurations, allowing the testing process to focus only on viable combinations, thereby enhancing productivity without compromising the reliability of compatibility assurance.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If all components are retained for testing to ensure complete coverage, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvetesting coverageVSAvoidtesting system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent organizes the testing system into structured layers with clear hierarchies. Each layer contains specific components with associated descriptions, creating a manageable organizational structure. This segmentation reduces system complexity by providing a systematic framework for tracking and testing components, while still achieving comprehensive coverage through methodical layer-by-layer validation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary filtering of components based on log analysis results before initiating comprehensive testing. By removing components that are already known to be incompatible with specific layers, the system reduces the number of components that need to be managed and tested, thereby reducing device complexity while maintaining reliable coverage of all potentially compatible configurations.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If extensive testing is performed to identify incompatible components, then reliability is improved, but loss of substance increases

Engineering Contradiction:
Improvecompatibility accuracyVSAvoidtesting resources
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent performs preliminary analysis of log information to identify build failures and incompatible components before conducting exhaustive testing. This preliminary action allows the system to eliminate known-incompatible components from the testing pool, reducing the consumption of testing resources (time, computational power, etc.) while maintaining high reliability by ensuring that all potentially compatible components are still thoroughly tested.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10296331B2Log-based software porting
Publication Date: 2019.05.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10296331B2 patent drawing
  • US10296331B2 patent drawing
  • US10296331B2 patent drawing

AI summary

Methods, computer systems and computer program products for service packages porting are provided. Aspects include a computer implemented method for a service package porting is provided. One or more processors provision a component of a first layer based on a plurality of component descriptions and build the service package on the first layer. Hence the one or more processors collect first log information that relates to build failures of the service package. According to another embodiment of the present invention, the method further comprises determine whether a build failure is related to the first layer based on the first log information and remove the component of the first layer if it is determined that the build failure is related to the first layer.