PLFS Middleware for HPC Checkpoint Archival in Cloud Object Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

High-performance computing applications require efficient storage of archived checkpoints and results for long periods, but existing cloud object storage APIs are insufficient for handling complex parallel I/O workloads, and traditional parallel file systems are costly for small markets.

Innovation Solution

Implementing a middleware process, such as the Parallel Log-Structured File System (PLFS), that converts complex parallel file-based I/O into object-based workloads, enabling storage in cloud object storage systems while ensuring security through multi-tenancy mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If traditional parallel file systems are used to store archived checkpoints and results, then storage capability is provided, but cost increases significantly for small markets

Engineering Contradiction:
ImprovecostVSAvoidmarket adaptability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces a middleware layer between the HPC application and cloud storage that converts parallel file system I/O operations into cloud object storage API calls. This intermediary enables HPC applications to leverage cost-effective cloud object storage without requiring changes to the applications themselves, resolving the contradiction by making expensive specialized storage accessible through a universal cloud interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal storage interface that works with both traditional parallel file systems and cloud object storage through a common middleware layer. This multi-functional approach allows the same HPC application to access different storage backends (local parallel file systems for performance-critical data, cloud object storage for archival) without rewriting code, thereby reducing costs while maintaining versatility.

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

2Ease of manufacture

If cloud object storage is used to store archived data, then cost is reduced, but security threats increase due to relinquished control over IT resources

Engineering Contradiction:
ImprovecostVSAvoidsecurity threats
Core Design Contradiction:
Ease of manufactureVSObject-affected harmful factors

Solution Approach 1:

The middleware layer acts as a security intermediary that sits between the HPC application and the cloud storage provider. It handles authentication, authorization, and data encryption, allowing the application to access cloud storage without directly exposing itself to security risks. The middleware manages credentials and access controls, preventing direct compromise of cloud resources while maintaining cost benefits.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service security mechanisms where the middleware automatically manages security protocols without requiring manual intervention from the HPC application. Authentication tokens, encryption keys, and access policies are automatically handled by the middleware layer, allowing applications to benefit from cloud storage security without needing to implement their own security infrastructure.

Inventive Principle:
Principle #25Self-service

3Ease of manufacture

If cloud object storage APIs are used directly, then cost is reduced, but capability to handle complex parallel I/O workloads is insufficient

Engineering Contradiction:
ImprovecostVSAvoidI/O workload handling capability
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The middleware serves as a translation layer that converts complex parallel file system I/O patterns (random reads, sequential writes, directory traversals) into cloud object storage API calls. It batches multiple small I/O operations into fewer larger API calls, handles parallel requests efficiently, and manages the asynchronous nature of cloud storage operations, thereby enabling cost-effective cloud storage to handle complex HPC workloads.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The middleware dynamically adjusts I/O parameters and operation characteristics to optimize performance when accessing cloud storage. It changes data access patterns from random sequential access to optimized parallel batch operations, adjusts buffer sizes and request timings, and modifies error handling strategies to match cloud storage characteristics, thereby maintaining productivity while reducing costs.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9069778B1Cloud object store for archive storage of high performance computing data using decoupling middleware
Publication Date: 2015.06.30 EMC IP HLDG CO LLC
  • US9069778B1 patent drawing
  • US9069778B1 patent drawing
  • US9069778B1 patent drawing

AI summary

Cloud object storage is enabled for archived data, such as checkpoints and results, of high performance computing applications using a middleware process. A plurality of archived files, such as checkpoint files and results, generated by a plurality of processes in a parallel computing system are stored by obtaining the plurality of archived files from the parallel computing system; converting the plurality of archived files to objects using a log structured file system middleware process; and providing the objects for storage in a cloud object storage system. The plurality of processes may run, for example, on a plurality of compute nodes. The log structured file system middleware process may be embodied, for example, as a Parallel Log-Structured File System (PLFS). The log structured file system middleware process optionally executes on a burst buffer node.