Shared Computing Resource Reassignment Without Non-Volatile Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

High-performance computing resources are often underutilized due to stringent security requirements and procedural delays when sharing computing resources between projects, particularly in environments with classified data, leading to inefficiencies in resource allocation and increased costs.

Innovation Solution

A reservation-based high-performance computing system that removes non-volatile storage from shared computing resources, allowing for quick reassignment by powering down, disconnecting, and reconnecting these resources between projects, while maintaining data security through volatile storage and emulation of local data storage, thereby avoiding the need for sanitization and reducing auditing requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of stationary object

If shared computing resources are equipped with non-volatile storage to maintain data between projects, then data persistence is improved, but security compliance and reassignment speed deteriorate due to sanitization requirements

Engineering Contradiction:

Improvedata persistenceVSAvoidreassignment speed

Core Design Contradiction:

Duration of action of stationary objectVSProductivity

Solution Approach 1:

The patent removes non-volatile storage devices from shared computing resources, extracting the data persistence function from the shared system. This eliminates the need for sanitization procedures while maintaining security compliance, enabling rapid reassignment between projects.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system uses volatile storage that is cleared upon each project transition, treating data storage as a temporary, disposable function rather than a persistent one. This approach prioritizes security and reassignment speed over long-term data retention in shared resources.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

2Adaptability or versatility

If virtualization is implemented to enable sharing of computing resources between projects, then resource utilization is improved, but security compliance deteriorates due to increased auditing requirements

Engineering Contradiction:

Improveresource sharing capabilityVSAvoidauditing complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments computing resources into dedicated core computing resources with non-volatile storage and shared computing resources without non-volatile storage. This segmentation allows resource sharing through physical reassignment rather than virtualization, reducing auditing complexity while maintaining security compliance.

Inventive Principle:

Principle #1Segmentation

3Productivity

If shared computing resources are reassigned between projects, then resource utilization is improved, but time consumption increases due to sanitization and reconfiguration procedures

Engineering Contradiction:

Improveresource utilizationVSAvoidreassignment time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary configuration by removing non-volatile storage from shared computing resources before projects begin. This preliminary action eliminates the need for time-consuming sanitization procedures during reassignment, reducing reassignment time while maintaining security.

Inventive Principle:

Principle #10Preliminary action

4Productivity

If non-volatile storage is removed from shared computing resources, then reassignment speed is improved, but data storage capability deteriorates

Engineering Contradiction:

Improvereassignment speedVSAvoiddata storage capacity

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The system segments data storage functionality between core computing resources (with non-volatile storage for persistent data) and shared computing resources (without non-volatile storage for temporary processing). This segmentation enables rapid reassignment of shared resources while maintaining data storage capability in dedicated resources.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11593171B2Reservation-based high-performance computing system and method

Publication Date: 2023.02.28 RAYTHEON CO

AI summary

A method includes communicatively coupling a shared computing resource to core computing resources associated with a first project. The core computing resources associated with the first project are configured to use the shared computing resource to perform data processing operations associated with the first project. The method also includes reassigning the shared computing resource to a second project by (i) powering down the shared computing resource, (ii) disconnecting the shared computing resource from the core computing resources associated with the first project, (iii) communicatively coupling the shared computing resource to core computing resources associated with the second project, and (iv) powering up the shared computing resource. The core computing resources associated with the second project are configured to use the shared computing resource to perform data processing operations associated with the second project. The shared computing resource lacks non-volatile memory to store data related to the first and second projects.