Logical Volume Expansion for Disk-Limited Application Builds
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Industrial automation devices face challenges in building software applications due to scarce disk space, leading to failed build processes when additional temporary space is required during the build process but not needed post-completion.
Innovation Solution
A method to expand the target device's logical volume using an external storage device through logical volume management (LVM), allowing seamless integration and temporary space allocation during the build process, which is then released after completion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If the build process is performed on the target device with limited internal storage, then the application can be built directly on the target device, but the build process fails due to insufficient disk space
Solution Approach 1:
The patent extends the storage capacity by integrating an external storage device into the logical volume management system, effectively adding another dimension of storage space. The LVM layer abstracts the physical storage boundaries, allowing the build process to access combined internal and external storage as a unified logical volume, thus resolving the disk space insufficiency without changing the target device itself.
Solution Approach 2:
The logical volume management system acts as an intermediary between the build process and the physical storage devices. It manages the integration of internal and external storage devices, presenting a unified logical volume to the build process while handling the complexity of storage integration in the background, thus enabling the build process to proceed with sufficient space.
2Quantity of substance
If external storage device is integrated to expand logical volume, then sufficient space is available for build process, but device complexity increases
Solution Approach 1:
The system automatically detects the external storage device, integrates it with internal storage through LVM, and manages the logical volume configuration without requiring manual user intervention. The automation of storage integration and management reduces the perceived complexity for users while maintaining the expanded storage capability.
Solution Approach 2:
The logical volume management system provides multi-functionality by managing both internal and external storage devices through a unified interface. It handles storage expansion, space allocation, and device integration automatically, making the system versatile in handling different storage configurations without increasing user-facing complexity.
3Reliability
If external storage device is permanently integrated, then build process can always succeed, but storage space is wasted when external storage is not needed
Solution Approach 1:
The storage configuration is made dynamic rather than static. The external storage device is integrated only when needed for the build process and can be dynamically disconnected or have its space released after the build completes. This dynamic approach ensures storage space is available when needed while preventing waste when the external device is not required.
4Productivity
If users delete existing data to free up space, then build process can proceed, but data integrity is compromised
Solution Approach 1:
The external storage device is integrated into the logical volume before the build process begins, proactively providing the necessary space. This preliminary action eliminates the need to delete existing data during the build process, as the expanded logical volume already has sufficient capacity to accommodate the build requirements while preserving all existing data.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A computer-implemented method for building an application image on a target device of an industrial automation system is disclosed. The target device includes an internal storage medium organized into one or more logical volumes. The method includes identifying an external storage device connected to the target device. The method further includes extending a logical volume of the target device through integration between the internal storage medium and the external storage device. The method further includes initiating a build process for building the application image, wherein the extended logical volume is utilized by the build process. The build process necessitates more space than that used by a final artifact resulting from the build process. The method further includes, subsequent to the completion of the build process, shrinking the extended logical volume to its original state prior to the extension, enabling release of the external storage device from the target device.