Container Operation Control for Large Data Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Operating applications with large-scale data on containers is inefficient due to the time it takes to obtain and start Docker images, and managing combinations of Docker images and data is complex, especially when dealing with large data sets like learning data and models, which often exceed the 10 GB limit and require external storage.

Innovation Solution

An operation control method that stores data used by an application separately from the Docker image, allowing the image to be started quickly without embedding large data, and manages data and image combinations through a catalog system that registers definitions for starting containers, enabling users to specify only the catalog name and version for operation without knowing the data storage locations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If large-scale data is embedded in the Docker image, then the application can access data without external storage, but the image size exceeds the 10 GB limit and startup time increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidimage size
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent separates data from the Docker image by creating a catalog that references external data storage locations. The Docker image contains only the application and necessary runtime dependencies, while large-scale data is stored externally and mounted during container startup. This segmentation resolves the contradiction by allowing the image to remain small while data remains accessible through the catalog-defined mounting mechanism.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If data is stored externally, then image size is reduced, but managing combinations of Docker images and data becomes complex

Engineering Contradiction:
Improveimage sizeVSAvoidmanagement complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent introduces a catalog as an intermediary layer between Docker images and external data. The catalog stores structured definitions that map image identifiers to data storage locations and mounting configurations. This intermediary simplifies management by providing a centralized registry that automatically handles the matching and mounting of data to images, eliminating the need for manual combination management.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of time

If Docker images are obtained and started quickly, then container startup time is reduced, but large-scale data cannot be accessed without external storage configuration

Engineering Contradiction:
Improvestartup timeVSAvoiddata configuration complexity
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The patent performs preliminary actions by pre-defining data mounting configurations in the catalog before container startup. The catalog is prepared in advance with all necessary data location and mounting path information. During container startup, the system simply references the pre-configured catalog entries, allowing quick data mounting without requiring complex real-time configuration decisions, thus reducing startup time while maintaining ease of operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10810025B2Operation control method, and apparatus for operation control, and non-transitory computer-readable storage medium for storing program
Publication Date: 2020.10.20 FUJITSU LTD
  • US10810025B2 patent drawing
  • US10810025B2 patent drawing
  • US10810025B2 patent drawing

AI summary

An operation control method includes: storing data used by an application according to a first definition with respect to an interface of data operation when defining a way of starting a container, the container representing a region in which an execution environment of the application is disposed; storing an image file for the execution environment of the application; and registering a second definition into definition information, the second definition indicating the way of starting the container and being obtained by adding data information to information regarding the image file for the execution environment of the application in accordance with a third definition with respect to an interface of container operation, the data information being information regarding data used by the application in the container.