Unified Object Storage with Native File Protocol Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current virtual computing systems face limitations in resource utilization and performance due to their configuration and operation, particularly when accessing object stores using separate gateway appliances that convert file-based access to object access, leading to latency and scalability issues.

Innovation Solution

Implementing file-based access protocols natively within the object store, allowing users to access objects using either object or file-based access protocols, with on-demand directory creation and unified namespace management to reduce latency and enhance scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a separate gateway appliance is used to convert file-based access to object access, then compatibility with file-based systems is improved, but system complexity and latency increase

Engineering Contradiction:

Improvecompatibility with file-based systemsVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the gateway appliance functionality directly into the object storage system, eliminating the need for a separate conversion layer. The object storage system natively implements file-based access protocols (NFS, SMB) while maintaining object-based protocols (S3, Swift), allowing both access methods to operate through a unified architecture without requiring external translation appliances.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The object storage system is designed to support multiple access protocols simultaneously through a unified namespace. It provides universal access by implementing both object-based protocols (S3, Swift) and file-based protocols (NFS, SMB) within the same system, enabling diverse clients to access stored data through their preferred protocol without requiring separate gateway infrastructure.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If a separate gateway appliance is used to convert file-based access to object access, then compatibility with file-based systems is improved, but latency increases

Engineering Contradiction:

Improvecompatibility with file-based systemsVSAvoidaccess latency

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

Inventive Principle:

Principle #5Merging (Combining)

3Ease of operation

If traditional file-based directory structures are pre-created in object store, then file-based access is improved, but resource consumption increases

Engineering Contradiction:

Improvefile-based accessVSAvoidresource consumption

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The system performs preliminary action by creating directory structures on-demand when first accessed, rather than pre-creating all directories in advance. When a client accesses a path like /data/file.txt, the system automatically creates the /data directory if it doesn't exist, ensuring directories are prepared exactly when needed without wasting resources on empty pre-created structures.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The object storage system provides self-service by automatically creating directory structures as needed during normal operation. The system monitors access patterns and dynamically creates directories when clients attempt to access paths that don't yet exist, eliminating the need for manual or pre-emptive directory creation and optimizing resource utilization based on actual demand.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS11822370B2Concurrent multiprotocol access to an object storage system

Publication Date: 2023.11.21 NUTANIX INC

AI summary

In accordance with some aspects of the present disclosure, a non-transitory computer readable medium is disclosed. The non-transitory computer readable medium includes instructions when executed by a processor cause the processor to write an object to an object store using an object-based access protocol, look up the object from the object store using a file-based access protocol, and create one or more directories on-demand in the object store.